Enhanced assisted independent bluetooth positioning

Abstract

According to some embodiments, a method is performed by a location server network node for angle-of-arrival (AoA) Bluetooth positioning. The method comprises transmitting a request to a wireless device for transmitting a Bluetooth signal according to a Bluetooth assistance configuration and obtaining an AoA positioning report from a Bluetooth anchor node. The AoA positioning report is based on one or more Bluetooth signals transmitted from the wireless device to the Bluetooth anchor node according to the Bluetooth assistance configuration. The method further comprises estimating a position of the wireless device based on the positioning report.

Description

ENHANCED ASSISTED INDEPENDENT BLUETOOTH POSITIONING TECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to enhanced assisted independent Bluetooth positioning. BACKGROUND

[0002] Positioning in fourth generation (4G) / Long Term Evolution (LTE) / Evolved Packet Core (EPC) and fifth generation (5G) / New Radio (NR) / 5G Core (5GC) is supported by the architecture in FIGURE 1, with direct interactions between a UE 100 and a location server 130 via the LTE Positioning Protocol (LPP) 151. Moreover, there are also interactions between location server 130 and serving radio base station 110 via the LPPa protocol 152, to some extent supported by interactions between radio base station 110 and UE 100 via the Radio Resource Control (RRC) protocol 150. Radio base station 110 interacts with a mobility network entity 120 via a first interface protocol 153, and mobility network entity 120 interacts with location server 130 via a second interface protocol 154. In some applications, the location server interacts with an external application 140 via a third interface protocol 155.

[0003] A non-3GPP technology such as Bluetooth low energy (BLE), WiFi, ultra-wideband technology (UWB), etc. may also be supported by UE 100 to send a signal to an anchor node 160 or receive a signal from an anchor node 160 via a fourth interface protocol 157. Furthermore, anchor node 160 may interact with location server 130 via a fifth interface protocol 156.

[0004] In 4G / LTE / EPC and 5G / NR / 5GC, the servers / nodes / functions / interfaces / protocols are named as follows: Generic name Name in 4G / LTE / EPC Name in 5G / NR / 5GC Location server 130 Evolved Serving Mobile Location Management Location Center (E-SMLC) Function (LMF) or SLP or SLP Radio base station 110 eNodeB gNodeB Mobility network entity 120 Mobility Management Access and Mobility Entity (MME) Management Function (AMF) First interface 153 S1-MME N2P105974WO01 PCT APPLICATION 2 of 66 Second interface 154 SLs NL1

[0005] In both cases, the location server may also interact with the UE directly over user plane communication carrying LPP 151 with signaling defined by Open Mobile Alliance (OMA) Secure User Plane Location (SUPL) or some other user plane signaling. For SUPL, the location server is denoted SUPL Location Platform (SLP) and the device is denoted SUPL Enabled Terminal (SET).

[0006] FIGURE 2 illustrates the different 4G / LTE / EPC and 5G / NR / 5GC entities in the extended and common architecture.

[0007] 5G positioning methods based on 5G signals are realized based on the following signals. ^ Downlink positioning reference signals, associated to a specific radio resource, which may be transmitted using a radio beam with directivity. Each positioning reference signal is associated to an identifier. One or more such signals are transmitted from a specific transmission point associated to radio base station 110. ^ Uplink positioning reference signals, associated to a specific radio resource, which may be received using a radio beam with directivity. The uplink positioning reference signal is allocated to user equipment 100. One or more such signals are received at a specific transmission point associated to radio base station 110. ^ Uplink and downlink reference signals in combination.

[0008] Positioning methods rely on measurements, and several positioning methods rely on non-3GPP technologies based on global navigation satellite system (GNSS) signals, WiFi signals, Bluetooth signals, beacon signals, as well as sensor measurements, etc. BLE

[0009] 3GPP LPP supports BLE baseline positioning where devices report measured received signal strength from a set of BLE beacons. The terminology “beacon” indicates something only transmitting, but not receiving. Therefore, the term BLE anchor will be used both for the baseline support as well as for the extensions described herein.

[0010] Bluetooth Special Interest Group (SIG) has introduced support for direction finding in terms of Angle of Arrival(AoA) / Angle of Departure (AoD) positioning in core specification 5.1. It describes two modes:P105974WO01 PCT APPLICATION 3 of 66 ^ AoA where a single antenna transmitter is transmitting a signal that is received by a multiple antenna receiver to estimate the incoming angle(s). The angles(s) may be the horizontal / azimuth angle and / or the vertical / elevation / zenith angle. The transmitter is seen as a device and the receiver as a BLE anchor. ^ AoD where a transmitter transmits signals over multiple antennas and a single antenna receiver receives the signals and can estimate the outgoing angle from the transmitter. The transmitter is seen as a BLE anchor and the receiver as a device.

[0011] The transmitted (reference) signal is referred to as a Continuous Tone Extension (CTE) signal extending a Bluetooth message - labelled a message on an advertisement channel. The advertisement messages are sent with a configurable periodicity and contains an advertisement address, identifying the transmitter. For AoA, the transmission is continuous, while the reception can be switched and sampled by different antennas. For AoD, the transmission is switched, and the reception is sampled to match the transmissions, following a configurable pattern.

[0012] Both AoA and AoD modes can be configured for connection-less operation, where both the receiver and the transmitter are configured without direct interaction and for connection- oriented operation, where the transmitter and receiver exchange configuration information.

[0013] There currently exist certain challenges. For example, BLE direction finding can be configured via limited capacity BLE connections in a connection-oriented fashion. This limits the scalability of the features and does not enable integration with 3GPP-based positioning.

[0014] BLE is used herein to exemplify different non-3GPP or independent technologies without loss of generality, where there is a need to manage BLE transmission configurations via 3GPP protocols. Examples, signals, protocols, etc. are thereby described from a BLE context, but is transferrable to any other non-3GPP technology. SUMMARY

[0015] As described above, certain challenges currently exist with non-Third Generation Partnership Project (3GPP) positioning. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments facilitate one technology, such as 3GPP, and a server to device protocol, such as Long Term Evolution (LTE) Positioning Protocol (LPP), may be used to control the operation, transmission and measurements of another technology, such as Bluetooth Low Energy (BLE).P105974WO01 PCT APPLICATION 4 of 66

[0016] For BLE Angle of Arrival (AoA), the transmitter / device is seen as a user equipment (UE) capable of transmitting the BLE Continuous Tone Extension (CTE), and 3GPP protocols are enhanced to enable i) configuration of the UE and ii) reporting of UE configuration between a UE and a network node. The network node is referred to as a location server without loss of generality. The multiple antenna receiver is referred to as a BLE anchor.

[0017] FIGURE 3A illustrates two BLE anchors 301 and 303 estimating incoming angles 320 and 330, respectively, from BLE signal 310 transmitted buy UE 100. The angles are reported by the BLE anchors to a location server 130 for position estimation.

[0018] For BLE AoD, the receiver / device is seen as a UE capable of receiving the BLE CTE from multiple antenna transmitters (referred to as a BLE anchors) and 3GPP protocols are enhanced to provide UE from a network node with details about the transmitter configuration as assistance data.

[0019] FIGURE 3B illustrates two BLE anchors 305 and 307 transmitting BLE signals 340 and 360 over the antenna arrays enabling UE 100 to estimate outgoing angles 350 and 370, respectively, from the BLE anchors. The UE uses the estimated angles for position estimation.

[0020] According to some embodiments, a method is performed by a location server network node for angle-of-arrival (AoA) Bluetooth positioning. The method comprises transmitting a request to a wireless device for transmitting a Bluetooth signal according to a Bluetooth assistance configuration and obtaining an AoA positioning report from a Bluetooth anchor node. The AoA positioning report is based on one or more Bluetooth signals transmitted from the wireless device to the Bluetooth anchor node according to the Bluetooth assistance configuration. The method further comprises estimating a position of the wireless device based on the positioning report.

[0021] In particular embodiments, the method further comprises transmitting a request to the wireless device for Bluetooth capabilities of the wireless device and receiving the Bluetooth capabilities from the wireless device.

[0022] In particular embodiments, the method further comprises receiving an indication from the wireless device of an updated address for the wireless device. The indication may comprise an unsolicited indication from the wireless device.

[0023] In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; and CTE repetition.P105974WO01 PCT APPLICATION 5 of 66

[0024] According to some embodiments, a method is performed by a location server network node for angle-of-departure (AoD) Bluetooth positioning. The method comprises: receiving a request from a wireless device for a Bluetooth assistance configuration for the wireless device; transmitting the Bluetooth assistance configuration to the wireless device; and obtaining an AoD positioning report from the wireless device. The AoD positioning report is based on one or more Bluetooth signals transmitted from a Bluetooth anchor node to the wireless device according to the Bluetooth assistance configuration.

[0025] In particular embodiments, the method further comprises transmitting a request to the wireless device for Bluetooth capabilities of the wireless device and receiving the Bluetooth capabilities from the wireless device.

[0026] In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; PHY type; transmit power; CTE length; CTE repetition; and antenna configuration.

[0027] According to some embodiments, a location server comprises processing circuitry operable to perform any of the methods of the location servers described above.

[0028] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the location servers described above.

[0029] According to some embodiments, a method is performed by a wireless device for angle- AoA Bluetooth positioning. The method comprises receiving a request from a location server for transmitting a Bluetooth signal according to a Bluetooth assistance configuration and transmitting one or more Bluetooth signals to a Bluetooth anchor node according to the Bluetooth assistance configuration.

[0030] In particular embodiments, the method further comprises receiving a request from the location server for Bluetooth capabilities of the wireless device and transmitting the Bluetooth capabilities to the location server.

[0031] In particular embodiments, the method further comprises transmitting an indication of an updated address for the wireless device to the location server. The indication may comprise an unsolicited indication from the wireless device.P105974WO01 PCT APPLICATION 6 of 66

[0032] In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; PHY type; transmit power; CTE length; and CTE repetition.

[0033] According to some embodiments, a method performed by a wireless device for AoD Bluetooth positioning. The method comprising: transmitting a request to a location server for a Bluetooth assistance configuration for the wireless device; receiving the Bluetooth assistance configuration from a network node; receiving one or more Bluetooth signals for AoD positioning from a Bluetooth anchor node according to the Bluetooth assistance configuration; estimating a position of the wireless device based on the one of more received Bluetooth signals; and transmitting an AoD positioning report based on the estimated position to the location server.

[0034] In particular embodiments, the method further comprises receiving a request from the location server for Bluetooth capabilities of the wireless device and transmitting the Bluetooth capabilities to the location server.

[0035] In particular embodiments, receiving the Bluetooth assistance configuration comprises receiving the Bluetooth assistance configuration from the location server or broadcast from a base station.

[0036] In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; PHY type; transmit power; CTE length; CTE repetition; and antenna configuration.

[0037] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless devices described above.

[0038] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.

[0039] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments integrate Bluetooth positioning with 3GPP positioning with provisions to start / stop Bluetooth positioning. Further, particular embodiments facilitate a location server to obtain new measurements from a UE such as reference signal receive power (RSRP) and downlink angle-of-departure (DL-AoD) that is performed by UE on differentP105974WO01 PCT APPLICATION 7 of 66 Bluetooth anchor points. Some embodiments provide a way for a location server to provide assistance data for Bluetooth anchor points. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 is a functional diagram illustrating an example positioning architecture; FIGURE 2 illustrates the different 4G / LTE / EPC and 5G / NR / 5GC entities in the extended and common architecture; FIGURE 3A illustrates two BLE anchors estimating incoming angles from a BLE signal transmitted buy a UE; FIGURE 3B illustrates two BLE anchors transmitting BLE signals over the antenna arrays enabling s UE to estimate outgoing angles from the BLE anchors; FIGURE 4A illustrates a signaling chart for BLE AoA; FIGURE 4B also illustrates an embodiment for AoA with update, extending FIGURE 4A; FIGURE 5 illustrates the basic steps and some optional steps of particular AoA embodiments from a device perspective; FIGURE 6 illustrates the basic steps and some optional steps of particular AoA embodiments from a location server perspective; FIGURE 7 illustrates a signaling chart for BLE AoD; FIGURE 8 illustrates the basic steps and some optional steps of the BLE AoD embodiments from a device perspective; FIGURE 9 illustrates steps of the BLE AoD embodiments from a location server perspective; FIGURE 10 illustrates a signaling chart for an embodiment when BLE AoD assistance data is provided from a base station to a UE via system information broadcast; FIGURE 11 illustrates the steps of a BLE AoD embodiment from a UE perspective when the assistance data is provided via system information broadcast from a base station; FIGURE 12 illustrates a virtual apparatus to represent the functions in a device as well as in a location server;P105974WO01 PCT APPLICATION 8 of 66 FIGURE 13 illustrates an example communication system, according to certain embodiments; FIGURE 14 illustrates an example user equipment (UE), according to certain embodiments; FIGURE 15 illustrates an example network node, according to certain embodiments; FIGURE 16 illustrates a block diagram of a host, according to certain embodiments; FIGURE 17 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 18 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments; FIGURE 19 is a flow diagram illustrating a method performed by a location server for angle of arrival (AoA) positioning, according to particular embodiments; FIGURE 20 is a flow diagram illustrating a method performed by a location server for angle of departure (AoD) positioning, according to particular embodiments; FIGURE 21 is a flow diagram illustrating a method performed by a wireless device for angle of arrival (AoA) positioning, according to particular embodiments; and FIGURE 22 is a flow diagram illustrating a method performed by a wireless device for angle of departure (AoD) positioning, according to particular embodiments. DETAILED DESCRIPTION

[0041] As described above, certain challenges currently exist with non-Third Generation Partnership Project (3GPP) positioning. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments facilitate one technology, such as 3GPP, and a server to device protocol, such as Long Term Evolution (LTE) Positioning Protocol (LPP), may be used to control the operation, transmission and measurements of another technology, such as Bluetooth Low Energy (BLE).

[0042] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.P105974WO01 PCT APPLICATION 9 of 66

[0043] Some embodiments use BLE angle-of-arrival (AoA). FIGURE 4A illustrates a signaling chart for BLE AoA with UE 100, BLE anchor 160 and location server 130.

[0044] Some embodiments may optionally comprise a capability handshake, where location server 130 may request 400 and device 100 provide 410 device capabilities associated to BLE AoA positioning.

[0045] The exchange of configuration information between the UE and the location server is captured by steps 420 and 430, where the location server signals a message 420 to configure the UE BLE AoA transmission and request UE BLE AoA transmission configuration, and where the UE signals a message 430 to confirm and provide BLE AoA transmission configuration. In one embodiment, the exchange is handled based on the LPP Location Information Request 420 / Provide 430 procedure.

[0046] The scope of the BLE AoA transmission configuration and message content embodiments are described in more detail below.

[0047] The configured BLE signal transmission 440 from UE 100 is used by one or more BLE anchors 160 to estimate incoming angles 442 – angles that are reported 444 to the location server 130 to enable position estimation 450.

[0048] Optionally, the UE may transmit more BLE signals 460 for one or more BLE anchors 160 to estimate incoming angles 462 – angles that are reported 464 to location server 130 to enable position estimation 470.

[0049] FIGURE 4B also illustrates an embodiment for AoA with update, extending FIGURE 4A with step 455. In this embodiment, UE 100 changes its advertisement address after transmitting the BLE signal at step 440 but before transmitting the BLE signal at step 460 and therefore needs to notify location server 130 about the new advertisement address. This is in one mode of the embodiment realized by an unsolicited LPP ProvideLocationInformation message, where unsolicited means that the message has not been predated by a request message from the location server.

[0050] Optionally, location server 130 may use steps 480 and 490 to reconfigure the UE BLE signal transmission, such as aborting the UE BLE signal.

[0051] FIGURE 5 illustrates the basic steps and some optional steps of particular AoA embodiments from a device perspective.

[0052] In some embodiments, device 100 obtains 500 a request for and provides 510 capabilities associated to BLE AoA positioning.P105974WO01 PCT APPLICATION 10 of 66

[0053] Device 100 obtains from location server 130 a request 520 for location information comprising a request for BLE AoA signal transmission details and / or a configuration of a BLE AoA signal transmission. The device provides 530 BLE AoA signal information and / or configuration confirmation. The scope of the BLE AoA transmission configuration and message content embodiments are described in more detail below.

[0054] The device transmits one 540 or optionally more 550 BLE AoA signals to facilitate BLE anchor AoA estimation.

[0055] Optionally, the device may obtain 560 from a location server a BLE AoA signal reconfiguration such as aborting the UE BLE signal, to which the device optionally will confirm 570. In one embodiment, the messages are based on 3GPP LPP Location Information Request / Provide messages as part of a LPP Location Information procedure.

[0056] FIGURE 6 illustrates the basic steps and some optional steps of particular AoA embodiments from a location server perspective.

[0057] In some embodiments, location server 130 provides 600 to UE 100 a request for and obtains 610 capabilities associated to BLE AoA positioning.

[0058] Location server 130 provides to UE 100 a request 620 for location information comprising a request for BLE AoA signal transmission details and / or a configuration of a BLE AoA signal transmission. The location server obtains 630 BLE AoA signal information and / or configuration confirmation. The scope of the BLE AoA transmission configuration and message content embodiments are described in more detail below.

[0059] The location server obtains 640 a BLE AoA measurement report associated to a UE from BLE anchor 160. The location server based on the obtained measurement report from one or more BLE anchors estimates 650 the UE position. Optionally, the location server obtains 660 a BLE AoA measurement report associated to a UE at one or more later time instants, and estimates 670 the UE position.

[0060] Optionally, the location server may provide 670 to a UE a BLE AoA signal reconfiguration, such as aborting the UE BLE signal, to which the location server optionally will obtain a confirmation 680 from the UE. In one embodiment, the messages are based on 3GPP LPP Location Information Request / Provide messages as part of a LPP Location Information procedure.

[0061] Some embodiments include BLE AoD. FIGURE 7 illustrates a signaling chart for BLE AoD with UE 100, BLE anchor 160 and location server 130.P105974WO01 PCT APPLICATION 11 of 66

[0062] Some embodiments include a capability handshake, where location server 130 may request 700 and device 100 provide 710 device capabilities associated to BLE AoD positioning.

[0063] The assistance data provisioning from location server to a UE is captured by steps 720 and 730 where the UE signals a message 720 to request UE BLE AoD assistance data, and where the location server signals a message 730 to provide BLE AoD assistance data. In one embodiment, the exchange is handled based on the LPP Assistance Data Request 720 / Provide 730 procedure.

[0064] The scope of the BLE AoD assistance data and message content embodiments are described in more detail below.

[0065] Optionally, the location server may request location information 732 from the UE to provide once or at several later time instants position estimates or angle measurements.

[0066] The BLE AoD assistance data is used to receive a transmitted BLE AoD signal 740 from one or more BLE anchors 160 to estimate the outgoing angles 742 – angles that are used by the UE for position estimation 750. The estimated position or angle measurements may optionally be reported 752 to the location server.

[0067] Optionally, the UE may receive BLE AoD signals at later time instants 760 for one or more BLE anchors 160 to estimate the incoming angles 762 – angles that are used by the UE for position estimation 770. The estimated position or angle measurements may optionally be reported 772 to the location server.

[0068] FIGURE 8 illustrates the basic steps and some optional steps of the BLE AoD embodiments from a device perspective.

[0069] Some embodiments include a capability handshake, where UE 100 may obtain a request for 800 and provide 810 capabilities associated to BLE AoD positioning from / to location server 130.

[0070] The assistance data provisioning from location server to a UE is captured by steps 820 and 830 where the UE signals a message 820 to request UE BLE AoD assistance data, and obtains a message 830 from the location server with BLE AoD assistance data. In one embodiment, the exchange is handled based on the LPP Assistance Data Request 820 / Provide 830 procedure.

[0071] The scope of the BLE AoD assistance data and message content embodiments are described in more detail below.P105974WO01 PCT APPLICATION 12 of 66

[0072] Optionally, the UE may obtain 840 a request location information from the location server to request the UE to provide once or at several later time instants position estimates or angle measurements.

[0073] The BLE AoD assistance data is used to receive a transmitted BLE AoD signal from one or more BLE anchors 160 to estimate the outgoing angles 850 – angles that are used by the UE for position estimation 860. The estimated position or angle measurements may optionally be reported 865 to the location server.

[0074] Optionally, the UE may receive BLE AoD signals at later time instants for one or more BLE anchors 160 to estimate the incoming angles 870 – angles that are used by the UE for position estimation 880. The estimated position or angle measurements may optionally be reported 885 to the location server.

[0075] FIGURE 9 illustrates the basic steps and some optional steps of the BLE AoD embodiments from a location server perspective.

[0076] Some embodiments include a capability handshake, where location server 130 may request UE 100 for 900 and obtain from the UE 910 capabilities associated to BLE AoD positioning.

[0077] The assistance data provisioning from location server to a UE is captured by steps 920 and 930, where the location server obtains from the UE a message 920 to request BLE AoD assistance data, and provides a message 930 to the UE with BLE AoD assistance data. In one embodiment, the exchange is handled based on the LPP Assistance Data Request 920 / Provide 930 procedure.

[0078] The scope of the BLE AoD assistance data and message content embodiments are described in more detail below.

[0079] Optionally, the location server may provide 940 a request location information to the UE to provide once or at several later time instants position estimates or angle measurements. The location server will optionally obtain 950 once or at several time instants position estimates or angle measurements from the UE.

[0080] Some embodiments include BLE AoD via system information broadcast. FIGURE 10 illustrates a signaling chart for an embodiment when BLE AoD assistance data is provided from a base station to a UE via system information broadcast.

[0081] UE 100 obtains BLE AoD assistance data via system information broadcast 1030 from a base station 110.P105974WO01 PCT APPLICATION 13 of 66

[0082] The scope of the BLE AoD assistance data and message content embodiments are described in more detail below.

[0083] The BLE AoD assistance data is used to receive a transmitted BLE AoD signal 1040 from one or more BLE anchors 160 to estimate the outgoing angles 1042 – angles that are used by the UE for position estimation 1050.

[0084] Optionally, the UE may receive BLE AoD signals at later time instants 1060 for one or more BLE anchors 160 to estimate the outgoing angles 1062 – angles that are used by the UE for position estimation 1070.

[0085] FIGURE 11 illustrates the basic steps and some optional steps of the BLE AoD embodiments from a UE perspective when the assistance data is provided via system information broadcast from a base station.

[0086] The assistance data provisioning is obtained 1100 by a UE 100 via system information broadcast from a base station 110.

[0087] The scope of the BLE AoD assistance data and message content embodiments are described in more detail below.

[0088] The BLE AoD assistance data is used to receive a transmitted BLE AoD signal from one or more BLE anchors 160 to estimate the outgoing angles 1110 – angles that are used by the UE for position estimation 1120.

[0089] Optionally, the UE may receive BLE AoD signals at later time instants for one or more BLE anchors 160 to estimate the incoming angles 1130 – angles that are used by the UE for position estimation 1140.

[0090] FIGURE 12 illustrates a virtual apparatus to represent the functions in a device as well as in a location server. The functions are described for five different cases.

[0091] The first is the BLE AoA device perspective. Communication unit 1206 is configured to obtain a request for capabilities from a location server, to provide a response with capabilities to the location server, obtain BLE AoA configuration information and configuration requests, provide confirmation about an obtained BLE AoA configuration and provide configuration information, obtain a BLE AoA reconfiguration, for example, to abort BLE AoA signals, and provide a confirmation for the reconfiguration. Determining unit 1204 determines what capabilities to provide to the location server, determines how the BLE AoA signal should be configured, and determines when to reconfigure / abort the BLE AoA signal. Transmitting and receiving unit 1202 transmits the BLE AoA signal according to the determined configuration.P105974WO01 PCT APPLICATION 14 of 66

[0092] The second is the BLE AoA location server perspective. Communication unit 1206 is configured to provide a request for capabilities to a UE, to obtain a response with capabilities from the UE, provide a BLE AoA configuration information and configuration requests to a UE, obtain a confirmation about a provided BLE AoA configuration and configuration information from a UE, obtain BLE AoA angle estimates from BLE anchors, provide a BLE AoA reconfiguration to a UE, for example, to abort BLE AoA signals, and obtain a confirmation from the UE for the reconfiguration. Determining unit 1204 determines what BLE AoA signal configuration to provide to the UE based on obtained capabilities and estimates a UE position based on obtained estimated BLE AoA angles associated to a UE from BLE anchors.

[0093] The third is the BLE AoD device perspective. Communication unit 1206 is configured to obtain a request for capabilities from a location server, to provide a response with capabilities to the location server, provide a BLE AoA assistance data request to a location server, obtain BLE AoA assistance data from a location server, obtain a location information request from a location server, and provide location information to a location server. Determining unit 1204 determines which BLE anchor AoD signals to measure on, determines the outgoing angles per BLE anchors based on measured BLE AoD signals, and determines a position estimate based on the determined BLE AoD angle estimates. Transmitting and receiving unit 1202 receives the BLE AoD signal according to the determined configuration and measures on the BLE AoD signals per BLE anchor antenna element.

[0094] The fourth is the BLE AoD location server perspective. Communication unit 1206 is configured to provide a request for capabilities to a UE, to obtain a response with capabilities from the UE, obtain a BLE AoD assistance data request from a UE, provide BLE AoD assistance data to the UE, provide a location information request to a UE and obtain location information from the UE. Determining unit 1204 determines what BLE AoD assistance data to provide to the UE based on obtained capabilities.

[0095] The fifth is the BLE AoD via system information broadcast device perspective. Communication unit 1206 is configured to obtain BLE AoA assistance data from a base station via system information broadcast. Determining unit 1204 determines which BLE anchor AoD signals to measure on, determines the outgoing angles per BLE anchors based on measured BLE AoD signals, and determines a position estimate based on the determined BLE AoD angle estimates. Transmitting and receiving unit 1202 receives the BLE AoD signal according to theP105974WO01 PCT APPLICATION 15 of 66 determined configuration and measures on the BLE AoD signals per BLE anchor antenna element.

[0096] The BLE AoA signal configuration is an extension to an advertisement message or an extended advertisement message. The advertisement message comprises an advertisement address uniquely identifying the UE. The address is not known to the location server, and the address is something that the location server needs to request from the device. The address may either be static or subject to changes over time. Therefore, the device may need to provide an update to the location server over time.

[0097] The advertisement address may be a static medium access control (MAC) address or a Resolvable Random Private Address (RPA) that changes over time. In the current specification, the address is represented by six bytes. The type of address used is indicated by a TX address type that can take any of the following values: BLE_GAP_ADDR_TYPE_PUBLIC; / / Public address 0x00 BLE_GAP_ADDR_TYPE_RANDOM_STATIC; / / Random static address 0x01 BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE; / / Random private resolvable address 0x02 BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE; / / Random private non-resolvable address 0x03

[0098] The advertisements used with the extension are periodic and configured with an advertisement period – advInterval, which takes values from 20ms to about 10s (10.485759375s) in steps of 0.625 ms.

[0099] The Bluetooth periodic advertisements are a set of several transmissions with one message ADV_EXT_IND on one of the BLE primary channels that indicate how additional advertisements will be transmitted on a secondary channel. At the secondary channel, the device transmits the message AUX_ADV_IND, which in turn provides periodicity information of the AUX_SYNC_IND message that will be sent with a periodic interval of advInterval plus a pseudo random offset to avoid that the same device transmissions may collide over time.

[0100] The periodic advertisements when configured for BLE AoA are extended with the constant tone extension (CTE). The CTE is configured with the following: Length of the CTE in 8us steps, 1-20 steps corresponding to 8us to 160us CTE type AoAP105974WO01 PCT APPLICATION 16 of 66 CTE Count - specifies how many packets that include a CTE are to be transmitted each periodic advertising event PHY, which can be either 1 Msymbols / s (mandatory) or 2 Msymbols / s (optional)

[0101] If the device updates any of its AoA configurations, the device needs to send an update to the location server as a reconfiguration. For example, the device may change its address while engaging in CTE transmissions.

[0102] Basically, the same as for BLE AoA applies also for BLE AoD with some aspects being different because the device is now a receiver and the transmitter is now switching between different antennas.

[0103] The advertisement addressing is the same, and the periodicity.

[0104] The periodic advertisements when configured for BLE AoD are extended with the CTE. The transmitted CTE is configured with the following: Length of the CTE in 8us steps, 1-20 steps corresponding to 8us to 160us CTE type AoD with slot duration either 1us or 2us CTE Count - specifies how many packets that include a CTE are to be transmitted each periodic advertising event Antenna switching pattern – number of antennas in a set Antenna IDs Antenna configuration with respect to elements PHY, which can be either 1 Msymbols / s (mandatory) or 2 Msymbols / s (optional) Antenna array configuration to describe the antenna element configuration or beam patterns

[0105] The following are signaling examples, according to some embodiments.

[0106] The IE BT-ProvideCapabilites is used by the target device to provide its capabilities for Bluetooth positioning to the location server. -- ASN1START BT-ProvideCapabilities-r13 ::= SEQUENCE { bt-Modes-r13 BIT STRING {standalone (0),ue-assisted (1), ue-based (2)} (SIZE (1..8)), bt-MeasSupported-r13 BIT STRING {rssi-r13 (0)} (SIZE (1..8)), ..., [[ idleStateForMeasurements-r14 ENUMERATED {required } OPTIONAL, periodicalReportingSupported-r14P105974WO01 PCT APPLICATION 17 of 66 PositioningModes OPTIONAL ]], [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL ...,[[ bt-AoA-Capability-r18 BT-AoA-Capability-r18 OPTIONAL, -- Cond AoAsup bt-AoD-Capability-r18 BT-AoD-Capability-r18 OPTIONAL, -- Cond AoDsup ]] } BT-AoA-Capability-r18 ::= SEQUENCE { bt-AoA-TXadrType-r18 ENUMERATED {public, random-static, random-private- resolvable}, bt-TX-PHY-2M-r18 ENUMERATED {supported} OPTIONAL, ... } BT_AoD-Capability-r18 ::= SEQUENCE { bt-AoD-slotDuration-r18 ENUMERATED {us1, us2, both},bt-RX-PHY-2M-r18 ENUMERATED {supported} OPTIONAL, ... } -- ASN1STOP Conditional presence Explanation AoAsup The field is mandatory present if BT AoA is supported; otherwise it is not present. AoDsup The field is mandatory present if BT AoD is supported; otherwise it is not present. BT-ProvideCapabilities field descriptions bt-Modes This field specifies the Bluetooth mode(s) supported by the target device. This is represented by a bit string, with a one value at the bit position means the Bluetooth mode is supported; a zero value means not supported. bt-MeasSupported This field specifies the Bluetooth measurements supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular measurement is supported; a zero-value means not supported. A zero-value in all bit positions in the bit string means only the basic Bluetooth positioning method is supported by the target device which is reporting of the Bluetooth beacon identity. The following bits are assigned for the indicated measurements. rssi: Bluetooth beacon signal strength at the target device idleStateForMeasurements This field, if present, indicates that the target device requires idle state to perform BT measurements.P105974WO01 PCT APPLICATION 18 of 66 BT-ProvideCapabilities field descriptions periodicalReportingSupported for which the target device supports with a one value at the bit position meansa zero value means not supported. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonIEsRequestLocationInformation. scheduledLocationRequestSupported This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests. bt-AoA-TXadrType This field specifies used TX address type in the advertisements - public – the device Bluetooth MAC address - random-static – a random, static address - random-resolvable – a random address made resolvable for the location server bt-TX-PHY-2M This field, if present, indicates that the device supports 2M PHY mode with 2 Msymbols / s transmission rate (1 Msymbols / s rate is mandatory) bt-AoD-slotDuration This field specifies which slot durations that are supported by the device, us1 (1 us), us2 (2 us) or both (both 1 us and 2 us). bt-RX-PHY-2M This field, if present, indicates that the device supports 2M PHY mode with 2 Msymbols / s reception rate (1 Msymbols / s rate is mandatory)

[0107] The IE BT-RequestCapabilities is used by the location server to request Bluetooth positioning capabilities from a target device. -- ASN1START BT-RequestCapabilities-r13 ::= SEQUENCE { ... }-- ASN1STOP

[0108] used by the target device to provide measurements for one or more Bluetooth beacons to the location server. It may also be used to provide Bluetooth positioning specific error reason. -- ASN1START BT-ProvideLocationInformation-r13 ::= SEQUENCE { bt-MeasurementInformation-r13 BT-MeasurementInformation-r13 OPTIONAL, bt-Error-r13 BT-Error-r13 OPTIONAL, ..., [[ bt-AoA-Config-r18 BT-AoA-Config-r18 OPTIONAL, ]]P105974WO01 PCT APPLICATION 19 of 66 } BT-AoA-Config-r18 ::= SEQUENCE { btAddr-r13 BIT STRING (SIZE (48)), advInterval INTEGER (0..16745),cteLength-r18 INTEGER (1..20) OPTIONAL, cteCount-r18 INTEGER () OPTIONAL, tx-PHY-r18 ENUMERATED {M1, M2} OPTIONAL, ... } -- ASN1STOP BT- ProvideLocationInformation field descriptions btAddr anchor.This field specifies the Bluetooth advertisement periodicity. cteLength This field specifies the configured CTE length to be used by the device in number of 8us segments. cteCount This field specifies the number of Bluetooth packets that include a CTE that shall be transmitted each periodic advertising event tx-PHY-r18 This field specifies the Bluetooth TX PHY rate to be used, where M1 and M2 corresponds to 1 and 2 Megasymbols / s respectively

[0109] – The IE BT-MeasurementInformation is illustrated below. -- ASN1START BT-MeasurementInformation-r13 ::= SEQUENCE { measurementReferenceTime-r13 UTCTime OPTIONAL, bt-MeasurementList-r13 BT-MeasurementList-r13 OPTIONAL,... } BT-MeasurementList-r13 ::= SEQUENCE (SIZE(1..maxBT-Beacon-r13)) OF BT-MeasurementElement-r13 BT-MeasurementElement-r13 ::= SEQUENCE { btAddr-r13 BIT STRING (SIZE (48)), rssi-r13 INTEGER (-128..127) OPTIONAL, ...} -- ASN1STOPP105974WO01 PCT APPLICATION 20 of 66 BT-MeasurementInformation field descriptions measurementReferenceTime are performed and should takeThis field provides the Bluetooth measurements for up to 32 Bluetooth beacons. btAddr This field specifies the Bluetooth public address of the Bluetooth beacon. rssi This field provides the beacon received signal strength indicator (RSSI) in dBm.

[0110] The IE BT-RequestLocationInformation is used by the location server to request Bluetooth measurements from a target device. -- ASN1START BT-RequestLocationInformation-r13 ::= SEQUENCE { requestedMeasurements-r13 BIT STRING { rssi (0)} (SIZE(1..8)), ..., [[ bt-requestedAoA-Config-r18 BIT STRING { cteLength (0), cteCount (1)} (SIZE(1..8)) OPTIONAL, bt-providedAoA-Config-r18 BT-ProvidedAoA-Config-r18 OPTIONAL, ]]} BT-ProvidedAoA-Config-r18 ::= SEQUENCE { cteStatus-r18 ENUMERATED {enabled, disabled} OPTIONAL, cteLength-r18 INTEGER (1..20) OPTIONAL, cteCount-r18 INTEGER () OPTIONAL, tx-PHY-r18 ENUMERATED {M1, M2} OPTIONAL, ... } -- ASN1STOP BT-RequestLocationInformation field descriptions requestedMeasurements This field specifies the Bluetooth measurements requested. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included. rssi: Bluetooth beacon signal strength at the targetP105974WO01 PCT APPLICATION 21 of 66 BT-RequestLocationInformation field descriptions bt-requestedAoA-Config requested. This is represented by a measurement is requested; arequests can be included. advAddress: The Bluetooth advertisement address of the device cteLength: The Bluetooth CTE length in number of 8us segments cteCount: The number of Bluetooth packets that include a CTE transmitted each periodic advertising event cteStatus This field specifies the Bluetooth AoA CTE status of the device, and is used by the location server to enable or disable transmission of the BLE CTE by the device for AoA estimation at BLE anchors enabled: The Bluetooth CTE shall be enabled by the device disabled: The Bluetooth CTE shall be disabled by the device cteLength This field specifies the configured CTE length to be used by the device in number of 8us segments. cteCount This field specifies the number of Bluetooth packets that include a CTE that shall be transmitted each periodic advertising event tx-PHY-r18 This field specifies the Bluetooth TX PHY rate to be used, where M1 and M2 corresponds to 1 and 2 Megasymbols / s respectively

[0111] The RequestAssistanceData message body in a LPP message is used by the target device to request assistance data from the location server. -- ASN1START RequestAssistanceData ::= SEQUENCE { criticalExtensions CHOICE { r16P105974WO01 PCT APPLICATION 22 of 66 [[ bt-RequestAssistanceData-r18 BT-RequestAssistanceData-r18 OPTIONAL ]] } --

[0112] The ProvideAssistanceData message body in a LPP message is used by the location server to provide assistance data to the target device either in response to a request from the target device or in an unsolicited manner. -- ASN1START ProvideAssistanceData ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { -- -- -- -- -- -- -- -- -- -- ---- ASN1STOPP105974WO01 PCT APPLICATION 23 of 66 […]

[0113] The IE BT-ProvideAssistanceData is used by the location server to provide assistance data to enable UE-based BT positioning. It may also be used to provide BT positioning specific error reason. -- ASN1START BT-ProvideAssistanceData-r18 ::= SEQUENCE { bt-DataSet-r14 SEQUENCE (SIZE (1..maxBT-DataSets-r18)) OF BT-DataSet-r18 OPTIONAL, --Need ON bt-Error-r18 BT-Error-r18 OPTIONAL, -- Need ON ... } -- ASN1STOP WLAN-ProvideAssistanceData field descriptions bt-DataSet This field provides data for sets of Bluetooth bt-Error This field provides error information and may be in response to a Request Assistance Data.

[0114] The IE BT-DataSet is used byinformation for one set of Bluetooth anchors. -- ASN1START BT-DataSet-r18 ::= SEQUENCE { bt-anchor-List-r18 SEQUENCE (SIZE (1..maxBTanchor-r18)) OF BT-Anchor-Data- r18, ... }BT-Anchor-Data-r18 ::= SEQUENCE {btAddr-r13 BIT STRING (SIZE (48)), bt-AoD-Data-r18 BT-AoD-Data-r18 OPTIONAL, bt-Anchor-Location-r18 BT-Anchor-Location-r18 OPTIONAL, -- Need ON ... } BT-AoD-Data-r18 ::= SEQUENCE { advInterval INTEGER (0..16745), cteLength-r18 INTEGER (1..20) OPTIONAL, cteCount-r18 INTEGER () OPTIONAL, tx-PHY-r18 ENUMERATED {M1, M2} OPTIONAL, bt-AntennaConfig-r18 BT-AntennaConfig-r18, ...}BT-AntennaConfig-r18 ::= SEQUENCE {... }P105974WO01 PCT APPLICATION 24 of 66 BT-AP-Location-r18 ::= SEQUENCE { locationDataLCI-r18 LocationDataLCI-r18, ... } LocationDataLCI-r18 ::= SEQUENCE { latitudeUncertainty-r18 BIT STRING (SIZE (6)), latitude-r18 BIT STRING (SIZE (34)), longitudeUncertainty-r18 BIT STRING (SIZE (6)), longitude-r18 BIT STRING (SIZE (34)), altitudeUncertainty-r18 BIT STRING (SIZE (6)) OPTIONAL, -- Need ON altitude-r18 BIT STRING (SIZE (30)) OPTIONAL, -- Need ON datum-r18 BIT STRING (SIZE (8)), ... } -- ASN1STOP BT-DataSet field descriptions bt-Anchor-ListcteCount This fieldperiodic tx-PHY-r18 This field specifies theMegasymbols / s bt-AP-Location - locationDataLCI This field providesConfiguration latitudeUncertainty: 6-bits quantifying the amount of uncertainty in latitude. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 34 are reserved. Its relation with the corresponding value in degrees is expressed with the following formula: latitudeUncertainty = 8 - ceil(log2(uncertainty in degrees)) latitude: A 34-bits fixed point value consisting of 9-bits of integer and 25-bits of fraction indicating the Latitude (+ / - 90 degrees) of the AP. longitudeUncertainty: 6-bits quantifying the amount of uncertainty in longitude. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 34 are reserved. Its relation with the corresponding value in degrees is expressed with the following formula: longitudeUncertainty = 8 - ceil(log2(uncertainty in degrees)) longitude: A 34-bits fixed point value consisting of 9-bits of integer and 25-bits of fraction indicating the Longitude (+ / - 180 degrees) of the AP.P105974WO01 PCT APPLICATION 25 of 66 BT-DataSet field descriptions bt-Anchor-ListcteCount specifies the number of Bluetooth packets that include a CTE that are transmitted eachevent tx-PHY-r18 This field specifies the TX PHY M1 M2 1 2 Megasymbols / saltitudeUncertainty: 6-bits value quantifying the amount of uncertainty in the altitude value. A value of 0 is reserved to indicate that the uncertainty is unknown; values greater than 30 are reserved. Its relation with the corresponding value in metres is expressed with the following formula: altitudeUncertainty = 21 - ceil(log2( uncertainty in metres)) A 30-bit fixed point value consisting of 22-bits of integer and 8-bits of fraction indicating the altitude of the AP in metres. 8-bits indicating the map datum used for the coordinates. Defined codes are: Bit 1: World Geodetic System 1984 (WGS-84) Bit 2: North American Datum 1983 (NAD-83) with North American Vertical Datum 1988 (NAVD-88) Bit 3: North American Datum 1983 (NAD-83) with Mean Lower Low Water (MLLW) vertical datum. Bits 4 – 8 are reserved.

[0115] The IE BT-RequestAssistanceData is used by the target device to request BT assistance data from a location server. -- ASN1START BT-RequestAssistanceData-r18 ::= SEQUENCE { requestedAD-r18 BIT STRING {aod-config (0), anchor-location (1)} (SIZE (1..8)), ...} -- ASN1STOPP105974WO01 PCT APPLICATION 26 of 66 BT-RequestAssistanceData field descriptions requestedADaod-config: Bluetooth anchor AoD configurationtransmission signal to be enabled / disabled (start / stop). One way is to extend the existing measurement / location request BIT STRING to also include start / stop and another way is to simply have a new field.

[0117] The IE BT-RequestLocationInformation is used by the location server to request Bluetooth measurements, start or stop Bluetooth signal transmission from a target device -- ASN1START BT-RequestLocationInformation-r13 ::= SEQUENCE { requestedMeasurements-r13 BIT STRING { rssi (0), ),^ BT-RequestLocationInformation field descriptions ^^ This specifies the Bluetooth measurements requested and Bluetooth transmission to be started or stopped. This is represented by a bit string, with a one-value at the bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included. ^ ^ rssi: Bluetooth beacon signal strength at the target ^ ^ The following transmission request can be included. ^ ^ start: UE shall start SRS transmission after receiving with a one-value at the bit position. ^ stop: UE shall stop SRS transmission after receiving with a one-value at the bit position.P105974WO01 PCT APPLICATION 27 of 66 ^ BT-RequestLocationInformation field descriptions ^ requestedTransmision field specifies the Bluetooth transmission to be started or stopped.message body in a LPP message is used by the location server to provide assistance data to the target device either in response to a request from the target device or in an unsolicited manner.-- ASN1STARTProvideAssistanceData ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { -- -- -- -- -- -- -- -- -- -- --P105974WO01 PCT APPLICATION 28 of 66 btAnchorID-r18 INTEGER (1..4096) OPTIOANL, ... }-- ASN1STOP

[0119] The IE BT-ProvideLocationInformation is used by the target device to provide measurements for one or more Bluetooth beacons to the location server. It may also be used to provide Bluetooth positioning specific error reason. -- ASN1START BT-ProvideLocationInformation-r13 ::= SEQUENCE { bt-MeasurementInformation-r13 BT-MeasurementInformation-r13 OPTIONAL, bt-Error-r13 BT-Error-r13 OPTIONAL, ...} -- ASN1STOP

[0120] The IE BT-MeasurementInformation is illustrated below. -- ASN1START BT-MeasurementInformation-r13 ::= SEQUENCE { measurementReferenceTime-r13 UTCTime OPTIONAL, bt-MeasurementList-r13 BT-MeasurementList-r13 OPTIONAL, ..., bt-MeasurementList-r18 BT-MeasurementList-r18 OPTIONAL } BT-MeasurementList-r13 ::= SEQUENCE (SIZE(1..maxBT-Beacon-r13)) OF BT-MeasurementElement-r13 BT-MeasurementElement-r13 ::= SEQUENCE { btAddr-r13 BIT STRING (SIZE (48)), rssi-r13 INTEGER (-128..127) OPTIONAL, ..., dl-AoD-r18 INTEGER (0..180) OPTIONAL } BT-MeasurementElement-r18 ::= SEQUENCE { btAnchorAddress-r18 BIT STRING (SIZE (48)) OPTIOANL,-- ASN1STOPP105974WO01 PCT APPLICATION 29 of 66 ^ BT-MeasurementInformation field descriptions measurementReferenceTime This field provides the UTC time when the Bluetooth measurements are performed and should take the form of YYMMDDhhmmssZ. bt-MeasurementList This field provides the Bluetooth measurements for up to 32 Bluetooth beacons. btAddr This field specifies the Bluetooth public address of the Bluetooth beacon. rssi This field provides the beacon received signal strength indicator (RSSI) in dBm. btAnchorID This field indicates the measured Bluetooth Anchor ID which is assigned by the location server and provided in the assistance data. dl-AoD This field indicates the DL Angle of Departure.

[0121] The IE BT-RequestLocationInformation is used by the location server to request Bluetooth measurements, start or stop Bluetooth signal transmission from a target device. -- ASN1START BT-RequestLocationInformation-r13 ::= SEQUENCE { requestedMeasurements-r13 BIT STRING { ),P105974WO01 PCT APPLICATION 30 of 66 ^ BT-RequestLocationInformation field descriptions requestedMasurements Bluetooth transmission to be started orthe bit position means the particular measurement is requested; a zero-value means not requested. The following measurement requests can be included. ^ ^ rssi: Bluetooth beacon signal strength at the target ^ dl-AoD: Downlink Angle of Departure. This is the measurement performed at the target on the DL BLE signal transmitted by the Anchor point. ^ rsrp: Bluetooth beacon signal received signal received power. The following transmission request can be included. ^ start: UE shall start SRS transmission after receiving with a one-value at the bit position. ^ stop: UE shall stop SRS transmission after receiving with a one-value at the bit position. requestedTransmision This field specifies the Bluetooth transmission to be started or stopped.

[0122] The IE BT-ProvideCapabilites is used by the target device to provide its capabilities for Bluetooth positioning to the location server. -- ASN1START BT-ProvideCapabilities-r13 ::= SEQUENCE { bt-Modes-r13 BIT STRING { standalone (0), ue-assisted (1)} (SIZE (1..8)), bt-MeasSupported-r13 BIT STRING { rssi-r13 (0)} (SIZE (1..8)), ...,[[ idleStateForMeasurements-r14 ENUMERATED { required } OPTIONAL, periodicalReportingSupported-r14 PositioningModes OPTIONAL ]], [[ scheduledLocationRequestSupported-r17 ScheduledLocationTimeSupportPerMode-r17 OPTIONAL ]], [[bt-transmissionStartStopSupported-r18 ENUMERATED { supported} OPTIONAL ]] } -- ASN1STOPP105974WO01 PCT APPLICATION 31 of 66 ^ BT-ProvideCapabilities field descriptions bt-Modes target device. This is represented by a bitmode is supported; a zero value means not supported. bt-MeasSupported This field specifies the Bluetooth measurements supported by the target device. This is represented by a bit string, with a one-value at the bit position means the particular measurement is supported; a zero-value means not supported. A zero-value in all bit positions in the bit string means only the basic Bluetooth positioning method is supported by the target device which is reporting of the Bluetooth beacon identity. The following bits are assigned for the indicated measurements. ^ rssi: Bluetooth beacon signal strength at the target device bt-transmissionStartStopSupported ^ This field specifies the Bluetooth transmission enable / disable (start / stop) by the target device. idleStateForMeasurements ^ This field, if present, indicates that the target device requires idle state to perform BT measurements. periodicalReportingSupported ^ This field, if present, specifies the positioning modes for which the target device supports periodicalReporting. This is represented by a bit string, with a one value at the bit position means periodicalReporting for the positioning mode is supported; a zero value means not supported. If this field is absent, the location server may assume that the target device does not support periodicalReporting in CommonIEsRequestLocationInformation. scheduledLocationRequestSupported ^ This field, if present, specifies the positioning modes for which the target device supports scheduled location requests – i.e., supports the IE ScheduledLocationTime in IE CommonIEsRequestLocationInformation – and the time base(s) supported for the scheduled location time for each positioning mode. If this field is absent, the target device does not support scheduled location requests.

[0123] FIGURE 13 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodesP105974WO01 PCT APPLICATION 32 of 66 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0124] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0125] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0126] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription IdentifierP105974WO01 PCT APPLICATION 33 of 66 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0127] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0128] As a whole, the communication system 100 of FIGURE 13 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0129] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0130] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal orP105974WO01 PCT APPLICATION 34 of 66 external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).

[0131] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0132] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In otherP105974WO01 PCT APPLICATION 35 of 66 embodiments, the hub 114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0133] FIGURE 14 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0134] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0135] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 14. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multipleP105974WO01 PCT APPLICATION 36 of 66 instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0136] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0137] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0138] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the powerP105974WO01 PCT APPLICATION 37 of 66 from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0139] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0140] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0141] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / orP105974WO01 PCT APPLICATION 38 of 66 a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0142] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0143] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0144] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0145] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearableP105974WO01 PCT APPLICATION 39 of 66 technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in FIGURE 14.

[0146] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0147] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.P105974WO01 PCT APPLICATION 40 of 66

[0148] FIGURE 15 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0149] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0150] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0151] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In suchP105974WO01 PCT APPLICATION 41 of 66 embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0152] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0153] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0154] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store anyP105974WO01 PCT APPLICATION 42 of 66 calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0155] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0156] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0157] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / orP105974WO01 PCT APPLICATION 43 of 66 signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0158] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0159] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0160] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 15 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0161] FIGURE 16 is a block diagram of a host 400, which may be an embodiment of the host 116 of FIGURE 13, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtualP105974WO01 PCT APPLICATION 44 of 66 machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0162] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 3 and 4, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0163] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0164] FIGURE 17 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one orP105974WO01 PCT APPLICATION 45 of 66 more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0165] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0166] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0167] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0168] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.P105974WO01 PCT APPLICATION 46 of 66

[0169] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0170] FIGURE 18 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of FIGURE 13 and / or UE 200 of FIGURE 14), network node (such as network node 110a of FIGURE 13 and / or network node 300 of FIGURE 15), and host (such as host 116 of FIGURE 13 and / or host 400 of FIGURE 16) discussed in the preceding paragraphs will now be described with reference to FIGURE 18.

[0171] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0172] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 13) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.P105974WO01 PCT APPLICATION 47 of 66

[0173] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0174] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0175] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.P105974WO01 PCT APPLICATION 48 of 66

[0176] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0177] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the delay to directly activate an SCell by RRC and power consumption of user equipment and thereby provide benefits such as reduced user waiting time and extended battery lifetime.

[0178] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0179] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTTP105974WO01 PCT APPLICATION 49 of 66 connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

[0180] FIGURE 19 is a flow diagram illustrating a method performed by a location server for angle of arrival (AoA) positioning, according to particular embodiments. In particular embodiments, one or more steps of FIGURE 19 may be performed by network node 300 described with respect to FIGURE 15 or a location server. The network node is capable of operating as a location server for AoA positioning via an independent / non-3GPP technique.

[0181] The method may begin at step 1912, where the network node (e.g., network node 200) transmits a request to the wireless device for Bluetooth capabilities of the wireless device. Examples are described with respect to step 400 of Figures 4A and 4B, step 500 of Figure 5, and step 600 of Figure 6.

[0182] At step 1914, the network node may receive the Bluetooth capabilities from the wireless device. Examples are described with respect to step 410 of Figures 4A and 4B, step 510 of Figure 5, and step 610 of Figure 6.

[0183] At step 1916, the network node transmits a request to the wireless device for transmitting a Bluetooth signal according to a Bluetooth assistance configuration. In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; and CTE repetition. Examples are described with respect to step 420 of Figures 4A and 4B, step 520 of Figure 5, and step 620 of Figure 6.P105974WO01 PCT APPLICATION 50 of 66

[0184] At step 1918, the network node obtains an AoA positioning report from a Bluetooth anchor node. The AoA positioning report is based on one or more Bluetooth signals transmitted from the wireless device to the Bluetooth anchor node according to the Bluetooth assistance configuration. Examples are described with respect to step 444 of Figures 4A and 4B, and step 640 of Figure 6.

[0185] At step 1920, the network node estimates a position of the wireless device based on the positioning report. Examples are described with respect to step 450 of Figures 4A and 4B, and step 650 of Figure 6.

[0186] At step 1922, the network node may receive an indication from the wireless device of an updated address for the wireless device. Examples are described with respect to step 455 of Figure 4B.

[0187] Modifications, additions, or omissions may be made to method 1900 of FIGURE 19. Additionally, one or more steps in the method of FIGURE 19 may be performed in parallel or in any suitable order.

[0188] FIGURE 20 illustrates a method performed by a location server for angle of departure (AoD) positioning, according to particular embodiments. In particular embodiments, one or more steps of FIGURE 20 may be performed by network node 300 described with respect to FIGURE 15 or a location server. The network node is capable of operating as a location server for AoD positioning via an independent / non-3GPP technique.

[0189] The method may begin at step 2012, where the network node (e.g., network node 300) transmits a request to the wireless device for Bluetooth capabilities of the wireless device. Examples are described with respect to step 700 of Figure 7, step 800 of Figure 8, and step 900 of Figure 9.

[0190] At step 2014, the network node may receive the Bluetooth capabilities from the wireless device. Examples are described with respect to step 710 of Figure 7, step 810 of Figure 8, and step 910 of Figure 9.

[0191] At step 2016, the network node receives a request from the wireless device for a Bluetooth assistance configuration for the wireless device. In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; PHY type; transmit power; CTE length; CTE repetition; and antenna configuration. Examples are described with respect to step 720 of Figure 7, step 820 of Figure 8, and step 920 of Figure 9.P105974WO01 PCT APPLICATION 51 of 66

[0192] At step 2018, the network node transmits the Bluetooth assistance configuration to the wireless device. Examples are described with respect to step 730 of Figure 7, step 830 of Figure 8, and step 930 of Figure 9.

[0193] At step 2020, the network node obtains an AoD positioning report from the wireless device. The AoD positioning report is based on one or more Bluetooth signals transmitted from a Bluetooth anchor node to the wireless device according to the Bluetooth assistance configuration. Examples are described with respect to step 752 of Figure 7, step 865 of Figure 8, and step 950 of Figure 9.

[0194] At step 2022, the network node estimates a position of the wireless device based on the positioning report. For example, the position of the wireless device may be included in the positioning report, or the network node may determine a position of the wireless device based on information in the positioning report.

[0195] Modifications, additions, or omissions may be made to method 2000 of FIGURE 20. Additionally, one or more steps in the method of FIGURE 20 may be performed in parallel or in any suitable order.

[0196] FIGURE 21 illustrates a method performed by a wireless device for AoA positioning, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 21 may be performed by wireless device 200 described with respect to FIGURE 14. The wireless device is operable to perform AoA positioning via an independent / non-3GPP technique.

[0197] The method may begin at step 2112, where the wireless device (e.g., UE 200) receives a request from a location server for Bluetooth capabilities of the wireless device. Examples are described with respect to step 400 of Figures 4A and 4B, step 500 of Figure 5, and step 600 of Figure 6.

[0198] At step 2114, the wireless device may transmit the Bluetooth capabilities to the location server. Examples are described with respect to step 410 of Figures 4A and 4B, step 510 of Figure 5, and step 610 of Figure 6.

[0199] At step 2116, the wireless device receives a request from the location server for transmitting a Bluetooth signal according to a Bluetooth assistance configuration. In particular embodiments, the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; PHY type; transmit power; CTE length; and CTE repetition. ExamplesP105974WO01 PCT APPLICATION 52 of 66 are described with respect to step 420 of Figures 4A and 4B, step 520 of Figure 5, and step 620 of Figure 6.

[0200] At step 2118, the wireless device transmits one or more Bluetooth signals to a Bluetooth anchor node according to the Bluetooth assistance configuration. Examples are described with respect to step 440 of Figures 4A and 4B, and step 540 of Figure 5.

[0201] At step 2120, the wireless device may transmit an indication of an updated address for the wireless device to the location server. Examples are described with respect to step 455 of Figure 4B.

[0202] Modifications, additions, or omissions may be made to method 2100 of FIGURE 21. Additionally, one or more steps in the method of FIGURE 21may be performed in parallel or in any suitable order.

[0203] FIGURE 22 illustrates a method performed by a wireless device for AoD positioning, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 22 may be performed by wireless device 200 described with respect to FIGURE 14. The wireless device is operable to perform AoD positioning via an independent / non-3GPP technique.

[0204] The method may begin at step 2212, where the wireless device (e.g., UE 200) receives a request from a location server for Bluetooth capabilities of the wireless device. Examples are described with respect to step 700 of Figure 7, step 800 of Figure 8, and step 900 of Figure 9.

[0205] At step 2214, the wireless device may transmit the Bluetooth capabilities to the location server. Examples are described with respect to step 710 of Figure 7, step 810 of Figure 8, and step 910 of Figure 9.

[0206] At step 2216, the wireless device transmits a request to a location server for a Bluetooth assistance configuration for the wireless device. Examples are described with respect to step 720 of Figure 7, step 820 of Figure 8, and step 920 of Figure 9.

[0207] At step 2218, the wireless device receives the Bluetooth assistance configuration from a network node. Examples are described with respect to step 730 of Figure 7, step 830 of Figure 8, and step 930 of Figure 9.

[0208] At step 2220, the wireless device receives one or more Bluetooth signals for AoD positioning from a Bluetooth anchor node according to the Bluetooth assistance configuration. Examples are described with respect to step 740 of Figure 7 and step 850 of Figure 8.P105974WO01 PCT APPLICATION 53 of 66

[0209] At step 2222, the wireless device estimates a position of the wireless device based on the one of more received Bluetooth signals. Examples are described with respect to steps 742 and 750 of Figure 7 and steps 850 and 860 of Figure 8.

[0210] At step 2224, the wireless device transmits an AoD positioning report based on the estimated position to the location server. Examples are described with respect to step 752 of Figure 7, step 865 of Figure 8, and step 950 of Figure 9.

[0211] Modifications, additions, or omissions may be made to method 2200 of FIGURE 22. Additionally, one or more steps in the method of FIGURE 22may be performed in parallel or in any suitable order.

[0212] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

[0213] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0214] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0215] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0216] Examples of particular embodiments are included below.P105974WO01 PCT APPLICATION 54 of 66 EMBODIMENTS 1. A method performed by a location server for positioning via a non-3GPP positioning protocol, the method comprising: − transmitting a request to a wireless device for a non-3GPP positioning protocol configuration of the wireless device; − receiving the non-3GPP positioning protocol configuration from the wireless device; − obtaining an AoA positioning report from an anchor node of the non-3GPP positioning protocol; and − estimating a position of the wireless device based on the positioning report. 2. A method performed by a location server for positioning via a non-3GPP positioning protocol, the method comprising: − transmitting a request to a wireless device for a non-3GPP positioning protocol configuration of the wireless device; − receiving the non-3GPP positioning protocol configuration from the wireless device; and − obtaining an AoD positioning report from the wireless device. 3. The method of any one of the previous embodiments, wherein the non-3GPP positioning protocol comprises a Bluetooth low energy protocol. 4. A method performed by a location server for positioning via a non-3GPP positioning protocol, the method comprising: − any of the location server steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Group A Embodiments 5. A method performed by a for positioning via a non-3GPP positioning protocol, the method comprising: − receiving a request from a location server for a non-3GPP positioning protocol configuration of the wireless device;P105974WO01 PCT APPLICATION 55 of 66 − transmitting the non-3GPP positioning protocol configuration to the location server; and − transmitting a non-3GPP positioning protocol positioning signal for AoA positioning by an anchor node of the non-3GPP positioning protocol. 6. A method performed by a for positioning via a non-3GPP positioning protocol, the method comprising: − receiving a request from a location server for a non-3GPP positioning protocol configuration of the wireless device; − transmitting the non-3GPP positioning protocol configuration to the location server; − estimating a position of the wireless device based on AoD positioning on a non- 3GPP positioning protocol positioning signal; and − transmitting an AoD positioning report to the location server. 7. The method of any one of embodiments 6-7, wherein the non-3GPP positioning protocol comprises a Bluetooth low energy protocol. 8. A method performed by a wireless device, the method comprising: − any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 9. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. 10. The method of any of the previous embodiments, further comprising: − providing user data; and − forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments 11. A method performed by a base station, the method comprising: − any of the steps, features, or functions described above with respect to baseP105974WO01 PCT APPLICATION 56 of 66 station, either alone or in combination with other steps, features, or functions described above. 12. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above. 13. The method of any of the previous embodiments, further comprising: − obtaining user data; and − forwarding the user data to a host computer or a wireless device. Group C Embodiments 14. A mobile terminal comprising: − processing circuitry configured to perform any of the steps of any of the Group A embodiments; and − power supply circuitry configured to supply power to the wireless device. 15. A base station comprising: − processing circuitry configured to perform any of the steps of any of the Group B embodiments; − power supply circuitry configured to supply power to the wireless device. 16. A user equipment (UE) comprising: − an antenna configured to send and receive wireless signals; − radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; − the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; − an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; − an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and − a battery connected to the processing circuitry and configured to supply powerP105974WO01 PCT APPLICATION 57 of 66 to the UE. 17. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), − wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 18. The communication system of the pervious embodiment further including the base station. 19. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. 20. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE comprises processing circuitry configured to execute a client application associated with the host application. 21. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. 22. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. 23. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at theP105974WO01 PCT APPLICATION 58 of 66 UE, executing a client application associated with the host application. 24. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. 25. A communication system including a host computer comprising: − processing circuitry configured to provide user data; and − a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), − wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. 26. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. 27. The communication system of the previous 2 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application. 28. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, providing user data; and − at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. 29. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. 30. A communication system including a host computer comprising:P105974WO01 PCT APPLICATION 59 of 66 − communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, − wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments. 31. The communication system of the previous embodiment, further including the UE. 32. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. 33. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. 34. The communication system of the previous 4 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and − the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. 35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: − at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. 36. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.P105974WO01 PCT APPLICATION 60 of 66 37. The method of the previous 2 embodiments, further comprising: − at the UE, executing a client application, thereby providing the user data to be transmitted; and − at the host computer, executing a host application associated with the client application. 38. The method of the previous 3 embodiments, further comprising: − at the UE, executing a client application; and − at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, − wherein the user data to be transmitted is provided by the client application in response to the input data. 39. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. 40. The communication system of the previous embodiment further including the base station. 41. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. 42. The communication system of the previous 3 embodiments, wherein: − the processing circuitry of the host computer is configured to execute a host application; − the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. 43. A method implemented in a communication system including a host computer, a baseP105974WO01 PCT APPLICATION 61 of 66 station and a user equipment (UE), the method comprising: − at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. 44. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. 45. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

P105974WO01 PCT APPLICATION 62 of 66 CLAIMS:

1. A method performed by a location server network node for angle-of-arrival (AoA) Bluetooth positioning, the method comprising: transmitting (1916) a request to a wireless device for transmitting a Bluetooth signal according to a Bluetooth assistance configuration; obtaining (1918) an AoA positioning report from a Bluetooth anchor node, wherein the AoA positioning report is based on one or more Bluetooth signals transmitted from the wireless device to the Bluetooth anchor node according to the Bluetooth assistance configuration; and estimating (1920) a position of the wireless device based on the positioning report.

2. The method of claim 1, further comprising: transmitting (1912) a request to the wireless device for Bluetooth capabilities of the wireless device; and receiving (1914) the Bluetooth capabilities from the wireless device.

3. The method of any one of claims 1-2, further comprising receiving (1922) an indication from the wireless device of an updated address for the wireless device.

4. The method of claim 3, wherein the indication comprises an unsolicited indication from the wireless device.

5. The method of any one of claims 1-4, wherein the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; and CTE repetition.

6. A network node (300) capable of operating as a location server for angle-of- arrival (AoA) Bluetooth positioning, the network node comprising processing circuitry (302)P105974WO01 PCT APPLICATION 63 of 66 operable to perform the steps of any one of claims 1-5.

7. A method performed by a location server network node for angle-of-departure (AoD) Bluetooth positioning, the method comprising: receiving (2016) a request from a wireless device for a Bluetooth assistance configuration for the wireless device; transmitting (2018) the Bluetooth assistance configuration to the wireless device; and obtaining (2020) an AoD positioning report from the wireless device, wherein the AoD positioning report is based on one or more Bluetooth signals transmitted from a Bluetooth anchor node to the wireless device according to the Bluetooth assistance configuration.

8. The method of claim 7, further comprising: transmitting (2012) a request to the wireless device for Bluetooth capabilities of the wireless device; and receiving (2014) the Bluetooth capabilities from the wireless device.

9. The method of any one of claims 7-8, wherein the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; CTE repetition; and antenna configuration.

10. A network node (300) capable of operating as a location server for angle-of- departure (AoD) Bluetooth positioning, the network node comprising processing circuitry (302) operable to perform the steps of any one of claims 7-9.

11. A method performed by a wireless device for angle-of-arrival (AoA) Bluetooth positioning, the method comprising: receiving (2116) a request from a location server for transmitting a Bluetooth signalP105974WO01 PCT APPLICATION 64 of 66 according to a Bluetooth assistance configuration; and transmitting (2118) one or more Bluetooth signals to a Bluetooth anchor node according to the Bluetooth assistance configuration.

12. The method of claim 11, further comprising: receiving (2112) a request from the location server for Bluetooth capabilities of the wireless device; and transmitting (2114) the Bluetooth capabilities to the location server.

13. The method of any one of claims 11-12, further comprising transmitting (2120) an indication of an updated address for the wireless device to the location server.

14. The method of claim 13, wherein the indication comprises an unsolicited indication from the wireless device.

15. The method of any one of claims 11-14, wherein the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; and CTE repetition.

16. A wireless device (200) operable to perform angle-of-arrival (AoA) Bluetooth positioning, the wireless device comprising processing circuitry (202) operable to perform the steps of any one of claims 11-15.

17. A method performed by a wireless device for angle-of-departure (AoD) Bluetooth positioning, the method comprising: transmitting (2216) a request to a location server for a Bluetooth assistance configuration for the wireless device; receiving (2218) the Bluetooth assistance configuration from a network node;P105974WO01 PCT APPLICATION 65 of 66 receiving (2220) one or more Bluetooth signals for AoD positioning from a Bluetooth anchor node according to the Bluetooth assistance configuration; estimating (2222) a position of the wireless device based on the one of more received Bluetooth signals; and transmitting (2224) an AoD positioning report based on the estimated position to the location server.

18. The method of claim 17, further comprising: receiving (2212) a request from the location server for Bluetooth capabilities of the wireless device; and transmitting (2214) the Bluetooth capabilities to the location server.

19. The method of any one of claims 17-18, wherein receiving the Bluetooth assistance configuration comprises receiving the Bluetooth assistance configuration from the location server.

20. The method of any one of claims 17-18, wherein receiving the Bluetooth assistance configuration comprises receiving the Bluetooth assistance configuration broadcast from a base station.

21. The method of any one of claims 11-14, wherein the Bluetooth assistance configuration comprises any one or more of: advertising periodicity; physical layer (PHY) type; transmit power; constant tone extension (CTE) length; CTE repetition; and antenna configuration.

22. A wireless device (200) operable to perform angle-of-departure (AoD) Bluetooth positioning, the wireless device comprising processing circuitry (202) operable to perform the steps of any one of claims 17-21.

Images