# US 2021/0173034 A1 · Object monitoring system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0173034 A1
- Document ID: US20210173034A1
- Status: Published application
- Kind: A1
- Application number: 16/951,577
- Filed: 2020-11-18
- Published: 2021-06-10
- Earliest claimed: 2018-03-01
- Assignees: Commonwealth Scientific and Industrial Research Organisation
- Applicants: Commonwealth Scientific and Industrial Research Organisation
- Inventors: Philip Juan VALENCIA; Nicholas Alexander HEANEY
- Web page: https://patentgrep.com/patent/US20210173034A1

## CPC

- G01S 1/022: {Means for monitoring or calibrating}
- G06Q 10/0635: Risk analysis of enterprise or organisation activities
- G01S 1/68: Marker, boundary, call-sign, or like beacons transmitting signals not carrying directional information
- G01S 5/02: using radio waves (using satellite radio beacon systems for determining position G01S19/00)
- G01S 5/0284: {Relative positioning}
- G06Q 10/08: Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G08B 21/0275: {Electronic Article Surveillance [EAS] tag technology used for parent or child unit, e.g. same transmission technology, magnetic tag, RF tag, RFID}
- G08C 21/00: Systems for transmitting the position of an object with respect to a predetermined reference system, e.g. tele-autographic system
- H04W 4/029: Location-based management or tracking services
- H04W 4/30: Services specially adapted for particular environments, situations or purposes
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- G08B 21/0227: {System arrangements with a plurality of child units}
- G08B 21/023: {Power management, e.g. system sleep and wake up provisions}
- G08B 21/0272: {System arrangements wherein the object is to detect exact location of child or item using triangulation other than GPS}
- G01S: RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08C: TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS (fluid pressure transmitting systems F15B; mechanical means for transferring the output of a sensing member into a different variable G01D5/00; mechanical control systems G05G)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

An object monitoring system including a plurality of location beacons, each location beacon being configured to generate a location broadcast message indicative of a beacon location and a tag associated with a respective object in use. The includes a tag memory configured to store object rules, a tag transceiver configured to transmit or receive messages and a tag processing device configured to determine context data at least partially indicative of a tag context by at least one of determining a tag location in accordance with at least one location broadcast message received via the tag transceiver from at least one of a plurality of location beacons and using stored context data, use the object rules and the context data to identify a trigger event, determine an action associated with the trigger event and cause the action to be performed.

## Claims

### Claim 1

1) An object monitoring system including:
a tag associated with a respective object in use, wherein the tag includes:
i) a tag memory configured to store object rules;
ii) a tag transceiver configured to transmit or receive messages;
iii) a tag processing device configured to:
(1) determine context data at least partially indicative of a tag context by at least one of:
(a) a received message, including at least one of:
(i) a broadcast message from another tag;
(ii) a client device message from a client device;
(b) sensor data from at least one sensor;
(c) user input commands; and
(d) using stored context data;
(2) use the object rules and the context data to identify a trigger event;
(3) determine an action associated with the trigger event; and,
(4) cause the action to be performed.

### Claim 2 (depends on 1)

2) A system according to claim 1, wherein the system includes:
a) a repository storing object rules for a plurality of object types; and,
b) a client device that communicates with the tag and the repository, and wherein in use object rules are uploaded from the repository to the tag using the client device based on an object type of the respective object.

### Claim 3 (depends on 1)

3) A system to according to claim 1, wherein the system includes:
a) a repository storing object rules for a plurality of object types;
b) a client device that communicates with the tag and the repository, and wherein in use:
i) object rules are uploaded from the repository to the tag using the client device based on an object type of the respective object; and,
ii) the tag processing device is configured to:
(1) determine context data at least partially indicative of a current tag context;
(2) use the object rules and the context data to identify a trigger event;
(3) determine an action associated with the trigger event; and,
(4) cause the action to be performed.

### Claim 4 (depends on 1)

4) A system according to claim 1, wherein the system includes a plurality of location beacons, each location beacon being configured to generate a location broadcast message indicative of a beacon location and wherein the tag processing device is configured to determine context data in accordance with at least one location broadcast message received via the tag transceiver from at least one of the plurality of location beacons.

### Claim 5 (depends on 2)

5) A system according to claim 2, wherein at least one of:
a) the object rules are uploaded to the tag via one or more of the plurality of location beacons
b) a tag message is transferred to a client device via a location beacon; and
c) a client device message is transferred to a tag via a location beacon.

### Claim 6 (depends on 2)

6) A system according to claim 2, wherein the client device includes at least one of:
a) one or more computer systems;
b) one or more smart phones;
c) one or more tablets; and,
d) one or more mobile computing devices.

### Claim 7

7) (canceled)

### Claim 8 (depends on 17)

8) A system according to claim 17, wherein the tag memory is configured to store stored context data and wherein at least one of:
a) the stored context data is indicative of at least one of:
i) an object history;
ii) an action history;
iii) a trigger history;
iv) a tag movement
v) one or more measured parameters; and,
vi) an elapsed time period; and,
b) the tag processing device is configured to update stored context data in accordance with at least one of:
i) an identified trigger;
ii) an action performed; and,
c) user input commands.

### Claim at position 9

-10) (canceled)

### Claim 11 (depends on 1)

11) A system according to claim 1, wherein the object rules are stored in the tag memory as a plurality of executable byte code snippets, and wherein the tag processing device is configured to repeatedly execute the snippets to identify if a trigger event has occurred.

### Claim at position 11

-13) (canceled)

### Claim 14 (depends on 1)

14) A system according to claim 1, wherein the tag includes an object identifier indicative of at least an object type of the associated objected and wherein the object identifier includes:
a) a first identifier indicative of an object category;
b) a second identifier indicative of an object sub-category.

### Claim 15

15) (canceled)

### Claim 16 (depends on 1)

16) A system according to claim 1, wherein the tag periodically transmits a broadcast message indicative of at least one of:
a) an object type identifier;
b) a tag location;
c) measured parameters; and,
d) context data.

### Claim 17

17) (canceled)

### Claim 18 (depends on 1)

18) A system according to claim 1, wherein the tag:
a) compares the tag location to location restrictions defined in the object rules for the respective object; and,
b) identifies a trigger event if the tag location breaches the location restrictions.

### Claim 19 (depends on 1)

19) A system according to claim 1, wherein the tag is a first tag that:
a) compares the proximity to proximity restrictions for the first and second objects defined in the object rules for the first object; and,
b) identifies a trigger event if the proximity breaches the proximity restrictions.

### Claim 20

20) (canceled)

### Claim 21 (depends on 1)

21) A system according to claim 1, wherein the tag is a first tag that:
a) determines a second tag context using a broadcast message transmitted by a second tag associated with the second object;
b) determines a mutual context using the second tag context and a first tag context; and,
c) identifies a trigger event if the mutual context breaches the mutual context restrictions.

### Claim 22 (depends on 1)

22) A system according to claim 1, wherein a client device:
a) determines a selected object type in accordance with user input commands; and,
b) generates a notification indicative of the tag location when a tag broadcast message having an object identifier of the selected object type is received.

### Claim 23

23) (canceled)

### Claim 24 (depends on 1)

24) A system according to claim 1, wherein the tag:
a) uses sensor data from at least one sensor to determine a measured parameter value; and,
b) identifies a trigger event if the measured parameter value breaches parameter value restrictions.

### Claim at position 23

-28) (canceled)

### Claim 29 (depends on 1)

29) A system according to claim 1, wherein the action includes at least one of:
a) using a tag output device to at least one of:
i) at least partially control equipment;
ii) at least partially control the object; and,
generate a notification;
b) transferring an action message to a client device, the client device being responsive to the action message to at least one of:
i) generate a notification;
ii) perform an action;
iii) forward the action message to a defined destination; and,
iv) cause an event log to be updated;
c) alerting a user to a rule breach;
d) notifying a user of required maintenance;
e) deactivating the object; and
f) causing a transaction to be performed.

### Claim at position 25

-31) (canceled)

### Claim 32 (depends on 1)

32) A system according to claim 1, wherein at least one of:
a) the tag includes an output device including at least one of:
i) an audio output;
ii) a light source; and,
iii a signal generator
b) a power supply;
c) an output device; and
d) at least one sensor.

### Claim 33

33) (canceled)

### Claim 34 (depends on 1)

34) A system according to claim 1, wherein at least one of:
a) the tag:
i) repeatedly transmits broadcast messages separated by a transmission interval; and,
ii) repeatedly listens for a message over a listening interval greater than the transmission interval; and
b) the tag:
i) wakes from a sleep mode;
ii) determines if a trigger event has occurred; and
iii) if a trigger event has not occurred, returns to the sleep mode, wherein the tag is configured to wake from a sleep mode, at least of:
iv) in response to sensing of movement using a movement sensor; and
v) periodically.

### Claim at position 29

35).-45) (canceled)

### Claim 46

46) A method for use in an object monitoring system, the object monitoring system including
a tag associated with a respective object in use, wherein the tag includes:
i) a tag memory configured to store object rules;
ii) a tag transceiver configured to transmit or receive messages; and,
iii) a tag processing device, the method including, in the tag processing device:
(1) determining context data at least partially indicative of a tag context by using at least one of:
a) a received message, including at least one of:
i) a broadcast message from another tag;
ii) a client device message from a client device;
b) sensor data from at least one sensor;
c) user input commands;
d) using stored context data;
(2) using the object rules and the context data to identify a trigger event;
(3) determining an action associated with the trigger event; and,
(4) causing the action to be performed.

### Claim 47

47) A computer program product for use in an object monitoring system including a tag associated with a respective object in use, wherein the tag includes:
i) a tag memory configured to store object rules;
ii) a tag transceiver configured to transmit or receive messages; and,
iii) a tag processing device, the computer program product including computer executable code that when executed by the tag processing device, causes the tag processing device to:
(1) determine context data at least partially indicative of a tag context by using at least one of:
a) a received message, including at least one of:
i) a broadcast message from another tag;
ii) a client device message from a client device;
b) sensor data from at least one sensor;
c) user input commands;
d) using stored context data;
(2) use the object rules and the context data to identify a trigger event;
(3) determine an action associated with the trigger event; and,
(4) cause the action to be performed.

### Claim at position 32

48)-52) (canceled)
