AU2023201233A1

AU2023201233A1 - Method, system, and device to monitor vehicles

Info

Publication number: AU2023201233A1
Application number: AU2023201233A
Authority: AU
Inventors: Paul Mitchell FENECH; Rylan Jeffrey KOLB
Original assignee: V Daq Pty Ltd
Current assignee: V Daq Pty Ltd
Priority date: 2023-02-28
Filing date: 2023-02-28
Publication date: 2024-09-12
Also published as: WO2024178463A1; AU2024266964A1

Abstract

A system (1) of monitoring a vehicle (3) having a truck (5) and at least one connected vehicle sub-unit (7), the system (1) comprising: at least one data collection device (11) and a server (31). The data collection device (11) is configured to: receive (120) signals (13) transmitted by one or more sensor units (15, 16) in the vicinity of the truck (5); and send (150), to a server (31), sensor data (23, 27) based on the signals (13). The server (31) is configured to: receive (112) a selection (17) of one or more selected sensor units (15) that are associated with the vehicle (3); receive (151) sensor data (23, 27); and identify (160) based on the sensor data (23, 27) whether one or more additional sensor units (16), that is not one of the selected sensor units (1), is following the truck (5). In some examples the server (31) is further configured to send control signals (41) to the vehicle (3) and/or sensor units (15, 16). 1/10 31 1 88 MEN EN Data store MN Server Network Organisation 73 18 60 28 /21,25, 41 Satellite Base station r------------ -------- -- ------- ----------t -------- , 66 Mobile communication device Data 6collection 163 Driver/ 1513 operator 1Sensor Sensor Sensor Sensor 15 Sensor 15 16 1 2 7 12 7 10 12 12' 14 . 5 10 8 12 3 7 Fig.I1

Description

1/10

31 1 88

MEN Data store EN MN

Server Network Organisation

73

18

60 28

/21,25, 41 Satellite Base station r------------ -------- -- ------- ----------t --------

, 66

Mobile communication device Data 6collection 163

Driver/ 1513 1Sensor operator Sensor Sensor Sensor 15 Sensor 15 16

12 7 12 7 10 12 12' 14 5 10 8 12 .

3 7 Fig.I1

"Method, system, and device to monitor vehicles"

Technical Field

[0001] The present disclosure relates to telematics methods, systems, and devices to monitor vehicles. This includes collecting and sending data associated with a vehicle, such as a prime mover or truck with trailer(s), for record keeping, reporting regulatory and/or fleet management purposes.

Background

[0002] There are business reasons, as well as compliance requirements mandated by governments, to have access to information concerning the weight of a heavy vehicle combinations, or trucks. A heavy vehicle combination is a truck or prime mover towing one or more trailers. Record keeping information about the weight of a heavy vehicle combination typically includes: identification information; order of the trailer(s) connected to the prime mover or truck; individual weights at the axle or axle groups; and the total weight of the combination. In the context of such road systems, it is to be appreciated weight and mass are related concepts and reference to weight is taken to be inclusive of mass.

[0003] Trucks and prime movers towing multiple trailers are becoming more popular globally due to the rise in safety and compliance technology and increase in governments willingness to permit the use of these larger, heavier, and more complex combinations. As an example, heavy vehicle combinations in Australia can be complex due to a combination of factors including: long vehicle length; heavy overall weight; and a significant number of trailers and associated axle groups. Additionally, the rate in which trailers can be interchanged or swapped between different trucks or prime movers is very frequent, and this makes record keeping a difficult task.

[0004] Existing solutions for record keeping include manual paper based records. This may include a driver physically walking around the combination to record identification, order of trailers, and weight via estimation, weight can be recorded using on-board weigh sensors via an analogue dial or digital display on the prime mover, truck or trailer, or using an in-ground weighbridge, or an alternate method. This does not provide accurate periodic measurements throughout a journey and would be impractical for drivers to record the weights at periodic intervals manually.

[0005] Some digital solutions exist where proprietary weight sensors are associated with an axle group (as slave sensor) that sends data to a proprietary central unit (e.g. master) in the prime mover or truck. The data from these sensors may be presented as information on a graphical display in the cab of the prime mover or truck for the driver or other operator to record. However, these existing solutions require user input such as correct connection (or pairing) of sensors. Furthermore, difficulties arise if a trailer uses another proprietary sensor system that is incompatible with the master proprietary central unit.

[0006] These solutions struggle to keep up with the complexity of trailer interchange as drivers fail to use the systems properly, resulting in low-assurance and inconsistent combination information, which cannot be used adequately for business and compliance requirements.

[0007] Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

[0008] Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present disclosure as it existed before the priority date of each claim of this application.

Summary

[0009] There is disclosed a method of monitoring a vehicle comprising a truck and at least one connected vehicle sub-unit, the method comprising: receiving a selection to associate the truck with one or more selected sensor units, wherein the selected sensor units are physically associated with respective vehicle sub-unit connected to the truck; periodically or continuously receiving, by a data collection device associated with the vehicle, signals transmitted by one or more sensor units in a vicinity of the truck. The method further includes determining from the signals: a first set of sensor data associated with the one or more selected sensor units and respective vehicle sub-unit; and a second set of sensor data associated with, if any, one or more additional sensor units in the vicinity of the truck that excludes the first set of sensor data. The method also includes: storing the first set of sensor data with associated time information; and sending the first set of sensor data to a server.

[0010] In some examples, the method further comprises: storing the second set of sensor data with associated time information; identifying whether one or more additional sensor units are following the truck based on the second set of sensor data; and responsive to identifying one or more additional sensor units following the truck, sending a notification to indicate the one or more additional sensor unit and/or an additional vehicle sub-unit.

[0011] In further examples of the method, the step of identifying whether on or more additional sensor units is following the truck is further based on additional contextual conditions including one or more of:

- movement of the truck;

- distance between the additional sensor unit and the data collection device or truck;

- signal strength of received signals associated with the additional sensor unit;

- identity of the additional sensor unit and/or respective additional vehicle sub-unit;

- historical or trend information; and

- third party input such as a third party software (for job management or compliance) or data input system.

[0012] In some examples of the method, the notification includes a request, recommendation, or control signal to include the one or more additional sensor units to the selection to associate the additional sensor unit, and/or additional vehicle sub-unit, to the truck.

[0013] In some examples, the method further comprises: sending the second set of sensor data to the server, wherein the step of identifying whether one or more additional sensor units is following the truck is performed by the server.

[0014] In some examples of the method, the step of identifying whether one or more additional sensor units is following the truck is performed by the data collection device.

[0015] In some examples of the method, the step of sending the first set of sensor data to a server comprises: sending via an embedded second communication module of the data collection device to the server; or sending from the data collection device, via a mobile communication device, to the server.

[0016] In some examples, the method further comprises: determining, based on the received first set of sensor data and/or second set of sensor data, one or more control signals; and sending one or more control signals to the data collection device, truck, vehicle sub-unit, one or more sensor units, and/or one or more actuators associated with the vehicle.

[0017] In further examples of the method, the one or more control signals include one or more of:

- a request to send further sensor data;

- power settings and/or actuation of a sensor unit;

- pairing of additional sensor units; and

- mesh/network settings for the sensor units.

[0018] There is also disclosed a data collection device to monitor a vehicle having a truck and at least one connected sub-unit, wherein the data collection device comprises: a first communication module, a memory, and a processing device. The first communication module is configured to periodically, or continuously, receive signals transmitted by one or more sensor units in the vicinity of the truck. The memory is configured to store: selection data indicative of a selection of one or more sensor units associated with the truck, wherein the selected sensor units are physically associated with respective vehicle sub-unit(s) connected to the truck; and sensor data. The processing device is configured to: determine from the signals received at the first communication module:(i) a first set of sensor data associated with one or more selected sensor units and respective vehicle sub-unit; and (ii) a second set of sensor data associated with one or more sensor units in the vicinity of the truck that exclude the first set of sensor data. The processing device is further configured to: store, in the memory, at least the first set of sensor data with associated time information; and send the first set of sensor data to a server.

[0019] In some examples of the data collection device, the processing device is further configured to: store, in the memory, the second set of sensor data with associated time information; identify whether one or more additional sensor units is following the truck based on the second set of sensor data; and responsive to identifying one or more additional sensor units following the truck, send a notification to indicate the one or more additional sensor unit and/or an additional vehicle sub-unit.

[0020] In some examples of the data collection device, the notification is sent to a user interface associated with the data collection device, a portable communication device associated with a user of the vehicle, a processing device of the vehicle, and/or the server.

[0021] In some examples of the data collection device, the processing device is further configured to: send the second set of sensor data to the server to enable the server to identify whether one or more additional sensor units is following the truck based on the second set of sensor data; and receive from the server, in response to identification of one or more additional sensor units following the truck, a notification to indicate the one or more additional sensor unit and/or additional vehicle sub-unit.

[0022] In some examples, the data collection device further comprises: a second communication module configured to communicate with a communications network, wherein the first set of sensor data is transmitted to the server via the second communication module and communications network.

[0023] In some examples, of the data collection device, the processing device is further configured to: receive one or more control signals from the server, wherein the control signals are determined by the server based on the first set and/or second set of sensor data; and send, via the first communication module or other communication module, the one or more control signals to the truck, vehicle sub-unit, one or more sensor units, and/or one or more actuators associated with the vehicle.

[0024] There is also disclosed a system of monitoring a vehicle having a truck and at least one connected vehicle sub-unit, the system comprising: at least one data collection device; and a server. The at least one data collection device is configured to: receive signals transmitted by one or more sensor units in the vicinity of the truck; and send, to a server, sensor data based on the signals. The server is configured to: receive a selection of one or more selected sensor units that are associated with the vehicle; receive sensor data; and identify based on the sensor data whether one or more additional sensor units, that is not one of the selected sensor units, is following the truck.

[0025] In some examples of the system, the server is further configured to: determine based on at least the sensor data, one or more control signals; and send one or more control signals to the data collection device , truck, vehicle sub-unit, one or more sensor units, and/or one or more actuators associated with the vehicle.

[0026] There is also disclosed a method of monitoring one or more vehicles at a server, wherein each vehicle comprises a truck and at least one connected vehicle sub-unit, the method comprising: receiving sensor data from a data collection device associated with the vehicle, wherein the sensor data is based on signals transmitted by one or more sensor units in the vicinity of the truck and received by the data collection device; identifying, based on the sensor data, specific sensor units that are following the truck; and identifying one or more vehicle-sub units that are connected to the truck based on the identified specific sensor units following the truck.

[0027] There is also disclosed a method of monitoring one or more vehicles at a server, wherein each vehicle comprises a truck and at least one connected vehicle sub-unit, the method comprising: receiving sensor data based on signals transmitted by one or more sensor units in the vicinity of the truck; identifying, based on the sensor data, specific sensor units that are following the truck; and identifying one or more vehicle-sub units that are connected to the truck based on the identified specific sensor units following the truck.

[0028] In some examples the method further comprises: storing in a data store, vehicle data indicative of: the identified specific sensor units following the truck; the identified one or more vehicle sub-units connected to the truck; and sensor data associated with the vehicle.

[0029] In some examples, the method further comprises: determining, based on at least the sensor data, one or more control signals; and sending one or more control signals to the data collection device, truck, vehicle sub-unit, one or more sensor units, and/or one or more actuators associated with the vehicle.

Brief Description of Drawings

[0030] Examples of the present disclosure will be described with reference to:

[0031] Fig. 1 is a schematic of a system to monitor a vehicle;

[0032] Fig. 2 is a schematic diagram of a data collection device used in the system of Fig. 1;

[0033] Fig. 3 is a flow diagram of a method of monitoring a vehicle including receiving sensor data to be stored at a server;

[0034] Fig. 4 is a flow diagram of a method of identifying additional sensor units following a vehicle;

[0035] Fig. 5 is a flow diagram of a method of automatically identifying sensor units and vehicle sub-unit (such as a trailer) associated with the vehicle;

[0036] Fig. 6 is a flow diagram of a method of generating control signals to be sent to the vehicle 3;

[0037] Fig. 7 is a schematic and flow diagram of a specific example implementation of the system;

[0038] Fig. 8 illustrates examples of vehicles including truck and trailer combinations;

[0039] Fig. 9 illustrates a variation of the system where each sensor unit is also a data collection device unit; and

[0040] Fig. 10 illustrates an example of a processing device.

Description of Embodiments

[0041] Overview of the system 1

[0042] Fig. 1 illustrates a schematic of a system 1 of monitoring vehicles 3 having a truck 5 and at least one connected vehicle sub-unit 7.

[0043] One or more sensor units 15, 16 are associated with respective vehicle sub-units 7 (where examples of the vehicle sub-unit 7 may be a trailer 10 or an axle group 12, or part of the truck 5). Signals 13 are transmitted from the sensor units 15, 16, where the signals include measurements or other data. The measurements or other data may be indicative of one or more of weight, forces, acceleration, speed, temperature, time, state of wear, tyre pressure, identification data, location, cumulative time of operation, service intervals, status, error states, notifications, etc. In some examples, the sensor units 15, 16 broadcast the signals 13 wirelessly (such as using Bluetooth protocols).

[0044] The system 1 includes at least one data collection device 11 that is associated with a respective vehicle 3, and in some examples the data collection device 11 is located with the truck 5. The data collection device 11 is configured to receive 120, periodically or continuously, the signals 13 transmitted by one or more sensor units 15, 16 in the vicinity of the truck 5. The data collection device 11 has a processing device 57 configured to process the received signals 15 to determine sensor data 23, 27 for further processing and analysis. This can include at least part of the processing steps of a method 100 of monitoring the vehicle 3 discussed in further detail below. The data collection device 11 is also configured to send sensor data 23, 27 to a server 31 of the system 1.

[0045] The server 31 includes a processing device to perform steps of the methods 100, 200. The server 31 may have an associated data store 73 to store sensor data and other data received from the data collection device 11. The data store 73 may store such data for regulatory and compliance purposes as well as business intelligence and fleet management purposes. The server 31 can also be used to identify sensor unit 16 following a truck 5 and to send control signals. It is to be appreciated that the server 9 may be a cloud-based server.

[0046] The system 1 can be used for the following methods:

i. Monitor the vehicle by collecting sensor data;

ii. Identifying sensor units and respective vehicle sub-units

iii. Controlling sensors, actuators, and other vehicles components

[0047] These methods 100, 200 will be describe in separate headings. Components of the system 1 will now be described in detail.

[0048] Sensor units 15/16

[0049] The sensor units 15, 16 are configured to include at least one sensor to receive information associated with the vehicle sub-unit 7, nearby elements, and/or surrounding environment. In heavy vehicle applications, a crucial measurement is weight of the vehicle 3, including: the overall weight of the vehicle, the weight corresponding to particular axles or axle groups 12, and/or the weight at a trailer 10. Thus in some examples the sensor of the sensor unit 15 receives measurements to indicate weight (or force) applied at vehicle sub-unit 7.

[0050] An example of a sensor unit 7 providing weight information is the wireless axle load sensor GNOM DDE S7. In some examples, the sensor units 15 include a strain gauge to measure deformation or displacement that can then be used to determine applied forces on a spring or structure in the vehicle sub-unit 7. In other examples, axle load may be measured by displacement of components such as a leaf spring relative to another component of the vehicle 3. In yet another example where air suspensions are used, measurements of the air pressure is indicative of the weight or load at the axle.

[0051] In some example, the sensor units 15/16 communicate with other devices, such as the data collection device 11 and/or other sensor units 15/16 wirelessly. This can include radio frequency wireless transmission. In some examples, the sensor unit 15 has, or is associated with, a communications module to enable wireless transmission of the signals 13. This may include signals 13 transmitted according to Bluetooth protocol. In some examples, this includes Bluetooth Low Energy (BLE). In some examples, this includes BLE Coded PHY that enables extended range signal.. In some examples, the signals 13 are broadcast (e.g. advertised) by the sensor units so that at least portions of the data can received and understood by other Bluetooth capable devices within the vicinity. In particular, these signals 13 may be understood by such devices without specific pairing with another Bluetooth device in master and slave relationship. This broadcast signal may be advantageous by enabling easy receipt of data and without requiring pairing operations that may require diligence and effort of a human operator. It also enables easy receipt of data for a vehicle combination even if the truck 5 has never been paired with a particular trailer 10. The broadcast signal may also avoid issues with proprietary sensor units that require pairing with proprietary controllers and/or masters. This may enable sensor units 15 from multiple manufacturers to be used in the system 1.

[0052] In some examples the broadcast signal 13 includes one or more of:

- a sensor identifier of the sensor unit 15;

- a vehicle sub-unit identifier to enable association of the sensor unit 15 to a physically associated vehicle sub-unit 7;

- an organisation identifier to enable association with an organisation 88, business, operator, etc;

- measured data from the sensor indicative of the measurements, such as weight, forces, acceleration, etc;

- time information;

- location information.

[0053] It is to be appreciated other wireless transmission protocols may be used by the sensor unit 15, including ZigBee, Wi-Fi, LTE, etc.

[0054] The sensor unit 15/16 may include an independent power source. In other examples, the sensor unit 15/16 may be powered by vehicle supplied power, such as 12V, 24V, 48V, from the truck 5. Further examples may include combinations of battery and vehicle supplied power.

[0055] In some examples, some of the sensor units 15/16 may be in wired communication to transmit signals 13. For example, an axle group may have a plurality of sensor units 15/16 where a subset of the sensor units 15 has a wireless communication module. The remaining sensor units may transmit signals 13 via a wire to the sensor unit 15 with the wireless communication module that, in turn, retransmits the signal 13 to the data collection device 11.

[0056] It is to be appreciated that the sensor unit 15/16 may receive other information. In some examples, the sensor unit 15/16 also includes a satellite navigation module to receive signals from one or more satellites 28. The satellite navigation module may receive signals from GPS (Global Positioning System), GLONASS (GLObal Navigation Satellite System), or other navigation systems. This may also include receiving supplementary signals, such as from a Differential GPS System, and augmentation signals such as WASS (Wide Area Augmentation System). The satellite navigation module may also utilise Assisted GPS. Receiving position information from the satellite navigation module can be advantageous in ensuring quality and integrity of sensor data (e.g. sensor data from a single vehicle can be associated with a time and location for data from each sensor, and all sensors for a vehicle should have a location that match or are in close proximity).

[0057] It is to be appreciated that in some examples, the sensor unit 15/16 has a communication module (or further communication module) to enable extended communications such as connection with the network 18 via a cellular network 60. By having cellular communication, such as LTE, 5G, this may enable some sensor units 15/16 to communicate with the server 31 independent of a distinctly separate data collection device 11. This may be useful as an alternative or supplementary communication means to the data collection device 11 in case there is an error state with the data collection device. In other examples, where the data collection device 11 is a mobile communication device 66 of the operator, this alternative communication means enables the server 31 to receive updated information on the vehicle 3 if the operator is absent. I

[0058] In some other examples, it may be desirable for at least some of the sensor units 15, 16 to communicate with the server 31 without going through the data collection device 11. This may be for data integrity and/or security reasons where the sensor unit 15, 16 may belong to another organisation (such as government, regulatory body, an environmental protection organisation) and they do not want to rely on the data collection device 11 to pass on data but instead use their own independent communication means. In such use cases, the data collection device 11 may still receive signals 13 from such sensor units 15, 16 to enable proximity detection. That is, there are multiple data paths that can be used for different purposes.

[0059] Data collection device 11

[0060] Fig. 2 illustrates a schematic example of a data collection device 11. The data collection device 11 includes a processing device 57 that communicates via a bus 58 to other components such as a memory 53, a first communication module 51, and in some examples a second communication module 59. The data collection device 11 may also have a user interface 63.

[0061] The first communication module 51 periodically, or continuously, receives 120 signals transmitted by the one or more sensor units 15, 16. The first communication module 51 may include a RF receiver or transceiver configured to receive protocols of signals of the sensor unit 15 (e.g. Bluetooth, ZigBee, and Wi-Fi). In some examples, the first communication module 51 may receive broadcast signals from the sensor units 15, 16 without requiring master to slave type pairing. In other examples, select sensor units 15 may by paired to the data collection device 11.

[0062] The second communication module 59 is configured to communicate information to the server 31 via a network 18. This can include sending sets 21, 25 of sensor data 23, 27 to the server 31 for record keeping and/or further processing. This can also include the second communication module 59 receiving control signals 41, via the network 18, from the server 31. In some examples, the second communication module 59 communicates via cellular networks 60 that operate on (but not limited to) GPRS, 3G, 4G/LTE, 5G technology which, depending on reception, advantageously enables continuous or near continuous communications with the server 31.

[0063] The second communication module 59 may communicate through another network, such as wireless local area network operating of Wi-Fi technology. This, in turn, may be in communication to a wider network such as the internet. Reliable Wi-Fi networks may be intermittent and the second communication module 59 may be configured to send and receive data at certain times and intervals such as during rest and refuelling stops, truck depots, warehouses, etc.

[0064] The second communication module 59, in the illustrated example is embedded in the data collection module 11. In some examples, the first and second communication modules 51, 59 although performing different functions, may be physically performed by a common communication module. For example, a common communication module may communicate via a Bluetooth protocol to receive signals 13 from the sensor units 15 and also communicate, via Bluetooth, to a mobile communication device 66. The cellular network 60 capabilities of the mobile communication device 66 can then be used to communicate with the server 31 via the network 18.

[0065] The processing device 57 may be configured to process data and to perform at least some of the steps of the method 100 that will be discussed in a separate section below.

[0066] The memory 53 may store instructions and data for implementing the method 100 performed by the processing device 57. In some examples, the data stored in the memory 53 includes sets 21, 25 of sensor data 23, 27 based on the received signals 13 from the sensor units 15, 16. This storage of data may be useful to act as a data buffer if there is intermittent communication with the server 31. Furthermore, there may be practical reasons, operational reasons, and regulatory requirements to store the sensor data 23, 27 with the data collection device 11. The memory 53 may also store vehicle data, identification data, or other data such as location, time, weather, etc. In some examples, this includes non-volatile memory storage.

[0067] The user interface 63 enables user interaction with an operator 6. This can include an output indicative of notifications and other data, which could be a visual, audible, tactile output. The user interface 63 may also include a user input to enable the operator 6 to enter data, such as information regarding the vehicle, operator, operation of the vehicle, connected vehicle sub-units 7, etc. In some examples this can include selection 17 of the one or more sensor units 15 (which may be indicative of a selection of a respective vehicle sub-unit 7). In some examples, the user interface 63 may include a touchscreen interface. In yet another example, a mobile communication device 63, communicatively coupled to the data collection device 11, may function as the user interface 63. It is to be appreciated that in some alternatives, the user interface 63 is not direct communication with the data collection device 11. Instead the communication may be between the user interface 63 to the server 31 to send and receive information to the operator 6. In turn, some of this information may be directly, or indirectly, communicated from the server 31 to the data collection device 11.

[0068] The data collection device 11 may be integrated with the vehicle 3, retrofitted to the vehicle 3, or placed inside the vehicle 3. For example, the data collection device 11 may be mounted to the dashboard, mounted to the windscreen, located in a glovebox, a storage area, under the bonnet, or other compartment of the vehicle 3. In some examples, the data collection device 11 may be integrated with other electronics and telematics devices of the vehicle, such as the entertainment, monitoring and control, and/or navigation system. Whilst some examples of the data collection device 11 includes embedding with the vehicle 3, in alternative examples the data collection device 11 may be incorporated as part of, or a modified form, of a mobile communication device 66 such as a smart phone or tablet.

[0069] The data collection device 11 may also include a satellite navigation module to receive signals from one or more satellites 28 to enable determination of position of the vehicle.

[0070] Mobile communication device

[0071] The mobile communication device 66 maybe used in some example implementations of the system 1. In some examples, the mobile communication device 66 performs all, or substantially all, of the functions of the data collection device 11. This may be advantageous as a high proportion of people already carry a mobile communication device.

[0072] In other examples, the mobile communication device 66 may supplement or complement parts of the system 1. As noted above, the mobile communication device 66 may function as a user interface 63. The mobile communication device 66 may enable the operator to better display the sensor data, manipulate the data, forward the data for reporting purpose, etc. The mobile communication device 66 may also have a more powerful processing device to process the data. In other examples the mobile communications and network capabilities of the mobile communication device may be used to transmit and receive data to the network 18 and server 31.

[0073] In some examples, an application is run on the mobile communication device 66 to enable the function as a data collection device or to interface with parts of the system 1. This may include secure access to data from the data store 73 of the server 31.

[0074] Server 31

[0075] The server 31 includes one or more processing device to perform steps of the methods 100, 200 and has an associated data store 73. The server 31 may be operated by a business organisation 88 (such as the operator of a fleet of vehicles 3), a third party fleet management business, a third party computing service, a government or regulatory entity, etc. In some examples, the data store 73 is configured to be accessible by multiple entities, which may be through a secured API. In other examples, an application (including a web application) can be used to access the data. This may include presenting the information in a dashboard, and include tools for analysing the data, and creating reports.

[0076] In some examples, the data in the data store 73 may be available for commercial or research purposes. This may include selling, or providing a subscription service for the data in the data store.

[0077] The server 31 may perform several functions, including:

- Record keeping, such as recording vehicle and sensor data for business and commercial purposes as well as compliance purposes;

- Processing data for identification purposes, such as identifying use and state of vehicles 3 (including associated vehicle sub-units such as trailers), combination of truck and trailers being used, wear monitoring, and maintenance requirements; and

- Controlling sensors, actuators, or other components of the vehicle 3 based on sensor data and identified issues in the earlier functions.

[0078] Vehicle 3

[0079] Fig. 8 illustrates non-limiting examples of vehicles 3. The first example vehicle 3 is a combination that includes a rigid truck 5 with two axle groups 12 and a trailer with two axle groups 12'. In this example, the rigid truck 5 carries and supports cargo load. In some examples, the truck 5 and trailer are connected via intermediate couplings.

[0080] The second example vehicle 3' is a combination that includes a truck 5' (in the form of a prime mover) with two axle groups 12. The example prime mover 5' includes a fifth wheel to connect to a first trailer 10' which has one axle group 12'. A second trailer 10" is connected to the axle group 12' of the first trailer 10'. The second trailer 10" also has a single axle group 12".

[0081] The third example vehicle 3" is a variation of the second example vehicle 3' with a graphical representation of weight distribution of the vehicle 3" to the axle groups 12, 12', 12". The overall weight of the vehicle 3" is 62.5 tonnes. This is distributed with 6 tonnes at a first axle group 12 of the prime mover 5' and 16.5 tonnes at a second axle group 12 of the prime mover 5'. It will be appreciated that a portion of the 16.5 tonnes at the second axle group 12 is attributable to the weight of the first trailer 10'. The axle group 12' of the first trailer 10 has 20 tonnes which will be attributable to the weight of the load on both the first trailer 10' and the second trailer 10'. Finally, the axle group 12" of the second trailer 10 has 20 tonnes that is attributable to the load on the second trailer 10".

[0082] An important factor to measure for road safety is the weight (mass) distribution and the overall weight. By having sensor units 15 located at each of the axle groups 12, 12', 12", this enables the operator (as well as business owners and regulator) to have real-time, or near real-time mass data of the vehicle. This increase confidence that a vehicle 3 has been loaded safely and can operate safely on roadways. This can also be used to alert a driver or operator if weight has significantly changed which can indicate a loss or spillage of the load.

[0083] In the context of this description a truck 5 includes a part of the vehicle 3 that is configured to tow a trailer. That is, the truck include a power pack (such as a diesel engine, petrol engine, electric motor, etc.) to drive the vehicle combination. The truck may include a rigid truck, prime mover, tractor, etc. In other examples, it is to be appreciated other vehicle types that tow a trailer could use this system. For example, a light utility vehicle, sports utility vehicle, minibus, light passenger car, could be configured to tow a caravan, or other trailer containing substantial weight that needs to be monitored.

[0084] In the context of this description, a vehicle sub-unit 7 can include the axle group 12 (or components thereof), a trailer 10, or other components that can forms part of, or can be connected to, the vehicle 3.

[0085] In some other examples, the vehicle sub-unit can be part of the truck 5. For example, the vehicle sub-unit may be a tyre and wheel combination and the sensor unit 15 is a tyre pressure monitoring unit. In other examples the vehicle sub-unit may be an axle group, suspension assembly, brake assembly of the truck 5, whereby the respective sensor unit is also at the truck 5.

[0086] It is to be appreciated that in some examples or scenarios, the system 1 may be operated while the vehicle 3 does not have a trailer 3 under tow, and that the system is receiving sensor data from sensor units 15 associated with the truck 5 for record keeping and other purposes described herein. In some example the selection 17 may include removal of vehicle sub-unit (7) such as removing a trailer (10) that was previously selected for another journey.

[0087] The various methods 100 performed by the system 1, the data collection device 11, and the server 31 will now be described in examples.

[0088] Overview of a method of collecting sensor data

[0089] Turning to Fig. 3, a first method 100 of collecting sensor data is illustrated. This examples includes a selection 17 of sensor units 15 that should be associated with a vehicle 3. Typically, this may include an operator 6 entering, via a user interface 63, details of the truck 5 and trailer 10 combination, which in turn can be used to specify the selected sensor units 15 that should be associated with the vehicle 3/truck 5. It is to be appreciated that this can be an explicit selection of a selected sensor unit 15 (e.g. a serial number or identifier of the sensor) or an indirect selection such as entering an identifier of a specific sub-unit and whereby the system 1 will determine the respective selected sensor unit 15.

[0090] In practical examples, the selected sensor units 15 are physically associated with respective vehicle sub-unit 7 (such as a trailer 10 or axle group 12) that the operator connects to the truck 5. The selection 17 may also include the order in which the vehicle sub-units 7 are connected (such as the order of trailers in a long vehicle combination).

[0091] For this example (and with reference to Fig. 1), the operator 6 selects sensor units 15 from the first two respective trailers 10 (as a vehicle sub-unit 7). For illustrative purposes, the operator 6 inadvertently omits to select sensor units 16 of the third trailer 14.

[0092] The method includes sending the selection 17 that is then received 110 by the data collection device 11 and/or received 112 at the server 31. It is to be appreciated that in some alternatives, the selection may be made at multiple points in the system, and in some examples the selection 17 may even be initiated as the server 31 to specify, to the operator 6, which trailers 10 should be connected to the truck 5.

[0093] The method 100 further includes receiving 120 signals 13 from sensor units 15, 16 in the vicinity of the truck 5. This can be achieved with the first communication module 51 of the data collection device 11 that may continuously, or periodically, receive transmitted data from the sensor units. In some examples, this may include receiving signals 1 from the sensor units 15 every second. However, it is to be appreciated this level of frequency may be lower. For example, receiving such signals 15 once every minute may satisfy reporting or regulatory requirements for timely and updated data whilst, potentially increasing battery life by reducing the frequency of transmitting, receiving, and processing of the signals 13.

[0094] It is to be appreciated that the frequency of receiving data may be faster than described above (such as more than once a second) and the skilled person would appreciate that this can be adjusted based on use case requirements.

[0095] The received 120 signals 13 may come from the selected sensor units 15 (that were earlier selected by the operator 6) as well as other sensor units 16 within wireless signal communication range. Other sensor units 16 (as illustrated in Fig. 1) includes additional sensor units 16 of an additional trailer 14 that the operator 6 had omitted to select. It can be appreciated that signals from sensor units of other passing, or parked, vehicles may also be received from time to time.

[0096] The method 100 further includes selecting, from the received signals 13, relevant data for reporting. To achieve this, the method 100 includes (with reference to Fig. 3) determining 130 from the signals 13:

i. a first set 21 of sensor data 23 associated with the selected sensor units 15; and

ii. a second set 25 of sensor data 27 associated with, if any, one or more additional sensor units 16 in the vicinity of the truck 5 that excludes the first set of sensor data 23. That is, sensor data that is not from the selected sensor units 15 that are known to be connected to the truck 5.

[0097] The first set 21 of sensor data 23 is clearly relevant to the vehicle 3 as the corresponding sensor units 15 were selected by the operator. The first set 21 of sensor data 23 is then stored 140, with associated time information 29, and sent 150 to the server 31 for record keeping purposes. In some examples, the storing the sensor data 23 at the data collection device 11 may be temporary (e.g. for the purposes of buffering before sending to the server 31). In other examples, the sensor data 23 (or parts thereof) are stored at the data collection device 11 (or an associated data store) to provide an on board record of data. In yet other examples, sensor data 23 may be transmitted to a mobile communication device 66 for record, reporting, and review.

[0098] It is to be appreciated that in some examples, the selection of selected sensor units 15 may be missing or non-existent. For example, when there is a new vehicle 3 or part of the system has been reset. In such cases, the described system 1 and method 100, 200 may continue to function and with the result that the first set 21 would have no valid sensor data 23 and where most (or all) of the signals 13 would be categorised as second set 25 of sensor data 27 associated with the additional sensor units 16.

[0099] The second set 25 of sensor data 27 may, in some circumstances, be excluded from further processing. For example, if it is determined that the signal 13 was from a sensor unit 16 of an unrelated vehicle passing by the subject vehicle 3.

[0100] However, the second set 25 of sensor data 27 can be useful to determine additional information, such as context (for example, amount of traffic, proximity of other vehicles, etc.). In addition, the second set 25 of sensor data 27 may be relevant as it could be indicative of a sensor unit 16 connected to the vehicle 3 but omitted from earlier selection. A method of identifying such additional sensors is described under a separate heading below.

[0101] The server 31 receives 151 the sensor data (which may be the first set 21 and/or second set 25) and stores 156 the sensor data in a data store 73. This record in the data store 73 may be selectively available based on use case. In some examples, the sensor data is confidential information for the organisation operating the vehicle 3. In further examples, the sensor data, and other data, may be kept or made available to a regulatory authority. In yet further examples, the sensor data is available publicly, by subscription, or purchase.

[0102] Overview of the method of identifying additional sensors 16

[0103] Referring to Fig. 4, this illustrates an example of a method of identifying additional sensor units 16 and respective additional vehicle sub units 8.

[0104] In alternative examples, the method is performed at the server 31. An advantage of performing the method at the server 31 is greater processing power and potentially greater access to records and other data to assist identification (such as a library in a data store 73 that links identifiers of sensor units 16 to respective additional vehicle sub units 8, fleet details, ownership details, etc.). If the method is performed at the server 31, the data collection device 11 can send 152 the second set 25 of sensor data 27 to the server 31; and once processed by the server 31, receives 163 a notification 33 regarding any identified additional sensor units 16 and/or additional vehicle sub-units 8.

[0105] In alternative examples, the method maybe performed at the data collection device 11. This may be advantageous in situations where the vehicle is travelling in areas without cellular networks or other network connections to enable reliable and frequent communication with the server 31.

[0106] Referring to Fig. 4, the method includes storing 142 the second set of sensor data with associated time information. Storage may be useful as patterns over time of the signals (and sensor data 27) can be useful to differentiate whether the sensor unit 16 is passing by versus following the truck 5 in a steady regular manner (as would be expected if they were connected).

[0107] The method also includes identifying 160 whether one or more additional sensor units 16 are following the truck 5 with the second set 25 of sensor data 27. This can include determining whether a signal 16 corresponding to a particular and specific additional sensor unit 16 has been detected consistently and for at least a threshold period.

[0108] In some examples, the step of identifying 160 whether the additional sensor units is following the truck is based on additional contextual conditions including one or more of:

- movement of the truck 5;

- distance between the additional sensor unit 16 and the data collection device 11 or truck 5;

- signal strength of received signals 13 associated with the additional sensor unit 16;

- identity of the additional sensor unit 160 and/or respective additional vehicle sub unit 8;

- historical or trend information; and

[0109] Responsive to identification of an additional sensor unit 16 following the truck 5, a notification 33 can be sent 162 to the operator 6 or other entity of this fact. This notification may include details of the specific additional sensor unit(s) 16 and/or an additional vehicle sub-unit 8. This can include querying a database so that the notification can be specific, including identifying the specific trailer 14 (such as by a serial number or licence plate) that is associated with the identified additional sensor unit 16.

[0110] The notification 33 can be useful to notify the operator 6 of an error. In some examples, this can simply be a trailer 16 or axle group 12' that was physically connected to the vehicle 3 but where the appropriate data entry to the system 1 was not performed correctly (such as selecting the wrong trailer). This notification can also indicate other technical errors. For example, a mechanic may have mounted a sensor unit to an incorrect vehicle sub-unit 7 with the result of the data collection device 11 receiving signals 13 from an unexpected sensor unit.

[0111] The notification 33 maybe sent to one or more of the following: to a user interface 63 associated with the data collection device 11, a mobile communication device 6 associated with a user 67 of the vehicle 3, a processing device 69 of the vehicle 3, and/or the server 31.

[0112] In some examples, the notification 33 includes a request 35, or recommendation 37 to include the one or more additional sensor units 16 to the selection 17. If accepted, this associates the additional sensor unit 16, and/or additional vehicle sub-unit 8, to the truck 5. The result is that further signals from these additional sensor units 16 is expected and will form part of the first set 21 of sensor data 23.

[0113] In other examples 33 the notification 33 is, or is associated with, a control signal or other direction to include the one or more additional sensor unit(s) 16 into the selection 17. This may be suitable if the system 1 has high confidence that the additional sensor unit 16 should be associated with the vehicle 3 and thus the system 1/server 31 automatically (i.e. without human intervention) adds the additional sensor unit(s) to the selection 17.

[0114] In further examples, the system may identify that the expected sensor units 15 and trailers 10 are connected to the vehicle 3, but that the actual order of trailers entered into the records are incorrect. That is the operator may have selected the correct vehicle sub-units but entered the order incorrectly during the selection 17 process. This may be error may be detected based on signal strength to the data collection device 11. The notification 33 may include a recommendation to reorder the selection 17.

[0115] Overview of a method 200 of automatically identifying sensor units

[0116] In some examples the method 200 includes automatically identifying 261 sensor units 15 following the vehicle 3 and automatically identifying the vehicle sub-units 7 connected to the truck 5. This reduces the step of having an operator 6 having to explicitly select which trailer 10 or axle group 12 is connected to the truck and can reduce the instances of an operator entering the wrong data or manipulating the data.

[0117] Referring to Fig. 6, the data collection device 11 sends 150, 152 the sensor data 23, 27 that is based on the signals 13 from the sensor units 15, 16. The sensor data 23, 27 is received 251 at the server 31 to identify 260 specific sensor units 15, 16 that are following the truck 5. This can include identifying 260 a serial number or other identifier specific to the sensor unit 15, 16 within the sensor data. As noted above, the signals 13 may include various data that could be used to identify the sensor unit 15, 16, that may include: sensor identifier; a sub-unit identifier; and organisation identifier, model number, ownership information, etc.

[0118] To determine whether a specific sensor unit 15, 16 is following the truck 5, data such as timing information, location information, signal strength, can assist in determining that the sensor unit 15. 16 is following the truck over a period of time. The period of time, and context, may be specified by operators but truck and trailer combinations are in practice used for periods of time in the order of minutes, hours, or even days. Thus in one example, a specified threshold period may involve confirmation that signals 13 from a sensor unit 15, 16 are received at the data collection device for 1 minute or more whilst the truck 5 is in motion (or has moved during that period). In other examples, this may be more such as 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, or more. It is to be appreciated that a longer specified period would reduce the likelihood of identifying sensor units of other passing vehicles as following the truck 5. Conversely a shorter specified period may decrease the time for the server 31 to identify the sensor unit 15, 16 following the truck 5.

[0119] The method also includes identifying 261 one or more vehicles sub-units 7, 8 that are connected to the truck 5. This can be based on the identified specific sensor units 15, 16 that were following the truck 5. In some examples, the signals 13 from the sensor units 15, 16 may include a message identifying the vehicle sub-unit 7, 8, the owner of the sub-unit 7, 8, or even a related truck 5. For example, in a fleet of vehicles and trailers, the organisation 88 may have assigned specific identifiers for all of the sensor units 15, 16 and associated vehicle sub units 7, 8, and have signals 13 sent from these sensor units 15, 16 encoded with messages with these identifiers.

[0120] In other examples, a library or look-up table in a database is used to identify the association between a specific sensor unit and respective vehicle sub-unit. This database may be stored in the data store 73 of the server 31, stored at the organisation 88, or even stored at a regulatory body (such as a vehicle registration database of a government body).

[0121] The method 200 also includes storing 265, in a data store, vehicle data indicative of:

i. the identified specific sensor units 15, 16 following the truck 5;

ii. the identified vehicle sub-units 7, 8 following the truck 5, which indicates those vehicle sub-units 7, 8 are connected to the truck 5 to form the vehicle;

iii. Sensor data that was received and associated with the vehicle 3.

[0122] Thus the above described process enables automatic identification of vehicle sub units 7, 8 such as trailer 10 and axle groups 12 that should be associated with the vehicle 3. This can reduce the likelihood of data entry errors or omissions from the operator 6. This may also serve as a check of operator data entry and selection 17 and it is to be appreciated that such systems may also allow operators 6 to manually enter or correct identification information.

[0123] In the example described in Fig. 5, the server 31 performs the process of automatic identification. However, it is to be appreciated that some, or all, of these steps in alternative variations be performed by the data collection device 11 or at a mobile communication device 66. Yet further variations may include the method being performed by a combination of the above mentioned devices and server.

[0124] The lower portion of Fig. 5 shows the steps of the server 31 determining 270 control signals 41 that are sent 272 to perform operations at other nodes and devices. These will be discussed in detail in a separate example below.

[0125] Overview of a method of sending control signals

[0126] With reference to Fig. 6, the system and method can also include generating and sending 172, 272 control signals 41. These control signals are then sent to the data collection device 11, truck 5, vehicle sub-unit 7, sensor units 15, 16, and/or actuators associated with the vehicle3. In practical examples, this may include controlling specific sensor units 15, 16 such as increasing sampling frequency, querying for more data, changing power state, resetting, communication pairing or other network settings, changing device settings, etc.

[0127] Various sensor data 23, 27 are sent 150, 152 to the server 31 (or other device or node performing the method). This may be based on a continuous, periodic, stream of sensor data 23, 27 or ad hoc reception of sensor data. In some examples a received notification 33 may also be a trigger, or contain relevant information, for the control signal 41.

[0128] The method includes determining 170, 270 one or more control signals 41 based on the sensor data 23, 27. For example, if the sensor data 23, 27 indicates particular conditions, there may be advantages to change the mode or function of the sensor units 15, 16 or other devices at the vehicle. For example, if the sensor data 23, 27 indicates high loads, temperature, or particular context (such as the vehicle being in operation for an extended period of time) it may be desirable to obtain more information and an appropriate control signal 41 may be to turn on further sensors, or increase sampling frequency, etc. On the other hand, if the sensor data 23, 27 indicated normal operating conditions or that the vehicle is parked, an appropriate control signal 41 may include switching sensor units 15, 16 to a low power mode with reduced sampling frequency and/or reporting frequency.

[0129] Examples of control signals 41 may include one or more of:

- a request to send further sensor data;

- power settings and/or actuation of a sensor unit 15;

- pairing of additional sensor units 16 that are identified as being associated with the vehicle 3; and

- mesh/network settings for the sensor units 15.

[0130] The control signals 41 are sent 172, 272 by the server 31 to the respective devices that need to be controlled. This may include the server 31 sending the control signals 41 via the network 18 to be received 174 by the data collection device 11. The data collection device 11 can, in turn, send 176 the control signal 41 to the sensor units 15, 16, actuators, truck 5, and/or vehicle sub-unit 7. This may include passing the control signal 41 via the first and/or second communication module 51, 59. In other examples, the control signal 41 may be transmitted by alternative communication paths. For example, the vehicle 3 may have other transceivers on board that can receive the control signal 41 via a cellular network or other RF networks.

[0131] Although the above example has been described with reference to the server 31 performing steps of determining 170 the control signals 41 and sending 172 the control signals 41, it is to be appreciated that some or all of these steps may be performed at other devices such as the data collection device 11, mobile communication device 66, or a computer in communication with the system 1 (such as a computer operated at the organisation's operations and control centre).

[0132] Advantages

[0133] The data collection device 11 may collect information from sensor units 15, 16 without prior pairing of the components (such as master and slave). This can be advantageous in that the sensor units 15, 16 may be from a variety of manufacturers without having the data collection device 11 limited to use with particular proprietary components or standards. This can simplify integration into fleets that may have a mix of trailers and sensor units from different manufacturers. This increases brand interoperability and in some examples, the data collection device 11 can be updated or adapted to new or additional communication protocols or specifications as new sensor units come to market.

[0134] Examples of the system 1 can also identify unexpected sensor units 15, 16 which can be useful to detect errors and omissions when operators connect particular truck 5 and trailer 10 combinations. This can reduce the instances of misreporting, underreporting, or even fraudulent reporting.

[0135] The disclosed system 1 and methods 100, 200 may also reduce the burden of manual reporting, such as ease of data entry and selection of sensor units and trailers. The notifications 33 and recommendations 37 can assist an operator to easily select devices and components in the vicinity of the truck 5. In further examples, the system and method enable automatic identification of sensor units and trailers.

[0136] The system may also improve functionality whereby control signals 41 cause elements of the system to behave more efficiently and/or accurately.

[0137] Variations

[0138] An example ofa specific implementation

[0139] Fig. 7 illustrates a specific example implementation of a system 81 to monitor vehicles 3. The system 81 includes many features of the above mentioned system and like features have been provided with corresponding reference numerals. The system 81 also includes data flow from the server 31 with three other entities, namely:

- Platform administrator 83;

- Tracking application 84; and

- System displaying vehicle-based weight monitoring 85.

[0140] The platform administrator 83 may have a computer, computer terminal, or other node, that enables wide access to data and control of the system 81. For example, the administrator may have access to vehicle data, the corresponding sensor data, as well as notifications 33, view error messages, etc. The platform administrator 83 may also have authority to authorise control signals 41. The administrator may also have authority to reset systems, configure sensors and other equipment in the system 81.

[0141] The tracking application 84 maybe implemented on a computer, terminal, node, portable communication device, etc. This tracking application may be used by an organisation, such as a business, regulatory authority, research organisations, etc. to view data in the system 81. This can be useful for tracking vehicles 3 as a fleet, or in other examples, tracking volume of traffic and loads for research and monitoring purposes. For example, a university researcher may want to obtain data on the number of vehicles passing over a bridge or a section of road, and have weight (as well as other data) of such vehicles. In further examples and applications, the data anonymization may be applied to the sensor and vehicle data to protect personal or commercial information.

[0142] The system displaying vehicle-based weight monitoring 85 may include a user interface accessible to the driver, mechanic, warehouse staff, or other operator associated with vehicle 3. This can output sensor data and the implications of the data to enable the operator to identify errors (such as configuration errors), load data (to enable balanced loading of the vehicle), as well as other configuration data relevant to the vehicle. In some examples the user interface may be integrated into a display or other user interface of the vehicle. In other examples, this visualisation may be presented on a dedicated terminal, or other device. In yet other examples, this visualisation may be displayed on a mobile communication device (such as smartphone or tablet), laptop computer, desktop computer, etc.

[0143] Variation of system with multiple sensors communicating with the server

[0144] Fig. 9 illustrates another variation of the system 301. In this variation, each of the sensor units 315, 316 may functionally perform steps of the data collection device 11 described above. In some examples, this may include combining the modules of the sensor unit with those of the data collection device 11. In other examples, the sensor units 315, 316 are equipped with communications modules that enable communication with cellular networks 60. Thus the sensors units may provide signals 13 to the server 31, whereby the server 31 then perform processing steps (such as those methods described above, including those steps performed by the data collection device 11 and the server 31).

[0145] Thus in one variation of the method 200 of Fig. 5, the server 31 receives 251 sensor data 23, 27 (which can include the corresponding signals 13 to determine the sensor data) from the sensor units 315, 316. In a further variation, the server 31 may send control signals 41 to the sensor units 315, 316 without going through a separate data collection device 11.

[0146] In some examples, the sensor units 315, 316 are in communication with one or more other sensor units in the vicinity to form a mesh network. In further examples, this mesh network facilitates identification of sensor units 315. 316 that are following one another in a common vehicle 3.

[0147] Variation of operatingmode without a trailer

[0148] Although many of the above examples relate to the system 1 being used when the vehicle 3 includes a truck 3 towing a trailer 10, it is to be appreciated that the system may be operational to send sensor data to the server 31 when the vehicle does not have a trailer (i.e. absence of vehicle sub-units). In some examples, the system 1 may determine an absence of signals 13 (or absence of anticipated signals 13 from selected sensor units 15) to indicate that the truck 5 is not towing a trailer 10 and this could be relevant information for record keeping and/or processing at the server 31. This determination may be made at the data collection device 11 and/or server 31. In addition, sensor units 15 on the truck itself may also continue sending relevant data, such as weight data which can be important for rigid trucks that can carry a load without a trailer 10.

[0149] Variation on automated determination of configurationof vehicle and operator

[0150] In some examples, the described system enables high automation whereby minimal or no user selection 17 is required to determine how the vehicle 3 is configured. As noted above, in some examples, the system 1 can automatically determine if the vehicle 3 is operating as a truck 3 without a trailer 10. In other examples, this can automatically determine the vehicle sub-unit 7, such as trailers 10, that are attached and the order they are configured in the vehicle.

[0151] In yet other examples, the system 1 can automatically determine a driver/operator 6 and vehicle 3 combination. In some examples, the data collection device 11 is (or functionally is in part) a mobile communication device 66 of the operator 6 who may have access to a plurality of vehicles in a fleet. Instead of manually entering details and/or pairing the mobile communication device 66 with the sensors or other components of the vehicle 3, the operator may be able to simply drive the vehicle. With use, the system may determine that the mobile communication device 66 of that specific operator 6 is travelling in the same, or similar pattern (or close proximity) to the sensor units 15, 16 and/or other components of that particular vehicle. The system 1, and in practical examples the server 31, can then associate that operator 6, the mobile communication device 66, and the vehicle 3 as being operated together and record that fact, and other data as appropriate. This may be useful in supplementing, or entering, data for a driver's log book, timesheet, etc.

[0152] In yet other examples, the system 1 may be useful in determining when a sensor unit 15 has failed by absence of receiving a signal 13. In yet a further examples, the system 1 may also determine when a sensor unit 15 has been replaced by another sensor unit 15, and update the selection 17 accordingly. For example, the system 1 may identify that an original selected unit that should be there is no longer online or sending signals 13, but has detected signals from an additional sensor unit 16 that is outputting signals that would be expected of the original selected sensor unit. Furthermore, the system 1 may determine that the additional sensor unit 16 is in proximity to the vehicle 3 and following the vehicle 3. This information may be used to determine, with confidence, that the additional sensor unit 16 is a replacement sensor and the system may then record (or recommend) that the additional sensor unit 16 should replace the original selected sensor unit 15 in the records.

[0153] Processing device

[0154] Fig. 10 illustrates an example of a processing device 57, 91. The processing device may be in the form of a computer. The processing device 91 may be used at the data collection device 11, the mobile communication device 66, and/or the server 9. A processing device may also be used with one or more devices associated with the organisation 88. The processing device 91 includes a processor 93, a memory 94 and an interface device 95 that communicate with each other via a bus 96. The memory 94 stores instructions 97 and data 98 for implementing the method 100, 200described above, and the processor 93 performs the instructions from the memory 98 to implement the methods 100, 200. The interface device 95 facilitates communication with the communications network 18 and, in some examples, with the user interface and other peripherals. It should be noted that although the processing device may be independent network elements, server 31 may also be part of another network element. Further, functions performed by the processing device 91 may be distributed between multiple network elements.

[0155] It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the above-described embodiments, without departing from the broad general scope of the present disclosure. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

CLAIMS:

1. A method (100) of monitoring a vehicle (3) comprising a truck (5) and at least one connected vehicle sub-unit (7), the method comprising:

- receiving (110) a selection (17) to associate the truck (5) with one or more selected sensor units (15), wherein the selected sensor units (15) are physically associated with respective vehicle sub-unit (7) connected to the truck (5);

- periodically or continuously receiving (120), by a data collection device (11) associated with the vehicle (3), signals (13) transmitted by one or more sensor units (15, 16) in a vicinity of the truck (5),

- determining (130) from the signals (13):

- a first set (21) of sensor data (23) associated with the one or more selected sensor units (15) and respective vehicle sub-unit (7); and

- a second set (25) of sensor data (27) associated with, if any, one or more additional sensor units (16) in the vicinity of the truck (5) that excludes the first set (21) of sensor data (23);

- storing (140) the first set (21) of sensor data (23) with associated time information (29); and

- sending (150) the first set (21) of sensor data (23) to a server (31).

2. A method (100) according to claim 1 further comprising:

- storing (142) the second set (25) of sensor data (27) with associated time information (32);

- identifying (160) whether one or more additional sensor units (16) are following the truck (5) based on the second set (25) of sensor data (27); and

- responsive to identifying (160) one or more additional sensor units (16) following the truck (5), sending (162) a notification (33) to indicate the one or more additional sensor unit (16) and/or an additional vehicle sub-unit (8).

3. A method (100) according to claim 2, wherein the step of identifying (160) whether one or more additional sensor units (16) is following the truck (5) is further based on additional contextual conditions including one or more of:

- movement of the truck (5);

- distance between the additional sensor unit (16) and the data collection device (11) or truck (5);

- signal strength of received signals (13) associated with the additional sensor unit (16);

- identity of the additional sensor unit (160) and/or respective additional vehicle sub unit (8);

- historical or trend information; and

4. A method (100) according to either claim 2 or 3 wherein the notification (33) includes a request (35), recommendation (37), or control signal to include the one or more additional sensor units (16) to the selection (17) to associate the additional sensor unit (16), and/or additional vehicle sub-unit (8), to the truck (5).

5. A method (100) according to any one of claims 2 to 4, further comprising:

- sending (152) the second set (25) of sensor data (27) to the server (31),

wherein the step of identifying (160) whether one or more additional sensor units (16) is following the truck (5) is performed by the server (31).

6. A method (100) according to any one of claims 2 to 4, wherein the step of identifying (160) whether one or more additional sensor units (16) is following the truck (5) is performed by the data collection device (11).

7. A method (100) according to any one of the preceding claims wherein the step of sending (150) the first set (21) of sensor data (23) to a server (31) comprises:

- sending via an embedded second communication module (34) of the data collection device (11) to the server (1); or

- sending from the data collection device (11), via a mobile communication device (66), to the server (31).

8 A method (100) according to any one of the proceeding claims further comprising:

- determining (170), based on the received first set (21) of sensor data (23) and/or second set (25) of sensor data (27), one or more control signals (41); and

- sending (172) one or more control signals (41) to the data collection device (11), truck (5), vehicle sub-unit (7), one or more sensor units (15, 16), and/or one or more actuators associated with the vehicle (3).

9. A method (100) according to claim 8, wherein the one or more control signals (41) include one or more of:

- a request to send further sensor data;

- power settings and/or actuation of a sensor unit (15);

- pairing of additional sensor units (16); and

- mesh/network settings for the sensor units (15).

10. A data collection device (11) to monitor a vehicle (3) having a truck (5) and at least one connected sub-unit (7), wherein the data collection device (11) comprises:

- a first communication module (51) to periodically, or continuously, receive (120) signals (13) transmitted by one or more sensor units (15, 16) in the vicinity of the truck (5);

- a memory (53) to store:

- selection data (55) indicative of a selection (17) of one or more sensor units (15) associated with the vehicle (3), wherein the selected sensor units (15) are physically associated with respective vehicle sub-unit(s) (7) connected to the truck (5); and

- sensor data (23, 27);

- a processing device (57) configured to:

- determine (130) from the signals (13) received at the first communication module (51):

(i) a first set (21) of sensor data (23) associated with one or more selected sensor units (15) and respective vehicle sub-unit (7); and

(ii) a second set (25) of sensor data (27) associated with one or more sensor units (16) in the vicinity of the truck (5) that exclude the first set (21) of sensor data (23);

- store (140), in the memory (53), at least the first set (21) of sensor data (23) with associated time information (29); and

- send (150) the first set (21) of sensor data (23) to a server (31).

11. A data collection device (11) according to claim 10, wherein the processing device (57) is further configured to:

- store (142), in the memory (53), the second set (25) of sensor data (27) with associated time information (32);

- identify (160) whether one or more additional sensor units (16) is following the truck (5) based on the second set (25) of sensor data (27); and

- responsive to identifying (160) one or more additional sensor units (16) following the truck (5), send (162) a notification (33) to indicate the one or more additional sensor unit (16) and/or an additional vehicle sub-unit (8).

12. A data collection device (11) according to claim 11, wherein the notification (33) is sent to a user interface (63) associated with the data collection device (11), a portable communication device (65) associated with a user (67) of the vehicle (3), a processing device (69) of the vehicle (3), and/or the server (31).

13. A data collection device (11) according to claim 10, wherein the processing device (57) is further configured to:

- send (152) the second set (25) of sensor data (27) to the server (31) to enable the server to identify (160) whether one or more additional sensor units (16) is following the truck (5) based on the second set (25) of sensor data (27); and

- receive (163) from the server (31), in response to identification of one or more additional sensor units (16) following the truck (5), a notification (33) to indicate the one or more additional sensor unit (160) and/or additional vehicle sub-unit (8).

14. A data collection device (11) according to any one of claims 10 to 12 further comprising:

- a second communication module (59) configured to communicate with a communications network (61), wherein the first set (21) of sensor data (23) is transmitted to the server (31) via the second communication module (59) and communications network (61).

15. A data collection device (11) according to any one of claims 10 to 14, wherein the processing device (57) is further configured to:

- receive (174) one or more control signals (41) from the server (31), wherein the control signals (41) are determined by the server (31) based on the first set (21) and/or second set (25) of sensor data (23, 27); and

- send (176), via the first communication module (51) or other communication module (71), the one or more control signals (41) to the truck (5), vehicle sub-unit (7), one or more sensor units (15, 16), and/or one or more actuators associated with the vehicle (3).

16. A system (1) of monitoring a vehicle (3) having a truck (5) and at least one connected vehicle sub-unit (7), the system (1) comprising:

- at least one data collection device (11) configured to:

- receive (120) signals (13) transmitted by one or more sensor units (15, 16) in the vicinity of the truck (5); and

- send (150), to a server (31), sensor data (23, 27) based on the signals (13);

- the server (31) configured to:

- receive (112) a selection (17) of one or more selected sensor units (15) that are associated with the vehicle (3);

- receive (151) sensor data (23, 27); and

- identify (160) based on the sensor data (23, 27) whether one or more additional sensor units (16), that is not one of the selected sensor units (1), is following the truck (5).

17. A system (1) according to claim 16, wherein the server (31) is further configured to:

- determine (170) based on at least the sensor data (23, 27), one or more control signals (41); and

- send (172) one or more control signals (41) to the data collection device (11), truck (5), vehicle sub-unit (7), one or more sensor units (15, 16), and/or one or more actuators associated with the vehicle (3).

18. A method (200) of monitoring one or more vehicles (3) at a server (31), wherein each vehicle (3) comprises a truck (5) and at least one connected vehicle sub-unit (7), the method (200) comprising:

- receiving (251) sensor data (23, 27) from a data collection device (11) associated with the vehicle (3), wherein the sensor data (23, 27) is based on signals (13) transmitted by one or more sensor units (15, 16) in the vicinity of the truck (5) and received by the data collection device (11);

- identifying (260), based on the sensor data (23, 27), specific sensor units (15) that are following the truck (5); and

- identifying (261) one or more vehicle-sub units (7) that are connected to the truck (5) based on the identified specific sensor units (15) following the truck (5).

19. A method (200) of monitoring one or more vehicles (3) at a server (31), wherein each vehicle (3) comprises a truck (5) and at least one connected vehicle sub-unit (7), the method (200) comprising:

- receiving (251) sensor data (23, 27) based on signals (13) transmitted by one or more sensor units (15, 16) in the vicinity of the truck (5);

20. A method (200) according to either claim 18 or 19 further comprising:

- storing (265) in a data store (73), vehicle data (75) indicative of:

- the identified specific sensor units (15) following the truck (5);

- the identified one or more vehicle sub-units (7) connected to the truck (5); and

- sensor data (23, 27) associated with the vehicle (3).

21. A method (200) according to any one of claims 18 to 20 further comprising:

- determining (270), based on at least the sensor data (23, 27), one or more control signals (41); and

- sending (272) one or more control signals (41) to the data collection device (11), truck (5), vehicle sub-unit (7), one or more sensor units (15, 16), and/or one or more actuators associated with the vehicle (3).