WO2017064356A1 - Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement - Google Patents

Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement Download PDF

Info

Publication number
WO2017064356A1
WO2017064356A1 PCT/FI2015/050693 FI2015050693W WO2017064356A1 WO 2017064356 A1 WO2017064356 A1 WO 2017064356A1 FI 2015050693 W FI2015050693 W FI 2015050693W WO 2017064356 A1 WO2017064356 A1 WO 2017064356A1
Authority
WO
WIPO (PCT)
Prior art keywords
trackable
timing control
devices
control packet
packet
Prior art date
Application number
PCT/FI2015/050693
Other languages
English (en)
Inventor
Olli KOSKIMIES
Ilari Teikari
Markus ISOMÄKI
Jani Ollikainen
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/FI2015/050693 priority Critical patent/WO2017064356A1/fr
Publication of WO2017064356A1 publication Critical patent/WO2017064356A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006—Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This specification relates to managing operation of at least one wireless communication device in a positioning system.
  • Such systems include Nokia's High Accuracy Indoor Positioning (HAIP) system which is configured to track the position of trackable devices using locator devices which utilise phased antenna arrays to determine a bearing between the trackable device and the locator device based on radio frequency (RF) data packets received at the locator device.
  • HAIP High Accuracy Indoor Positioning
  • RF radio frequency
  • COIP cost-optimised indoor positioning
  • These systems may utilise the signal strength of incoming data packets to provide room-level accuracy or, if a sufficient number of COIP locator devices are provided within a particular space, may utilise the signal strength in addition to fingerprinting (radio-maps) to provide an accuracy of approximately 2 meters.
  • this specification describes a method comprising: positioning server apparatus managing operation of at least one wireless communication device located within a managed area of a positioning system by causing a timing control packet to be transmitted to the at least one wireless communication device by an intermediary device located within the managed area, the timing control packet being configured to cause the recipient wireless communication device to adapt at least one timing parameter relating to at least one of a reception window and a transmission window.
  • the intermediary device may be configured to constantly listen for incoming packets from trackable devices.
  • the intermediary device may be mains powered and/or may be a low-cost device comprising a single antenna.
  • the intermediary device may be operable to determine a signal strength of packets received from trackable devices and to provide information indicative of the measured signal strength to the positioning server apparatus.
  • Timing parameter control information included in the timing control packet may be prepared based on information derived from packets received by the intermediary device from the at least one trackable device.
  • the at least one wireless communication device may include at least one of: the at least one trackable device; and at least one locator device configured to enable locations of trackable devices to be determined.
  • the timing control packet may be: a trackable device timing control packet configured to cause the at least one trackable device to adapt a timing of at least one of a reception window and a transmission window; or a locator device timing control packet configured to cause the at least one locator device to adapt a timing of a reception window during which the locator device listens for incoming packets; or a locator device timing control packet configured to cause the at least one locator device to adapt a timing of a transmission during which the locator device uploads data relating to one or more trackable devices within the area for receipt by the positioning server apparatus.
  • the timing control packet may be a trackable device timing control packet configured to cause the at least one trackable device to adapt a start time of a transmission window during which the trackable device transmits a packet and/or to adapt an interval between transmission windows.
  • the method may further comprise the positioning server apparatus causing transmission of the trackable device timing control packet in response to determining that the trackable device is newly arrived in the managed area of the positioning system. The determination may be based on area ID included in packet from trackable device.
  • the method may further comprise the positioning server apparatus determining the interval between transmission windows for the newly arrived trackable device based on a positioning requirement for the newly arrived trackable device and preparing the timing adaptation information for the newly arrived trackable device timing control packet based on the determined interval. For instance, the server apparatus may determine the positioning requirements (e.g. positioning frequency) for the trackable device based on information in the received packet (e.g. device type and/or device ID) and information stored in a database.
  • the positioning requirements e.g. positioning frequency
  • the method may further comprise, subsequent to causing transmission of the trackable device timing control packet, the positioning server apparatus determining, based on a positioning packet received from the newly arrived trackable device, if the newly arrived trackable device has adapted the at least one timing parameter in accordance with the trackable device timing control packet, and, if so, causing the intermediary device to transmit a locator device timing control packet to at least one locator device in the managed area to cause the at least one locator device to adapt a reception window to coincide with the transmission window of the newly arrived trackable device. If not, the server apparatus may cause the trackable device timing control packet to be re-sent by the intermediary device.
  • the locator device timing control packet may be a reception synchronisation packet configured to cause the at least one locator device to adapt a timing of a reception window during which the locator device listens for incoming packets from trackable devices in the managed area.
  • the locator device timing control packet may include information for causing the locator device to adapt an interval between transmissions by the locator device during which the locator device uploads data relating to trackable devices within the managed area for receipt by the positioning server apparatus.
  • the method may further comprise the positioning server apparatus determining the interval between transmissions by the locator device based on at least one of a trackable device identifier and a type of one or more of the trackable devices within the area.
  • a locator device timing control packet may be a sleep mode initiation packet configured to cause the at least one locator device to enter sleep mode in which an interval between reception windows during which the locator device listens for incoming timing control packets from the intermediary device is increased and in which, during the interval between the reception windows, reception components of the locator device are powered-down.
  • the method may further comprise the positioning server apparatus causing the intermediary device to transmit the sleep mode initiation packet in response to a determination that there are no trackable devices currently located in the managed area.
  • a locator device timing control packet may be a sleep mode adjustment packet configured to cause the at least one locator device, when already operating in a sleep mode, to increase an interval between reception windows during which the locator device listens for incoming timing control packets from the intermediary device.
  • the method may further comprise the positioning server apparatus causing the intermediary device to transmit the sleep mode adjustment packet in response to a determination that there are no trackable devices currently located in the managed area and there are no trackable devices in at least one neighbouring managed area.
  • locator device timing control packet may be a wake-up packet configured cause the at least one locator device to exit sleep mode and thereby to resume listening for incoming packets from trackable devices in the managed area.
  • the method may further comprise the positioning server apparatus causing the intermediary device to transmit the wake-up packet in response to a determination that a trackable device is approaching or has entered the managed area.
  • the method may further comprise the positioning server apparatus causing the intermediary device to transmit the trackable device timing control packet in response to receiving an indication that at least two trackable devices are located within the managed area.
  • the method may further comprise the positioning server apparatus causing the intermediary device to transmit the trackable device timing control packet to a first of the trackable devices in the managed area, the trackable device timing control packet being configured to cause the first of the trackable devices to adapt at least one timing parameter such that the transmission window of the first of the trackable devices during which a packet is transmitted coincides with the reception window of a second of the trackable devices in the managed area and/or the reception window of the first of the trackable devices coincides with the transmission window of the second of the trackable devices.
  • the positioning server apparatus may further cause the intermediary device to transmit a second trackable device timing control packet to the second of the trackable devices, the second trackable device timing control packet being configured to cause the second of the trackable devices to adapt at least one timing parameter such that the transmission window of the first of the trackable devices coincides with the reception window of a second of the trackable devices in the managed area and/ or the reception window of the first of the trackable devices coincides with the transmission window of the second of the trackable devices.
  • the trackable device timing control packet and the second trackable device timing control packet may be configured to indicate a time at which the first and second devices should listen for a process initiation control message, and the method may further comprise, subsequent to transmission of the trackable device timing control packet and the second trackable device timing control packet, causing the intermediary device to transmit a process initiation control packet to the first and second trackable devices for causing the first and second trackable devices to respond by carrying out the adaptation of the at least one timing parameter indicated by the respective one of the trackable device timing control packets.
  • the method may further comprise the positioning server apparatus receiving from the intermediary device at least one of: information indicative of a signal strength of a proximity measurement packet transmitted by the first of the trackable devices and received by the second of the trackable devices; and information indicative of a signal strength of a proximity measurement packet transmitted by the second of the trackable devices and received by the first of the trackable devices, and based on the received information, determining a proximity between the first and second trackable devices.
  • the method may also or alternatively, comprise the positioning server apparatus causing the intermediary device to transmit the trackable device timing control packet following a determination, based on a device identifier and/or a type of each of the first and second trackable devices, that transmission of the trackable device timing control packet is required.
  • this specification describes apparatus configured to perform any method as described with reference to the first aspect.
  • this specification describes computer-readable instructions which when executed by computing apparatus cause the computing apparatus to perform any method as described with reference to the first aspect.
  • this specification describes apparatus comprising: at least one processor; and at least one memory including computer program code, which when executed by the at least one processor, causes the apparatus: to manage operation of at least one wireless communication device located within a managed area of a positioning system by causing a timing control packet to be transmitted to the at least one wireless communication device by an intermediary device located within the managed area, the timing control packet being configured to cause the recipient wireless communication device to adapt at least one timing parameter relating to at least one of a reception window and a transmission window.
  • the intermediary device may be configured to constantly listen for incoming packets from trackable devices.
  • the intermediary device may be mains powered and/or may be a low-cost device comprising a single antenna.
  • the intermediary device may be operable to determine a signal strength of packets received from trackable devices and to provide information indicative of the measured signal strength to the apparatus.
  • Timing parameter control information included in the timing control packet may be prepared based on information derived from packets received by the intermediary device from the at least one trackable device.
  • the at least one wireless communication device may include at least one of the at least one trackable device, and at least one locator device configured to enable locations of trackable devices to be determined.
  • the timing control packet may be: a trackable device timing control packet configured to cause the at least one trackable device to adapt a timing of at least one of a reception window and a transmission window; or a locator device timing control packet configured to cause the at least one locator device to adapt a timing of a reception window during which the locator device listens for incoming packets; or a locator device timing control packet configured to cause the at least one locator device to adapt a timing of a transmission during which the locator device uploads data relating to one or more trackable devices within the area for receipt by the positioning server apparatus.
  • the timing control packet may be a trackable device timing control packet configured to cause the at least one trackable device to adapt a start time of a transmission window during which the trackable device transmits a packet and/or to adapt an interval between transmission windows.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause transmission of the trackable device timing control packet in response to determining that the trackable device is newly arrived in the managed area of the positioning system. The determination may be based on area ID included in packet from trackable device.
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine the interval between transmission windows for the newly arrived trackable device based on a positioning requirement for the newly arrived trackable device and preparing the timing adaptation information for the newly arrived trackable device timing control packet based on the determined interval.
  • the server apparatus may determine the positioning requirements (e.g. positioning frequency) for the trackable device based on information in the received packet (e.g. device type and/or device ID) and information stored in a database.
  • the computer program code when executed by the at least one processor, may cause the apparatus, subsequent to causing transmission of the trackable device timing control packet: to determine, based on a positioning packet received from the newly arrived trackable device, if the newly arrived trackable device has adapted the at least one timing parameter in accordance with the trackable device timing control packet; and, if so, to cause the intermediary device to transmit a locator device timing control packet to at least one locator device in the managed area to cause the at least one locator device to adapt a reception window to coincide with the transmission window of the newly arrived trackable device. If not, the apparatus may cause the trackable device timing control packet to be re-sent by the intermediary device.
  • the locator device timing control packet may be a reception synchronisation packet configured to cause the at least one locator device to adapt a timing of a reception window during which the locator device listens for incoming packets from trackable devices in the managed area.
  • the locator device timing control packet may in some examples additionally or instead include information for causing the locator device to adapt an interval between
  • the computer program code when executed by the at least one processor, may cause the apparatus to determine the interval between transmissions by the locator device based on at least one of a trackable device identifier and a type of one or more of the trackable devices within the area.
  • a locator device timing control packet may be a sleep mode initiation packet configured cause the at least one locator device to enter sleep mode in which an interval between reception windows during which the locator device listens for incoming timing control packets from the intermediary device is increased and in which, during the interval between the reception windows, reception components of the locator device are powered-down.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit the sleep mode initiation packet in response to a determination that there are no trackable devices currently located in the managed area.
  • a locator device timing control packet may be a sleep mode adjustment packet configured to cause the at least one locator device, when already operating in a sleep mode, to increase an interval between reception windows during which the locator device listens for incoming timing control packets from the intermediary device.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit the sleep mode adjustment packet in response to a determination that there are no trackable devices currently located in the managed area and there are no trackable devices in at least one neighbouring managed area.
  • locator device timing control packet may be a wake-up packet configured cause the at least one locator device to exit sleep mode and thereby to resume listening for incoming packets from trackable devices in the managed area.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit the wake-up packet in response to a determination that a trackable device is approaching or has entered the managed area.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit the trackable device timing control packet in response to receiving an indication that at least two trackable devices are located within the managed area.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit the trackable device timing control packet to a first of the trackable devices in the managed area, the trackable device timing control packet being configured to cause the first of the trackable devices to adapt at least one timing parameter such that the transmission window of the first of the trackable devices during which a packet is transmitted coincides with the reception window of a second of the trackable devices in the managed area and/or the reception window of the first of the trackable devices coincides with the transmission window of the second of the trackable devices.
  • the computer program code when executed by the at least one processor, may cause the apparatus to cause the intermediary device to transmit a second trackable device timing control packet to the second of the trackable devices, the second trackable device timing control packet being configured to cause the second of the trackable devices to adapt at least one timing parameter such that the transmission window of the first of the trackable devices coincides with the reception window of a second of the trackable devices in the managed area and/or the reception window of the first of the trackable devices coincides with the transmission window of the second of the trackable devices.
  • the trackable device timing control packet and the second trackable device timing control packet may be configured to indicate a time at which the first and second devices should listen for a process initiation control message, and the computer program code, when executed by the at least one processor, may cause the apparatus to, subsequent to transmission of the trackable device timing control packet and the second trackable device timing control packet, cause the intermediary device to transmit a process initiation control packet to the first and second trackable devices for causing the first and second trackable devices to respond by carrying out the adaptation of the at least one timing parameter indicated by the respective one of the trackable device timing control packets.
  • the positioning server apparatus causes the intermediary device to transmit the trackable device timing control packet in response to receiving an indication that at least two trackable devices are located within the managed area
  • the computer program code when executed by the at least one processor, may cause the apparatus to receive from the intermediary device at least one of: information indicative of a signal strength of a proximity measurement packet transmitted by the first of the trackable devices and received by the second of the trackable devices; and information indicative of a signal strength of a proximity measurement packet transmitted by the second of the trackable devices and received by the first of the trackable devices, and based on the received information, to determine a proximity between the first and second trackable devices.
  • the computer program code may, also or alternatively, when executed by the at least one processor, cause the apparatus to cause the intermediary device to transmit the trackable device timing control packet following a determination, based on a device identifier and/or a type of each of the first and second trackable devices, that transmission of the trackable device timing control packet is required.
  • this specification describes a computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, cause performance of at least: positioning server apparatus managing operation of at least one wireless communication device located within a managed area of a positioning system by causing a timing control packet to be transmitted to the at least one wireless communication device by an intermediary device located within the managed area, the timing control packet being configured to cause the recipient wireless
  • the computer-readable code stored on the medium of the fifth aspect may further cause performance of any of the operations described with reference to the method of the first aspect.
  • this specification describes apparatus comprising: means for positioning server apparatus managing operation of at least one wireless communication device located within a managed area of a positioning system by causing a timing control packet to be transmitted to the at least one wireless communication device by an intermediary device located within the managed area, the timing control packet being configured to cause the recipient wireless communication device to adapt at least one timing parameter relating to at least one of a reception window and a transmission window.
  • the apparatus of the sixth aspect may further comprise means for causing performance of any of the operations described with reference to method of the first aspect.
  • Figure l is a positioning system comprising at least one managed area
  • Figure 2 is a flow chart schematically illustrating various functionalities which may be provided by the positioning server apparatus of Figure l;
  • Figure 3 is a flow chart schematically illustrating various other functionalities which may be provided by the positioning server apparatus of Figure l;
  • Figure 4 is a message flow diagram schematically illustrating an example of an
  • Figure 5 is a message flow diagram schematically illustrating another example of an implementation of the system described with reference to at least Figures 1, 2 and 6A to 6C;
  • Figures 6A to 6C are schematic block diagrams illustrating example configurations of the intermediary devices, the locator devices and the trackable devices of Figure 1.
  • Figure 1 is an example of positioning system 1 comprising positioning server apparatus 13 for managing operations of at least one wireless communication device located within a managed area A, B using an intermediary device 11A, 11B.
  • the positioning server apparatus 13 is also configured to determine a position of at least one trackable device 10 within at least one managed area A, B.
  • the server apparatus may be able to reduce the amount of energy consumed by the device and also to reduce network traffic within a particular area.
  • each area A, B is shown as including at least one locator device 12. However, in some implementations, neither area may include the locator devices 12, while in others the at least one locator device 12 may be present in only the first managed area A.
  • Figure 1 shows each of the managed areas A, B as including at least one trackable device 10. However, some or all of these trackable devices may be mobile and so the example of Figure 1 represents just a snapshot in time. At other times, as will be discussed later, no trackable devices 10 may be located in one or both areas A, B.
  • the positioning server apparatus 13 is configured to manage the at least one wireless communication device located within a managed area A, B by causing a timing control packet to be transmitted to the at least one wireless communication device by the intermediary device 11.
  • the timing control packet when received by the recipient device, causes the recipient to adapt at least one timing parameter relating to at least one of a reception window and a transmission window.
  • the timing control packet includes timing parameter control (or adaptation) information which is prepared based on information relating to at least one trackable device 10.
  • the information relating to the trackable device may be derived from receipt of packets transmitted by the trackable device. In such examples, this information may be provided to the positioning server apparatus 13 by the intermediary device 11.
  • the at least one wireless communication device 10, 12 within the managed area A, B, operation of which is managed by the positioning server apparatus 13, may include one or more trackable devices 10 located within the managed area A, B.
  • the at least one wireless communication device may additionally include one or more locator devices 12.
  • Timing control packets which are for receipt by one or more trackable devices 10 may be referred to as trackable device timing control packets.
  • Timing control packets which are for receipt by one or more locator device packets 10 may be referred to as locator device timing control packets.
  • the trackable device timing control packets may be configured to cause the at least one trackable device to adapt a timing of at least one of a reception window and a transmission window. More specifically, in some examples, the trackable device timing control packet may be configured to cause the at least one trackable device to adapt a start time of a transmission window during which the trackable device transmits a packet and/or to adapt an interval between transmission slots/windows. This may be used to synchronise transmission and reception of data packets to reduce collisions between packets transmitted by multiple trackable devices in one managed area. Similarly, by controlling when the trackable devices 10 transmit packets, it enables locator devices 12 to "listen for" packets only when they are expected and between those times the locator devices may be operating in a reduced power mode. In some examples, so as to eliminate collisions (as far as possible), each trackable device 10 in the managed area A, B may be allocated a different transmission slot.
  • the positioning server apparatus 13 may determine the interval between transmission windows for trackable devices 10 based on a type of the trackable device 10 and may prepare the timing parameter control information accordingly.
  • the type of the trackable device 10 may be determined based in information in a field of packets transmitted by the trackable device.
  • the interval between transmission windows may be determined by querying a database based on the type and/or a device ID of the trackable device 10.
  • Locator device timing control packets may be configured to cause the at least one locator device to adapt a timing of a reception window during which the locator device listens for incoming packets from trackable devices and/or control packets from the intermediary device.
  • a specific type of such a packet may be referred to as a locator device reception synchronisation packet, which synchronises a reception window of the locator device 12 with a transmission window of a trackable device 10. This enables the locator devices 12 to utilise less power when transmissions from trackable devices 10 in the area are not expected.
  • a sleep mode initiation packet which is configured to cause the at least one locator device 12 to enter sleep mode in which an interval between reception windows during which the locator device 12 listens for incoming timing control packets from the intermediary device 11 is increased and in which, during the interval between the reception windows, reception components of the locator device are powered- down.
  • a sleep mode initiation packet may be caused to be transmitted when the positioning server apparatus 13 determines that no trackable devices 10 are in the managed area A, B.
  • the timing parameter control information in the sleep mode initiation packet may be said to be prepared based on information (e.g. an elapsed time) indicating that at least one trackable device is not in the managed area.
  • a sleep mode adjustment packet may be transmitted by the intermediary device 11 under control of the positioning server 13.
  • a sleep mode adjustment packet is configured to cause the at least one locator device, when already operating in a sleep mode, to change an interval between reception windows during which the locator device 12 listens for incoming timing control packets from the intermediary device 11. This may further reduce the energy being utilised by the locator devices 12 in the managed area A, B.
  • the positioning server apparatus 13 may for instance cause the intermediary device 11 to transmit the sleep mode adjustment packet which increases the interval between reception windows in response to a determination that there are no trackable devices 10 currently located in the managed area and there are no trackable devices 10 in at least one neighbouring area.
  • Another sleep mode adjustment packet may subsequently be sent which reduces the interval between reception windows. This may be sent, for instance, when it is determined that a trackable device 10 has entered the neighbouring area.
  • a locator device wake-up packet which is configured to cause the at least one locator device 12 to exit sleep mode and thereby to resume listening for incoming packets from trackable devices 10 in the managed area A, may be transmitted by the intermediary device 11 under the control of the positioning server apparatus 13.
  • locator device timing control packets which may also or alternatively be employed include locator device upload timing control packets. These are configured to cause the at least one locator device 12 to adapt a timing of a transmission during which the locator device uploads data relating to trackable devices 10 within the area A, B for receipt by the positioning server apparatus 13. This enables the positioning server apparatus 13 to determine a balance between the higher-energy usage of frequent (and so low latency) uploads and the more energy-efficient (but higher latency) less frequent uploads. The determination may be made on the basis of properties associated with the trackable devices 10 in the managed area A, B.
  • the functionality of the positioning server apparatus 13 may be provided under control of a controller 130.
  • the positioning server apparatus 13 includes an
  • I/O interface 131 for receiving data from the intermediary device 11 (and also, in some examples, the locator devices 12) and also for providing data (such as timing control information and commands) to the intermediary device 11.
  • the data may be passed using any suitable protocol over a wired or wireless connection, and the I/O interface 131 is configured accordingly based on the type of connection and protocol used.
  • the positioning server apparatus 12 may be made up of one or more different computing apparatuses which may be located in the same premises as the intermediary device 11 and, if applicable also the one or more locator devices 12, (put another way, they may be part of the local area network) or may be remotely located and connected to the intermediary devices 11 via the internet (put another way, may be a cloud server).
  • the intermediary device 11 of each managed area A, B is configured to transmit timing control packets to the one or more communication devices 10, 12 within its managed area
  • the intermediary device may also be configured to receive data packets from trackable devices 10 in the managed area A, B and to provide information derived from receipt of those packets to the positioning server apparatus 13. As much of the data/control information being transferred within a particular managed area A is routed through the intermediary device 11, the intermediary device 11 may be referred to as a gateway device.
  • the positioning server apparatus 13 may be able to determine which trackable devices 10 are located in which managed area A.
  • the intermediary device 11 may be configured to determine a signal strength (e.g. RSSI) of packets it receives. The information indicative of the signal strength may then be provided to the positioning server apparatus 13, which may use it to determine the area A, B in which the trackable device is currently located. For instance, if a particular trackable device 10 is near a boundary between managed areas, packets it transmits may be received by the intermediary device 11 from each area A,
  • a signal strength e.g. RSSI
  • the positioning server apparatus 13 may deem the trackable device 10 to be in the area whose intermediary device 11 reports the highest signal strength.
  • the intermediary device 11 may be a simple, relatively low-value device. As such, the intermediary device 11 may utilise only a single antenna 111 (see the schematic illustration of Figure 6A) to transmit the timing control packets and may use the same antenna 111 to receive packets from the trackable devices 10.
  • the intermediary device may be mains- powered. For instance, it may be configured so as plug in to a mains power socket.
  • the intermediary device 11 may be constantly listening for incoming packets from the trackable devices 10. Despite constantly listening for incoming packets, the simple nature of the intermediary device 11 means that less energy is used than would result from one of the locator devices 12 constantly listening for incoming packets.
  • the intermediary device 11 may report data/information derived from all packets it receives to the positioning server apparatus 13. This reporting of data/information may be performed in response to receipt of a packet from a trackable device 10.
  • the intermediary device 11 may be configured to maintain a master clock. It may periodically broadcast the current time based on the master clock to the other wireless communication devices 10, 12 within its managed area. As such, the devices within its managed area are kept time-synchronised.
  • the antenna 111 of the intermediary device 11 is connected to transceiver circuitry 112.
  • the functionality provided by the intermediary device 11, as described herein, may be controlled (or caused) by a controller 113 which forms part of the intermediary device 11.
  • Data/information is passed to and received from the positioning server apparatus 13 by the intermediary device 11 via an input/output (I/O) interface 115.
  • the data may be passed using any suitable protocol over a wired or wireless connection, and the I/O interface 115 is configured accordingly based on the type of connection and protocol used. For instance, as will be discussed later, in some examples, data may be provided to the positioning server apparatus 13 using an 802.11 wireless local area network protocol (e.g.
  • the locator devices 12 are configured to receive packets from the one or more trackable device and to pass information derived from receipt of the packets to the positioning server apparatus 13. The positioning server apparatus 13 then uses this information to determine locations of the trackable devices 10 from which packets are received.
  • the locator devices 12 may be high-accuracy locator devices 12 which are configured to derive information or data from receipt of a certain type of packet (known as a positioning packet) which enables a bearing from the trackable device 10 to the locator device 12 to be determined.
  • the high-accuracy locator devices 12 (a schematic example of which is shown in Figure 6B) may include a phased array of antennas 120.
  • the antennas of the array 120 are connected to transceiver circuitry 121 via a switch mechanism 122 which is configured to connect only one of the antennas to the transceiver circuitry 121 at any one time.
  • the bearing to the trackable device 10 is determinable based on data derived from the receipt of a specific data portion of the positioning packet as the switch mechanism 122 sequentially connects a different one of the antennas to the transceiver circuitry 121.
  • the data derived from the receipt of the data packet may, in some specific examples, include I and Q data.
  • the locator device 12 further includes a controller 123 for controlling the other components of the device 12 in the manner discussed above and for providing various functionalities as discussed below.
  • the controller 123 may cause data, derived from receipt of data packets from the trackable device 10, to be provided to the positioning server 13.
  • the data is provided to the positioning server apparatus 13 via an I/O interface 124 which may be configured to transfer data using any suitable wired or wireless protocol.
  • the high-accuracy locator devices 12 may be referred to as HAIP (high accuracy indoor positioning) locator devices.
  • HAIP high accuracy indoor positioning locator devices.
  • HAIP as developed by Nokia is known in the art. Indeed, it is mentioned, and is described in various levels of detail, in (among other publications) the following published PCT patent applications: WO 2014087196A, WO2013179195A, WO2014087198A, WO 2015013904A, WO 2014107869A, WO2014108753A,
  • the one or more trackable devices 10 may be electronic tags or a more complex device such as a personal computing/communications device (such as, but not limited to, a mobile phone, a tablet computer or a wearable computing device such as a smart watch).
  • the one or more trackable devices 10 may be of various different types, with some or all of the devices 10 providing the functionality described herein.
  • Figure 6C is a simplified schematic of various components of an example of a trackable device 10.
  • the trackable device 10 comprises at least a controller 100 and transceiver circuitry 101.
  • the controller 100 controls the signals from a trackable device.
  • the trackable devices 10 may be associated with an asset (e.g. carried by a user or attached to an object) and/or a location (e.g. installed at a fixed location).
  • the trackable devices 10, the intermediary devices 11 and the locator devices 12 may be configured to communicate using any suitable wireless transmission protocol.
  • the transceivers 101, 112, 121 of the devices 10, 11, 12 may each be configured, under the control of respective controllers, to communicate via a Bluetooth transmission protocol.
  • the transceivers 101, 112, 121 may be configured to transmit and/or receive data packets (including data packets for enabling position determination and timing control packets) using a Bluetooth Low Energy protocol, as described in or compatible with the current version of the Core Bluetooth specification (Version 4.2).
  • a Bluetooth Low Energy protocol as described in or compatible with the current version of the Core Bluetooth specification (Version 4.2).
  • at least some of the devices 10, 11, 12 may also or additionally be configured to communicate using another suitable protocol.
  • Such protocols may include but are not limited to 802.11 wireless local area network protocols, other types of Bluetooth protocol or IEEE 802.15.4 protocols.
  • Figure 2 is a flow chart illustrating examples of various operations which may be performed by the positioning server apparatus 13 of Figure 1.
  • the positioning server apparatus 13 receives information derived from receipt of packets transmitted by one or more trackable devices 10 within the managed area A, B.
  • the information may in some examples be received from the intermediary device 11.
  • packets transmitted by the trackable device 10 may be received by the locator devices 12 with the derived information being routed to the positioning server apparatus 13 via the intermediary device 11 or, alternatively, directly from the locator device 12.
  • some information may be received from the intermediary device 11, while other information may be received from one or more locator device 12.
  • the positioning server apparatus 13 identifies one or more communication devices within the managed area to which a timing control packet is to be sent. This may be based on a number of considerations some of which discussed in reference to this figure while others are discussed with reference to other figures. As an example, trackable devices 10 within the area to which trackable device timing control packets are to be sent may be identified based on device IDs which are present in the received information. In addition, the trackable devices 10 may, in some examples, be identified based on a consideration as to whether the trackable device is already associated with, or synchronised with other devices in, the area A, B.
  • the positioning server apparatus 13 may identify the devices as one to which a timing control packet should be sent.
  • Locator devices 12 to which the timing control packets should be sent may be identified based on the managed area in which the trackable devices 10 are currently present. As such, locator devices 12 associated with that managed area may be identified as recipients of a timing control packet. Alternatively, if the positioning server apparatus 13
  • the locator devices 12 in that area may be identified as candidates for receiving a sleep mode initiation packet.
  • the positioning server apparatus determines the new timing parameters for the timing control packets. This may be based on a number of considerations, some examples of which are described here and with other examples being described elsewhere in the specification. Other examples will be apparent to the skilled person from reading the specification.
  • the new timing parameters for trackable devices 10 may, for example, be determined such that transmissions from two trackable devices 10 within an area do not collide. In some examples in which trackable devices 10 communicate with one another, the timing parameters may be determined such that a reception window (or listening slot) of one trackable device 10 corresponds with a transmission window (or slot) of another device 10.
  • the new timing parameters for locator device reception synchronisation packets may be determined, for instance, such that the recipient locator device 12 has a reception window that coincides with a transmission window of each trackable device 10 within the managed area.
  • the timing parameters for reception windows for receiving control packets may, for example, be selected based on information stored in a database. Alternatively, the timing parameters may be pre-programmed into the locator devices 12 and may be employed in response to receipt of a respective one of the packets. For upload timing control packets, the timing parameters may be determined based on an assessment of the requirements of the trackable devices 10 within the area (e.g. based on types or priorities of the trackable devices 10). For instance, if the trackable devices 10 are of a type which requires low latency, timing parameters for ensuring regular uploading of data from the locator devices 12 may be selected. If, however, the trackable devices 10 are such that high latency is suitable, timing parameters for ensuring less frequent uploading of data may be selected.
  • the positioning server apparatus 13 After preparing one or more timing parameters for a timing control packet, in operation S2.4, the positioning server apparatus 13 causes the intermediary device 11 to transmit timing control packets including the selected timing parameters as part of timing control information to be transmitted to the identified communication devices 10, 12 in the managed area A.
  • the positioning server apparatus 13 may cause the intermediary device 11 to transmit the timing control packets by sending a command or instruction message, which includes information for formulating the relevant control packet.
  • the trackable device timing control packets may include the Area ID in addition to the timing parameters and the trackable device may respond to receipt of the control packet by updating the area ID field in the packets it transmits.
  • the positioning server apparatus 13 is able to determine whether or not a trackable device 10 from which a packet is received is already associated with the area.
  • the positioning server apparatus 13 may cause a trackable device timing control packet and one or more locator device timing control packets to be transmitted by the intermediary device 11. For instance, the positioning server apparatus 13 may cause a trackable device timing control packet including an Area ID to be transmitted to a trackable device 10. Subsequently, the positioning server apparatus may cause transmission of a locator device timing control packet for synchronising a reception slot of one or more locator devices 12 in the area with a transmission slot of trackable device 10 as allocated in the trackable device control packet. However, in some examples, the subsequent transmission of the locator device timing control packet may be conditional upon receipt by the positioning server apparatus 13 of an indication that the trackable device has adapted its timing parameters as instructed in the timing control packet.
  • the positioning server apparatus 13 may respond by causing the intermediary device 11 to transmit a locator device timing control packet to at least one locator 12 in the managed area A to cause the at least one locator device 21 to adapt a timing of reception window to coincide with the transmission slot of the trackable device 10. If it is determined (e.g.
  • the positioning server apparatus 13 may respond by causing the trackable device timing control packet to be re-sent by the intermediary device 11.
  • the intermediary device 11 may respond by causing the trackable device timing control packet to be re-sent by the intermediary device 11.
  • more than one different control packet may be transmitted to a particular device.
  • a locator device 12 may receive both a reception synchronisation packet and an upload timing packet.
  • the timing control information from the two packets may be combined into a single timing control packet.
  • the operations S2.2, S2.3 and S2.4 may be referred to as operations for managing operation of wireless communication devices within the managed area A, B.
  • the devices 10, 11, 12 within the area may communicate in accordance with the new timing parameters to enable the positioning server apparatus 13 to determine positions of the trackable devices 10 within the managed area.
  • the positioning server apparatus 13 may receive information, uploaded from the locator devices 12 in accordance with any upload timing control packets, which is derived from receipt of packets from the trackable devices 10 within the area.
  • the positioning server apparatus determines the location of the trackable devices within the area A, B based on the received information.
  • the determined positions may then be used for any number of different applications. Indeed, the determined positions may be passed to an application server, which provides particular services using the positions of the trackable devices 10.
  • operations S2.5 and S2.6 may not be performed by the positioning server 13 immediately following operation S2.4. Instead, various other operations may be performed, after which the positioning server apparatus 13 may return to operation S2.1. Examples of such operations are illustrated in the flow chart of Figure 3, which starts with operation S2.4A in which a locator device timing control packet, specifically a sleep mode initiation packet, is caused to be transmitted from the intermediary device 11 to the locator device 12 in the managed area, for instance the first managed area A of Figure 1.
  • operation S2.4B the positioning server apparatus 13 determines that, in addition to no trackable device being in the first managed area A, no trackable devices 12 are present in a neighbouring area, for instance the second managed area B of Figure 1. This
  • determination may be based on a recognition that an intermediary device 11 and/or any locator devices 12 in the neighbouring area have not received packets transmitted by any trackable devices for longer than a predetermined duration.
  • the positioning server apparatus 12 In response to determining that no trackable devices 12 are present in a neighbouring area B, the positioning server apparatus 12, in operation S2.4C causes a sleep mode adjustment packet to be transmitted by the intermediary device 11A in the first managed area A to the locator devices 12A in that area A.
  • the sleep mode adjustment packet includes, in this instance, timing control information for causing the locator device 12A to increase the interval between reception windows during which it listens for incoming timing control packets.
  • the positioning server apparatus 13 may, prior to causing transmission of the sleep mode adjustment packet, determine the new timing parameters for inclusion in the packet.
  • This may be determined for instance, based on a time since a trackable device was last detected in the neighbouring area B and/or based on the presence or otherwise of trackable devices in more remote managed areas (e.g. areas adjoining the neighbouring area but not the first managed area). As such, if no devices are present in neighbours of the neighbouring area, the interval between reception windows, during which the locator device listens for incoming timing control packets, may be longer than the interval that is used if devices are detected as being present in an area that adjoins the neighbouring area.
  • the positioning server apparatus 13 receives information indicative of a trackable device 10 being in the neighbouring area B, for instance from the intermediary device 11B of the neighbouring area B. This is an indicator that the trackable device 10 may soon be entering the first managed area A.
  • the positioning server apparatus 13 causes the intermediary device in the first area A to transmit another sleep mode adjustment packet to the locator devices 12A in the first area A.
  • This is transmitted at a time which corresponds with one of the reception windows, the time and/or interval between which are defined by the sleep mode adjustment packet previously caused to be transmitted in operation S2.4C.
  • the sleep mode adjustment packet includes control information for causing the locator devices to reduce the interval between reception windows. In this way, the locator devices 12A in the first area A can be brought out of sleep mode more quickly if/when necessary.
  • the positioning server apparatus 13 determines that a trackable device 10 has entered the first area A. This is determined in response to information received from the intermediary device 11A which indicates that packets transmitted by the trackable device 10 have been received by the intermediary device 11A. In some instances, packets transmitted by trackable devices 10 may be received by the intermediary device 11A even when the trackable device 10 is not in its area. In this case, the positioning server apparatus may determine whether the trackable device is truly in the first area based on a consideration of information indicative of the signal strength of the received packet which is measured by the intermediary device 11A.
  • the positioning server apparatus causes a wake-up packet to be transmitted by the intermediary device 11A to the locator devices 12A in the first area A during a reception window.
  • the locator devices 12A respond to this by exiting sleep mode and once again listening for incoming packets (e.g. positioning packets) from the trackable devices 10.
  • the positioning server apparatus 13 may return to operation S2.2 in which the locator devices 12A and/or the trackable device 10A are identified as recipients for timing control packets (e.g. to synchronise transmission windows of the trackable devices 10 with reception windows of the locator devices 12A).
  • the intermediary devices 11 are shown in the centre of their respective managed area. While this may be beneficial when the intermediary device 11 is controlled so as to keep devices within the area time-synchronised, the intermediary device may alternatively be close to an entrance or outside the managed area. In such examples, the intermediary device may act as a simple gatekeeper only, for instance, to give the positioning server advanced warning of trackable devices approaching the managed area. The positioning server apparatus 13 may respond to this advanced warning by, for instance, waking up the locator devices in the area.
  • the first implementation is described with reference two managed areas A and B, each of which include at least one intermediary device 11 as well as at least one high accuracy locator device 12.
  • the intermediary devices 11 may be mains-powered. However, in contrast to the high accuracy locator devices 12 which require accurate placement, their placement is flexible and as such their installation is inexpensive. For instance, the intermediary devices 11 may be placed near or even in a mains power socket.
  • the intermediary devices 11 each maintain a master clock and keep the locator devices 12 and trackable devices 10 in their area time-synchronized by sending out packets (e.g. advertisement packets) with time information (e.g. in the form of a timestamp). These packets may be referred to as time-synchronization packets (or messages) and they may be transmitted repeatedly by the intermediary device 11 to ensure that the devices in the managed area remain time-synchronized (and do not suffer the effects of timing drift etc.). As such, the devices 10, 12 in the area may update their internal clock based on the received time-synchronization packets.
  • the time-synchronization packets may include information for identifying the intermediary device 11 (e.g. a device ID) from which the packet originates and/ or for identifying the managed area (e.g. an Area ID).
  • the intermediary device 11 may use knowledge of the trackable devices' 10 and locator devices' 12 receive timeslot to send the time-synchronization packets.
  • the information identifying the receive timeslots of the devices in the area may be stored by the intermediary device when the intermediary device receives timing control instructions from the positioning server apparatus.
  • the intermediary device 11 may send time-synchronization packets to trackable devices 10 immediately after receiving a packet from the trackable device 10 (this assumes that the trackable devices 10 always provides a reception window for a short while after sending a packet).
  • the managed area may include plural intermediary devices 11 (e.g. because it is large in size). In such examples, only one of the intermediary devices
  • the plural intermediary devices 11 in the managed area may be installed within range of each other so that they can synchronize their clocks from the master clock based on a time indicated in packets transmitted by the intermediary device 11 which maintains the master clock.
  • the other intermediary devices 11 in the managed area then repeat the time synchronization packets, in some instances with an adjustment to account for their processing latency.
  • a trackable device 10 or high accuracy locator 12 may receive several time synchronization packets each indicating a slightly different time. If this occurs, the time in the packet indicating the earliest time may be used by the devices 10, 12.
  • advertisement packets may be particularly well-suited for broadcasting time information as the latency associated with such packets is small.
  • a trackable device 10 transmits a positioning packet (which may include the specific portion for enabling determination of the bearing to the trackable device 10).
  • a positioning packet (which may include the specific portion for enabling determination of the bearing to the trackable device 10).
  • the intermediary device 11B in the second area B As the trackable device 10 is in the second area B, this is detected by the intermediary device 11B in the second area B.
  • the trackable device has entered the second area B from the first area and, as such, the Area ID in the positioning packet identifies the first area A.
  • the intermediary device 11B in the second area B receives the positioning packet and in operation S4.2 provides a message including information derived from receipt of the positioning packet to the positioning server apparatus 13, for instance using a Wi-Fi protocol.
  • the information provided to the positioning server apparatus 13 includes the Area ID as well as signal strength indication associated with receipt of the positioning packet, which was determined by the intermediary device 11B.
  • the information additionally includes the device ID of the trackable device 10 which was included in the positioning packet.
  • the information may also include a type ID which was included in the received positioning packet.
  • the positioning server apparatus 13 determines based on the area ID whether the trackable device 10 is already associated the current managed area. In this instance, as the area ID does not correspond to that of the intermediary device 11B from which the message was received, the positioning server apparatus 13 determines that the trackable device is not associated with the current managed area (i.e. the trackable device is newly- arrived in the area).
  • the positioning server apparatus 13 uses the signal strength indication (e.g. an RSSI value) in those messages to determine the managed area with which the trackable device 10 should be associated.
  • signal strength indication e.g. an RSSI value
  • hysteresis e.g. different RSSI thresholds for leaving and entering a managed area
  • minimum times before managed area switching is allowed may be used to prevent the association of trackable devices 10 from thrashing between managed areas.
  • the positioning server apparatus 13 determines the new timing parameters for the trackable device 10.
  • the interval between transmission slots may be determined based on a type associated with the trackable device 10. This may be determined based on the Type ID included in message of operation S4.2 or based on querying a database using the device ID included in the message.
  • the start time of a transmission slot for the trackable device 10 may be selected so as not to coincide with that of other trackable devices 10 already in the area.
  • the positioning server apparatus 13 may thus maintain a record of the trackable devices 10, and their timing parameters, that are currently present in a particular managed area.
  • Timeslots allocated to devices in different managed areas may be the same. However, the master clocks in each managed area may be different. As such, in the event that the packets transmitted by trackable devices can be detected in multiple managed areas, the difference in master clocks ensures that collisions with transmissions by devices in different areas are unlikely.
  • the positioning server apparatus sends to the intermediary device 11, in operation S4.3, a control packet instruction.
  • the control packet instruction includes the new timing parameters, an indication of the new Area ID, and indicates the device ID of the trackable device 10 to which the instruction relates.
  • the intermediary device 11 in operation S4.5 sends a trackable device timing control packet to the trackable device 10.
  • the trackable device timing control packet is transmitted during the device's next window, which may immediately follow the transmission of another positioning packet (which is shown by the dashed arrow labelled S4.4).
  • the trackable device timing control packet includes at least the new timing parameters, which indicate transmit and receive timeslots that should be used while in this managed area, and an instruction to update the Area ID.
  • the trackable device control packet may additionally include the time information (e.g. a timestamp) derived from the master clock maintained by the intermediary device 11.
  • the trackable device control packet may in some examples also perform the function of the time-synchronization packet. This enables the trackable device 10 to synchronize its timing with the other devices in the managed area.
  • the time-synchronization packets may be sent independently of the trackable device control packets.
  • the trackable device 10 Upon receiving the timing control packet, the trackable device 10 updates its timing parameters in accordance with the timing control packet. In addition, it also updates the Area ID field in future packets, thereby to indicate that it is now associated with the different managed area.
  • each trackable device 10 may be associated with at most one managed area.
  • the trackable device 10 may be configured so as to only synchronize its timing on the basis of the master clock maintained by the intermediary device located in the managed area with which the device is currently associated.
  • the trackable devices may be configured to ignore time-synchronization packets which are received from intermediary devices which are not associated with the managed area with which the trackable device is currently associated.
  • An exception to this may be when the time information derived from the master clock (e.g. the time stamp) is received as part of a trackable device control packet, in which case the trackable device 10 may update its area ID and synchronize its clock based on the time information included in the trackable device control packet.
  • the trackable device 10 may be configured to remove its current Area ID association if it does not receive time-synchronization packets from the intermediary device 11 in that area for a certain time.
  • the positioning server apparatus 13 may also or alternatively be configured to send a message to the trackable device 10 via the intermediary device 11 which instructs the trackable device 10 to disassociate itself from the current managed area (e.g. by removing the Area ID from the relevant field in the packets it transmits). This may occur for instance if the positioning server apparatus 13 repeatedly, for a certain duration, receives messages, including information derived from positioning packets transmitted by the trackable device, from intermediary devices which are not associated with any managed area.
  • the positioning server apparatus 13 may send an instruction to the intermediary device 11 of that area.
  • the intermediary device 11 may send a timing control instruction to the locator devices 12 of that area to deallocate the reception timeslots for the trackable device 10 that has been disassociated from the managed area. This is similar to operations S4.10 and S4.11 described below.
  • the trackable device 10 transmits, in operation S4.6, a positioning packet in accordance with the updated timing parameters and including the Area ID of the current managed area.
  • the trackable device may ignore the updated timing parameters when transmitting its next positioning packet and may instead transmit it immediately. In such examples, subsequent positioning packets are transmitted in accordance with the received timing parameters.
  • the positioning packet including the updated Area ID is received by the intermediary device 11B in the second managed area B which then sends a corresponding message to the positioning server apparatus 13 in operation S4.7.
  • the positioning server apparatus 13 determines locator device reception synchronization timing parameters for the locator devices 12B in the second managed area B.
  • the locator device reception synchronization timing parameters are determined (e.g. by referring to the record of trackable devices currently associated with the area) such that a reception window of the locator devices 12B in the second managed area B coincides with the transmission window of the trackable device 10.
  • the locator devices 12B may be configured so as not to receive (or to ignore) incoming packets that are received outside an allocated reception timeslot.
  • the positioning server apparatus 13 sends a control packet instruction to the intermediary device 11 for causing the intermediary device 11 to send a reception synchronization control packet to the locator devices 12B in the second managed area B.
  • Both the control packet instruction and the reception synchronization control packet include the previously-determined locator device timing parameters. If the message received in operation S4.7 does not include the updated Area ID, the positioning server apparatus 13 may cause the intermediary device 11B to resend the timing control packet (as transmitted in operation S4.5) to the trackable device 10. Once it is determined that the timing parameters have been updated by the trackable device 10 (e.g.
  • the positioning server apparatus 13 sends a control packet instruction to the intermediary device 11A of the managed area A with which the trackable device 10 was previously associated. This can be seen in operation S4.10.
  • This instruction causes the intermediary device 11A to send (in operation S4.11) a timing control packet to its locator devices 12A to cause them to remove the remove the reception timeslots which are allocated to the trackable device 10 which is no longer associated with their area.
  • the trackable device 10 transmits positioning packets which are received by the locator devices 12B of the second area in the timeslots allocated to that device. This may be repeated a number of times.
  • the data/information derived from receipt of these positioning packets may be stored by the locator devices 12B until an allocated timeslot for upload of the data arrives.
  • allocated upload timeslot arrives, the data stored by the locator device 12B is forwarded to the positioning server apparatus 13.
  • the uploading of stored data may, for instance, be performed via Wi-Fi (or a similar communication protocol) or a Bluetooth protocol.
  • Wi-Fi may be beneficial in that is has high bandwidth, but it also has higher power consumption.
  • Bluetooth may be beneficial in that has lower power consumption, but it also has lower bandwidth. From an energy consumption perspective, using Wi-Fi may be more appropriate, for instance, when the interval between uploads is long and/ or when the area is particularly congested with trackable devices 10 and so there is a large quantity of data to upload.
  • the data may be sent directly to the positioning server apparatus from the locator devices 12.
  • the data may be sent to the positioning server apparatus via the intermediary device 11.
  • the data may be uploaded outside the allocated reception windows during which the locator devices 12 are listening for positioning packets from trackable devices 10, in order to reduce the chance of collisions.
  • a different radio channel may be used to upload the data.
  • the locator devices 12 forward the stored data to the intermediary device 11 operation S4.13, which then forwards the data to the positioning server apparatus 13 in operation S4.14. Upload Interval Adjustment
  • the positioning server apparatus 13 In addition to causing transmission of locator device reception synchronisation packets for controlling the timing of reception windows, the positioning server apparatus 13 also causes transmission of upload timing control packets to the locator devices 12. These may be sent to the locator devices 12 at the same time as the locator device reception synchronisation packet.
  • the locator device reception synchronisation packets may additionally include the upload timing parameters based on which the locator devices 12 adapt the timing of transmission windows during which they upload data.
  • the upload timing control packets may be transmitted at a different time to the locator device reception synchronisation packets.
  • the upload timing parameters may be dependent on the application for which the positioning data of the trackable devices 10 is being used. For some applications, high latency may be acceptable whereas for other is may not be suitable. In addition, a different latency may be determined on a device-by-device basis.
  • Positioning frequency (which is set by the interval between transmission windows during which positioning packets are transmitted by the trackable devices) and positioning latency (which is set by, among other things, interval between data upload windows) are separate consideration. For instance, for some trackable devices 10 very frequent positioning data may be required, but if the data is only used for offline data analysis, the latency may not matter. For these devices, the locator devices 12 may buffer the data for a considerable time before uploading it (i.e. the interval between uploads may be a relatively long time). As described above, use of Wi-Fi or a similar protocol may be appropriate. In other scenarios in which low latency positioning is required, the locator devices 12 may be controlled to upload the stored data with high frequency (i.e. with a relatively low interval).
  • the use of Bluetooth to send the data via the intermediary device 11 may be appropriate.
  • the upload frequency may be lower than the required positioning frequency, and as such the locator devices 12 may still buffer the data for a short time before uploading it.
  • the positioning server apparatus 13 may dynamically adjust the upload frequency of the locator devices 12 depending on the trackable devices that are in the managed area. As such, the positioning server apparatus 13 may cause the intermediary device 11 to send new upload timing parameters when the set of trackable devices in the area changes.
  • the locator devices 12 can conserve power. This is because it is typically more power-efficient to send a given amount of data in a single burst than it would be to send it in many parts (e.g. there is typically some energy overhead associated with switching the radio components on and off). Sleep Mode
  • the positioning server apparatus may use the intermediary device 11 to set the locator devices 12 into sleep mode 13.
  • the locator devices 12 may wake up briefly every now and then, for instance, once per second (or even less if the assets with which the trackable devices 10 are associated do not move quickly) to listen for wake-up control packets.
  • the locator devices 12 may be powered up just enough to be able to receive the packet and identify it as a wake-up control packet. Full power-up of the locator devices 12 may only occur only once a wake- up control packet is received.
  • frequency of reception timeslots (the listening frequency) in the sleep mode may be adjusted using a sleep mode adjustment packet, depending on how close the nearest trackable device is. For example, when a floor of a facility is completely empty, the locator devices in a particular managed area (which might incorporate the entire floor) may be controlled to listen for wake-up control signals every ten seconds.
  • the positioning server apparatus 13 may cause the locator devices 12 in the managed areas to be sent (during their next listening timeslot) a sleep mode adjustment packet which instructs them to adapt the interval between reception timeslots, such that they occur once per second. In this way, they can be quickly woken up if the trackable device approaches. Conversely, once the trackable device leaves the area again, the locator devices in the area may be sent a sleep mode adjustment packet which instructs them to adjust the frequency of reception slots to the lower value (e.g. once every ten seconds again).
  • locator devices 12 are able to save even more power e.g. during night time when there is nothing to observe, while maintaining the ability to accurately position, for instance, a night guard that walks through each floor occasionally when required.
  • a trackable device 10 having left an area may be detected either when an intermediary device 11 in another distant area, e.g. a different floor, detects it or when the trackable device is not detected 10 by any locator device 12 or intermediary device 11 for a certain duration.
  • the positioning system 1 described herein is such that the energy consumption of the locator devices 12 now depends to a large extent on movement of trackable devices 10 throughout the environment covered by the positioning system. As such, locator devices 12 may require a change in battery at varying times which are difficult to predict.
  • the locator devices 12 may be configured to monitor their battery levels and to send battery level information to the positioning server apparatus 13, either directly or via their intermediary device 11.
  • the positioning server apparatus 13 determines an optimal time for a battery change operation, such that the batteries of multiple locator devices 12 may be changed at the same time, the positioning server apparatus 13 triggers a battery change alert which identifies the locator devices 12 that require new batteries.
  • the positioning server apparatus 13 may utilize knowledge of the locations of the locator devices 12 that require a battery change as well as the floorplan of the environment to provide a recommended route for performing the battery change operation which minimizes the distance that must be travelled.
  • Example Implementation 2 The second example implementation is described with reference to a single managed area A including at least one intermediary device 11 but in some examples no high accuracy locator devices 12.
  • the positioning server apparatus 13 uses the intermediary device 11 to synchronise transmission and reception slots of two or more trackable devices 10 within the managed area. Following this synchronisation, the positioning server apparatus 13 is able to determine when two or more trackable devices 10 are in proximity to one another, without requiring locator devices 12 to be present in the managed area.
  • Examples in accordance with this implementation may be beneficial in scenarios in which accurate location determination of an asset carrying a trackable device 10 is not particularly important, but instead proximity of the trackable device 10 to either a fixed location (in which a static trackable device, e.g. a cheap "tag", may be positioned) or to another asset.
  • a static trackable device e.g. a cheap "tag”
  • proximity detection between trackable devices may be useful in order to track which staff member is using a certain piece of equipment.
  • the intermediary device 11 is a low- value, mains powered device which may be configured to listen constantly for trackable devices 10 which are present in the managed area.
  • a packet (which may be an advertising packet) is transmitted by a first trackable device 10 in the area.
  • This is received by the intermediary device 11, which in operation S5.2 forwards a message including information derived from the receipt of the packet to the positioning server apparatus 13.
  • This information may include at least the trackable device ID and an indication of the signal strength (e.g. RSSI).
  • the information forwarded to the positioning server apparatus 13 may include the contents of the packet. As such, it may include other information (e.g. device type, priority, sensor data etc.) in addition to device ID and RSSI value.
  • a second tag in the area transmits a packet which is received by the intermediary device 11.
  • the intermediary device 11 forwards a message (including e.g. device ID and RSSI) to the positioning server apparatus 13 in operation S54.
  • the positioning server apparatus 13 determines whether the trackable devices 10 are potentially in proximity using conventional, (e.g. fingerprint or radio-map based) positioning. If the trackable devices 10 are determined to be in potentially in proximity, the positioning server apparatus 13 determines whether an occurrence of proximity between the two trackable devices 10 is of interest. The positioning server apparatus 13 may determine whether an occurrence of proximity between the two devices is of interest (and so whether subsequent transmission of trackable device timing control packets for synchronising the devices is required), based on a device identifier and/or a device type of each of the first and second trackable devices. A potential proximity event may be considered interesting, for instance, if there is an action to be performed if the trackable devices 10 are determined to be in proximity.
  • conventional, (e.g. fingerprint or radio-map based) positioning e.g. fingerprint or radio-map based) positioning. If the trackable devices 10 are determined to be in potentially in proximity, the positioning server apparatus 13 determines whether an occurrence of proximity between the two trackable devices 10 is of interest. The positioning server
  • the proximity measurements by the trackable devices 10 may be caused to be performed when a trackable device 10 associated with a doctor is potentially in proximity with a trackable device io associated with a patient.
  • the proximity measurements may not be performed when the potential proximity is between trackable devices, which are both associated with a doctor or both associated with a patient.
  • the positioning server apparatus 13 may also include one or more pre-defined geofences or other conditions (e.g. based on time) that limit when a certain kind of proximity event between devices is interesting. For example, it may be defined that a doctor-patient proximity event is interesting when it happens in hospital ward, but not when it occurs in a hallway or in a cafeteria. Similarly, it may be defined that a doctor-patient proximity event is interesting only during the doctor's working hours.
  • the intermediary device 11 is then used to synchronize the trackable devices 10. Synchronisation of the trackable devices 10 is performed in response to receipt in operation S5.6 of a trackable device control packet instruction by the intermediary device 10 from the positioning server apparatus 13. This instruction may include the timing parameters for the trackable devices.
  • One requirement for being potentially in proximity may be that all trackable devices 10 are within range of the same intermediary device 11 (the range in some examples may define the managed area). As such, it could be said that positioning server apparatus 13 causes the intermediary device 11 to transmit the trackable device timing control packet in response to receiving an indication that at least two trackable devices 10 are located within the managed area.
  • the intermediary device 11 waits for each trackable device to transmit a packet (in operations S5.7 and S5.10) and uses the subsequent reception window (that ordinarily is provided by the trackable devices after a transmission) to send the trackable device a timing control packet (in operations S5.8 and S5.11).
  • the positioning server apparatus 13 causes the intermediary device 11 to transmit the trackable device timing control packet to the first of the trackable devices 10 in the managed area.
  • the positioning server apparatus 13 may cause the intermediary device 11 to transmit the trackable device timing control packet to the second of the trackable devices 10 in the managed area
  • the timing control packet instructs the recipient trackable device 10 when to send future packets (i.e. when to provide transmission slots) and when to listen for them (i.e. when to provide reception slots) such that the recipient trackable device 10 adapts at least one timing parameter such that the transmission window of the recipient device io during which a packet is transmitted coincides with the reception window of another device in the area and/or the reception window of the recipient trackable device coincides with the transmission window of the other trackable device io.
  • the timing control packet may, in this implementation also instruct the recipient trackable device as to when to listen (i.e. provide a reception slot) for a future control packet (which may be termed "a start indication packet" or "a process initiation control message" that signifies that the proximity determination process should be started.
  • a future control packet which may be termed "a start indication packet” or "a process initiation control message"
  • the time of the reception slot for receiving a start indication packet may be the same for both (or all trackable devices 10).
  • the intermediary device 11 sends the timing control packet to all the tags, and the propagation and processing delays are negligible, the timing can be set with great accuracy.
  • the intermediary device 11 may not be configured to maintain a master clock. However, in other examples, the intermediary device 11 may maintain the master clock and may include e.g. a time stamp in the timing control packets it sends to the trackable devices 20.
  • the intermediary device 11 transmits the start indication packet in operation S5.13.
  • This start indication packet is transmitted at the time indicated in the timing control packet transmitted previously. All timings indicated in the timing control packets may be interpreted relative to the receive time of the start indication packet.
  • the first and second trackable devices may carry out the adaptation of the at least one timing parameter indicated by the respective one of the trackable device timing control packets and may operate in accordance with the updated parameters.
  • each trackable device 10 transmits a packet during the transmission timeslot it was allocated in the timing control packet (see operations S5.14 and S5.16).
  • the packets transmitted in operations S5.14 and S5.16 may include data to indicate that the packet is one for which the indication of signal strength should be provided to the intermediary device 11.
  • Such packets may be referred to as measurement packets.
  • the use of measurement packets allows the trackable devices 10 to only send signal strength information to the intermediary device 11 for received measurements packets (and not for packets having other purposes). This prevents the trackable devices 10 from sending signal strength information for all packets received during a particular time period.
  • this effect may be provided by the trackable device control packet (as transmitted by the intermediary device n in operations S5.8 and S5.11) carrying information indicating which devices are participating in the proximity measurement.
  • the trackable device 10 can be configured so as to only send signal strength information to the intermediary device 11 for those packets received from one of the participating devices.
  • the packets transmitted in operations S5.14 and S5.16 may also include the device ID of the sending device. This may be beneficial particularly when the device ID is not the same as the Bluetooth address of the sending device.
  • Each of the other trackable devices 10 listens for the transmitted packet at the time of a reception window indicated in the timing control packet. Each of the other trackable devices 10 then measures the signal strength of the received packet and determines a value of this (e.g. an RSSI value). In some examples, the trackable devices 10 may send their packets multiple times using different frequencies. This may reduce the effect of interference.
  • a value of this e.g. an RSSI value
  • the intermediary device 11 may also measure the signal strength of the packet and may send an indication of this (see operations S5.15 and S5.17) to the positioning server apparatus 13, which may use it for conventional (e.g. fingerprint-based) positioning in operation S5.18.
  • each trackable device 10 reports the observed signal strength indication in a message to the intermediary device 11 (in operations S5.19 and S5.22).
  • the message additionally includes the device ID of the trackable device 10 by which the packet was transmitted.
  • the intermediary device 11 then forwards the signal strength indication to the positioning server apparatus 13 (in operations S5.21 and S5.24).
  • the intermediary device may acknowledge receipt of the signal strength message from the trackable devices 10 (see operations S5.20 and S5.23).
  • the positioning server apparatus 13 determines the proximity between the trackable devices (or put another way, evaluates the distance between the trackable devices 10). If a preconfigured proximity threshold between two trackable devices 10 is exceeded, the positioning server apparatus may trigger, for instance, a proximity alert or any other functionality which the positioning server apparatus 13 is configured to activate when it is determined that the trackable devices are in proximity with one another.
  • the management of devices within an area in accordance with the second example implementation enables a determination as to when two devices are in proximity with one another without requiring a, relatively expensive, locator device to be installed throughout a facility. However, this may result in additional power consumption for the trackable devices 10.
  • the managed area may include one or more high accuracy locator devices 12 at locations in which a determination of proximity is most commonly required. As such, when the trackable devices 10 are in such locations, they may not need to take part in the proximity determination process as described with reference to Figure 5.
  • exciters may be utilised to reduce the amount of synchronization between trackable devices 10 and subsequent signal strength measurements.
  • An exciter is a device which emits a signal that does not pass through walls (e.g. based on infrared light or ultrasound).
  • an exciter may be installed in a room, which forms part of the managed area.
  • the ID of the exciter which may be used to identify the room, may be encoded into the signal emitted by the exciter.
  • a trackable device 10 receives such a signal, it transmits a packet which includes the exciter ID to the intermediary device 11 which forwards this to the positioning server apparatus 13.
  • an exciter may be placed in a location in which proximity between devices often occurs. Based on the exciter ID detected and reports by the trackable devices 10, the positioning server apparatus 13 is able to determine when two or more trackable devices 10 are
  • the positioning server apparatus may activate the proximity measurement process.
  • the positioning server apparatus 13 may directly trigger a proximity alert (or some other functionality that should be activated when the trackable devices are in proximity) when it is determined that two or more trackable devices 10 are simultaneously receiving the exciter signal.
  • first and second example implementations have been described separately it will be appreciated that they are not exclusive of one another.
  • the proximity measurement process of the second example implementation may be utilised in
  • the management of an area of a positioning system by a positioning server apparatus 13 using a low cost, mains-powered intermediary device 11 may provide many benefits. These may include reduced energy consumption (for instance by synchronising devices with one another so that they can be active only when required and/or reducing the need for use of high accuracy locators) and increased reliability (for instance, by reducing collisions). Another benefit that may be derived is a reduction in network traffic when the managed areas (or at least some devices within those areas) are not active all the time. This additional bandwidth may be useful in, for instance, hospitals in which medical data may need to be sent wirelessly for analysis and monitoring and may even be streamed in real time.
  • the controllers 100, 113, 123, 130 of each of the apparatuses or devices 10, 11, 12, 13 comprise processing circuitry 1001, 1131, 1231, 1301 communicatively coupled with memory 1002, 1132, 1232, 1302.
  • the memory 1002, 1132, 1232, 1302 has computer readable instructions 1002A, 1132A, 1232A, 1302A stored thereon, which when executed by the processing circuitry 1001, 1131, 1231, 1301 causes the processing circuitry 1001, 1131, 1231, 1301 to cause performance of various ones of the operations described with reference to Figures 1 to 3.
  • the controllers 100, 113, 123, 130 may in some instance be referred to, in general terms, as "apparatus".
  • the processing circuitry 1001, 1131, 1231, 1301 of any of the apparatuses 10, 11, 12, 13 described with reference to Figures 1 to 6C may be of any suitable composition and may include one or more processors 1001A, 1131A, 1231A, 1301A of any suitable type or suitable combination of types.
  • the processing circuitry 1001, 1131, 1231, 1301 may be a programmable processor that interprets computer program instructions 1002A, 1132A, 1232A, 1302A and processes data.
  • the processing circuitry 1001, 1131, 1231, 1301 may include plural programmable processors.
  • the processing circuitry 1001, 1131, 1231, 1301 may be, for example, programmable hardware with embedded firmware.
  • the processing circuitry 1001, 1131, 1231, 1301 may be termed processing means.
  • the processing circuitry 1001, 1131, 1231, 1301 may alternatively or additionally include one or more Application Specific Integrated Circuits (ASICs).
  • ASICs Application Specific Integrated Circuits
  • processing circuitry 1001, 1131, 1231, 1301 may be referred to as computing apparatus.
  • the processing circuitry 1001, 1131, 1231, 1301 is coupled to the respective memory (or one or more storage devices) 1002, 1132, 1232, 1302 and is operable to read/write data to/from the memory 1002, 1132, 1232, 1302.
  • the memory 1002, 1132, 1232, 1302 may comprise a single memory unit or a plurality of memory units, upon which the computer readable instructions (or code) 1002A, 1132A, 1232A, 1302A is stored.
  • the memory 1002, 1132, 1232, 1302 may comprise both volatile memory 1002-2, 1132-2, 1232- 2, 1302-2 and non-volatile memory 1002-1, 1132-1, 1232-1, 1302-1.
  • the computer readable instructions 1002A, 1132A, 1232A, 1302A may be stored in the nonvolatile memory 1002-1, 1132-1, 1232-1, 1302-1 and may be executed by the processing circuitry 1001, 1131, 1231, 1301 using the volatile memory 1002-2, 1132-2, 1232-2, 1302-2 for temporary storage of data or data and instructions.
  • volatile memory include RAM, DRAM, and SDRAM etc.
  • non-volatile memory include ROM, PROM, EEPROM, flash memory, optical storage, magnetic storage, etc.
  • the memories in general may be referred to as non-transitory computer readable memory media.
  • the term 'memory' in addition to covering memory comprising both non-volatile memory and volatile memory, may also cover one or more volatile memories only, one or more non-volatile memories only, or one or more volatile memories and one or more nonvolatile memories.
  • the computer readable instructions 1002A, 1132A, 1232A, 1302A may be pre-programmed into the apparatuses 10, 11, 12, 13. Alternatively, the computer readable instructions 1002A, 1132A, 1232A, 1302A may arrive at the apparatus 10, 11, 12, 13 via an
  • the computer readable instructions 1002A, 1132A, 1232A, 1302A may provide the logic and routines that enables the devices/apparatuses 10, 11, 12, 13 to perform the functionality described above.
  • the combination of computer-readable instructions stored on memory may be referred to as a computer program product.
  • the Bluetooth Low Energy (BLE) capability of the apparatuses io, n, 12, 13 may be provided by a single integrated circuit. It may alternatively be provided by a set of integrated circuits (i.e. a chipset).
  • the BLE-capability may alternatively be a hardwired, application-specific integrated circuit (ASIC).
  • ASIC application-specific integrated circuit
  • the apparatuses 10, 11, 12, 13 described herein may include various hardware components which have may not been shown in the Figures.
  • the trackable device 10 may in some implementations be a portable computing device such as a mobile telephone or a tablet computer and so may contain components commonly included in a device of the specific type.
  • the apparatuses 10, 11, 12, 13 may comprise further optional software components which are not described in this
  • Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic.
  • the software, application logic and/ or hardware may reside on memory, or any computer media.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
  • a "memory" or “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • references to, where relevant, "computer-readable storage medium”, “computer program product”, “tangibly embodied computer program” etc., or a “processor” or “processing circuitry” etc. should be understood to encompass not only computers having differing architectures such as single/multi-processor architectures and sequencers/parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices and other devices.
  • References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device as instructions for a processor or configured or configuration settings for a fixed function device, gate array, programmable logic device, etc.
  • circuitry refers to all of the following: (a) hardware- only circuit implementations (such as implementations in only analogue and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé consistant à positionner un appareil de serveur gérant le fonctionnement d'au moins un dispositif de communication sans fil situé dans une zone gérée d'un système de positionnement en contraignant un paquet de commande de synchronisation à être transmis au ou aux dispositifs de communication sans fil par un dispositif intermédiaire situé dans la zone gérée, le paquet de commande de synchronisation étant configuré de sorte à contraindre le dispositif de communication sans fil destinataire à s'adapter à au moins un paramètre de synchronisation se rapportant à une fenêtre de réception et/ou à une fenêtre de transmission.
PCT/FI2015/050693 2015-10-14 2015-10-14 Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement WO2017064356A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/FI2015/050693 WO2017064356A1 (fr) 2015-10-14 2015-10-14 Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/FI2015/050693 WO2017064356A1 (fr) 2015-10-14 2015-10-14 Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement

Publications (1)

Publication Number Publication Date
WO2017064356A1 true WO2017064356A1 (fr) 2017-04-20

Family

ID=58517874

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2015/050693 WO2017064356A1 (fr) 2015-10-14 2015-10-14 Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement

Country Status (1)

Country Link
WO (1) WO2017064356A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10772057B1 (en) 2019-02-25 2020-09-08 Hong Kong Applied Science And Technology Research Institute Co., Ltd. Systems and methods for wireless device synchronization

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7974639B2 (en) * 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
WO2011085265A2 (fr) * 2010-01-08 2011-07-14 Qualcomm Incorporated Procédé et appareil de routage de messages d'un protocole de localisation dans un réseau sans fil
US20130321209A1 (en) * 2012-05-30 2013-12-05 Nokia Corporation Method, apparatus, and computer program product for high accuracy location determination
WO2014087196A1 (fr) * 2012-12-07 2014-06-12 Nokia Corporation Manipulation d'unités de données en paquets
US20140241257A1 (en) * 2013-02-26 2014-08-28 Qualcomm Incorporated Scalable discovery in contention-based peer-to-peer wireless networks
US20140274135A1 (en) * 2012-06-15 2014-09-18 Qualcomm Incorporated Client access to mobile location services
US20150201305A1 (en) * 2014-01-15 2015-07-16 Ford Global Technologies, Llc Methods and systems for providing location based services in a venue using femtocells
US20150201308A1 (en) * 2006-10-27 2015-07-16 Santa Monica Semiconductor, LLC. Location of cooperative tags with personal electronic device

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7974639B2 (en) * 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
US20150201308A1 (en) * 2006-10-27 2015-07-16 Santa Monica Semiconductor, LLC. Location of cooperative tags with personal electronic device
WO2011085265A2 (fr) * 2010-01-08 2011-07-14 Qualcomm Incorporated Procédé et appareil de routage de messages d'un protocole de localisation dans un réseau sans fil
US20130321209A1 (en) * 2012-05-30 2013-12-05 Nokia Corporation Method, apparatus, and computer program product for high accuracy location determination
US20140274135A1 (en) * 2012-06-15 2014-09-18 Qualcomm Incorporated Client access to mobile location services
WO2014087196A1 (fr) * 2012-12-07 2014-06-12 Nokia Corporation Manipulation d'unités de données en paquets
US20140241257A1 (en) * 2013-02-26 2014-08-28 Qualcomm Incorporated Scalable discovery in contention-based peer-to-peer wireless networks
US20150201305A1 (en) * 2014-01-15 2015-07-16 Ford Global Technologies, Llc Methods and systems for providing location based services in a venue using femtocells

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10772057B1 (en) 2019-02-25 2020-09-08 Hong Kong Applied Science And Technology Research Institute Co., Ltd. Systems and methods for wireless device synchronization

Similar Documents

Publication Publication Date Title
US11163034B2 (en) Location system
US10715465B1 (en) Asset tracking systems and methods
EP2662703B1 (fr) Amélioration de la précision de positionnement de système de suivi d'emplacement
US20150002271A1 (en) Variable listen duration and/or synchronized wake-up of asset tags
EP3679557B1 (fr) Système et procédé pour transmettre des données d'occupation à partir de capteurs à un serveur distant
JP6082734B2 (ja) 無線通信システム
JP6884786B2 (ja) 測位モード間の遷移の発生
CN112262586B (zh) 低级智能电话音频和传感器时钟同步
WO2013117734A1 (fr) Dispositif mobile de communication de données sans fil et procédé de communication de données par communication de données sans fil dans un réseau de communication de données
WO2017064356A1 (fr) Gestion du fonctionnement d'au moins un dispositif de communication sans fil dans un système de positionnement
US11860261B2 (en) Master-less device coordination in location positioning system
EP4258711A1 (fr) Procédé et système de surveillance à distance d'un signe vital d'un patient

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15906191

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15906191

Country of ref document: EP

Kind code of ref document: A1