AU2019101086A4 - Trackable device, assembly, system, method and computer readable medium - Google Patents

Abstract

TRACKABLE DEVICE, ASSEMBLY, SYSTEM, METHOD AND COMPUTER READABLE MEDIUM Disclosed is a trackable device, assembly, system, method and computer readable medium. In one aspect the trackable device comprises: one or more transceivers; one or more memories storing data indicative of one or more wireless devices; and one or more processors configured to: control the one or more transceivers to perform a wireless device scan; and if the trackable device is outside range of the one or more wireless devices based on the wireless device scan, transmit, to a tracking system via another wireless device, a tracking signal indicative of at least some of the wireless device scan. -2/14 Mtw w1 -V o.co ww Y-g LA V-1 I wL wC wLat I o E 1 Ln II-V e

Description

TRACKABLE DEVICE, ASSEMBLY, SYSTEM, METHOD AND

COMPUTER READABLE MEDIUM

Related Applications [0001] The current application is a divisional application of Australian Patent Application No 2018220110, filed 23 August 2018, the contents of which is herein incorporated by reference in its entirety.

Technical Field [0002] The present invention relates generally to tracking and, in particular, to a trackable device, method and computer readable medium.

Background [0003] It is possible to currently physically associate (e.g. tether, secure, etc.) a trackable device with an object to thereby track the object. For example, if the object is lost or stolen, the trackable device can be used to try and locate the associated object.

[0004] Some trackable devices utilise cellular and/or GPS technologies to allow the tracking of the associated object with another computerised device. Whilst these tracking devices can be quite sophisticated, these technologies have a high level electrical power consumption which result in a portable power source of the trackable device needing to be recharged regularly (e.g. every day or so).

[0005] There has been recent development of low power trackable devices which utilise Bluetooth Low Energy (BLE). However, BLE tracking devices are not sophisticated devices due to power constraints. If a user is trying to locate a lost object associated with a BLE tracking device, one must hope that a GPS and Bluetooth enabled computerised device, such as a smart phone, is within transmission range. Generally, the smart phone is configured to present a general indication of the proximity of the tracking device relative to the smart phone based on the received signal strength. However, this scenario with BLE tracking devices is only

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 somewhat useful if the user has a general idea of where the device was lost (i.e. it is located in a house, but the specific location is unknown).

[0006] In circumstances where the user does not know the general location of the lost object (and therefore the associated BLE tracking device), smart phones of other users can be configured to forward a received beacon signal to a tracking server processing system. The smart phones of other users use their respective location services to determine the location which the beacon signal was received. However, it may take a considerable period of time before another user may be within range. In the meantime, the tracking device continues emitting a beacon signal, thereby slowly draining the battery.

[0007] Furthermore, given a BLE signal can travel distances of approximately 50 to 100 metres, and given there is also some degree of error with GPS in unfavourable locations (areas with tall buildings, underground car parks, etc.) the geographical location forwarded to the server processing system could be quite inaccurate.

[0008] The reference in this specification to any prior publication (or information derived from it), or to any matter which is known, is not, and should not be taken as, an acknowledgement or admission or any form of suggestion that prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavor to which this specification relates.

Summary [0009] It is an object of the present invention to substantially overcome, or at least ameliorate, one or more disadvantages of existing arrangements mentioned above or provide a useful alternative.

[0010] In a first aspect, the present invention provides a trackable device comprising: one or more transceivers; one or more memories storing data indicative of one or more wireless devices; and one or more processors configured to: control the one or more transceivers to perform a wireless device scan; and if the trackable device is outside range of the one or more wireless devices based on the wireless device scan, transmit, to a tracking system via another wireless device, a tracking signal indicative of at least some of the wireless device scan.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0011] In one embodiment, the one or more transceivers comprise a first and second transceiver using a first and second wireless communication protocol respectively, wherein the one or more wireless devices comprise one or more first devices and one or more second devices which communicate using the first and second wireless communication protocols respectively, wherein the one or more processors are configured to perform the wireless device scan by controlling the first transceiver to perform a first scan and controlling the second transceiver to perform a second scan.

[0012] In another embodiment, the first wireless communication protocol is Bluetooth communication protocol and the first transceiver is a Bluetooth Low Energy (BLE) transceiver, and wherein the second wireless communication protocol is Wi-Fi and the second transceiver is a Wi-Fi transceiver.

[0013] In another embodiment, the trackable device is configured to store in the one or more memories, historical data indicative of at least some of the detected wireless devices from the wireless device scan, and wherein the data stored in the one or more memories is indicative of a primary device, wherein if the wireless device scan detects that the primary device is within range of the trackable device, the one or more processors are configured to control the one or more transceivers to: establish, a wireless connection with the primary device; and upload, to the primary device, the historical data.

[0014] In another embodiment, the one or more processors determine if a comparison of one or more preceding wireless device scans with the wireless device scan satisfies a wireless scan discrepancy condition, wherein in response to the wireless scan discrepancy condition being satisfied, temporal data is updated in the one or more memories, wherein the tracking signal is indicative of the temporal data.

[0015] In a further aspect there is provided a trackable device comprising: one or more transceivers;

one or more memories storing whitelist data indicative of one or more whitelisted wireless devices; and one or more processors configured to:

control the one or more transceivers to perform a wireless device scan; and

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 if the trackable device is outside range of the one or more whitelisted wireless devices based on the wireless device scan, transmit, to a tracking system via a non-whitelisted wireless device, a tracking signal indicative of at least some of the wireless device scan.

[0016] In certain embodiments, the trackable device is operable in a configuration mode, wherein the one or more processors are configured to obtain and store the whitelist data in the one or more memories.

[0017] In certain embodiments, the trackable device is configured to obtain, from a computerised device, configuration data indicative of the whitelist data.

[0018] In certain embodiments, the trackable device is configured to store in the one or more memories, a historical tracking report indicative of at least some of the detected wireless devices from the wireless device scan.

[0019] In certain embodiments, the whitelist data is indicative of a primary whitelisted device, wherein if the wireless device scan detects that the primary whitelisted device is within range of the trackable device, the one or more processors are configured to control the one or more transceivers to:

establish, a wireless connection with the primary whitelisted device; and upload, to the primary whitelisted device, the historical tracking report.

[0020] In certain embodiments, the one or more processors determine if a comparison of one or more preceding wireless device scans with the wireless device scan satisfies a wireless scan discrepancy condition, wherein in response to the wireless scan discrepancy condition being satisfied, temporal data is updated in the one or more memories, wherein the tracking signal is indicative of the temporal data.

[0021] In certain embodiments, the one or more transceivers comprise a first and second transceiver using a first and second wireless communication protocol respectively, wherein the one or more whitelisted wireless devices comprise one or more first whitelisted devices and one or more second whitelisted devices which communicate using the first and second wireless communication protocols respectively, wherein the one or more processors are configured to perform the wireless device scan by controlling the first transceiver to perform a first scan and controlling the second transceiver to perform a second scan.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0022] In certain embodiments, the second wireless communication protocol is Wi-Fi and the second transceiver is a Wi-Fi transceiver.

[0023] In certain embodiments, the non-whitelisted wireless device is a Wi-Fi access point.

[0024] In certain embodiments, the one or more memories have stored therein credential data, wherein the trackable device uses the credential data to establish a wireless connection with the non-whitelisted wireless device in order to transmit the tracking signal to the tracking system.

[0025] In certain embodiments, the one or more processors are configured to control the second transceiver to transmit the tracking signal if the detected non-whitelisted wireless device satisfies a routing condition stored in the one or more memories.

[0026] In certain embodiments, the routing condition is satisfied if a device or network identifier of the detected non-whitelisted wireless device is stored in the one or more memories.

[0027] In certain embodiments, the first wireless communication protocol is Bluetooth communication protocol and the first transceiver is a Bluetooth Low Energy (BLE) transceiver.

[0028] In certain embodiments, the first transceiver is configured to transmit a beacon signal in response to a timer interrupt or a sensor interrupt.

[0029] In certain embodiments, the trackable device includes an accelerometer, wherein the sensor interrupt is detected in response to motion sensed by the accelerometer.

[0030] In a second aspect there is provided a trackable pet assembly including:

a collar having attached thereto a trackable device configured according to the first aspect; and a leash assembly releasably coupled to the collar including a beacon transmitter, the beacon transmitter being one of the one or more whitelisted wireless devices.

[0031] In certain embodiments, the trackable device includes a rechargeable power source, wherein leash assembly includes a further rechargeable power source, wherein a leash of the leash assembly includes an electrical transfer medium for electrically connecting the rechargeable power source of the trackable device with the further rechargeable power source of

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 the leash assembly so that the rechargeable power source is recharged by the further rechargeable power source whilst electrically connected.

[0032] In certain embodiments, the beacon transmitter is a Bluetooth Low Energy beacon transmitter.

[0033] In a further aspect there is provided a method performed by a trackable device, the trackable device comprising one or more transceivers, one or more memories storing one or more whitelisted wireless devices; and one or more processors, wherein the method includes:

controlling the one or more transceivers to perform a wireless device scan; and if the trackable device is outside transmission range of the one or more whitelisted wireless devices based on the wireless device scan, transmitting, to a tracking system via a detected non-whitelisted wireless device, a tracking signal indicative of at least some of the wireless device scan.

[0034] In a further aspect there is provided a computer readable medium including executable instructions for configuring a trackable device, wherein the trackable device comprises one or more transceivers, one or more memories storing one or more whitelisted wireless devices; and one or more processors, wherein execution of the executable instructions configure the trackable device to:

control the one or more transceivers to perform a wireless device scan; and if the trackable device is outside range of the one or more whitelisted wireless devices based on the wireless device scan, transmit, to a tracking system via a detected non-whitelisted wireless device, a tracking signal indicative of at least some of the wireless device scan.

[0035] Other aspects and embodiments will be appreciated throughout the detailed description of the one or more preferred embodiments.

Brief Description of the Figures [0036] Example embodiments should become apparent from the following description, which is given by way of example only, of at least one preferred but non-limiting embodiment, described in connection with the accompanying figures.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0037] Figure 1A is a schematic block diagram representation of an example of a trackable device;

[0038] Figure IB is a schematic block diagram representing a further example of a trackable device;

[0039] Figure 1C is a schematic block diagram representing a further example of a trackable device;

[0040] Figure 2 is a flow diagram of an example method performed by the trackable device of Figure 1A;

[0041] Figure 3 A is a system diagram of an example of a system where the trackable device of Figure 1A being configured;

[0042] Figure 3B is a schematic diagram of a smartphone used for defining the whitelisted wireless devices for configuring the trackable device in Figure 3A;

[0043] Figure 3C is schematic diagram of the smartphone of Figure 3B presenting configuration data for configuring the trackable device of Figure 3 A;

[0044] Figure 3D is a system diagram of the system of Figure 3 A where the trackable device of the system of Figure 3 A is located outside transmission range of one or more whitelisted wireless devices but is located within range of a non-whitelisted device facilitating a tracking system;

[0045] Figure 3E is a system diagram of the system of Figure 3 A where the trackable device is located within transmission range of a first type of whitelisted wireless device from the whitelist data defined in Figure 3C;

[0046] Figure 3F is a system diagram of the system of Figure 3 A where the trackable device is located within transmission range of a second type of whitelisted wireless device from the whitelist data defined in Figure 3C;

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0047] Figure 3G is a system diagram of the system of Figure 3 A where the trackable device is located within transmission range of a primary whitelisted wireless device;

[0048] Figure 4 is a flowchart representing a method of configuring the trackable device of Figure 1A, IB or 1C;

[0049] Figure 5 is a flowchart representing a method of operating the trackable device of Figure 1A, IB, or 1C;

[0050] Figure 6A is a schematic of an example of a trackable leash assembly;

[0051] Figure 6B is a block diagram of the leash assembly of Figure 6 A;

[0052] Figure 7 is a block diagram of a processing system suitable for use in one or more embodiments; and [0053] Figure 8 is a block diagram of a mobile computerised device suitable for use in one or more embodiments.

Detailed Description of Example Embodiments [0054] The following modes, given by way of example only, are described in order to provide a more precise understanding of the subject matter of a preferred embodiment or embodiments.

[0055] Described herein is a trackable device, a method performed by the trackable device, a computer readable medium for configuring the trackable device, and a system for tracking the trackable device.

[0056] Referring to Figure 1A there is shown a block diagram schematic of a trackable device 100. In particular, the trackable device 100 comprises one or more transceivers 115, one or more memories 110 storing whitelist data indicative of one or more whitelisted wireless devices, and one or more processors 105. The one or more processors 105 are configured to control the one or more transceivers 115 to perform a wireless device scan. If the trackable device 100 is outside range of the one or more whitelisted wireless devices based on the wireless device scan, the one or more processors 105 are configured to transmit, via at least one of the one or more

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 transceivers 115 to a tracking system 360 (see Figure 3A), a tracking signal indicative of the wireless device scan. The tracking system 360 can use the wireless device scan indicated by the tracking signal to determine a location, or at least a region of the trackable device 100.

[0057] Advantageously, the trackable device 100 dynamically controls when the tracking signal is transmitted based on the wireless device scan. If the trackable device is located within transmission range of one or more whitelisted devices, the trackable device 100 does not emit a tracking signal. This can be advantageous in terms of conservation of power. As explained in the below examples, the tracking system may utilize a database including mapped geographical locations of a plurality of wireless devices to determine that the trackable device 100 is located within transmission range of the one or more detected wireless devices. This is advantageous as it allows for more a accurate location to potentially be determined for the trackable device 100 due to the mapped geographical locations of wireless devices such as Wi-Fi access points.

[0058] In a preferable form, in the event that no whitelisted device from the whitelist data is detected within transmission range of the trackable device 100, the trackable device can transmit a tracking signal to the tracking system 360 via a non-whitelisted access point. For example, the tracking signal can be provided in the form of a probe request which is transmitted via Wi-Fi for configured one or more non-whitelisted access points within transmission range to receive and forward to a server processing system associated with the tracking system. The probe request can include a payload which can be indicative of tracking data such as at least some of the wireless scan including at least some of the one or more wireless devices detected from the scan. The probe request can include an identifier to indicate to the receiving Wi-Fi access point that the probe request includes tracking data for forwarding to the server processing system of the tracking system 360.

[0059] In certain forms, in the event that no whitelisted device from the whitelist data is detected within transmission range of the trackable device 100, but at least one of the detected wireless devices is a non-whitelisted access point which the trackable device 100 can use as a router to communicate the wireless scan data to the tracking system 360, the trackable device can communicate the tracking signal to the tracking system 360 via the non-whitelisted access point. In one form, the trackable device 100 has stored in the one or more memories 110 credentials for enabling the one or more processors 105 to establish using at least one of the one or more transceivers 115 a wireless connection with the detected non-whitelisted wireless

23500536 (IRN: P307305D1) ίο

2019101086 20 Sep 2019 device. Once the wireless connection has been established with the detected non-whitelisted wireless device, the trackable device 100 transmits the tracking signal which is received by the detected non-whitelisted wireless device and is routed to the tracking system 360.

[0060] Continuing to refer to Figure 1A, the trackable device 100 can also include one or more input devices 140. The one or more input devices 140 can be manually selected by a user to control configuration of the whitelist data. As discussed in later examples, the one or more input devices 140 may also be used for other purposes. As shown in Figure 1 A, the trackable device 100 also includes a portable power source 125 such as one or more batteries. As also shown in Figure 1A, the one or more processors 105, the one or more memories 110, the one or more input devices 140, and the one or more transceivers 115 are interconnected by a bus 170.

[0061] Referring to Figure IB, a further example of the trackable device 100 is shown. In addition to the trackable device 100 including the one or more processors 105, the one or more memories 110, the first and second transceivers 116, 120, the one or more input devices 140, and the power source 125 as discussed in relation to Figure 1A, the trackable device can further include one or more sensors 130 and one or more output devices 140.

[0062] The one or more sensors 130 can include a multi axis accelerometer 135. The one or more input devices 140 can include a push button 145 which is coupled to the bus 170. The one or more output devices 150 can include a light 155 such as an LED (Light Emitting Diode) and a speaker 160 which are coupled to the bus 170. The power source 125 may be provided in the form of a rechargeable power source such as one or more rechargeable batteries. In one form, if the button 145 is selected, the one or more processors actuate the LED 155 to provide user feedback. In this embodiment, the trackable device 100 can include a recharging interface 165 to enable a charging device to couple to the trackable device to recharge the portable power source 125 of the trackable device 100. The trackable device 100 can include a power detection device 127, electrically coupled to the portable power source 125 and coupled to the bus 170, configured to determine and generate data indicative of an amount of charge stored by the portable power source. As shown in Figure IB, the one or more transceivers 115 preferably includes a first transceiver 117 and a second transceiver 120.

[0063] Referring of Figure 1C there is shown a schematic of a further example of a trackable device 100. The trackable device 100 exemplified by Figure 1C can include the same

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 components as discussed in relation to Figure IB. However, as shown in Figure 1C, the trackable device 100 can include a first controller 180 in communication with a second controller 182. The first controller 180 can include similar components as that shown in Figure IB except the first controller 180 does not include the second transceiver 120. More specifically, the second transceiver 120 is part of the second controller 182.

[0064] The second controller 182 can include a processor 184, a memory 186, the second transceiver 120, and an i/o interface 188 coupled together via a bus. The i/o interface 188 of the second controller 182 is in communication with an i/o interface 175 of the first controller 180. A data transfer medium 198 such as a serial cable or the like can interconnect the first and second controllers 180, 182 to form the trackable device 100.

[0065] As shown in Figure IB, the second controller 182 does not include an input device, an output device and/or one or more sensors 196. However, it will be appreciated that certain components or the first controller 180 could be redistributed to the second controller 182. The second controller 182 may share the power source 125 of the first controller 180. However, it is possible that the trackable device 100 may include multiple power sources.

[0066] In a preferable form, the first transceiver 116 of the first controller 180 is a Bluetooth (i.e. Bluetooth Low Energy) transceiver and the second transceiver 120 of the second controller 182 is a Wi-Fi transceiver. In one example, the first and second controllers 180, 182 can be provided in the form of a system on chip respectively. In one example first controller 180 is a RTL8762AG produced by Realtek (http://www.realtek.com), and the second controller 182 is an ESP8266 produced by Espressif Systems (https://www.espressif.com).

[0067] Referring to Figure 2 there is shown a method 200 performed by the trackable device 100. Method 200 will be described in conjunction with Figures 3C and 3D for the purposes of clarity. Furthermore, Figures 3C and 3D will be described in relation to the trackable device exemplified by Figure IB or 1C which includes the first and second transceivers 116, 120.

[0068] In particular, at step 210 the method 200 includes the one or more processors 105 controlling the one or more transceivers 115 to perform a wireless device scan. As the first and second transceiver utilise different wireless communication protocols such as Bluetooth and WiFi, the transmission range for each transceiver may be different. Generally, Wi-Fi has a larger

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 transmission range to that of Bluetooth. This is represented in Figure 3D as circle having broken line, wherein the first transceiver 116 has a transmission range represented by circle 301 and the second transceiver 120 has a transmission range represented by circle 302. It will be appreciated that in practice, the transmission range of the transceivers will unlikely have a circular crosssection due to a variety of factors such as obstacles and the like.

[0069] As shown in Figure 3D, wireless devices 310P, 310A and 310D are located outside transmission range of the trackable device 100 and would not be identified in the wireless device scan. Wireless devices 310C, 310B and 31 OF are located within transmission range (illustrated by dotted circle 302) of the trackable device 100 and are identified during the wireless device scan. In this example, wireless device 31 OF uses the first communication protocol detected by the first transceiver 116, and wireless devices 310B and 310C use the second communication protocol detected by the second transceiver 120. As would be appreciated, the wireless device scan can include performing a first scan using the first transceiver 116 and a second scan using the second transceiver 120.

[0070] At step 220, the method 200 includes the one or more processors 105 determining if the trackable device 100 is outside transmission range of the one or more whitelisted wireless devices indicated by the whitelist data 390 based on the wireless device scan. As shown in Figure 3C, the whitelist data for this example includes wireless devices 310A, 310D, and 310P. None of the detected wireless devices identified in the wireless device scan performed by the first and second transceiver 116, 120 are part of the whitelist data 390.

[0071] In response to a positive determination (i.e. “yes”) in relation to step 220, the method 200 proceeds to step 230. In response to a negative determination (i.e. “no”) in relation to step 220, the method 200 can end or preferably return to step 210. In relation to the example depicted in Figure 3D, the method 200 proceeds to step 230. A further example will be discussed later in relation to Figures 3E and 3F in the event that one of the whitelisted wireless devices 310A, 310D, 31 OP is detected as being located within transmission range of the trackable device 100 based on the wireless device scan.

[0072] At step 230 the method 200 includes the trackable device 100 transmitting, via the one or more transceivers 115 to the tracking system 315, a tracking signal indicative of the wireless device scan. The tracking signal with respect to Figure 3D would be indicative of detected

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 wireless devices 31 OB, 3 IOC and 31 OF being within transmission range of the trackable device 100. The tracking signal is also indicative of a unique identity associated with the trackable device 100 which may include a MAC address of the first transceiver 116 and/or second transceiver 120.

[0073] In one form, the method 200 includes the trackable device 100 communication the tracking signal in the form of a probe request to be received by any appropriately configured access point within transmission range. As discussed above, the probe request is generated to include a payload which is indicative of tracking data. The tracking data can include at least some of the wireless scan data.

[0074] Additionally or alternatively, the method 200 includes the trackable device 100 communicating the tracking signal 305 via a non-whitelisted wireless devices 310C detected during the wireless device scan.

[0075] For example, as shown in Figure 3D, the trackable device 100 can transmit the tracking signal 305 using the second transceiver 120 to the wireless device 310C acting as a router which routes data received from the trackable device 100 to the tracking system 360. As discussed above, the one or more processors 105 may use credentials stored as credential data in the one or more memories 110 of the trackable device 100 for establishing a wireless connection with a detected non-whitelisted wireless device 310C in order to transmit the tracking signal 305 to the tracking system 360.

[0076] Continuing with Figure 2, the method 200 then ends or preferably returns to step 210. As shown in Figure 2, the method 200 preferably proceeds back to step 210 to perform a loop of steps 210 to 230. In a preferable form, the trackable device 100 waits at step 240 for a predetermined period of time prior to proceeding back to step 210 again or until a certain condition has been met such as a particular interrupt has occurred. In one form, the method 200 may end due to external input such as a user pressing the button 145 for a threshold period of time in order to return the trackable device 100 to a configuration mode to be reconfigured.

[0077] As shown in Figure 3D, the trackable device 100 can also be configured to transmit a beacon signal 303 using the first transceiver 116. The beacon signal 303 is transmitted periodically or in response to sensed motion which exceeds an acceleration threshold by the

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 accelerometer 135. If a user would like to track the trackable device 100 (e.g. the user may have lost the object associated with the trackable object), they may use their computerised device 350 to transfer a tracking request to the tracking system 360. The tracking request can be associated with a unique identity of the trackable device 100 in accessible memory of the tracking server processing system 370. When the beacon signal 303 is received by a third party computerised device 31 OF (such as a smartphone) having installed thereon a companion application 355 running in background services, the computerised device 31 OF forwards the received notification to the tracking server processing system 370. The notification is indicative of the unique identity associated with the trackable device 100. The tracking server processing system 370 determines if a tracking request is outstanding for the trackable device in accessible memory. If yes, the tracking server processing system 370 uses additional data provided with the received notification to determine the location of the trackable device 100. For example, the third party computerised device 31 OF may be a GPS enabled device and can be configured by the companion application 355 to use its geolocation services to determine a current position of the third party computerised device 31 OF after receiving the beacon signal 303 such that the notification sent to the tracking server processing system 370 is indicative of a location such as a latitude and longitude. If the third party computerised device is not a GPS enabled device, the third party computerised device 31 OF can be configured by the companion application 355 to perform a wireless device scan to detect Wi-Fi access points within transmission range. The tracking server processing system 370 can transfer a query 322 to a mapping server processing system 330 to determine a location of the trackable device 100 based on the Wi-Fi access points detected by the third party computerised device shortly after receiving the beacon signal from the trackable device 100.

[0078] Referring to Figure 3E there is shown a further example system where wireless device 310D is located within transmission range of the trackable device 100. In this particular example, the wireless device 310D is a Bluetooth enabled smartwatch which the user may regularly wear. In this example, the trackable device 100 may be tethered to the user’s set of keys which are generally located within transmission range of the user. When the method 200 is performed in relation to the user shown in Figure 3E, at step 210 the wireless scan performed using the first transceiver 116 determines that wireless device 310D is located within transmission range of the trackable device 100. The second scan performed by the second transceiver 120 returns no wireless devices as shown schematically in Figure 3E where wireless devices 310B, 310C, 31 OP and 310A which communicate using the second communication

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 protocol are located outside transmission range of the trackable device 100. At step 220, the one or more processors 110 determine that the wireless device 310D is a whitelisted wireless device in the whitelist data depicted in Figure 3C. Therefore, the trackable device 100 does not transmit the tracking signal 305. This use case would occur in a situation where the user has left their home location (and the whitelisted data defines Wi-Fi access points which are receivable and indicative of their home location) but the trackable device 100 is located within transmission range of a portable Bluetooth device, such as the smartwatch 310D being worn by the user. However, if the user dropped their keys unknowingly (outside transmission range) from home and walked away, the trackable device 100 would periodically perform step 210 again which will identify that wireless device 310D is also outside transmission range resulting in the trackable device 100 attempting to transmit the tracking signal 305 to communicate with the tracking system 360 if possible.

[0079] Referring to Figure 3F, when method 200 is being performed, the wireless device scan performed by the second transceiver 120 at step 210 would return wireless devices 310A, 310B, and 310C as these wireless devices are located within transmission range of the trackable device 100. Step 220 would result in a negative determination due to wireless device 310A being a whitelisted wireless device as depicted in Figure 3C. As such, in this use case, the trackable device also does not transmit the tracking signal 105.

[0080] Referring to Figure 3G, there is shown a scenario where the trackable device is located within transmission range of a primary whitelisted wireless device 31 OP. As shown in Figure 3C, the user can select one of the whitelisted wireless devices 390 as the primary whitelisted device 395. In this use case, if the trackable device 100 detects the primary whitelisted wireless device 31 OP is within transmission range based on the wireless device scan, the trackable device 100 transmits, to the primary whitelisted wireless device 31 OP, a historical tracking signal 360 indicative of a historical tracking report stored in the one or more memories 110 of the trackable device 100. As shown in Figure 3G, the primary whitelisted device 31 OP may be a Wi-Fi router such as the user’s home router. However, it is possible that the primary whitelisted wireless device 31 OP may be a Bluetooth enabled device such as a Bluetooth enabled smartphone or some other Bluetooth enabled computerised device. Therefore, the first or second transceiver 116, 120 may be used for transmitting the historical tracking signal 360. The primary whitelisted device 31 OP may then transfer the historical tracking report to the tracking system for storage. The historical tracking report can be pushed to or pulled by the user’s computerised device 350

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 from the tracking system using the companion application 355. In some situations, there may be no historical tracking report stored in memory of the trackable device 100. Thus despite the primary whitelisted wireless device 31 OP being located within transmission range of the trackable device 100, the trackable device may not communicate with the primary whitelisted wireless device 31 OP.

[0081] Referring to Figure 4 there is shown a flowchart representing a method of configuring the trackable device 100. Method 400 will be described with reference to Figure 3A.

[0082] At step 410, the method 300 includes the user pressing the button 145 of the trackable device 100 to operate the trackable device 100 in a configuration mode. In particular, when the user first acquires the trackable device 100 (e.g. purchases the trackable device), the trackable device 100 can be in a sleep mode where no RF signals are emitted by the trackable device 100. Once the user presses the button 145, the trackable device 100 awakens due to a button interrupt being detected and the trackable device 100 moves to a configuration mode. It will be appreciated that method 400 may also be performed when reconfiguring the trackable device 100. Therefore, the trackable device 100 may alternatively enter the configuration mode from an operating mode.

[0083] At step 420, the method 400 includes the trackable device 100 establishing a wireless connection 308 with a user’s computerised device 350. In particular, the trackable device 100 attempts to pair with the user’s computerised device 350 using the first transceiver 116. Configuration may be guided via the companion application (“app”) 355 downloaded from an application server. Execution of the companion application 355 can cause configuration instructions to be presented via a user interface of the user’s computerised device 350. The user may be instructed via the user interface to press the button 145 of the trackable device 100. The companion application 355 can cause the computerised device 350 to attempt to pair with the trackable device 100. Whilst not depicted by Figure 4, if the trackable device 100 is unable to establish a wireless connection with the user’s computerised device, the trackable device 100 may return to the previous mode (i.e. sleep or operating modes).

[0084] At step 430, the method 400 includes the trackable device 100 performing a wireless device scan. As discussed above, the wireless device scan may include the first wireless device scan using the first transceiver 116 and the second wireless device scan using the second

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 transceiver 120. For the trackable device of Figure IB and 1C, the wireless device scan detects Bluetooth enabled devices and Wi-Fi access points within transmission range of the trackable device 100. For example, as shown in Figure 3A, during the wireless device scan of the configuration of trackable device 100, the first scan using the first transceiver 116 detects computerised device 350, wireless device 310D, and wireless device 310E. The second scan using the second transceiver 120 detects Wi-Fi access point 310A, Wi-Fi access point 310B and Wi-Fi access point 31 OP. During the scan, various details are stored in the one or more memories of the trackable device 100 such as a wireless device name, MAC address of the detected wireless device, SSID of the detected wireless device, and BSSID of the detected wireless device where appropriate for the respective wireless protocol.

[0085] At step 440, the method 400 includes the trackable device 100 transferring, during the established wireless communication session, the detected wireless devices to the user’s computerised device 350. In order to minimise data transfer between the trackable device 100 and the user’s computerised device 350, the data transferred to the user’s computerised device 350 merely provides sufficient information for the user to be able to recognise the respective wireless devices. For example, for detected Wi-Fi access points, the trackable device 100 may simply transfer the SSID (i.e. Wi-Fi network name) to the user’s computerised device 350. Information such as BSSID and MAC addresses which are generally not easily recognisable by humans may not be transferred but may be retained in the one or more memories of the trackable device 100.

[0086] At step 450, the method 400 includes the computerised device 350 presenting the list of detected wireless devices 380 received from the trackable device 100. As shown in Figure 3B, a list of human recognisable names may be presented via the user interface of the companion application 355 executing upon the user’s computerised device 350. For example, for Bluetooth enabled devices, the Bluetooth device name may be presented in the detected wireless device list 380 of the user interface, and for Wi-Fi access points the network name (i.e. SSID) may be presented in the detected wireless device list 380 of the user interface. Whilst these fields may not be unique fields, generally this type of information is sufficient for the transmission region and assists the user defining the whitelist data as the user is likely to be aware of these nonunique identifiers from previous interactions with these wireless devices.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0087] At step 460, the method 400 includes the user customizing the list of detected wireless devices 380 to define the whitelisted wireless devices. As shown in Figure 3B, the user can select to delete one or more of the detected wireless devices from the list thereby filtering the list. For example, in the example shown in Figure 3B the user has selected wireless devices 310B, 310C, 310E, and 350 to be removed from the detected wireless device list thereby defining the whitelist data to include wireless devices 310A, 310D and 31 OP. The user may exclude one or more wireless devices for various reasons. For example, wireless speaker 310D may not be the user’s device and is unlikely to be in same area in the future, thereby not being a useful indicator of the trackable device’s location. However, it will be appreciated that the user does not necessarily need to able to connect the all whitelisted wireless devices. For example, a detected Wi-Fi access point of a neighbour may be appropriate to indicate that the trackable device is located within transmission range of the neighbour’s property and thus the user’s home. As shown in Figure 3C, the finalized whitelisted wireless devices 390 is presented via the user interface of the companion application 355 executing upon the user’s computerised device 350.

[0088] At step 470, the method 400 includes the user selecting a primary whitelisted device 395. In the use case shown in Figure 3A, the primary whitelisted device is wireless device 31 OP. In one form, the wireless device 31 OP may be a user’s home router. In another form, the primary whitelisted device 395 may be the user’s computerised device 350. Preferably, the user interacts with the companion application 355 to select one of the whitelisted wireless devices 390 as the primary whitelisted device 395. Upon selection, connection data is saved in association with the whitelist data 390 in memory of the computerised device 350. If the selected primary whitelisted device 395 is a Bluetooth enabled device, Bluetooth connection details are stored in association with the selection of the primary whitelisted device 395 in memory of the user’s computerised device 350. If the primary whitelisted device is a Wi-Fi access point, a Wi-Fi password may be input by the user using the user interface of the companion application 355 and stored in association with the selection of the primary whitelisted device 395 in memory of the user’s computerised device 350.

[0089] At step 480, the method 400 includes the user’s computerised device 350 transferring configuration data 399 to the trackable device 100 for storage in the one or more memories 110. The transfer of the configuration data 399 occurs during the secure wireless connection established in step 420. The configuration data 399 includes an indication of the whitelisted

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 wireless devices 390, an indication of the primary whitelisted wireless device 395, and the connection data for connecting to the primary whitelisted wireless device.

[0090] After step 480 has been completed, the method 400 ends and the trackable device 100 proceeds to operate in the operational mode.

[0091] Referring to Figure 5 there is shown a flowchart representing a method 500 performed by the trackable device 100 when operating in the operational mode. Method 500 will be described with respect to the trackable device of Figure IB or 1C.

[0092] At step 505, the method 500 includes the one or more processors 105 determining if an input interrupt has occurred. This may occur in respect to the user pressing the button 145 to reconfigure the trackable device 100. If an input interrupt has been detected, the method 500 ends and returns to method 400. If no input interrupt has been detected, the method 500 proceeds to step 510.

[0093] At step 510, the method 500 includes the one or more processors 105 determining if a sensor interrupt or timer interrupt has occurred. The trackable device 100 is configured to perform a wireless scan periodically or in response to the accelerometer 135 of the trackable device 100 sensing movement which exceeds an acceleration threshold stored in the one or more

110. In one form, the first controller 180 is configured to periodically transmit the beacon signal 303. Therefore the trackable device 100 operates in a low power state and awakens when a timer interrupt is detected. If a sensor interrupt or a timer interrupt has been detected by the one or more processors 105, the method proceeds to step 515. If neither a sensor interrupt nor a time interrupt has been detected, the method 500 proceeds backs to step 505.

[0094] At step 515, the method 500 includes the trackable device 100 transmitting a beacon signal 303. The beacon signal 202 is transmitted by the first transceiver 116 preferably using BLE protocol. As should be appreciated from step 510, the BLE beacon signal 303 can be generally performed periodically unless step 515 is being performed due to movement sensed by the accelerometer 135. The BLE beacon signal 303 can be indicative of a unique identity associated with the trackable device 100, a power level of the trackable device 100, and data indicative of a time period stored in the one or more memories 110 that the trackable device 100 has detected the same or similar wireless devices based on previous wireless scans. The method

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 which the trackable device 100 determines this time period will be discussed in subsequent steps later in method 500. The power level is determined by the power detection device 127. As discussed in relation to Figure 3D, a user may register a tracking request with the tracking server processing system 370 of the tracking system 360 in the event the trackable device 100 requires tracking (e.g. the user has lost the object which the trackable device is tethered to). Third party computerised devices 31 OF, such as smartphones, with the companion application 355 installed thereon and running in background services, which are within transmission range of the trackable device 100 can transfer the notification to the tracking server processing system 370 in response to receiving the beacon signal 303. The notification can be indicative of the data received in the beacon signal such as the unique identity associated with the trackable device 100 and the power level. In addition, the notification signal can also be indicative of a geographical location of the computerised device determined using geolocation services of the computerised device, and a timestamp. Preferably, the notification may also include Wi-Fi access points detected in response to performing a Wi-Fi scan to determine one or more Wi-Fi access points within transmission range.

[0095] At step 520, the method 500 includes the trackable device 100 performing a wireless device scan. The first transceiver 116 is configured to perform a first scan and the second transceiver 120 is configured to perform a second scan. The first transceiver 116 performs a scan for Bluetooth transmitting devices within transmission range of the trackable device 100, and the second transceiver 120 performs a scan for Wi-Fi access points within transmission range of the trackable device 100. Whilst it is possible that the first and second scans can be performed simultaneously or substantially simultaneously, it is not necessary.

[0096] At step 525, the method 500 includes the trackable device 100 determining if primary whitelisted wireless device 395 has been detected during the wireless device scan. In response to a positive determination (“yes”), the method 500 proceeds to step 527 where the trackable device 100 determines if a recent upload of a historical tracking report has occurred. The trackable device stored in memory a timestamp of the last instance when the historical tracking report was uploaded. If it was recent (i.e. within a temporal threshold), the method proceeds to step 545. If it was not recent (i.e. outside a temporal threshold), the method proceeds to step 529 to transfer a historical tracking report, if one is stored in the one or more memories 110, to the primary whitelisted wireless device 31 OP. The trackable device 100 uses the primary whitelisted wireless device credential data stored during configuration to establish a wireless connection

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 and wirelessly transfer the historical tracking report. Step 529 further includes purging the historical tracking report from memory in order to provide additional storage space for scan data to store a further historical report. The historical tracking report can be routed by the primary whitelisted wireless device 31 OP to the tracking system 360 for storage. The method then proceeds to step 545.

[0097] In response to a negative determination (“no”) at step 525, the method 500 proceeds to step 530 where the method includes the trackable device 100 determining if a whitelisted wireless device has been detected during the wireless device scan. In response to a positive determination, the method proceeds to step 545. In response to a negative determination, the method proceeds to step 533.

[0098] At step 533, the method 500 includes the trackable device 100 generating and transmitting a tracking signal in the form of a probe request. The probe request is preferably transmitted on all available Wi-Fi channels in order to increase the probability that the tracking data is forwarded by an appropriately configured Wi-Fi access point to the tracking server processing system. The payload of the probe request can be indicative of tracking signal identifier to indicate that the probe request includes tracking data, the unique identifier associated with the trackable device 100, the second scan data and a power level indicator determined by the power detection device 127. Preferably, the tracking signal 305 is further indicative of a timestamp which the tracking signal 305 is being sent, first scan data (i.e. Bluetooth devices within transmission range), data indicative of the length of time which the trackable device 100 has sensed the same or substantially similar wireless devices. In response to receiving the tracking signal in the form of a probe request, the non-whitelisted Wi-Fi access point 310C forwards data to a tracking server processing system 370 of the tracking system 360. The memory of the access point may store therein the address of the tracking server processing system 370. After the probe request has been transmitted, the method 500 proceeds to step 535.

[0099] At step 535, the method 500 includes the trackable device 100 determining if a further tracking signal can be transmitted to the tracking system 360 by connecting to a wireless network. In one form, the method 500 includes the trackable device 100 determining if a routing condition has been satisfied. The routing condition is condition is considered satisfied if the trackable device 100 can communicate with the tracking system 360 via any non-whitelisted Wi-Fi access points detected from the second scan. In particular, the trackable device 100

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 determines if any non-whitelisted Wi-Fi access points detected from the second scan are able to route a tracking signal to the tracking system 360. In one form, the trackable device 100 may determine if a device or network identifier, such as the SSID of any one of the detected nonwhitelisted Wi-Fi access points, includes a string portion which is stored in the one or more memories 110, indicative of a distributed network of Wi-Fi access points which the trackable device 100 can use to route the tracking signal to the tracking system. For example, the distributed network of Wi-Fi access points may include the Fon network (www.fon.com). The string portion stored in memory of the tracking system may be “Fon”. Based on the second scan data, one of the detected non-whitelisted Wi-Fi access points 310C has an SSID of “ExampleTelco Fon”. In this example, the trackable device 100 determines that the SSID includes the string portion and thus is able to send the tracking signal to the tracking system 360 via the detected non-whitelisted Wi-Fi access point 310C.

[00100] In response to the method 500 reaching a negative determination at step 530, the method proceeds to step 537 where the trackable device 100 generates a historical tracking report indicative of at least some of the wireless device scan or appends to an existing historical tracking report already stored in the one or more memories 110 of the trackable device 100. The method then proceeds to 545.

[00101] In the event that the trackable signal 305 can be transmitted to the tracking system 360, the method 500 proceeds to step 540, where the method 500 includes the trackable device 100 generating and transmitting the tracking signal 305 to the tracking system 360. The trackable device 100 uses the credential data stored in the one or more memories 110 to connect to the Wi-Fi network associated with the detected non-whitelisted Wi-Fi access point 310C. Upon successfixl connection, the trackable device 100 transmits the tracking signal. The tracking signal 305 can be indicative of the unique identifier associated with the trackable device 100, the second scan data and a power level indicator determined by the power detection device 127. Preferably, the tracking signal 305 is further indicative of a timestamp which the tracking signal 305 is being sent, first scan data (i.e. Bluetooth devices within transmission range), data indicative of the length of time which the trackable device 100 has sensed the same or substantially similar wireless devices. In response to receiving the tracking signal via the Wi-Fi network, the detected non-whitelisted Wi-Fi access point 310C forwards data to a tracking server processing system 370 of the tracking system 360. After the tracking signal has been transmitted, the method 500 proceeds to step 545.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [00102] At step 545 the method includes the trackable device updating temporal data in the one or more memories 110. In particular, the trackable device has stored in the one or more memories 110 temporal data indicative of a time period where successive wireless scans have determined the same or substantially the same wireless devices within transmission range. In one form, the temporal data may be stored as a counter indicative of the number of successive wireless scans that have been performed where the same or substantially similar wireless devices have been detected. As the wireless device scans are performed periodically or at least the period of time between scans is stored in memory of the trackable device 100, the counter is indicative of a time value. The trackable device 100 may have stored in memory a a wireless scan discrepancy condition, wherein in response to the wireless scan discrepancy condition being satisfied, the temporal data is updated in the one or more memories. The wireless scan discrepancy condition may be considered satisfied when a threshold number of wireless devices match between successive wireless device scans. When the wireless scan discrepancy has been satisfied, the updating could include incrementing the counter to indicate the time which the trackable device has been located within transmission range of the same or substantially similar wireless devices. For example, the threshold may be 50%. If successive scan is not considered the same or substantially similar, the temporal data is reset to zero. Once step 545 has been completed, the method proceeds back to step 505. This time period can be presented in the user interface of the companion application 355 of the user’s computerised device 350.

[00103] Upon the tracking server processing system 370 receiving the tracking signal data from the trackable device 100, the tracking server processing system 370 is configured to determine the location of the trackable device 100. For example, the data received from the non-whitelisted wireless device 305 can include the MAC address of each detected Wi-Fi access point which is part of the BSSID. In a preferred form, the tracking signal is indicative of at least two Wi-Fi access points detected within transmission range of the trackable device 100, The tracking signal can also include the signal strength for each detected Wi-Fi access point, a channel which each detected Wi-Fi access point was using for communication, and a signal to noise ratio for each detected Wi-Fi access point. The data can be used by the tracking server processing system 370 to query the mapping server processing system 330 having access to a database 340 which maps stationary wireless devices (e.g. Wi-Fi access points) to geographical locations. The result of the query is a geographical location, such as a latitude coordinate and longitude coordinate of the

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 trackable device 100 as well as a degree of accuracy. A user can obtain the location of the trackable device 100 from the tracking server processing system 370. For example, the location may be pushed or pulled from the tracking server processing system 370 by the user’s computerised device 350 and presented via the user interface of the companion application 355.

[00104] It will be appreciated from method 500 that two tracking signals can be sent. For example, a first tracking signal in the form of a probe request can be sent by the trackable device 100, and a second tracking signal is sent by the trackable device 100 when able to connect to a Wi-Fi network associated with a Wi-Fi access point. Whilst method 500 shows that the first tracking signal sent in the form of a probe request followed by the transmission of the second tracking signal sent via the Wi-Fi connection, these steps could be performed in reverse order where the first tracking signal is initially sent via the Wi-Fi connection followed by the second tracking second being transmitted in the form of the probe request.

[00105] The trackable device 100 can be associated with any object that a user wishes to track. For example, a user could mount the trackable device 100 to a bicycle frame to track whether it has been stolen from a user’s yard [0100] In one variation as shown in Figures 6A and 6B, the trackable device 100 can be secured to or integrated with a pet collar 610 to form a trackable leash assembly 620 in order to track the associated pet wearing the pet collar 610. In this embodiment, a leash device 625 may be releasably coupled to the pet collar 610, wherein the leash device 625 has associated therewith a BLE beacon transmitter 710 electrically coupled to a power source 720 which forms part of the whitelisted wireless device data 390 of the trackable device 100 associated with the pet collar 610. Therefore, despite the pet being walked outside transmission range of a home Wi-Fi router which can also be part of the whitelisted wireless devices 390, the trackable device 100 detects the whitelisted BLE beacon transmitter 710 of the leash device 625 and does not transmit the tracking signal 305 in response. However, should the pet become uncoupled from the leash device 620 at a park, the trackable device 100 will no longer be within transmission range of the BLE transmitter 710 of the leash 620 such that the tracking signal 100 is transmitted by the trackable device 100.

[0101] In one variation as shown in Figures 6A and 6B, the leash device 625 may include a rechargeable power source 720 in electrical contact with a recharging/charging interface 730

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 which can electrically couple to the rechargeable interface 165 of the trackable device 100 associated with the pet collar 610. The leash 630 of the leash device 625 may include an electrical transfer medium such as an electrical wire to transfer electrical power to the recharging interface 165 of the trackable device 100. As such, the power source 720 of the leash device 625 recharges the battery 125 of the trackable device 100 whilst the pet is tethered via the leash 630. In one form, the leash device 625 may include a handle 640 which houses the BLE beacon transmitter 710, the power source 720 and the recharging/charging interface 730.

[0102] As discussed above, the trackable device 100 can include a light 155 and a speaker 160. If the user’s computerised device 350 is within transmission range of the trackable device 100 but the specific location is unknown, the user can interact with the companion application 355 and instruct the user’s computerised device 350 to transmit a command via the companion application 355 to actuate the light 155 and/or the speaker 160. In response to the trackable device 100 receiving the actuation command via the one or more transceivers 116, 120, the one or more processors 105 actuate the light and/or the speaker in order to aid the user locate the trackable device 100.

[0103] Figure 7 illustrates a schematic block diagram of an example processing system 700 suitable for use as the tracking server processing system 370 and mapping server processing system as discussed above. The processing system 700 includes one or more processors 705, one or more memories 710, and a communication interface 715 coupled together via a bus 770.

[0104] Figure 8 illustrates a schematic block diagram of an example mobile computerised device 800 suitable for use as user’s computerised device 350 as discussed above. The mobile computerised device 800 includes one or more processors 805, one or more memories 810, one or more transceivers 815, one or more input devices 820, and one or more output devices 825.

[0105] In one form, the trackable device 100 has stored in the one or more memories executable instructions which when executed by the one or more processors, perform the respective methods as discussed above. However, in other arrangements, the trackable device 100 may include firmware which configure the trackable device to perform the respective methods as discussed above.

Industrial Applicability

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019 [0106] The arrangements described are applicable to asset tracking industries.

[0107] The foregoing describes only some embodiments of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.

[0108] In the context of this specification, the word “comprising” means “including principally but not necessarily solely” or “having” or “including”, and not “consisting only of’. Variations of the word comprising, such as “comprise” and “comprises” have correspondingly varied meanings.

[0109] Many modifications within the scope of the invention will be appreciated by those skilled in the art without department from the spirit of the invention.

Claims (5)

1. A trackable device comprising: one or more transceivers;

one or more memories storing data indicative of one or more wireless devices; and one or more processors configured to:

control the one or more transceivers to perform a wireless device scan; and if the trackable device is outside range of the one or more wireless devices based on the wireless device scan, transmit, to a tracking system via another wireless device, a tracking signal indicative of at least some of the wireless device scan.

2. The trackable device of claim 1, wherein the one or more transceivers comprise a first and second transceiver using a first and second wireless communication protocol respectively, wherein the one or more wireless devices comprise one or more first devices and one or more second devices which communicate using the first and second wireless communication protocols respectively, wherein the one or more processors are configured to perform the wireless device scan by controlling the first transceiver to perform a first scan and controlling the second transceiver to perform a second scan.

3. The trackable device according to claim 2, wherein the first wireless communication protocol is Bluetooth communication protocol and the first transceiver is a Bluetooth Low Energy (BLE) transceiver, and wherein the second wireless communication protocol is Wi-Fi and the second transceiver is a Wi-Fi transceiver.

4. The trackable device according to claim 3, wherein the trackable device is configured to store in the one or more memories, historical data indicative of at least some of the detected wireless devices from the wireless device scan, and wherein the data stored in the one or more memories is indicative of a primary device, wherein if the wireless device scan detects that the primary device is within range of the trackable device, the one or more processors are configured to control the one or more transceivers to:

establish, a wireless connection with the primary device; and upload, to the primary device, the historical data.

23500536 (IRN: P307305D1)

2019101086 20 Sep 2019

5. The trackable device according to any one of claims 1 to 4, wherein the one or more processors determine if a comparison of one or more preceding wireless device scans with the wireless device scan satisfies a wireless scan discrepancy condition, wherein in response to the wireless scan discrepancy condition being satisfied, temporal data is updated in the one or more memories, wherein the tracking signal is indicative of the temporal data.

LX Design House Pty Ltd

Patent Attorneys for the Applicant/Nominated Person