AU2014253558A1 - Vehicular light box and computerised system for monitoring one or more vehicles - Google Patents

Vehicular light box and computerised system for monitoring one or more vehicles Download PDF

Info

Publication number
AU2014253558A1
AU2014253558A1 AU2014253558A AU2014253558A AU2014253558A1 AU 2014253558 A1 AU2014253558 A1 AU 2014253558A1 AU 2014253558 A AU2014253558 A AU 2014253558A AU 2014253558 A AU2014253558 A AU 2014253558A AU 2014253558 A1 AU2014253558 A1 AU 2014253558A1
Authority
AU
Australia
Prior art keywords
processing system
vehicle
data
computerised
location
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
AU2014253558A
Inventor
Alexander Green
Evan Karjalainen
Vladmir Lasky
Nathan Parrott
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PRECISION TRACKING Pty Ltd
Original Assignee
PREC TRACKING Pty Ltd
PRECISION TRACKING Pty Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
Application filed by PREC TRACKING Pty Ltd, PRECISION TRACKING Pty Ltd filed Critical PREC TRACKING Pty Ltd
Priority to AU2014253558A priority Critical patent/AU2014253558A1/en
Publication of AU2014253558A1 publication Critical patent/AU2014253558A1/en
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=52011526&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=AU2014253558(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application status is Abandoned legal-status Critical

Links

Abstract

A vehicular light box and computerised system is disclosed for monitoring vehicles. In one aspect, the system includes a plurality of computerised devices, a server processing system, and a client processing system, wherein: each computerised device is associated with one of the vehicles, computerised device includes a location receiver and a wireless communication module, wherein each computerised device is configured to: obtain, via the location receiver, location data indicative of locations of the vehicle over time; and transfer, via the wireless communication module, a plurality of packets indicative of the location data; the server processing system is configured to: receive the plurality of packets indicative of a location of the vehicles; transfer, via a network, tracking data indicative of at least a portion of the received packets; and the client processing system is configured to: receive, from the server processing system, the tracking data; and present, using the tracking data, a tracking interface indicative of the location of the vehicles. F-UR 1

Description

- 1 VEHICULAR LIGHT BOX AND COMPUTERISED SYSTEM FOR MONITORING ONE OR MORE VEHICLES Field of Invention [0001] The present invention relates to a vehicular light box and a computerised system for monitoring one or more vehicles. Background [0002] A number of problems currently exist for employers which utilise drivers to deliver goods or provide services to customers or members. Additionally, a number of problems exist for customer's who order the good or service to be provided by a vehicle at a requested destination. [0003] For example, some employers have employees which deliver goods or services to customers using their private vehicle. This is quite common in the freshly cooked food industry (e.g. pizza home delivery) where delivery drivers may use their private vehicle to deliver the ordered food to the customer. However, it is generally not desirable for the employee to have their private vehicle branded with advertising. In the event that an employee's vehicle is branded with the advertising, it can be difficult for the employer to arrange for the advertising to be removed from the vehicle after the employee ceases employment. [0004] In the ordered food industry, it can also be difficult for the store's cooking staff to schedule the cooking of fresh food given delivery drivers may be out of the store currently completing other deliveries. For example, in relation to home delivered pizza, cooking staff may attempt to estimate when a driver will return and then arrange for the pizza to be placed in the oven at predetermined time prior to the estimated return of the driver. However, the driver may be delayed for various reasons, therefore the quality of the delivered pizza may suffer as a result of cooling in store prior to finally being picked up for delivery.

-2 [0005] Furthermore, it is known that certain delivery drivers may take unnecessary driving risks or break particular driving rules (i.e. speeding) when delivering the ordered goods or services. In the event that advertising is associated with the delivery driver's vehicle, such driving can damage the store's brand as it may be perceived that the employer endorses such behaviour by it's staff. Furthermore, the employer may be responsible for at least partial payment of any damage to third party property due to the dangerous driving. In other cases, the driver may not be attempting to reach the requested destination a timely manner. In this case, it can be difficult for the employer to be aware that such activities are occurring by their drivers as generally as they may be quite busy running other aspects of the business. [0006] It is also quite frustrating for customers of ordered goods or services who may not be provided with an accurate estimated time of arrival of the vehicle. In some instances, a message may be relayed to the customer when the order is first placed indicating an estimated time of arrival based on a delivery schedule. However, it is common that the vehicle either arrives much earlier or later than indicated for various reasons (traffic congestion, cancellation of an order, etc.). Other alternatives include providing the customer with a temporal window which can be highly frustrating for the customer who may need to stay at the destination for the entire temporal window. Updated temporal windows (typically later delivery windows) may also be provided to the customer throughout the day which may further frustrate the customer. [0007] Therefore, there is a need to alleviate one or more of the above mentioned problems or provide a useful alternative. [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 acknowledgment or admission or any form of suggestion that the prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavour to which this specification relates.

-3 Summary of Invention [0009] In a first aspect there is provided a vehicular light box for a vehicle, including: a housing including advertising and a securing arrangement to releasably secure the vehicular light box to a portion of the vehicle; an electrical cable for electrical connection to a vehicular electrical power source; one or more lights for illuminating the advertising upon receiving electrical power via the electrical cable; a computerised device in electrical connection with the electrical cable, wherein the computerised device includes a location receiver and a wireless communication module, wherein the computerised device is configured to: obtain, via the location receiver, location data indicative of locations of the vehicle over time; and transfer, via the wireless communication module, a plurality of packets indicative of the location data to a server processing system for monitoring the location of the of the vehicle over time. [0010] In certain embodiments, the computerised device includes an accelerometer, wherein the computerised device is configured to: obtain acceleration data of the vehicle; determine if an acceleration of the vehicle indicated by the acceleration data meets or exceeds an acceleration threshold indicative of dangerous driving; and wherein at least some of the packets are indicative of whether dangerous driving has been detected for the vehicle. [0011] In certain embodiments, the computerised device determines the speed of the vehicle based on the location data, wherein at least some of the packets are indicative of the speed of the vehicle. [0012] In certain embodiments, the computerised device determines a heading of the vehicle based on the location data, wherein at least some of the packets are indicative of the heading of the vehicle.

-4 [0013] In certain embodiments, the computerised device includes an internal rechargeable battery, wherein the internal rechargeable battery recharges upon receiving electrical power from the vehicular electrical power source via the electrical cable. [0014] In certain embodiments, the housing has attached thereto a contactless readable identifier to enable a reading device to read an identity associated with the vehicular light box in order to associate the identity of the vehicular light box with an identity of the driver. [0015] In certain embodiments, the contactless readable identifier is an RFID device. [0016] In a second aspect there is provided a system for monitoring vehicles, wherein the system includes a server processing system and a client processing system, wherein: the server processing system is configured to: receive a plurality of packets indicative of a location of the vehicles over time from computerised devices associated therewith; transfer, via a network, tracking data indicative of at least a portion of the received packets to the client processing system; and the client processing system is configured to: receive, from the server processing system, the tracking data; and present, using the tracking data, a tracking interface indicating the location of the vehicles. [0017] In certain embodiments, the tracking interface includes a map including a marker indicative of each vehicle. [0018] In certain embodiments, the tracking interface includes a temporal marker indicative of a predetermined estimated travel time to a central meeting location. [0019] In certain embodiments, the client processing system includes: -5 a first display device presenting a registration interface enabling one or more drivers to register an association with one of the respective computerised devices; and a second display device in electrical connection with the which presents the tracking interface; wherein the first display device and the second display device present the respective interfaces simultaneously. [0020] In certain embodiments, the client processing system includes a contactless reading device for reading contactless readable devices associated with the computerised devices, wherein upon reading one of the contactless readable devices, the client processing system in combination with the server processing system associates respective associated computerised device with an identity of one of the drivers, wherein the association is stored by the server processing system. [0021] In certain embodiments, the client processing system is a tablet processing system, wherein the first display device is a touch screen interface of the tablet processing system, and the second display device is in data communication via a data cable with the tablet processing system. [0022] In certain embodiments, the client processing system transfers a request to a mapping server processing system to determine a driving route for one of the vehicles, wherein the driving route is received from the mapping server processing system and presented by the client processing system. [0023] In a third aspect there is provided a system for monitoring vehicles, wherein the system includes a plurality of computerised devices, a server processing system, and a client processing system, wherein: each computerised device is associated with one of the vehicles, computerised device includes a location receiver and a wireless communication module, wherein each computerised device is configured to: obtain, via the location receiver, location data indicative of locations of the -6 vehicle over time; and transfer, via the wireless communication module, a plurality of packets indicative of the location data; the server processing system is configured to: receive the plurality of packets indicative of a location of the vehicles; transfer, via a network, tracking data indicative of at least a portion of the received packets; and the client processing system is configured to: receive, from the server processing system, the tracking data; and present, using the tracking data, a tracking interface indicative of the location of the vehicles. [0024] In certain embodiments, at least some of the computerised devices are associated with a portable light box which is releaseably secured to the respective vehicle. [0025] In certain embodiments, the server processing system is configured to: receive order data indicative of a order placed using a user device; receive association data for associating one of the vehicles with the order; generate vehicle interface data, wherein the vehicle interface data is generated using the location data of the respective vehicle; and transfer the vehicle interface data to the user device. [0026] In certain embodiments, the vehicle interface includes an estimated time of arrival of the respective vehicle to a destination associated with the order. [0027] In certain embodiments, the server processing system determines, based on the location data for the respective vehicle if the respective vehicle is within a threshold temporal or spatial threshold of the destination, wherein in the event of a successful determination, the server processing system transfers an alert to the user device indicating that the vehicle is approaching the destination.

-7 [0028] In certain embodiments, the vehicle interface includes at least one of: a driver's name of the respective vehicle; and a digital photograph of the driver of the respective vehicle. [0029] Other aspects and embodiments will be appreciated throughout the detailed description. Brief Description of the Figures [0030] 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. [0031] Figure 1 illustrates a functional block diagram of an example processing system that can be utilised to embody or give effect to a particular embodiment; [0032] Figure 2 illustrates an example network infrastructure that can be utilised to embody or give effect to a particular embodiment; [0033] Figure 3 illustrates an example of a vehicular light box; [0034] Figure 4 illustrates an example of the vehicular light box of Figure 3 releasably secured to a roof of a vehicle; [0035] Figure 5A illustrates a removable base plate of the vehicular light box of Figure 3 which has various electrical components secured thereto; [0036] Figure 5B illustrates a functional block diagram of a computerised device of the vehicular light box; [0037] Figure 6 illustrates a system diagram for an example system for monitoring one or more vehicles; -8 [0038] Figure 7 represents an example user interface presented via the display device of the client processing system; [0039] Figure 8 represents another example of the user interface with a speeding notification; [0040] Figure 9 represents a tablet processing system of the client processing system presenting an example registration interface for a driver; [0041] Figure 10 represents the tablet processing system of the client processing system presenting an example location searching interface; [0042] Figure 11 represents the tablet processing system of the client processing system presenting a route to a location selected from the location searching interface; [0043] Figure 12 represents an example speeding report interface generated using the the client processing system; [0044] Figure 13 represents an executive user interface displayed by a user processing system operated by an executive user in communication with the server processing system; [0045] Figures 14 to 17 illustrates various example reports generated and presented to an authorized user in relation monitored jobs; [0046] Figure 18 illustrates a system diagram of another example system for monitoring one or more vehicles and providing arrival information to a user via a user device; [0047] Figure 19 illustrates a system diagram of another example system for monitoring one or more vehicles and providing arrival information to a user via a user device; -9 [0048] Figure 20 illustrates a system diagram of another example system for monitoring one or more vehicles and providing arrival information to a user via a user device; [0049] Figure 21 illustrates a schematic of an example user device presented with an example vehicle interface providing arrival information to the user; and [0050] Figure 22 illustrates a schematic of the user device of Figure 21 presenting an arrival alert. Description of Preferred Embodiments [0051] 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. In the figures, incorporated to illustrate features of an example embodiment, like reference numerals are used to identify like parts throughout the figures. Example processing system and network [0052] A particular embodiment can be realised using a processing system, an example of which is shown in Fig. 1. In particular, the processing system 100 generally includes at least one processor 102, or processing unit or plurality of processors, memory 104, at least one input device 106 and at least one output device 108, coupled together via a bus or group of buses 110. In certain embodiments, input device 106 and output device 108 could be the same device. An interface 112 also can be provided for coupling the processing system 100 to one or more peripheral devices, for example interface 112 could be a PCI card or PC card. At least one storage device 114 which houses at least one database 116 can also be provided. The memory 104 can be any form of memory device, for example, volatile or non-volatile memory, solid state storage devices, magnetic devices, etc. The processor 102 could include more than one distinct processing device, for example to handle different functions within the processing system 100. [0053] Input device 106 receives input data 118 and can include, for example, a keyboard, a pointer device such as a pen-like device or a mouse, audio receiving device for - 10 voice controlled activation such as a microphone, data receiver or antenna such as a modem or wireless data adaptor, data acquisition card, etc.. Input data 118 could come from different sources, for example keyboard instructions in conjunction with data received via a network. Output device 108 produces or generates output data 120 and can include, for example, a display device or monitor in which case output data 120 is visual, a printer in which case output data 120 is printed, a port for example a USB port, a peripheral component adaptor, a data transmitter or antenna such as a modem or wireless network adaptor, etc.. Output data 120 could be distinct and derived from different output devices, for example a visual display on a monitor in conjunction with data transmitted to a network. A user could view data output, or an interpretation of the data output, on, for example, a monitor or using a printer. The storage device 114 can be any form of data or information storage means, for example, volatile or non-volatile memory, solid state storage devices, magnetic devices, etc.. [0054] In use, the processing system 100 is adapted to allow data or information to be stored in and/or retrieved from, via wired or wireless communication means, the at least one database 116 and/or the memory 104. The interface 112 may allow wired and/or wireless communication between the processing unit 102 and peripheral components that may serve a specialised purpose. The processor 102 receives instructions as input data 118 via input device 106 and can display processed results or other output to a user by utilising output device 108. More than one input device 106 and/or output device 108 can be provided. It should be appreciated that the processing system 100 may be any form of terminal, server, specialised hardware, or the like. [0055] The processing device 100 may be a part of a networked communications system 200, as shown in Fig. 2. Processing device 100 could connect to network 202, for example the Internet or a WAN. Input data 118 and output data 120 could be communicated to other devices via network 202. Other terminals, for example, thin client 204, further processing systems 206 and 208, notebook computer 210, mainframe computer 212, PDA 214, pen based computer 216, server 218, etc., can be connected to network 202. A large variety of other types of terminals or configurations could be utilised. The transfer of information - 11 and/or data over network 202 can be achieved using wired communications means 220 or wireless communications means 222. Server 218 can facilitate the transfer of data between network 202 and one or more databases 224. Server 218 and one or more databases 224 provide an example of an information source. [0056] Other networks may communicate with network 202. For example, telecommunications network 230 could facilitate the transfer of data between network 202 and mobile or cellular telephone 232 or a PDA-type device 234, by utilising wireless communication means 236 and receiving/transmitting station 238. Satellite communications network 240 could communicate with satellite signal receiver 242 which receives data signals from satellite 244 which in turn is in remote communication with satellite signal transmitter 246. Terminals, for example further processing system 248, notebook computer 250 or satellite telephone 252, can thereby communicate with network 202. A local network 260, which for example may be a private network, LAN, etc., may also be connected to network 202. For example, network 202 could be connected with Ethernet 262 which connects terminals 264, server 266 which controls the transfer of data to and/or from database 268, and printer 270. Various other types of networks could be utilised. [0057] The processing device 100 is adapted to communicate with other terminals, for example further processing systems 206, 208, by sending and receiving data, 118, 120, to and from the network 202, thereby facilitating possible communication with other components of the networked communications system 200. [0058] Thus, for example, the networks 202, 230, 240 may form part of, or be connected to, the Internet, in which case, the terminals 206, 212, 218, for example, may be web servers, Internet terminals or the like. The networks 202, 230, 240, 260 may be or form part of other communication networks, such as LAN, WAN, ethernet, token ring, FDDI ring, star, etc., networks, or mobile telephone networks, such as GSM, CDMA or 3G, etc., networks, and may be wholly or partially wired, including for example optical fibre, or wireless networks, depending on a particular implementation.

- 12 Example embodiments [0059] For the purposes of clarity, the below examples discuss monitoring vehicles operated by a driver which delivers goods from a central location. However, it will be appreciated that the disclosed embodiments have many other applications such as the provision of services such as road side assistance. [0060] Referring to Figure 3 there is shown an example of a vehicular light box 300. The vehicular light box 300 includes a housing 310 having a securing arrangement (not shown) to releasably secure the vehicular light box 300 to a portion of a vehicle 400, wherein the housing 310 includes walls depicting advertising 312. The securing arrangement 317 can be provided in the form of magnets 317 which secure the vehicular light box 300 to the roof of the vehicle 400 as shown in Figure 4, although other securing arrangement can be used. [0061] The vehicular light box 300 also includes an electrical conductor such as an electrical cable 320 for electrical connection to a vehicular electrical power source (not shown) of the vehicle 400. In particular embodiments, the electrical cable 320 is connected to a cigarette lighter electrical port of the vehicle 400 although other electrical ports such as a USB port could potentially be used. The electrical cable 320 can be threaded adjacent the door seal or the like of the vehicle 400. [0062] The vehicular light box 300 also includes one or more lights 330, as shown in Figure 5A which show a removable base plate 315 of the housing 310, which are electrically connected to the electrical cable 320 and illuminate the advertising 317 upon receiving electrical power. The base plate 315 can be secured to the housing 310 via the magnets which are pivotally mounted to the housing such that they underlap the underside surface of the base plate 315 in the operative position. [0063] The vehicular light box 300 also includes a computerised device 340 in electrical connection with the electrical cable 320 as shown in Figure 5A. The computerised device - 13 320 is provided in the form of a microcontroller including a number of electrical components. [0064] In one form, as shown in Figure 5B, the computerised device 340 includes a processor 310, a memory 520, an input/output interface 530 coupled together via a bus 590. The computerised device 300 additionally includes a location receiver 560 (such as a Global Navigation Satellite Systems (GNSS) receiver which can include GPS, Galileo, Glonass, IRNAS and Beidou-2 satellite navigation receivers) including an internal GPS antenna, and a wireless communication module 550, which can be provided in the form of a GSM modem and associated antenna, which are coupled via the bus directly, as shown for example in Figure 5B, or indirectly via the input/output interface 530. The GSM modem generally includes a SIM card which has associated therewith a unique serial number (ICCID) which is used as a unique identifier for the computerised device 340 and vehicular light box 300. However, it will be appreciated that other identifiers, such as a MAC address or the like may be used to uniquely identify the computerised device 340. [0065] Preferably, the computerised device 340 includes a rechargeable battery 540 and a electrical power port 580 to receive electrical power from an external power source such as the cigarette lighter receptacle of the vehicle 400. [0066] In particular embodiments, the computerised device 340 can include an accelerometer 570. The computerised device 340 is configured to obtain, via the location receiver 560, location data indicative of locations of the vehicle 400 over time, and transfer, via the wireless communication module 550, a plurality of packets indicative of the location data to a server processing system 610 for monitoring the location of the of the vehicle 400. Generally, the computerised device 340 includes firmware stored in memory 520 indicating the address to transfer the data to the server processing system 610. The computerised device 340 can additionally include a control application stored in memory 520 to control the operation of the device 340.

- 14 [0067] Advantageously, the vehicular light box 300 enables monitoring of the vehicle 400 without having to permanently install equipment in or on the driver's vehicle 400. At the start of a shift, the driver can collect a light box 340 from the store/central meeting location/hub and releasably secure it to the vehicle 400. At the end of the shift, the driver can remove the light box 300 from the vehicle 400 and return it to the store/central meeting location/hub. Whilst it will be appreciated that this arrangement is advantageous for vehicles 400 owned by the drivers, other advantages are also provided by vehicular light box 300 in relation to vehicles 400 owned by the employer. In particular, once a vehicle 400 has begun to fail or is no longer required by the employer, the portable light box 300 can simply be interchanged with another vehicle 400. [0068] Generally, some of the packets of data are transferred to the server processing system 610 in the form of a heartbeat signal, for example every 20 seconds, so that the location of the vehicle 400 can be updated and monitored regularly by the server processing system 610. However, as will be discussed further below, additional events may occur which enable additional packets of data to be generated and transferred which do not occur on a periodic basis but rather upon detection of a particular event by the computerised device 340. Packets which are transferred back to the server processing system 610 indicate the type of data being sent, for example, heartbeat, change in acceleration, change in speed, change in heading, etc., as will be explained in more detail below. [0069] In particular embodiments, as discussed above, the computerised device 340 includes the accelerometer 570. In this embodiment, acceleration data indicative of the proper acceleration of the vehicle 400 is obtained by the processor 510 from the accelerometer 570 and then compared against an acceleration threshold indicative of dangerous driving (e.g. 3m/sec/sec or the like) which is set in memory 520, and more specifically in the firmware, of the computerised device 340. In the event of a positive determination, the computerised device 340 transfers to the server processing system 610 a packet of data indicative of the captured data including the sensed acceleration or an indication that the threshold has been met or exceeded. The packet can additionally - 15 indicate a packet type indicating the a change in acceleration has been detected. In the event that the acceleration threshold is not met, the computerised device 340 transfers the acceleration of the vehicle 400 as part of the heartbeat packet when required. [0070] In particular embodiments, the processor 510 of the computerised device 340 can be configured to determine the speed of the vehicle 400 based on the location data. For example, the location data includes a plurality of time stamped coordinates which are stored in memory 520, wherein the vehicle's speed travelling between points can be calculated by the processor 510 and transferred to the server processing system 610. The processor 510 is configured to determine if a change in speed greater than or equal to a speed threshold stored in memory 520 has occurred based on the determined speed, wherein in the event of a positive determination, the computerised device 340 generates and transfers one or more packets of data indicative of the captured data including the speed to the server processing system. The packet can additionally indicate a packet type indicating a change in speed has been detected. In the event that the speed threshold is not met, the computerised device 340 transfers the speed of the vehicle 400 as part of the heartbeat signal when required. [0071] The processor 510 of the computerised device 340 can also be configured to determine a heading of the vehicle 400 based on the location data, wherein at least some of the packets are indicative of the heading of the vehicle 400. In particular, the series of time-stamped locations indicated by the location data can be used by the processor 510 to determine the heading of the vehicle 400. The processor 510 is configured to determine if a change in heading greater than or equal to a heading threshold stored in memory 520 has occurred based on the determined heading, wherein in the event of a positive determination, the computerised device 340 generates and transfers a packet of data indicative of the captured data including the heading to the server processing system. The packet can additionally indicate a packet type indicating the a change in heading has been detected. In the event that the heading threshold is not met, the computerised device transfers the heading of the vehicle 400 as part of the heartbeat packet when required.

- 16 [0072] Each packet can be indicative of various data captured by or inferred by the computerised device. In one form, each packet includes a timestamp, quality of location receiver signal, location data including latitude, longitude and elevation, heading, speed, ignition of vehicle, voltage of vehicular battery, internal battery voltage, packet type, one or more digital inputs and outputs, one or more analogue inputs and outputs, and the identifier of the computerized device which can be unique serial number of the SIM card (ICCID). [0073] As discussed above, the computerised device 340 can optionally include an internal rechargeable battery 540. The internal rechargeable battery 540 recharges upon receiving electrical power from the vehicular electrical power source via the electrical cable 320. It will be appreciated that in the event the ignition of the vehicle 400 has been turned off, the computerised device 340 may sense that no electrical power is being provided and enter a sleep mode. Upon detecting the ignition, the computerised device 340 can recommence operation and transfer collected data back to the server processing system 610. [0074] In particular instances, the driver may forget to connect the electrical cable 320 to the power source of the vehicle 400, in which case the computerised device 340 may still operate to capture and transfer location data as well as other data discussed based on the internal battery power supply. The processor 510 of the computerised device 340 can be configured to detect a change in location, speed, acceleration and/or heading of the vehicle 400 to indicate that the vehicle's ignition has been started. The computerised device 340 can then operate as per normal. When there is no change in location, speed, acceleration and/or heading for a threshold period of time stored in memory of the device 340, then the computerised device 340 enters a sleep mode and records that the ignition of the vehicle is off. As discussed above, the ignition states of the vehicle can be transferred to the server processing system, whether these be inferred as discussed or sensed when the vehicular light box 300 is connected to the power source.

- 17 [0075] As will be discussed in further examples below, the housing 310 can have attached thereto a contactless readable identifier to enable a reading device at the employer's premises to read an identity associated with the vehicular light box in order to associate the identity of the vehicular light box 300 with an identity of the driver and/or an identity of the vehicle 400. In particular, the contactless readable identifier is an RFID tag, although it will be appreciated that other identifiers such as barcodes, QR codes or the like can be used. In specific arrangements, a hole is drilled through part of the housing 310, wherein a tether is placed through the hole to secure the RFID tag to the housing 310. A record is maintained at the server processing system 610 in the data store 612 indicative of the association between the RFID identity and the unique identity associated with the computerised device 340 or light box 300. When the RFID tag is scanned by a driver, the server processing system 610 can then associate the light box 300 and/or the computerised device 340 as indicated by the RFID tag with a driver identity.. [0076] In particular situations the computerised device 340 may not be able to transfer the packet data to the server processing system 610. For example, there may be geographical areas which the communication module 550 is unable to obtain sufficient service. In this regard, the computerised device stores the packets in a buffer in the memory 520. When a connection is re-established between the computerised device 340 and the server processing system 610, the data stored in the buffer is transferred to the server processing system 610 accordingly. [0077] Referring to Figure 6 there is shown a system diagram of a system 600 for a monitoring vehicle 400. As will be appreciated, the system 600 can be used for monitoring one or more vehicles 400 for an employer premises, however the examples discussed in relation to Figure 6 are directed toward multiple vehicles being monitored for multiple employer's premises. [0078] In particular, the system 600 includes a plurality of vehicular light boxes 300 including 300a, 300b and 300c associated with a respective plurality of vehicles 400, a server processing system 610 and a plurality of client processing systems 620 including - 18 620a, 602b and 620c located in respective plurality of employer premises. It will be appreciated that the server processing system 610 is generally located remotely to the employer premises. [0079] The server processing system 610, which can be provided in the form of processing system 100, includes a server application 614 stored in memory which configures the server processing system 610 to receive the plurality of packets from the computerised devices 340a, 340b, 340c, and store the received data in a data store 612 which may be embodied in the form of a database. For each employer premises, the server processing system 610 then transfers at least some of the data captured to the respective client processing system 620 for presenting a representation of the location of one or more vehicles relevant for the respective employer premises. The client processing system 620 can be provided in the form of processing system 100, although a specific arrangement will be discussed in examples below. [0080] In one form, the server processing system 610 generates a tracking interface 700 (see Figure 7) for each employer premises depicting the location of each vehicle 400 associated with the respective employer premises. The server processing system 610 then transfers tracking interface data indicative of the respective tracking interface 700, via one or more communication networks (i.e. Internet, etc), to the respective client processing system 620a, 620b, 620c for presentation. However, in other embodiments, the relevant raw captured data for the each employer premises can be transferred to each respective client processing system 620 for interpretation and generation of the tracking interface 700 which is presented at the employer's premises by the client processing system 620. In particular, the server processing system 610 maintains data in the data store 612 which indicates the associated employer premises and/or the associated respective client processing system 620 for each computerised device 340. [0081] Generally the client processing system 620 includes one or more applications 623 stored in memory. The applications 623 control the client processing system 620 to present the tracking interface 700 to staff in the employer premises via a display device 624. In - 19 particular, the client processing system 620 can include a first display device for presenting an interface of one or more of the applications 623 and a second display device which presents the tracking interface 700 which is based upon the relevant packet data captured by the server processing system 610. [0082] In one preferable arrangement, the client processing system 620 includes a tablet processing system 622 which includes a touch screen interface providing the first display device and a separate display device (i.e. the second display device) provided in the form of a computer monitor or television screen which is connected to the tablet processing system 622 via cable such as a HDMI cable or the like. The display device 624 can be significantly larger (i.e. 40 inch screen or larger) than the touch screen interface of the tablet processing system 622 to enable staff to easily view the tracking interface 700 at various points in the employer premises in a quick manner. [0083] In a preferable form, the tablet processing system 622 and/or the display device 624 are mounted to a wall in the employer premises. In particular arrangements, the display device 624 is mounted above the tablet processing system 622. The tablet processing system 622 can include one or more peripheral input devices such as a mouse and keyboard despite the touch screen interface to enable other input options. The tablet processing system generally includes a communications module including an Ethernet port to enable the tablet processing system 622 to be coupled to a computer network which allows communication with server processing system 610 via one or more networks. However, it will be appreciated that wireless communication is also possible between the tablet processing system 622 and other computing devices. It will be appreciated that whilst the tablet processing system 622 is a preferable arrangement to enable staff such as the drivers to quickly interact with the one or more of the applications 623 using the touch screen interface, it is entirely possible that a traditional processing system, such as personal computer (PC) could be used. Additionally, whilst two separate user interfaces are preferable, a single display device could be used. For clarity purposes, the following description will continue with the preferred arrangement using the tablet processing system 622 and the additional display device 624.

- 20 [0084] At least some of the one or more applications 623 stored in memory of the tablet processing system 622 are configured to receive the data from the server processing system 610 and present the tracking interface 700 via the display device 624. Referring to Figure 7, each tracking interface 700 preferably includes a map portion 701 including a marker 705 indicative of the location of one or more vehicles 400 and a marker 710 for the location of the respective employer premises. The marker 705 representing each vehicle 400 includes an arrow indicating the detected heading captured from the respective computerised device 340 such that the staff at the employer premises can determine the direction of travel of the vehicle 400. The map portion 701 of the tracking interface 700 includes a temporal marker 720 indicative of a predetermined estimated travel time to the employer premises. The temporal marker 720 is generally presented in the form of a circular annotation on the map 701 with the employer premises 710 at the centre of the circle. The temporal marker 720 can indicate, for example, a 5 minute travel time radius on the map. This feature is particularly advantageous where the staff may only have a very short period of time to determine when to expect a vehicle 400 back at the employer premises to attend to a new job. In relation to a pizza store example, a cooking staff member may wait until the driver's location depicted on the tracking interface 700 has crossed within the temporal marker 720 and then place an uncooked pizza in an oven such that the respective driver arrives back in store at the time the cooked pizza is being placed in a pizza box, thereby seeking to reduce the time that the pizza is delivered to the customer after leaving the oven. [0085] As shown in Figure 7, the tracking interface 700 can additionally include a driver interface portion 740 indicating the current drivers operating for the employer, and a resources portion 730 indicating various resources that are currently not operating but are potentially available to the employer, such as drivers, employees, light boxes, etc. [0086] In one form, one or more of the applications 623 can present via the touch screen interface of the tablet processing system 622 a registration interface 900 of the application 623 as shown in Figure 9 to enable the driver to register use of a vehicular light box 300 to - 21 be releasably secured to the vehicle 400. As discussed above, the vehicular light box 300 may have attached thereto a contactless readable device like an RFID tag for reading by the client processing system. In relation to this embodiment, the tablet processing system 622 can include or is in data communication with a contactless reading device which reads the RFID tag attached to the vehicular light box 300 to be releasably secured to the vehicle, wherein upon reading the contactless readable device the tablet processing system 622 records in memory and transfers to the server processing system 610 an association between an identity of the driver and an identity of the contactless readable device. The server processing system 610 receives and stores this association in the data store 612 in order to associate the respective computerised device 340 with the respective driver. The driver generally inputs their identity via the registration interface 900. As will be discussed later in other examples, the driver can alternatively register use of an employer owned vehicle 400 which has a computerised device 340 mounted thereto. In this arrangement, a key of the vehicle 400 can have an RFID tag attached thereto wherein the driver can scan the RFID tag of the key of the vehicle in order to associate the driver identity with the RFID tag which is associated with the respective computerised device 340 mounted to the vehicle 400. [0087] The one or more applications 623 of the tablet processing system 622 can enable the driver to quickly determine a driving route to a particular location via a map. In particular, the driver can input text indicative of the destination (either via the touch screen or via an input device such as a keyboard) via a location searching interface of the application 623 as shown in Figure 10, wherein a map is presented as shown in Figure 11 indicating a highlighted route. The route can be traffic optimised. In particular forms, the tablet processing system 622 has stored in memory a list of each street within a geographical area associated with the respective employer premises to enable the user to quickly select from the list after entering a portion of the destination. The tablet processing system 622 can query the server processing system 610 or a remote mapping server processing system (e.g. Google Maps) to determine and return an optimised route from the employer premises to the location, wherein the route is presented via the touch screen interface of the tablet processing system 623.

- 22 [0088] The tracking interface 700 which is presented upon the display device 624 can be generated as a webpage by the server processing system which is hosted by the server processing system 610 or a web-hosting server associated with the server processing system 610. The webpage includes dynamic components, for example AJAX components, which periodically (i.e. every 10 seconds) cause the tablet processing system 622 to transfer a request to the server processing system 610 to obtain updated tracking interface data from the server processing system 610 for presentation. In some instances in order to reduce download rates, only portions of the tracking interface which have changed between the last version of the tracking interface 700 and the current tracking interface 700 are transferred to the tablet processing system 622 in order for the cached data to be combined with the updated data of the tracking interface in order to display the updated tracking interface 700 via the display device 624. The tracking interface 700 presented on the display device 624 can be a web-browser, such as Google Chrome operating upon the tablet processing system in a kiosk mode, which interprets the web-page generated by the server processing system 610, wherein the tracking interface 700 is presented via the display device 624. In other embodiments, the one or more applications 623 are a thick client application which can generate and present the tracking interface 700 rather than presenting a web-based interface which is provided by the server processing system 610. [0089] Data other than the location and heading of the vehicles can be presented via the tracking interface 700. In particular, in the event that a driver has been detected speeding or has been detected driving in a dangerous manner, a notification 810 may be presented on the tracking interface 700 for the attention of the manager as shown in Figure 8. The notification 810 may additionally be presented audibly via speakers of the display device 624. In specific arrangements, the server processing system 610 may have stored in the data store 612 geographical speed limit data in order to determine whether one or more drivers have been speeding in a particular location. However, in other arrangements, the server processing system 610 can transfer a query to a third party server processing system to determine the speed limit in the respective location to determine if speeding has been detected for one or more of the vehicles 400.

- 23 [0090] Authorised staff, such as a manager, may also utilise the one or more applications 623 of the tablet processing system 622 to run and present reports based on the data collected by the server processing system 610 and/or transferred to the tablet processing system 622 as will be discussed in further detail below. In particular, the authorised staff member may be required to enter a username and password which is authenticated by the server processing system 610 against data stored in the data store, wherein the authorised staff member can then interact with a report interface of the one or more applications 623 to generate various reports, such as a speeding report 1200 of the driver's of the employer as shown for example in Figure 12. [0091] The server processing system 610 additionally hosts an administration web-portal which can be accessed by any user processing system (such as processing system 100) in data communication with the server processing system 610 using a username and password associated with an authorised user. The server processing system 610 authenticates the user's credentials prior to presenting an administration webpage of the portal as shown in Figure 13. The administrative webpage 1300 enables the user to perform various administrative functions such as generate particular reports in relation to the captured data received from the computerised devices 300 for one or more employer premises of a franchise. [0092] In particular, referring to Figure 13 there is shown a driver report indicating employer owned vehicles 400 that need registration renewed, particular jobs and the associated driver which took longer than a predetermined temporal threshold, flat battery notifications for employer owned vehicles, poor GPS signal notifications from computerised devices, and computerised devices that are not in use. Referring to Figure 14, various graphs are generated using the captured data. Figure 15 shows a graph indicating average job time versus dangerous driving notifications for each driver of the employer premises. An additional graph is generated which shows the number of speeding drivers detected over a week. A further graph indicates the dangerous driving notifications received per employer owned vehicle. Figure 16 shows a first graph indicating the number - 24 of jobs for an employer over a week, a table of drivers and their associated captured data, and a table of the employer owned vehicles and the associated data such as total jobs and distance travelled. Figure 17 shows captured data for unassigned drivers, wherein the driver has not registered the light box 300 or the vehicle with their identity as discussed in relation to Figure 9. Additionally, Figure 17 shows a further graph and table relating the distance travelled per employer owned vehicle. It will be appreciated that the server processing system receives the report query from the user processing system operated by the administrative user and processes the report query on the data stored in the data store 612 to generate the reports which are then returned to the user processing system as a webpage although the reports can additionally be provided in a document format such as PDF, Microsoft Word, Microsoft Excel or the like. [0093] As discussed above, it will be appreciated that in certain instances the employer may already possess one or more vehicles 400 which are already branded with the employer's advertising. Therefore, in these instances it is not necessary to use a removable light box 300. However, it is possible to mount the computerised device 340 to the employer owned vehicle 400 in order to allow the employer to monitor the vehicle 400. In some instances, the employer owned vehicle 400 may have a permanently mounted light box which the computerised device 340 can be retrofitted thereto or therein. Alternatively, the computerised device 340 may be mounted to other portions of the vehicle 400. [0094] In embodiments, the computerised device 340 can sense a voltage of the vehicular power source (i.e. the vehicle's battery). In this embodiment, at least some of the plurality of packets transferred to the server processing system 610 are indicative of the sensed voltage of the vehicle's battery. The server processing system 610 can compare the sensed voltage source against a battery voltage threshold stored in memory, wherein in the event that the sensed voltage is less than or equal to the battery voltage threshold then the server processing system 610 generates the tracking interface data such that the tracking interface 700 presented by the client processing system 620 includes a battery notification indicative of the detection associated with the vehicle 400. The battery notification remains on the tracking interface 700 until an acceptable battery voltage ha been sensed. Therefore, in the - 25 event that a driver is about to start a shift, the manager can quickly view the tracking interface 700 on the display device 624 and notice that one or more particular vehicles 400 may have a failing battery and may therefore suggest that the driver use a different vehicle 400 with an acceptable battery. Additionally or alternatively, the manager may ask a driver or staff member to attempt to start the failing vehicle 400 determined from the battery notifications on the tracking interface 700 and drive the vehicle 400 for a period of time to allow the alternator to recharge the failing battery. It is possible that the computerised device 340 can sense the battery voltage of privately owned vehicles. [0095] The server processing system 610 maintains in the data store 612 various data about the employer owned vehicles 400. For example, registration renewal dates are maintained in the data store 612. When a vehicle 400 is within a threshold period of time for registration to be renewed, the server application 623 generates a reminder on the tracking interface 700 with a registration renewal notification. If registration has been past, a different notification 820 can be generated by the server application 623 on the tracking interface 700 as shown in Figure 8. As discussed above, reports can be generated which to the vehicle information such as registration renewals, distance travelled, and the like. [0096] In particular embodiments, the tablet processing system 622 can include a camera module. Upon a driver interacting with the registration interface 900 of the application 623, the tablet processing system 622 actuates the camera module to take a digital photograph of the driver. The photograph is transferred to the server processing system 610 for storage although it is possible that the digital photograph can be also be stored locally in the memory of the tablet processing system 622. The tracking interface 700 can then depict the driver in the driver portion 740 of the tracking interface 700 with the photograph captured in the employer premises to make the manager's operation of the driver's easier by being able to visually depict the appearance of each driver. In particular, the tracking interface 700 is generated by the server processing system 610 to include the digital photograph received from the client processing system 620. Alternatively the tracking interface 700 is generated by the server processing system to include a link to the - 26 predetermined location in memory of the tablet processing system 622 having stored the digital photograph. [0097] In one form, the an authorised user such as a manager can interact with the tablet processing system 622 to request, under control of the one or more applications 623, that a particular vehicle 400 is highlighted on the display device 624. Upon authentication of the authorised user and upon receiving input data via an input device (such as the touch screen interface, keyboard, mouse or the like) from the authorised user indicative of the particular vehicle, the map interface 700 is presented on the display device 624 with the particular vehicle 400 centred within the map portion 701 of the interface 700, wherein the map portion 701 has been zoomed to a predetermined zoom level. This feature can be particularly useful in situations where the driver has contacted the employer premises to request assistance in finding the destination. For example, the manager or other drivers or staff in store may have previously visited the destination a number of times in the past, wherein the zoomed and centred tracking interface 700 can assist in providing the driver feedback in finding the specific destination. [0098] Referring to Figure 18 there is shown a further system diagram of a further example system 1800 that is substantially based upon system 600. The following description outlines differences between the operation of system 1800 and system 600. [0099] In particular, the server processing system 610 is in data communication with a user device 1830, such as a user processing system 100 or mobile communication device, for example a smart phone or tablet processing system executing an ordering application 1840. The server processing system 610 can be configured to serve the ordering application 1840 in order to receive an order from the user device 1830. Order data including an order identifier, the destination and the good(s)/service(s) ordered are stored in the data store 612. After the order has been submitted, the order application 1840 can present a vehicle interface 2105 to the user via the user device 1830 as shown in Figure 21. The vehicle interface provides the user with an indication of the location 2120 of the assigned vehicle 400 which is determined and provided by the server processing system - 27 610 using the data captured from the computerised device 340 of the respective vehicle 400 as discussed above. [00100] It will be appreciated that shortly after the user order has been submitted, the vehicle interface 2105 may not immediately be presented within the ordering application 1840 as a vehicle 400 may yet to be assigned to the user order, or at least a message may be displayed indicating that the user order has yet to be assigned to a vehicle 400. However, once a vehicle 400 has been assigned to the user order, as will be discussed below, the vehicle interface 2105 is presented within the ordering application 1840 on the user's device 1830 indicating the location of the vehicle 400 during the route. [00101] In one form, the vehicle interface 2105 may be presented in the form of a map interface 2110 similarly to that of the interface 700 of the display device 624 wherein a marker 2120 is shown on the map interface 2110 indicating the vehicle's location. The vehicle interface 2105 is updated periodically by the server processing system 610 with an indication of an estimated time of arrival 2140 to the destination 2130. Once the server processing system 610 determines that the vehicle 400 is within a threshold distance or threshold time of arrival to the user location 2130, an alert is transferred to the user device 1830 for presentation to the user via the ordering application 1840 indicating that the vehicle 400 will arrive shortly. The vehicle interface can additionally include other information such as the driver's name 2150 and a picture 2155 of the driver which are stored in the data store 612. [00102] Once a user order has been received by the server processing system 610 via the ordering application 1840, the order details are then transferred to a dispatch processing system 1810 located in the employer premises. Once a driver is available, input data is input into a dispatch application of the dispatch processing system 1810 via an input device (such as a keyboard, mouse, touch screen interface, barcode scanner, or the like) by the driver which thereby associates the user order with the driver identity of the driver. This association data is then transferred to the server processing system 610 in order to associate the user order with the vehicle 400.

- 28 [00103] At the user device 1830, the ordering application 1840 can transfer a periodic request (e.g. every 5 seconds) to the server processing system 610 for an update of the vehicle interface 2105. As discussed above, initially before a driver is assigned the user order, a message may be transferred back to the ordering application 1840 by the server processing system 610 indicating that no vehicle 400 has been assigned the user's order. Alternatively, until a message is received from the server processing system 610 indicating that a driver has been assigned the user's order, the vehicle interface 2105 may not be displayed within the ordering application 1840. Once a driver has been assigned the user's order, the server processing system 610 generates vehicle interface data using the collected data from the respective vehicle's computerised device 340. More specifically, the vehicle interface data 2105 can include the driver's name 2150, a digital photograph 2155, the map interface 2110 including the vehicle's location 2120, and an estimated time of arrival 2140 to the requested destination. The server processing system 610 can determine the estimated time of arrival 2140 using the current location of the vehicle 400 from the computerised device 340 and utilising mapping software or alternatively using a third party mapping server processing system (e.g. Google Maps) to determine the estimated time of arrival 2140 at the requested destination 2130. The estimated time of arrival may additionally take into account traffic congestion. The user device 1830 receives the vehicle interface data, wherein the vehicle interface data is used to present the vehicle interface 2105 within the ordering application 1840. Whilst this example discusses the vehicle interface data being pulled from the server processing system 610 by the user device 1830 in a periodic manner, it will be appreciated that the vehicle interface data could be pushed to the user device 1830 from the server processing system 610 when available. [00104] When the server processing system 610 determines that the vehicle 400 is within a temporal threshold (e.g. 30 seconds, 1 minute, 2 minutes, 3, minutes, 4 minutes or 5 minutes) or spatial threshold (e.g. 1 km, 500m, 200m, etc) of arriving at the requested destination 2140 based on the estimate time of arrival 2140 which is generated using the current location indicated by the computerised device 340, the server processing system 610 may additionally transfer an alert 2210 to the user device 1830 indicating that the - 29 vehicle will shortly arrive as shown in Figure 22. For example, the alert may indicate "Your delivery will arrive in 1 minute" or "Your delivery is 1km away". The alert can be presented visually and in addition can be presented audibly via speakers of the user device 1830. It will be appreciated that the determination of the vehicle 400 being within the threshold can be determined by the server processing system 610 using mapping software or a third party mapping server processing system as discussed above. In particular forms, live traffic congestion data accessed from a third party server processing system may be used to determine the estimated time of arrival. [00105] Referring to Figure 19 there is shown a further system diagram of a further example system 1900 that is substantially based upon system 1800. The following description outlines particular differences between the operation of system 1900 and system 1800 in order to avoid reduplication of particular features. In particular, the system 1900 includes an ordering server processing system 1910 that is operated by a first party, such as a franchisor of a plurality of employer premises, and the server processing system 610 is operated by a second party which collects the data from the computerised devices 400. The server processing system 610 may transfer all or portions of the collected data received from the computerised device 400 to the ordering server processing system 1910 to generate the vehicle interface data which is then served to the user device 1830 for presentation within the ordering application 1840. The ordering processing system 1910 may call various exposed functions of an API provided by the server processing system 610 to request portions of the collected data to be retrieved from the data store 612. However, it will be appreciated that in other instances, all the data received is transferred to the ordering server processing system such that the ordering server processing system maintains a copy of the collected data in a data store. [00106] Referring to Figure 20 there is shown a further system diagram of a further example system 2000 that is substantially based upon system 1800 and 1900. The following description outlines particular differences between the operation of system 1900 and system 1800 order to avoid reduplication of particular features. In particular, upon the association of the driver to the user order occurring, the dispatch processing system 1810 -30 calls an exposed function of an API provided by the server processing system 610 to provide order and driver details to the server processing system 610 for recordal in the data store 612. In particular, the dispatch server processing system 1810 can indicate a user order identifier, an identity of the driver and a destination address. [00107] The ordering application 1840 of system 2000 may periodically request and receive vehicle interface data from the server processing system 610 which is generated based on the collected data from the associated computerised device 340 for the respective vehicle 400. The request can include the user order identifier such that the server processing system 610 can determine which data collected from a plurality of computerised devices 340 is to be used to generate the vehicle interface data. In one form, the ordering application 1840 includes an HTML iframe to present the vehicle interface which includes dynamic code such as AJAX code which periodically requests retrieval of vehicle interface data from the server processing system 610. The vehicle interface data may be a webpage that is interpreted and presented within the iframe. [00108] In certain embodiments, in the event that the driver is performing multiple jobs on the route without returning to the store/central location/hub, the server processing system calculates the estimated time of arrival based upon a schedule including the multiple destinations which is generated and stored in the data store 612, wherein schedule is associated with each user order. Thus, despite the vehicle indicating that their current location may only be a short distance away, the estimated time of arrival to a particular destination which is later in the schedule is adjusted according to the order of destinations. In one form, the server processing system 610 generates an optimised schedule based on multiple destinations using a mapping server and an optimisation algorithm. [00109] In the above embodiments, upon associating a user order with a driver at the dispatch processing system 1810, the client processing system 620 can present the route from the employer premises to the destination. In particular, the server processing system can communicate with the client processing system 620 upon receiving the association -31 data to present the route which can be generated as discussed above. For example, the route may be presented via the tablet processing system 622. [00110] In particular embodiments, the function of the dispatch processing system 1810 may be performed by the client processing system 620, wherein in this arrangement it is not necessary to have two separate processing systems. [00111] In particular embodiments, an alert may be generated by the server processing system and transferred to the user device in response to other events detected from the collected data from the computerised devices. For example, the ignition state indicating that the vehicle has turned on could be used by the server processing system to generate and transfer an alert to the user ordering application. [00112] Whilst a number of embodiments have been described in relation to the delivery of freshly cooked food, it will be appreciated that embodiments of the invention can be applicable to other industries that use vehicles 400 to deliver goods or provide desired services at the requested destination. For example, home delivered groceries for supermarket franchises, online retailers which deliver ordered goods, roadside assistance vehicles which provide roadside assistance services to members, and the like, can benefit from the described invention where the customer is provided an accurate indication of the estimated time of arrival of the vehicle 400. [00113] Many modifications will be apparent to those skilled in the art without departing from the scope of the present invention.

Claims (20)

1. A vehicular light box for a vehicle, including: a housing including advertising and a securing arrangement to releasably secure the vehicular light box to a portion of the vehicle; an electrical cable for electrical connection to a vehicular electrical power source; one or more lights for illuminating the advertising upon receiving electrical power via the electrical cable; a computerised device in electrical connection with the electrical cable, wherein the computerised device includes a location receiver and a wireless communication module, wherein the computerised device is configured to: obtain, via the location receiver, location data indicative of locations of the vehicle over time; and transfer, via the wireless communication module, a plurality of packets indicative of the location data to a server processing system for monitoring the location of the of the vehicle over time.
2. The vehicular light box according to claim 1, wherein the computerised device includes an accelerometer, wherein the computerised device is configured to: obtain acceleration data of the vehicle; determine if an acceleration of the vehicle indicated by the acceleration data meets or exceeds an acceleration threshold indicative of dangerous driving; and wherein at least some of the packets are indicative of whether dangerous driving has been detected for the vehicle.
3. The vehicular light box according to claim 1 or 2, wherein the computerised device determines the speed of the vehicle based on the location data, wherein at least some of the packets are indicative of the speed of the vehicle.
4. The vehicular light box according to any one of claims 1 to 3, wherein the computerised device determines a heading of the vehicle based on the location data, - 33 wherein at least some of the packets are indicative of the heading of the vehicle.
5. The vehicular light box according to any one of claims 1 to 4, wherein the computerised device includes an internal rechargeable battery, wherein the internal rechargeable battery recharges upon receiving electrical power from the vehicular electrical power source via the electrical cable.
6. The vehicular light box according to any one of claims 1 to 5, wherein the housing has attached thereto a contactless readable identifier to enable a reading device to read an identity associated with the vehicular light box in order to associate the identity of the vehicular light box with an identity of the driver.
7. The vehicular light box according to claim 6, wherein the contactless readable identifier is an RFID device.
8. A system for monitoring vehicles, wherein the system includes a server processing system and a client processing system, wherein: the server processing system is configured to: receive a plurality of packets indicative of a location of the vehicles over time from computerised devices associated therewith; transfer, via a network, tracking data indicative of at least a portion of the received packets to the client processing system; and the client processing system is configured to: receive, from the server processing system, the tracking data; and present, using the tracking data, a tracking interface indicating the location of the vehicles.
9. The system according to claim 8, wherein the tracking interface includes a map including a marker indicative of each vehicle.
10. The system according to claim 9, wherein the tracking interface includes a temporal - 34 marker indicative of a predetermined estimated travel time to a central meeting location.
11. The system according to any one of claims 8 to 10, wherein the client processing system includes: a first display device presenting a registration interface enabling one or more drivers to register an association with one of the respective computerised devices; and a second display device in electrical connection with the which presents the tracking interface; wherein the first display device and the second display device present the respective interfaces simultaneously.
12. The system according to claim 11, wherein the client processing system includes a contactless reading device for reading contactless readable devices associated with the computerised devices, wherein upon reading one of the contactless readable devices, the client processing system in combination with the server processing system associates respective associated computerised device with an identity of one of the drivers, wherein the association is stored by the server processing system.
13. The system according to claim 11 or 12, wherein the client processing system is a tablet processing system, wherein the first display device is a touch screen interface of the tablet processing system, and the second display device is in data communication via a data cable with the tablet processing system.
14. The system according to claim 13, wherein the client processing system transfers a request to a mapping server processing system to determine a driving route for one of the vehicles, wherein the driving route is received from the mapping server processing system and presented by the client processing system.
15. A system for monitoring vehicles, wherein the system includes a plurality of computerised devices, a server processing system, and a client processing system, wherein: each computerised device is associated with one of the vehicles, computerised - 35 device includes a location receiver and a wireless communication module, wherein each computerised device is configured to: obtain, via the location receiver, location data indicative of locations of the vehicle over time; and transfer, via the wireless communication module, a plurality of packets indicative of the location data; the server processing system is configured to: receive the plurality of packets indicative of a location of the vehicles; transfer, via a network, tracking data indicative of at least a portion of the received packets; and the client processing system is configured to: receive, from the server processing system, the tracking data; and present, using the tracking data, a tracking interface indicative of the location of the vehicles.
16. The system according to claim 15, wherein at least some of the computerised devices are associated with a portable light box which is releaseably secured to the respective vehicle.
17. The system according to claim 15 or 16, wherein the server processing system is configured to: receive order data indicative of a order placed using a user device; receive association data for associating one of the vehicles with the order; generate vehicle interface data, wherein the vehicle interface data is generated using the location data of the respective vehicle; and transfer the vehicle interface data to the user device.
18. The system according to claim 17, wherein the vehicle interface includes an estimated time of arrival of the respective vehicle to a destination associated with the order. -36
19. The system according to claim 18, wherein the server processing system determines, based on the location data for the respective vehicle if the respective vehicle is within a threshold temporal or spatial threshold of the destination, wherein in the event of a successful determination, the server processing system transfers an alert to the user device indicating that the vehicle is approaching the destination.
20. The system according to any one of claims 17 to 19, wherein the vehicle interface includes at least one of: a driver's name of the respective vehicle; and a digital photograph of the driver of the respective vehicle.
AU2014253558A 2014-10-24 2014-10-24 Vehicular light box and computerised system for monitoring one or more vehicles Abandoned AU2014253558A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2014253558A AU2014253558A1 (en) 2014-10-24 2014-10-24 Vehicular light box and computerised system for monitoring one or more vehicles

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
AU2014253558A AU2014253558A1 (en) 2014-10-24 2014-10-24 Vehicular light box and computerised system for monitoring one or more vehicles
AU2014101356A AU2014101356B4 (en) 2014-10-24 2014-11-12 Vehicular Light Box And Computerised System for Monitoring One Or More Vehicles
AU2015101096A AU2015101096B4 (en) 2014-10-24 2015-08-12 Vehicular light box and computerised system for monitoring one or more vehicles

Related Child Applications (2)

Application Number Title Priority Date Filing Date
AU2014101356A Division AU2014101356B4 (en) 2014-10-24 2014-11-12 Vehicular Light Box And Computerised System for Monitoring One Or More Vehicles
AU2015101096A Division AU2015101096B4 (en) 2014-10-24 2015-08-12 Vehicular light box and computerised system for monitoring one or more vehicles

Publications (1)

Publication Number Publication Date
AU2014253558A1 true AU2014253558A1 (en) 2015-03-12

Family

ID=52011526

Family Applications (3)

Application Number Title Priority Date Filing Date
AU2014253558A Abandoned AU2014253558A1 (en) 2014-10-24 2014-10-24 Vehicular light box and computerised system for monitoring one or more vehicles
AU2014101356A Active AU2014101356B4 (en) 2014-10-24 2014-11-12 Vehicular Light Box And Computerised System for Monitoring One Or More Vehicles
AU2015101096A Active AU2015101096B4 (en) 2014-10-24 2015-08-12 Vehicular light box and computerised system for monitoring one or more vehicles

Family Applications After (2)

Application Number Title Priority Date Filing Date
AU2014101356A Active AU2014101356B4 (en) 2014-10-24 2014-11-12 Vehicular Light Box And Computerised System for Monitoring One Or More Vehicles
AU2015101096A Active AU2015101096B4 (en) 2014-10-24 2015-08-12 Vehicular light box and computerised system for monitoring one or more vehicles

Country Status (1)

Country Link
AU (3) AU2014253558A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016154674A1 (en) * 2015-03-30 2016-10-06 Domino's Pizza Enterprises Limited A system for real-time monitoring of vehicles
WO2017177274A1 (en) * 2016-04-13 2017-10-19 Domino's Pizza Enterprises Limited System and method for monitoring delivery of orders amongst parties through use of a positioning or location system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040039504A1 (en) * 1999-12-19 2004-02-26 Fleet Management Services, Inc. Vehicle tracking, communication and fleet management system
US6812851B1 (en) * 1999-12-15 2004-11-02 Vert, Inc. Apparatuses for displaying information on vehicles
US6970783B2 (en) * 1997-08-19 2005-11-29 Siemens Vdo Automotive Corporation Vehicle information system
US20100191412A1 (en) * 2006-09-14 2010-07-29 Qualcomm Incorporated Critical event reporting

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140274152A1 (en) * 2013-03-14 2014-09-18 Tim Lichti System and Method for Tracking of Mobile Resources

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6970783B2 (en) * 1997-08-19 2005-11-29 Siemens Vdo Automotive Corporation Vehicle information system
US6812851B1 (en) * 1999-12-15 2004-11-02 Vert, Inc. Apparatuses for displaying information on vehicles
US20040039504A1 (en) * 1999-12-19 2004-02-26 Fleet Management Services, Inc. Vehicle tracking, communication and fleet management system
US20100191412A1 (en) * 2006-09-14 2010-07-29 Qualcomm Incorporated Critical event reporting

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016154674A1 (en) * 2015-03-30 2016-10-06 Domino's Pizza Enterprises Limited A system for real-time monitoring of vehicles
WO2017177274A1 (en) * 2016-04-13 2017-10-19 Domino's Pizza Enterprises Limited System and method for monitoring delivery of orders amongst parties through use of a positioning or location system

Also Published As

Publication number Publication date
AU2014101356A4 (en) 2014-12-11
AU2014101356B4 (en) 2015-04-02
AU2015101096A4 (en) 2015-09-24
AU2015101096B4 (en) 2016-05-26

Similar Documents

Publication Publication Date Title
EP1883914B1 (en) System and method of tracking the movement of individuals and assets
US9377319B2 (en) Estimating times to leave and to travel
EP1280119B1 (en) Location management method and apparatus
US9749823B2 (en) Providing city services using mobile devices and a sensor network
KR100432268B1 (en) System and method of accessing and recording messages at coordinate way points
US8489113B2 (en) Method and system for tracking, monitoring and/or charging tracking devices including wireless energy transfer features
JP4662675B2 (en) Computing devices and methods context aware
US8306746B2 (en) Method and system for providing travel time information
KR100689954B1 (en) System and method of accessing and recording messages at coordinate way points
CA2823070C (en) Remote distribution of software updates in a transportation management network
KR100702501B1 (en) Wireless house server and method for communicating with the wireless house server
US6664922B1 (en) Method for distributing location-relevant information using a network
US8831627B2 (en) System and method for tracking, monitoring, collecting, reporting and communicating with the movement of individuals
JP3984002B2 (en) Electronic notification method and a mobile user terminal to-Doo list item
US9122542B1 (en) Location based reminders
JP5162505B2 (en) Environmental interactive context-aware devices, and methods
US20080174485A1 (en) Tracking System and Method with Asset Tool Bar for Polling, Message, Historic Report, Location, Map and Geo Fence Features
US20070210936A1 (en) System and method for arrival alerts
US7818317B1 (en) Location-based tasks
JP4806143B2 (en) Methods for policy decision and enforcement of context-oriented
US20080125965A1 (en) Tracking System and Method with Automatic Map Selector and Geo Fence Defining Features
US20090291672A1 (en) System And Method For Providing Personalized Automated And Autonomously Initiated Information Delivery And Chaperone Service
JP4138308B2 (en) Location-aware mobile phone and methods in the context-aware
US8055277B2 (en) Customized location tracking service
US20050143097A1 (en) System for providing location-based services in a wireless network, such as providing notification regarding meetings, destination arrivals, and the like

Legal Events

Date Code Title Description
ON Decision of a delegate or deputy of the commissioner of patents (result of patent office hearing)

Free format text: (2016) APO 13: DECISION: I AM NOT CURRENTLY SATISFIED THAT ORDERS UNDER SECTION 210 FOR THE PRODUCTION OF DOCUMENTS AND THE SUMMONS OF WITNESSES SHOULD BE ISSUED. I REFUSE THE REQUESTS FOR THE COMMISSIONER TO ORDER PRODUCTION OF DOCUMENTS IDENTIFIED AS REQUESTS 1 TO 4 IN MY REASONS BELOW. I ALLOW THE SECTION 36 REQUESTOR 14 DAYS FROM THE DATE OF THIS DECISION TO FILE FURTHER INFORMATION IN RELATION TO REQUEST 5 AND THE REQUEST FOR THE COMMISSIONER TO SUMMONS WITNESSES CONSISTENT WITH MY REASONS BELOW. IF NOT THESE REQUESTS WILL ALSO BE REFUSED.

Opponent name: DOMINO S PIZZA ENTERPRISES LIMITED

Effective date: 20160315

MK5 Application lapsed section 142(2)(e) - patent request and compl. specification not accepted