Transmission of differential broadcast positioning sib for reduced power consumption

Abstract

Positioning assistance data (PAD) is encoded in positioning system information blocks and periodically broadcast by base stations in a differential manner. PAD elements that are different relative to previously broadcast PAD are encoded in a posSIB block separately from PAD that has not changed. Another separate posSIB block includes a reference encoding that identifies the changed PAD and provides scheduling information. A UE can decode the reference encoding and determine whether the UE has previously decoded the changed PAD. If the UE has previously received the PAD but has not yet received the new or changed PAD, the UE can receive and decode the posSIB block with only the changed PAD, thereby improving efficiency.

Description

[0001] Priority requirements

[0002] This application claims priority to Indian Application No. 202041028976, filed on July 8, 2020, entitled “TRANSMISSION OF DIFFERENTIALBROADCAST POSITIONING SIBS FOR REDUCED POWER CONSUMPTION”, which is incorporated herein by reference in its entirety.

[0003] background

[0004] field:

[0005] The topics disclosed in this article relate to the estimation of the location of mobile devices, and in particular to notifying mobile devices to help locate them when broadcast location assistance data has changed.

[0006] information:

[0007] The location of mobile devices (such as cellular phones) can be useful or essential for several applications, including emergency calls, navigation, direction finding, asset tracking, and internet services. The location of a mobile device can be estimated based on information collected from various systems. For example, in cellular networks implemented using 4G (also known as fourth-generation) Long Term Evolution (LTE) radio access or 5G (also known as fifth-generation) “New Radio” (NR), base stations can transmit a Location Reference Signal (PRS). Mobile devices that require PRS transmitted from different base stations can deliver signal-based measurements to a location server (which may be part of an Evolved Packet Core (EPC) or a 5G Core Network (5GCN)) for use in calculating the location estimate of that mobile device. For example, a UE can generate location measurements (such as Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and Receive-to-Transmit (RX-TX) time difference measurements) based on a downlink (DL) PRS. These location measurements can be used in various location methods (such as Time Difference of Arrival (TDOA), Angle of Departure (AOD), and Multi-Cell Round-Trip Time (RTT)). Alternatively, mobile devices can use various positioning methods to calculate an estimate of their own location. Other positioning methods that can be used for mobile devices include using a Global Navigation Satellite System (GNSS) (such as GPS, GLONASS, or Galileo) and using Auxiliary GNSS (A-GNSS), in which a network provides auxiliary data to the mobile device to help it capture and measure GNSS signals and / or calculate a location estimate from GNSS measurements.

[0008] Sending auxiliary data to mobile devices to assist in signal acquisition and measurement and / or calculating location estimates from measurements can be useful for GNSS location and cellular-based location determination. However, sending auxiliary data individually to each mobile device can result in significant latency and / or consume significant resources in the network and / or the mobile devices, including battery usage for network interaction. Therefore, in some implementations, broadcasting auxiliary data to many or all mobile devices may be preferred. In such implementations, mobile devices can benefit from knowing when the broadcast auxiliary data has changed, thus avoiding the repeated reception and processing of auxiliary data that has not yet changed.

[0009] Overview

[0010] Location Assist Data (PAD) is encoded in a Positioning System Information Block (posSIB) and periodically broadcast by the base station in a differential manner. PAD elements that differ from previously broadcast PADs are encoded separately from unchanged PADs in the posSIB block. Another separate posSIB block includes a reference code identifying the changed PAD and provides scheduling information. The UE can decode the reference code and determine whether it has previously decoded the changed PAD. If the UE has previously received a PAD but has not yet received a new or changed PAD, the UE can receive and decode a posSIB block containing only the changed PAD, thereby improving efficiency.

[0011] In one implementation, a method performed by a base station in a wireless network for supporting the broadcasting of location assistance data in the wireless network includes: broadcasting a first block of a Location System Information Block (posSIB) including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has changed compared to location assistance data included in a reference posSIB; and broadcasting the second block of the posSIB containing the changed location assistance data.

[0012] In one implementation, a base station configured to support broadcasting location assistance data in a wireless network includes: an external interface configured to wirelessly communicate with a UE in the wireless network; at least one memory; and at least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: broadcast a first block of a Positioning System Information Block (posSIB) including a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and broadcast the second block of the posSIB containing the changed location assistance data.

[0013] In one implementation, a base station configured to support broadcasting location assistance data in a wireless network includes: means for broadcasting a first block of a Positioning System Information Block (posSIB), the first block including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has changed compared to location assistance data included in a reference posSIB; and means for broadcasting the second block of the posSIB containing the changed location assistance data.

[0014] In one implementation, a non-transient computer-readable storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a base station in a wireless network to support broadcasting location assistance data in the executed wireless network, the program code including instructions for: broadcasting a first block of a Positioning System Information Block (posSIB) including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has changed compared to location assistance data included in a reference posSIB; and broadcasting the second block of the posSIB containing the changed location assistance data.

[0015] In one implementation, a method performed by a location server in a wireless network for supporting the broadcasting of location assistance data in the wireless network includes: determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; generating a plurality of blocks of a Location System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing the modified location assistance data compared to location assistance data included in a reference posSIB; and transmitting the plurality of blocks of the posSIB to a base station.

[0016] In one implementation, a location server configured to support broadcasting location assistance data in a wireless network includes: an external interface configured to wirelessly communicate with a base station in the wireless network; at least one memory; and at least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: determine location assistance data to be broadcast by the base station, the location assistance data including modified location assistance data and unchanged location assistance data; generate a plurality of blocks of Location System Information Blocks (posSIBs), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing location assistance data modified compared to location assistance data included in a reference posSIB; and transmit the plurality of blocks of the posSIBs to the base station.

[0017] In one implementation, a location server configured to support broadcasting location assistance data in a wireless network includes: means for determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; means for generating a plurality of blocks of a Location System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference code for one or more blocks of the posSIB that contain location assistance data, the reference code indicating a second block of the posSIB that contains modified location assistance data; a second block of the posSIB containing location assistance data that has been modified compared to location assistance data included in a reference posSIB; and means for transmitting the plurality of blocks of the posSIB to a base station.

[0018] In one implementation, a non-transient computer-readable storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a location server to support broadcasting location assistance data in a wireless network. The program code includes instructions for: determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; generating a plurality of blocks of a Positioning System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing location assistance data modified compared to location assistance data included in a reference posSIB; and transmitting the plurality of blocks of the posSIB to a base station.

[0019] In one implementation, a method performed by a user equipment (UE) in a wireless network for supporting the broadcasting of location assistance data in the wireless network includes: receiving and decoding a first block of a Location System Information Block (posSIB) broadcast by a base station, the first block of the posSIB including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the changed location assistance data.

[0020] In one implementation, a user equipment (UE) configured to support broadcasting location assistance data in a wireless network includes: a radio transceiver configured to wirelessly communicate with a base station in the wireless network; at least one memory; and at least one processor coupled to the radio transceiver and the at least one memory, wherein the at least one processor is configured to: receive and decode via the radio transceiver a first block of a Location System Information Block (posSIB) broadcast by the base station, the first block of the posSIB including a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and receive and decode via the radio transceiver a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the changed location assistance data.

[0021] In one implementation, a user equipment (UE) configured to support broadcasting location assistance data in a wireless network includes: means for receiving and decoding a first block of a Location System Information Block (posSIB) broadcast by a base station, the first block of the posSIB including a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and means for receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the changed location assistance data.

[0022] In one implementation, a non-transient computer-readable storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) to support broadcasting location assistance data in a wireless network, the program code including instructions for: receiving and decoding a first block of a Positioning System Information Block (posSIB) broadcast by a base station, the first block of the posSIB including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has changed compared to location assistance data included in a reference posSIB; and receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the changed location assistance data.

[0023] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Brief description of the attached diagram

[0025] The accompanying drawings are provided to help describe various aspects of this disclosure, and the drawings are provided for illustrative purposes only and not for limiting the aspects.

[0026] Figure 1 Exemplary wireless communication systems according to various aspects of this disclosure are explained.

[0027] Figure 2A and Figure 2B Example wireless network architectures based on various aspects of this disclosure are explained.

[0028] Figure 3 The explanation can be Figure 1 A block diagram of the design of one of the base stations and one of the user equipment (UE) in the system.

[0029] Figure 4The paper explains posSIB scheduling using posSIB blocks containing a complete Positioning System Information Block (posSIB) payload.

[0030] Figure 5 An example of a signaling stream used to broadcast positioning auxiliary data in a differential manner is shown.

[0031] Figure 6 The posSIB scheduling with differential coding is explained, in which new or changed auxiliary data is encoded and broadcast in separate posSIB blocks.

[0032] Figure 7 The explanation covers posSIB scheduling with differential coding and broadcasting, where posSIB blocks with full posSIB payloads are not broadcast separately.

[0033] Figure 8 The paper explains posSIB scheduling with differential coding and broadcasting, where posSIB blocks with unchanged posSIB payloads are not broadcast separately.

[0034] Figure 9 Another example of a signaling stream used to broadcast positioning auxiliary data in a differential manner is shown.

[0035] Figure 10 A schematic block diagram is shown illustrating some exemplary features of a base station implemented to support broadcast differentially coded positioning assistance data.

[0036] Figure 11 A schematic block diagram is shown illustrating some exemplary features of a location server implemented to support broadcast differentially encoded location assistance data.

[0037] Figure 12 A schematic block diagram is shown illustrating some exemplary features of a UE that is implemented to support broadcast differentially coded positioning assistance data.

[0038] Figure 13 A flowchart is shown of an exemplary method performed by a base station to support the broadcasting of location-aiding data in a wireless network.

[0039] Figure 14 A flowchart is shown of an exemplary method performed by a location server to support the broadcasting of location-aided data in a wireless network.

[0040] Figure 15 A flowchart is shown of an exemplary method executed by a UE to support the broadcasting of location assistance data in a wireless network.

[0041] Detailed description

[0042] Various aspects of this disclosure are provided below in the description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, elements well-known in this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0043] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than the others. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0044] Those skilled in the art will appreciate that the information and signals described below can be represented using any of a variety of different techniques and arts. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0045] Furthermore, many aspects are described in the form of sequences of actions performed by elements of, for example, computing devices. It will be appreciated that the various actions described herein can be performed by special-purpose circuitry (e.g., application-specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be considered to be fully embodied in any form of non-transient computer-readable storage medium storing a corresponding set of computer instructions that, upon execution, will cause an associated processor of the device to perform the functions described herein. Thus, various aspects of this disclosure can be embodied in several different forms, all of which are contemplated to fall within the scope of the claimed subject matter. Furthermore, for each aspect described herein, a corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0046] As used herein, the terms “User Equipment” (UE) and “base station” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a radio access network (RAN). As used herein, the term “UE” can be interchangeably referred to as “access terminal” or “AT,” “client device,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or “UT,” “mobile terminal,” “mobile station,” “mobile device,” or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) (e.g., based on IEEE 802.11, etc.).

[0047] A base station may operate according to one of several RATs when communicating with a UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, B-Node, Evolved B-Node (eNB), New Radio (NR) B-Node (also known as gNB or gNodeB), etc. Additionally, in some systems, the base station may provide purely edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can signal to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can signal to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse or DL / forward traffic channel.

[0048] The term "base station" can refer to a single physical transmission point or multiple physical transmission points that may or may not be located in the same place. For example, when the term "base station" refers to a single physical transmission point, the physical transmission point may be a base station antenna corresponding to a cell of the base station. When the term "base station" refers to multiple physical transmission points located in the same place, these physical transmission points may be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple physical transmission points not located in the same place, these physical transmission points may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to the serving base station). Alternatively, physical transmission points not located in the same place may be the serving base station from which the UE receives measurement reports and neighboring base stations from which the UE is measuring its reference RF signal.

[0049] To support UE location, two main categories of location solutions have been defined: control plane and user plane. Using control plane (CP) location, location-related and location support signaling can be carried over existing network (and UE) interfaces using existing protocols dedicated to signaling transmission. Using user plane (UP) location, location-related and location support signaling can be carried using protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP) as part of other data.

[0050] The 3rd Generation Partnership Project (3GPP) has defined control plane location solutions for UEs using radio access based on GSM (2G), UMTS (3G), LTE (4G), and New Radio (NR) for 5G. These solutions are defined in 3GPP Technical Specifications (TS) 23.271 and 23.273 (common parts), 43.059 (GSM access), 25.305 (UMTS access), 36.305 (LTE access), and 38.305 (NR access). The Open Mobility Alliance (OMA) similarly defines an up-plane location solution called Secure User Plane Location (SUPL), which can be used to locate UEs accessing any of several radio interfaces supporting IP packet access, such as General Packet Radio Service (GPRS) in GSM, GPRS in UMTS, or IP access in LTE or NR.

[0051] Both CP and UP location solutions can utilize a Location Server (LS) to support positioning. The LS can be part of or accessible from the UE's serving or home network, or simply accessible via the Internet or local intranet. If positioning of the UE is required, the LS can initiate a session with the UE (e.g., a positioning session or a SUPL session) and coordinate location measurements performed by the UE and the determination of the estimated location of the UE. During the positioning session, the LS can request the UE's positioning capabilities (or the UE can provide these capabilities without request), provide auxiliary data to the UE (e.g., upon request or without request), and request location estimates or measurements from the UE, such as for GNSS, TDOA, AoD, multi-RTT, and / or enhanced cell ID (ECID) positioning methods. Auxiliary data can be used by the UE to capture and measure GNSS and / or PRS signals (e.g., by providing expected characteristics of these signals such as frequency, expected time of arrival, signal coding, and signal Doppler).

[0052] In UE-based operating modes, auxiliary data may be used by the UE, either additionally or alternatively, to help determine the location estimate from the resulting location measurement (e.g., providing satellite ephemeris data in the case of GNSS positioning or providing base station location and other base station characteristics (such as PRS timing) in the case of ground positioning using, for example, TDOA, AoD, Multi-RTT, etc).

[0053] In UE-assisted operation mode, the UE can return location measurements to the LS, which can determine the UE's estimated location based on these measurements and possibly also on other known or configured data (e.g., satellite ephemeris data for GNSS positioning or base station characteristics (including base station location and possible PRS timing) in cases of ground positioning using, for example, TDOA, AoD, Multi-RTT, etc.).

[0054] In another autonomous operating mode, the UE can perform position-related measurements without any positioning assistance data from the LS, and can further calculate position or position changes without any positioning assistance data from the LS. Positioning methods that can be used in autonomous mode include GPS and GNSS (e.g., in cases where the UE obtains satellite orbit data from data broadcast by the GPS and GNSS satellites themselves) and sensors.

[0055] In the case of 3GPP CP positioning, the LS can be an Enhanced Serving Mobile Location Center (E-SMLC) for LTE access, a Self-reliant SMLC (SAS) for UMTS access, a Serving Mobile Location Center (SMLC) for GSM access, or a Location Management Function (LMF) for 5G NR access. In the case of OMA SUPL positioning, the LS can be a SUPL Positioning Platform (SLP), which can act as any of the following: (i) Home SLP (H-SLP) (in the case of being in or associated with the UE's home network, or in the case of providing a permanent subscription for location services to the UE); (ii) Discovered SLP (D-SLP) (in the case of being in or associated with some other (non-home) network, or in the case of not being associated with any network); (iii) Emergency SLP (E-SLP) (in the case of supporting positioning for emergency calls initiated by the UE); or (iv) Visited SLP (V-SLP) (in the case of being in or associated with the UE's serving network or current local area).

[0056] During a positioning session, the LS and UE can exchange messages defined according to a positioning protocol to coordinate the determination of the estimated location. Possible positioning protocols may include, for example, the LTE Positioning Protocol (LPP) defined by 3GPP in 3GPP TS 36.355 and the LPP Extensions (LPPe) protocols defined by OMA in OMA TS OMA-TS-LPPe-V1_0, OMA-TS-LPPe-V1_1, and OMA-TS-LPPe-V2_0. LPP and LPPe protocols can be used in combination, where an LPP message contains an embedded LPPe message. The combined LPP and LPPe protocols may be referred to as LPP / LPPe. LPP and LPP / LPPe can be used to help support 3GPP control plane solutions for LTE or NR access, in which case LPP or LPP / LPPe messages are exchanged between the UE and the E-SMLC or between the UE and the LMF. LPP or LPPe messages can be exchanged between the UE and the E-SMLC via the UE's Serving Mobility Management Entity (MME) and the Serving Evolved B-Node. LPP or LPPe messages can also be exchanged between the UE and the LMF via the UE's Serving Access and Mobility Management Function (AMF) and Serving NR B-Node (gNB). LPP and LPP / LPPe can also be used to help support OMA SUPL solutions for many types of radio access that support IP messaging, such as LTE, NR, and WiFi, where LPP or LPP / LPPe messages are exchanged between the SUPL-enabled terminal (SET) (SET is the term used for the UE in SUPL) and the SLP, and can be transmitted within SUPL messages such as SUPL POS or SUPL POS INIT messages.

[0057] The LS and the base station (e.g., an evolved B-node for LTE access) can exchange messages enabling the LS to: (i) obtain location measurements for a specific UE from the base station, or (ii) obtain location information (such as the location coordinates of the base station's antennas), the cells supported by the base station (e.g., cell identity), the cell timing of the base station, and / or parameters of signals transmitted by the base station (such as PRS signals) that are not associated with a specific UE. In the case of LTE access, the LPP A (LPPa) protocol can be used to transmit such messages between the base station as an evolved B-node and the LS as an E-SMLC. In the case of NR access, the NRPPA protocol can be used to transmit such messages between the base station as a g-B-node and the LS as an LMF. Note that the terms "parameter" and "information element" (IE) are synonyms and are used interchangeably herein. It should also be noted that the term "posSIB" as used herein refers to a System Information Block (SIB) that includes auxiliary data (also known as "location auxiliary data") used to support the positioning of one or more UEs. However, in some instances, the term "SIB" is used herein to refer to an SIB containing auxiliary data used to support the positioning of one or more UEs. It is further noted that the terms "SI message" and "positioning SI message" are used interchangeably herein to refer to a system information message containing auxiliary data (e.g., auxiliary data in the form of one or more posSIBs).

[0058] Figure 1 An exemplary wireless communication system 100 has been described. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. Base station 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base station may include an eNB (where the wireless communication system 100 corresponds to an LTE network), or a gNB (where the wireless communication system 100 corresponds to a 5G network), or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0059] Each base station 102 can collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or next-generation core (NGC)) via a backhaul link 122, and interface with one or more location servers 172 via the core network 170. Among other functions, base station 102 can also perform functions related to one or more of the following: transmitting user data, radio channel cryptography and decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of alarm messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / NGC) on a backhaul link 134, which can be wired or wireless.

[0060] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, it is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). In some cases, the term “cell” can also refer to a geographical coverage area (e.g., a sector) of a base station in the sense that a carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0061] While the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in handover areas), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that provide service to a restricted group known as a Closed Subscriber Group (CSG).

[0062] The communication link 120 between base station 102 and UE 104 may include downlink (UL) transmission from UE 104 to base station 102 (also known as the reverse link) and / or downlink (DL) transmission from base station 102 to UE 104 (also known as the forward link). The communication link 120 may use MIMO antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0063] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a clear channel assessment (CCA) to determine the availability of the channel before communication.

[0064] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or 5G technology and use the same 5GHz unlicensed spectrum as used by WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can enhance access network coverage and / or increase access network capacity. LTE in unlicensed spectrum may be referred to as LTE Unlicensed (LTE-U), Licensed Assisted Access (LAA), or MulteFire.

[0065] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180, which can operate in mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to a 3 GHz frequency with a 100 mm wavelength. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Accordingly, it will be understood that the foregoing explanations are merely illustrative and should not be construed as limiting the aspects disclosed herein.

[0066] Transmit beamforming is a technique for focusing RF signals in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (referred to as a "phased array" or "antenna array") that generates a beam of RF waves, which can be "guided" to different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship so that radio waves from the separate antennas add together in the desired direction to increase radiation, while simultaneously canceling each other out in the undesired direction to suppress radiation.

[0067] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signal received from that direction (e.g., increase its gain level). Thus, when a receiver is referred to as beamforming in a certain direction, it means that the beam gain in that direction is higher than the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal strength (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), etc.) of the RF signal received from that direction.

[0068] In 5G, the spectrum in which radio nodes (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into several frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems (such as 5G), one of the carrier frequencies is called the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are called “secondary carriers” or “secondary serving cells” or “SCell.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and on the cell in which UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all shared and UE-specific control channels. A secondary carrier is a carrier operating on a second frequency (e.g., FR2). This carrier can be configured once an RRC connection is established between UE 104 and the anchor carrier, and it can be used to provide additional radio resources. The secondary carrier may contain only the necessary signaling information and signals; for example, UE-specific signaling information and signals may not be present in the secondary carrier, as both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Since a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier that a base station is using for communication, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., can be used interchangeably.

[0069] For example, still refer to Figure 1 One of the frequencies utilized by the macrocell base station 102 can be an anchor carrier (or "PCell"), and other frequencies utilized by the macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20MHz aggregated carriers in a multi-carrier system would theoretically result in twice the data rate (i.e., 40MHz) compared to the data rate obtained from a single 20MHz carrier.

[0070] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. Figure 1 In the example, UE190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity from this link), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE190 can indirectly obtain WLAN-based Internet connectivity from this link). In one example, D2D P2P links 192 and 194 can use any known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D)). (etc.) to support.

[0071] The wireless communication system 100 may further include a UE 164, which can communicate with a macrocell base station 102 on a communication link 120 and / or with an mmW base station 180 on an mmW communication link 184. For example, the macrocell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0072] Figure 2AExample wireless network architecture 200 is explained. For example, NGC 210 (also referred to as "5GC") can be functionally considered as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate collaboratively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB 222 to NGC 210, specifically to control plane functions 214 and user plane functions 212. In an additional configuration, eNB 224 can also connect to NGC 210 via NG-C 215 to control plane function 214 and NG-U 213 to user plane function 212. Furthermore, eNB 224 can communicate directly with gNB 222 via backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more eNBs 224 and one or more gNBs 222. The gNB 222 or eNB 224 may be used with UE 204 (e.g., Figure 1 The UE 204 may communicate with any UE depicted herein. Another optional aspect may include one or more location servers 230a, 230b (sometimes collectively referred to as location server 230) (which may correspond to location server 172), which may communicate with control plane function 214 and user plane function 212 in NGC 210, respectively, to provide location assistance to UE 204. Location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server. Location server 230 may be configured to support one or more location services for UE 204, which UE 204 can connect to via the core network, NGC 210, and / or via the Internet (not described). Furthermore, location server 230 may be integrated into components of the core network, or alternatively, may be external to the core network (e.g., in a new RAN 220).

[0073] Figure 2BAnother example wireless network architecture 250 is described. For example, NGC 260 (also referred to as "5GC") can be functionally considered as a core network consisting of control plane functions (AMF) 264, user plane functions (UPF) 262, session management functions (SMF) 266, SLP 268, and LMF 270, which operate collaboratively to form the core network (i.e., NGC 260). User plane interface 263 and control plane interface 265 connect ng-eNB 224 to NGC 260, specifically to UPF 262 and AMF 264, respectively. In an additional configuration, gNB 222 can also connect to NGC 260 via control plane interface 265 to AMF 264 and user plane interface 263 to UPF 262. Furthermore, eNB 224 can communicate directly with gNB 222 via backhaul connection 223, regardless of whether it has direct gNB connectivity to NGC 260. In some configurations, the new RAN 220 may have only one or more gNB 222s, while other configurations include both one or more ng-eNB 224s and one or more gNB 222s. The ng-gNB 222 or eNB 224 can be used with UE 204 (e.g., Figure 1 The base station of the new RAN 220 communicates with the AMF 264 on the N2 interface and with the UPF 262 on the N3 interface.

[0074] The AMF's functions include registration management, connection management, reachability management, mobility management, lawful interception, session management (SM) messaging between UE 204 and SMF 266, transparent proxy service for routing SM messages, access authentication and access authorization, short message service (SMS) messaging between UE 204 and the Short Message Service Function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, and receives the intermediate key established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, the AMF retrieves security material from the AUSSF. The AMF's functions also include security context management (SCM). The SCM receives a key from the SEAF, which is used by the SCM to derive a key that varies depending on the access network. The functionality of the AMF also includes location service management for regulatory services, location service messaging between UE 204 and Location Management Function (LMF) 270 (which may correspond to Location Server 172) and between the new RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for interoperability with EPS, and UE 204 mobility event notification. Furthermore, the AMF also supports functionality for non-3GPP access networks.

[0075] The functions of the UPF include: acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., UL / DL rate enforcement, reflective QoS marking in DL), UL traffic verification (mapping of service data flow (SDF) to QoS flow), transport-level packet marking in UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node.

[0076] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF for routing traffic to the correct destination, control of policy enforcement and QoS, and downlink data notification. The interface used by SMF 266 to communicate with AMF 264 is called the N11 interface.

[0077] Another optional aspect may include an LMF 270, which can communicate with the NGC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the NGC 260, and / or via the Internet (not described).

[0078] Figure 3 A block diagram of a design 300 for base station 102 and UE 104 is shown, which can be Figure 1 One of the base stations and one of the UEs. Base station 102 may be equipped with T antennas 334a to 334t, while UE 104 may be equipped with R antennas 352a to 352r, where generally T≥1 and R≥1.

[0079] At base station 102, transmit processor 320 can receive data destined for one or more UEs from data source 312, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., encode and modulate) the data destined for each UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmit processor 320 can also process system information (e.g., semi-static resource allocation information (SRPI) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor 320 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 332a to 332t. Each modulator 332 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 332 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 332a to 332t can be transmitted via T antennas 334a to 334t, respectively. According to the aspects described in more detail below, position coding can be used to generate synchronization signals to convey additional information.

[0080] At UE 104, antennas 352a to 352r can receive downlink signals from base station 102 and / or other base stations and can provide the received signals to demodulators (DEMODs) 354a to 354r respectively. Each demodulator 354 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 354 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 356 can obtain the received symbols from all R demodulators 354a to 354r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 358 can process (e.g., demodulate and decode) these detected symbols, provide the decoded data for UE 104 to data sink 360, and provide the decoded control information and system information to controller / processor 380. The channel processor can determine the Reference Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Received Quality (RSRQ), Channel Quality Indicator (CQI), and so on. In some respects, one or more components of UE 104 may be included in the housing.

[0081] On the uplink, at UE 104, transmit processor 364 can receive and process data from data source 362 and control information from controller / processor 380 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). Transmit processor 364 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 364 can be pre-encoded by TX MIMO processor 366 where applicable, further processed by modulators 354a to 354r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 102. At base station 102, uplink signals from UE 104 and other UEs can be received by antenna 334, processed by demodulator 332, detected by MIMO detector 336 where applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. The receiver processor 338 can provide decoded data to the data trap 339 and decoded control information to the controller / processor 340. The base station 102 may include a communication unit 344 and communicate with the network controller 389 via the communication unit 344. The network controller 389 may include a communication unit 394, a controller / processor 390, and a memory 392.

[0082] The controller / processor 340 of base station 102, the controller / processor 380 of UE 104, the controller 390 of network controller 389 (which may be location server 172) and / or Figure 3Any other component may perform one or more techniques associated with broadcasting positioning assistance data differentially, as described in more detail elsewhere herein. For example, the controller / processor 340 of base station 102, the controller 390 of network controller 389, the controller / processor 380 of UE 104, and / or Figure 3 Any other component may execute or direct, for example Figure 13 , 14 The processes 1300, 1400, and 1500 and / or other processes as described herein. Memory 342, 382, ​​and 392 may store data and program code for base station 102, UE 104, and network controller 389, respectively. In some aspects, memory 342 and / or memory 382 and / or memory 392 may include a non-transient computer-readable medium storing one or more instructions for wireless communication. For example, these one or more instructions may be executed or direct, when executed by one or more processors of base station 102, network controller 389, and / or UE 104, for example... Figure 13 , 14 The operation of processes 1300, 1400, and 1500 and / or other processes as described herein. Scheduler 346 can schedule the UE for data transmission on the downlink and / or uplink.

[0083] As indicated above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0084] In a particular implementation, UE 104 may have circuitry and processing resources capable of acquiring location-related measurements (also known as location measurements) such as measurements of signals received from GPS or other satellite positioning systems (SPS), measurements of cellular transceivers (such as base station 102), and / or measurements of local transceivers. UE 104 may further have circuitry and processing resources capable of calculating a location lock or estimating the location of UE 104 based on these location-related measurements. In some implementations, the location-related measurements acquired by UE 104 may be transmitted to a location server (such as location server 172, location servers 230a, 230b, or LMF 270), which may then estimate or determine the location of UE 104 based on these measurements.

[0085] The location-related measurements obtained by UE 104 may include measurements of signals received from satellite vehicles (SVs) that are part of an SPS or Global Navigation Satellite System (GNSS) (such as GPS, GLONASS, Galileo, or BeiDou), and / or may include measurements of signals received from ground transmitters (for example, such as base station 102 or other local transceivers) fixed at a known location. UE 104 or a separate location server (e.g., location server 172) may then use any of several positioning methods (such, for example, GNSS, Auxiliary GNSS (A-GNSS), Advanced Forward Link Trilateral Measurement (AFLT), Observation Time Difference of Arrival (TDOA), Enhanced Cellular ID (ECID), TDOA, AoA, Multiple RTT, or combinations thereof) based on these location-related measurements to obtain a location estimate for UE 104. In some of these technologies (e.g., A-GNSS, AFLT, and OTDOA), pseudorange or timing difference can be measured by the UE 104 relative to three or more ground transmitters fixed at known locations, or relative to four or more SVs with accurate known orbit data, or a combination thereof, based at least in part on pilot signals, positioning reference signals (PRS), or other positioning-related signals transmitted by these transmitters or SVs and received at the UE 104. Here, a location server (such as location server 172, location server 230a, 230b, or LMF152) can be able to provide the UE 104 with positioning assistance data, including, for example, information about the signals to be measured by the UE 104 (e.g., expected signal timing, signal encoding, signal frequency, signal Doppler), the location and / or identity of the ground transmitters, and / or signal, timing, and orbit information about the GNSS SVs, to facilitate positioning technologies such as A-GNSS, AFLT, OTDOA, TDOA, AoA, AoD, multiple RTT, and ECID. This facilitation may include improving the signal acquisition and measurement accuracy of UE 104, and / or, in some cases, enabling UE 104 to calculate its estimated location based on location measurements. For example, the location server may include an almanac (e.g., a Base Station Almanac (BSA)) that indicates the location and identity of cellular transceivers and transmitters (e.g., base station 102) and / or local transceivers and transmitters in one or more specific areas (such as specific locations); and may further include information describing the signals transmitted by these transceivers and transmitters, such as signal power, signal timing, signal bandwidth, signal encoding, and / or signal frequency.In the ECID scenario, UE 104 may obtain measurements of the signal strength of signals received from a cellular transceiver (e.g., base station 102) and / or a local transceiver (e.g., Received Signal Strength Indication (RSSI) or Reference Received Power (RSRP)), and / or may obtain the signal-to-noise ratio (S / N), Reference Received Quality (RSRQ), or the round-trip time (RTT) between UE 104 and the cellular transceiver (e.g., base station 102) or local transceiver. UE 104 may transmit these measurements to a location server to determine the location of UE 104; or in some implementations, UE 104 may use these measurements together with positioning assistance data received from the location server (e.g., ground almanac data or GNSS SV data (such as GNSS almanac and / or GNSS ephemeris information)) to determine the location of UE 104.

[0086] In the case of TDOA, UE 104 can measure the Reference Signal Time Difference (RSTD) between signals (such as Position Reference Signal (PRS) or Cell-Specific Reference Signal (CRS)) received from nearby transceivers or base stations (e.g., base station 102). The RSTD measurement provides the time difference of arrival between signals (e.g., CRS or PRS) received at UE 104 from two different transceivers (the RSTD between signals received from the two base stations 102). UE 104 can return the measured RSTD to a location server, which can calculate an estimated location for UE 104 based on the known location of the transceiver being measured and the known signal timing. In some implementations of OTDOA, the signals used for RSTD measurement (e.g., PRS or CRS signals) can be accurately synchronized to common universal time (such as GPS time or Coordinated Universal Time (UTC)) by the transceiver or transmitter, for example, by using the GPS receiver or transmitter at each transceiver to accurately obtain that common universal time.

[0087] An estimate of the location of UE 104 may be referred to as location, location estimate, location lock, lock, positioning, location estimation, or location lock, and may be geodesic, providing location coordinates (e.g., latitude and longitude) of UE 104, which may or may not include an elevation component (e.g., altitude; height above or below ground level, floor level, or basement level). Alternatively, the location of UE 104 may be expressed as a municipal location (e.g., a postal address or a designation of a point or smaller area within a building, such as a specific room or floor). The location of UE 104 may also include uncertainty, and may thus be expressed as an area or volume (geodetic or municipally defined) in which UE 104 is expected to be located with a given or default probability or confidence level (e.g., 67% or 95%). The location of UE 104 may be an absolute location (e.g., defined in the form of latitude, longitude, and possibly altitude and / or uncertainty), or it may be a relative location, which includes, for example, distance and direction defined relative to an origin at a known absolute location, or relative to X, Y (and Z) coordinates. In the description contained herein, the use of the term location may include any of these variations unless otherwise indicated. Measurements used to determine (e.g., calculate) the location estimate for UE 104 (e.g., measurements obtained by UE 104 or another entity, such as base station 102) may be referred to as measurements, location measurements, location-related measurements, or positioning measurements, and the act of determining the location of UE 104 may be referred to as the positioning of UE 104 or positioning UE 104.

[0088] The communication system 100 can be configured to deliver location assistance data in a downlink broadcast message to a UE device (such as UE 104).

[0089] Support for broadcast location assistance data is provided by 3GPP for LTE access and may be similarly supported by 3GPP for 5G NR access later. Location assistance data can be included in a Location System Information Block (SIB) (sometimes called posSIB). The posSIB can be carried in a Location System Information (SI) message transmitted by base station 102 using the LTE wireless communication protocol or the NR protocol. The mapping from posSIB to SI messages can be flexibly configured according to the pos-schedulingInfoList parameter included in the SIB 1 message (also called SIB1), which is also periodically broadcast from base station 102 as defined for the Radio Resource Control (RRC) LTE protocol as defined in 3GPP TS 36.331. A separate posSIB type can be defined for each assistance data element defined in LPP (TS 36.355). As examples, posSIBs designated as pos-sib-type1-1 to pos-sib type1-7 may include shared GNSS auxiliary data; pos-sib-type2-1 to pos-sib type2-19 may include auxiliary data that varies depending on the GNSS, where a specific GNSS is indicated in the pos-schedulingInfoList in SIB1; and pos-sib-type3-1 may include OTDOA auxiliary data. Furthermore, each posSIB may be encrypted by location server 172 using the same encryption key or a different encryption key for each type of posSIB (e.g., using a 128-bit Advanced Encryption Standard (AES) algorithm with counter mode). An indication of whether a particular posSIB is encrypted can be provided in the pos-schedulingInfoList parameter. These posSIBs can be formatted, encoded, and clustered into SI messages at location server 172 and transparently provided to base station 102 as LPPa or NRPPa messages for broadcast by base station 102.

[0090] The information provided by base station 102 to location server 172 using LPPa or NRPPa may include timing and configuration information regarding the PRS transmission of base station 102, as well as the location coordinates of base station 102. Subsequently, location server 172 may provide some or all of this information to UE 104 as supplementary data via base station 102 in LPP and / or NPP messages.

[0091] The LPP and / or NPP messages sent from location server 172 to UE 104 can instruct UE 104 to perform any of a variety of operations, depending on the desired functionality. For example, LPP and / or NPP messages may contain instructions for UE 104 to obtain measurements for GNSS (or A-GNSS), wireless LAN, and / or OTDOA (or some other positioning method). In the case of OTDOA, LPP and / or NPP messages may instruct UE 104 to obtain one or more measurements (e.g., Reference Signal Time Difference (RSTD) measurements) of PRS signals transmitted within a specific cell supported by specific base station 102. UE 104 may send these measurements back to location server 172 via serving base station 102 in LPP and / or NPP messages (e.g., within 5G NAS messages).

[0092] Location server 172 can encode location assistance data and optionally cryptographicate the encoded location assistance data, and transmit the encoded and optionally cryptographic location assistance data to base station 102 for broadcast to UE 104.

[0093] Positioning assistance data that can be broadcast by base station 102 is typically time-varying and valid only for a certain period of time. For example, GNSS ephemeris data is typically valid for about 2 hours. Other assistance data (such as DGNSS corrections or RTK observations) may change more frequently (on the order of seconds to tens of seconds).

[0094] For broadcasting auxiliary data using LTE or NR, the auxiliary data may be included in a Positioning System Information Block (posSIB). The posSIB may include specific types of auxiliary data (e.g., auxiliary data for UE-assisted OTDOA, UE-based OTDOA, differential correction for A-GNSS, acquisition auxiliary data for A-GNSS, RTK reference station information, etc.) and may have an associated posSIB type (e.g., identified by integers or integer pairs). Within a specific cell, a specific posSIB type may be broadcast periodically (e.g., at fixed intervals from 80 ms to 5.12 seconds) carrying auxiliary data of the associated type. The auxiliary data may remain the same for a period of time and may subsequently be changed (e.g., to match changes in associated source information about the auxiliary data). The posSIB type may then continue to be broadcast periodically, but now contains the changed auxiliary data. This process may continue to involve further changes to the auxiliary data.

[0095] To improve broadcast efficiency, one or more posSIBs with the same shared broadcast periodicity can be included in a Positioning System Information (SI) message broadcast with the shared broadcast periodicity. A posSIB containing more auxiliary data than can fit into a single Positioning SI message can be segmented into two or more posSIB segments and included in a coherent Positioning SI message (e.g., where each Positioning SI message includes a posSIB segment for any segmented posSIB).

[0096] System Information Block 1 (SIB1) can be used to broadcast scheduling information about positioning SI messages to UE 104. SIB1 is broadcast periodically by base station 102 and periodically received and interpreted by UE 104. The scheduling information may include an identifier indicating that each positioning SI message is periodically broadcast, and may indicate the periodicity of each positioning SI message and the identity of each posSIB included in the positioning SI message. For posSIBs carrying auxiliary data for positioning methods related to A-GNSS or RTK, the scheduling information may further indicate the specific GNSS constellation (e.g., GPS, GLONASS, Galileo, or BeiDou) to which the auxiliary data in the posSIB applies.

[0097] Using the scheduling information in SIB1, UE 104 can know that a location SI message is broadcast in a specific cell, the posSIB type included in each location SI message, and the periodicity of each location SI message.

[0098] Currently, the ancillary data used for measurement and reporting can be very large. For example, ancillary data may include broadcast information about up to 256 TRPs. Therefore, UE 104 needs to be intelligent to avoid repeatedly reading the same ancillary data. To support more efficient means for enabling UE 104 to determine when to receive and decode location ancillary data, systemInfoValueTag and / or expiration timers can be used. For example, the expirationTime field indicates the duration for which the broadcast ancillary data content is valid and can be specified as UTC time and indicate when the broadcast ancillary data content will expire. For example, the expiration timer may include a start time indicating when the ancillary data in the posSIB begins to be valid, and an duration indicating the expected duration for which the ancillary data will remain valid after the start time. systemInfoValueTag can indicate to UE 104 when the posSIB includes changed ancillary data. For example, the value tag can be encoded as an integer whose value is incremented by 1 modulo a certain maximum value in the first segment or only segment of the posSIB that includes the changed ancillary data. The `valueTag` field indicates to UE 104 when any changes have occurred in the broadcast auxiliary data content. `valueTag` is incremented by 1 by the location server each time modified auxiliary data content is provided. This field is not included if the broadcast auxiliary data changes too frequently. If neither `valueTag` nor `expirationTime` exists, UE 104 can assume that the broadcast auxiliary data content changes at every broadcast interval.

[0099] However, the current use of the systemInfoValueTag and expirationTime fields is not power-optimal for UE 104. For example, any change to TRP information (e.g., addition or deletion) will change the systemInfoValueTag value, requiring UE 104 to decode the complete posSIB. Therefore, even small changes will cause the systemInfoValueTag value to change, and UE 104 will need to receive and decode the complete posSIB. In the current framework, there is no mechanism for base station 102 to notify UE 104 of minor or differential changes to the existing posSIB.

[0100] As an example, Figure 4The current SIB scheduling 400 is explained. Block 1 402 includes the complete posSIB payload. Block 1 with the posSIB payload is scheduled for periodic transmission (e.g., every T1 milliseconds). For example, whenever UE 104 powers on, UE 104 needs to receive and decode Block 1 with the complete posSIB payload. The information in the posSIB payload is associated with an expiration timer (expirationTime) and a value tag (systemInfoValueTag). The expirationTime field indicates the validity period of the broadcast auxiliary data content. This field can be specified as UTC time and indicates when the broadcast auxiliary data content will expire. The valueTag field indicates to the target device any changes to the broadcast auxiliary data content. Each time modified auxiliary data content is provided, the valueTag can be incremented by 1 by the location server. If the broadcast auxiliary data changes too frequently, the valueTag may not be included. If neither the valueTag nor the expirationTime exists, the UE assumes that the broadcast auxiliary data content changes in every broadcast interval. If UE 104 has already decoded the posSIB payload in block 1, UE 104 will check the expiration timer and value tag associated with the posSIB payload before reading and decoding the posSIB payload in block 1 again. For example, before the timer expires, UE 104 can check the preamble of the next received block 1 to determine if the value tag has changed. If the value tag has changed, UE 104 can then decode the complete posSIB payload.

[0101] As an example, `expirationTime` and `valueTag` can be included in the information element (IE) `AssistanceDataSIBelement` used in `IESystemInformationBlockPos` as specified in 3GPP TS 36.331, as shown in Table 1 below. The definitions in Table 1 are based on fragments of Abstract Syntax Mark 1 (ASN.1). The subscript "-r15" may not be considered part of the parameter name and may only be included to indicate the 3GPP version (e.g., version 15) in which the parameter is first defined.

[0102]

[0103]

[0104] Table 1

[0105] If only a small portion of the posSIB payload in block 1 changes, the value label will indicate that the posSIB payload includes the change, and UE 104 will need to decode the complete posSIB payload, including information that has not yet changed, which is inefficient for both the network and UE 104.

[0106] Currently, there are three types of auxiliary data that can be broadcast for positioning. One type of auxiliary data broadcast in posSibType6-1 is DL PRS auxiliary data. Another type of auxiliary data broadcast in posSibType6-2 is TRP location data. The third type of auxiliary data is broadcast in posSibType6-3 and is associated with TRP real-time differential (RTD) information.

[0107] Table 2 below shows the IE in RRC, which illustrates that posSIB is mapped to the System Information Block (Sib) in version 16 (v16).

[0108]

[0109] Table 2

[0110] Broadcast auxiliary data can be broadcast at fixed intervals with scheduled periods (posSI), such as 80ms, 160ms, 320ms, 640ms, 1280ms, 2560ms, and 5120ms. An offset (offsetToSI-Used) can be used to indicate that SI messages in the PosSI-SchedulingInfoList are scheduled with an offset of 8 radio frames compared to SI messages in the SchedulingInfoList, where a radio frame is 10ms. This offset (offsetToSI-Used) is only possible if the shortest configured SI message period for SI messages in the SchedulingInfoList is 80ms.

[0111] Table 4 below shows possible Pos-SchedulingInfoLists. The definitions in Table 1 are based on fragments of Abstract Syntax Marker 1 (ASN.1). The subscript "-r16" may not be considered part of the parameter name and may only be included to indicate the 3GPP version (e.g., version 16) where the parameter is first defined. Table 4 shows a list of location SI messages (Pos-SchedulingInfoList), where each element (Pos-SchedulingInfo) provides information about its contents: broadcast periodicity (in 10ms (radio frames)) (posSI-Periodicity), offset (offsetToSI-Used), and the included list of posSIBs (i.e., auxiliary data) (Pos-SIB-MappingInfo). The list of Pos-SIB-Types includes information containing: (a) whether the auxiliary data is cryptographic (encrypted), (b) information about the applicable GNSS (gnss-id, sbas-id), and (c) an indication of a specific posSIB type (pos-sib-type). Each pos-sib-type maps to a specific auxiliary data element, as defined in the LPP (TS 36.355). For example, posSib type 1-1 includes GNSS reference time auxiliary data, posSib type 1-2 includes GNSS reference position auxiliary data, etc. Table 3 below specifies the supported posSib types mapped to auxiliary data elements. NR-related SIBs are sib 6-1, 6-2, and 6-3.

[0112]

[0113]

[0114]

[0115]

[0116] Table 3

[0117]

[0118]

[0119]

[0120] Table 4

[0121] As discussed above, in the current framework, when there are minor changes in the auxiliary data, the value label will indicate the change, and UE 104 needs to decode the entire posSIB payload. There is no mechanism for base station 102 to notify UE 104 of minor or differential changes to the existing posSIB.

[0122] Accordingly, this paper discloses the differential coding of posSIB, which may be particularly useful for posSIB (due to its heavy payload).

[0123] In one implementation, modified location assistance data is included differentially in each posSIB block and broadcast separately from posSIB blocks containing unchanged location assistance data. For example, modified location assistance data relative to a reference posSIB (such as previously broadcast location assistance data) can be encoded in a separate posSIB block from posSIB blocks containing location assistance data unchanged relative to the reference posSIB. The separately broadcast individual posSIB blocks include a reference code to identify the modified location assistance data. For example, a version number or value label can be associated with each posSIB. The reference code can indicate the current version number of the posSIB that has changed relative to the reference posSIB, allowing UE 104 to determine that UE 104 has previously received and decoded a posSIB with modified location assistance data. If UE 104 has not previously received modified location assistance data, then UE 104 only needs to receive and decode the posSIB block containing the modified location assistance data.

[0124] As an example, Figure 5 An example of a signaling stream 500 for differentially broadcasting positioning assistance data in a communication system (such as communication system 100) is shown.

[0125] In Phase 1, location server 502 (which may be, for example, E-SMLC or LMF) collects, processes, and formats various auxiliary data elements for each supported positioning method. For example, location server 502 may collect data (e.g., for GNSS, RTK, OTDOA, TDOA, AoD, multiple RTT, and / or ECID) from base station 102 and other sources (e.g., other base stations). Positioning auxiliary data may be used for DL ​​PRS auxiliary data, TRP location data, or RTD data. A separate posSIB type is defined for each auxiliary data element. Subsequently, location server 502 may encode and potentially cryptographicate the Positioning System Information Block (posSIB) content and scheduling information. Larger auxiliary data elements may be segmented. Any new auxiliary data (i.e., different from the auxiliary data provided in the reference posSIB (e.g., a previously broadcast posSIB)) may be encoded in a separate posSIB block from the posSIB block used to encode shared (i.e., unchanged relative to the reference posSIB) data. Location server 502 can further encode the separate posSIBs using reference data associated with the new data to identify the data using a version number or value tag (e.g., by incrementing the value associated with the location assistance data in the event of a change in the location assistance data relative to previous location assistance data). For example, cryptography can use the 128-bit Advanced Encryption Standard (AES) algorithm defined by the National Institute of Standards and Technology (NIST). For example, an AES counter mode can be used. Additionally, a validity period can be used.

[0126] In Phase 2, auxiliary data information is provided to base station 102 and other base stations using LPPa or NRPPa procedures (e.g., via AMF 504 108). The auxiliary data is provided in separate posSIB blocks, with reference coding in one posSIB block, new or modified positioning auxiliary data in another posSIB block, and shared (unmodified) positioning auxiliary data in yet another posSIB block.

[0127] In phase 3, base station 102 includes the received auxiliary data information in a Positioning System Information (SI) message that can be used with the Radio Resource Control (RRC) protocol. Separate posSIB blocks are periodically broadcast separately by base station 102 (and other base stations) using the Positioning SI message. Additionally, scheduling information may be periodically broadcast by base station 102 in SIB1 messages (also referred to as SIB1). UE 104 may apply a system information capture procedure to capture the separately broadcast auxiliary data information. UE 104 decodes the posSIB block only if it includes positioning auxiliary data that it has not yet obtained (e.g., as determined from reference coding).

[0128] In Phase 4, if the posSIB is encrypted, the location server 502 provides any encrypted keys used in Phase 1 to the AMF 504 and other AMFs. For example, the encrypted keys can be provided in Phase 4 using a Location Services Application Protocol (LCS-AP) message. The information provided for each key in Phase 4 may include the identifier of the applicable posSIB, the key value, the key identifier, and the applicable time and geographic region of the key.

[0129] In Phase 5, AMF 504 uses NAS mobility management procedures (such as attachment or tracking area updates) to distribute cryptographic keys to appropriately subscribed UEs (e.g., UE 104). Alternatively, supplemental service procedures may be used to distribute keys (e.g., Mobile Origin Location Request (MO-LR)). When cryptography is used, the UE (e.g., UE 104) can use these keys to decrypt auxiliary data received in the location SI message broadcast in Phase 3.

[0130] Figure 6 The text describes a posSIB scheduling method 600 with differential coding, where new or changed auxiliary data is encoded in separate posSIB blocks from auxiliary data that has not changed relative to previously transmitted auxiliary data. Using differential coding, larger posSIB payloads (such as block 1 602) are divided into separate posSIB blocks. Figure 6 As explained in the text, block 2604 may include reference coding, block 3606 may include set A auxiliary data (AD) which is shared with previously broadcast auxiliary data (e.g., reference posSIB), and block 4608 may include set B AD, which is differential data, for example, including new or changed auxiliary data relative to previously broadcast auxiliary data.

[0131] Block 1 602 includes a complete posSIB payload containing shared and modified auxiliary data. In some implementations, Block 1 602 may be used with a conventional posSIB payload (e.g., such as...). Figure 4 The block shown is identical to block 1 402, and the information in the posSIB payload can be associated with the expiration time and the systemInfoValueTag. In another implementation, block 1 602 can be a combination of blocks 2 604, 3 606, and 4 608.

[0132] Block 2 604 may include a reference code that identifies a version number or value tag of auxiliary data encoded in one or two other posSIB blocks. For example, each auxiliary data element encoded in a posSIB is associated with a version number. The version number is incremented as the auxiliary data element changes. The reference code in Block 2 604 identifies, for example, the current version number of the auxiliary data element in Blocks 3 606 and 4 608, as well as scheduling information. Therefore, the reference code indicates whether the posSIB in Block 4 608 has changed compared to the positioning auxiliary data included in a reference posSIB (e.g., a previously broadcast posSIB). Additionally, in some implementations, Block 2 604 may further include the validity period of the positioning auxiliary data in other posSIB blocks, such as an expiration time.

[0133] After decoding block 2 604, UE 104 can determine, based on reference coding, whether the location assistance data in block 3 606 or block 4 608 has been previously captured (e.g., in previously broadcast assistance data), or whether one or both contain location assistance data that UE 104 has not previously captured. For example, if all location assistance data in block 3 606 or block 4 608 has been previously captured, UE 104 does not need to receive or decode these posSIB blocks. On the other hand, UE 104 can determine, based on reference coding, that the location assistance data in block 4 608 has changed (or is new) relative to previously captured location assistance data, and UE 104 can, for example, use the scheduling information provided in block 2 604 to receive and decode only the posSIBs in block 4 608. Additionally, UE 104 may not have previously captured any location assistance data (e.g., after it is enabled), and UE 104 may capture all location assistance data, for example, from block 1 602 or from blocks 3 606 and 4 608, using the scheduling information provided in block 2 604.

[0134] Block 3 606 includes a set A AD, which is auxiliary data shared with respect to previously broadcast auxiliary data (e.g., reference posSIB).

[0135] Block 4 608 includes a set B AD, which includes new or changed auxiliary data relative to previously broadcast auxiliary data (e.g., reference posSIB). In some implementations, block 4 608 may additionally include auxiliary data that has not yet been changed but is associated with the new or changed auxiliary data.

[0136] As an example, posSIB may include 50 TRPs, where each TRP may have 100 PRS resources previously broadcast (e.g., refer to posSIB).

[0137] If, for one of the 50 TRPs, 99 of these PRS resources remain unchanged relative to the reference posSIB, then block 4 608 may include only the PRS resources that have changed for that particular TRP. However, in another implementation, in addition to the changed PRS resources, block 4 608 may also include the entire frequency layer containing the PRS resources that have changed for that particular TRP. In yet another implementation, in addition to the changed PRS resources, block 4 608 may also include all PRS resources across all frequency layers for that particular TRP. In yet another example, block 4 608 may include location information about any changed TRPs.

[0138] like Figure 6 As explained, blocks 1, 2, 3, and 4 are broadcast separately. For example, block 1 can be broadcast periodically (e.g., every T1 milliseconds). Blocks 2, 3, and 4 are each broadcast individually periodically. For example, blocks 2, 3, and 4 can be broadcast in groups at periodic intervals of T2 milliseconds. Block 3 can be separated from block 2 by T3 milliseconds, and block 4 can be separated from block 3 by T3 milliseconds. As explained, block 2 can be separated from block 1 by T4 milliseconds. By broadcasting blocks 2, 3, and 4 in groups with a sufficiently small interval T3, UE 104 can receive any desired blocks while in an active state without having to switch between inactive and active states, thereby improving efficiency. For example, T3 can be less than 8 radio frames, e.g., less than 80 milliseconds. It should be understood that although... Figure 6 The explanation describes two separate groups for blocks 2, 3, and 4 within time period T1, but more groups can exist if needed.

[0139] In operation, UE 104 can receive and decode block 2 to determine if any new or changed ancillary data exists in block 4, and will only receive and decode block 4 if new or changed ancillary data exists. UE 104 does not need to receive and decode block 3 with unchanged ancillary data, unless, for example, UE 104 has not yet received ancillary data (e.g., UE 104 is powering on for the first time). UE 104 can receive the complete set of ancillary data from block 1, or from blocks 3 and 4.

[0140] In some implementations, it may not be necessary to broadcast the full posSIB payload in block 1, since the full set of auxiliary data can be obtained from blocks 3 and 4.

[0141] For example, Figure 7 The explanation of posSIB scheduling 700 with differential coding, where the complete posSIB payload is not broadcast in a single posSIB block. Figure 7 The posSIB scheduling 700 in the middle includes Figure 6Blocks 2 604, 3 606, and 4 608 are described, but block 1 602 is not included. As explained, blocks 2, 3, and 4 can be... Figure 6 The posSIB scheduler 600 shown is broadcast in a similar manner, but block 1 is not transmitted.

[0142] In some implementations, it may not be necessary to broadcast block 3 606 with posSIB unchanged relative to previous broadcasts, since the complete set of auxiliary data can be obtained from blocks 1 and 4.

[0143] For example, Figure 8 The explanation of posSIB scheduling 800 with differential coding is provided, in which the complete posSIB payload is broadcast in a single posSIB block and the unchanged posSIB is not broadcast separately. Figure 8 The posSIB scheduling 800 in the middle includes Figure 6 Blocks 1 602, 2 604, and 4 608 are described, but block 3 606 is not included. As explained, blocks 1, 2, and 4 can be... Figure 6 The posSIB scheduler 600 shown broadcasts in a similar manner, but block 3 is not transmitted. As explained, in this implementation (and in other implementations if necessary), block 4 is separated from block 2 by T3 milliseconds.

[0144] Figure 9 This illustrates a communication system suitable for using NR networks (such as...) Figure 1 The example signaling stream 900 of the communication system 100 shown is for creating and distributing differentially coded positioning assistance data for use by a UE device (such as UE 104) in positioning operations. Although only one base station is described, it should be understood that multiple base stations can exist. As previously noted, this can also be implemented using an LTE network. Figure 9 The characteristics, without departing from the subject matter for which protection is sought. For example, in Figure 9 In the implementation, base station 102 can be a gNB or eNB, AMF 904 can be replaced by MME, LMF 902 can be replaced by E-SMLC, and the use of NRPPa can be replaced by the use of LPPa. Signaling flow 900 can be... Figure 5 The signaling flow in 500 is similar to or the same as that in 500, but includes more than Figure 5 Further details are provided to describe and illustrate additional embodiments and techniques.

[0145] In phase 1, LMF 902 can request location parameters from base station 102 that are applicable to the positioning method (such as, for example, TDOA, AoD, multiple RTT, etc.).

[0146] In phase 2, base station 102 provides the requested location parameters to LMF 902. Location information may include antenna location, cell identifier, cell timing, and PRS parameters (e.g., PRS bandwidth, frequency, subframe allocation) for the cell of base station 102. LMF 902 may additionally (e.g., from another reference source (not shown)) receive location information (e.g., location parameters) for GNSS positioning. For example, location parameters for GNSS positioning may include orbital data, almanac data, and / or timing data for one or more GNSS satellites or spacecraft (SVs).

[0147] In phase 3, based at least in part on location parameters obtained from the message, base station 102 and any other source (e.g., other base stations or reference sources (e.g., LMF 902)) can create Location Assistance Data (PAD) for use by UE devices (such as UE 104) when obtaining measurements, observations, and / or estimates related to the location of UE 104 using various positioning technologies (e.g., GNSS, TDOA, AoD, multi-RTT, etc.). LMF 902 can identify any new or changed portion of the PAD relative to a previously broadcast PAD. LMF 902 can create one or both of a value tag validity time and a version number for the PAD to notify UE 104 of the change to the PAD. For example, LMF 902 can determine the start time, duration, end time, or some combination thereof of the PAD's validity. LMF 902 can also determine the version number or value tag associated with the PAD, for example, by incrementing a value in the event that the PAD has been changed relative to a previous PAD.

[0148] The LMF 902 can determine the valid time based on the type of PAD and / or the update rate at which the location information is provided to the LMF 902. For example, if the reference source is configured to provide differential GNSS data every 30 seconds, the LMF can use 30 seconds of valid time in the differential GNSS PAD. In another example, if the location information is GNSS orbital parameters (e.g., ephemeris and / or almanac data), the LMF can determine the valid time based on the update rate of the individual GNSS (e.g., as defined in the respective GNSS specification).

[0149] The LMF 902 can also determine the effective time based on the desired quality of service. For example, for differential GNSS correction, the accuracy of position estimation may decrease with the age of the correction. The LMF 902 can determine the effective time of the differential GNSS correction PAD for the desired quality of service (e.g., the accuracy of position estimation). The LMF 902 can receive GNSS observation data (e.g., code and / or carrier phase measurements) from a reference station and can use these measurements together with the differential correction to perform reference positioning calculations. The LMF 902 can use various effective times of the correction data to determine the acceptable reduction in positioning accuracy. The LMF 902 can then select the effective time to provide the desired quality of service (e.g., the desired positioning accuracy). In this case, the effective time may exceed the interval of auxiliary data changes (e.g., the interval between receiving coherent reference data updates from the reference station).

[0150] In implementation, the PADs created in Phase 3 may include a subset of PADs to be applied by UE 104, rather than the entire PADs to be used by UE 104. For example, PADs created in Phase 3 may supplement or enhance PADs provided to the UE from other sources (e.g., provided by LMF 902 using LPP or LPP / LPPe point-to-point, or provided by LMF 902 using LPP or NPP). Furthermore, PADs created in Phase 3 may include a subset of PADs for a specific LPP positioning method to be used in conjunction with other PADs for that specific LPP positioning method. In one aspect, PADs created in Phase 3 may include some or all of the auxiliary data defined for the supported UE-based positioning method or UE-assisted positioning method.

[0151] LMF 902 can encode PADs separately in separate blocks of the posSIB for new or modified PADs relative to previously broadcast PADs and shared or unchanged PADs. LMF 902 can further encode PADs in posSIB blocks (e.g., Figure 6 , 7 Reference encoding is provided in block 2 of section 8, indicating which PAD is new or changed and its current value tag or version number, and in some implementations, the validity period. Reference encoding may further include scheduling information. A separate posSIB can be used to communicate different types of PADs, where any new or changed PAD is encoded in the same posSIB block (e.g., ...). Figure 6 , 7 In block 4 discussed in section 8, the posSIB block can be used with a posSIB block that has an unchanged PAD (e.g., Figure 6 and 7The block discussed in section 3) is separated. In some implementations, LMF 902 can be in the same posSIB block (e.g., such as...). Figure 6 and 8 The modified and unchanged PADs are encoded in block 1) discussed in the text.

[0152] In phase 4, LMF 902 can transmit the PADs encoded in separate posSIB blocks in phase 3 to base station 102. According to one embodiment, LMF 902 can further encrypt certain PADs encoded for transmission in the posSIBs according to a cryptographic key (e.g., a 128-bit cryptographic key) before transmission in phase 4 (e.g., using Advanced Encryption Standard (AES)). One or more posSIBs may be accompanied (e.g., may contain) an indication to the receiving base station 102 that the PADs in certain posSIBs are encrypted. For example, the posSIBs may be accompanied by an identifier or identity (ID) of the specific cryptographic key used to encrypt the PADs in the posSIB, indicating which cryptographic key was used.

[0153] In phase 5, base station 102 can broadcast a posSIB block including reference coding ( Figure 6 , 7 And block 2 discussed in section 8), for example, indicates the PAD content that has changed relative to a previously broadcast PAD (e.g., reference posSIB). UE 104 can receive and decode this posSIB block.

[0154] In phase 6, base station 102 may broadcast a posSIB that includes PADs shared with previously broadcast PADs (e.g., those that have not changed relative to a reference posSIB). For example, the posSIB block broadcast in phase 6 could be... Figure 6 and 7 Block 3 is discussed in section 3. In another implementation, the posSIB block broadcast in phase 6 can be the entire set of PADs, i.e., including new or changed PADs, for example, Figure 6 and 8 Block 1 is discussed in section 1. For example, if UE 104 has not yet received auxiliary data (e.g., at power-on), UE 104 may simply receive and decode the posSIB block broadcast in phase 6.

[0155] In phase 7, base station 102 broadcasts a posSIB block that includes a PAD different from the previously broadcast PAD (e.g., reference posSIB). Figure 6 , 7(and block 4 discussed in section 8). As discussed above, a posSIB block including a PAD different from a previously broadcast PAD may include only the changed information, or may additionally include auxiliary data that has not yet been changed but is related to the changed auxiliary data (e.g., the frequency layer of the changed PRS resource, or the TRP of the changed PRS resource). The changed auxiliary data may include location information about any TRP whose location information has changed. Base station 102 may broadcast the posSIB block in phase 7 separately from the posSIB block including the reference code by, for example, an offset of less than 8 radio frames. For example, if UE 104 has not yet received the changed PAD as indicated in the reference code received in phase 5, UE 104 may only receive and decode the posSIB block broadcast in phase 7.

[0156] In phase 8 (which may be optional), base station 102 may broadcast a posSIB block including the complete payload of the PAD (e.g., including modified and unchanged auxiliary data). Figure 6 and 8 (See Block 1 discussed in the text). For example, if the posSIB block broadcast in stage 6 includes the complete payload of the PAD, then stage 8 does not need to be executed. Additionally, if the posSIB block broadcast in stage 6 only includes the unchanged PAD, then stage 8 can be executed, as... Figure 6 The discussion may not require the execution of Phase 8, as discussed in Phase 7. For example, if UE 104 has not yet received auxiliary data (e.g., at power-on), UE 104 may simply receive and decode the posSIB block broadcast in Phase 6.

[0157] In phase 9, LMF 902 may transmit one or more messages to one or more other nodes in the network, the messages including cryptographic keys for encrypting PADs in the posSIB created in phase 3. For example, LMF 902 may transmit message 420 to AMF 904 containing information about the cryptographic keys used to encrypt PADs in the posSIB. Information about each cryptographic key may include a cryptographic key value (e.g., 128 bits of AES), an identifier for the cryptographic key (e.g., an integer, string, or binary value), an applicable time for the cryptographic key (e.g., a time period indicating during which LMF 902 can use the cryptographic key), an applicable geographic area (e.g., an indication of in which part of the network the PAD encrypted by the cryptographic key will be broadcast in the posSIB), or a combination thereof. In one embodiment, the applicable time may include a start time or an end time, duration, or a combination thereof. In another embodiment, the applicable geographic area may include at least one cell for the network, at least one location area for the network, at least one tracking area for the network, or at least one geographic area defined using coordinates (e.g., latitude and longitude coordinates).

[0158] In phase 10, the registration management procedure is executed. According to one embodiment, during registration management, AMF 904 may forward at least a portion of information regarding the cryptographic key used to encrypt PADs in the posSIB to UE 104. Parameters for forwarding each cryptographic key may include the cryptographic key value (e.g., 128 bits of AES), the identifier of the cryptographic key (e.g., an integer, string, or binary value), the applicable time of the cryptographic key (e.g., indicating the duration during which LMF 902 can use the cryptographic key), the applicable geographic area (e.g., indicating in which part of the network a PAD encrypted by the cryptographic key can be broadcast in the posSIB), or a combination thereof. For example, AMF 904 may forward at least a portion of the content from phase 9 to UE 104 during a specific procedure (such as an attachment procedure, a Tracking Area Update (TAU) procedure, or a Service Request Mobility Management procedure, to name a few). Here, AMF 904 may forward at least a portion of the content of Phase 9 to UE 104 in Non-Access Stratum (NAS) Attached Accept Message, NASTAU Accept Message, NAS Authentication Response Message, Downlink NAS Transport Message, Downlink General NAS Transport Message and / or NAS Service Accept Message (e.g., the cryptographic key for encrypting PAD in posSIB together with the identifier of the cryptographic key, the applicable time, the applicable geographic region, or a combination thereof).

[0159] In one embodiment, to avoid sending information about the cryptographic key used to encrypt the PAD to a UE that does not have a subscription for receiving the cryptographic PAD, the AMF 904 may use a registration management procedure to send information about the cryptographic key to UE 104 only if (e.g., if received from a network node) subscription data about UE 104 indicates that UE 104 has a subscription for receiving the cryptographic PAD. Furthermore, the AMF 904 may only send cryptographic key information to UE 104 about a specific posSIB for which UE 104 has a subscription for receiving the cryptographic PAD. Additionally, to avoid sending information about the cryptographic key used to encrypt the PAD to UE 104 that does not need the information or has already received it, the AMF 904 may only send information about the cryptographic key to UE 104 if UE 104 provides a request or indication that it needs the cryptographic key information. For example, in an embodiment of the registration management procedure, UE 104 may include an indication that it needs or requests cryptographic key information about the PAD. The indication may be included by UE 104 when UE 104 requires a PAD (e.g., to assist in UE 104's positioning) and when any previously encrypted key information provided to UE 104 by AMF 904 (or another AMF) is no longer valid. For example, UE 104 may determine that the previously encrypted key information provided to UE 104 by AMF 904 (or another MME) is no longer valid when the applicable period of the previously encrypted key information has expired, when UE 104 moves outside the applicable geographical area of ​​the previously encrypted key information, or when UE 104 receives one or more posSIBs broadcast by base station 102 (or another base station) containing an encrypted PAD and an indication to encrypted the PAD using an encrypted key that UE 104 does not have encrypted key information. AMF 904 can then send the cryptographic key information to UE 104 only when it receives an instruction from UE 104, which avoids using signaling resources to unnecessarily send the cryptographic key information.

[0160] In phase 11, LMF 902 may send a request for location information message to UE 104. Here, LMF 902 may request location-related measurements (e.g., measurements for A-GNSS, TDOA, AoD, multiple RTT, etc.). In some embodiments, the request for location information message may request UE 104 to calculate a location estimate based on these measurements (e.g., if the positioning method is UE-based), and may also include a requested accuracy and / or maximum response time for any location measurement or location estimate.

[0161] In phase 12, UE 104 can obtain the measurements requested in phase 11. Position-related measurements obtained by UE 104 can be obtained for RF signals transmitted by base station 102 (another base station) and / or satellites. For example, position-related measurements may include measurements of RSTD obtained by measuring PRS or other reference signals (e.g., CRS signals) transmitted by base station 102, measurements of RTT obtained by measuring signals transmitted from and / or to base station 102 (and other base stations), and / or measurements of pseudorange, code phase, or carrier phase obtained by measuring one or more navigation signals transmitted by each of one or more satellites. In some embodiments, UE 104 may also calculate a position estimate based on the obtained position measurements. UE 104 may use PADs broadcast by base station 102 in phases 5, 6, 7, and 8 to assist in obtaining position measurements and / or determining any position estimate.

[0162] In phase 13, UE 104 sends information indicating one or more location-related measurements and / or location estimates to LMF 902 in a location information provision message.

[0163] In phase 14, LMF 902 can use the measurement information received in phase 13 (including one or more location-related measurements or location estimates) to determine (e.g., calculate or verify) the estimated location of UE 104.

[0164] Figure 10 The illustration shows a base station 1000 implemented to support broadcast differentially coded positioning assistance data as described herein (e.g., Figure 1 A schematic block diagram of certain exemplary features of base station 1000. Base station 1000 can be an eNB or a gNB. Base station 1000 can perform... Figure 13The process flow is shown in the diagram. Base station 1000 may include, for example, one or more processors 1002, memory 1004, and external interfaces that may include transceiver 1010 (e.g., a wireless network interface) and communication interfaces 1016 (e.g., wired or wireless network interfaces to other base stations and / or entities in the core network, such as location servers), which may be operatively coupled to non-transient computer-readable medium 1020 and memory 1004 via one or more connections 1006 (e.g., buses, lines, optical fibers, links, etc.). Base station 1000 may further include additional items not shown, such as a user interface by which a user can interface with the base station, which may include, for example, a display, keypad, or other input devices (such as a virtual keypad on a display). In some example implementations, all or part of base station 1000 may take the form of a chipset, etc. Transceiver 1010 may include, for example, a transmitter 1012 implemented to transmit one or more signals over one or more types of wireless communication networks, and a receiver 1014 to receive one or more signals transmitted over such one or more types of wireless communication networks. Communication interface 1016 can be capable of connecting to other base stations or network entities in the RAN (such as...) Figure 1 The location server 172 shown has a wired or wireless interface.

[0165] In some embodiments, base station 1000 may include antenna 1011, which may be internal or external. Antenna 1011 may be used to transmit and / or receive signals processed by transceiver 1010. In some embodiments, antenna 1011 may be coupled to transceiver 1010. In some embodiments, measurements of signals received (transmitted) by base station 1000 may be performed at the connection point of antenna 1011 and transceiver 1010. For example, a measurement reference point for measuring received (transmitted) RF signals may be an input (output) terminal of receiver 1014 (transmitter 1012) and an output (input) terminal of antenna 1011. In base station 1000 having multiple antennas 1011 or antenna arrays, antenna connectors may be considered as virtual points representing the aggregated outputs (inputs) of multiple antennas. In some embodiments, base station 1000 may measure received signals (including signal strength and TOA measurements), and the raw measurements may be processed by one or more processors 1002.

[0166] The one or more processors 1002 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1002 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1008 on a non-transient computer-readable medium (such as medium 1020 and / or memory 1004). In some embodiments, the one or more processors 1002 may represent one or more circuits that may be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of base station 1000.

[0167] Medium 1020 and / or memory 1004 may store instruction or program code 1008 containing executable code or software instructions that, when executed by one or more processors 1002, cause one or more processors 1002 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As explained in base station 1000, medium 1020 and / or memory 1004 may include one or more components or modules that may be implemented by the one or more processors 1002 to perform the methodologies described herein. Although each component or module is described as software in medium 1020 executable by the one or more processors 1002, it should be understood that each component or module may be stored in memory 1004 or may be dedicated hardware in or outside of the one or more processors 1002. Several software modules and data tables may reside in medium 1020 and / or memory 1004 and be utilized by one or more processors 1002 to manage both the communications and functionalities described herein. It should be understood that the organization of the contents of the medium 1020 and / or memory 1004 shown in the base station 1000 is merely exemplary, and thus, the functionality of the modules and / or data structures may be combined, separated, and / or constructed in different ways depending on the implementation of the base station 1000.

[0168] The medium 1020 and / or memory 1004 may include a receive PAD module 1021, which, when implemented by one or more processors 1002, configures the one or more processors 1002 to receive location assistance data (PAD) from a location server via transceiver 1010. This module may include separate posSIB blocks containing reference codes, differential PADs, unchanged PADs, and complete PADs (including both differential and unchanged PADs), for example, such as... Figure 6-9 This was discussed in the article.

[0169] Media 1020 and / or memory 1004 may include a broadcast posSIB (reference code) module 1022, which, when implemented by one or more processors 1002, configures the one or more processors 1002 to broadcast posSIB blocks including reference codes, for example, such as Figure 6-9This was discussed in the article.

[0170] Media 1020 and / or memory 1004 may include a broadcast posSIB (differential PAD) module 1024, which, when implemented by one or more processors 1002, configures the one or more processors 1002 to broadcast via transceiver 1010 a posSIB block including positioning assistance data that has changed relative to a previously broadcast posSIB block, for example, such as Figure 6-9 This was discussed in the article.

[0171] Media 1020 and / or memory 1004 may include a broadcast posSIB (unchanged PAD) module 1026, which, when implemented by one or more processors 1002, configures the one or more processors 1002 to broadcast via transceiver 1010 a posSIB block including positioning assistance data unchanged relative to previously broadcast posSIB blocks, for example, such as Figure 6-9 This was discussed in the article.

[0172] Media 1020 and / or memory 1004 may include a broadcast posSIB (complete PAD) module 1028, which, when implemented by one or more processors 1002, configures the one or more processors 1002 to broadcast via transceiver 1010 a posSIB block comprising complete positioning assistance data including both differential and unchanged PAD data relative to previously broadcast posSIB blocks, for example, such as Figure 6-9 This was discussed in the article.

[0173] The methodologies described herein can be implemented through various means depending on the application. For example, these methodologies can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors 1002 can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0174] For firmware and / or software implementations, these methodologies can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software code can be stored in a non-transient computer-readable medium 1020 or memory 1004 connected to and executed by one or more processors 1002. Memory can be implemented within or outside of the one or more processors. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type or number of memories, or the type of medium on which memory is stored.

[0175] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 1008 on a non-transient computer-readable medium (such as medium 1020 and / or memory 1004). Examples include computer-readable media encoding data structures and computer-readable media encoding computer programs 1008. For example, a non-transient computer-readable medium including program code 1008 stored thereon may include program code 1008 that supports broadcast differential positioning auxiliary data in a manner consistent with the disclosed embodiments. The non-transient computer-readable medium 1020 includes a physical computer storage medium. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transient computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code 1008 in the form of instructions or data structures and that can be accessed by a computer; as used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs, wherein disks often magnetically reproduce data, while discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0176] In addition to being stored on the computer-readable medium 1020, instructions and / or data may also be provided as signals included on a transmission medium in a communication apparatus. For example, a communication apparatus may include a transceiver 1010 having signals indicating instructions and data. These instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions.

[0177] Memory 1004 can represent any data storage device. Memory 1004 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although described in this example as separate from one or more processors 1002, it should be understood that all or part of the main memory may be located within one or more processors 1002 or otherwise coexist / coupled with one or more processors 1002. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems (such as, for example, disk drives, optical disc drives, tape drives, solid-state drives, etc.).

[0178] In some implementations, secondary memory may be operatively accommodated or otherwise configured to be coupled to non-transient computer-readable medium 1020. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of a computer-readable medium 1020 which may include all or a portion of computer-readable code 1008 stored thereon, which, when executed by one or more processors 1002, may be operatively implemented to perform all or a portion of the example operations as described herein. Computer-readable medium 1020 may be part of memory 1004.

[0179] Figure 11 A schematic block diagram illustrating some exemplary features of a location server 1100 (e.g., location server 172) implemented to support broadcast differentially encoded location assistance data as described herein. The location server 1100 may be, for example, an E-SMLC or LMF. Figure 14 The process flow is shown in the diagram. Location server 1100 may include, for example, one or more processors 1102, memory 1104, and a communication interface 1116 (e.g., a wired or wireless network interface to other network entities, such as core network entities and base stations), which may be operatively coupled to non-transient computer-readable medium 1120 and memory 1104 via one or more connections 1106 (e.g., bus, line, fiber optic, link, etc.). Base station 1100 may further include additional items not shown, such as a user interface by which a user can interface with the location server, which may include, for example, a display, keypad, or other input device (such as a virtual keypad on a display). In some example implementations, all or part of location server 1100 may take the form of a chipset, etc. Communication interface 1116 may be a wired or wireless interface capable of connecting to base stations or network entities (such as AMF or MME) in the RAN.

[0180] The one or more processors 1102 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1102 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1108 on a non-transient computer-readable medium, such as medium 1120 and / or memory 1104. In some embodiments, the one or more processors 1102 may represent one or more circuits that may be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of location server 1100.

[0181] Medium 1120 and / or memory 1104 may store instruction or program code 1108 containing executable code or software instructions that, when executed by one or more processors 1102, cause one or more processors 1102 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As explained in location server 1100, medium 1120 and / or memory 1104 may include one or more components or modules that may be implemented by the one or more processors 1102 to perform the methodologies described herein. Although each component or module is described as software in medium 1120 executable by the one or more processors 1102, it should be understood that each component or module may be stored in memory 1104 or may be dedicated hardware in or outside of the one or more processors 1102. Several software modules and data tables may reside in medium 1120 and / or memory 1104 and be utilized by one or more processors 1102 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of media 1120 and / or memory 1104 as shown in location server 1100 is merely exemplary, and thus, the functionality of the modules and / or data structures may be combined, separated, and / or constructed in different ways depending on the implementation of location server 1100.

[0182] The medium 1120 and / or memory 1104 may include a PAD determination module 1121, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to determine positioning assistance data (PADs) to be broadcast, the PADs including differential PADs and unchanged PADs, such as... Figure 6-9 This was discussed in the article.

[0183] The medium 1120 and / or memory 1104 may include a posSIB (reference code) module 1122, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to generate posSIB blocks including reference codes indicating that PADs have been modified and scheduling information, for example, such as Figure 6-9 This was discussed in the article.

[0184] The medium 1120 and / or memory 1104 may include a posSIB (differential PAD) module 1124, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to generate posSIB blocks that include positioning assistance data that has changed relative to previously broadcast posSIB blocks, for example, such as Figure 6-9 This was discussed in the article.

[0185] Media 1120 and / or memory 1104 may include a posSIB (unchanged PAD) module 1126, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to generate posSIB blocks that include positioning assistance data unchanged relative to previously broadcast posSIB blocks, for example, such as Figure 6-9 This was discussed in the article.

[0186] Media 1120 and / or memory 1104 may include a posSIB (Complete PAD) module 1128, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to produce a posSIB block that includes, for example, complete positioning assistance data containing, both differential and unchanged PAD data relative to a previously broadcast posSIB block, such as... Figure 6-9 This was discussed in the article.

[0187] Medium 1120 and / or memory 1104 may include a transmit PAD module 1130, which, when implemented by one or more processors 1102, configures the one or more processors 1102 to transmit blocks of the posSIB to the base station via communication interface 1116 for broadcast by the base station, for example, such as Figure 6-9 This was discussed in the article.

[0188] The methodologies described herein can be implemented through various means depending on the application. For example, these methodologies can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors 1102 can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0189] For firmware and / or software implementations, these methodologies can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software code can be stored in a non-transient computer-readable medium 1120 or memory 1104 connected to and executed by one or more processors 1102. Memory can be implemented within or outside of the one or more processors. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type or number of memories, or the type of medium on which memory is stored.

[0190] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 1108 on a non-transient computer-readable medium (such as medium 1120 and / or memory 1104). Examples include computer-readable media encoding data structures and computer-readable media encoding computer programs 1108. For example, a non-transient computer-readable medium including program code 1108 stored thereon may include program code 1108 supporting broadcast differential positioning auxiliary data in a manner consistent with the disclosed embodiments. The non-transient computer-readable medium 1120 includes a physical computer storage medium. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transient computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code 1108 in the form of instructions or data structures and that can be accessed by a computer; as used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs, wherein disks often magnetically reproduce data, while discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0191] In addition to being stored on the computer-readable medium 1120, instructions and / or data may also be provided as signals included on a transmission medium in the communication apparatus. For example, the communication apparatus may include a communication interface 1116 having signals indicating instructions and data. These instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions.

[0192] Memory 1104 can represent any data storage device. Memory 1104 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although described in this example as separate from one or more processors 1102, it should be understood that all or part of the main memory may be located within one or more processors 1102 or otherwise coexist / coupled with one or more processors 1102. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems (such as, for example, disk drives, optical disc drives, tape drives, solid-state drives, etc.).

[0193] In some implementations, secondary memory may be operatively accommodated or otherwise configured to be coupled to non-transient computer-readable medium 1120. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of a computer-readable medium 1120 which may include all or a portion of computer-readable code 1108 stored thereon, which, when executed by one or more processors 1102, may be operatively implemented to perform all or a portion of the example operations as described herein. Computer-readable medium 1120 may be part of memory 1104.

[0194] Figure 12 The illustration shows a UE 1200 capable of supporting broadcast differentially coded location assistance data as discussed herein (e.g., it could be...). Figure 1 A schematic block diagram of some exemplary features of UE 104 shown. UE 1200 is executable. Figure 15 The process flow is shown in the diagram. UE 1200 may include, for example, one or more processors 1202, memory 1204, and external interfaces (such as transceiver 1210, e.g., a wireless network interface) operably coupled to non-transient computer-readable medium 1220 and memory 1204 via one or more connections 1206 (e.g., bus, line, fiber optic, link, etc.). UE 1200 may further include additional items not shown, such as a user interface by which a user can interface with the UE, which may include, for example, a display, keypad, or other input device (such as a virtual keypad on a display), or a satellite positioning system receiver. In some example implementations, all or part of UE 1200 may take the form of a chipset, etc. Transceiver 1210 may include, for example, a transmitter 1212 implemented to transmit one or more signals over one or more types of wireless communication networks, and a receiver 1214 to receive one or more signals transmitted over such one or more types of wireless communication networks.

[0195] In some embodiments, UE 1200 may include an antenna 1211, which may be internal or external. The UE antenna 1211 may be used to transmit and / or receive signals processed by transceiver 1210. In some embodiments, the UE antenna 1211 may be coupled to transceiver 1210. In some embodiments, measurements of signals received (transmitted) by UE 1200 may be performed at the connection point between the UE antenna 1211 and transceiver 1210. For example, a measurement reference point for measuring the received (transmitted) RF signal may be an input (output) terminal of receiver 1214 (transmitter 1212) and an output (input) terminal of UE antenna 1211. In a UE 1200 having multiple UE antennas 1211 or an antenna array, the antenna connector may be considered as a virtual point representing the aggregated output (input) of multiple UE antennas. In some embodiments, UE 1200 may measure received signals (including signal strength and TOA measurements), and the raw measurements may be processed by one or more processors 1202.

[0196] The one or more processors 1202 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 1202 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 1208 on a non-transient computer-readable medium (such as medium 1220 and / or memory 1204). In some embodiments, the one or more processors 1202 may represent one or more circuits that may be configured to perform at least a portion of a data signal calculation procedure or process related to the operation of UE 1200.

[0197] Medium 1220 and / or memory 1204 may store instruction or program code 1208 containing executable code or software instructions that, when executed by one or more processors 1202, cause one or more processors 1202 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As explained in UE 1200, medium 1220 and / or memory 1204 may include one or more components or modules that may be implemented by the one or more processors 1202 to perform the methodologies described herein. Although each component or module is explained as software in medium 1220 executable by the one or more processors 1202, it should be understood that each component or module may be stored in memory 1204 or may be dedicated hardware in or outside of the one or more processors 1202. Several software modules and data tables may reside in medium 1220 and / or memory 1204 and be utilized by one or more processors 1202 to manage both the communications and functionality described herein. It should be understood that the organization of the contents of the medium 1220 and / or memory 1204 as shown in UE 1200 is merely exemplary, and thus, the functionality of the modules and / or data structures may be combined, separated, and / or constructed in different ways depending on the implementation of UE 1200.

[0198] Media 1220 and / or memory 1204 may include a posSIB (reference code) receiving module 1222, which, when implemented by one or more processors 1202, configures the one or more processors 1202 to receive a posSIB block including a reference code, for example, such as Figure 6-9 This was discussed in the article.

[0199] The medium 1220 and / or memory 1204 may include a receive posSIB (differential PAD) module 1224, which, when implemented by one or more processors 1202, configures the one or more processors 1202 to receive via transceiver 1210 a posSIB block including positioning assistance data that has changed relative to a previously broadcast posSIB block, such as... Figure 6-9 This was discussed in the article.

[0200] Media 1220 and / or memory 1204 may include a receive posSIB (unchanged PAD) module 1226, which, when implemented by one or more processors 1202, configures the one or more processors 1202 to receive via transceiver 1210 a posSIB block including positioning assistance data unchanged relative to a previously broadcast posSIB block, for example, such as Figure 6-9 This was discussed in the article.

[0201] Medium 1220 and / or memory 1204 may include a receive posSIB (complete PAD) module 1228, which, when implemented by one or more processors 1202, configures the one or more processors 1202 to receive via transceiver 1210 a complete positioning assistance data including, for example, differential and unchanged PAD data relative to a previously broadcast posSIB block, such as... Figure 6-9 This was discussed in the article.

[0202] The methodologies described herein can be implemented through various means depending on the application. For example, these methodologies can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors 1202 can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0203] For firmware and / or software implementations, these methodologies can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software code can be stored in a non-transient computer-readable medium 1220 or memory 1204 connected to and executed by one or more processors 1202. Memory can be implemented within or outside of the one or more processors. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type or number of memories, or the type of medium on which memory is stored.

[0204] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 1208 on a non-transient computer-readable medium (such as medium 1220 and / or memory 1204). Examples include computer-readable media encoding data structures and computer-readable media encoding computer program 1208. For example, a non-transient computer-readable medium including program code 1208 stored thereon may include program code 1208 supporting broadcast differential positioning auxiliary data in a manner consistent with the disclosed embodiments. Non-transient computer-readable medium 1220 includes physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transient computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code 1208 in the form of instructions or data structures and that can be accessed by a computer; as used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs, wherein disks often magnetically reproduce data, while discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0205] In addition to being stored on the computer-readable medium 1220, instructions and / or data may also be provided as signals included on a transmission medium in a communication apparatus. For example, a communication apparatus may include a transceiver 1210 having signals indicating instructions and data. These instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions.

[0206] Memory 1204 can represent any data storage device. Memory 1204 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although described in this example as separate from one or more processors 1202, it should be understood that all or part of the main memory may be located within one or more processors 1202 or otherwise coexist / coupled with one or more processors 1202. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems (such as, for example, disk drives, optical disc drives, tape drives, solid-state drives, etc.).

[0207] In some implementations, secondary memory may be operatively accommodated or otherwise configured to be coupled to non-transient computer-readable medium 1220. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of a computer-readable medium 1220 that may include all or a portion of computer-readable code 1208 stored thereon, which, when executed by one or more processors 1202, may be operatively implemented to perform all or a portion of the example operations as described herein. Computer-readable medium 1220 may be part of memory 1204.

[0208] Figure 13 A flowchart of an exemplary method 1300 for supporting the broadcasting of location assistance data in a wireless network, performed by a base station (such as base station 102) in a wireless network, is shown in a manner consistent with the disclosed implementation.

[0209] In block 1302, a first block of a Base Station Broadcast Positioning System Information Block (posSIB) includes a reference code for one or more blocks of the posSIB containing positioning assistance data. This reference code indicates a second block of the posSIB containing positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 , 7 8 and Figure 9 This is discussed in Phase 5. In some implementations, the reference encoding further indicates scheduling information regarding the second block of posSIB, for example, as... Figure 6 , 7 8 and Figure 9 The apparatus for broadcasting the first block of the Positioning System Information Block (posSIB), as discussed in Phase 5, may include, for example, a wireless transceiver 1010 and dedicated hardware or implementations. Figure 10 One or more processors 1002 in the memory 1004 and / or medium 1020 of the base station 1000 shown in the illustration contain executable code or software instructions (such as broadcast posSIB (reference code) 1022), the first block including reference code for one or more blocks of posSIB containing positioning assistance data, the reference code indicating a second block of posSIB containing positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB.

[0210] In box 1304, the base station broadcasts a second block of the posSIB containing the modified positioning assistance data, for example, such as... Figure 6 , 7 8 and Figure 9The device used to broadcast the second block of the modified positioning assistance data, as discussed in phase 7, can be, for example, a wireless transceiver 1010 and has dedicated hardware or implementations. Figure 10 One or more processors 1002 containing executable code or software instructions (such as broadcast posSIB (differential PAD) 1024) in memory 1004 and / or medium 1020 in the base station 1000 shown.

[0211] In some implementations, the base station may broadcast a third block of the posSIB, which contains positioning assistance data that has not changed compared to the positioning assistance data included in the reference posSIB, for example, such as Figure 6 , 7 8 and Figure 9 The third block of positioning assistance data, which is included in the reference posSIB and has not changed compared to the positioning assistance data included in the reference posSIB, can be, for example, a wireless transceiver 1010 and has dedicated hardware or implementation. Figure 10 One or more processors 1002 containing executable code or software instructions (such as broadcast posSIB (unaltered PAD) 1028) in memory 1004 and / or medium 1020 in the base station 1000 shown.

[0212] In one implementation, the third block of posSIB can be broadcast separately from the first and second blocks of posSIB, for example, as Figure 6 and 7 as well as Figure 9 This is discussed in stage 6. For example, a base station can broadcast the fourth block of the posSIB, which contains both unchanged positioning assistance data and changed positioning assistance data, such as... Figure 6 as well as Figure 9 The fourth block of location assistance data, which includes both unchanged and changed location assistance data, is discussed in stages 5, 6, 7, and 8. This device for broadcasting posSIB can be, for example, a wireless transceiver 1010 with dedicated hardware or implementations. Figure 10 One or more processors 1002 containing executable code or software instructions in memory 1004 and / or media 1020 in the base station 1000 shown. In one implementation, a first block, a second block, a third block, and a fourth block of posSIB are periodically broadcast, wherein the fourth block of posSIB is broadcast less frequently than the first, second, and third blocks, for example, as... Figure 6 As discussed in the article.

[0213] In one implementation, the third block of the posSIB may further include positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 and 8 as well as Figure 9 This is discussed in stage 6. For example, the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block is broadcast less frequently than the first and second blocks, for example, as... Figure 6 As discussed in the article.

[0214] In one implementation, the second block of posSIB can be broadcast separately from the first block of posSIB, for example, as Figure 6 , 7 8 and Figure 9 This is discussed in stages 5 and 7. For example, the first block and the second block of posSIB can be broadcast separately with an offset of less than 8 radio frames, for example, as... Figure 6 As discussed in the article.

[0215] In one implementation, positioning assistance data is used in one of the following: downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data, for example, Figure 6 As discussed in the article.

[0216] In one implementation, the second block of the posSIB contains complete PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0217] In one implementation, the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Points (TRPs) whose corresponding PRS configuration has changed compared to the reference posSIB, for example, Figure 6 as well as Figure 9 The discussion is in stage 7.

[0218] In one implementation, the second block of the posSIB contains complete PRS configuration information for any frequency layer whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0219] In one implementation, the second block of the posSIB contains location information for any TRPs that differ in location information from the same Transmitter-Receiver Point (TRP) included in the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0220] In one implementation, the reference encoding in the first block of posSIB further includes the validity time for each of one or more blocks of posSIB, for example, as Figure 6 as well as Figure 9 This is discussed in stage 3.

[0221] Figure 14 A flowchart of an exemplary method 1400 for supporting the broadcasting of location-aiding data in a wireless network, performed by a location server (such as location server 172) in a wireless network, is shown in a manner consistent with the disclosed implementation.

[0222] In box 1402, the location server can determine the location assistance data to be broadcast by the base station, which includes both changed and unchanged location assistance data, for example, such as Figure 6 , 7 8 and Figure 9 The stage 2 discussed above. The means for determining the positioning assistance data to be broadcast by the base station may include, for example, a communication interface 1116 and dedicated hardware or implementations. Figure 11 The location server 1100 shown contains one or more processors 1102 with executable code or software instructions (such as determining PAD module 1121) in memory 1104 and / or media 1120. The location assistance data includes both changed and unchanged location assistance data.

[0223] In box 1404, the location server may generate multiple blocks of a Positioning System Information Block (posSIB), the multiple blocks including: a first block of the posSIB containing reference encoding of one or more blocks of the posSIB containing positioning assistance data, the reference encoding indicating a second block of the posSIB containing modified positioning assistance data; and a second block of the posSIB containing positioning assistance data that has changed compared to positioning assistance data included in a reference posSIB, for example, such as... Figure 6 , 7 8 and Figure 9 This is discussed in stage 3. In some implementations, the reference encoding may further indicate scheduling information about the second block of posSIB, for example, as... Figure 6 , 7 8 and Figure 9This is discussed in Phase 3. In some implementations, multiple blocks of the posSIB may further include a third block of the posSIB, which contains at least positioning assistance data that has not changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 , 7 8 and Figure 9 The process discussed in stage 3. The means for generating multiple blocks of Positioning System Information Blocks (posSIBs) may include, for example, a communication interface 1116 and dedicated hardware or implementations. Figure 11 One or more processors 1102 containing executable code or software instructions (such as posSIB modules 1122, 124, 1126) in memory 1104 and / or media 1120 in the location server 1100 shown.

[0224] In box 1406, the location server can send the multiple blocks of each posSIB to the base station, for example, such as Figure 6 , 7 8 and Figure 9 The apparatus discussed in phase 4, for transmitting multiple blocks of posSIB to the base station, may include, for example, a communication interface 1116 and dedicated hardware or implementations. Figure 11 One or more processors 1102 in the memory 1104 and / or medium 1120 of the location server 1100 shown, containing executable code or software instructions (such as the transmit PAD module 1130), wherein the base station broadcasts the second block of the posSIB separately from the first block of the posSIB.

[0225] In one implementation, the base station broadcasts the third block of the posSIB separately from the first and second blocks of the posSIB, for example, as... Figure 6 and 7 as well as Figure 9 This is discussed in stage 6. In one example, the multiple blocks of posSIB further include a fourth block of posSIB, which contains both unchanged positioning assistance data and changed positioning assistance data, for example, such as... Figure 6 as well as Figure 9 The phases 5, 6, 7, and 8 are discussed. In one implementation, the first block, the second block, the third block, and the fourth block of the posSIB are broadcast periodically, with the fourth block being broadcast less frequently than the first, second, and third blocks, for example, as... Figure 6 As discussed in the article.

[0226] In one implementation, the third block of the posSIB further includes positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 and 8 as well as Figure 9 This is discussed in Phase 6. For example, the base station periodically broadcasts the first block, the second block, and the third block of the posSIB, wherein the third block is broadcast less frequently than the first and second blocks, for example, as... Figure 6 As discussed in the article.

[0227] In one implementation, the base station can broadcast the second block of the posSIB separately from the first block of the posSIB, for example, as Figure 6 , 7 8 and Figure 9 This is discussed in stages 5 and 7. For example, the base station broadcasts the first block and the second block of the posSIB separately with an offset of less than 8 radio frames, for example, as... Figure 6 As discussed in the article.

[0228] In one implementation, positioning assistance data is used in one of the following: downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data, for example, Figure 6 As discussed in the article.

[0229] In one implementation, the second block of the posSIB contains complete PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0230] In one implementation, the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Points (TRPs) whose corresponding PRS configuration has changed compared to the reference posSIB, for example, Figure 6 as well as Figure 9 The discussion is in stage 7.

[0231] In one implementation, the second block of the posSIB contains complete PRS configuration information for any frequency layer whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0232] In one implementation, the second block of the posSIB contains location information for any TRPs that differ in location information from the same Transmitter-Receiver Point (TRP) included in the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0233] In one implementation, the reference encoding in the first block of posSIB further includes the validity time of each of one or more blocks of posSIB, for example, as Figure 6 as well as Figure 9 This is discussed in stage 3.

[0234] Figure 15 A flowchart of an exemplary method 1500 for supporting the broadcasting of location assistance data in a wireless network, performed by a UE (such as UE 104) in a wireless network, is shown in a manner consistent with the disclosed implementation.

[0235] In block 1502, the UE receives and decodes a first block of a Positioning System Information Block (posSIB) broadcast by the base station. This first block of the posSIB includes reference encoding of one or more blocks of the posSIB containing positioning assistance data. This reference encoding indicates a second block of the posSIB containing positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 , 7 8 and Figure 9 This is discussed in Phase 5. In one implementation, the reference encoding may further indicate scheduling information regarding the second block of the posSIB. The means for receiving and decoding the first block of the Positioning System Information Block (posSIB) broadcast by the base station may include, for example, a wireless transceiver 1210 and dedicated hardware or implementations. Figure 12 One or more processors 1202 containing executable code or software instructions (such as receiving posSIB (reference code) module 1222) in memory 1204 and / or media 1220 of the UE 1200 shown.

[0236] In box 1504, the UE receives and decodes the second block of the posSIB broadcast by the base station. This second block of the posSIB contains the modified positioning assistance data, for example, such as... Figure 6 , 7 8 and Figure 9 The apparatus for receiving and decoding the second block of the posSIB broadcast by the base station, as discussed in Phase 7, may include, for example, a wireless transceiver 1210 and dedicated hardware or implementations. Figure 12The UE 1200 shown includes memory 1204 and / or media 1220 containing executable code or software instructions (such as receiving posSIB (differential PAD) module 1224) from one or more processors 1202, the second block of which contains altered positioning assistance data.

[0237] In some implementations, the UE may receive a third block of the posSIB, which contains at least positioning assistance data that has not changed compared to the positioning assistance data included in the reference posSIB, for example, such as Figure 6 , 7 8 and Figure 9 The devices for receiving the third block of posSIB, as discussed in stages 6 and 8, may include, for example, a wireless transceiver 1210 and dedicated hardware or implementations. Figure 12 The third block contains at least one processor 1202 of the memory 1204 and / or the executable code or software instructions (such as the receiving posSIB (unchanged PAD) module 1226) in the UE 1200 shown, and the memory 1204 and / or the medium 1220 contain at least the positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0238] In one implementation, the third block of posSIB, containing at least the unchanged positioning assistance data, is not decoded, for example, as... Figure 6 , 7 8 and Figure 9 As discussed in stages 6 and 8, the third block of posSIB can be broadcast separately from the first and second blocks of posSIB, for example, as... Figure 6 and 7 as well as Figure 9 This is discussed in stage 6. The UE can further receive a fourth block of the posSIB broadcast by the base station, which contains both unchanged positioning assistance data and changed positioning assistance data, such as... Figure 6 as well as Figure 9 The fourth block of the posSIB, as discussed in stages 5, 6, 7, and 8, may include, for example, a wireless transceiver 1210 and dedicated hardware or implementations. Figure 12The UE 1200 shown includes one or more processors 1202 containing executable code or software instructions in memory 1204 and / or media 1220. The fourth block of the posSIB contains both unchanged positioning assistance data and changed positioning assistance data. The first, second, third, and fourth blocks of the posSIB can be broadcast periodically, with the fourth block being broadcast less frequently than the first, second, and third blocks, for example, as... Figure 6 As discussed in the article.

[0239] In one implementation, the third block of the posSIB may further include positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB, for example, such as... Figure 6 and 8 as well as Figure 9 This is discussed in stage 6. For example, the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block is broadcast less frequently than the first and second blocks, for example, as... Figure 6 As discussed in the article.

[0240] In one implementation, the second block of posSIB can be broadcast separately from the first block of posSIB, for example, as Figure 6 , 7 8 and Figure 9 This is discussed in stages 5 and 7. For example, the first block and the second block of posSIB can be broadcast separately with an offset of less than 8 radio frames, for example, as... Figure 6 As discussed in the article.

[0241] In one implementation, positioning assistance data is used in one of the following: downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data, for example, Figure 6 As discussed in the article.

[0242] In one implementation, the second block of the posSIB contains complete PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0243] In one implementation, the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Points (TRPs) whose corresponding PRS configuration has changed compared to the reference posSIB, for example, Figure 6 as well as Figure 9 The discussion is in stage 7.

[0244] In one implementation, the second block of the posSIB contains complete PRS configuration information for any frequency layer whose PRS configuration has changed compared to the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0245] In one implementation, the second block of the posSIB contains location information for any TRPs that differ in location information from the same Transmitter-Receiver Point (TRP) included in the reference posSIB, for example, such as Figure 6 as well as Figure 9 The discussion is in stage 7.

[0246] In one implementation, the reference encoding in the first block of posSIB further includes the validity time of each of one or more blocks of posSIB, for example, as Figure 6 as well as Figure 9 This is discussed in stage 3.

[0247] Throughout this specification, the terms "an example," "an example," "some examples," or "exemplary implementation" mean that a particular feature, structure, or characteristic described in conjunction with a feature and / or example may be included in at least one feature and / or example of the claimed subject matter. Therefore, the phrases "in an example," "an example," "some examples," or "in some implementations," or other similar phrases appearing throughout the specification do not necessarily all refer to the same feature, example, and / or limitation. Furthermore, these particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0248] Some portions of the detailed description included herein are presented in the form of algorithms or symbolic representations of operations on binary digital signals stored in the memory of a particular device or dedicated computing device or platform. In the context of this particular specification, the terms "particular device," etc., include general-purpose computers that, once programmed, perform specific operations according to instructions from program software. Algorithm descriptions or symbolic representations are examples of techniques used by those skilled in the art of signal processing or related fields to convey the essence of their work to others skilled in the art. An algorithm herein and generally is considered as a self-consistent sequence of operations or similar signal processing leading to a desired result. In this context, the operation or processing involves the physical manipulation of physical quantities. Typically, but not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transmitted, combined, compared, or otherwise manipulated. It has proven convenient at times to refer to such signals as bits, data, values, elements, symbols, characters, items, numbers, numerical values, etc., primarily for reasons of general use. However, it should be understood that all such terms, or similar terms, are to be associated with the appropriate physical quantity and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the discussion herein, throughout this specification, the use of terms such as “processing,” “calculating,” “determining,” and “determining” refers to the actions or processes of a particular device (such as a dedicated computer, dedicated computing device, or similar dedicated electronic computing device). In the context of this specification, therefore, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or transforming signals that are generally represented as physical electronic or magnetic quantities within the memory, registers, or other information storage, transmission, or display devices of such dedicated computer or similar dedicated electronic computing device.

[0249] In the detailed description above, numerous specific details have been set forth to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will understand that the claimed subject matter can be practiced without these specific details. In other instances, methods and apparatus known to those of ordinary skill in the art have not been described in detail to avoid obscuring the claimed subject matter.

[0250] As used herein, the terms “and,” “or,” and “and / or” may include a variety of meanings, which are also contemplated, at least in part, depending on the context in which such terms are used. Generally, “or,” when used to relate a list such as A, B, or C, is intended to mean A, B, and C (in the inclusive sense) and A, B, or C (in the exclusive sense). Additionally, the term “one or more” as used herein may be used to describe any feature, structure, or characteristic in the singular form, or to describe multiple features, structures, or characteristics, or some other combination thereof. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example.

[0251] While the features currently considered exemplary have been explained and described, those skilled in the art will understand that various other modifications can be made and equivalents can be substituted without departing from the claimed subject matter. Additionally, numerous modifications can be made to adapt a particular scenario to the teachings of the claimed subject matter without departing from the central concepts described herein.

[0252] In view of this specification, various embodiments may include different combinations of features. Examples of implementations are described in the following numbered clauses.

[0253] Clause 1. A method performed by a base station for supporting the broadcasting of positioning assistance data in a wireless network, the method comprising: broadcasting a first block of a Positioning System Information Block (posSIB) including a reference encoding of one or more blocks of the posSIB containing positioning assistance data, the reference encoding indicating a second block of the posSIB containing positioning assistance data that has been changed compared to positioning assistance data included in a reference posSIB; and broadcasting the second block of the posSIB containing the changed positioning assistance data.

[0254] Clause 2. The method of Clause 1, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0255] Clause 3. The method of any of Clauses 1 or 2 further includes: broadcasting a third block of the posSIB, the third block containing at least the positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0256] Clause 4. The method of Clause 3, wherein the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0257] Clause 5. The method of Clause 4 further includes: broadcasting a fourth block of posSIB, the fourth block containing both the location assistance data that has not been changed and the location assistance data that has been changed.

[0258] Clause 6. The method of Clause 5, wherein the first block, the second block, the third block and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first block, the second block and the third block of the posSIB.

[0259] Clause 7. The method of any of Clauses 3-6, wherein the third block of the posSIB further includes positioning assistance data that has been changed compared to the positioning assistance data included in the reference posSIB.

[0260] Clause 8. The method of Clause 7, wherein the first block, the second block and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0261] Clause 9. The method of any of Clauses 1-8, wherein the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0262] Clause 10. The method of Clause 9, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0263] Clause 11. The method of any of Clauses 1-10, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data.

[0264] Clause 12. The method of any of Clauses 1-11, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0265] Clause 13. The method of any of Clauses 1-12, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0266] Clause 14. The method of any of Clauses 1-13, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0267] Clause 15. The method of any of Clauses 1-14, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitting and Receiving Point (TRP) included in the reference posSIB.

[0268] Clause 16. The method of any of Clauses 1-15, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0269] Clause 17. A base station configured to support broadcasting location assistance data in a wireless network, comprising: an external interface configured to wirelessly communicate with a UE in the wireless network; at least one memory; and at least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: broadcast a first block of a Location System Information Block (posSIB) via the external interface, the first block including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and broadcast the second block of the posSIB containing the changed location assistance data via the external interface.

[0270] Clause 18. A base station as described in Clause 17, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0271] Clause 19. A base station as described in any of Clauses 17 or 18, wherein the at least one processor is further configured to: broadcast a third block of the posSIB via the external interface, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0272] Clause 20. A base station as described in Clause 19, wherein the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0273] Clause 21. A base station as described in Clause 20, wherein the at least one processor is further configured to: broadcast a fourth block of posSIB, the fourth block containing positioning assistance data that has not been changed and positioning assistance data that has been changed.

[0274] Clause 22. A base station as described in Clause 21, wherein the first block, the second block, the third block, and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first block, the second block, and the third block of the posSIB.

[0275] Clause 23. A base station as described in any of Clauses 19-22, wherein the third block of the posSIB further includes positioning assistance data that has been modified compared to the positioning assistance data included in the reference posSIB.

[0276] Clause 24. A base station as described in Clause 23, wherein the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0277] Clause 25. A base station of any of Clauses 17-24, wherein the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0278] Clause 26. A base station as described in Clause 25, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0279] Clause 27. A base station of any of Clauses 17-26, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

[0280] Clause 28. A base station as described in any of Clauses 17-27, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0281] Clause 29. A base station of any of Clauses 17-28, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0282] Clause 30. A base station as described in any of Clauses 17-29, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0283] Clause 31. A base station of any of Clauses 17-30, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitter Receiver Point (TRP) included in the reference posSIB.

[0284] Clause 32. A base station of any of Clauses 17-31, wherein the reference coding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0285] Clause 33. A base station configured to support broadcasting location assistance data in a wireless network, comprising: means for broadcasting a first block of a Positioning System Information Block (posSIB), the first block including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and means for broadcasting the second block of the posSIB containing the changed location assistance data.

[0286] Clause 34. A base station as described in Clause 33, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0287] Clause 35. A base station as described in any of Clauses 33 or 34 further includes: means for broadcasting a third block of the posSIB, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0288] Clause 36. A base station as described in Clause 35, wherein the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0289] Clause 37. The base station as described in Clause 36 further includes: broadcasting a fourth block of the posSIB, the fourth block containing both unaltered and altered positioning assistance data.

[0290] Clause 38. A base station as described in Clause 37, wherein the first block, the second block, the third block, and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first, second, and third blocks of the posSIB.

[0291] Clause 39. A base station as described in any of Clauses 35-38, wherein the third block of the posSIB further includes positioning assistance data that has been modified compared to the positioning assistance data included in the reference posSIB.

[0292] Clause 40. A base station as described in Clause 39, wherein the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0293] Clause 41. A base station of any of Clauses 33-40, wherein the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0294] Clause 42. A base station as described in Clause 41, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0295] Clause 43. A base station of any of Clauses 33-42, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

[0296] Clause 44. A base station as described in any of Clauses 33-43, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0297] Clause 45. A base station as described in any of Clauses 33-44, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0298] Clause 46. A base station as described in any of Clauses 33-45, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0299] Clause 47. A base station as described in any of Clauses 33-46, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitter Receiver Point (TRP) included in the reference posSIB.

[0300] Clause 48. A base station as described in any of Clauses 33-47, wherein the reference coding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0301] Clause 49. A non-transient computer-readable storage medium including program code stored thereon, the program code being operable to configure at least one processor in a base station to support broadcasting location assistance data in a wireless network, the program code including instructions for: broadcasting a first block of a Positioning System Information Block (posSIB) including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and broadcasting the second block of the posSIB containing the changed location assistance data.

[0302] Clause 50. A method performed by a location server for supporting the broadcasting of location assistance data in a wireless network, the method comprising: determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; generating a plurality of blocks of a Location System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing location assistance data modified compared to location assistance data included in a reference posSIB; and transmitting the plurality of blocks of the posSIB to a base station.

[0303] Clause 51. The method of Clause 50, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0304] Clause 52. The method of any of Clauses 50 or 51, wherein the plurality of blocks of posSIB further includes a third block of posSIB, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0305] Clause 53. The method of Clause 52, wherein the base station broadcasts the third block of the posSIB separately from the first block and the second block of the posSIB.

[0306] Clause 54. The method of Clause 53, wherein the plurality of blocks of posSIB further includes a fourth block of posSIB, the fourth block containing both the unaltered positioning assistance data and the altered positioning assistance data.

[0307] Clause 55. The method of Clause 54, wherein the base station periodically broadcasts the first block, the second block, the third block, and the fourth block of the posSIB, wherein the fourth block of the posSIB is broadcast less frequently than the first, second, and third blocks of the posSIB.

[0308] Clause 56. The method of any of Clauses 52-55, wherein the third block of the posSIB further includes positioning assistance data that has been changed compared to the positioning assistance data included in the reference posSIB.

[0309] Clause 57. The method of Clause 56, wherein the base station periodically broadcasts the first block, the second block and the third block of the posSIB, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0310] Clause 58. The method of any of Clauses 50-57, wherein the base station broadcasts the second block of the posSIB separately from the first block of the posSIB.

[0311] Clause 59. The method of Clause 58, wherein the base station broadcasts the first block and the second block of the posSIB separately with an offset of less than 8 radio frames.

[0312] Clause 60. The method of any of Clauses 50-59, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data.

[0313] Clause 61. The method of any of Clauses 50-60, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0314] Clause 62. The method of any of Clauses 50-61, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0315] Clause 63. The method of any of Clauses 50-62, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0316] Clause 64. The method of any of Clauses 50-63, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitting and Receiving Point (TRP) included in the reference posSIB.

[0317] Clause 65. The method of any of Clauses 50-64, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0318] Clause 66. A location server configured to support broadcasting location assistance data in a wireless network, comprising: an external interface configured to wirelessly communicate with a base station in the wireless network; at least one memory; at least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: determine location assistance data to be broadcast by the base station, the location assistance data including modified location assistance data and unchanged location assistance data; generate a plurality of blocks of a Location System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing modified location assistance data compared to location assistance data included in a reference posSIB; and transmitting the plurality of blocks of the posSIB to the base station via the external interface.

[0319] Clause 67. A location server as described in Clause 66, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0320] Clause 68. A location server as described in any of Clauses 66 or 67, wherein the plurality of blocks of the posSIB further includes a third block of the posSIB, the third block containing at least the location assistance data that has not been changed compared to the location assistance data included in the reference posSIB.

[0321] Clause 69. A location server as described in Clause 68, wherein the base station broadcasts the third block of the posSIB separately from the first block and the second block of the posSIB.

[0322] Clause 70. A location server as described in Clause 69, wherein the plurality of blocks of posSIB further includes a fourth block of posSIB containing both unaltered and altered location assistance data.

[0323] Clause 71. A location server as described in Clause 70, wherein a base station periodically broadcasts a first block, a second block, a third block, and a fourth block of the posSIB, wherein the fourth block of the posSIB is broadcast less frequently than the first, second, and third blocks of the posSIB.

[0324] Clause 72. A location server as described in any of Clauses 68-71, wherein the third block of the posSIB further includes location assistance data that has been modified compared to the location assistance data included in the reference posSIB.

[0325] Clause 73. A location server as described in Clause 72, wherein a base station periodically broadcasts a first block, a second block, and a third block of the posSIB, wherein the third block of the posSIB is broadcast less frequently than the first and second blocks of the posSIB.

[0326] Clause 74. A location server such as any of Clauses 66-73, wherein the base station broadcasts the second block of the posSIB separately from the first block of the posSIB.

[0327] Clause 75. A location server as described in Clause 74, wherein the base station broadcasts the first block and the second block of the posSIB separately with an offset of less than 8 radio frames.

[0328] Clause 76. A location server as described in any of Clauses 66-75, wherein the location assistance data is used for one of downlink location reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

[0329] Clause 77. A location server as described in any of Clauses 66-76, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0330] Clause 78. A location server as described in any of Clauses 66-77, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0331] Clause 79. A location server as described in any of Clauses 66-78, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0332] Clause 80. A location server as described in any of Clauses 66-79, wherein the second block of the posSIB contains location information for any TRP that differs in location information for the same Transmitting and Receiving Point (TRP) included in the reference posSIB.

[0333] Clause 81. A location server as described in any of Clauses 66-80, wherein the reference encoding in the first block of the posSIB further includes the validity period of each of one or more blocks of the posSIB.

[0334] Clause 82. A location server configured to support broadcasting location assistance data in a wireless network, comprising: means for determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; means for generating a plurality of blocks of a Location System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing location assistance data modified compared to location assistance data included in a reference posSIB; and means for transmitting the plurality of blocks of the posSIB to a base station.

[0335] Clause 83. The location server as in Clause 82, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0336] Clause 84. A location server as described in any of Clauses 82 or 83, wherein the plurality of blocks of the posSIB further includes a third block of the posSIB, the third block containing at least the location assistance data that has not been changed compared to the location assistance data included in the reference posSIB.

[0337] Clause 85. A location server as described in Clause 84, wherein the base station broadcasts the third block of the posSIB separately from the first block and the second block of the posSIB.

[0338] Clause 86. A location server as described in Clause 85, wherein the plurality of blocks of posSIB further includes a fourth block of posSIB containing both unaltered location assistance data and altered location assistance data.

[0339] Clause 87. A location server as described in Clause 86, wherein a base station periodically broadcasts a first block, a second block, a third block, and a fourth block of the posSIB, wherein the fourth block of the posSIB is broadcast less frequently than the first, second, and third blocks of the posSIB.

[0340] Clause 88. A location server as described in any of Clauses 84-87, wherein the third block of the posSIB further includes location assistance data that has been modified compared to the location assistance data included in the reference posSIB.

[0341] Clause 89. A location server as described in Clause 88, wherein a base station periodically broadcasts a first block, a second block, and a third block of the posSIB, wherein the third block of the posSIB is broadcast less frequently than the first and second blocks of the posSIB.

[0342] Clause 90. A location server as described in any of Clauses 82-89, wherein the base station broadcasts the second block of the posSIB separately from the first block of the posSIB.

[0343] Clause 91. A location server as described in Clause 90, wherein the base station broadcasts the first block and the second block of the posSIB separately with an offset of less than 8 radio frames.

[0344] Clause 92. A location server as described in any of Clauses 82-91, wherein the location assistance data is used for one of downlink location reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data.

[0345] Clause 93. A location server as described in any of Clauses 82-92, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0346] Clause 94. A location server as described in any of Clauses 82-93, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0347] Clause 95. A location server as described in any of Clauses 82-94, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0348] Clause 96. A location server as described in any of Clauses 82-95, wherein the second block of the posSIB contains location information for any TRP that differs in location information for the same Transmitting and Receiving Point (TRP) included in the reference posSIB.

[0349] Clause 97. A location server as described in any of Clauses 82-96, wherein the reference encoding in the first block of the posSIB further includes the validity period of each of one or more blocks of the posSIB.

[0350] Clause 98. A non-transient computer-readable storage medium including program code stored thereon, the program code being operable to configure at least one processor in a location server to support broadcasting location assistance data in a wireless network, the program code including instructions for: determining location assistance data to be broadcast by a base station, the location assistance data including modified location assistance data and unchanged location assistance data; generating a plurality of blocks of a Positioning System Information Block (posSIB), the plurality of blocks including: a first block of the posSIB containing a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing modified location assistance data; a second block of the posSIB containing location assistance data modified compared to location assistance data included in a reference posSIB; and transmitting the plurality of blocks of the posSIB to a base station.

[0351] Clause 99. A method performed by a user equipment (UE) for supporting the broadcasting of location assistance data in a wireless network, the method comprising: receiving and decoding a first block of a location system information block (posSIB) broadcast by a base station, the first block of the posSIB including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been modified compared to location assistance data included in a reference posSIB; and receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the modified location assistance data.

[0352] Clause 100. The method of Clause 99, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0353] Clause 101. The method of any of Clauses 99 or 100 further includes: receiving a third block of the posSIB, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0354] Clause 102. The method of Clause 101, wherein at least a third block of the posSIB containing unaltered positioning assistance data is not decoded.

[0355] Clause 103. The method of Clause 101, wherein the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0356] Clause 104. The method of Clause 103 further includes: receiving a fourth block of a posSIB broadcast by a base station, the fourth block of the posSIB containing positioning assistance data that has not been changed and positioning assistance data that has been changed.

[0357] Clause 105. The method of Clause 104, wherein the first block, the second block, the third block and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first block, the second block and the third block of the posSIB.

[0358] Clause 106. The method of any of Clauses 101-105, wherein the third block of the posSIB further includes positioning assistance data that has been changed compared to the positioning assistance data included in the reference posSIB.

[0359] Clause 107. The method of Clause 106, wherein the first block, the second block and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0360] Clause 108. The method of any of Clauses 99-107, wherein the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0361] Clause 109. The method of Clause 108, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0362] Clause 110. The method of any of Clauses 99-109, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit-receive-point (TRP) location data, or real-time differential (RTD) data.

[0363] Clause 111. The method of any of Clauses 99-110, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0364] Clause 112. The method of any of Clauses 99-111, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0365] Clause 113. The method of any of Clauses 99-112, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0366] Clause 114. The method of any of Clauses 99-113, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitting and Receiving Point (TRP) included in the reference posSIB.

[0367] Clause 115. The method of any of Clauses 99-114, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0368] Clause 116. A user equipment (UE) configured to support broadcasting location assistance data in a wireless network, comprising: a radio transceiver configured to wirelessly communicate with a base station in the wireless network; at least one memory; and at least one processor coupled to the radio transceiver and the at least one memory, wherein the at least one processor is configured to: receive and decode via the radio transceiver a first block of a Location System Information Block (posSIB) broadcast by the base station, the first block of the posSIB including a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing location assistance data that has been modified compared to location assistance data included in a reference posSIB; and receive and decode via the radio transceiver a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the modified location assistance data.

[0369] Clause 117. The UE as in Clause 116, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0370] Clause 118. The UE of any of Clauses 116 or 117, wherein the at least one processor is further configured to: receive a third block of the posSIB via the radio transceiver, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0371] Clause 119. The UE as in Clause 118, wherein at least a third block of the posSIB containing location assistance data that has not yet been altered is not decoded.

[0372] Clause 120. As in Clause 118 of the UE, wherein the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0373] Clause 121. The UE as described in Clause 120, wherein the at least one processor is further configured to: receive via the radio transceiver a fourth block of the posSIB broadcast by the base station, the fourth block containing both unchanged positioning assistance data and changed positioning assistance data.

[0374] Clause 122. The UE as in Clause 121, wherein the first block, the second block, the third block, and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first, second, and third blocks of the posSIB.

[0375] Clause 123. The UE of any of Clauses 118-122, wherein the third block of the posSIB further includes positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB.

[0376] Clause 124. The UE as in Clause 123, wherein the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0377] Clause 125. For any of Clauses 116-124, the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0378] Clause 126. The UE as in Clause 125, wherein the first block of the posSIB and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0379] Clause 127. For any UE of Clauses 116-126, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit and receive point (TRP) location data, or real-time differential (RTD) data.

[0380] Clause 128. For any UE of Clauses 116-127, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0381] Clause 129. For any UE of Clauses 116-128, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0382] Clause 130. For any UE of Clauses 116-129, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0383] Clause 131. For any UE of Clauses 116-130, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitter Receiver Point (TRP) included in the reference posSIB.

[0384] Clause 132. The UE of any of Clauses 116-131, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0385] Clause 133. A user equipment (UE) configured to support broadcasting location assistance data in a wireless network, comprising: means for receiving and decoding a first block of a location system information block (posSIB) broadcast by a base station, the first block of the posSIB including a reference code for one or more blocks of the posSIB containing location assistance data, the reference code indicating a second block of the posSIB containing location assistance data that has been modified compared to location assistance data included in a reference posSIB; and means for receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the modified location assistance data.

[0386] Clause 134. The UE as in Clause 133, wherein the reference code further indicates scheduling information regarding a second block of the posSIB.

[0387] Clause 135. The UE of any of Clauses 133 or 134 further includes: means for receiving a third block of the posSIB, the third block containing at least positioning assistance data that has not been changed compared to the positioning assistance data included in the reference posSIB.

[0388] Clause 136. The UE as in Clause 135, wherein at least a third block of the posSIB containing location assistance data that has not yet been altered is not decoded.

[0389] Clause 137. As in Clause 135, the third block of the posSIB is broadcast separately from the first block and the second block of the posSIB.

[0390] Clause 138. The UE as described in Clause 137 further includes: means for receiving a fourth block of a posSIB broadcast by a base station, the fourth block of the posSIB containing positioning assistance data that has not been changed and positioning assistance data that has been changed.

[0391] Clause 139. The UE of Clause 138, wherein the first block, the second block, the third block and the fourth block of the posSIB are broadcast periodically, wherein the fourth block of the posSIB is broadcast less frequently than the first block, the second block and the third block of the posSIB.

[0392] Clause 140. The UE of any of Clauses 135-139, wherein the third block of the posSIB further includes positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB.

[0393] Clause 141. The UE as in Clause 140, wherein the first block, the second block, and the third block of the posSIB are broadcast periodically, wherein the third block of the posSIB is broadcast less frequently than the first block and the second block of the posSIB.

[0394] Clause 142. The UE of any of Clauses 133-141, wherein the second block of the posSIB is broadcast separately from the first block of the posSIB.

[0395] Clause 143. The UE as in Clause 142, wherein the first block of the posSIB and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

[0396] Clause 144. For any UE of Clauses 133-143, wherein the positioning assistance data is used for one of downlink positioning reference signal (PRS) assistance data, transmit and receive point (TRP) location data, or real-time differential (RTD) data.

[0397] Clause 145. For any UE of Clauses 133-144, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

[0398] Clause 146. For any UE of Clauses 133-145, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

[0399] Clause 147. For any UE of Clauses 133-146, wherein the second block of the posSIB contains complete PRS configuration information for any frequency layer whose PRS configuration has changed compared to the reference posSIB.

[0400] Clause 148. For any UE of Clauses 133-147, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same Transmitting Receiver Point (TRP) included in the reference posSIB.

[0401] Clause 149. The UE of any of Clauses 133-148, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of one or more blocks of the posSIB.

[0402] Clause 150. A non-transient computer-readable storage medium including program code stored thereon, the program code being operable to configure at least one processor in a user equipment (UE) to support broadcasting location assistance data in a wireless network, the program code including instructions for: receiving and decoding a first block of a Positioning System Information Block (posSIB) broadcast by a base station, the first block of the posSIB including a reference encoding of one or more blocks of the posSIB containing location assistance data, the reference encoding indicating a second block of the posSIB containing location assistance data that has been changed compared to location assistance data included in a reference posSIB; and receiving and decoding a second block of the posSIB broadcast by the base station, the second block of the posSIB containing the changed location assistance data.

[0403] Therefore, the subject matter claimed is not intended to be limited to the specific examples disclosed, but may also include all aspects falling within the scope of the appended claims and their equivalents.

Claims

1. A method executed by a network node for supporting the broadcasting of location assistance data in a wireless network, the method comprising: Periodically broadcast reference blocks containing both unchanged and changed positioning assistance data, and / or at least reference blocks containing the unchanged positioning assistance data; A first block of a Positioning System Information Block (posSIB) is periodically broadcast. The first block includes a reference code for one or more blocks of the posSIB containing positioning assistance data. The reference code indicates a second block of the posSIB, which contains positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB. The reference code further indicates scheduling information for the second block of the posSIB. as well as The second block of the posSIB containing the changed positioning assistance data is broadcast periodically, wherein the reference block is broadcast less frequently than the second block.

2. The method of claim 1, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

3. The method as described in claim 1, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

4. The method of claim 1, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

5. The method of claim 1, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

6. The method of claim 1, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

7. The method of claim 1, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same transmit / receive point TRP included in the reference posSIB.

8. The method of claim 1, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

9. A network node configured to support broadcasting location assistance data in a wireless network, comprising: An external interface configured to communicate wirelessly with the UE in the wireless network; At least one memory; At least one processor coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: The external interface periodically broadcasts reference blocks containing both unchanged and changed positioning assistance data, and / or at least reference blocks containing the unchanged positioning assistance data. The first block of the Positioning System Information Block (posSIB) is periodically broadcast via the external interface. The first block includes a reference code for one or more blocks of the posSIB containing positioning assistance data. The reference code indicates a second block of the posSIB, which contains positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB. The reference code further indicates scheduling information for the second block of the posSIB. as well as The second block of the posSIB containing the modified positioning assistance data is periodically broadcast via the external interface, wherein the reference block is broadcast less frequently than the second block.

10. The network node of claim 9, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

11. The network node of claim 9, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

12. The network node of claim 9, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

13. The network node of claim 9, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

14. The network node of claim 9, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

15. The network node of claim 9, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same transmit / receive point TRP included in the reference posSIB.

16. The network node of claim 9, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

17. A method performed by a location server for supporting the broadcasting of location-aiding data in a wireless network, the method comprising: The location assistance data to be broadcast by the network nodes is determined, including both changed and unchanged location assistance data. Multiple blocks of the Positioning System Information Block (posSIB) are periodically generated, the multiple blocks including: A reference block containing both unchanged and changed positioning assistance data, and / or at least a reference block containing the unchanged positioning assistance data; The first block of posSIB contains a reference code for one or more blocks of posSIB containing the positioning assistance data, the reference code indicating a second block of posSIB containing the modified positioning assistance data, wherein the reference code further indicates scheduling information for the second block of posSIB. The second block of the posSIB contains positioning assistance data that has changed compared to positioning assistance data included in a reference posSIB, wherein the reference block is generated less frequently than the second block; and The plurality of blocks of the posSIB are sent to the network node.

18. The method of claim 17, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

19. The method of claim 17, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

20. The method of claim 17, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

21. The method of claim 17, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

22. The method of claim 17, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same transmit / receive point TRP included in the reference posSIB.

23. The method of claim 17, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

24. A location server configured to support broadcasting location assistance data in a wireless network, comprising: An external interface is configured to communicate wirelessly with the UE in the wireless network. At least one memory; At least one processor, coupled to the external interface and the at least one memory, wherein the at least one processor is configured to: The location assistance data to be broadcast by the network nodes is determined, including both changed and unchanged location assistance data. Multiple blocks of the Positioning System Information Block (posSIB) are periodically generated, the multiple blocks including: A reference block containing both unchanged and changed positioning assistance data, and / or at least a reference block containing the unchanged positioning assistance data; The first block of posSIB contains a reference code for one or more blocks of posSIB containing the positioning assistance data, the reference code indicating a second block of posSIB containing the modified positioning assistance data, wherein the reference code further indicates scheduling information for the second block of posSIB. The second block of the posSIB contains positioning assistance data that has changed compared to positioning assistance data included in a reference posSIB, wherein the reference block is generated less frequently than the second block; and The plurality of blocks of the posSIB are sent to the network node.

25. The location server of claim 24, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

26. The location server of claim 24, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter-Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

27. The location server of claim 24, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter / Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

28. The location server of claim 24, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

29. The location server of claim 24, wherein the second block of the posSIB contains location information for any TRP that differs in location information for the same transmit / receive point TRP included in the reference posSIB.

30. The location server of claim 24, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

31. A method executed by a user equipment (UE) for supporting the broadcasting of location assistance data in a wireless network, the method comprising: Periodically receive and decode reference blocks containing both unchanged and changed positioning assistance data, and / or at least reference blocks containing the unchanged positioning assistance data; The system periodically receives and decodes a first block of a Positioning System Information Block (posSIB) broadcast by a network node. The first block of the posSIB includes a reference code for one or more blocks of the posSIB containing positioning assistance data. The reference code indicates a second block of the posSIB containing positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB. The reference code further indicates scheduling information for the second block of the posSIB. as well as The second block of the posSIB, broadcast by the network node, is periodically received and decoded. The second block of the posSIB contains the modified positioning assistance data, wherein the reference block is broadcast less frequently than the second block.

32. The method of claim 31, wherein the first block and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

33. The method of claim 31, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

34. The method of claim 31, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

35. The method of claim 31, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

36. The method of claim 31, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

37. The method of claim 31, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same transmit / receive point TRP included in the reference posSIB.

38. The method of claim 31, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

39. A user equipment (UE) configured to support broadcasting location assistance data in a wireless network, comprising: A wireless transceiver configured to communicate wirelessly with network nodes in the wireless network; At least one memory; At least one processor, coupled to the wireless transceiver and the at least one memory, wherein the at least one processor is configured to: Periodically receive and decode reference blocks containing both unchanged and changed positioning assistance data, and / or at least reference blocks containing the unchanged positioning assistance data; The wireless transceiver periodically receives and decodes a first block of a Positioning System Information Block (posSIB) broadcast by the network node. The first block of the posSIB includes a reference code for one or more blocks of the posSIB containing positioning assistance data. The reference code indicates a second block of the posSIB, which contains positioning assistance data that has changed compared to the positioning assistance data included in the reference posSIB. The reference code further indicates scheduling information for the second block of the posSIB. as well as The wireless transceiver periodically receives and decodes a second block of the posSIB broadcast by the network node, the second block of the posSIB containing the modified positioning assistance data, wherein the reference block is broadcast less frequently than the second block.

40. The UE of claim 39, wherein the first block of the posSIB and the second block of the posSIB are broadcast separately with an offset of less than 8 radio frames.

41. The UE of claim 39, wherein the positioning assistance data is one of downlink positioning reference signal (PRS) assistance data, transmit / receive point (TRP) location data, or real-time differential (RTD) data.

42. The UE of claim 39, wherein the second block of the posSIB contains complete PRS configuration information regarding any Transmitter Receiver Point (TRP) whose PRS configuration has changed compared to the reference posSIB.

43. The UE of claim 39, wherein the second block of the posSIB contains PRS configuration information regarding any Transmitter Receiver Point (TRP) whose corresponding PRS configuration has changed compared to the reference posSIB.

44. The UE of claim 39, wherein the second block of the posSIB contains complete PRS configuration information regarding any frequency layer whose PRS configuration has changed compared to the reference posSIB.

45. The UE of claim 39, wherein the second block of the posSIB contains location information of any TRP that differs in location information of the same transmit / receive point TRP included in the reference posSIB.

46. ​​The UE of claim 39, wherein the reference encoding in the first block of the posSIB further includes the validity time of each of the one or more blocks of the posSIB.

47. A non-transient computer-readable storage medium comprising program code stored thereon, the program code configuring at least one processor to perform the method as claimed in any one of claims 1-8, 17-23, and 31-38.

Images