Methods, systems, and devices for monitoring vehicles
The telematics system addresses inefficiencies in monitoring trucks with multiple trailers by using wireless sensor units and a data acquisition device to automatically identify and associate sensors, ensuring accurate and real-time weight and identification data transmission.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- V DAQ PTY LTD
- Filing Date
- 2024-02-27
- Publication Date
- 2026-04-10
AI Technical Summary
Existing solutions for monitoring and recording the weight and identification of trucks with multiple trailers are inefficient, requiring manual input and are prone to errors due to incompatibilities between proprietary sensor systems, leading to unreliable data for compliance and business needs.
A telematics system that includes sensor units transmitting data wirelessly to a data acquisition device, which processes and transmits data to a server, automatically identifying and associating sensor units with vehicles, and enabling real-time monitoring and control of vehicle subunits, using a broadcast signal protocol like Bluetooth Low Energy (BLE) to facilitate compatibility across different manufacturers.
Enables accurate, real-time monitoring and recording of vehicle weights and identities, improving compliance and operational efficiency by reducing manual input and ensuring data consistency across different trailer configurations.
Smart Images

Figure 2026510712000001_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a telematics method, system, and device for monitoring vehicles. This includes the collection and transmission of data associated with vehicles such as trucks with trailers or tractor-trailers for the purpose of record keeping, regulatory reporting, and / or fleet management.
Background Art
[0002] In order to have access to information regarding the combination of heavy vehicles or the weight of trucks, there are not only business reasons but also compliance requirements mandated by the government. A combination of heavy vehicles is a truck or tractor that pulls one or more trailers. Record-keeping information regarding the weight of a combination of heavy vehicles typically includes identification information, the order of trailers connected to the tractor or truck, the individual weights at the axles or axle groups, and the total weight of the combination. In the context of such a road system, weight and mass are related concepts, and references to weight should be interpreted to include mass.
[0003] Trucks and tractors that pull multiple trailers are becoming increasingly popular worldwide due to improvements in safety and compliance technologies and the increasing willingness of governments to permit the use of these larger, heavier, and more complex combinations. As an example, combinations of heavy vehicles in Australia can be complicated due to a combination of factors including long vehicle lengths, heavy overall weights, and a significant number of trailers and associated axle groups. Additionally, the frequency with which trailers can be exchanged or swapped between different trucks or tractors is very frequent, which makes it difficult to keep records.
[0004] Existing solutions for record-keeping include manual, paper-based records. This may involve the driver physically walking around the combination to record identification information, trailer order, and weight via estimation, which can be recorded using on-board weight sensors via analog dials or digital displays on the tow vehicle, truck, or trailer, or using ground weighing scales or alternative methods. This does not provide accurate periodic measurements during travel, and it is impractical for the driver to manually record weight at regular intervals.
[0005] Several digital solutions exist in which a proprietary weight sensor is associated with a group of axles (acting as slave sensors) that transmit data to a proprietary central unit (e.g., a master) in the towing vehicle or truck. Data from these sensors can be presented as information on a graphical display in the driver's cab of the towing vehicle or truck for recording by the driver or other operator. However, these existing solutions require user input, such as correct sensor connection (or pairing). Furthermore, problems arise if the trailer uses a different, proprietary sensor system that is incompatible with the master's proprietary central unit.
[0006] These solutions present challenges in addressing the complexities of trailer changes, as drivers are unable to properly utilize the system, resulting in low-reliability and inconsistent combined information that cannot be adequately used to meet business and compliance requirements.
[0007] Throughout this specification, the word “comprise” or its variations such as “comprises” or “comprising” shall be understood to imply that it includes the element, integer, or step, or group of elements, integers, or steps, described herein, but not to exclude any other element, integer, or step, or group of elements, integers, or steps.
[0008] Nothing discussed herein, including documents, acts, materials, apparatus, articles, etc., shall be deemed to acknowledge that any or all of these matters formed part of the basis of the prior art or were common knowledge in the art relating to this disclosure, as they existed prior to the priority date of each claim of this application. [Overview of the Initiative]
[0009] A method for monitoring a vehicle including a truck and at least one connected vehicle subunit is disclosed, comprising: receiving a selection to associate the truck with one or more selected sensor units, the selected sensor units being physically associated with each vehicle subunit connected to the truck; and periodically or continuously receiving signals transmitted by one or more sensor units in the vicinity of the truck by a data acquisition device associated with the vehicle. The method further includes determining from the signals a first set of sensor data associated with one or more selected sensor units and each vehicle subunit, and a second set of sensor data associated with one or more additional sensor units in the vicinity of the truck, excluding the first set of sensor data, if present. The method also includes storing the first set of sensor data together with associated time information and transmitting the first set of sensor data to a server.
[0010] In some examples, the method further includes storing a second set of sensor data along 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 sending a notification indicating one or more additional sensor units and / or additional vehicle subunits in response to identifying one or more additional sensor units that are following the truck.
[0011] In a further example of the method, the step of determining whether one or more additional sensor units are tracking a track is further based on additional circumstance conditions, including one or more of the following: - Truck movement, - Distance between additional sensor units and data acquisition devices or tracks, - Signal strength of the received signal associated with the additional sensor unit, - Identification information for additional sensor units and / or each additional vehicle subunit, - Historical or trend information, and - Third-party input such as third-party software (for job management or compliance) or data entry systems.
[0012] In some examples of this method, the notification includes a request, recommendation, or control signal to include one or more additional sensor units in the selection in order to associate additional sensor units and / or additional vehicle subunits with the truck.
[0013] In some examples, the method further includes sending a second set of sensor data to a server, where the server performs the step of identifying whether one or more additional sensor units are tracking the track.
[0014] In some examples of the method, the step of identifying whether one or more additional sensor units are tracking the track is performed by the data acquisition device.
[0015] In some examples of the method, the step of sending a first set of sensor data to a server includes sending it to the server via a second communication module incorporated in the data acquisition device, or sending it to the server from the data acquisition device via a mobile communication device.
[0016] In some examples, the method further includes determining one or more control signals based on a first set and / or a second set of received sensor data, and transmitting one or more control signals to a data acquisition device, a truck, a vehicle subunit, one or more sensor units, and / or one or more actuators associated with the vehicle.
[0017] In a further example of this method, one or more control signals include one or more of the following: - Request to send further sensor data, - Power setting and / or operation of the sensor unit, - Pairing of additional sensor units, and - Mesh / network settings for the sensor unit.
[0018] In some examples, the method further includes having a data acquisition device periodically or continuously receive network signals transmitted by one or more network devices in the vicinity of the vehicle. The method also includes determining from the network signals a first class of network signals associated with each known or authorized vehicle subunit connected to the truck, and a second class of network signals associated with an unknown or unauthorized additional vehicle subunit. The method may also include determining the configuration of the vehicle's vehicle subunits and / or additional vehicle subunits based on signal timing, signal strength, or network connectivity characteristics.
[0019] Also disclosed is a data acquisition device for monitoring a truck and a vehicle having at least one connected subunit, comprising 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 located near the truck. The memory is configured to store selection data and sensor data, indicating the selection of one or more sensor units associated with the truck, wherein the selected sensor units are physically associated with each vehicle subunit connected to the truck. The processing device is configured to determine from the signals received by the first communication module (i) a first set of sensor data associated with one or more selected sensor units and each vehicle subunit, and (ii) a second set of sensor data associated with one or more sensor units located near the truck, excluding the first set of sensor data. The processing device is further configured to store at least the first set of sensor data in memory along with associated time information, and to transmit the first set of sensor data to a server.
[0020] In some examples of data acquisition devices, the processing device is further configured to store a second set of sensor data in memory along with associated time information, to identify whether one or more additional sensor units are following the truck based on the second set of sensor data, and, in response to identifying one or more additional sensor units that are following the truck, to send a notification indicating one or more additional sensor units and / or additional vehicle subunits.
[0021] In some examples of data collection devices, notifications are sent to a user interface associated with the data collection device, a portable communication device associated with the vehicle user, a processing device in the vehicle, and / or a server.
[0022] In some examples of the data collection device, the processing device enables the server to identify whether one or more additional sensor units are tracking a track based on a second set of sensor data by sending the second set of sensor data to the server and, in response to identifying one or more additional sensor units tracking the track, receiving from the server a notification indicating the one or more additional sensor units and / or additional vehicle subunits, and is further configured to perform the operations.
[0023] In some examples, the data collection device further comprises a second communication module configured to communicate with a communication network, and the first set of sensor data is transmitted to the server via the second communication module and the communication network.
[0024] In some examples of the data collection device, the processing device is further configured to receive one or more control signals from the server, the control signals being determined by the server based on the first set of sensor data and / or the second set of sensor data, and to transmit the one or more control signals to a track, a vehicle subunit, one or more sensor units, and / or one or more actuators associated with the vehicle via the first communication module or another communication module.
[0025] Also disclosed is a system for monitoring a vehicle having a truck and at least one connected vehicle sub-unit, 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 to transmit sensor data to the server based on the signals. The server is configured to receive a selection of one or more selected sensor units associated with the vehicle, receive the sensor data, and identify based on the sensor data whether one or more additional sensor units other than one of the selected sensor units are tracking the truck.
[0026] In some examples of the system, the server is further configured to determine one or more control signals based at least on the sensor data and to transmit the one or more control signals to the data collection device, the truck, the vehicle sub-unit, the one or more sensor units, and / or one or more actuators associated with the vehicle.
[0027] Also disclosed is a method of monitoring one or more vehicles in a server, each vehicle including a truck and at least one connected vehicle sub-unit, the method including receiving sensor data from a data collection device associated with the vehicle, the sensor data being based on signals transmitted by one or more sensor units in the vicinity of the truck and received by the data collection device, identifying a particular sensor unit tracking the truck based on the sensor data, and identifying one or more vehicle sub-units connected to the truck based on the identified particular sensor unit tracking the truck.
[0028] Also disclosed is a method for monitoring one or more vehicles on a server, each vehicle comprising a truck and at least one connected vehicle subunit, the method comprising: receiving sensor data based on signals transmitted by one or more sensor units located near the truck; identifying a specific sensor unit tracking the truck based on the sensor data; and identifying one or more vehicle subunits connected to the truck based on the identified specific sensor unit tracking the truck.
[0029] In some examples, the method further includes determining the configuration of vehicle subunits and / or sensors within the vehicle based on sensor data and / or signals.
[0030] In some examples, the method further includes storing in the datastore identified specific sensor units that are tracking the truck, one or more identified vehicle subunits connected to the truck, and vehicle data indicating sensor data associated with the vehicle.
[0031] In some examples, the method further includes determining one or more control signals based on at least sensor data, and transmitting one or more control signals to a data acquisition device, a truck, a vehicle subunit, one or more sensor units, and / or one or more actuators associated with the vehicle. [Brief explanation of the drawing]
[0032] Examples of this disclosure are described below.
[0033] [Figure 1] This is a schematic diagram of a vehicle monitoring system. [Figure 2] Figure 1 is a schematic diagram of the data acquisition devices used in the system shown. [Figure 3] This is a flowchart illustrating a method for monitoring a vehicle, including receiving sensor data stored on a server. [Figure 4] This is a flowchart illustrating how to identify additional sensor units tracking a vehicle. [Figure 5] This is a flowchart illustrating a method for automatically identifying sensor units and vehicle subunits (such as trailers) associated with a vehicle. [Figure 6] This is a flowchart illustrating the method for generating the control signal that will be transmitted to vehicle 3. [Figure 7] This is a schematic flowchart of a specific exemplary embodiment of the system. [Figure 8] This provides an example of a vehicle that includes a combination of trucks and trailers. [Figure 9] This section illustrates a modified version of a system where each sensor unit also functions as a data acquisition device unit. [Figure 10] This section illustrates a modified system in which each sensor unit communicates directly with the data acquisition device. [Figure 11] This example illustrates a modified system in which a sensor unit communicates indirectly with a data acquisition device via a mobile communication device. [Figure 12] This example illustrates a modified system having multiple sensor units associated with the first and third trailers, but without a sensor associated with the second trailer. [Figure 13] This illustrates a modified example of a system having data acquisition devices for each of the vehicle's subunits. [Figure 14] This example illustrates a modified system having a mesh network that enables communication between a sensor unit and a data acquisition device. [Figure 15] This document illustrates variations of a system that includes a local area network and a combination of multiple data collection devices. [Figure 16] This illustrates a modified version of a system in which a data collection device communicates with a server. [Figure 17] This illustrates an example of a processing device. [Modes for carrying out the invention]
[0034] System Overview 1 Figure 1 illustrates a schematic diagram of a system 1 that monitors a vehicle 3 having a track 5 and at least one connected vehicle subunit 7.
[0035] One or more sensor units 15, 16 are associated with their respective vehicle subunits 7 (examples of vehicle subunits 7 may be a trailer 10 or axle group 12, or part of a truck 5). Signals 13 are transmitted from the sensor units 15, 16, and the signals include measured values or other data. These measured values or other data may represent one or more of the following: weight, force, acceleration, speed, temperature, time, wear condition, tire pressure, identification data, location, cumulative operating time, service interval, status, error condition, and notifications. In some examples, the sensor units 15, 16 broadcast the signals 13 wirelessly (using a protocol such as Bluetooth).
[0036] System 1 includes at least one data acquisition device 11 associated with each vehicle 3, and in some examples, the data acquisition device 11 is located on a track 5. The data acquisition device 11 is configured to periodically or continuously receive signals 13 transmitted by one or more sensor units 15, 16 located near the track 5. The data acquisition 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 may include at least some of the processing steps of a method 100 for monitoring the vehicles 3, which will be discussed in more detail below. The data acquisition device 11 is also configured to transmit the sensor data 23, 27 to a server 31 of System 1.
[0037] Server 31 includes processing devices for carrying out the steps of methods 100 and 200. Server 31 may have an associated data store 73 for storing sensor data and other data received from the data acquisition device 11. The data store 73 may store such data for regulatory and compliance purposes as well as for business intelligence and fleet management purposes. Server 31 can also be used to identify the sensor unit 16 tracking track 5 and to transmit control signals. It should be understood that Server 9 may be a cloud-based server.
[0038] System 1 can be used in the following ways: i. Monitor the vehicle by collecting sensor data. ii. Identify the sensor unit and each vehicle subunit. iii. To control sensors, actuators, and other vehicle components.
[0039] These methods 100 and 200 are described under separate headings. Here, the components of System 1 are described in detail.
[0040] Sensor unit 15 / 16 Sensor units 15 and 16 are configured to include at least one sensor for receiving information associated with the vehicle subunit 7, nearby elements, and / or the surrounding environment. In heavy vehicle applications, important measurements include the weight of the vehicle 3, including the overall weight of the vehicle, the weight corresponding to a specific axle or group of axles 12, and / or the weight in the trailer 10. Thus, in some examples, the sensor in sensor unit 15 receives measurements indicating the weight (or force) applied to the vehicle subunit 7.
[0041] An example of a sensor unit 7 that provides weight information is the wireless axle load sensor GNOM DDES7. In some examples, the sensor unit 15 includes strain gauges for measuring deformation or displacement, which can be used to determine the force applied to a spring or structure within the vehicle subunit 7. In other examples, the axle load may be measured by the displacement of a component, such as a leaf spring, relative to another component of the vehicle 3. In yet another example where air suspension is used, a measurement of air pressure indicates the weight or load on the axle.
[0042] In some examples, the weight sensor is configured to output the current mass. In some examples, this may be the mass relative to a force at a particular axle. In other examples, the sensor units may communicate with each other to output the overall mass of the vehicle (or the mass of a subunit). Sensor unit 7 may be configured to determine the actual mass of the vehicle based on the sensed data and transmit this mass data as an output.
[0043] Other examples of sensor unit 7 may include, but are not limited to, other sensor types. • Temperature sensors. These may include ambient temperature sensors, cargo area temperature sensors, and / or temperature sensors for specified components of the vehicle or trailer. These may include brake temperature sensors, axle temperature sensors, and tire temperature sensors. • Humidity sensor. This may include measuring the ambient temperature and / or the temperature of the vehicle's cargo area. In some examples, the humidity sensor may measure the humidity within vehicle components such as the pneumatic system and tire components. • Pressure sensors. This may include pressure sensors related to the functional components of the vehicle, such as tire pressure, pneumatic system pressure, and hydraulic system pressure. This subset may include pressure related to brakes and / or air suspension. In some examples, pressure sensors may include ambient air pressure and / or air pressure in the vehicle's cargo area. • Strain sensors or other force sensors, or displacement sensors – in some cases, sensors that measure force on one or more components of a vehicle can be used to monitor the structural integrity of the vehicle. • Network Data Sensor - This includes local network data, which can include the vehicle's local network. In some examples, this can include EBS (Electronic Brake System) data. In other examples, this can include the vehicle's CAN (Controller Area Network) bus data. In still other examples, this can include the vehicle's LIN (Local Interconnect Network) data. • Encoders, gyroscopes, and accelerometers – This includes providing the position and / or orientation of one or more components of a vehicle. In some examples, this may include the relative position and / or orientation of one component to another, for example, the relative orientation between a truck and a trailer. In some examples, this may include the level of a vehicle or trailer based on accelerometer data of a stationary (or stabilized) vehicle. In some examples, this may include rotational data based on a gyroscope within the vehicle. • Other sensors on the drivetrain. These may include sensors associated with the driving condition and health of the drivetrain, such as RPM (revolutions per minute), the speed of one or more wheels, and the calculated speed of the vehicle (or vehicle subunit). • Emission sensors – These may include sensors configured to determine pollutants or air composition inside and around the vehicle. These include carbon monoxide, carbon dioxide, and other vehicle exhaust gases. • Energy and fuel sensors. These may include sensors that detect the amount of fuel in a fuel tank, such as gasoline or diesel. In another example, this may include sensors associated with the battery charge state. In yet another example, this may include sensors associated with data on the amount of hydrogen fuel in a hydrogen fuel storage unit on the vehicle.
[0044] In some examples, the sensor units 15 / 16 communicate wirelessly with data acquisition devices 11 and / or other devices such as other sensor units 15 / 16. This may include radio frequency wireless transmission. In some examples, the sensor unit 15 has or is associated with a communication module to enable wireless transmission of a signal 13. This may include a signal 13 transmitted according to the Bluetooth protocol. In some examples, this includes Bluetooth Low Energy (BLE). In some examples, this includes a BLE coding PHY that enables extended range signals. In some examples, the signal 13 is broadcast (e.g., advertised) by the sensor unit, and as a result, at least a portion of the data can be received and understood by other Bluetooth-enabled devices in the vicinity. In particular, these signals 13 can be understood by such devices without specific pairing with another Bluetooth device in a master-slave relationship. This broadcast signal can be advantageous by enabling easy reception of data without requiring a pairing operation that may require the attention and effort of a human operator. It also enables easy reception of data about vehicle combinations, even if truck 5 has never been paired with a particular trailer 10. Broadcast signals can also avoid the problem of proprietary sensor units requiring pairing with their own controller and / or master. This may allow the use of sensor units 15 from multiple manufacturers within System 1.
[0045] In some examples, System 1 is configured to receive and process sensor messages from broadcast signals known to be associated with sensor units 15, 16 associated with a vehicle or vehicle subunit. This may include a data acquisition device 11 configured to process broadcast signals from sensor units 15, 16 that it recognizes as being associated with a vehicle, vehicle subunit, or additional vehicle subunit, and to reject other broadcast signals from other devices. In other words, the system can screen the received data.
[0046] In some examples, the system may include a whitelist of sensor unit types or sensor signal types that the system recognizes for processing. This can be done in one or more of the data acquisition devices, mobile communication devices, and / or servers. In further examples, this may include specific sensor units registered by a user, fleet operator, regulatory authority, or other entity.
[0047] In some examples, a server, mobile communication device, or data acquisition device may dynamically select specific sensor units and associated sensor signals to prioritize processing. In further examples, this may include these system elements actively requesting specific sensors to transmit collected sensor data.
[0048] In some examples, the broadcast signal 13 includes one or more of the following: - Sensor identifier of sensor unit 15, - A vehicle subunit identifier that enables the association of the sensor unit 15 with the vehicle subunit 7 to which it is physically associated. - Organization identifiers that enable association with organizations, entities, operators, etc. - Measurement data from sensors showing measured values such as weight, force, and acceleration. -Time information, -Location information.
[0049] Please understand that other wireless transmission protocols besides BLE, including ZigBee, Wi-Fi, and LTE, may be used by the sensor unit 15.
[0050] Sensor units 15 / 16 may include an independent power supply. In other examples, sensor units 15 / 16 may be powered by vehicle-supplied power such as 12V, 24V, or 48V from track 5. Further examples may include a combination of battery and vehicle-supplied power.
[0051] In some examples, some of the sensor units 15 / 16 may communicate via wired communication to transmit signals 13. For example, an axle group may have a subset of sensor units 15 / 16 that have wireless communication modules. The remaining sensor units may transmit signals 13 to sensor unit 15 via wires, in which case the wireless communication modules retransmit the signals 13 to the data acquisition device 11.
[0052] It should be understood that sensor units 15 / 16 may receive other information. In some examples, sensor units 15 / 16 also include a satellite navigation module for receiving signals from one or more satellites 28. The satellite navigation module may receive signals from GPS (Global Positioning System), GLONASS (Global Positioning Satellite System), or other Global Navigation Satellite Systems (GNSS). This may also include receiving auxiliary signals from differential GPS systems, etc., and augmentation signals from WASS (Wide Area Augmentation System), etc. The satellite navigation module may also utilize auxiliary GPS. Receiving location information from a satellite navigation module may be advantageous in ensuring the quality and integrity of sensor data (for example, sensor data from a single vehicle may be associated with the time and location of data from each sensor, and all sensors on the vehicle should have matching or nearby locations).
[0053] In some examples, it should be understood that the sensor units 15 / 16 have a communication module (or further communication module) to enable extended communication, such as connection to the network 18 via the cellular network 60. By having cellular communication such as LTE or 5G, this may allow some sensor units 15 / 16 to communicate with the server 31 independently of the distinctly separate data acquisition device 11. This may be useful as an alternative or supplementary means of communication to the data acquisition device 11 when the data acquisition device is in an error state. In other examples, if the data acquisition device 11 is the operator's mobile communication device 66, this alternative means of communication allows the server 31 to receive updated information about the vehicle 3 when the operator is absent.
[0054] 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 passing through the data acquisition device 11. This may be for data integrity and / or security reasons, where the sensor units 15, 16 may belong to a different organization (such as a government, regulatory body, or environmental protection organization) and do not wish to rely on the data acquisition device 11 to pass data, but instead use their own independent means of communication. In such use cases, the data acquisition device 11 may still receive signals 13 from such sensor units 15, 16 to enable proximity detection. In other words, there are multiple data paths that can be used for different purposes.
[0055] Data acquisition device 11 Figure 2 illustrates a schematic example of a data acquisition device 11. The data acquisition device 11 includes a processing device 57 that communicates via a bus 58 to a memory 53, a first communication module 51, and other components such as a second communication module 59 in some examples. The data acquisition device 11 may also have a user interface 63.
[0056] The first communication module 51 periodically or continuously receives signals transmitted by one or more sensor units 15, 16. The first communication module 51 may include an RF receiver or transceiver configured to receive the signal protocols of the sensor units 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-slave type pairing. In other examples, selected sensor units 15 may be paired with a data acquisition device 11.
[0057] The second communication module 59 is configured to communicate information to the server 31 via the network 18. This may include sending sets of sensor data 23, 27 21, 25 to the server 31 for record keeping and / or further processing. This may also include the second communication module 59 receiving control signals 41 from the server 31 via the network 18. In some examples, the second communication module 59 communicates via a cellular network 60 operating on (but not limited to) GPRS, 3G, 4G / LTE, or 5G technologies, which may, upon reception, advantageously enable continuous or near-continuous communication with the server 31 (see line 22 in Figure 2).
[0058] The second communication module 59 may communicate over another network, such as a wireless local area network operation of Wi-Fi technology. In this case, it may communicate over a broader network, such as the Internet. Reliable Wi-Fi networks may be intermittent, and the second communication module 59 may be configured to transmit and receive data at specific times and intervals, such as during breaks and refueling stops, while in a truck depot or warehouse. In some examples, this may include the second communication module 59 communicating with the server 31 via a mobile communication device 66 (as shown in line 24 of Figure 2). It should be understood that the second communication module 59 may include more than one physical communication module, and that functionality may be provided by any (or divided) different means, such as Wi-Fi and cellular.
[0059] In the illustrated example, the second communication module 59 is embedded in the data acquisition module 11. In some examples, the first communication module 51 and the second communication module 59 perform different functions but may be physically implemented by a common communication module. For example, the common communication module may communicate via the Bluetooth protocol to receive signals 13 from the sensor unit 15 and may also communicate with a mobile communication device 66 via Bluetooth (see line 20 in Figure 2). In this case, the cellular network 60 function of the mobile communication device 66 can be used to communicate with the server 31 via the network 18.
[0060] Furthermore, in other examples, sensors 15 and 16 may communicate with a mobile communication device 66 via additional routes. For example, if an operator is located away from the vehicle, they may be able to receive data from sensors 15 and 16 as follows: For example, a route may include transmitting sensor data from sensors 15 and 16 to a data collection device 11 via a first communication module 51 (such as a Bluetooth communication module). The data may then be transmitted from the data collection device 11 via a second communication module 59 (e.g., via cellular data to a cellular network and over the internet). The data may be received by a mobile communication device 60 via a mobile phone, Wi-Fi, or other network means.
[0061] The processing device 57 may be configured to process data and perform at least some of the steps of method 100, which are described in a separate section below.
[0062] Memory 53 may store instructions and data for implementing method 100 carried out by processing device 57. In some examples, the data stored in memory 53 includes sets 21, 25 of sensor data 23, 27 based on received signals 13 from sensor units 15, 16. This storage of data may be useful as a data buffer in the event of intermittent communication with server 31. Furthermore, there may be practical, operational, and regulatory reasons for storing the sensor data 23, 27 in data acquisition device 11. Memory 53 may also store vehicle data, identification data, or other data such as location, time, and weather. In some examples, this includes a non-volatile memory storage device.
[0063] The user interface 63 enables user interaction with the operator 6. This may include outputs that indicate notifications and other data, which may be visual, audible, or tactile outputs. The user interface 63 may also include user inputs that allow the operator 6 to input data such as information about the vehicle, the operator, vehicle operation, connected vehicle subunits 7, etc. In some examples, this may include a selection 17 of one or more sensor units 15 (which may indicate a selection of each vehicle subunit 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 acquisition device 11 may function as the user interface 63. It should be understood that in some alternative forms, the user interface 63 does not communicate directly with the data acquisition device 11. Instead, communication may occur between the user interface 63 and the server 31 to send and receive information to and from the operator 6. In this case, some of this information may be communicated directly or indirectly from the server 31 to the data acquisition device 11.
[0064] In some examples, the data acquisition device 11 may include the sensor unit 5 in a single physical package. For example, the data acquisition device 11 may have an accelerometer and a gyroscope for detecting acceleration, vibration, linear and / or angular motion. Other examples may include the data acquisition device 11 with other sensor units 15, as described herein.
[0065] In some examples, a vehicle may be equipped with multiple data collection devices 11 (as illustrated in Figures 13 and 15). This may include data collection devices located on the truck and one or more vehicle subunits (e.g., one on each trailer). Having multiple data collection devices can provide asset redundancy, security, and improved tracking, for example, when a trailer is intentionally or unintentionally separated from the rest of the vehicle.
[0066] The data collection device 11 may be integrated with the vehicle 3, incorporated into the vehicle 3, or located inside the vehicle 3. For example, the data collection device 11 may be mounted on the dashboard of the vehicle 3, mounted on the windshield, located in the glove compartment, located in the storage area, located under the hood, or located in another compartment. In other examples, the data collection device may be mounted on the exterior of the vehicle, such as on the roof of a truck or on the exterior of the driver's cab. In some examples, the data collection device may be mounted on a trailer (as described in the modifications below). In some examples, the data collection device 11 may be integrated with other electronic and telematics devices in the vehicle, such as entertainment, monitoring and control, and / or navigation systems. Some examples of the data collection device 11 include embedding it in the vehicle 3, but in alternative examples, the data collection device 11 may be incorporated as part of a mobile communication device 66, such as a smartphone or tablet, or in a modified form.
[0067] The data acquisition device 11 may also include a satellite navigation module for receiving signals from one or more satellites 28 to enable the determination of the vehicle's position.
[0068] Mobile communication devices The mobile communication device 66 may be used in several exemplary implementations of 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 because a high percentage of people already carry mobile communication devices.
[0069] In other examples, the mobile communication device 66 may complement or complete a part of System 1. As described 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 sensor data, manipulate the data, and transfer the data for reporting purposes. The mobile communication device 66 may also have a more powerful processing device for processing the data. In other examples, the mobile communication and networking functions of the mobile communication device may be used to transmit and receive data to and from the network 18 and the server 31.
[0070] In some examples, an application is run on the mobile communication device 66 to enable its function as a data collection device or to interface with a part of System 1. This may include secure access to data from the data store 73 of Server 31.
[0071] Server 31 Server 31 includes one or more processing devices for carrying out the steps of Method 100, 200 and has an associated data store 73. Server 31 may be operated by a business organization 88 (such as an operator of a fleet 3 of vehicles), a third-party fleet management entity, a third-party computing service, a government or regulatory body, etc. In some examples, the data store 73 is configured to be accessible by multiple entities, which may be through a secure API. In other examples, an application (including a web application) may be used to access the data. This may include presenting information in a dashboard, and including tools for analyzing the data and creating reports.
[0072] In some cases, the data in datastore 73 may be available for commercial or research purposes. This may include selling or offering subscription services for the data in the datastore.
[0073] Server 31 may perform several functions, including the following: - Record keeping, such as recording vehicle and sensor data for business and commercial purposes, as well as for compliance purposes. -Identification of the use and status of vehicle 3 (including related vehicle subunits such as trailers), combination of trucks and trailers in use, wear monitoring, and processing of data for identification purposes such as maintenance requirements, and - Control of sensors, actuators, or other components of vehicle 3 based on sensor data and problems identified in previous functions.
[0074] Vehicle 3 Figure 8 illustrates a non-limiting example of vehicle 3. The first exemplary vehicle 3 is a combination including a rigid truck 5 having two axle groups 12 and a trailer having two axle groups 12'. In this example, the rigid truck 5 transports and supports the cargo. In some examples, the truck 5 and the trailer are connected via an intermediate coupling.
[0075] A second exemplary vehicle 3' is a combination including a truck 5' (in the form of a towing vehicle) having two axle groups 12. The exemplary towing vehicle 5' includes a fifth wheel for connecting to a first trailer 10' having one axle group 12'. The second trailer 10'' connects to the axle group 12' of the first trailer 10'. The second trailer 10'' also has a single axle group 12''.
[0076] The third exemplary vehicle 3'' is a variation of the second exemplary vehicle 3'' with a graphical representation of the weight distribution of vehicle 3'' to axle groups 12, 12', and 12''. The total weight of vehicle 3'' is 62.5 tons. This is distributed as 6 tons in the first axle group 12 of the towing vehicle 5' and 16.5 tons in the second axle group 12 of the towing vehicle 5'. It will be understood that a portion of the 16.5 tons in 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 tons, 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 tons, attributable to the load on the second trailer 10''.
[0077] Key factors for measuring traffic safety are weight (mass) distribution and overall weight. Having sensor units 15 positioned on each of the axle groups 12, 12', and 12'' allows operators (as well as business owners and regulators) to have real-time or near-real-time large amounts of data on the vehicle. This increases confidence that the vehicle 3 is safely loaded and can operate safely on the road. It can also be used to warn the driver or operator if there is a significant change in weight that could indicate a loss or spillage of load.
[0078] In the context of this explanation, truck 5 includes a portion of vehicle 3 configured to tow a trailer. That is, truck includes a power pack (such as a diesel engine, gasoline engine, or electric motor) to drive the vehicle combination. Truck may include a rigid truck, a tow truck, a tractor, etc. It should be understood that other vehicle types that tow trailers may use this system in other examples. For example, a light vehicle, a sports utility vehicle, a minibus, or a light passenger car may be configured to tow a caravan or other trailer containing substantial weight that needs to be monitored.
[0079] In the context of this description, the vehicle subunit 7 may include an axle group 12 (or its components), a trailer 10, or other components that can form part of or connect to the vehicle 3.
[0080] In some other examples, a vehicle subunit can be part of track 5. For example, a vehicle subunit could be a combination of tires and wheels, and the sensor unit 15 is a tire pressure monitoring unit. In other examples, a vehicle subunit could be an axle group, suspension assembly, or brake assembly on track 5, and thereafter, the respective sensor units are also located on track 5.
[0081] In some examples or scenarios, System 1 may operate while Vehicle 3 does not have Trailer 3 under its towing, and it should be understood that the system receives sensor data from Sensor Unit 15 associated with Track 5 for record-keeping and other purposes described herein. In some examples, Selection 17 may include the removal of a vehicle subunit (7), such as removing a previously selected Trailer (10) for another journey.
[0082] Here, various methods 100 implemented by System 1, the data acquisition device 11, and the server 31 are described exemplarily.
[0083] Overview of sensor data collection methods Referring to Figure 3, a first method 100 for collecting sensor data is illustrated. This example includes the selection 17 of a sensor unit 15 to be associated with a vehicle 3. Typically, this may involve the operator 6 entering details of a combination of a truck 5 and a trailer 10 via a user interface 63, which can be used to specify the selected sensor unit 15 to be associated with the vehicle 3 / truck 5. It should be understood that this could be an explicit selection of the sensor unit 15 to be selected (e.g., a serial number or identifier of the sensor) or an indirect selection, such as entering an identifier of a particular subunit, so that the system 1 can determine each selected sensor unit 15.
[0084] In a practical example, the selected sensor unit 15 is physically associated with each vehicle subunit 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 subunits 7 are connected (such as the order of trailers in a long vehicle combination).
[0085] In this example (and with reference to Figure 1), operator 6 selects sensor units 15 (as vehicle subunits 7) from each of the first two trailers 10. For illustrative purposes, operator 6 inadvertently omits selecting sensor unit 16 from the third trailer 14.
[0086] The method then includes transmitting a selection 17, which is received by the data acquisition device 11 and / or by the server 31. In some alternative forms, the selection may occur at multiple points in the system, and in some examples, the selection 17 may even be initiated by the server 31 specifying to the operator 6 which trailer 10 should be connected to the track 5.
[0087] Method 100 further includes receiving signals 13 from sensor units 15, 16 located near track 5. This can be achieved by a first communication module 51 of the data acquisition device 11, which can receive data transmitted from the sensor units continuously or periodically. In some examples, this may include receiving a signal 1 from sensor unit 15 every second. However, it should be understood that this frequency level can be lower. For example, receiving such a signal 15 every minute may satisfy reporting or regulatory requirements for timely and updated data while potentially increasing battery life by reducing the frequency of transmission, reception, and processing of signals 13.
[0088] It is understood that the frequency of data reception may be faster than described above (e.g., more than twice per second), and those skilled in the art will understand that this can be adjusted based on use case requirements.
[0089] The received signal 13 may come from the selected sensor unit 15 (previously selected by operator 6) and other sensor units 16 within wireless signal communication range. Other sensor units 16 (as illustrated in Figure 1) include additional sensor units 16 of additional trailers 14 that operator 6 has omitted selecting. It can be understood that signals from sensor units of other passing or parked vehicles may also be received from time to time.
[0090] Method 100 further includes selecting relevant data for reporting from the received signal 13. To achieve this, Method 100 includes determining the following from the signal 13 (see Figure 3): i. A first set 21 of sensor data 23 associated with the selected sensor unit 15, and ii. A second set of sensor data 27 associated with one or more additional sensor units 16 located near track 5, excluding the first set of sensor data 23 if present. That is, sensor data not from selected sensor units 15 known to be connected to track 5.
[0091] The first set 21 of sensor data 23 is clearly related to vehicle 3 because the corresponding sensor unit 15 was selected by the operator. The first set 21 of sensor data 23 is then stored 140 along with associated time information 29 and transmitted to server 31 for record-keeping purposes 150. In some examples, storing the sensor data 23 in the data acquisition device 11 may be temporary (for example, for buffering purposes before transmitting to server 31). In other examples, the sensor data 23 (or a portion thereof) is stored in the data acquisition device 11 (or an associated data store) to provide onboard records of the data. In yet another example, the sensor data 23 may be transmitted to a mobile communication device 66 for recording, reporting, and review.
[0092] It should be understood that in some examples, the selection of the sensor unit 15 to be selected may be missing or absent. For example, this may occur when there is a new vehicle 3 or when part of the system is reset. In such cases, the described system 1 and methods 100, 200 may continue to function, and as a result, the first set 21 will not have valid sensor data 23, and most (or all) of the signals 13 will be categorized as a second set 25 of sensor data 27 associated with an additional sensor unit 16.
[0093] The second set 25 of sensor data 27 may be excluded from further processing in some situations. For example, if it is determined that signal 13 is from a sensor unit 16 of an unrelated vehicle passing through the target vehicle 3.
[0094] However, a second set 25 of the sensor data 27 may be useful for determining additional information such as context (e.g., traffic volume, proximity of other vehicles). Furthermore, the second set 25 of the sensor data 27 may be relevant because it may indicate a sensor unit 16 connected to vehicle 3 but omitted from the previous selection. Methods for identifying such additional sensors are described under a separate heading below.
[0095] Server 31 receives sensor data (which may be a first set 21 and / or a second set 25) 151 and stores the sensor data in data store 73 156. This record in data store 73 may be selectively available based on the use case. In some examples, the sensor data is sensitive information of the organization operating vehicle 3. In further examples, the sensor data and other data may be held or made available to regulatory authorities. In even further examples, the sensor data may be publicly available, by subscription or purchase.
[0096] Overview of how to identify additional sensor 16 Referring to Figure 4, this illustrates an example of how to identify the additional sensor unit 16 and each of the additional vehicle subunits 8.
[0097] In an alternative example, the method is performed on server 31. The advantages of performing the method on server 31 are greater processing power and potentially better access to records and other data to aid in identification (such as libraries in datastore 73 that link the identifiers of sensor units 16 to their respective additional vehicle subunits 8, fleet details, ownership details, etc.). When the method is performed on server 31, the data acquisition device 11 can send a second set 25 of sensor data 27 to server 31 152, which, once processed by server 31, receives a notification 33 about any additional sensor units 16 and / or additional vehicle subunits 8 that have been identified 163.
[0098] In an alternative example, this method may be implemented in the data collection device 11. This may be advantageous when the vehicle is traveling in an area without a cellular network or other network connectivity, in order to enable reliable and frequent communication with the server 31.
[0099] Referring to Figure 4, the method includes storing a second set of sensor data along with associated time information.142 The storage may be useful because the time-series pattern of the signal (and sensor data 27) may be useful in distinguishing between the sensor unit 16 passing through track 5 and tracking track 5 in a stable, regular manner (as would be expected if they were connected).
[0100] The method also includes identifying whether one or more additional sensor units 16 are tracking track 5 in a second set 25 of sensor data 27. This may include determining whether a signal 16 corresponding to a specific and distinctive additional sensor unit 16 has been detected consistently and over at least a threshold period.
[0101] In some examples, step 160, which identifies whether an additional sensor unit is tracking a track, is based on additional circumstances including one or more of the following: - Track 5 movement, - The distance between the additional sensor unit 16 and the data acquisition device 11 or track 5, - Signal strength of the received signal 13 associated with the additional sensor unit 16, - Identification information of the additional sensor unit 160 and / or each additional vehicle subunit 8, - Historical or trend information, and - Third-party input such as third-party software (for job management or compliance) or data entry systems.
[0102] In response to the identification of an additional sensor unit 16 tracking track 5, a notification 33 of this fact may be sent to the operator 6 or other entity 162. This notification may include details of the specific additional sensor unit 16 and / or additional vehicle subunit 8. This may include querying a database so that the notification can be specific, including identifying the specific trailer 14 associated with the identified additional sensor unit 16 (by serial number or license plate, for example).
[0103] Notification 33 is useful for informing operator 6 of an error. In some cases, this could simply be a trailer 16 or axle group 12' that was physically connected to vehicle 3 but did not properly input data to system 1 (e.g., selecting the wrong trailer). This notification may also indicate other technical errors. For example, a mechanic may have installed a sensor unit on the wrong vehicle subunit 7, resulting in the data acquisition device 11 receiving a signal 13 from an unexpected sensor unit.
[0104] The notification 33 may be sent to one or more of the following: the user interface 63 associated with the data collection device 11, the mobile communication device 6 associated with the user 67 of the vehicle 3, the processing device 69 of the vehicle 3, and / or the server 31.
[0105] In some cases, notification 33 includes a request 35 or recommendation 37 to include one or more additional sensor units 16 in selection 17. If accepted, this associates the additional sensor units 16 and / or additional vehicle subunits 8 with track 5. As a result, further signals from these additional sensor units 16 are expected to form part of a first set 21 of sensor data 23.
[0106] In another example 33, the notification 33 is or is associated with a control signal or other instruction to include one or more additional sensor units 16 in the selection 17. This may be suitable when system 1 has high confidence that the additional sensor units 16 should be associated with vehicle 3, and therefore system 1 / server 31 will automatically (i.e., without human intervention) add the additional sensor units to the selection 17.
[0107] In a further example, the system may identify that the expected sensor unit 15 and trailer 10 are connected to vehicle 3, but the actual order of the trailers entered in the record is incorrect. That is, the operator may have selected the correct vehicle subunits but entered the wrong order during the selection 17 process. This error may be detected based on the signal strength to the data acquisition device 11. Notification 33 may include a recommendation to reorder selection 17.
[0108] Overview of 200 methods for automatically identifying sensor units In some examples, method 200 includes automatically identifying a sensor unit 15 that is tracking a vehicle 3 and automatically identifying a vehicle subunit 7 connected to a truck 5 261. This reduces the step that would otherwise require the operator 6 to explicitly select which trailer 10 or axle group 12 is connected to the truck, thereby reducing instances in which the operator enters or manipulates incorrect data.
[0109] Referring to Figure 6, the data acquisition device 11 transmits sensor data 23, 27 based on signals 13 from sensor units 15, 16 150, 152. The sensor data 23, 27 is received by the server 31 251 to identify the specific sensor unit 15, 16 tracking track 5 260. This may include identifying a serial number or other identifier unique to the sensor unit 15, 16 within the sensor data 260. As described above, the signals 13 may include various data that can be used to identify the sensor units 15, 16, including a sensor identifier, subunit identifier, and organization identifier, model number, ownership information, etc.
[0110] To determine whether specific sensor units 15 and 16 are tracking track 5, data such as timing information, location information, and signal strength can assist in determining that sensor units 15 and 16 are tracking the track over a certain period of time. The time period and context may be specified by the operator, but in practice, the combination of truck and trailer is used over time periods of several minutes, several hours, or even several days. Therefore, in one example, the specified threshold period may include confirmation that signals 13 from sensor units 15 and 16 were received by the data acquisition device for more than one minute while track 5 was moving (or had moved during that period). In other examples, this could be 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, or longer. It should be understood that a longer specified period reduces the likelihood of identifying sensor units of other passing vehicles as tracking track 5. Conversely, a shorter specified period may reduce the time the server 31 has to identify sensor units 15 and 16 as tracking track 5.
[0111] The method also includes identifying one or more vehicle subunits 7, 8 connected to the truck 5.261 This can be based on a specific sensor unit 15, 16 that was tracking the truck 5. In some examples, the signals 13 from the sensor units 15, 16 may include a message identifying the vehicle subunits 7, 8, the owners of the subunits 7, 8, or even the associated truck 5. For example, in a fleet of vehicles and trailers, an organization 88 may assign specific identifiers to all of the sensor units 15, 16 and associated vehicle subunits 7, 8, and have signals 13 transmitted from these sensor units 15, 16 encoded with messages having these identifiers.
[0112] In other examples, a library or lookup table within a database is used to identify the association between a particular sensor unit and its respective vehicle subunit. This database may be stored in the data store 73 of server 31, in organization 88, or even in a regulatory body (such as a government vehicle registration database).
[0113] Method 200 also includes storing vehicle data in a data store as follows: i. Identified specific sensor units 15, 16 that are tracking track 5, ii. Identified vehicle subunits 7, 8 tracking track 5, indicating that these vehicle subunits 7, 8 are connected to track 5 to form a vehicle. iii. Sensor data received and associated with vehicle 3.
[0114] Therefore, the above process enables the automatic identification of vehicle subunits 7, 8, such as the trailer 10 and axle group 12, which should be associated with vehicle 3. This can reduce the possibility of data entry errors or omissions from operator 6. It should also be understood that this can serve as a check for operator data entry and selection 17, and such a system can also allow operator 6 to manually enter or modify identification information.
[0115] In the example shown in Figure 5, the server 31 performs the automatic identification process. However, it should be understood that some or all of these steps in alternative modifications may be performed by the data acquisition device 11 or the mobile communication device 66. Further modifications may include the implementation of this method by a combination of the devices and server described above.
[0116] The lower part of Figure 5 shows the step in which server 31 determines the 272 control signals 41 to be sent to perform operations on other nodes and devices. These will be explained in detail in another example below.
[0117] Overview of methods for sending control signals Referring to Figure 6, the system and method may also include generating and transmitting control signals 41 172, 272. These control signals are then transmitted to the data acquisition device 11, the track 5, the vehicle subunit 7, the sensor units 15, 16, and / or actuators associated with the vehicle 3. In a practical example, this may include controlling specific sensor units 15, 16, such as increasing the sampling frequency, querying for more data, changing the power state, resetting, communication pairing or other network settings, or changing device settings.
[0118] Various sensor data 23, 27 are transmitted 150, 152 to the server 31 (or other device or node implementing the method). This may be based on a continuous periodic stream of sensor data 23, 27, or on ad-hoc reception of sensor data. In some examples, the received notification 33 may also trigger a control signal 41 or contain relevant information.
[0119] The method includes determining one or more control signals 41 based on sensor data 23, 27 170, 270. For example, if the sensor data 23, 27 indicates certain conditions, there may be an advantage in changing the mode or function of the sensor units 15, 16 or other devices in the vehicle. For example, if the sensor data 23, 27 indicates high load, temperature, or a specific context (such as the vehicle being in operation for an extended period), it may be desirable to obtain more information, and an appropriate control signal 41 may include turning on additional sensors or increasing the sampling frequency. On the other hand, if the sensor data 23, 27 indicates normal operating conditions or the vehicle is parked, an appropriate control signal 41 may include switching the sensor units 15, 16 to a low-power mode with a reduced sampling frequency and / or reporting frequency.
[0120] An example of the control signal 41 may include one or more of the following: - Request to send further sensor data, -Power setting and / or operation of sensor unit 15, -Pairing of an additional sensor unit 16 that is identified as being associated with vehicle 3, and - Mesh / network settings for sensor unit 15.
[0121] The control signal 41 is transmitted by the server 31 to each device that needs to be controlled.172,272 This may include the server 31 transmitting the control signal 41 over the network 18 for reception by the data acquisition device 11.174 The data acquisition device 11 can then transmit the control signal 41 to the sensor units 15, 16, actuators, track 5, and / or vehicle subunit 7.176 This may include passing the control signal 41 over the first communication module 51 and / or second communication module 59. In other examples, the control signal 41 may be transmitted over alternative communication paths. For example, vehicle 3 may be equipped with other transceivers that can receive the control signal 41 over a cellular network or other RF network.
[0122] The above example has described how the server 31 determines the control signal 41 and performs the steps 170 and 172 of transmitting the control signal 41. However, it should be understood that some or all of these steps may be performed by other devices such as the data acquisition device 11, the mobile communication device 66, or a computer communicating with System 1 (such as a computer operating in the organization's operations and control center).
[0123] advantage The data acquisition device 11 can collect information from sensor units 15 and 16 without prior pairing of components (such as master and slave). This can be advantageous in that the sensor units 15 and 16 may come from various manufacturers, without limiting the data acquisition device 11 to use specific proprietary components or standards. This simplifies integration into fleets where trailers and sensor units from different manufacturers may be mixed. This increases brand interoperability, and in some cases, the data acquisition device 11 can be updated or adapted to new or additional communication protocols or specifications when new sensor units come onto the market.
[0124] The example of System 1 can also identify unexpected sensor units 15, 16 which may be useful in detecting errors and omissions when the operator connects a particular combination of truck 5 and trailer 10. This can reduce instances of false alarms, underreporting, or even fraudulent reporting.
[0125] The disclosed systems 1 and methods 100, 200 can also reduce the burden of manual reporting, such as the ease of data entry and the selection of sensor units and trailers. Notices 33 and Recommendation 37 can help operators easily select devices and components located near the track 5. In further examples, the systems and methods enable the automatic identification of sensor units and trailers.
[0126] The system can also improve the functionality of the control signals 41, which cause the elements of the system to behave more efficiently and / or accurately.
[0127] Variation Examples of specific embodiments Figure 7 illustrates a specific exemplary embodiment of system 81 for monitoring vehicle 3. System 81 includes many of the features of the system described above, similar features are given corresponding reference numbers. System 81 also includes a data flow from server 31, which has the following three other entities: -Platform administrator 83, - Tracking application 84, and - A system 85 that displays vehicle-based weight monitoring.
[0128] The platform administrator 83 may have a computer, computer terminal, or other node that enables broad access to data and control of the system 81. For example, the administrator may have access to vehicle data, corresponding sensor data, and the display of notifications 33, error messages, etc. The platform administrator 83 may also have the authority to authorize control signals 41. The administrator may also have the authority to reset the system and configure sensors and other devices within the system 81.
[0129] The tracking application 84 can be implemented on computers, terminals, nodes, portable communication devices, etc. This tracking application can be used by organizations such as businesses, regulatory authorities, and research institutions to display data within the system 81. It may be useful for tracking vehicles 3 as a fleet, or in other examples, for tracking the amount of traffic and load for research and monitoring purposes. For example, university researchers may want to obtain data on the number of vehicles passing through a bridge or road section and have the weight (and other data) of such vehicles. In further examples and applications, data anonymization may be applied to sensor and vehicle data to protect personal or commercial information.
[0130] A system displaying vehicle-based weight monitoring 85 may include a user interface accessible to drivers, mechanics, warehouse staff, or other operators associated with the vehicle 3. This interface can output sensor data and its meaning, enabling operators to identify errors (such as configuration errors), load data (to ensure balanced loading of the vehicle), and other configuration data related to the vehicle. In some examples, the user interface may be integrated into a display or other user interface in the vehicle. In other examples, the visualization may be presented on a dedicated terminal or other device. In yet another example, the visualization may be displayed on a mobile communication device (such as a smartphone or tablet), laptop computer, desktop computer, etc.
[0131] A modified example of a system with multiple sensors communicating with a server. Figure 9 illustrates another modification of system 301. In this modification, each of the sensor units 315 and 316 can functionally perform the steps of the data acquisition device 11 described above. In some examples, this may involve combining the modules of the sensor units with the modules of the data acquisition device 11. In other examples, the sensor units 315 and 316 are equipped with communication modules that enable communication with the cellular network 60. Thus, the sensor units can provide signals 13 to the server 31, thereby enabling the server 31 to perform processing steps (such as the methods described above, which include steps performed by the data acquisition device 11 and the server 31).
[0132] Therefore, in one modification of method 200 in Figure 5, the server 31 receives sensor data 23, 27 (which may include a corresponding signal 13 for determining the sensor data) from the sensor units 315, 316. In a further modification, the server 31 may transmit a control signal 41 to the sensor units 315, 316 without going through a separate data acquisition device 11.
[0133] In some examples, sensor units 315 and 316 communicate with one or more other nearby sensor units to form a mesh network. In further examples, this mesh network facilitates the identification of sensor units 315 and 316 following each other within a common vehicle 3.
[0134] Variations of operating modes without a trailer Many of the above examples relate to System 1 used when Vehicle 3 includes a truck 3 towing a trailer 10, but it should be understood that the system may be operable to transmit sensor data to Server 31 when the vehicle does not have a trailer (i.e., there is no vehicle subunit). In some examples, System 1 may determine the absence of signal 13 (or the expected absence of signal 13 from a selected sensor unit 15) to indicate that Truck 5 is not towing a trailer 10, which may be relevant information for recording and / or processing at Server 31. This determination may be made in the data acquisition device 11 and / or Server 31. In addition, the sensor unit 15 of the truck itself may also continue to transmit relevant data, such as weight data, which may be important for a rigid truck that can carry a load without a trailer 10.
[0135] Modified example of automatic determination of vehicle and operator configuration In some examples, the described system enables a high degree of automation, requiring minimal or no user selection 17 to determine how vehicle 3 is configured. As mentioned above, in some examples, system 1 can automatically determine whether vehicle 3 is operating as a truck 3 without a trailer 10. In other examples, it can automatically determine the vehicle subunits 7, such as the attached trailer 10, and the order in which they are configured within the vehicle; that is, it determines the truck and trailer combination of the vehicle (and, in some cases, provides feedback on whether the combination is permitted or not). In further examples, it determines the sensor types and sensor configurations in the vehicle.
[0136] For example, the configuration decision may include one or more of the following: a. Identify the trailer 10, which is part of the combination, based on proximity over one or more time periods. Proximity can be inferred in some examples by actually receiving a wireless signal 13 (such a wireless signal has a limited range). One or more time periods may include while the vehicle 3 is stationary and / or in motion. b. Identify the specific position of the trailer in the combination. This may include one or more of the following: i. Bluetooth = This may include the use of a Received Signal Strength Indicator (RSSI) or Received Power (RX). This may be the relative distance from the indicator or sensor unit to the data acquisition device. In a further example, nodes in a network (including a mesh network) can determine the relative strength of signals from other nodes, which can then be used to determine the relative configuration of the nodes and the combination of vehicle subunits. In a further example, the network system may include direction-finding functionality (such as Bluetooth direction-finding for BLE signals). ii. Data matching – This may include data matching based on time and vehicle movement. For example, when a vehicle travels over a bump in the road (e.g., a speed bump, a pothole, etc.), acceleration (or mass) sensors on each axle of the trailer detect changes at different points in time. For example, the first trailer 10' detects the bump at t=0, and the second trailer 10'' detects the bump at t=0+1. If the system determines that the vehicles are moving forward, it can determine that the first trailer 10' is leading the second trailer 10''. It should be understood that other sensors (or data types), such as changes in motion, changes in mass, etc., may be used. In addition to bumps in the road, this principle can be extended to other changes affecting vehicle subunits, such as changes in direction, angular motion, and other forces. iii. Historical Data Matching - This may include data matching based on historical data. In one example, this may include referencing historical data (which may include data maps) that includes historical configurations with corresponding sensor data. For example, there may be historical patterns of trailer combinations including engine revolutions per minute (RPM), mass, and vehicle speed. So, if a vehicle is operating with some of these parameters (e.g., similar RPM and vehicle speed) on a new day (and without specific user input of trailer combinations), the system may determine / verify the trailer combination based on similar data from the sensor units corresponding to that historical data. In another example, historical data matching may be based on route or usage. For example, a vehicle may regularly travel from one place to another while having the same combination (e.g., a truck moving from a tunnel to a storage area). So, the historical pattern is that the vehicle uses the same combination for each ride on that particular route. So, if the system determines that a vehicle is traveling that route, the system may set that combination as one of the known historical combinations. iv. Global Navigation Satellite System (GNSS) position. If the trailer (and / or each sensor unit 15, 16) has a receiver that determines the GNSS position, the respective positions can be used to determine the configuration of the vehicle's subunits. It should be understood that this can be combined with vector mathematics to determine the trailer's position. For example, the vehicle's configuration can be determined by taking into account the overall direction, speed, and time of the received signal in conjunction with the GNSS position.
[0137] In yet another example, System 1 can automatically determine the combination of driver / operator 6 and vehicle 3. In some examples, the data acquisition device 11 is (or functionally partially) the operator 6's mobile communication device 66, which can access multiple vehicles in the fleet. Instead of manually entering details and / or pairing the mobile communication device 66 with the vehicle 3's sensors or other components, the operator may simply be able to drive the vehicle. By using this, the system may determine that the mobile communication device 66 of that particular operator 6 is moving in the same or similar pattern (or in close proximity) as the sensor units 15, 16 and / or other components of that particular vehicle. System 1, and in actual examples, the server 31, can then associate the operator 6, the mobile communication device 66, and the vehicle 3 as being operated together, and appropriately record that fact and other data. This helps to supplement or enter data such as the driver's resume, timesheets, etc.
[0138] In some examples, determining the configuration of sensors and / or each vehicle subunit (such as a trailer combination) is based on the strength and / or timing of signals 13 (e.g., RSSI or RX). For example, a weaker wireless signal may indicate a sensor further away from the data acquisition device 11 than a signal from a stronger sensor. It should be understood that this can indicate distance, but is not definitive, because sensors can transmit signals at different power levels. It should also be understood that signals can be attenuated by the vehicle's components. Therefore, in some examples, a lookup table of known signal strengths with sensor and vehicle subunit configurations and distances may be used to assist in determining the vehicle configuration.
[0139] In other examples, signal timing, such as pings between data acquisition devices and sensors, can be used to determine or estimate the distance between components. In some examples, this may also involve collecting data on communication between sensors, as well as their respective timings and signal strengths. The data acquisition devices and sensors are part of a wireless network, and in some examples, this may involve determining the configuration of sensors and / or subunits based on how the network components (nodes) are configured, which may indicate the configuration of sensors and vehicle subunits. In some examples, the wireless network is a mesh network, and the network organization may be used to determine the configuration.
[0140] In yet another example, system 1 may be useful in determining when sensor unit 15 has failed due to the lack of reception of signal 13. In yet another example, system 1 may also determine when sensor unit 15 has been replaced by another sensor unit 15 and update selection 17 accordingly. For example, system 1 may identify that the original selected unit that should be there is no longer online, or is transmitting signal 13 but is detecting a signal from an additional sensor unit 16 that is outputting the expected signal to the original selected sensor unit. Furthermore, system 1 may determine that the additional sensor unit 16 is close to vehicle 3 and is tracking vehicle 3. Using this information, it can be confidently determined that the additional sensor unit 16 is a replacement sensor, and the system can then record (or recommend) that the additional sensor unit 16 should replace the original selected sensor unit 15 in the record.
[0141] Modified example having individual sensors communicating with a single data acquisition device Figure 10 illustrates an example of a system in a surveillance vehicle 3, in this case located on track 5, having a single data acquisition device 11. Sensor units 15 are provided to various vehicle subunits 7, such as axle groups 12. In this example, the sensor units 15 communicate directly with the data acquisition device 11. The data acquisition device 11 can communicate with a mobile communication device 66, as described in the example provided above.
[0142] In this example, an additional vehicle subunit 8, which was not part of the vehicle combination 1 specified (or otherwise determined) by the user, is located near truck 5. Each sensor unit 16 of the additional vehicle subunit 8 also broadcasts a signal that is directly received by the data acquisition device 11. The data acquisition device 11 (or system) can then determine whether the additional sensor unit 16 (or vehicle subunit 8, such as an additional trailer 14) is following truck 5. In response, the data acquisition device 11 (or system) can take additional actions, such as adding the vehicle subunit 8 as part of the vehicle combination, or send a notification of this fact to the driver, fleet operator, regulator, or another user or entity.
[0143] Modified example having individual sensors that communicate with a mobile communication device. Figure 11 illustrates an alternative example of the system in the surveillance vehicle 3, in which each of the sensor units 15 and 16 directly transmits a signal 13 to a mobile communication device 66. In this example, sensor data 23 and 27 from the signal 13 can be relayed from the mobile communication device 66 to the data acquisition device 11. The system 1, or its components such as the data acquisition device, can then perform methods described herein, such as identifying whether an additional sensor 16 or an additional vehicle subunit 8 is tracking the track 3, and may perform additional steps in response.
[0144] Variant variation: Some subunits have data collectors, while at least one of the other subunits lacks a sensor. Figure 12 illustrates an example of a vehicle 1 including a truck 5 and several subunits 7. This includes a first trailer 10' and a third trailer 10''', each having associated sensor units 15. In particular, the second trailer 10'', located between the first and second trailers, has no sensors whatsoever.
[0145] In this example, the data acquisition device 11 can determine the location or estimated location of each trailer based on signals 13, 13' from the sensor units. In this example, the signal 13' from the sensor unit 15' of the third trailer 10''' is received later than would normally be expected if the sensor were mounted on the second trailer. This may be due to the longer flight time of the signal 13'.
[0146] Furthermore, the data acquisition device 11 (or server, or mobile communication device) can identify that the system is not receiving signals from the trailer between the first trailer and the third trailer. Therefore, from the gap / distance from the third trailer, it can be determined that there is a second trailer 10'' (or another subunit) in between. The system may output a notification that there is a second trailer without its respective sensors and invite the operator to check the sensors, install sensors, or input data regarding the second trailer or the overall trailer configuration.
[0147] This advantageously allows the system to be used with trailers that may not have the sensor unit 15 (for example, for one-time use) or in the event of a sensor unit failure. At the same time, this still allows the unit to determine the configuration of the vehicle 3 (or invite the user to input the configuration data of the vehicle 3) in such alternative cases.
[0148] Modified form with multiple data collection devices Figure 13 illustrates an alternative modification of the system for a monitoring vehicle 3, in which the vehicle may have multiple data acquisition devices 11. In this example, each trailer 10', 10'', 10'' (as vehicle subunit 7) has one or more respective data acquisition devices 11', 11'', 11'''', 11''''. Thus, the sensors of the vehicle subunits may be configured to communicate with the data acquisition devices 11 in their subunits (instead of communicating directly with the data communication devices 11 in the truck 5). This may be advantageous for long vehicles such as road trains, in which signals 13 from sensors (from the rearmost trailer, for example) may need to travel relatively long distances to reach the data acquisition devices 11 in the truck 3. This may affect reliability, and by having data acquisition devices 11', 11'''', 11'''', 11'''', this can increase the reliability of the system receiving sensor data.
[0149] In some examples, data communication devices 11', 11'', 11'''', 11'''' may then relay sensor data by communicating directly with a mobile communication device 66 and / or data acquisition device 11 in the truck. In other examples, the data communication device in the vehicle subunit may include cellular communication means for transmitting sensor data to a server, data acquisition device 11, and / or mobile communication device 66.
[0150] In a further example, data communication devices in vehicle subunits can also function as asset tracking means for the operator. This may include tracking the usage, location, and other data of trailers, axle groups, and other components.
[0151] Modified example with network device Figures 14 and 15 illustrate an alternative example in which vehicle 3 includes a communication network for networked devices.
[0152] In some examples, one or more network devices are part of a network of devices that communicate directly or indirectly with the data acquisition device 11. In some examples, a network device may include a repeater 116 (e.g., a network extender) that relays messages from the sensor to the data acquisition device. It should be understood that a network device may include other devices that are nodes in the network. The network device 115 may also include sensor units 15, 16, identification beacons, other communication devices, etc.
[0153] In some cases, the signals and / or identification information of network devices may be used to help determine the configuration of a vehicle and / or whether there are any unauthorized sensors, vehicle subunits, or other components moving with the vehicle.
[0154] Therefore, Method 100 may include the data acquisition device 11 periodically or continuously receiving network signals 113 transmitted by one or more network devices 115, 116, 15, 16 located near the vehicle 3. The Method further includes determining the following from the network signals 113: - A first class of network signals associated with each known, expected, or authorized vehicle subunit 7 connected to track 5, and - A second class of network signals associated with an unknown or unauthorized additional vehicle subunit 8.
[0155] A first class of network signals can be used to determine the configuration of the vehicle's vehicle subunit 7. This may include the order of the combinations of trailers 10 for vehicle 3. In some examples, a second class of network signals may also be used to determine an unknown or unauthorized additional vehicle subunit 8. This could be a subsequent additional trailer 14, which consistently results in the evaluation that the vehicle is connected to vehicle 3.
[0156] In some examples, the signal timing and / or signal strength of network signals can be used to determine the configuration of a vehicle subunit. In other examples, network characteristics such as the configuration of a mesh network may be used.
[0157] In some cases, each vehicle subunit, such as a trailer, may have a network device 115, but may not necessarily have a sensor unit. According to this method, it is possible to determine the configuration of such sensorless trailers within the vehicle 3 by using the network device to assist in the detection and identification of trailers within the vehicle.
[0158] Figure 14 illustrates an example in which multiple network devices 115 form a mesh network. In this example, this may include sensor units 15, 16 that communicate with repeaters or other networking devices. To support robustness, a mesh network can allow a single network device to form multiple communication paths with multiple network devices. Therefore, even if one of the network devices, for example, repeater 115', fails, the sensor units can still communicate signals and data through the remaining repeaters.
[0159] Figure 15 illustrates an example of a system with a local area network that combines features from the other examples described above. In this example, multiple data acquisition devices 11, 11', 11'' are provided to truck 5, vehicle subunit 7, and an additional vehicle subunit 8. A second trailer 10'' does not have a data acquisition device 11, but instead has a repeater 116 that allows sensors on the second trailer 10'' to communicate with at least one of the data acquisition devices 11. This can provide additional redundancy in case one of the data acquisition devices fails.
[0160] This example also includes additional sensor units 15' located in other parts of the vehicle subunit, which may include temperature sensors, pressure sensors, etc. It should be understood that further examples, though not marked in Figure 15, may include sensor units and other network devices operating in a mesh network.
[0161] Modified example having a data collection device that communicates with a server Figure 16 illustrates another alternative configuration of the system in which a data acquisition device 11 communicates with a sensor 15 and a server 73 (via a network 18 which may include cellular communication with a station 60). The data acquisition device 11 can periodically or continuously receive signals 13 from the sensor unit 15. The data acquisition device 11 can also transmit the signals 13 (or corresponding sets 21, 25 of sensor data 27 based on these signals 12) to the server 31. This can be achieved independently of and without the mobile communication device 66.
[0162] In some examples, the selection 17 to associate track 5 with the sensor unit 15 and subunit 7 connected to the track may be made independently of the mobile communication device 66. For example, the combination of track and subunit may be specified in a job or work instruction, or the combination may be communicated to the server 31 / organization 88 by other means (paper document, fax, email, telephone, etc.). Thus, some configurations of system 1 can operate without a mobile communication device.
[0163] Processing device Figure 17 illustrates an example of processing devices 57 and 91. The processing devices may take the form of a computer. Processing device 91 may be used in a data acquisition device 11, a mobile communication device 66, and / or a server 9. The processing devices may also be used in conjunction with one or more devices associated with an organization 88. Processing device 91 includes a processor 93, memory 94, and an interface device 95 that communicate with each other via a bus 96. Memory 94 stores instructions 97 and data 98 for implementing the methods 100 and 200 described above, and the processor 93 executes the instructions from memory 98 to implement methods 100 and 200. The interface device 95 facilitates communication with the communication network 18 and, in some examples, with a user interface and other peripherals. Note that while the processing devices may be independent network elements, the server 31 may also be part of another network element. Furthermore, the functions performed by processing device 91 may be distributed across multiple network elements.
[0164] Those skilled in the art will understand that numerous changes and / or modifications can be made to the embodiments described above without departing from the broad overall scope of this disclosure. Therefore, the embodiments of the present invention should be interpreted as illustrative and not restrictive in all respects.
Claims
1. A method (100) for monitoring a vehicle (3) comprising a truck (5) and at least one connected vehicle subunit (7), - Receiving (110) a selection (17) to associate the track (5) with one or more selected sensor units (15), wherein the selected sensor units (15) are physically associated with each vehicle subunit (7) connected to the track (5), - A data acquisition device (11) associated with the vehicle (3) periodically or continuously receives signals (13) transmitted by one or more sensor units (15, 16) located near the truck (5) (120), - From the above signal (13), - A first set (21) of sensor data (23) associated with one or more selected sensor units (15) and each vehicle subunit (7), and - Determine (130) a second set (25) of sensor data (27) associated with one or more additional sensor units (16) located near the track (5), excluding the first set (21) of sensor data (23) if present. -Storing the first set (21) of sensor data (23) together with associated time information (29) (140), A method (100) comprising: transmitting the first set (21) of sensor data (23) to a server (31) (150).
2. -Storing the second set (25) of sensor data (27) together with associated time information (32) (142), - Based on the second set (25) of sensor data (27), identify (160) whether one or more additional sensor units (16) are tracking the track (5), The method according to claim 1 (100), further comprising: identifying (160) one or more additional sensor units (16) that are tracking the track (5), and transmitting (162) a notification (33) indicating the one or more additional sensor units (16) and / or additional vehicle subunits (8).
3. Step (160) of determining whether one or more additional sensor units (16) are tracking the track (5) is, - The movement of the aforementioned track (5), - The distance between the additional sensor unit (16) and the data acquisition device (11) or track (5), - The signal strength of the received signal (13) associated with the additional sensor unit (16), - Identification information of the additional sensor unit (160) and / or each of the additional vehicle subunits (8), - Historical or trend information, and The method (100) of claim 2, further based on additional circumstances including one or more third-party inputs such as third-party software (for job management or compliance) or a data entry system.
4. The method (100) of claim 2 or 3, wherein the notification (33) includes a request (35), recommendation (37), or control signal to include one or more additional sensor units (16) in the selection (17) in order to associate the additional sensor units (16) and / or additional vehicle subunits (8) with the track (5).
5. - Further includes transmitting the second set (25) of sensor data (27) to the server (31) (152), The method according to any one of claims 2 to 4 (100), wherein the server (31) performs the step (160) of identifying whether one or more additional sensor units (16) are tracking the track (5).
6. The method according to any one of claims 2 to 4 (100), wherein the data acquisition device (11) performs the step (160) of identifying whether one or more additional sensor units (16) are tracking the track (5).
7. The step (150) of sending the first set (21) of sensor data (23) to the server (31) is, - To transmit to the server (1) via the second communication module (34) into which the data acquisition device (11) is incorporated, or - The method according to any one of the prior claims (100), comprising transmitting from the data acquisition device (11) to the server (31) via a mobile communication device (66).
8. - Determining one or more control signals (41) based on the first set (21) of received sensor data (23) and / or the second set (25) of sensor data (27) (170), The method according to any one of the prior claims (100), further comprising transmitting one or more control signals (41) to the data acquisition device (11), the truck (5), the vehicle subunit (7), one or more sensor units (15, 16), and / or one or more actuators associated with the vehicle (3) (172).
9. The one or more control signals (41) - Request to send further sensor data, - Power setting and / or operation of the sensor unit (15), - Pairing of additional sensor units (16), and - The method according to claim 8 (100), comprising one or more mesh / network settings of the sensor unit (15).
10. - The data acquisition device (11) periodically or continuously receives network signals (113) transmitted by one or more network devices (115) located near the vehicle (3), - From the network signal (113), - A first class of network signals associated with each known or authorized vehicle subunit (7) connected to the track (5), and The method according to any one of the prior claims (100), further comprising determining a second class of network signals associated with an unknown or unauthorized additional vehicle subunit (8).
11. The method according to claim 10, further comprising determining the configuration of the vehicle subunit and / or additional vehicle subunit (8) of the vehicle based on signal timing, signal strength, or network connectivity characteristics.
12. A data acquisition device (11) for monitoring a vehicle (3) having a truck (5) and at least one connected subunit (7), wherein the data acquisition device (11) - A first communication module (51) for periodically or continuously receiving (120) signals (13) transmitted by one or more sensor units (15, 16) located near the track (5), -Memory (53), Selection data (55) indicating the selection (17) of one or more sensor units (15) associated with the track (3), wherein the selected sensor units (15) are physically associated with each vehicle subunit (7) connected to the track (5), - A memory (53) for storing sensor data (23, 27), - Processing device (57), - From the signal (13) received in the first communication module (51), (i) A first set (21) of sensor data (23) associated with one or more selected sensor units (15) and each vehicle subunit (7), (ii) Determining (130) a second set (25) of sensor data (27) associated with one or more sensor units (16) located near the track (5), excluding the first set (21) of sensor data (23), The first set (21) of sensor data (23) together with associated time information (29) is stored (140) in the memory (53), A data acquisition device (11) comprising a processing device (57) configured to transmit (150) the first set (21) of sensor data (23) to a server (31).
13. The processing device (57) -Storing the second set (25) of sensor data (27) together with associated time information (32) in the memory (53) (142), - Based on the second set (25) of sensor data (27), identify (160) whether one or more additional sensor units (16) are tracking the track (5), - The data acquisition device (11) according to claim 12, further configured to transmit a notification (33) indicating the one or more additional sensor units (16) and / or additional vehicle subunits (8) in response to identifying (160) one or more additional sensor units (16) that are tracking the track (5).
14. The data acquisition device (11) according to claim 13, wherein the notification (33) is transmitted to a user interface (63) associated with the data acquisition 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).
15. The processing device (57) - The server (31) transmits the second set (25) of sensor data (27) to the server (31) (152) in order to enable the server (31) to identify (160) whether one or more additional sensor units (16) are tracking the track (5) based on the second set (25) of sensor data (27), - The data acquisition device (11) according to claim 12, further configured to receive (163) a notification (33) from the server (31) indicating the one or more additional sensor units (160) and / or additional vehicle subunits (8) in response to identifying one or more additional sensor units (16) that are tracking the track (5).
16. - A data acquisition device (11) according to any one of claims 12 to 15, further comprising a second communication module (59) configured to communicate with a communication network (61), wherein the first set (21) of sensor data (23) is transmitted to the server (31) via the second communication module (59) and the communication network (61).
17. The processing device (57) - Receiving (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 the second set (25) of sensor data (23, 27), - A data acquisition device (11) according to any one of claims 12 to 16, further configured to transmit (176) one or more control signals (41) to the track (5), a vehicle subunit (7), one or more sensor units (15, 16), and / or one or more actuators associated with the vehicle (3) via the first communication module (51) or another communication module (71).
18. A system (1) for monitoring a vehicle (3) having a truck (5) and at least one connected vehicle subunit (7), wherein the system (1) - At least one data acquisition device (11), - Receiving (120) a signal (13) transmitted by one or more sensor units (15, 16) located near the track (5), - A data acquisition device (11) is configured to transmit sensor data (23, 27) to a server (31) based on the signal (13) (150), - The server (31), - Receiving (17) the selection (17) of one or more selected sensor units (15) associated with the vehicle (3), - Receiving sensor data (23, 27) (151), A system (1) comprising: a server (31) configured to identify (160) whether one or more additional sensor units (16) other than one of the selected sensor units (1) are tracking the track (5) based on the sensor data (23, 27).
19. The server (31) - Determining at least one control signal (41) based on sensor data (23, 27) (170), The system (1) according to claim 18, further configured to transmit (172) one or more control signals (41) to the data acquisition device (11), the truck (5), the vehicle subunit (7), one or more sensor units (15, 16), and / or one or more actuators associated with the vehicle (3).
20. A method (200) for monitoring one or more vehicles (3) on a server (31), wherein each vehicle (3) comprises a truck (5) and at least one connected vehicle subunit (7), and the method (200) - Receiving (251) sensor data (23, 27) from a data acquisition device (11) associated with the vehicle (3), wherein the sensor data (23, 27) is based on a signal (13) transmitted by one or more sensor units (15, 16) located near the truck (5) and received by the data acquisition device (11), - Based on the sensor data (23, 27), identify a specific sensor unit (15) that is tracking the track (5) (260), A method (200) comprising: identifying one or more vehicle subunits (7) connected to the track (5) based on identified specific sensor units (15) that are tracking the track (5) (261).
21. A method (200) for monitoring one or more vehicles (3) on a server (31), wherein each vehicle (3) comprises a truck (5) and at least one connected vehicle subunit (7), and the method (200) - Receiving sensor data (23, 27) based on signals (13) transmitted by one or more sensor units (15, 16) located near the track (5) (251), - Based on the sensor data (23, 27), identify a specific sensor unit (15) that is tracking the track (5) (260), A method (200) comprising: identifying one or more vehicle subunits (7) connected to the track (5) based on identified specific sensor units (15) that are tracking the track (5) (261).
22. - The method according to claim 21 (200), further comprising determining the configuration of the vehicle subunit and / or sensors within the vehicle based on the sensor data (23, 27) and / or signals (13).
23. - In the data store (73), - The identified specific sensor unit (15) that is tracking the track (5), - One or more identified vehicle subunits (7) connected to the track (5), and - The method (200) according to claim 20 or 21, further comprising storing (265) vehicle data (75) indicating sensor data (23, 27) associated with the vehicle (3).
24. - Determining one or more control signals (41) based on at least the sensor data (23, 27) (270), The method according to any one of claims 20 to 23 (200), further comprising transmitting one or more control signals (41) to the data acquisition device (11), the truck (5), the vehicle subunit (7), one or more sensor units (15, 16), and / or one or more actuators associated with the vehicle (3) (272).