AUTOMATED TELEMATICS DATA LOGGING SYSTEM

The system addresses the challenge of irrelevant data logging by using access levels and timely data transmission to ensure accurate and efficient telematics data collection for vehicle diagnostics.

DE102024111663A1Pending Publication Date: 2024-11-07CUMMINS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
DE102024111663
Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-22
Filing Date
2024-04-25
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Existing systems for logging telematics data in vehicles and stationary devices do not provide sufficient data for accurate diagnosis and often capture data that is irrelevant or outdated due to changes in the vehicle's duty cycle between error code receipt and data logging.

Method used

A system comprising a remote computer system that controls a telematics device to log telematics data based on access levels, monitor for error codes, and transmit relevant data to the remote system, ensuring data relevance and reducing unnecessary data collection and transfer.

Benefits of technology

The system ensures that only relevant telematics data is collected and transmitted, reducing processing power, memory requirements, and data transfer costs while providing timely and accurate data for troubleshooting vehicle issues.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

This document provides systems, procedures, and facilities for the automatic logging of telematics data. A facility includes one or more processors and one or more storage devices that store instructions which, when executed by one or more processors, cause the one or more processors to: receive access information from a remote computer system, the access information including information specifying a data type and a logging duration; and log telematics data corresponding to the data type.Logging telematics data includes the following: storing the telematics data corresponding to the data type in a buffer for the duration of the logging; monitoring for an error code; in response to the failure to detect the error code, causing the buffer to delete a portion of the telematics data; and in response to the detection of the error code, providing telematics data to the remote computer system.
Need to check novelty before this filing date? Find Prior Art

Description

REFERENCE TO A RELATED REGISTRATION

[0001] This application claims the benefit and priority of U.S. Patent Application No. 63 / 464,344, filed on May 5, 2023, which is hereby incorporated by reference in full and for all purposes. TECHNICAL AREA

[0002] The present disclosure relates to systems and methods for automatic telematics data logging for a fleet and / or individual vehicles or stationary equipment (e.g. generator systems) or components thereof, such as powertrains, using a remote computer system. STATE OF THE ART

[0003] Vehicles used on-road and / or off-road, and / or stationary equipment such as generator sets, may include one or more electronic control units (e.g., an engine control unit (ECU), an engine control module (ECM), etc.). The electronic control unit may be configured to provide an indication of a problem with the vehicle or stationary equipment (hereinafter referred to as a "fault code") according to a predefined standard, such as the SAE J1939 standard. However, the fault code may only provide an indication of the problem and may not provide sufficient data for an accurate diagnosis. Furthermore, there may be a time lag between receiving the fault code and logging the data associated with the fault code, which corresponds to a period of time after the problem occurred.For example, the operating cycle of the vehicle or device may have changed between the receipt of the fault code and the start of data logging. Therefore, the logged data associated with the fault code may be of limited value in troubleshooting the triggered fault code. SUMMARY

[0004] One embodiment relates to a device. The device includes one or more processors and one or more storage devices that store instructions which, when executed by one or more processors, cause the one or more processors to: receive access information from a remote computer system, wherein the access information includes information specifying a data type and a logging duration; log telematics data corresponding to the data type, wherein logging the telematics data includes: storing the telematics data corresponding to the data type in a buffer for the logging duration; monitoring for an error code; in response to the failure to detect the error code, causing the buffer to delete a portion of the telematics data; and in response to the detection of the error code, providing telematics data to the remote computer system.

[0005] Another embodiment relates to a method for automatically logging telematics data for a vehicle fleet. The method includes the following: receiving a specification of a first fault code from a first vehicle in the fleet by a processing circuit of a computer system; comparing the first fault code with a list of fault codes stored in a problem database by the processing circuit, wherein the problem database stores a frequency value for each fault code in the list of fault codes; identifying by the processing circuit that the first fault code is a frequent fault code, in response to the fact that the frequency value of the first fault code is at or above a predetermined threshold; generating by the processing circuit a first vehicle group, wherein the first vehicle group includes one or more vehicles in the fleet;Generating access information by the processing circuit that causes a telematics device to log telematics data; providing the access information by the processing circuit to each vehicle in the first vehicle group, wherein the access information is structured in such a way that it causes each vehicle in the first vehicle group to generate telematics data; receiving the telematics data from one or more vehicles in the first vehicle group by the processing circuit; and providing the telematics data to a user device.

[0006] Another embodiment relates to a non-volatile, computer-readable medium that stores instructions which, when executed by one or more processors of a computer system, cause the computer system to perform operations.The operations include: receiving access information from a remote computer system, wherein the access information includes information specifying a data type and a logging duration; logging telematics data corresponding to the data type, wherein the logging of the telematics data includes: causing one or more sensors to provide the telematics data to the computer system; storing an initial telematics data record in a buffer for the duration of the logging; monitoring for an initial problem; in response to the failure to detect the initial problem, causing the buffer to delete a portion of the initial telematics data record; and in response to the detection of the initial problem, providing the telematics data to the remote computer system.

[0007] Numerous specific details are provided to facilitate a comprehensive understanding of the embodiments of the subject matter of this disclosure. The described features of the subject matter of this disclosure can be combined in any suitable manner in one or more embodiments and / or implementations. In this context, one or more features of one aspect of the invention can be combined with one or more features of another aspect of the invention. Furthermore, additional features may be identified in certain embodiments and / or implementations that may not be present in all embodiments or implementations. BRIEF DESCRIPTION OF THE FIGURES Fig. Figure 1 is a block diagram of a system for automatically logging telematics data according to an exemplary embodiment. Fig. 2 is a block diagram of a vehicle of the system of Fig. 1 according to an exemplary embodiment. Fig. 3 is a block diagram of a control system of Fig. 2 according to an exemplary embodiment. Fig. Figure 4 is a block diagram of a vehicle telematics device. Fig. 2 according to an exemplary embodiment. Fig. 5 a flowchart of a procedure for activating the automatic logging of telematics data according to an exemplary embodiment. Fig. Figure 6 is a flowchart of a procedure for activating the automatic logging of telematics data according to another exemplary embodiment. Fig. 7 a flowchart of a procedure for the automatic logging of telematics data according to an exemplary embodiment.

[0008] These and other features, as well as their organization and function, will become apparent from the following detailed description in conjunction with the attached drawings. DETAILED DESCRIPTION

[0009] The following are more detailed descriptions of various concepts relating to the implementation of procedures, facilities, and systems for the automated logging of telematics data. The various concepts introduced can be implemented in any number of ways, as the described concepts are not limited to a specific implementation method. Examples of specific implementations and applications are provided primarily for illustrative purposes.

[0010] With reference to the figures in general, the various embodiments disclosed herein relate to systems, devices, and methods for the automated logging of telematics data. A vehicle may include one or more propulsion systems (e.g., an engine, an electric motor, or another suitable propulsion machine), at least one control unit (e.g., an engine control module (ECM), an engine control unit (ECU), other electronic control units, etc.), and / or a telematics device. In some embodiments, the telematics device is implemented as a separate hardware unit comprising at least one processor and at least one memory in which instructions are stored which, when executed by the processor, cause the telematics unit to perform various operations.In some embodiments, the telematics device can be embodied in the controller as any combination of hardware and / or software. In these embodiments, the controller includes at least one processor and at least one memory containing instructions which, when executed by the processor, cause the controller and / or its telematics device to perform various operations. In the embodiments described herein, the operations are described as if they were performed by the telematics device. However, it should be clear that in other embodiments, the operations can be performed by the processing logic (e.g., processor and / or memory) of the controller. For example, the telematics device or parts thereof can be embodied in the controller described herein.In further embodiments, a combination of the control system and a separate telematics device can jointly perform various of the processes described herein.

[0011] In an exemplary operating scenario, a remote computer system uses an event-driven technical data logger to automatically collect telematics data. Specifically, the remote computer system automatically causes a telematics device to log and transmit telematics data to the remote computer system for a fleet of vehicles. Advantageously, the remote computer system collects a sample of telematics data from a selected group of vehicles. In another exemplary operating scenario, a telematics device automatically logs telematics data for a single vehicle and transmits the telematics data to the remote computer system. Advantageously, the telematics device automatically performs the data logging process before a problem (such as a fault code, diagnostic trouble code (DTC), or other diagnostic code) is detected.

[0012] In each of the exemplary operating scenarios described above, a telematics device is configured to perform operations for logging telematics data. These operations include determining a data access level. In some embodiments, the telematics device determines the data access level by requesting access level information from a remote computer system. In other embodiments, the telematics device determines the data access level based on previously received access level information. The access level refers to a quantitative or relative indication of the type of information the telematics device can access. For example, multiple access levels can correspond to one or more quantitative values ​​(e.g., between 0 and 10, between 0 and 100, etc.).In another example, the access levels include one or more relative or qualitative descriptors, such as "high," "medium," "low," etc. One or more vehicle components, such as sensors, can have a corresponding access level. For example, a first sensor might have a first access level, and a second sensor might have a second access level that differs from the first. The telematics device is structured to collect information, such as sensor data or other data, from one or more vehicle components that have an access level equal to or lower than the determined access level.

[0013] In some embodiments, the access level defines one or more specific parts of the data or information relating to the operation of one or more specific vehicle components, such as a particular operational data value. Operational data generally refers to data or information about the operation of a vehicle or vehicle component. In these embodiments, the telematics device is structured to acquire information relating to the defined operational data value via the access level. In some embodiments, the operational data values ​​defined by the access level are defined by user input. In other embodiments, the operational data values ​​defined by the access level are defined by the remote computer system.For example, the remote computer system can identify a common problem and determine one or more operational data values ​​that correspond to the common problem. The remote computer system can define the one or more access-level operational data values ​​as the one or more operational data values ​​that correspond to the common problem.

[0014] Advantageously, the access layer limits data collection to optimize the type and amount of data captured by the telematics device to data that is relevant or likely to be relevant to a problem. In this way, the access layer reduces the processing power required to capture the telematics data and decreases the storage requirements for storing that data.

[0015] The processes also include logging data based on the data access level. For example, the access level can define a data type to be logged. The data type can include one or more predefined operational data values ​​and / or one or more predefined operating parameters of the vehicle. The processes can also include storing a predefined amount of data in a buffer until the telematics device detects that a trigger event has occurred. For example, the telematics device can discard older data (data older than a predefined age, where the age is based on when the data was added to the buffer) when the amount of data in the buffer exceeds the predefined amount. Advantageously, the data stored in the buffer includes operational data values ​​corresponding to a predefined period prior to the trigger event.In some embodiments, the trigger event may include the detection and / or receipt of a problem indication (and / or the detection of a fault or disturbance condition that may or may not be associated with the problem). If, in these embodiments, the telematics device detects a problem and / or receives an indication thereof, the telematics device determines that the trigger event has occurred and may therefore retain the captured data in the buffer and / or transmit the buffered data to a remote computer system. In further embodiments, the trigger event includes the detection and / or receipt of an indication of a first problem among a plurality of problems. In these embodiments, the access-level information includes an indication of which problem among the plurality of problems is the first problem.Furthermore, the telematics device determines that the trigger event has not occurred if / when the telematics device detects and / or receives an indication of a different problem than the first one defined by the access level (e.g., access information). Advantageously, the telematics device can retain captured data in a buffer without transmitting the data to a remote computer system until the trigger event occurs, thereby reducing the amount of data transmission.

[0016] As briefly described above, the operations can also include providing the logged data to a remote computer system in response to the detection of the trigger event. Discarding older data in the buffer advantageously reduces the size of the logged data provided to the remote computer system. Furthermore, by waiting until a predefined trigger event is detected, the data provided to the remote computer system corresponds to the data that occurred immediately before (a predefined time interval prior to) the problem detection, thus increasing the likelihood that the data is the most relevant to the problem and is therefore provided to the remote computer system. Additionally, since the data stored in the buffer includes operational data values ​​corresponding to a data type defined by the access level (e.g.,Data that is relevant or likely to be relevant to the first problem can include curated data from the triggering event in the transmitted data, but only if the triggering event occurs. The transmission, including the data in the buffer, can include less than all the generated telematics data, thereby reducing the transmission size, the processing power required to transmit the data, the amount of storage needed to store the transmitted data, and the costs associated with transmitting the data (e.g., mobile data costs).

[0017] In some embodiments, the remote computer system can receive telematics data from one or more vehicles in a fleet. As described above, the vehicle(s) can provide telematics data that includes data relevant or likely to be relevant to a predefined problem (e.g., the problem defined by the access level). In this way, the remote computer system receives data from one or more vehicles in the fleet, including telematics data that is relevant or likely to be relevant to the predefined problem. Advantageously, a user can use the data received from one or more vehicles to understand and resolve the problem.

[0018] The term "operating parameter" and similar terms used herein refer to a setting (numerical, etc.), an operating state, a control procedure or sequence, and / or any other parameter that defines and / or controls the operation of a device or part thereof (e.g., a vehicle, a vehicle engine, etc.). Examples of operating parameters may include, but are not limited to, a fuel-air mixture, a transmission shift pattern, a maximum permissible engine speed, a maximum permissible engine torque, a maximum power output via a power take-off, a maximum engine speed, etc. Operating parameters may also include control parameters for an exhaust aftertreatment system and other components or systems. Control parameters for an exhaust aftertreatment system may, for example, include the dosing quantity and timing, maximum / minimum permissible exhaust heating values, etc.

[0019] The term "operating data" and similar terms used herein refer to data, information, etc., concerning the operation of a device, such as a vehicle. The operating data is based on the device's control parameters. This operating data may include data relating to the operation of an exhaust aftertreatment system (e.g., NOx emissions, greenhouse gas (GHG) emissions, particulate emissions (PM), etc.), data relating to the operation of an engine (e.g., torque, speed, etc.), data relating to the operation of a turbocharger, data relating to the operation of a fuel system (e.g., timing and / or quantity of fuel injection), etc. In some embodiments, the operating data may be measured, detected, and / or determined by one or more sensors.

[0020] The term “telematics data” and similar terms used herein refer to any combination of operating parameters and / or operating data. In some embodiments, metadata is provided with one or both of the operating parameters and / or operating data. The metadata may include information such as a vehicle or engine identifier, a timestamp, a geolocation stamp indicating the location of the vehicle or the device associated with the data, and / or other metadata. Accordingly, the operating parameters, operating data, and / or telematics data described herein, which are generated, transmitted, or received, may additionally include corresponding metadata. For example, when an operating data value is generated, transmitted, or received, metadata corresponding to that operating data value may also be generated, transmitted, or received. More specifically, when an initial operating data value is generated (e.g.,(detected by a sensor), the telematics device also generates metadata corresponding to the first operational data value, such as a timestamp, an identification of which sensor generated the first operational data value, a geolocation stamp, etc.

[0021] As used herein, the terms “problem,” “vehicle problem,” “potential problem,” and similar terms refer to a situation in which one or more vehicles and / or other equipment (e.g., powertrains, engines, etc.) or one or more components thereof are operated under predefined operating conditions (e.g., a threshold or other predefined conditions). In some embodiments, when a problem or potential problem occurs in a vehicle, one or more values ​​of the vehicle’s operating data may be greater than a maximum threshold and / or less than a minimum threshold. In some embodiments, two or more operating data values ​​may be used in combination to characterize the problem.A problem can be characterized, for example, by a first operating data value being above a first threshold and a second operating data value being below a second threshold that differs from the first. It is understood that any combination of operating data values ​​(and corresponding thresholds) can be used to characterize a problem. In some embodiments, the vehicle problem can correspond to a fault code or cause the triggering of a fault code or other malfunction code, such as a diagnostic trouble code (DTC), by an electronic control unit (ECU). In these embodiments, the ECU can be configured to detect and / or determine the problem and output a fault code corresponding to the problem.

[0022] The systems, methods, and devices described herein provide a technical solution to the technical problem of logging telematics data for a single vehicle and / or a fleet of vehicles and / or other equipment (e.g., powertrains, engines, etc.) relevant to a vehicle problem, thereby reducing the amount of data transmitted between a vehicle's telematics device and a remote computer system. For example, in one embodiment, a telematics device may not log any telematics data until it is provided with an appropriate level of access to prevent it from logging data that is not, or is unlikely to be, relevant to a vehicle problem.Determining the access level reduces the processing power required by the telematics device to generate data logs and decreases the device's memory usage by preventing the storage of telematics data that is not, or likely not, relevant to a vehicle problem. Furthermore, when the telematics device logs telematics data, it may filter out received data that is not, or likely not, related to the vehicle problem. This means that essentially only vehicle-relevant data is logged, reducing the amount of data recorded by the telematics device. Additionally, the telematics device may transmit only a portion of the logged data to a remote computer system, further reducing the amount of data provided during a data transfer.For example, the telematics device can store the logged data in a buffer that regularly (e.g., every time new data is received, every second, every minute, every hour, etc.) deletes older logged data. Advantageously, only the most recent portion of the logged data is transmitted to the remote computer system to reduce the amount of data provided during transmission.

[0023] In another exemplary embodiment, the computer systems described herein can advantageously cause a group of vehicles in a fleet to log telematics data and make this data available to the remote computer system. In this way, the remote computer system collects a sample of the fleet's telematics data from only one group of vehicles. For example, the remote computer system can use a model (e.g., a statistical model, a machine learning model, an artificial intelligence model, etc.) to identify an initial group of vehicles in the fleet. The remote computer system can then cause a telematics device in each vehicle of the initial group to log telematics data and transmit it to the remote computer system.Advantageously, the first vehicle group includes fewer vehicles than the total number of vehicles in the fleet, thus reducing the number of transmissions for receiving telematics data by the remote computer system and the amount of data received by the remote computer system. These and other features and advantages are described in more detail below.

[0024] Referring to Fig. Figure 1 shows a block diagram of a system 100 for powertrain and fleet management via cloud computing according to an exemplary embodiment. As in Fig. As shown in Figure 1, System 100 includes a network 105, a remote computer system 110, and a fleet 200, which includes one or more vehicles 202. The individual components of System 100 communicate with each other and are coupled via Network 105. In particular, the remote computer system 110 and the computer systems (e.g., controllers, telematics devices, etc.) of the vehicles 202 of Fleet 200 are communicatively coupled to Network 105, so that Network 105 allows the direct or indirect exchange of data, values, instructions, messages, and the like (represented by the double arrows in Figure 1). Fig. 1).

[0025] In some configurations, Network 105 is configured for communicative coupling with additional computer systems. In operation, Network 105 facilitates data communication between the remote computer system 110 and other computer systems connected to a service provider operating the remote computer system 110, and / or to a customer of the service provider (e.g., a vehicle or fleet owner), such as a user device (e.g., a mobile device, smartphone, desktop computer, laptop computer, tablet, or other suitable computer system). Network 105 may include one or more of a cellular network, the internet, Wi-Fi, WiMAX, a proprietary vendor network, a proprietary service provider network, and / or any other type of wireless or wired network.

[0026] The remote computer system 110 is a remote computer system such as one or more remote servers, a cloud computer system, and the like. As used herein, the terms "remote computer system" and "cloud computer system" are used interchangeably and refer to a computer or data processing system that has terminals located remote from the central processing unit (e.g., processing circuit 112) from which users and / or other computer systems communicate with the central processing unit. In some embodiments, the remote computer system 110 is part of a larger computer system, such as a general-purpose server or other general-purpose computer system. In other embodiments, the remote computer system 110 is implemented on a third-party computing device operated by a third-party service provider (e.g., AWS, Azure, GCP, and / or other third-party computing services).

[0027] In some embodiments, the remote computer system 110 is operated by a service provider (e.g., a company). Accordingly, in some embodiments, the remote computer system 110 is a computer system of a service and / or system / component provider that is controlled, managed, or otherwise connected to a service and / or system / component provider (e.g., an engine manufacturer, a vehicle manufacturer, a manufacturer of an exhaust aftertreatment system, etc.). In the example shown, the remote computer system 110 is operated and managed by an engine manufacturer (which may also manufacture and distribute other goods and services). Accordingly, an employee or other operator connected to the service and / or system / component provider can operate the remote computer system 110.

[0028] As in Fig. As shown in Figure 1, the remote computer system 110 includes a processing circuit 112, a fleet monitoring circuit 130, and a communication interface 150. The processing circuit 112 is coupled to the fleet monitoring circuit 130 and / or the communication interface 150.

[0029] In a configuration, the fleet monitoring circuit 130 and / or one or more of its components (e.g., the vehicle data circuit 132, the problem tracking circuit 134, and / or the vehicle cluster circuit 136) are embodied as instructions executable by a processor, such as processor 114. The instructions can be embodied as programmable logic, including code written in any programming language, including but not limited to Java or similar languages ​​and all conventional procedural programming languages, such as C or similar. The machine-readable program code can be executed on a single processor or on multiple remotely located processors. In the latter case, the remote processors can be interconnected via any network type (e.g., CAN bus, etc.).

[0030] In another configuration, the Fleet Monitoring Circuit 130 and / or one or more of its components are embodied as hardware units, such as one or more electronic control units. Thus, the Fleet Monitoring Circuit 130 and / or one or more of its components can be embodied as one or more circuit components, including, but not limited to, processing circuitry, network interfaces, peripherals, input devices, output devices, sensors, etc. In some embodiments, the Fleet Monitoring Circuit 130 and / or one or more of its components can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-chip (SoC) circuits, microcontrollers, etc.), telecommunications circuits, hybrid circuits, and any other type of "circuit."In this respect, the Fleet Monitoring Circuit 130 and / or one or more components thereof may include any type of component to achieve or facilitate the achievement of the operations described herein. A circuit such as described herein may, for example, include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, etc. The Fleet Monitoring Circuit 130 and / or one or more components thereof may also include programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, or the like.The Fleet Monitoring Circuit 130 and / or one or more components thereof may include one or more memory devices for storing instructions executable by the processor(s) of the Fleet Monitoring Circuit 130 and / or one or more components thereof. The one or more memory devices and the processor(s) may have the same definition as provided below with respect to the memory device 116 and the processor 114. In some configurations of the hardware unit, the Fleet Monitoring Circuit 130 and / or one or more components thereof may be geographically distributed across different locations within the System 100. Alternatively, and as shown, the Fleet Monitoring Circuit 130 and / or one or more components thereof may be embodied in or within a single unit / enclosure, which is shown to be the Remote Computer System 110.

[0031] In the example shown, the remote computer system 110 includes at least one processing circuit 112 with the processor 114 and the storage device 116. The processing circuit 112 can be constructed or configured to execute or implement the instructions, commands, and / or control operations described herein with respect to the fleet monitoring circuit 130 and / or one or more components thereof. The configuration shown represents the fleet monitoring circuit 130 and / or one or more components thereof embodied as instructions. However, as mentioned above, this representation is not to be understood as a limitation, since the present disclosure provides for other embodiments in which the fleet monitoring circuit 130 and / or one or more components thereof are configured as a hardware unit.All such combinations and variations shall fall within the scope of protection of the present disclosure.

[0032] The at least one processor 114 can be implemented as one or more single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and / or suitable processors (e.g., other programmable logic devices, discrete hardware components, etc.) to perform the functions described herein. A processor can be a microprocessor, a group of processors, etc. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or another such configuration. In some embodiments, the one or more processors can be shared by multiple circuits (e.g.,The fleet monitoring circuit 130 and / or one or more components thereof may include or otherwise share the same processor, which in some exemplary embodiments can execute instructions stored in different memory areas or accessed in other ways. Alternatively or additionally, the one or more processors may be structured to perform certain operations independently of one or more coprocessors. In other embodiments, two or more processors may be connected via a bus to enable independent, parallel execution of instructions, pipelined execution, or multithreaded execution of instructions. All such variations are intended to fall within the scope of protection of this disclosure.

[0033] The at least one storage device 116 (e.g., memory, storage unit, storage device) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage) for storing data and / or computer code to complete or facilitate the various processes, layers, and modules described herein. For example, the storage device 116 may include dynamic random-access memory (DRAM). The storage device 116 may be communicatively connected to the processor 114 to provide the processor 114 with computer code or instructions for performing at least some of the operations described herein. Furthermore, the storage device 116 may be or include physical, persistent memory or non-volatile memory.Accordingly, the storage device can include 116 database components, object code components, script components, or any other type of information structure to support the various activities and information structures described herein.

[0034] The communication interface 150 is structured to receive messages from and to other computing devices, users, and the like that are connected to the remote computer system 110. The communication interface 150 is structured to exchange data, messages, instructions, and the like with an input / output device of the components of the system 100. In some embodiments, the communication interface 150 includes communication switching logic to facilitate the exchange of data, values, messages, etc., between the communication interface 150 and the components of the remote computer system 110. In some embodiments, the communication interface 150 includes machine-readable media on which instructions for facilitating the exchange of information between the communication interface 150 and the components of the remote computer system 110 are stored.In some configurations, the communication interface 150 includes any combination of hardware components, communication switching logic, and machine-readable media.

[0035] The communication interface 150 can include at least one network interface. The network interface is used to establish connections with other computing devices over the network 105. The network interface includes program logic that facilitates the connection of the remote computer system 110 to the network 105. In some arrangements, the network interface includes any combination of a wireless network transceiver (e.g., a cellular modem, a Bluetooth transceiver, a Wi-Fi transceiver) and / or a wired network transceiver (e.g., an Ethernet transceiver). For example, the communication interface 150 includes an Ethernet device such as an Ethernet card and machine-readable media such as an Ethernet driver configured to facilitate connections to the network 105.In some configurations, the network interface includes the hardware and machine-readable media sufficient to support communication over multiple data communication channels. Furthermore, in some configurations, the network interface incorporates cryptographic functions for establishing a secure or relatively secure communication session, in which the data transmitted during the session is encrypted.

[0036] In an exemplary embodiment, the communication interface 150 is structured to receive information from the vehicles 202 of the fleet 200 and to provide this information to the components of the remote computer system 110. The communication interface 150 is also structured to transmit information (e.g., data, instructions, etc.) from the components of the remote computer system 110, such as the fleet monitoring circuit 130, to the vehicles 202 of the fleet 200.

[0037] The vehicle data circuit 132 is structured to receive telematics data from one or more vehicles 202 of the fleet 200 (e.g., via the communication interface 150 and the network 105). As described above, the telematics data may include operational data and / or one or more operational parameters corresponding to a vehicle problem or potential vehicle problem. In some embodiments, the vehicle data circuit 132 is structured to provide instructions to the one or more vehicles 202 (e.g., a vehicle controller) that cause the one or more vehicles 202 to provide the telematics data. For example, the vehicle data circuit 132 may be configured to provide access information to a vehicle 202. In some embodiments, the access information is provided as an access information data packet.The access information data packet is a data object containing a payload, a header, and / or a signature. The access information can encode instructions for a telematics device (e.g., the Telematics Device 400 from [company name]). Fig. 2) Instruct, command, and / or otherwise permit and enable the logging of telematics data and the transmission of the telematics data to the remote computer system 110. In some embodiments, the access information includes information indicating an access level for the telematics device 400. For example, the access information may enable the telematics device 400 to log telematics data to which the telematics device 400 would not normally have access.

[0038] In some embodiments, the access information includes information indicating a data acquisition parameter to be logged by the telematics device 400. The data acquisition parameter may define a data type to be logged by the telematics device, a data logging duration, a data buffer size, etc. The data type may include one or more engine data (e.g., engine output power, engine output torque, engine speed, engine exhaust temperature, engine exhaust pressure, etc.), exhaust aftertreatment data (e.g., an exhaust aftertreatment temperature value, an exhaust aftertreatment efficiency such as a nitrogen oxide reduction value, a carbon oxide oxidation value, a sulfur oxide reduction value, etc.), and / or other operating data or operating parameters of the vehicle 202.

[0039] In some embodiments, the data type defined by the access information can correspond to one or more problems. The problem can correspond to one or more components of the vehicle 202. The access information can define a data type that specifies the collection or logging of data corresponding to the one or more components of the vehicle 202. In one exemplary implementation, a first problem can refer to a problem in a propulsion system of the vehicle 202, and the access information can define the logging of engine data. In another exemplary implementation, a second problem can refer to a problem in an exhaust aftertreatment system associated with the engine 210, and the access information can define the logging of both engine and exhaust aftertreatment data.It is understood that other problems may indicate problems in other components of the vehicle 202 (e.g., the cylinders 212, the vehicle subsystems 235 and / or other components located in ). Fig. (2 are not shown). Thus, the access information can define logging data corresponding to the component(s) where a problem or issue occurs.

[0040] In further embodiments, the access information can define the logging of one or more operational data values. In some embodiments, the remote computer system 110 can determine the one or more operational data values ​​based on user input. In further embodiments, the remote computer system 110 can determine the one or more operational data values ​​based on a common problem and identify one or more operational data values ​​that correspond to the common problem.

[0041] In some embodiments, the data logging duration can define a period during which the telematics device 400 logs data. The data logging duration can correspond to a predefined timestamp condition (e.g., data with timestamps within the last hour, last day, last week, etc.) stored by the telematics device 400. In some embodiments, the data logging duration can be defined by a predefined condition, such as the detection and / or receipt of information indicating a problem (e.g., an error code) and / or a user device condition.

[0042] In some embodiments, the data buffer size can define a data size (e.g., megabytes, gigabytes, etc.) for the telematics device 400 to log data. The data buffer size can correspond to a data volume (e.g., up to 100 megabytes, up to 10 gigabytes, etc.) stored by the telematics device. In an exemplary implementation, the data buffer size can be 100 megabytes, and if the data volume stored in the buffer exceeds 100 megabytes, the telematics device 400 can delete a portion of the data stored in the buffer (e.g., starting with the oldest data).

[0043] In some embodiments, the data buffer size can define a predefined period or duration. For example, the data buffer size can correspond to a predefined period (e.g., 45 minutes, 1 hour, 1 day, etc.) during which data is held in the buffer. The Telematics Device 400 can automatically delete data corresponding to older data (data older than the predefined period, where the age is based on when the data was added to the buffer). In an example implementation, the data buffer size can be one hour, and if a timestamp of a data value stored in the buffer is older than one hour, the Telematics Device 400 can delete the data value stored in the buffer.

[0044] The problem tracking circuit 134 is structured or configured to receive data from one or more vehicles 202 of the fleet 200 relating to a problem or issue associated with those vehicles 202. In this context, the data may include a description of a problem (e.g., an error code). In some embodiments, the problem tracking circuit 134 is configured to identify a common problem for the fleet 200. For example, upon receiving a description of the first problem from a number of vehicles 202 in the fleet 200 exceeding a predefined threshold, the problem tracking circuit 134 may determine that the first problem is a common problem.In another exemplary embodiment, the problem tracking circuit 134 can, in response to receiving user input indicating that the first problem is of interest, determine that a first problem is a problem of interest. In yet another exemplary embodiment, the problem tracking circuit 134 can, in response to receiving an indication of the first problem with a frequency exceeding a predetermined threshold of occurrences of the first problem, determine that a first problem is a frequent problem.

[0045] In one exemplary embodiment, the problem tracking circuit 134 is configured to identify a common problem for the fleet 200 by detecting that the frequency of occurrence of an initial problem exceeds a predetermined threshold. In some embodiments, the remote computer system 110 automatically enables the collection of telematics data by providing access information for one or more vehicles 202 of the fleet 200. In other embodiments, the remote computer system 110 enables the collection of telematics data by providing access information for one or more vehicles 202 of the fleet 200 in response to user input.

[0046] In some embodiments, the problem tracking circuit 134 can store or be coupled to a problem database containing a list of problems (e.g., error codes). The problem database can store a frequency indicator or frequency value for each problem in the list. The frequency indicator or frequency value refers to the number of times a problem (e.g., error code) has occurred within a predefined period (e.g., within the last 6 months, within the last 30 days, etc.). More precisely, the frequency indicator or frequency value indicates how often each of the problems (e.g., error codes) has occurred, based on the number of times the problem tracking circuit 134 received a notification for each problem in the list within the specified period.For example, if the fault code FCXXX is received more than X times for a vehicle group within a predefined period (e.g., a quarter of a year), then the problem tracking circuit 134 designates the fault code FCXXX as a frequent fault code. If FCXXX occurs less than X times within the predefined period, then the problem tracking circuit 134 designates the fault code FCXXX as an infrequent fault code.

[0047] The problem tracking circuit 134 can determine that a problem is a frequent problem by detecting that a frequency value of the problem is greater than a frequency threshold. In some embodiments, the problem database can store information about whether a problem is a frequent problem. For example, each problem in the list of problems stored by the problem database can correspond to an indication of whether the problem is a frequent problem. The problem tracking circuit 134 can compare a received error code with the problem database to determine whether the received problem is a frequent problem.

[0048] In some embodiments, the vehicle data circuit 132 is configured to transmit the access information to each of the vehicles 202 in the fleet 200. In other embodiments, the vehicle data circuit 132 selectively transmits the access information to one or more vehicles 202 in the fleet 200. The vehicle cluster circuit 136 is structured or configured to define a vehicle group 202 of the fleet 200 and enables the vehicle data circuit 132 to transmit the access information to that vehicle group 202. In some embodiments, the vehicle group 202 includes fewer vehicles 202 than the total number of vehicles 202 in the fleet 200.If the vehicle data circuit 132 selectively transmits the access information to one or more vehicles 202 in the group, advantageously only the vehicles 202 in the group are caused to provide operating data and / or operating parameters to the remote computer system 110. In this way, the remote computer system 110 collects a sample of the operating data and operating parameters of the fleet 200, thereby reducing the processing power required to collect the operating data and operating parameters and reducing the amount of memory required to store the operating data and operating parameters.

[0049] The vehicle clustering circuit 136 is structured or configured to determine a vehicle group 202 of the fleet based on one or more characteristics of the vehicles 202. In some embodiments, the vehicle clustering circuit 136 can use one or more models (e.g., statistical models, machine learning models, artificial intelligence modes, etc.) to determine the group. In some embodiments, the vehicle clustering circuit 136 determines the group based on previously received operational data and / or operating parameters. For example, the group can be determined based on vehicles 202 that have the same or similar hardware components, such as engines, exhaust aftertreatment systems, etc. In some embodiments, the vehicle clustering circuit 136 determines the group based on an engine performance profile of the vehicles 202.The engine performance profile includes one or more engine performance values, such as an engine torque value, an engine speed value, an engine power value, etc. More precisely, the engine performance profile includes an engine power value defined over a predetermined period and / or distance, such as a maximum engine power value during the predetermined period, an average engine power value over the predetermined period, a mean engine power value over the predetermined period, etc. In these embodiments, the operating data may indicate that the engine performance profile values ​​of one or more vehicles 202 are similar (e.g., differing from each other within 10%, differing from each other within 5%, etc.). More precisely, the vehicles 202 in a group may have similar output torque values, similar engine speed values, and / or other similar engine performance profile values.In some embodiments, the vehicles 202 of a first group may have similar output torque values, similar engine speed values, and / or other similar engine performance profile values ​​as a first vehicle of the vehicle group, wherein the first vehicle previously reported a problem. In these embodiments, the first vehicle group may include the first vehicle.

[0050] In some embodiments, the vehicle clustering circuit 136 can group the vehicles 202 based on one or more predefined “bins.” Each bin or grouping defines a range of engine power values ​​(e.g., a range of engine speed values, engine torque values, etc.). The vehicle clustering circuit 136 can determine a duration for which each vehicle 202 has been operated with the engine power values ​​corresponding to each bin. The duration for which each vehicle 202 has been operated with the engine power values ​​corresponding to each bin can be based on a cumulative number of predefined time periods for each engine value within a corresponding bin. For example, the vehicle clustering circuit 136 can determine that a first vehicle 202 operates with a first set of engine power values ​​within a first engine power range (e.g.,The vehicle cluster circuit 136 can determine that the time the first vehicle 202 operated with engine power values ​​corresponding to the first bin corresponds to the first set of engine power values ​​multiplied by the duration of the specified period, and that the time the first vehicle 202 operated with engine power values ​​corresponding to the second bin corresponds to the second set of engine power values ​​multiplied by the duration of the specified period.

[0051] The vehicle clustering circuit 136 can determine a group for a vehicle 202 based on the determined duration. More precisely, the vehicle clustering circuit 136 can determine the group based on the largest value of the determined duration. For example, a first vehicle that has a first duration value in a first bin, a second duration value in a second bin, and a third duration value in a third bin can be grouped into a first group based on the fact that the first duration value is greater than the second duration value and greater than the third duration value.

[0052] In an exemplary operating scenario, a first bin defines a first engine power range, for example, a speed range between 600 revolutions per minute (rpm) and 1,000 rpm, and a second bin defines a second engine power range, for example, a speed range between 1,001 rpm and 1,500 rpm. The vehicle cluster circuit 136 can determine a first time period during which a first vehicle 202 operated at engine speeds corresponding to the first bin, and a second time period during which the first vehicle 202 operated at engine speeds corresponding to the second bin, based on the telematics data received from the vehicle data circuit 132. In response to the finding that the first time period is greater than the second time period, the vehicle cluster circuit 136 can determine that the first vehicle 202 belongs to a first group.

[0053] In another exemplary operating scenario, the vehicle cluster circuit 136 can receive a multitude of engine power values, corresponding to each vehicle in the fleet. Each engine power value within this multitude corresponds to a predefined time period. The vehicle cluster circuit 136 can group each engine power value from this multitude into either a first bin, corresponding to a first engine power range, or a second bin, corresponding to a second engine power range that differs from the first.The vehicle cluster circuit 136 can include a vehicle from the vehicle fleet in the first vehicle group if a first set of the multitude of engine power values ​​associated with the vehicle in the first bin is greater than a second set of the multitude of engine power values ​​associated with the vehicle in the second bin.

[0054] As in Fig. As shown in Figure 1, the fleet 200 includes one or more vehicles 202. In some embodiments, the fleet 200 includes more or fewer (e.g., at least one) vehicles than shown in Figure 1. Fig. Figure 1 shows one. Although the fleet is depicted as vehicles, in other embodiments the fleet includes other equipment (e.g., generators, etc.) in addition to or instead of the vehicle fleet. In still other embodiments, the fleet includes 200 pieces of off-road equipment (e.g., power generators, mining equipment, construction equipment, marine equipment, excavation equipment, etc.).

[0055] Fig. Figure 2 is a block diagram of a vehicle 202 of system 100. Fig. 1 according to an exemplary embodiment. It should be noted that the description of vehicle 202 is applicable to any vehicle in the fleet 200. In this example, vehicle 202 is a road and / or off-road vehicle. As mentioned above, however, in other embodiments the vehicle is a stationary device (e.g., a generator). In the example shown, the vehicle can be a passenger or commercial vehicle, for example, a commercial road vehicle, including but not limited to a long-haul truck (e.g., a semi-trailer truck, a school bus, a garbage truck, etc.); a non-commercial road vehicle such as a passenger car, a truck, an SUV, a crossover vehicle, a van, a minivan, or a passenger car; an off-road vehicle such as a tractor, an aircraft, a boat, a forklift, a front loader, etc.; etc.

[0056] The vehicle 202 shown includes a motor 210, an operator I / O device, one or more vehicle subsystems 235, at least one controller 300, and a telematics device 400. In some embodiments, the vehicle 202 may include more, fewer, or different components than shown in the Fig. 2. In the embodiment shown, for example, a purely electric vehicle may include more, fewer, or different sensors than a vehicle with an internal combustion engine. The vehicle 202 includes a sensor array comprising a plurality of sensors 225. The sensors 225 are coupled to the controller 300 so that the controller 300 can monitor, receive, and / or acquire data relating to the operation of the vehicle 202 (which may be referred to here as vehicle-associated operating data). In this respect, the sensor array may include one or more physical (real) or virtual sensors 225. In another exemplary embodiment, the vehicle may include a propulsion system other than an engine.For example, the vehicle's propulsion system may include any combination of an internal combustion engine, an electric motor, a battery or other power source, and / or other suitable propulsion machines. Therefore, it should be clear that although certain embodiments described herein relate to an engine, each of the embodiments described herein may be applicable to any suitable propulsion system for the vehicle 202.

[0057] As shown, one or more sensors 225 are included in the vehicle 202. The number, location, and type of sensors included in the vehicle 202 are shown for illustrative purposes only. This means that in other configurations, the number, location, and type of sensors may differ. For example, the sensors 225 may be located in or near the engine 210, in front of the engine 210, and / or behind the engine 210. It is understood that the position of the sensors may vary. The sensors 225 may be engine sensors configured to detect and / or determine one or more parameters of the engine 210 (e.g., engine operating data), such as engine torque, engine power, engine speed (e.g., in revolutions per minute), or an engine exhaust value (e.g., exhaust manifold pressure).For example, the sensors 225 may include a torque sensor configured to detect and / or determine engine torque, a pressure sensor configured to detect and / or determine exhaust manifold pressure, an engine-mounted accelerometer or noise sensor configured to detect and / or determine engine knock, a cylinder pressure sensor configured to detect and / or determine pressure within a cylinder, and / or a temperature sensor configured to detect and / or determine engine temperature 210, exhaust gases emitted by the engine, etc. The vehicle 202 may also contain additional sensors. The sensors may include sensors connected to other components of the vehicle, such as the vehicle subsystems 235.The sensors 225 can include, for example, a turbocharger speed sensor, a fuel quantity and injection rate sensor, a fuel rail pressure sensor, etc.

[0058] The sensors 225 can be real or virtual (i.e., a non-physical sensor structured as program logic in the controller 300 and / or in the telematics device 400, which makes various estimates or determinations).

[0059] For example, a motor speed sensor can be a real or virtual sensor designed to measure or otherwise acquire data, values, or information indicating the speed of the motor 210 (usually expressed in revolutions per minute). The sensor 225 is coupled to the motor (if configured as a real sensor) and is configured to send a signal to the controller 300 and / or the telematics device 400 indicating the speed of the motor 210. If the sensor is configured as a virtual sensor, at least one input from the controller 300 and / or the telematics device 400 can be used in an algorithm, model, lookup table, etc., to determine or estimate a parameter of the motor (e.g., power output, etc.). All sensors 225 described herein can be real or virtual.

[0060] The controller 300 and / or the telematics device 400 is / are coupled to the sensors 225 for communication purposes. Accordingly, the controller 300 and / or the telematics device 400 is / are structured to receive data from one or more of the sensors 225. The received data can be used by the controller 300 to control one or more components in the system 100 and / or by the controller 300 and / or the telematics device 400 for data logging purposes.

[0061] All components of the vehicle 202 can be communicatively coupled with all other components via a direct data signal or indirectly via the control unit 300 and / or the telematics device 400. For example, the data signals (in Fig. 2 (shown as dashed lines) structured so that they pass through one or more components such as the controller 300 and / or the telematics device 400.

[0062] In some embodiments, the engine 210 is an internal combustion engine (ICE), such as a spark-ignition (SI) or compression-ignition (CI) engine. Accordingly, the engine 210 includes one or more cylinders 212. The engine 210 is designed to provide mechanical energy for propelling the vehicle 202. For example, the engine 210 is designed to consume a fuel (e.g., gasoline, diesel, natural gas, hydrogen, etc.) to generate electricity.

[0063] In other embodiments, the vehicle 202 includes an electric machine such as an electric motor, a fuel cell motor, etc. Thus, the vehicle can be a hybrid vehicle (e.g., a parallel or series hybrid, a fully electric vehicle, a plug-in hybrid vehicle, etc.), a fuel cell vehicle, etc. The vehicle can also include a battery (not shown) to power the electric drive device / electric drive machine. If the vehicle includes an electric motor, the electric motor(s) can generate electrical energy from one or more electrical energy storage devices (e.g., one or more batteries that can be recharged with electrical energy, a hydrogen source for fuel cell applications, etc.).

[0064] The operator I / O device 230 can be coupled with the controller 300, allowing information to be exchanged between the controller 300 and the operator I / O device 230, with the information affecting one or more components of the Fig. 1 or provisions (described below) of the controller 300. The operator I / O device 230 enables an operator of the vehicle 202 to communicate with the controller 300 and one or more components of the vehicle 202. For example, the operator input / output device 230 may include, but is not limited to, an interactive display, a touchscreen device, one or more buttons and switches, a voice command receiver, etc. In this way, the operator input / output device 230 can provide an operator with one or more pieces of information or notifications, such as a malfunction indicator lamp (MIL), etc. The vehicle may also include a port that allows the controller 300 to connect to or pair with a diagnostic tool so that indications of problems (e.g., fault codes) and other information relating to the vehicle can be retrieved.

[0065] Vehicle subsystems 235 can include one or more components, systems, and / or devices contained within the vehicle, such as mechanically or electrically driven vehicle components. Vehicle subsystems 235 can include, but are not limited to, an HVAC system, lights, pumps, fans, etc.

[0066] In some embodiments, the vehicle subsystems 235 also include one or more components positioned downstream of the engine 210 and configured to receive the exhaust gases emitted by the engine 210. In some embodiments, the vehicle 202 includes a turbocharger configured to receive the exhaust gases emitted by the engine 210 and to compress the intake fluid (e.g., air, etc.) supplied to the engine 210. In some embodiments, the vehicle 202 includes an exhaust aftertreatment system with components for converting exhaust emissions, such as a selective catalytic reduction (SCR) catalyst, a diesel oxide oxidation catalyst (DOC), a diesel particulate filter (DPF), a diesel exhaust fluid (DEF) metering unit with a diesel exhaust fluid supply, and a variety of sensors for monitoring the exhaust aftertreatment system (e.g., a nitrogen oxide (NOx) sensor, temperature sensors, etc.).) and / or other components.

[0067] As in Fig. As shown in Figure 2, the controller 300 is operationally and communicatively coupled with various components of the vehicle 202. The controller 300 is structured to control the operation, at least partially, of each of the components of the vehicle 202 by providing one or more commands to the components. For example, the controller 300 is structured to change an operating parameter of the engine 210, the operator I / O device, and / or the vehicle subsystems 235. The controller 300 is also structured to receive information, such as data signals, from various components and / or systems of the vehicle 202. For example, the controller 300 can receive data from the sensors 225. The controller 300 is described below with reference to Fig. 3 described in more detail.

[0068] The vehicle 202 shown includes a telematics unit or telematics device 400. The telematics device 400 can be structured as any type of telematics control unit. Accordingly, the telematics device 400 may include, but is not limited to, a location determination system (e.g., a global positioning system) for tracking the location of the vehicle (e.g., latitude and longitude data, altitude data, etc.), one or more storage devices for storing the tracked data, one or more electronic processing units for processing the tracked data, and a communication interface for enabling data exchange between the telematics device 400 and one or more remote devices (e.g., a telematics device provider / manufacturer, etc.).In this respect, the communication interface can be configured as any type of mobile communication interface or protocol, including but not limited to Wi-Fi, WiMAX, Internet, radio, Bluetooth, Zigbee, satellite, radio, cellular, GSM, GPRS, LTE, and the like. The telematics device 400 can also include a communication interface for communicating with the vehicle's controller 300 202. The communication interface for communicating with the controller 300 can include any type and number of wired and wireless protocols (e.g., any standard under IEEE 802, etc.). A wired connection can include, for example, a serial cable, an optical cable, an SAE J1939 bus, a CAT5 cable, or any other form of wired connection. In contrast, a wireless connection can include the Internet, Wi-Fi, Bluetooth, Zigbee, cellular, radio, etc.In one embodiment, a control unit network bus (CAN bus), which includes any number of wired and wireless connections, enables the exchange of signals, information, and / or data between the controller 300 and the telematics device 400. In further embodiments, a local area network (LAN), a wide area network (WAN), or an external computer (for example, via the internet using an internet service provider) can provide, facilitate, and support communication between the telematics device 400 and the controller 300. In yet another embodiment, communication between the telematics device 400 and the controller 300 takes place via the Unified Diagnostic Services (UDS) protocol. All such variations are said to fall within the spirit and scope of protection of the present disclosure.

[0069] With reference to Fig. Figure 3 is a schematic diagram of the control unit 300 of vehicle 202. Fig. 2 shown according to various exemplary embodiments. As in Fig. As shown in Figure 3, the controller 300 includes a processing circuit 302, which has a processor 304 and a storage device 306, and a communication interface 316. As described herein, the controller 300 is structured to control the operation of the vehicle 202 and / or one or more of its components (e.g., the engine 210, the sensors 225, the vehicle subsystems 235, etc.).

[0070] In some embodiments, the telematics device 400 is included in the controller 300. More precisely, the telematics device 400 can be embodied in the controller 300 as any combination of hardware and / or software. In other embodiments, and as described in Fig. As shown in Figure 3, the telematics device 400 is separate from the control unit 300 and can be communicatively coupled with the control unit 300.

[0071] The at least one processing circuit 302 includes at least one processor 304 coupled to at least one storage device 306. The processing circuit 302 can be constructed or configured to execute or implement the instructions, commands and / or control operations described herein with respect to the telematics device 400.

[0072] The at least one processor 304 can be implemented as one or more single- or multi-chip processors (including chiplet designs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and / or suitable processors (e.g., other programmable logic devices, discrete hardware components, etc.) to perform at least some of the functions described herein. A processor can be a microprocessor, a group of processors, etc. A processor can also be implemented as a combination of computing devices, for example, as a plurality of microprocessors or another suitable combination of hardware components. In some embodiments, the one or more processors can be shared by several circuits.Alternatively or additionally, one or more processors can be structured to perform certain operations independently of one or more coprocessors or to execute them in a different manner. In other embodiments, two or more processors can be connected via a bus to enable independent, parallel execution of instructions, pipelined execution, or multithreaded execution of instructions. All such variations are intended to fall within the scope of protection of this disclosure.

[0073] The at least one storage device 306 (e.g., memory, storage unit, storage device) may include one or more devices (e.g., RAM, ROM, flash memory, disk storage) for storing data and / or computer code to complete or facilitate the various processes, layers, and modules described herein. For example, the storage device 306 may include dynamic random-access memory (DRAM). The storage device 306 may be communicatively connected to the processor 304 to provide the processor 304 with computer code or instructions for performing at least some of the operations described herein. Furthermore, the storage device 306 may be or include physical, persistent memory or non-volatile memory.Accordingly, the storage device can include 306 database components, object code components, script components, or any other type of information structure to support the various activities and information structures described herein.

[0074] The communication interface 316 can include any combination of wired and / or wireless interfaces (e.g., sockets, antennas, transmitters, receivers, transceivers, wired terminals) for performing data communication with various systems, devices, or networks structured to enable communication within the vehicle (e.g., between and among the vehicle components 202) and communication outside the vehicle (e.g., with the remote computer system 110). For example, the communication interface 316 can include an Ethernet card and connector for sending and receiving data over an Ethernet-based communication network and / or a Wi-Fi transceiver for communicating over a wireless communication network when it comes to communication outside the vehicle / system.The 316 communication interface can be configured to communicate over local area networks or wide area networks (e.g., the Internet) and can use a variety of communication protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, near field communication).

[0075] As shown, the communication interface 316 can enable communication with the remote computer system 110 (e.g., via the network 105), the telematics device 400, and / or one or more components of the vehicle 202, such as the engine 210, the sensors 225, and / or the vehicle subsystems 235. In some embodiments, the communication interface 316 does not enable direct communication with the remote computer system 110, and instead, the controller 300 communicates with the remote computer system 110 via the telematics device 400.

[0076] In some embodiments, the controller 300 is structured to control the operation of the sensors 225 and to exchange information with them. For example, the controller 300 may be structured to generate one or more control signals and transmit these signals to one or more sensors 225 (e.g., to acquire data, etc.). The control signals may cause one or more sensors 225 to acquire and / or detect operational data and / or transmit the operational data to the controller 300. In some embodiments, the controller 300 may be structured to estimate the sensor data (e.g., if the sensors 225 are virtual sensors). The operational data may include temperature data (e.g., fluid temperature such as exhaust gas temperature or engine oil temperature, component temperature such as engine temperature, etc.), flow data (e.g., exhaust gas flow rate, charge air flow rate, etc.), pressure data (e.g., pressure, etc.).Include engine cylinder pressure, coolant pressure, exhaust pressure, etc.), engine operating data (e.g., engine torque, engine speed, engine power, etc.) and / or other data relating to the operation of the vehicle 202.

[0077] In some embodiments, the controller 300 is, includes, or is part of a vehicle control unit, such as an engine control module (ECM), an engine control unit (ECU), or another electronic control unit structured to control one or more components of the vehicle 202. In these embodiments, the controller 300 is configured to acquire data (e.g., from the sensors 225) corresponding to one or more components of the vehicle 202, such as the engine 210, the vehicle subsystems 235, etc., and, based on the data, output an indication of a problem (e.g., a fault code) for the one or more components. For example, the controller 300 may use a mapping table that matches operating data and / or operating parameters with one or more problems.In response to the detection that the operating data and / or operating parameters correspond to a problem, the controller 300 can output a description of the problem (e.g., via the communication interface 316). In some embodiments, the controller 300 provides the description of the problem to the remote computer system 110 and / or the telematics device 400.

[0078] With reference to Fig. Figure 4 is a schematic diagram of the telematics device 400 of vehicle 202. Fig. 2 according to an exemplary embodiment. As shown in Fig. As shown in Figure 4, the telematics device 400 includes a processing circuit 402 with a processor 404 and a storage device 406, an access circuit 422, a data logging circuit 424, an event monitoring circuit 426, and a communication interface 416. As described herein, the telematics device 400 is structured to log data about the operation of the vehicle 202 and / or one or more of its components (e.g., the engine 210, the sensors 225, the vehicle subsystems 235, etc.). As described in more detail herein, the buffer can be part of the storage device 406 in some embodiments.

[0079] In some embodiments, the access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426 are implemented as any combination of hardware and / or software. For example, the access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426 can be implemented as hardware, software, and / or any combination thereof, such as machine-readable or computer-readable media that store instructions.

[0080] The processing circuit 402 includes the processor 404 and the storage device 406. The processing circuit 402 can be structured or configured to execute or implement the instructions, commands, and / or control operations described herein with respect to the access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426. The illustrated configuration represents the access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426 embodied as machine-readable or computer-readable media that store instructions. However, as mentioned above, this representation is not to be construed as a limitation, since the present disclosure provides for other embodiments in which the access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426 are configured as a hardware unit.All such combinations and variations shall fall within the scope of protection of the present disclosure.

[0081] The at least one processor 404 can be implemented as one or more single-chip or multi-chip processors and / or chiplet processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and / or suitable processors (e.g., other programmable logic devices, separate hardware components, etc.) to perform the functions described herein. A processor can be a microprocessor, a group of processors, etc. A processor can also be implemented as a combination of computing devices, for example, as a plurality of microprocessors or another suitable combination of hardware components. In some embodiments, the one or more processors can be shared by several circuits (e.g.,The access circuit 422, the data logging circuit 424, and / or the event monitoring circuit 426 may comprise or otherwise share the same processor, which in some embodiments can execute instructions stored in different memory areas or accessed in other ways. Alternatively or additionally, the one or more processors may be structured to perform certain operations independently of one or more coprocessors. In other embodiments, two or more processors may be connected via a bus to enable independent, parallel execution of instructions, pipelined execution, or multithreaded execution of instructions. All such variations are intended to fall within the scope of protection of this disclosure.

[0082] The at least one storage device 406 (e.g., memory, storage unit, storage device) may include one or more devices (e.g., RAM, ROM, flash memory, disk storage) for storing data and / or computer code to complete or facilitate the various processes, layers, and modules described herein. For example, the storage device 406 may include dynamic random-access memory (DRAM). The storage device 406 may be communicatively connected to the processor 404 to provide the processor 404 with computer code or instructions for performing at least some of the operations described herein. Furthermore, the storage device 406 may be or include physical, persistent memory or non-volatile memory.Accordingly, the storage device can include database components, object code components, script components, or any other type of information structure to support the various activities and information structures described herein.

[0083] The communication interface 416 can include any combination of wired and / or wireless interfaces (e.g., sockets, antennas, transmitters, receivers, transceivers, wired terminals) for performing data communication with various systems, devices, or networks structured to enable communication within the vehicle (e.g., between and among the vehicle components 202) and communication outside the vehicle (e.g., with the remote computer system 110). For example, the communication interface 416 can include an Ethernet card and connector for sending and receiving data over an Ethernet-based communication network and / or a Wi-Fi transceiver for communicating over a wireless communication network when it comes to communication outside the vehicle / system.The 416 communication interface can be configured to communicate over local area networks or wide area networks (e.g., the Internet) and can use a variety of communication protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, near field communication).

[0084] As shown, the communication interface 416 can enable communication with the remote computer system 110 (e.g., via the network 105), the controller 300, and / or one or more components of the vehicle 202, such as the sensors 225. In some embodiments, the communication interface 416 enables communication between the controller 300 and the remote computer system 110.

[0085] In some embodiments, the telematics device 400 is structured to control the operation of the sensors 225 and to exchange information with them. For example, the telematics device 400 may be structured to generate one or more control signals and transmit these signals to one or more sensors 225 (e.g., to acquire data, etc.). The control signals may cause the one or more sensors 225 to acquire and / or detect operational data and / or to provide the operational data to the telematics device 400. In some embodiments, the telematics device 400 may be structured to estimate the operational data (e.g., if the sensors 225 are virtual sensors).

[0086] The access circuit 422 is structured to receive access information from the remote computer system 110 (e.g., via the network 105 and / or the communication interface 416). In some embodiments, the access circuit 422 is configured to determine an access level based on the access information. As described above, the access information can define the access level. For example, in response to the access level determination, the access circuit 422 can determine that the telematics device 400 can receive information (e.g., operating data, operating parameters, etc.) from a predefined group of one or more sensors and / or a predefined group of one or more components of the vehicle 202.Advantageously, the access level limits data collection to optimize the type and amount of data captured by the Telematics Device 400, thereby reducing the processing power required to capture the data and the storage requirements for storing the data. Furthermore, as described herein, the access level defines a data type to be captured that corresponds to a specific problem, such as an error code, so that the data captured by the Telematics Device 400 is relevant to, or likely to be relevant to, that specific problem.

[0087] In some embodiments, the access circuit 422 may not receive access information from the remote computer system. In these embodiments, if the access circuit 422 attempts to determine the access level, it may find that the access level is unknown. In some embodiments, if the access circuit 422 has not received access information from the remote computer system, it may send a request for access information to the remote computer system 110. In some embodiments, if the access circuit 422 cannot determine the access level, it advantageously prevents the telematics device 400 from acquiring and / or logging data, thereby reducing the processing power required for data acquisition and the amount of memory required for storing the logged data.

[0088] The data logging circuit 424 is structured to log the data received from the telematics device 400. In some embodiments, the data logging circuit 424 is structured to selectively log data corresponding to one or more vehicle problems (e.g., one or more fault codes).

[0089] In some embodiments, the data logging circuit 424 is structured to store logged data in a buffer. In some embodiments, the buffer may be part of the storage device 406. In other embodiments, the buffer may be a separate storage device, and in some implementations, the buffer storage device may be a storage device of the data logging circuit 424. As described above, the buffer may store the logged data for a predetermined period (e.g., 1 hour, 1 day, etc.) and / or based on a predetermined file size (e.g., in megabytes or gigabytes, etc.).

[0090] The event monitoring circuit 426 is structured to receive a triggering event, such as a problem or other predefined condition (e.g., a problem described herein), from the controller 300. As described above, the controller 300 can trigger and output a problem indication in response to the detection of a vehicle problem (e.g., via the sensors 225). The event monitoring circuit 426 is structured to receive the problem indication. In some embodiments, the event monitoring circuit 426 is structured to provide the logged data (e.g., data stored in the buffer) to the remote computer system 110 in response to receiving the problem indication (e.g., via the network 105 and / or the communication interface 416).

[0091] In some embodiments, the triggering event corresponds to the receipt of a specific problem or problems from a multitude of problems. In these embodiments, the access information includes information indicating that one or more problems from the multitude of problems are the specific problem(s). The event monitoring circuit 426 is structured to receive all information about a problem output by the controller 300 and compares the received information about the problem with the one or more problems indicated by the access information, or more precisely, with one or more vehicle problems associated with one or more fault codes.In response to the determination that the received problem is identical to one or more problems indicated by the access information, event monitor circuit 426 may provide the logged data to remote computer system 110. However, in response to the determination that the received problem is not in the specified list, event monitor circuit 426 may not provide the logged data to remote computer system 110, thus preventing the transmission of data that is unlikely to be relevant to the one or more problems indicated by the access information (i.e., a basis or cause of the problem).

[0092] With reference to the Fig. Sections 5 and 6 show methods for logging data according to various exemplary embodiments. In particular, the following refers to Fig. The 5 methods shown relate to an automated telematics data logging process for a fleet of 200 vehicles 202. Advantageously, the remote computer system 110 captures telematics data from a selected group of vehicles 202. The in Fig. Method 600, as shown, relates to an automated telematics data logging process for a single vehicle 202. Advantageously, the telematics device 400 automatically performs the data logging process when a problem (e.g., an error code) is detected that corresponds to a common problem.

[0093] Fig. Figure 5 is a flowchart of a procedure 500 for enabling the automatic logging of telematics data according to an exemplary embodiment. As in Fig. As shown in Figure 5, the method 500 can be executed by any combination of the remote computer system 110, the telematics device 400, and / or the controller 300. In some embodiments, if the telematics device 400 or parts thereof are embodied in the controller 300, the steps shown as being performed by the telematics device 400 are performed by the controller 300. The method 500 relates to a cloud-based method for logging data from one or more vehicles 202 of the fleet 200. In some embodiments, the operations of the method 500 can be performed in a different order than shown in Figure 5. Fig. 5 shown. In some embodiments, the method may include 500 more or fewer operations than shown. Fig. Figure 5 shows that in some embodiments, the operations of method 500 can be performed simultaneously, partially simultaneously, or sequentially. It is understood that while method 500 refers to a single vehicle 202 of the fleet 200, method 500 can be performed by any number of vehicles 202 of the fleet 200.

[0094] In process 502, the control unit 300 detects a vehicle problem and transmits information about the problem to the telematics device. In one embodiment, the problem information is represented as an error code (or diagnostic error code, fault code, etc.). In the explanation of this procedure, the information is described as an error code. However, it is understood that in other embodiments, information other than that described herein may be used (e.g., operating conditions that do not comply with one or more desired operating ranges / values / thresholds, etc.).

[0095] In process 504, the telematics device 400 receives the fault code. In process 506, the telematics device 400 provides the remote computer system 110 with information about the vehicle problem as defined by the fault code. In process 508, the remote computer system 110 receives the fault code. In some embodiments, the remote computer system can receive the fault code from one or more vehicles 202 of the fleet 200 in process 508. For example, the remote computer system 110 can receive the fault code from at least one initial vehicle of the fleet 200.

[0096] In process 510, the remote computer system 110 compares the received fault code with information stored in the problem database. By comparing the fault code with information stored in the problem database, the remote computer system 110 can determine whether the fault code is a common fault code. For example, the problem database can store a frequency value for each fault code within a large number of fault codes. In response to the finding that the frequency value of the received fault code is greater than a predefined frequency threshold, the remote computer system 110 can determine that the received fault code is a common fault code. As described herein, the granularity of the frequency determination can be further restricted by characteristics surrounding the fault code, such as: based on vehicle type, engine type (e.g.,certain engine models), specifically for a fleet regardless of the engine or vehicle types contained therein, and so on.

[0097] In process 512, the remote computer system 110 is configured to cluster one or more vehicles 202 from the fleet 200. More specifically, the remote computer system 110 is configured to identify a group of one or more vehicles 202 and to collect telematics data from the vehicle group 202, thus capturing a sample of the telematics data from the fleet 200. As described above, the remote computer system 110 can use one or more models (e.g., statistical models, machine learning models, etc.) to cluster the one or more vehicles 202. Capturing only a sample of the telematics data advantageously reduces the processing power and storage required to receive and store the telematics data.In some embodiments, operation 512 is executed in response to the finding that the error code received in operation 514 is a common error code.

[0098] In process 514, the remote computer system 110 generates access information and provides it to the telematics device 400. As described above, the access information can define an access level for the telematics device 400. In some embodiments, the access information can also specify a data type to be logged by the telematics device 400. For example, the access information can define one or more vehicle problems (and / or corresponding fault codes) that correspond to a specific data type to be logged by the telematics device 400. In some embodiments, the access information can also specify an event type to be monitored by the telematics device 400. For example, the access information can define one or more fault codes to be monitored by the telematics device 400.

[0099] In process 516, the telematics device 400 receives the access information. In process 518, the telematics device 400 executes the procedure 700, which is described herein with regard to Fig. 7 is described. In process 520, the controller 300 provides an error code to the telematics device 400. In process 522, the telematics device provides the telematics data to the remote computer system 110. In some embodiments, processes 514, 516, 520, and / or 522 can be executed as part of process 700.

[0100] In process 524, the remote computer system 110 receives telematics data from the remote computer system 110. In process 526, the remote computer system 110 provides the telematics data to a user device such as a PC, laptop, smartphone, etc.

[0101] Fig. Figure 6 is a flowchart of a procedure for activating the automatic logging of telematics data according to a further exemplary embodiment. As in Fig. As shown in Figure 6, the method 600 can be executed by any combination of the remote computer system 110, the telematics device 400, and / or the controller 300. In some embodiments, if the telematics device 400 or parts thereof are embodied in the controller 300, the steps shown to be performed by the telematics device 400 are performed by the controller 300. The method 600 relates to a local procedure for logging data corresponding to a vehicle 202 of the fleet 200. In some embodiments, the operations of the method 600 can be performed in a different order than shown in Figure 6. Fig. Figure 6 shows that in some embodiments, the method may include 600 more or fewer operations than shown. Fig. Figure 6 shows that in some embodiments, the operations of Method 600 can be performed simultaneously, partially simultaneously, or sequentially. Similar to the description of Method 500, as described herein, the specification of the problem is embodied as an error code (or diagnostic error code, fault code, etc.). In the explanation of this method, the specification is described as an error code. However, it is understood that in other embodiments, specifications other than those described herein may be used (e.g., operating conditions that do not comply with one or more desired operating ranges / values / thresholds, etc.).

[0102] In Operation 602, the remote computer system 110 provides a problem record to the telematics device. The problem record may contain the same or similar information as the information stored in the problem database associated with the problem tracking circuit 134 (or a subset thereof). For example, the problem record may include a list of problems and corresponding fault codes, a list of fault codes, and / or a frequency value for each of the fault codes. In Operation 604, the telematics device 400 receives the problem record.

[0103] In process 606, the telematics device 400 executes the procedure 700, which is described herein in relation to Fig. 7 is described. In process 608, the controller 300 provides an error code to the telematics device 400. In process 610, the telematics device 400 provides the telematics data to the remote computer system 110. In some embodiments, process 608 and / or process 610 can be executed as part of process 700.

[0104] In process 612, the remote computer system 110 receives telematics data from the remote computer system 110. In process 614, the remote computer system 110 provides the telematics data to a user device such as a PC, laptop, smartphone, etc.

[0105] Fig. 7 A flowchart of a method 700 for the automatic logging of telematics data according to an exemplary embodiment. In the Fig. In the embodiment shown in Figure 7, the method 700 can be executed by the telematics device 400. In some embodiments, when the telematics device 400 is embodied in the controller 300, the method 700 can be executed by the controller 300. In some embodiments, the operations of the method 700 can be performed in a different order than shown in Figure 7. Fig. Figure 7 shows that in some embodiments, the method may include 700 more or fewer operations than shown in Figure 700. Fig. Figure 7 shows that in some embodiments, the operations of Method 700 can be performed simultaneously, partially simultaneously, or sequentially. Similar to the description of Method 500, as described herein, the specification of the problem is embodied as an error code (or diagnostic error code, fault code, etc.). In the explanation of this method, the specification is described as an error code. However, it is understood that in other embodiments, specifications other than those described herein may be used (e.g., operating conditions that do not comply with one or more desired operating ranges / values / thresholds, etc.).

[0106] In process 702, an activation condition is received. The activation condition refers to a control signal received by the telematics device 400 and / or a predefined condition detected and / or determined by the telematics device 400. In this way, the telematics device 400 starts the process 700 when the activation condition is met. In some embodiments, the predefined condition includes a power-on event of the telematics device. More precisely, the activation condition is met when the telematics device detects that the telematics device 400 has been switched on. In other embodiments, the activation condition is met when the telematics device 400 receives a control signal from the controller 300 and / or the remote computer system 110. In some embodiments, the predefined condition is the activation condition.This means that if the predefined condition is detected and / or determined by the telematics device 400, the activation condition is met.

[0107] In process 704, the telematics device 400 determines whether access information is stored by the telematics device 400 (e.g., the storage device 406).

[0108] In response to the finding that the access information has been sorted by telematics device 400, the telematics device determines an access level based on the stored access information. In response to the determination of the access level, procedure 700 proceeds to operation 710. In response to the finding that the access information has not been sorted by telematics device 400, procedure 700 proceeds to operation 706.

[0109] In process 706, the telematics device 400 requests access information from the remote computer system 110 (e.g., the "cloud"). In some embodiments, the remote computer system 110 automatically provides the access information to the telematics device 400 (e.g., without a request from the telematics device 400). In some embodiments, the remote computer system 110 can provide the access information to the telematics device 400 after it has been determined that the telematics device 400 is on board a first vehicle of a vehicle group determined by the vehicle cluster circuit 136 (e.g., as process 512 of Fig. 5).

[0110] In operation 708, the telematics device 400 determines whether access information has been received from the remote computer system 110. Upon determining that the access information has not been received, procedure 700 proceeds to operation 748 (as shown by element "A"). Upon determining that the access information has been received, procedure 700 proceeds to operation 710.

[0111] In process 710, the telematics device 400 determines whether an access level defined by the access information is above a threshold access level (e.g., an "access threshold"). In some embodiments, the access level includes a plurality of access levels defined by one or more quantitative values ​​(e.g., between 0 and 10, between 0 and 100, etc.), and the threshold access level is a predefined value (e.g., 8, 80, etc.). In other embodiments, the access levels include one or more relative or qualitative descriptors, such as "high," "medium," "low," etc., and the threshold access level is a predefined relative descriptor, such as "medium." In each of the embodiments described above, one or more components of the vehicle 202, such as the sensors 225, have a corresponding access level.The access level determined by the telematics device 400 enables the telematics device 400 to acquire data from sensors 225 and / or other components of the vehicle 202 that have corresponding access levels equal to or lower than the determined access level. Advantageously, the access level limits data acquisition to optimize the type and amount of data acquired by the telematics device 400 to data that is relevant or likely to be relevant to a fault code, such as the fault code specified by the access information. In this way, the access level reduces the processing power required to acquire the telematics data and decreases the memory required to store the telematics data. For example, the access level can be a high access level and the threshold access level a medium access level.The telematics device 400 can determine that the access level defined by the access information is higher than the threshold access level because the access level is relatively higher than the threshold of the "medium" access level. In an exemplary embodiment, the access level defined by the access information can indicate that the telematics device 400 can acquire data from sensors 225 and / or other components of the vehicle 202 that have corresponding access levels equal to or lower than the threshold access level and / or the determined access level. The telematics device 400 may not acquire data from sensors 225 and / or other components of the vehicle 202 that have corresponding access levels higher than the threshold access level and / or the determined access level.

[0112] In some embodiments, during operation 710, the telematics device 400 determines a data type to be accessed based on the access information. As described above, the access information can define one or more data acquisition parameters, such as a data type. In some embodiments, the data type defined by the access information can correspond to one or more error codes. For example, the access information can define an error code that corresponds to a data type.

[0113] In operation 712, the telematics device 400 begins logging data. In some embodiments, the logged data corresponds to the data type determined in operation 710. For example, the telematics device 400 may log data that corresponds to an error code specified by the access information, so that data that is unlikely to correspond to the error code specified by the access information is not logged, thereby reducing the processing power and memory usage of the telematics device 400. In some embodiments, the logged data is one set of telematics data (e.g., a first set of telematics data). The telematics device 400 may discard (or not log) another telematics data set (e.g., a second telematics data set) that does not correspond to the error code. In some embodiments, the logged data is stored in the buffer (e.g.,(the storage device 306 and / or the storage device 406). Advantageously, the logged data is stored in the buffer before a triggering event occurs, so that the logged data corresponds to the data that occurred immediately before (before a predefined time interval, for example, 45 minutes, 1 hour, etc.) the occurrence of the triggering event (e.g., occurrence of a problem), so that the data is more likely to be the most relevant data for a problem.

[0114] In process 714, the telematics device 400 monitors for an error code. As described above, the telematics devices can monitor the controller 300 for one or more specific error codes from a multitude of error codes.

[0115] The access information includes details indicating that one or more error codes from the multitude of possible error codes are the specific error code(s). The telematics device 400 monitors the controller 300 for one or more specific error codes by comparing an error code received from the controller 300 with a list of one or more error codes specified in the access information.

[0116] In operation 716, the telematics device 400 determines whether an error code has been detected or received by the controller 300 and / or an electronic control unit. If the specific error code indicated by the access information is not detected or received, operation 700 can proceed to operation 718. If the specific error code indicated by the access information is detected or received, operation 700 can proceed to operation 722.

[0117] In step 718, the telematics device 400 compares the data logged in step 712 with a threshold. In some embodiments, the threshold may be a file size threshold measured in megabytes, gigabytes, etc. In other embodiments, the threshold may be a timestamp threshold (e.g., 1 hour, 1 day, 1 week, etc.). Upon determining that the logged data is larger than the file size threshold and / or that the logged data includes timestamps larger than the timestamp threshold, step 700 may proceed to step 720. Upon determining that the logged data is less than or equal to the file size threshold and / or that the logged data includes timestamps less than or equal to the timestamp threshold, step 700 may proceed to step 712.

[0118] In process 720, the telematics device 400 deletes the oldest data until the logged data falls below the threshold. For example, the telematics device 400 can delete logged data corresponding to the oldest timestamps until the file size of the logged data is below the file size threshold. In another example, the telematics device 400 can delete logged data corresponding to the oldest timestamps until the oldest logged data has a corresponding timestamp that is less than or equal to the timestamp threshold.

[0119] In operation 722, the telematics device 400 sends the available logged data to the remote computer system 110. Advantageously, the logged data can include data that matches or is likely to match the error code and data that falls within a threshold time period (e.g., less than or equal to the threshold timestamp) and / or within a threshold file size (e.g., less than or equal to the file size threshold), thus reducing the processing power, storage capacity, and / or bandwidth required to transmit the logged data to the remote computer system 110.

[0120] During operation 724, the telematics device 400 increments an event counter. The event counter indicates how often the error code was received and / or detected by the telematics device 400 during operation 716. In some embodiments, the telematics device selectively increments the event counter when it is determined that the received error code matches the error code specified by the access information.

[0121] In Operation 726, the telematics device 400 starts a timer (e.g., a data logging timer). In some embodiments, the timer refers to a software-based timing tool that counts up or down to a predetermined time value and expires when the timer reaches the predetermined time value (when counting up) or expires when the time reaches zero (when counting down). As described above, the access information includes information specifying a data logging duration. The telematics device 400 can determine the predetermined time value based on the data logging duration. In some embodiments, the telematics device 400 logs additional data while the timer is active (e.g., as described above in Operation 712, Operation 714, Operation 716, Operation 718, and Operation 720). The additional data may be of the same type as determined in Operation 710.In some embodiments, the telematics device 400 can create a new log file in response to the detection of a trigger event (e.g., as described above in relation to Operation 716).

[0122] In process 728, the telematics device 400 determines whether a stop event has been detected. In some embodiments, the stop event includes the detection and / or receipt of an error code. In some embodiments, the error code may be the same error code described in process 710, process 712, and / or process 714. In other embodiments, the error code is a different error code. In some embodiments, the stop event is based on a timer, such as the timer described in process 726. More precisely, the telematics device 400 may determine that the stop event has occurred in response to the detection that the timer started in process 726 has expired.

[0123] In some embodiments, the stop event is a command received from the remote computer system 110. In some embodiments, the command can be generated by the remote computer system 110 in response to receiving user input. In some embodiments, the command can be generated by the remote computer system 110 in response to receiving a user-defined trigger. The user-defined trigger can include, for example, the detection and / or receipt of an error code, the detection and / or receipt of an indication that an error code has changed from active to inactive, a user-defined duration, and / or other user-defined triggers. In response to the detection that the logging timer has not expired, procedure 700 proceeds to operation 730. In response to the detection that the logging timer has expired, procedure 700 proceeds to operation 740.In response to the finding that the stop event was not detected, procedure 700 continues with operation 730. In response to the finding that the stop event was detected, procedure 700 continues with operation 740.

[0124] In operation 730, the telematics device 400 determines whether a new log file has been created. For example, the telematics device 400 is configured to create a new log file in response to the detection of the trigger event (e.g., in operation 716) while the logging timer is active. Upon determining that a new log file has been created, operation 700 proceeds to operation 732. Upon determining that no new log file has been created, operation 700 returns to operation 726. In operation 732, the telematics device 400 sends the new log file to the remote computer system 110.

[0125] In process 740, the telematics device 400 stops logging data. In process 742, the telematics device 400 sends a log file to the remote computer system 110. In some embodiments, the log file may contain data stored in the buffer.

[0126] In process 744, the telematics device 400 compares the event counter value with an event counter threshold. Upon determining that the event counter is greater than the event counter threshold, process 700 proceeds to process 746. Upon determining that the event counter is less than or equal to the event counter threshold, process 700 proceeds to process 748 and terminates.

[0127] In Operation 746, the telematics device 400 is configured to stop logging data. In response to the cessation of data logging, the telematics device 400 can delete the access information, thus preventing the telematics device 400 from logging any further data. Advantageously, stopping data logging prevents the telematics device 400 from logging any additional telematics data, thereby reducing the processing power and memory requirements of the telematics device 400. In response to the termination of the data logging configuration, Operation 700 proceeds to Operation 748 and terminates.

[0128] In an exemplary operational implementation, the remote computer system 110 can determine a problem and / or fault code of interest (e.g., via the problem tracking circuit 134 and / or user input). For example, the remote computer system 110 can determine that an initial problem is of interest. In response to the determination that the initial problem is of interest, the remote computer system 110 can determine an initial group of vehicles 202 from which telematics data is to be received (e.g., via the vehicle cluster circuit 136). The remote computer system 110 can generate an access information data packet for the vehicles 202 in the initial group. The access information can define an access level for the telematics device 400 of each vehicle 202, a data type, and / or a logging duration.In one exemplary embodiment, the logging period can define a four-day period within the next two weeks during which the telematics device 400 of a vehicle 202 is to log data. In some embodiments, the data is logged automatically by the telematics device (e.g., without input from a user or the remote computer system) for a vehicle 202 of the fleet 200 in which the first problem occurs. The data type can define one or more operational data types or operational parameters that the telematics device 400 of each vehicle 202 is to log. The remote computer system 110 can receive telematics data from one or more vehicles 202 in the first group that have detected the first problem. Advantageously, the received telematics data includes data of the defined data type and data from the defined logging period.

[0129] As used herein, the terms “about”, “approximately”, “essentially”, and similar terms are to be interpreted broadly, in accordance with the usual and accepted usage by the average person skilled in the art in the field to which the subject matter of this disclosure relates. It should be clear to the person skilled in the art reading this disclosure that these terms are intended to enable a description of certain described and claimed features without limiting the scope of those features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insignificant or unimportant modifications or changes to the described and claimed subject matter are to be considered to be within the scope of the disclosure, as specified in the accompanying claims.

[0130] It should be noted that the term "exemplary" and variations thereof, as used herein to describe different embodiments, are intended to indicate that these embodiments are possible examples, representations or illustrations of possible embodiments (and that these terms are not intended to imply that these embodiments are necessarily extraordinary or superlative examples).

[0131] The term "coupled" and variations thereof as used here means the connection of two elements directly or indirectly. Such a connection may be stationary (e.g., permanent or fixed) or movable (e.g., removable or detachable). Such a connection may be achieved by directly coupling the two elements, by coupling the two elements using one or more separate intermediate elements, or by coupling the two elements using an intermediate element formed integrally as a single, unified body with one of the two elements. When "coupled" or variations thereof are modified by an additional term (e.g., directly coupled), the general definition of "coupled" provided above is modified by the specific meaning of the additional term (e.g.,"Directly coupled" means the connection of two elements without a separate intermediary element, which leads to a narrower definition than the general definition of "coupled" provided above. Such coupling can be mechanical, electrical, or fluidic. For example, circuit A can be "coupled" by communication with circuit B, meaning that circuit A communicates directly with circuit B (i.e., without an intermediary) or indirectly with circuit B (e.g., via one or more intermediaries).

[0132] The references to the positions of elements contained herein (e.g., "above", "below", "above") are used solely to describe the orientation of the various elements in the FIGURES. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and it is intended that such differences are covered by the present disclosure.

[0133] Although in Fig. Since Figures 1 and 3 to 4 show different circuits with special functionality, it is understood that the remote computer system 110, the controller 300, and / or the telematics device 400 can include any number of circuits to complete the functions described herein. For example, the activities and functions of the exhaust aftertreatment control circuit can be combined in several circuits or as a single circuit. Additional circuits with additional functionality may also be included. Furthermore, the remote computer system 110, the controller 300, and / or the telematics device 400 can also control other activities that go beyond the scope of this disclosure.

[0134] As mentioned above and in one configuration, the “circuits” can be stored in a machine-readable medium for execution by various types of processors, such as the 114 processor. Fig. 1, the 304 processor from Fig. 2 and / or the processor 404 Fig. 4. An executable code can, for example, comprise one or more physical or logical blocks of computer instructions, which may be organized, for example, as an object, procedure, or function. However, the executable files do not need to be physically located together; they can comprise different instructions stored in different locations, which, when logically connected, comprise the circuit and achieve the specified purpose for the circuit. In fact, a circuit of computer-readable program code can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and multiple storage devices.

[0135] Although the term "processor" is briefly defined above, the terms "processor" and "processing circuit" are to be interpreted broadly. In some embodiments, the one or more processors may be located outside the device (e.g., on board the vehicle control unit), or the one or more processors may be a remote processor (e.g., a cloud-based processor) or be contained within one. In this respect, a particular circuit or its components may be located locally (e.g., as part of a local server, a local computer system, etc.) or remotely (e.g., as part of a remote server such as a cloud-based server). To this end, a "circuit" described herein may have components distributed across one or more locations.

[0136] Embodiments within the scope of this disclosure include program products comprising computer- or machine-readable media for carrying or storing computer- or machine-executable instructions or data structures. Such machine-readable media can be any available media accessible to a computer. The computer-readable medium can be a physical computer-readable storage medium that stores the computer-readable program code. The computer-readable storage medium may be, for example, but not exclusively, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination thereof.More specific examples of a computer-readable medium include, but are not limited to, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage medium, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. For the purposes of this document, a computer-readable storage medium can be any physical medium capable of containing and / or storing computer-readable program code for use by and / or in conjunction with an instruction execution system, device, or apparatus.Machine-executable instructions include, for example, instructions and data that cause a computer or processing machine to perform a specific function or group of functions.

[0137] The computer-readable medium can also be a computer-readable signaling medium. A computer-readable signaling medium can include a propagated data signal containing computer-readable program code, for example, in the baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including, but not limited to, electrical, electromagnetic, magnetic, optical, or any suitable combination thereof. A computer-readable signaling medium can be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport computer-readable program code for use by or in conjunction with an instruction execution system, device, or apparatus.Computer-readable program code embodied on a computer-readable signaling medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cables, radio frequency (RF) or the like, or any suitable combination thereof.

[0138] In one embodiment, the computer-readable medium can comprise a combination of one or more computer-readable storage media and one or more computer-readable signaling media. For example, computer-readable program code can be propagated both as an electromagnetic signal via a fiber optic cable for execution by a processor and stored on a RAM storage device for execution by the processor.

[0139] Computer-readable program code for performing operations for aspects of the present disclosure may be written in any combination of one or more other programming languages, including an object-oriented programming language such as Java, Smalltalk, C++, or the like, and conventional procedural programming languages ​​such as the programming language "C" or similar programming languages. The computer-readable program code may be executed entirely on a local computer, partially on the local computer, as a standalone computer-readable package, partially on the local computer and partially on a remote computer, etc.In the latter scenario, the remote computer can be connected to the local computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, via the Internet using an Internet service provider).

[0140] The program code may also be stored in a computer-readable medium capable of instructing a computer, other programmable data processing device, or other apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce a manufactured item that includes instructions implementing, as a block or blocks, the function / action specified in the schematic flowcharts and / or schematic block diagrams.

[0141] Although the figures and description may illustrate a particular sequence of process steps, the sequence of such steps may differ from those shown and described, unless otherwise stated above. Furthermore, two or more steps may be performed simultaneously or partially simultaneously, unless otherwise stated above. Such variations may depend, for example, on the software and hardware systems chosen, as well as on the designer's choice. All such variations are within the scope of disclosure.

[0142] It is important to note that the design and arrangement of the device and system, as shown in the various exemplary embodiments, are for illustrative purposes only. Furthermore, any element disclosed in one embodiment can be integrated into or used in any other embodiment disclosed herein. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] US Patent Application No. 63 / 464,344

[0001]

Claims

[1] A method for automatically logging telematics data for a vehicle fleet, the method comprising: Receiving an indication of a first error code from a first vehicle of the vehicle fleet by a processing circuit of a computer system; Comparing, by the processing circuit, the first error code with a list of error codes stored in a problem database, wherein the problem database stores a frequency value for each error code in the list of error codes; identifying, by the processing circuit, that the first error code is a frequent error code in response to the frequency value of the first error code being at or above a predetermined threshold; Generating a first vehicle group by the processing circuit, wherein the first vehicle group comprises one or more vehicles of the vehicle fleet; generating, by the processing circuit, access information that causes a telematics device to log telematics data; Providing the access information by the processing circuit to each vehicle of the first vehicle group, the access information being structured to cause each vehicle of the first vehicle group to generate telematics data; Receiving the telematics data from one or more vehicles of the first vehicle group by the processing circuit; and Providing the telematics data to a user device. [2] The method of claim 1, wherein generating the first vehicle group comprises: Receiving a plurality of engine power values ​​corresponding to each vehicle in the vehicle fleet, each engine power value corresponding to the plurality of engine power values ​​in a predetermined period of time; Including each engine power value of the plurality of engine power values ​​in one of a first bin corresponding to a first engine power range or a second bin corresponding to a second engine power range different from the first engine power range for each vehicle in the vehicle fleet; and Including a vehicle of the vehicle fleet in the first vehicle group in response to a first set of the plurality of engine power values ​​associated with the vehicle in the first bin being greater than a second set of the plurality of engine power values ​​associated with the vehicle in the second bin. [3] The method of claim 1, further comprising receiving by the processing circuitry the frequency value of each error code in the list of error codes, the frequency value being based on a number of times the processing circuitry received an indication of each error code in the list of error codes within a predetermined period of time. [4] The method of claim 1, further comprising: Receiving a request for access information from the telematics device by the processing circuit; and Generating the access information by the processing circuit in response to receiving the request. [5] The method of claim 4, wherein the access information is generated in response to identifying the first error code as a common error code. [6] The method of claim 1, further comprising providing a stop command by the processing circuit to each vehicle of the first vehicle group, the stop command structured to prevent each vehicle of the first vehicle group from generating the telematics data, the stop command being provided in response to at least one of the following events: Receiving a second fault code from one or more vehicles in the first vehicle group that is different from the first fault code; Receiving an indication from one or more vehicles in the first vehicle group that the first fault code has changed from an active state to an inactive state; or Receiving an indication that a predefined period of time has elapsed. [7] The method of claim 1, further comprising: Receiving a second error code from a second vehicle of the vehicle fleet by the processing circuit; Comparing the second error code with the list of error codes by the processing circuit; determining, by the processing circuit, that the second error code is another frequent error code in response to the frequency value of the second error code being at or above the predetermined threshold; Generating a second vehicle group by the processing circuit, wherein the second vehicle group comprises one or more vehicles of the vehicle fleet that are different from the first vehicle group and include at least the second vehicle; and Providing the access information for the second vehicle group by the processing circuit. [8] A non-transitory, computer-readable medium that stores instructions that, when executed by one or more processors of a computer system, cause the computer system to perform the following operations: Receiving access information from a remote computer system, the access information comprising information indicating a data type and a logging duration; Logging telematics data corresponding to the data type, where logging the telematics data includes: Causing one or more sensors to provide the telematics data to the computer system; Storing a first telematics data record in a buffer for the duration of the logging; Monitor for an initial problem; in response to the failure to detect the first problem, causing the buffer to delete a portion of the first telematics data record; and In response to detecting the first problem, provide the telematics data to the remote computer system. [9] The non-transitory computer-readable medium of claim 8, wherein the instructions, when executed by one or more processors, further cause the following operations: Comparing a data size of the first telematics data set with a data size threshold; and in response to the data size of the first telematics data record being at or above the data size threshold, causing the buffer to delete the portion of the first telematics data record. [10] The non-transitory computer-readable medium of claim 8, wherein the instructions, when executed by one or more processors, further cause the following actions: Comparing one or more timestamps associated with the first telematics data record with a timestamp threshold; and in response to at least one timestamp of the one or more timestamps associated with the first telematics data record being at or above the timestamp threshold, causing the buffer to delete the portion of the first telematics data record. [11] The non-transitory computer-readable medium of claim 8, wherein the instructions, when executed by one or more processors, further cause operations including discarding a second telematics data record in response to the second telematics data record corresponding to a different data type, the second telematics data record being different from the first telematics data record. [12] The non-transitory computer-readable medium of claim 8, wherein the instructions, when executed by one or more processors, further cause operations that include receiving from the remote computer system a list of problems and a frequency value for each problem in the list of problems, wherein the first problem in the list of problems has a first frequency value that is at or above a predefined threshold. [13] The non-transitory computer-readable medium of claim 12, wherein the instructions, when executed by one or more processors, further cause operations including discarding a second telematics data set in response to the second set of telematics data corresponding to a second problem that is different from the first problem, the second problem having a second frequency value below the predefined threshold, the second problem being included in the list of problems, and the second telematics data set being different from the first telematics data set. [14] A device for logging telematics data of a vehicle, the device comprising: one or more processors; and one or more memory devices storing instructions that, when executed by one or more processors, cause the one or more processors to: Receiving access information from a remote computer system, the access information comprising information indicating a data type and a logging duration; Logging telematics data corresponding to the data type, where logging the telematics data includes: Storing the telematics data corresponding to the data type in a buffer for the logging duration; Monitor for an error code; in response to the failure to detect the fault code, causing the buffer to delete a portion of the telematics data; and In response to detecting the error code, provide telematics data to the remote computer system. [15] The apparatus of claim 14, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: in response to an access level being unknown, sending a request for the access information to the remote computer system, the access information further comprising information indicating the access level; Comparing the access level with an access threshold; Logging the telematics data in response to the access level exceeding the access threshold; and Prevent telematics data from being logged in response to the access level not exceeding the access threshold. [16] The device of claim 14, wherein the data type corresponds to at least one component of the vehicle, the at least one component being associated with the error code. [17] The apparatus of claim 14, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: Comparing a data size of the telematics data corresponding to the data type with a data size threshold; and in response to the data size of the telematics data corresponding to the data type being at or above the data size threshold and the trouble code not being detected, causing the buffer to delete the portion of the telematics data. [18] The apparatus of claim 14, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: Comparing one or more timestamps associated with the telematics data corresponding to the data type with a timestamp threshold; and in response to at least one timestamp of the one or more timestamps associated with the telematics data corresponding to the data type being at or above the timestamp threshold and the trouble code not being detected, causing the buffer to delete the portion of the telematics data corresponding to the data type. [19] The apparatus of claim 14, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: Increasing an event counter value in response to detecting the error code; Activating a data logging timer in response to incrementing the event counter value; Log additional telematics data corresponding to the data type; Generating an additional log file in response to detecting a second fault code while the data logging timer is enabled, the additional log file comprising the additional telematics data corresponding to the data type; and Deliver the additional log file to the remote computer system. [20] The apparatus of claim 19, wherein the instructions, when executed by one or more processors, further cause the one or more processors to: Comparing the event counter value with a predefined threshold; in response to the event counter value being at or above the predefined threshold, preventing additional telematics data from being logged; and Discard the access information and thereby prevent future telematics data from being logged.

Citation Information

Patent Citations

  • US63464344B2