as) United States
`a2) Patent Application Publication 0) Pub. No.: US 2008/0094256 Al
` Koen (43) Pub. Date: Apr. 24, 2008
`
`
`
`US 20080094256A1
`
`(54) DYNAMICALLY CONFIGURABLE
`WIRELESS DEVICE
`Inventor:
`(cB John Koen, Vancouver
`
`(75)
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`Cian ie
`
`D00601
`
`Correspondence Address:
`WebTech Wireless Inc.
`
`Attention Patent Department, Norman Eldridge
`215 - 4299 Canada Way
`Burnaby, BC V5G 113
`(73) Assignee:
`Webtech Wireless Inc.
`
`(21) Appl. No.:
`
`11/585,149
`
`(22)
`
`Filed:
`
`Oct. 24, 2006
`
`(52) U.S. Ch cc cceeecteeeeeneenees 340/988; 340/539.13
`
`(57)
`ABSTRACT
`Awireless device for facilitating for GPS-based asset track-
`ing via a wireless communications network and a centralized
`management system. The wireless device includes dynami-
`cally configurable event profiles which allow the wireless
`device to be dynamically reconfigured and to perform cer-
`tain actions based on a dynamically configurable combina-
`tion of received events.
`
`
`
`10
`
`oN
`
`RAM
`160
`
`
`PERSISENT MEMORY
`150
`SYSTEM SOFTWARE
`152
`STATUS RECORDS
`154
`
`PARAMETER MEMORY
`170
`DEVICE CONFIGURATION
`172
`PROFILE TABLE
`176
`GEOFENCE TABLE
`178
`
`
`
`
`
`i
`
`wae
`
`TOIFROMPC
`
`144
`
`TO/FROM
`WIRELESS
`NETWORK(12)
`
`
`
`
`RF VF
`418
`SATELLITE
`
`
`
`MODEM
`
`146
`
`
`
`<t____—.__}
`
`Exhibit 1029
`Page 01 of 16
`
`
`
`Samsung etal. v. Hardin et al.
`IPR2022-01328
`Exhibit 1029
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`:
`TO/FROM DIGITAL
`139
`442
`SENSORS)
`|
`FROM ANALOG :
`x
`CONTROLLERS |
`DIGITAL
`ANALOG
`
`TELEMETRY|TELEMETRY SENSORS |
`
`
`. areVcdWF WF i
`
`
`122
`112
`COMPUTER DATA
`“
`VEHICLE
`SIGNAL FROM
`132
`TO/FROM}
`
`MANAGEMENT BUS UFZovenicuesus,BUS,SATELLITES(14 140
`SYSTEM (18)
`GPS I/F
`114
`,
`i
`LOCAL
`i
`139
`1200 pig
`|
`COMPUTER
`|
`DATASIGNAL
`RS232 /F
`116
`136
`— fo
`
`vO
`
`440
`
`
`
`
`
`Exhibit 1029
`Page 01 of 16
`
`

`

`Patent Application Publication Apr. 24, 2008 Sheet 1 of 6
`
`US 2008/0094256 Al
`
`MANAGEMENT
`
`SYSTEM 18
`
`FIG.1
`
`WIRELESS
`
`
`
` 12
`NETWORK
`
` CUSTOMER PC 20
`
`
`DEVICE 10
`
`GPSSATELLITES
`
`LOCATOR
`
`Exhibit 1029
`
`Page 02 of 16
`
`Exhibit 1029
`Page 02 of 16
`
`

`

`Patent Application Publication
`
`Apr.24, 2008 Sheet 2 of 6
`
`US 2008/0094256 Al
`
`W901
`
`YALNdWOS
`
`
`
` -WNOISVLiVd
`
`
`
`NOILVYNDISANODADIAZGAYVMLIOSWALSAS
`
`
`
`
`
`eLycSt
`
`
`
`S319gV1l31sOudSQYOO3YSNLVLS
`
`
`
`
`
`
`
`SOWNYWOYS
`
`SYOSNAS
`
`WIS
`
`|.
`
`oer
`
`
`
`A1avlJONAAOAO
`
`BzT
`
`ZtPST
`
`
`
`
`
`TWLISICWOYS/OL
`
`|SHSTIONLNOD
`
`/SYOSN3S
`
`
`
`
`
`VLV¥dY3LNdWOO
`
`SN@STOINSAailenorl
`gEOTLdil|3dWOUS/OL3ceeSume
`
`NOYS/OLzel——7dild/lcrl
`velOzI6E|
`
`vl4aisdoNS
`
`
`(pL)SALITISLYSINSWSOVNV
`SSITSuIMveh
`Sd9WOuSWOIVNOIS
`WOXS/OL(“rLe
`
`
`
`(ZL)MYOMLIN
`
`
`
`(81)WALSAS
`
`¢Old
`
`SLITIALVS
`
`WACOW
`
`OFT
`
`
`
`AYNOWSWYSLSWVeWdWvdAYOWAWLNASISYad
`
`
`
`
`
`
`
`OZTOatOST
`
`Exhibit 1029
`
`Page 03 of 16
`
`Exhibit 1029
`Page 03 of 16
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr.24, 2008 Sheet 3 of 6
`
`US 2008/0094256 Al
`
`SIAR
`OTNWHOICalsnared/lSdOAN2€ZSu
`ANABMLAWATSL|4AMLSWSTSL
`
`
`
`
`SAINGOWW3LSASYAHLOYAOVNVW311d08d
`cllcel
`YANGAMLAWATALYaAldd(>ZezSuy
`
`
`vorcOP
`vieO2TOL
`
`AYVMLIOSWALSAS
`
`S.LNSASSONVAINIOD
`
`CST
`
`Exhibit 1029
`
`Page 04 of 16
`
`€Old
`
`ONVIWOS
`
`YALAYdYALNI
`
`900
`
`NOILVYNSISNOD
`
`eLb
`
`SYSATYG
`
`oly
`
`
`
`Y3AINdSSATAYIM
`
`Exhibit 1029
`Page 04 of 16
`
`

`

`Patent Application Publication Apr. 24, 2008 Sheet 4 of 6
`
`US 2008/0094256 Al
`
`500
`
`200
`
`PROFILE TABLE ENTRY FORMAT
`
`202 ~ PROFILE NUMBER Entry Number
`204 ~ T_WORD
`Binary word indicating triggers used in the entry
`206 ~ T_MASK
`Binary word indicating sufficient and necessary triggers
`208 ~ P_LHYSTERESIS
`Minimum duration all triggers must be active to activate profile
`210 ~ COMMANDS
`Device configuration commands associated with the profile
`212 ~ TIMER_START
`Hysteresis timer start time
`214 ~ P_ACTIVE
`Booleanflag indicating if profile is currently active
`
`FIG. 4
`
`Exhibit 1029
`
`Page 05 of 16
`
`Exhibit 1029
`Page 05 of 16
`
`

`

`Patent Application Publication Apr. 24, 2008 Sheet 5 of 6
`
`US 2008/0094256 Al
`
` START DUTY
`
`
`CYCLE
`
`302
`
`PROFILE MANAGER (426) PROCESS a
`
`EVALUATE ALL ACTIVE
`
`
`EVENTS TO CREATE
`
`
`
`
`
`ACT_T_WORD
`
`
`RETRIEVE NEXT
`310
`
`
`
`
`
`MORE
`PROFILE FROM
`
`
`
`
`PROFILES?
`
`
`PROFILE TABLE
`
`
`RETRIEVE FIRST PROFILE
`332
`
`
`334
`FROM PROFILE TABLE
`
`
`312
`
`
`
`
`
`
`SET P_ACTIVE
`= FALSE
`
`SUFFICIENTEVENTS
`
`STE = T_WORD AND
`
`T_MASK
`
`
`START
`
`314
`HYSTERESIS
`
`
`TIMER FOR
`
`TEST = STE AND
`
`
`PROFILE
`
`
`
`
`ACT_T_WORD
`338
`
`
`
`
`REQUIRED EVENTS
`
` TEST = TEST
`
`
`RTE = T_WORD XOR
` XOR RTW
`
`T_MASK
`
`320
`
`
`TEST = RTE AND
`
`
`ACT_T_WORD
`
`
`
`
`
`
`
`
`
`P_HYSTERESIS?
`340
`
`
`
` OUTUT PROFILE
`COMMANDS
`SET P_ACTIVE =
`TRUE
`
`
`344
`
`
`
`
`SET
`
`
`
`LOAD DEFAULT
` END DUTY CYCLE
`PROFILE
`P_ACTIVE =
`
`
`
`TRUE
`COMMANDS
`350
`
`
`
`
`
`349
`348
`
`
`
`FIG. 5
`
`Exhibit 1029
`
`Page 06 of 16
`
`Exhibit 1029
`Page 06 of 16
`
`

`

`Patent Application Publication
`
`Apr. 24, 2008 Sheet 6 of 6
`
`US 2008/0094256 Al
`
`(epucaes)sisoveysty
`
`pyrooiC]
`pndinoQC]
`pndoC)
`prow1]
`
`e6eea02on[J
`
`zvdnooi[)
`zdro9)[2]
`zougif)
`zygif)
`“somouw[A]
`Saueoy[]
`
`evdreiC]
`
`ermorl
`ereoC)
`evouorl]
`
`revedfaye[]
`e6erse[7]
`
`grimeiO]
`
`gwdyeO)(7)
`gduoC)
`gyeaof]
`
`gindnooi]
`gndegiC)
`gravgiT]
`greyoiCT]
`
`zvdnooi)
`LrdnogC]
`2rdo1fl)
`eye
`
`so0ugjoer
`
`eaeKieeseoeN[A]
`
`ZL¥enOQ)
`elvanoi
`zhmenooT
`fhediegC]
`2rdo1
`ermoi)
`zieoiCJ
`erroo)
`nogsoy[]ageroul)
`wozenoy(]@zeny[)
`
`mansways[gi]
`rivdnooC]
`FLdnogi(]
`pind1)
`pledol]
`geno[]
`wcenoy[)
`
`waneenor(7
`
`
`girdreiC]
`
`sineor)
`
` StdnoojC]
`
`wogewoy([)
`
`gwdineoiCJ
`gmdweQi7]
`grdugi[)
`erooil]
`
`puUc6o]
`o1mdmgi[]
`LLvedogi
`grdrooC]
`ude9OLmde1grdno910]
`oresof)
`iLor)
`grduofl)
`oreoT)
`iLyeugC)
`eymait}-
`no»ono[7]
`wyernoy([)
`wo1einoy[7]
`wysnoy(J
`
`wowepony(]\L4mporg[7]v08
`
`430370O1
`NOWOI
`44304101
`
`NO4Of
`
`on
`
`brdnoof0ordneoT
`Ondinegi(C]
`1idinegi
`omegi
`btsgiC)
`oreorl)
`pvegH)
`movsaC]
`ome2910
`
`sgZ)
`
`eaeSWS(7)NCauz08
`
`sUsA3
`
`Exhibit 1029
`
`Page 07 of 16
`
`Exhibit 1029
`Page 07 of 16
`
`
`
`

`

`US 2008/0094256 Al
`
`Apr. 24, 2008
`
`DYNAMICALLY CONFIGURABLE
`WIRELESS DEVICE
`
`FIELD OF THE INVENTION
`
`[0001] This invention relates to the field of wireless asset
`tracking and fleet operations management.
`
`BACKGROUND OF THE INVENTION
`
`[0002] Ever since the advent of ubiquitous wireless net-
`works and GPSsatellites, specialized wireless devices have
`been installed in vehicles to facilitate fleet operations man-
`agementandin virtually anything that moves or is moved to
`enable asset tracking. In the art, such devices are commonly
`called “locator devices”, referencing their basic functional-
`ity of locating and reporting a physical position of a vehicle,
`trailer or any asset. However, functionality of the locator
`devices is not
`limited to merely location tracking. The
`locator devices interface with many kinds of other devices
`and systems to collect information and data and to control
`operation of external systems. Although typically intended
`to be used with wireless networks to communicate with a
`
`centralized managementsystem,the locator devices are also
`typically capable of independent operation in an event of a
`network failure, for example. In such situations, instead of
`immediate reporting, the locator devices typically operate
`according to pre-defined rules and/or store the information
`they gather in local memory.
`[0003] When used by fleet operators, the locator devices
`provide a wealth of useful functions such as efficient vehicle
`scheduling, dispatching and location management, monitor-
`ing driver behaviour and compliance with traffic rules and
`government regulations, fuel
`tax recovery, detailed time
`tracking, and enhanced driver services such as real-time
`mapping, Internet access, credit card processing, and many
`others.
`
`In other applications, locator devices of all kinds
`[0004]
`are often used to track high-value assets ranging from cars
`and construction equipment to pallet shipments and even
`small packages.
`[0005] The use of locator devices in such a variety of
`applications naturally imposes a myriad of different require-
`ments, both physical (e.g., size, power consumption, pro-
`cessing speed, storage capacity, etc.), and operational(e.g.,
`software functionalities for monitoring, tracking, recording,
`controlling, etc.). Furthermore, even a single locator device,
`used for a single application, while having a single set of
`physical
`specifications, may have different
`functional
`requirements depending on the particular mode or location
`of use.
`
`To date, manufacturers of the locator devices have
`[0006]
`not adequately overcome these limitations. Specifically,
`while varying physical requirements have been usually met
`by designing the locator devices for a specific market (for
`example to be installed in vehicles or containers), the only
`solution to the varying functional requirements has been to
`develop custom software and firmware loads for each cus-
`tomer and/or application. There are many disadvantages to
`that solution: design and support costs requirement
`to
`develop and maintain a multitude of software streams; slow
`request-to-implementation time as any requested feature has
`to be integrated into existing software and the entire fleet of
`devices has to be upgraded; and lack of flexibility as each
`locator device can only operate a single feature set at any
`
`Exhibit 1029
`
`Page 08 of 16
`
`one time. Furthermore, this cumbersome approach did not
`solve the issue of a single locator device, which may have
`different operational profiles not based on the customer who
`is using it, but on a more transient quality such as where the
`locator device may be located or what the vehicle or asset
`with that locator device is doing at that time.
`
`SUMMARY OF THE INVENTION
`
`[0007] A method of dynamically operating a locator
`device, including the steps of defining a plurality of events
`where each of the events represents an operational status of
`the locator device. The methodincluding the step of defining
`a plurality of triggers where each of the triggers is a
`dynamically configurable contemporaneously occurring
`combination of the events and defining a plurality of event
`profiles where each of the event profiles is a user-config-
`urable dynamic association between oneofthe triggers; and
`a dynamically configurable set of device commands. The
`method further including responding to a contemporane-
`ously occurring subset of the events by evaluating the
`contemporaneously occurring subset of the events against
`the triggers of each of the event profiles and activating one
`of the event profiles by processing the set of device com-
`mands corresponding to the event profile whenever the
`contemporaneously occurring subset of the events corre-
`sponds to the trigger of the event profile
`[0008] A dynamically operable locator device comprising
`a definition of a plurality of events where each of the events
`represents an operational status of the locator device, a
`definition a plurality of triggers where each ofthe triggers is
`a dynamically configurable contemporaneously occurring
`combination of the events, and a definition a plurality of
`event profiles where each of the event profiles is a user-
`configurable dynamic association between oneofthe trig-
`gers and a dynamically configurable set of device com-
`mands. The device further comprising means for responding
`to a contemporaneously occurring subset of the events by
`evaluating the contemporaneously occurring subset of the
`events against the triggers of each of the event profiles and
`meansfor activating one of the event profiles by processing
`the set of device commands corresponding to the event
`profile whenever the contemporaneously occurring subset of
`the events corresponds to the trigger of the eventprofile.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0009] A better understanding of the present invention can
`be obtained when the following detailed description of the
`preferred embodimentis considered in conjunction with the
`following drawings, in which:
`[0010]
`FIG. 1 isa high level diagram ofa priorart wireless
`communication system.
`[0011]
`FIG. 2 is a block diagram of a dynamically con-
`figurable locator device according to one embodimentof the
`invention.
`
`FIG. 3 is a block diagram of a System Software
`[0012]
`module of the dynamically configurable locator device
`shown in FIG. 2.
`
`FIG. 4 is a high level diagram illustrating a format
`[0013]
`of entries in a Profile Table stored in the dynamically
`configurable locator device shown in FIG.2.
`[0014]
`FIG. 5 is a flowchart illustrating the operation of a
`Profile Manager process running as a module of the System
`Software shown in FIG.3.
`
`Exhibit 1029
`Page 08 of 16
`
`

`

`US 2008/0094256 Al
`
`Apr. 24, 2008
`
`FIG. 6 is an illustration of a software profile
`[0015]
`configuration tool according to one embodiment of the
`invention.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`
`[0016] Notice Regarding Copyrighted Material
`[0017] A portion of the disclosure of this patent document
`contains material which is subject to copyright protection.
`The copyright owner has no objection to the facsimile
`reproduction by anyone of the patent documentor the patent
`disclosure as it appears in the Patent and Trademark Office
`file or records, but otherwise reserves all copyright rights
`whatsoever.
`[0018] Wireless Communication System
`[0019] Referring to FIG. 1, a wireless communication
`system according to one embodiment of the invention is
`shown. The wireless communication system comprises a
`plurality of locator devices 10, a wireless network 12, a
`plurality of GPSsatellites 14, the Internet 16, a Management
`System 18, and a plurality of customer computers 20. The
`locator device 10 is a wireless communication device,
`commonly installed in a vehicle or a trailer to provide
`location-based communication services
`such as,
`for
`example, asset tracking and reporting, Internet access, voice
`and text communications, and telemetry monitoring or con-
`trol. Devices such as the locator devices 10, albeit not
`containing the novel elements recited and claimed herein,
`are well known in the art. For example, WebTech Wireless
`Inc., of Burnaby, British Columbia, produces and markets
`several models of the locator devices 10 underthe trademark
`WebTech Locator™.In one embodiment, the locator devices
`10 obtain position information from the GPSsatellites 14 via
`integrated or external GPS modems and antennas (not
`shown). Methods and apparatuses for obtaining GPS-based
`location information are well knownin the art. For example,
`WebTech Locator™ devices mentioned above include inte-
`
`grated GPS modems. The locator devices 10 are connected
`to the wireless communication network 12, which may be
`any available cellular, satellite, microwave or radio commu-
`nication network based on any communication standard
`such as, for example, GSM, GPRS, CDMA, CDPDor WiFi.
`Modes and methods of interconnection to such wireless
`communication networks are well known in the art and are
`
`not further described herein. The Management System 18 is
`also connected to the wireless network 12 via the Internet
`
`16. The Management System 18 provides portal-based loca-
`tor device 10 managementfunctions, such as remote device
`configuration and upgrades, data bridging, device monitor-
`ing, tracking and reporting, to Management System sub-
`scribers. The Management System 18 is well known in the
`art and is not described further herein. For example, WebT-
`ech Wireless Inc. of Burnaby, British Columbia, produces
`and markets a Management System under the name Quad-
`rant Vehicle Services System™. In order to utilize the
`locator device 10 management functions provided by the
`Management System 18, the subscribers of the Management
`System 18 access the Management System from PCs 20
`using web browsers (not shown) or any another remote
`access method knownin the art
`
`[0020] Locator Device
`[0021] Referring now to FIG. 2, the locator device 10 is
`shown in detail at 99 according to one embodimentof the
`invention. The locator device 10 comprises a microproces-
`
`Exhibit 1029
`
`Page 09 of 16
`
`sor 100, an I/O interface 110, a persistent memory 150, a
`RAM 160, a parameter memory 170, and a Subscriber
`Identity Module (SIM) 180. The functionality of these
`modules is described below.
`
`/O
`[0022]
`the I/O interface 110
`Still referring to FIG. 2,
`[0023]
`enables communications between the locator device 10 and
`other devices, integrated or external. The I/O interface 110
`includesa plurality of telemetry interfaces. Specifically, I/O
`interface 110 includes an analog telemetry interface 112, a
`digital telemetry interface 122, a vehicle bus interface 114,
`an RS232 interface 116, a radio (RF) interface 118, and a
`GPS interface 120. The analog telemetry interface 112
`provides a connection 130 to a plurality of analog sensors
`(not shown) which generate variable voltage signals to
`indicate their status. A common example of an analog sensor
`is a thermometer (not shown), which outputs temperature
`measurements as a voltage-graduated analog signal. The
`analog telemetry interface 112 further includes an analog-
`to-digital
`(A/D) converter (not shown), which converts
`received analog signals to their digital representations that
`can be further processed by the microprocessor 100. The
`operation of A/D converters is well-known in the art and is
`not described further herein. The digital telemetry interface
`122 provides a bidirectional connection to devices which
`generate, or are controlled by, digital signals. More specifi-
`cally, the digital telemetry interface 122 includes a plurality
`of digital inputs 142 and plurality of digital outputs 143. A
`common example of a device connected to the digital input
`142 is a door-mounted sensor which generates a logic HIGH
`signal when a door opens. A common example of a device
`connected to the digital output 143 is a relay which controls
`someoperational aspect of a vehicle in which it is installed,
`for example, disabling the vehicle’s fuel pump uponreceiv-
`ing a logic HIGHsignal from the digital telemetry interface
`122. The vehicle bus interface 114 provides a bidirectional
`connection 132 to various vehicle systems, for example
`J1587/J1708, OBD II or CANBUScompliant systems.
`[0024]
`Still referring to FIG. 2, the GPS interface 120
`enables receiving GPS location information from the GPS
`satellites 14 through a GPS antenna 141. A person skilled in
`the art will appreciate that
`the GPS interface 120 may
`comprise an integrated or external GPS receiver and may
`further utilize any appropriate GPS antenna type. For
`example,
`the WebTech 6000 Locator™,
`from WebTech
`Wireless Inc. of Burnaby, British Columbia,
`integrates a
`GPS receiver and is typically equipped with an external
`active GPS antenna. The RF interface 118 provides a wire-
`less connection 118 to the wireless network 12 via a radio
`
`antenna 139. For example, the WebTech 6000 Locator™
`device integrates a GSM/GPRS modem which can connect
`to any available GSM/GRPSnetwork. The RF interface 118
`is further used to receive a remote computer data signal 144
`from the Management System 18. The RS232 interface 116
`provides a primary serial connection 134 and a secondary
`serial connection 136. The primary serial connection 134
`typically connects to a computer or a navigation system
`co-located with the locator device 10. The primary serial
`connection 134 can be used for a variety of purposes, such
`as for local managementofthe locator device 10 via a laptop
`connected thereto that generates a local computer data signal
`148 containing device commands. The meaning of the term
`‘device commands’ will be described below. In another
`
`example, the primary serial connection 134 can be con-
`
`Exhibit 1029
`Page 09 of 16
`
`

`

`US 2008/0094256 Al
`
`Apr. 24, 2008
`
`nected to an in-vehicle navigation system to output thereto
`mapping and location information received from the Man-
`agement System 18 and the GPSsatellites 14 via the RF
`interface 118 and the GPS interface 120, respectively. The
`secondary serial connection 136 can be used to connect to a
`communication device, such as a satellite modem 146, to
`provide a primary or a backup connection to the wireless
`network 12 via the radio antenna 139 or another antenna (not
`shown) appropriate for the specific type of wireless network
`12 and the connection method used. In one embodimentof
`the invention, should the RF interface 118 or the primary
`wireless network 12 become unavailable,
`the secondary
`serial connection 136, via the satellite modem 146, can be
`used to a re-establish a connection to the Management
`System 18 via a satellite communication network.
`[0025] A person skilled in the art will appreciate that the
`interfaces comprising the I/O 110 described above are
`merely examples of possible configurations of the locator
`device 10. A variety of interfaces, connections, and signals
`may be implemented in the locator device 10 as may be
`appropriate for a particular application.
`[0026] Memory
`[0027]
`Still referring to FIG. 2, the persistent memory 150
`is a non-volatile memory which contains System Software
`152 and a database of status records 154. The database of
`status records 154 is used to log and store all measurements
`and events received, processed or generated by the locator
`device 10. The number of status records stored in the
`database of status records 154 is limited only by the size of
`the non-volatile persistent memory 150 installed in the
`locator device 10. The System Software 152 comprises a
`collection of computer encoded instructions, which direct
`the microprocessor 100 to perform functions of the locator
`device 10. The System Software 152 will be described in
`further detail below in reference to FIG. 3 and FIG.6.
`
`Still referring to FIG. 2, the RAM 160 is used by
`[0028]
`the locator device 10 to store various information of a
`temporary nature. Operation of the RAM 160 is well known
`in the art and will not be further described herein.
`
`Still referring to FIG.2, the parameter memory 170
`[0029]
`is a non-volatile memory which contains a device configu-
`ration 172, a Profile Table 176, and a Geofence Table 178.
`The device configuration 172 is used to store a plurality of
`operational parameters which define all dynamically con-
`figurable operational aspects of the locator device 10. A
`person skilled in the art will appreciate that the particular
`operational parameters for each type of the locator device 10
`depend on the specific implementation and functionality of
`the locator device. The device configuration 172 can also be
`modified by the Management System 18, by a user operating
`a terminal connectedto the primary serial connection 134, or
`by the System Software 152 in response to occurrence of
`certain events. The Profile Table 176 contains a plurality of
`event profiles which are used to dynamically respond to
`events by performing certain actions or changing the device
`configuration 172. The meaning of the terms ‘events’ and
`‘actions’ will be described below.
`
`Still referring to FIG. 2, the Geofence Table 178
`[0030]
`defines a plurality of geofences configured on the locator
`device 10. A geofence is a virtual boundary that can be
`configured on the locator device 10 using GPS co-ordinates.
`Geofences are typically configured on the locator device 10
`by using device commandsthat are automatically generated
`by a software geofence configuration tool (not shown). A
`
`Exhibit 1029
`
`Page 10 of 16
`
`geofence can define any area, for example, a work site,
`customersite, yard, home depot, area that should not be
`traveled through (exclusion fence), or any other type of area.
`As will be described further below, when, based on the
`location information received from the GPSsatellites 14, the
`locator device 10 enters or leaves a geofence area, an event
`is generated and actions can be taken or device configuration
`172 altered. There are generally three types of geofencesthat
`can be configured on the locator device 10 in the Geofence
`Table 172. Thefirst type is a polygon geofence created by
`drawing a polyon enclosing a desired area on a map. The
`second type is a route geofence, a virtual boundary created
`along a designated route, which may span several hundred
`miles or kilometres. For example, the route geofence can be
`created along a tow truck operator’s “Beat”, or an armored
`truck route along a stretch of highway between cities. The
`third type is a circular geofence that is created by defining
`a center location and a radius.
`
`Still referring to FIG. 2, the SIM 180 is used to
`[0031]
`store information that identifies the locator device 10 to the
`wireless network 12. The use of SIM 180 is well known in
`the art and will not be further described herein. A person
`skilled in the art will appreciate that, depending on the type
`of the wireless network 12 used with the particular locator
`device 10, a different methodfor identification of the locator
`device to the wireless network may be used.
`[0032] Apperson skilled in the art will appreciate that while
`the described embodiment uses the microprocessor 100 and
`memory modules 150, 160, 170 and 180, the locator device
`10 may also be implemented using FPGA or ASIC tech-
`nologies as alternative methods of encoding, storing and/or
`processing instructions which define the locator device
`operation. The choice of technology, 1.e., microprocessor,
`FPGA, ASIC, virtual machine, or any other, will depend on
`the particular device functionality desired and on the cost,
`manufacturing, and other application constraints.
`[0033]
`System Software
`[0034] Referring to FIG. 3, key aspects of the System
`Software 152 are shown in greater detail according to one
`embodiment of the invention. The System Software 152
`comprises a number of functional components including a
`Profile Manager 402 and Other System Modules 404 for
`implementing the functionality of the locator device 10, a
`CommandInterpreter 406 for managing the operation of the
`locator device, and Drivers 407 for controlling the interfaces
`112, 116, 118, 120 and 122 of the I/O 110. The Profile
`Manager 402 receives events from the drivers 407 via an
`event input 420, processes the events according to triggers
`(as will be described below) to determine what eventprofile
`needsto be activated and what device commandsneedto be
`
`output to the Command Interpreter 406 via a command
`output 421. The CommandInterpreter 406 provides a man-
`agement interface to the locator device 10 by interpreting
`device commandsto cause the locator device to perform
`actions or to change the device configuration 172 as speci-
`fied in the commands. The device commandsinterpreted by
`the Command Interpreter 406 can be received in the local
`computer data signal 148 from a local computer terminal, in
`the remote computer data signal 144 from the Management
`System 18, or via the command output 421 from the Profile
`Manager 402. The operation of the Profile Manager 402 and
`the meaning of the terms ‘events’, ‘triggers’, ‘event profiles’
`and ‘actions’ will be described below. Well knownaspects of
`
`Exhibit 1029
`Page 10 of 16
`
`

`

`US 2008/0094256 Al
`
`Apr. 24, 2008
`
`the locator device 10 are implemented in the Other System
`Modules 404 and are not further described herein.
`
`[0035] Drivers
`[0036]
`Still referring to FIG. 3, in the described embodi-
`ment of the invention, the drivers 407 include a wireless
`driver 410, an RS232 driver 412, a GPS driver 414, and a
`telemetry driver 416. The wireless driver 410 enables com-
`munications to/from the wireless network 12 via the RF
`
`interface 118. In addition to enabling network-specific com-
`munication functions, the wireless driver 410 further enables
`transmitting and receiving the remote computer data signal
`144 to and from the Management System 18 via the wireless
`network 12 (see FIG. 2). Where the remote computer data
`signal 144 contains device commands, they are forwarded
`by the wireless driver 410 to the CommandInterpreter 406.
`The RS232 driver 412 enables communications to and from
`a local computer or data terminal via the primary serial
`connection 134, and to/from a satellite network via the
`satellite modem 146 connected to the secondary serial
`connection 136 as previously described in reference to FIG.
`2. As device commands may bereceived via either of the
`serial connections 134 and 136,
`the RS232 driver 412
`forwards any received device commands to the Command
`Interpreter 406. The GPS driver 414 enables communication
`with the GPS interface 120 for receiving position informa-
`tion from the GPSsatellites 14 as was previously described
`in reference to FIG. 2. The telemetry driver 416 enables
`communication to and from the vehicle bus interface 114,
`the digital telemetry interface 122 and the analog telemetry
`interface 112 and devices connected thereto. The telemetry
`driver 416 controls all operational aspects of these interfaces
`(112, 114, 122) enabling digital and analog output, and
`analog input via the A/D converter described above in
`reference to FIG. 2. In some embodimentsof the invention,
`the telemetry driver 416 may further enable advanced func-
`tions such as connection to a digital handset for voice
`communications through the locator device 10. A person
`skilled in the art will appreciate that
`the drivers 407
`described herein are well known in the art and do not limit
`
`the function or the spirit of the invention as they may be
`implemented to enable any functionality required for a
`particular application of the locator device 10.
`[0037] Events, Triggers, Configuration Commands and
`Profiles
`
`[0038] As described above, the Profile Manager 402 and
`the CommandInterpreter 406 modules of the System Soft-
`ware 152 control the operation of the locator device 10 by
`processing event profiles, events,
`triggers, device com-
`mands, configuration parameters and actions. The terms
`‘event profiles’,
`‘events’,
`‘triggers’,
`‘device commands’,
`“configuration parameters’ and ‘actions’ in the context ofthis
`embodiment, are explained below.
`[0039] An event profile is a user-configurable dynamic
`association between (a) events and (b) device commands
`that represent actions and/or configuration parameters. More
`specifically, in the described embodiment, eventprofiles are
`stored in the Profile Table 176 in the format that will be
`
`described below in reference to FIG. 5. Each event profile
`has a trigger, which is a dynamically configurable combi-
`nation of events against which contemporaneous occurring
`events are evaluated to determine whether the eventprofile
`should becomeactive. Each event profile also has a dynami-
`cally configurable collection of device commands which are
`
`Exhibit 1029
`
`Page 11 of 16
`
`output to the CommandInterpreter 406 to implement the
`actions and/or configuration parameters associated with the
`active profile.
`[0040] An eventis an operational condition of the locator
`device 10. A list of events, according to one embodimentof
`the invention,
`is shown in Table 1 below. By way of
`explanation, it can be noted that geofence crossing events
`(6-11 and 14-19) can correspond to either polygon or route
`geofences stored in the Geofence Table 178. In this embodi-
`ment of the invention, a single circular geofence is imple-
`mented andits information is also stored in the Geofence
`
`Table 178. However, a person skilled in the art will appre-
`ciate that any number of any type of geofences may be
`configured on the locator device 10 limited only by the
`specifications of the device itself and requirements of a
`specific application. As will be described further below, the
`Profile Manager 402 accepts events as inputs and evaluates
`them according to event profile triggers to determine which
`event profile stored in the Profile Table 176 should be
`activated.
`
`[0041] A trigger is a dynamically configurable Boolean
`combination of events, which, in one embodiment of the
`invention, will cause the Profile Manager 402 to activate an
`event profile stored in the Profile Table 176. The triggers
`may be dynamically configured,
`i.e., the combination of
`events defined by device commandsissued to the Command
`Interpreter 406 by (a) users via the primary serial connection
`136 or via the Management System 18, or
`(b)
`issued
`automatically by the Profile Manager 402 as a consequence
`of event processing. A person skilled in the art will appre-
`ciate that non-Boolean logic for defining dynamically con-
`figurable combinations of events (e.g., fuzzy logic or other
`forms of sequential or combinatorial logic) may be used for
`specific applications, where advantageous.
`[0042] A device commandisa string, formatted according
`to a pre-defined syntax, which conveys operational instruc-
`tions and/or configuration parameters to the CommandInter-
`preter 406 in order to make the locator device 10 perform an
`action or to change the device configuration 172.
`[0043] An action represents a function(s) of the locator
`device 10, which can be implemented via one or more
`device command. For example, an action may be turning on
`a specific telemetry output or sending an alarm to the
`in-vehicle navigation system connected to the primary serial
`interface 134.
`
`In the context of this invent