Engine idling management for a vehicle communicating with an external server

Abstract

A vehicle management system (VMS) comprising a gateway (GW) and a sensor in communication with the GW is described. The sensor is couplable to one or more terminals of one or more batteries associated with a vehicle, and the VMS includes processing circuitry configured to measure, via the sensor, a battery parameter and cause the GW to transmit one or both of the battery parameter and one or more additional parameters. The transmitted one or both of the battery parameter and the one or more additional parameters are usable to determine an indication indicating whether to start or stop vehicle idling.

Description

[0001] ENGINE IDLING MANAGEMENT

[0002] TECHNICAL FIELD

[0003] This disclosure relates to a method and system for management of engine idling using one or more battery sensors.

[0004] BACKGROUND

[0005] Motor-powered and / or electrically powered vehicles typically rely on using one or more battery or battery systems for providing a starting power (e.g., power used to crank and start an engine) and / or at least a portion of a motion power for the vehicle. Such vehicles may include one or more of an air- or watercraft, a rail-guided vehicle, a street vehicle, etc., where a street vehicle may refer to, for example, cars, trucks, buses, recreational vehicles, etc.

[0006] A vehicle engine may be operated at idle such as when the vehicle is not in motion, or the vehicle is parked. For example, when a truck is parked over long periods of time such as overnight or over weekends, the driver of the truck may leave the vehicle engine idling to charge the vehicle batteries, avoid problems during engine start, etc. In many cases, idling is unnecessary to meet one or more conditions (e.g., battery state of charge), and the driver of the vehicle may not be aware that the idling is unnecessary, which may result in unnecessary fuel consumption and emissions.

[0007] SUMMARY

[0008] Some embodiments advantageously provide a method and system for management of engine idling using one or more battery sensors. In one or more embodiments, whether idling is necessary or unnecessary is determined based on one or more parameters such as battery parameters, vehicle parameters, location parameters, weather parameters, etc. In some embodiments, a sensor is used to measure one or more battery parameters, which may be transmitted to a server, which may perform the determination of whether idling is necessary or unnecessary. A notification or indication may be transmitted (e.g., by the server) to alert the driver of a vehicle that idling is necessary or unnecessary. The notification or indication may be transmitted to a wireless devices associated with the driver and / or vehicle, a management platform (e.g., fleet management platform), and a vehicle control system. In one or more embodiments, idling may be started, stopped or prevented by manually performing an action, such as turning the engine ignition switch on or off or any other position that stops idling. In some embodiments, idling may be started or stopped automatically, e.g., by a vehicle control system receiving the notification and causing the engine to start or stop.

[0009] In accordance with one aspect, a vehicle management system (VMS), is provided. The VMS includes a gateway (GW) and a sensor in communication with the GW, the sensor being couplable to one or more terminals of one or more batteries associated with a vehicle. The VMS includes processing circuitry configured to measure, via the sensor, a battery parameter, and cause the GW to transmit one or both of the battery parameter and one or more additional parameters, the transmitted one or both of the battery parameter and the one or more additional parameters being usable to determine an indication indicating whether to start or stop vehicle idling.

[0010] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0011] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0012] In some embodiments, the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

[0013] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0014] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0015] In some embodiments, the VMS is configured to communicate with a server, the one or both of the battery parameter and the one or more additional parameters are transmitted to the server and trigger the server to determine and transmit the indication.

[0016] In some embodiments, when an engine of vehicle is running, the state of charge is determined based at least in part on measured current from battery and the measured voltage of battery and / or battery cells.

[0017] In accordance with another aspect, a method implemented in a vehicle management system (VMS) is provided. The VMS includes a gateway (GW) and a sensor in communication with the GW, the sensor being couplable to one or more terminals of one or more batteries associated with a vehicle. The method includes measuring, via the sensor, a battery parameter, and causing the GW to transmit one or both of the battery parameter and one or more additional parameters, the transmitted one or both of the battery parameter and the one or more additional parameters being usable to determine an indication indicating whether to start or stop vehicle idling.

[0018] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0019] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0020] In some embodiments, the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

[0021] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0022] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0023] In some embodiments, the method further includes communicating with a server, transmitting to the server one or both of the battery parameter and the one or more additional parameters, and triggering the server to determine and transmit the indication.

[0024] In some embodiments, when an engine of vehicle is running, the state of charge is determined based at least in part on measured current from battery and the measured voltage of battery and / or battery cells.

[0025] In accordance with another aspect, a system including a vehicle management system, (VMS) and a server in communication with the VMS, the VMS including a gateway (GW) and a sensor in communication with the GW, the sensor being couplable to one or more terminals of one or more batteries associated with a vehicle, is provided. The VMS includes processing circuitry configured to measure, via the sensor, a battery parameter, and transmit the measured battery parameter to the GW, the GW including processing circuitry configured to receive the measured battery parameter, cause GW to transmit one or both of the battery parameter and one or more additional parameters to the server, the server including processing circuitry configured to receive one or both of the battery parameter and one or more additional parameters, and determine and transmit an indication indicating whether to start or stop vehicle idling based on the one or both of the battery parameter and the one or more additional parameters.

[0026] In some embodiments, the system further includes one or both of a wireless device (WD) and a management platform (MP) including processing circuitry configured to receive the indication and perform one or more actions based on the indication. In some embodiments, the system further includes a vehicle control system VCS) including processing circuitry configured to receive the indication and perform one or more actions based on the indication.

[0027] In some embodiments, the one or more actions include causing the vehicle to start or stop idling.

[0028] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0029] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0030] In some embodiments, the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

[0031] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0032] In some embodiments, the indication to stop idling is based at least in part on determining that a state of the one or more batteries will support a subsequent vehicle cranking operation.

[0033] In some embodiments, when an engine of vehicle is running, the state of charge is determined based at least in part on measured current from the one or more batteries and the measured voltage of the one or more batteries and / or battery cells.

[0034] In accordance with another aspect, a method implemented in a system including a vehicle management system, VMS and a server in communication with the VMS, the VMS including a gateway (GW) and a sensor in communication with the GW, the sensor being couplable to one or more terminals of one or more batteries associated with a vehicle, is provided. The method includes measuring, via the sensor a battery parameter, transmitting the measured battery parameter to the GW, receiving, via the GW, the measured battery parameter, transmitting one or both of the battery parameter and one or more additional parameters to the server, receiving, via the server, one or both of the battery parameter and one or more additional parameters, and determining and transmitting an indication indicating whether to start or stop vehicle idling based on the one or both of the battery parameter and the one or more additional parameters.

[0035] In some embodiments, the system further includes one or both of a wireless device, (WD) and a management platform (MP), the method further includes receiving the indication and performing one or more actions based on the indication. In some embodiments, the system further includes a vehicle control system (VCS) the method further includes receiving the indication and performing one or more actions based on the indication.

[0036] In some embodiments, the one or more actions include causing the vehicle to start or stop idling.

[0037] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0038] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0039] In some embodiments, the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

[0040] In some embodiments, the indication is based on whether the one or more batteries are predicted to meet or exceed a performance condition while the vehicle is not idling.

[0041] In some embodiments, the indication to stop idling is based at least in part on determining that a state of the one or more batteries will support a subsequent vehicle cranking operation.

[0042] In some embodiments, when an engine of vehicle is running, the state of charge is determined based at least in part on measured current from the one or more batteries and the measured voltage of the one or more batteries and / or battery cells.

[0043] BRIEF DESCRIPTION OF THE DRAWINGS

[0044] A more complete understanding of embodiments described herein, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0045] FIG. 1 is a diagram of an example system according to principles disclosed herein;

[0046] FIG. 2 shows an example battery and vehicle management system (VMS) constructed in accordance with the principles of the present disclosure;

[0047] FIG. 3 is a block diagram of some entities in the system according to some embodiments of the present disclosure;

[0048] FIG. 4 is a block diagram of an example gateway (GW) according to some embodiments of the present disclosure; FIG. 5 is a block diagram of a battery management system (BMS) according to some embodiments of the present disclosure;

[0049] FIG. 6 shows an example VMS coupled to two batteries according to some embodiments of the present disclosure;

[0050] FIG. 7 shows an example wiring harness according to some embodiments of the present disclosure;

[0051] FIG. 8 shows an example sensor being coupled to a battery terminal according to some embodiments of the present disclosure;

[0052] FIG. 9 shows example VMS components coupled to a battery terminal according to some embodiments of the present disclosure;

[0053] FIG. 10 shows other VMS components coupled to another battery terminal according to some embodiments of the present disclosure;

[0054] FIG. 11 shows an example gateway according to some embodiments of the present disclosure;

[0055] FIG. 12 is a flowchart of an example process according to some embodiments of the present disclosure;

[0056] FIG. 13 is a flowchart of another example process according to some embodiments of the present disclosure; and

[0057] FIG. 14 shows an example engine idling assessment process according to some embodiments of the present disclosure.

[0058] DETAILED DESCRIPTION

[0059] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to management of engine idling using one or more battery sensors.

[0060] Accordingly, the system and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0061] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0062] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0063] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. In some embodiments, “in communication with” refers to transmission / reception of signals which may include data, information, indications, notifications, etc. usable by any other components to perform one or more actions. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication.

[0064] In one or more embodiments, the term “couple” or “coupling” is used and may refer to a physical and / or electrical coupling of two or more components. The coupling of two or more components may be direct or indirect.

[0065] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0066] Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a diagram of a system 10, according to an embodiment, which comprises one or more vehicles 12, e.g., a car, motorcycle, scooter, golf cart, light utility vehicle, truck, etc. The vehicle 12 comprises a vehicle control system (VCS) 14 and battery 16 (i.e., one or more batteries) for powering at least one function of vehicle 12. VCS 14 may be configured to perform one or more actions associated with vehicle, such as engine control actions, provide vehicle and / or vehicle systems status information, etc. In an embodiments, VCS 14 may include one or more engine control units (ECUs). In some embodiments, battery 16 may be a lead-acid battery that includes one or more energy storage modules / cells. Although a lead-acid battery is described herein, the teachings described herein are equally applicable to other battery types. Battery 16 may include one or more batteries such as a first battery 16a, second battery 16b, third battery 16c, fourth battery 16d, etc., e.g., electrically connected (e.g., in parallel, series, etc.) as part of a battery pack. Although battery 16 is shown in conjunction with a vehicle 12, battery 16 is not limited as such and may be used in conjunction with any other component (e.g.., such as to power any other system component).

[0067] In some embodiments, battery 16 includes battery management system (BMS) 18 that is configured to perform one or more battery management functions described herein. In some embodiments, the BMS 18 may measure / determine certain battery parameters, e.g., resistance (e.g., battery resistance), voltage (e.g., cell voltage), current, state of charge (SoC), a time parameter, a frequency parameter, etc., and transmit / receive data (and / or signals such as control signals) to / from another system / device. In some embodiments, if the engine of vehicle 12 is running, the SoC can be determined based at least in part on measured current from battery 16 and the measured voltage of battery 16 and / or battery cells 46 (see FIG. 2). A BMS 18 may be configured to include a BMS management unit 20 (or battery management unit) that may be configured to perform one or more functions as described herein such as determining one or more parameters, steps, and / or processes associated with battery diagnostics.

[0068] System 10 may also include a vehicle management system (VMS) 22 which may be physically and electrically couplable to battery 16. VMS 22 may include vehicle management unit 24 which may be configured to perform one or more functions described herein such as measure battery parameters via one or more sensors, transmit battery data associated with the measurements, etc.

[0069] Further, system 10 may include server 26 which may be configured to communicate with any device or system of system 10 via networks 28, 30. In some embodiments, network 28 is a cloud network, and network 30 is an access network (e.g., 3GPP Fifth Generation (5G) network, Fong Term Evolution (ETE) network, etc.). Server 26 may include server management unit (SMU) 32 which may be configured to perform one or more functions described herein such as determining whether idling is not necessary and notifying one or more systems or devices of system 10. For example, system 10 may include wireless device (WD) 34 which may be associated with the driver of vehicle 12. WD 34 may be configured to perform one or more functions described herein such as receiving an indication and / or additional information from server 26 (e.g., a text message) indicating that idling is not necessary to meet a predetermined condition. The driver of vehicle 12 may then stop engine idling in response to the indication. Further, system 10 may include a management platform (MP) 36 (which may include one or more servers, personal computers, WDs 34, etc.). MP 36 may receive the indication and / or additional information and use the indication and information to perform one or more actions. For example, MP 36 may be a fleet management platform configured to perform one or more actions associated with fleet management.

[0070] It is contemplated that one or more entities of system 10 are in communication with each other via one or more of wireless communication, power communication, wired communication, fluid communication, etc. For example, vehicle 12, VCS 14, battery 16, VMS 22, server 26, WD 34, and MP 36 (and / or any other device or server) may communicate with each other directly or indirectly using wireless communication, power communication, wired communication, etc. Although battery 16 is shown as part of vehicle 12, battery 16 may be a standalone battery, removably couplable to any component of system 10 such as vehicle 12, etc.

[0071] FIG. 2 shows an example battery 16 and VMS 22 constructed in accordance with the principles of the present disclosure. Battery 16 includes a housing 38 into which one or more battery components may be positioned. In some embodiments, housing 38 may be made of a rigid polymer. The components may be electrically interconnected (not shown in the FIGS), such as via an electrically conductive busbar system which electrically interconnects the components in an electrically serial, electrically parallel or combination of electrically serial and parallel manner, depending on the intended voltage and current requirements.

[0072] A battery monitoring system (BMS) 18 may optionally be included. BMS 18 may include or be coupled to a monitoring connector 40 that allows for a removable external connection any other component of system 10 (e.g., to the vehicle’s data bus, to some other communication device, etc.) and / or internal connection, e.g., any components of battery 16 and / or BMS 18. Connector 40 may be comprised in BMS 18 and / or any other component of system 10. In some embodiments, connector 40 may be configured to removably couple and / or connect (electrically, physically) to another connector. The monitoring connector 40 can, in some embodiments, be integrated with the housing 38, such as in a cover 42 of the housing 38 or any other cover. Battery 16 also includes terminals, such as a positive terminal 44a and a negative terminal 44b (collectively referred to as terminals 44) to provide the contact points for electrical connection of the battery 16 (e.g., to power devices and / or the vehicle 12 and / or BMS 18 and / or VMS 22). Cover 42 may be arranged to receive BMS 18 in a cover space during assembly, e.g., such that BMS 18 is coupled to cover 42 and / or any other components of battery 16. Terminals 44 may be arranged to protrude through housing 38, such as protruding through cover 42. Terminals 44 may be electrically connected to the busbars inside housing 38 and / or directly connected to cells 46 (busbars and direct connection not shown).

[0073] Further, battery 16 may be arranged to provide many power capacities and physical sizes, and to operate under various parameters and parameter ranges. It is also noted that implementations of battery 16 some can be scaled to provide various capacities. For example, in some embodiments, the power capacity of battery 16 can range from 50Ah to lOOAh. It is noted, however, that this range is merely an example, and that it is contemplated that embodiments of battery 16 can be arranged to provide less than a 50Ah capacity or more than a lOOAh capacity. Power capacity scaling can be accomplished, for example, by using higher or lower power capacity cells 46 in the housing 38, and / or by using fewer or more cells 46 in the housing 38. In some embodiments, battery 16 may be incorporated as part of a vehicle where battery power is needed. Other electrical parameters of the battery 16 can be adjusted / accommodated by using cells 46 that may cumulatively have the desired operational characteristics, e.g., current, voltage, charge, charging capacity / rate, discharge rate, etc. Further, BMS 18 may be connected to at least one of the cells such as to determine / measure at least one parameter of battery 16 and / or cells 46.

[0074] In some embodiments, battery 16 may also include a plurality of leads 48 (e.g., lead assembly, lead frame), where each lead is electrically connected to a cell 46 and BMS 18. BMS 18 may be configured to determine one or more parameters of each cell 46 via leads 48 such as cell temperature, cell pressure, etc.

[0075] VMS 22 may include sensor 50 and / or gateway (GW) 52 and / or be configured to communicate with one or more devices and / or systems of system 10. Sensor 50 may be physically and / or electrically coupled to a battery terminal such as terminal 44b (e.g., a negative terminal). Further, sensor 50 may be electrically (and / or physically) coupled to GW 52. For example, GW 52 and sensor 50 may be electrically coupled and communicate with each other via one or more communication protocols (such as controller area network (CAN) protocol or any other protocol) and / or conductors. Other conductors may electrically couple to sensor 50 and GW 52 such as for providing power to one and / or the other of sensor 50 and GW 52. Further, other electrical connections may be established by electrically coupling terminals 44a, 44b to sensor 50 and GW 52. GW 52 may be configured to communicate any measurements performed by and / or any other data provided by sensor 50 to other components of system 10. In one or more embodiments, VMS 22 is in communication with VCS 14 and is configured to cause VCS 14 to perform vehicle actions such as stopping / starting the vehicle engine, exchange information associated with the battery 16 and / or vehicle 12.

[0076] Example implementations, in accordance with an embodiment, of VMS 22 discussed in the preceding paragraphs will now be described with reference to FIG. 3. VMS 22 may have hardware 54 that may include a communication interface 56 which may include GW 52. In some embodiments, GW 52 is not included in communication interface but is included in VMS 22. Communication interface 56 (and / or GW 52) is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications. GW 52 may also be configured to communicate with any other component of VMS 22 and receive and / or transmit signaling using one or more communication protocols.

[0077] Hardware 54 includes processing circuitry 58. Processing circuitry 58 may include a processor 60 and memory 62. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 58 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. Processor 60 may be configured to access (e.g., write to and / or read from) memory 62, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 54 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0078] In addition, VMS 22 may include a global positioning system (GPS) 64 which may be configured to provide positioning information and / or location information. In some embodiments, GPS 64 is included in GW 52 which may have one or more GPS antennas to receive signaling usable for determining positioning and / or location information. Thus, the VMS 22 may further comprise software 66, which is stored in, for example, memory 62, or stored in external memory (e.g., database, etc.) accessible by the VMS 22. The software 66 may be executable by the processing circuitry 58.

[0079] The processing circuitry 58 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by VMS 22. The processor 60 corresponds to one or more processors 60 for performing VMS functions described herein. The VMS 22 includes memory 62 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 66 may include instructions that, when executed by the processor 60 and / or processing circuitry 58, causes the processor 60 and / or processing circuitry 58 to perform the processes described herein with respect to VMS 22. For example, the processing circuitry 58 of the VMS 22 may include vehicle management unit 24 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., determining one or more parameters, steps, and / or processes associated with battery 16 such SoC and / or performing one or more actions. While vehicle management unit 24 is illustrated as being part of VMS 22, vehicle management unit 24 and associated functions described herein may be implemented in a device separate from VMS 22 such as in battery 16 or another device.

[0080] Server 26 may have hardware 68 that may include a communication interface 70. Communication interface 70 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0081] The hardware 68 includes processing circuitry 72. The processing circuitry 72 may include a processor 74 and memory 76. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 72 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 74 may be configured to access (e.g., write to and / or read from) memory 76, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 68 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0082] Thus, the server 26 may further comprise software 78, which is stored in, for example, memory 76, or stored in external memory (e.g., database, etc.) accessible by the server 26. The software 78 may be executable by the processing circuitry 72.

[0083] The processing circuitry 72 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by server 26. The processor 74 corresponds to one or more processors 74 for performing server functions described herein. The server 26 includes memory 76 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 78 may include instructions that, when executed by the processor 74 and / or processing circuitry 72, causes the processor 74 and / or processing circuitry 72 to perform the processes described herein with respect to server 26. For example, the processing circuitry 72 of the server 26 may include server management unit (SMU) 32 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., performing an idling assessment and / or performing one or more actions. While SMU 32 is illustrated as being part of server 26, SMU 32 and associated functions described herein may be implemented in a device separate from server 26.

[0084] MP 36 may have hardware 80 that may include a communication interface 82. Communication interface 82 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0085] The hardware 80 includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 68 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0086] Thus, MP 36 may further comprise software 90, which is stored in, for example, memory 88, or stored in external memory (e.g., database, etc.) accessible by MP 36. The software 90 may be executable by the processing circuitry 84.

[0087] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by MP 36. The processor 86 corresponds to one or more processors 86 for performing server functions described herein. The MP 36 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to MP 36. For example, the processing circuitry 84 of MP 36 may include management platform unit (MPU) 92 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., receiving idling indications and / or additional information from server 26 and / or performing one or more actions. While MPU 92 is illustrated as being part of MP 36, MPU 92 and associated functions described herein may be implemented in a device separate from MP 36.

[0088] WD 34 may have hardware 94 that may include a communication interface 96. Communication interface 96 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0089] The hardware 94 includes processing circuitry 98. The processing circuitry 98 may include a processor 100 and memory 102. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 98 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 102, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 94 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0090] Thus, WD 34 may further comprise software 104, which is stored in, for example, memory 102, or stored in external memory (e.g., database, etc.) accessible by WD 34. The software 104 may be executable by the processing circuitry 98.

[0091] The processing circuitry 98 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 34. The processor 100 corresponds to one or more processors 100 for performing server functions described herein. The WD 34 includes memory 102 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 104 may include instructions that, when executed by the processor 100 and / or processing circuitry 98, causes the processor 100 and / or processing circuitry 98 to perform the processes described herein with respect to WD 34. For example, the processing circuitry 98 of WD 34 may include wireless device unit (WDU) 106 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., receiving idling indications and / or additional information from server 26 and / or performing one or more actions. While WDU 106 is illustrated as being part of WD 34, WDU 106 and associated functions described herein may be implemented in a device separate from WD 34.

[0092] VCS 14 may have hardware 108 that may include a communication interface 110. Communication interface 110 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0093] The hardware 108 includes processing circuitry 112. The processing circuitry 112 may include a processor 114 and memory 116. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 112 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 114 may be configured to access (e.g., write to and / or read from) memory 116, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 108 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0094] Thus, VCS 14 may further comprise software 118, which is stored in, for example, memory 116, or stored in external memory (e.g., database, etc.) accessible by VCS 14. The software 118 may be executable by the processing circuitry 112.

[0095] The processing circuitry 112 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by VCS 14. The processor 114 corresponds to one or more processors 114 for performing server functions described herein. The VCS 14 includes memory 116 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 118 may include instructions that, when executed by the processor 114 and / or processing circuitry 112, causes the processor 114 and / or processing circuitry 112 to perform the processes described herein with respect to VCS 14. For example, the processing circuitry 112 of VCS 14 may include vehicle control unit (VCU) 120 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., receiving idling indications and / or additional information from server 26 and / or performing one or more actions such as starting or stopping the vehicle engine. While VCU 120 is illustrated as being part of VCS 14, VCU 120 and associated functions described herein may be implemented in a device separate from VCS 14.

[0096] Any one of VMS 22, server 26, WD 34, MP 36, and VCS 14 may directly or indirectly communicate with any other device or system or component of system 10. In a nonlimiting example, VMS 22 (and / or GW 52) may communicate with server 26 via communication link 122. Server 26 may communicate with MP 36 via communication link 124 and communicate with WD 34 via communication link 126. MP 36 may communicate with WD 34 via communication link 128. WD 34 may communicate with VMS 22 via communication link 130, VMS 22 may communicate with VCS 14 via communication link 132, and VMS 22 may communicate with MP 36 via communication link 134. That is, one or more communication links 122, 124, 126, 128, 130, 132, and 134 may be used for communication, but the embodiments are not limited as such and any device or component of system 10 may communicate with any other device shown on FIG. 3 or on any other figure or described herein. Although FIGS. 1-3 may show one or more “units” such as vehicle management unit 24, SMU 32, MPU 92, WDU 106, and VCU 120 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware, software or in a combination of hardware and software within the processing circuitry.

[0097] Example implementations, in accordance with an embodiment, of GW 52 discussed in the preceding paragraphs will now be described with reference to FIG. 4. GW 52 may have hardware 136 that may include a communication interface 138 which may include one or more antennas 140. Communication interface 138 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0098] The hardware 136 includes processing circuitry 142. The processing circuitry 142 may include a processor 144 and memory 146. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 142 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 144 may be configured to access (e.g., write to and / or read from) memory 146, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 136 may also have one or more circuit elements 148 such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements 148 may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0099] In addition, GW 52 may include a global positioning system (GPS) 64 which may be configured to provide positioning information and / or location information. In some embodiments, GPS 64 may have one or more GPS antennas to receive signaling usable for determining positioning and / or location information. Further, GW 52 may include one or more input output (IO) elements 150 configured to receive input from a user and provide output for a user. For example, an input element may include buttons, keys, etc., that a user may use to provide information and / or data to GW 52 such as to configure GW 52. Output elements may include displays, indicators, etc. that a user may use to obtain status information, or any other information associated with GW 52.

[0100] Thus, the GW 52 may further comprise software 152, which is stored in, for example, memory 146, or stored in external memory (e.g., database, etc.) accessible by the GW 52. The software 152 may be executable by the processing circuitry 58.

[0101] The processing circuitry 142 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by GW 52. The processor 144 corresponds to one or more processors 144 for performing GW functions described herein. The GW 52 includes memory 146 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 152 may include instructions that, when executed by the processor 144 and / or processing circuitry 142, causes the processor 144 and / or processing circuitry 142 to perform the processes described herein with respect to GW 52. For example, the processing circuitry 142 of the GW 52 may include GW unit (GWU) 154 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., transmitting and / or receiving one or more parameters associated with sensor 50 and / or vehicle 12 and / or battery 16 and / or performing one or more actions. While GWU 154 is illustrated as being part of GW 52, GWU 154 and associated functions described herein may be implemented in a device separate from GW 52.

[0102] Example implementations, in accordance with an embodiment, of BMS 18 discussed in the preceding paragraphs will now be described with reference to FIG. 5. BMS 18 may have hardware 156 that may include a communication interface 158. Communication interface 158 is configured to communicate with one or more entities in system 10 via wired and / or wireless communication. The communication may be protocol based communications.

[0103] The hardware 156 includes processing circuitry 160. The processing circuitry 160 may include a processor 162 and memory 164. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 160 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 162 may be configured to access (e.g., write to and / or read from) memory 146, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Hardware 156 may also have one or more circuit elements such as resistors, capacitors, inductors, diodes, transistors, ground connections, source elements, sink elements, sensors, etc. Circuit elements 148 may be arranged in any configuration or connection such as series, parallel, combinations thereof, etc.

[0104] Thus, the BMS 18 may further comprise software 166, which is stored in, for example, memory 164, or stored in external memory (e.g., database, etc.) accessible by the BMS 18. The software 166 may be executable by the processing circuitry 160.

[0105] The processing circuitry 160 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by BMS 18. The processor 162 corresponds to one or more processors 162 for performing BMS functions described herein. The BMS 18 includes memory 164 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 166 may include instructions that, when executed by the processor 162 and / or processing circuitry 160, causes the processor 162 and / or processing circuitry 160 to perform the processes described herein with respect to BMS 18. For example, the processing circuitry 160 of the BMS 18 may include BMS management unit (BMU) 20 that is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure. While BMU 20 is illustrated as being part of BMS 18, BMU 20 and associated functions described herein may be implemented in a device separate from BMS 18.

[0106] FIG. 6 shows an example VMS 22 coupled to two batteries 16a, 16b according to some embodiments of the present disclosure. System 10 includes a battery 16a and a battery 16b. Battery 16a includes terminal 44a (e.g., positive terminal) and terminal 44b (e.g., negative terminal). Battery 16b includes terminal 44c (e.g., positive terminal) and terminal 44d (e.g., negative terminal). VMS 22 includes sensor 50 and GW 52 which may be configured to communicate with server 26, WD 34, and MP 36. VMS 22 may be also configured to communicate with VMS 22. Further, VMS 22 includes a wiring harness that is physically and / or electrically couplable to one or more components of batteries 16a, 16b and / or VMS 22. Wiring harness 168 includes links 170, 172, 174, 176, 178. Eink 170 may be an electrical and / or communication link, where link 170 includes one or more conductors for establishing communication (e.g., using a controller area network (CAN) protocol) between sensor 50 and GW 52. For example, two wires may be used for CAN communication and two wires for power. In one or more embodiments, sensor 50 is directly powered by the GW 52. In other embodiments, sensor 50 is powered indirectly by GW 52 (e.g., links coupled to the battery terminals are routed via and / or coupled to the GW 52). In some embodiments, GW 52 is directly powered by the sensor 50. In other embodiments, GW 52 is powered indirectly by sensor 50 (e.g., links coupled to the battery terminals are routed via and / or coupled to the sensor 50).

[0107] In some embodiments, link 170 is referred to as Pl or battery sensor connector. Link 172 may be a conductor that connects to terminal 44b. Link 174 may be a conductor that connects to terminal 44a, and link 176 may be a conductor that connects to terminal 44c. In some embodiments, link 172 may be referred to as “BAT-” or Vehicle Ground GND / Batt #1 (-). In some embodiments, link 174 is referred to as “BAT12” or Bridge Tension / Batt #1 (+) or Batt #2 (-). In some embodiments, link 176 is referred to as “BAT24” or Vehicle Plus / Batt #2 (+). In some embodiments, sensor 50 and / or GW 52 are powered using any combination of BAT-, BAT12, and BAT24 (or their corresponding links). In one or more embodiments, sensor 50 is powered by the 24V rail signal (i.e., link 176 or BAT24) from the batteries 16a, 16b (i.e., battery pack) on the wiring harness 168. In some embodiments, GW 52 is powered by the 24V rail signal (i.e., link 176 or BAT24) from the batteries 16a, 16b (i.e., battery pack) on the wiring harness 168, and 12V (i.e., link 174) goes to the sensor for measurement of one or more battery parameters.

[0108] Further, link 178 includes one or more conductors for establishing communication (e.g., using a CAN protocol) between sensor 50 and GW 52 and / or for power and / or one or more of conductors of links 170, 172, 174, 176. In some embodiments, link 178 may be referred to as P2 or gateway connector. Further, sensor 50 may be physically coupled to terminal 44b via link 180 (e.g., a terminal clamp attached to the sensor and arranged to clamp on the terminal). Connector 182 may be configured to receive and / or couple to links 170, 172, 174, 176, 178 and / or serve as a passage and / or junction device for any conductor associated with links 170, 172, 174, 176, 178.

[0109] Terminal 44b may further be coupled to link 184 (e.g., ground cable which is couplable to the vehicle chassis). In some embodiments, link 184 is a cable or any other conductor. In some other embodiments, link 184 is directly coupled to link 180 such that link 184 is indirectly coupled to terminal 44b. In some embodiments, link 184 is directly coupled to terminal 44b. Terminals 44a and 44d may be interconnected via link 432 which may be a cable or any other conductor. In addition, link 186 is coupled to terminal 44c. Thus, the voltage across terminal 44c and terminal 44b may be the sum of the voltage across terminals 44a, 44b and the voltage across terminals 44c, 44d. In a nonlimiting example, battery 16a is a 12V battery, and battery 16b is a 12V battery. That is, in this example, the voltage across terminals 44a, 44b is 12V + / - a predetermined tolerance value, and the voltage across terminals 44c, 44c is 12V + / - a predetermined tolerance value. Then, the voltage across terminals 44c, 44d is 24V+ / - a predetermined tolerance value.

[0110] In some embodiments, link 174 and link 176 provide the voltage at / corresponding to terminal 44a (e.g., 12V) and the voltage at / corresponding to terminal 44c (e.g., 24V), respectively. In some other embodiments, sensor 50 is configured to measure battery parameters such as the 12V and 24V levels of battery 16a and of both batteries 16a, 16b. Sensor 50 may also be configured to measure current and / or temperature associated with batteries 16a, 16b.

[0111] In some embodiments, batteries 16a, 16b are arranged to couple to and power a vehicle 12 such as a truck that may be parked and possibly idle over a predetermined period of time. VMS 22 is configured to measure, via sensor 50, battery parameters and cause GW 52 to transmit the battery parameters and / or associated data to any of server 26, WD 34, and MP 36. In a nonlimiting example, server 26 may be configured to determine one or more additional parameters using the battery parameters received from GW 52 and / or perform an idling assessment based on the battery parameters and / or additional parameters. The idling assessment may include determining whether the engine of vehicle 12 may or may not need to idle and determining an indication that indicates whether to idle or whether idling is unnecessary (e.g., based on predetermined conditions). The indication may be transmitted to MP 36 and WD 34 for MP 36 and WD 34 to perform an action based on the indication and / or the user of any of MP 36 and WD to perform an action. The indication may also be transmitted to VCS 14 to trigger VCS 14 to perform an action, such as cause the engine to start idling (such as by starting the engine), to stop idling or stop the engine or continue running the engine.

[0112] FIG. 7 shows an example wiring harness 168 according to some embodiments of the present disclosure. Wire harness 168 may include links 170, 172, 174, 176, 178, connector 182, connector 188, connector 190, circuit element holder 192, and circuit element holder 194. Connector 188 is coupled to or part of link 170 and may be arranged to couple to sensor 50. Connector 190 is coupled to or part of link 178 and may be arranged to couple to GW 52. Circuit element holders 192, 194 (e.g., blade fuse holders) may be arranged to include any circuit element (e.g., a fuse or any other electric circuit protection element) and perform functions associated with the circuit element and / or releasably couple to any portion of vehicle 12 and / or battery 16. Circuit element holders 192, 194 are electrically and / or physically coupled to their respective links 176, 174. For example, an end of the circuit element included in circuit element holder 194 may be coupled to a portion of link 174, and another end of the circuit element included in circuit element holder 194 may be coupled to another portion of link 174 such that a continuity is established, and electrical current may flow through link 174 and the circuit element. Similarly, an end of the circuit element included in circuit element holder 192 may be coupled to a portion of link 176, and another end of the circuit element included in circuit element holder 192 may be coupled to another portion of link 176 such that a continuity is established, and electrical current may flow through link 176 and the circuit element. The circuit element (e.g., a fuse) may be arranged to discontinue the current flow when a predetermined parameter threshold is met or exceeded, e.g., a current value exceeding a predetermined current threshold. The circuit element may be arranged to be reset or replaced as the circuit element may be releasably coupled to its corresponding circuit element holder 192, 194 and / or links 174, 176.

[0113] FIG. 8 shows an example sensor 50 being coupled to a battery terminal 44 according to some embodiments of the present disclosure. Sensor 50 may include a sensor port 196 arranged to receive and couple to connector 188 and / or establish, maintain, or terminate an electrical connection with one or more components of VMS 22. Sensor 50 may also include fastener 198 electrically coupled to bar 200. Bar 200 may be electrically coupled to terminal clamp 202 and link clamp 204 which may include fastener 206. Sensor 50 may be coupled to link 170 via connector 188 and sensor port 196 and coupled to a battery terminal 44 such as battery terminal 44b. Link 172 may be coupled to a battery terminal 44 such as battery terminal 44b via terminal clamp 202, fastener 206, and link clamp 204. Link clamp 204 may be arranged to receive and secure link 172 (i.e., an end of link 172). Link 172 may also be coupled to any other component of VMS 22, e.g., link 172 may be coupled to GW 52 to provide electrical ground functions to GW 52. Ground cable 207 may be coupled and secured to fastener 198 using nut 210. In some embodiment, ground cable 207 is link 184.

[0114] In some embodiments, a sensor 50 is used to measure the 12V and 24V battery voltages, current, and temperature. The sensor 50 is mounted between the battery #1 negative (-) terminal of the battery system and the vehicle chassis GND. Sensor 50 connects to Pl of the wiring harness 168 for power and CAN bus communication with the GW 52.

[0115] FIG. 9 shows example VMS components coupled to a battery terminal 44 according to some embodiments of the present disclosure. Link 174 may be coupled to terminal 44a (e.g., positive terminal of battery 16a) via terminal clamp 212, link clamp 214 and fastener 216. Link 174 may also be coupled to sensor 50 for sensor 50 to perform measurements. Terminal 44a may be coupled to cable 218 (e.g., 12V cable) which may provide positive voltage to vehicle 12. FIG. 10 shows other VMS components coupled to another battery terminal 44 according to some embodiments of the present disclosure. Link 176 may be coupled to terminal 44c (e.g., positive terminal of battery 16b) via terminal clamp 212, link clamp 220 and fastener 222, via nut 223. Link 176 may also be coupled to sensor 50 and / or GW 52 such as to power sensor 50 and / or GW 52. Terminal 44b may be coupled to cable 224 (e.g., 24V cable) which may provide positive voltage to vehicle 12.

[0116] FIG. 11 shows an example GW 52 according to some embodiments of the present disclosure. GW 52 may be coupled to a wiring harness 168 (on its sensor port) and to one or more antennas 140 (e.g., cellular communication antennas, GPS antennas, etc.). Further, GW 52 may include IO elements 150 such as a display 226, status indicators (light emitting diodes (LEDs)), buttons for setting up or configuring GW 52 and buttons for accessing user functions. For example, status indicators may indicate a system status and / or sensor status (e.g., sensor 50 is off, no sensor is detected, senor is detected, etc.). In some embodiments, the GW 52 may have multiple operating modes as turning on, initializing, establishing cellular connection, retail / monitoring mode, commissioning mode, safe / over the air mode, etc.

[0117] FIG. 12 is a flowchart of an example process according to some embodiments of the present disclosure. The method implemented in VMS 22 which includes GW 52 and a sensor in communication with the GW 52. The sensor 50 is couplable to one or more terminals 44 of one or more batteries 16 associated with a vehicle 12. The method includes measuring (Block S101), via the sensor 50, a battery parameter and causing (Block S103) the GW 52 to transmit one or both of the battery parameter and one or more additional parameters. The transmitted one or both of the battery parameter and the one or more additional parameters are usable to determine and transmit an indication indicating whether to start or stop vehicle idling.

[0118] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0119] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0120] In some embodiments, the indication indicating whether to start or stop vehicle 12 idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results. In some embodiments, the indication is based on whether the one or more batteries 16 are predicted to meet or exceed a performance condition while the vehicle 12 is not idling.

[0121] In some embodiments, the indication to stop idling is based at least in part on determining that a state of the one or more batteries (16) will support a subsequent vehicle (12) cranking operation.

[0122] In some embodiments, the VMS 22 is configured to communicate with a server 26, the one or both of the battery parameter and the one or more additional parameters are transmitted to the server 26 and trigger the server 26 to determine and transmit the indication. However, the embodiments are not limited as such, and any components of system 10 (e.g., GW 52) may determine / transmit the indication.

[0123] In some embodiments, when an engine of vehicle 12 is running, the state of charge is determined based at least in part on measured current from battery 16 and the measured voltage of battery 16 and / or battery cells 46.

[0124] FIG. 13 is a flowchart of an example process according to some embodiments of the present disclosure. The method is implemented in a system 10 including VMS 22 and a server 26 in communication with the VMS 22. The VMS 22 includes GW 52 and a sensor 50 in communication with the GW 52, the sensor 50 being couplable to one or more terminals 44 of one or more batteries 16 associated with a vehicle 12. The method includes measuring (Block S105), via the sensor 50, a battery parameter. The method further includes transmitting (Block S107) the measured battery parameter to the GW 52. The method further includes receiving (Block S109) via the GW 52, the measured battery parameter. The method further includes transmitting (Block Si l l) one or both of the battery parameter and one or more additional parameters to the server 26. The method further includes receiving (Block SI 13), via the server 26, one or both of the battery parameter and one or more additional parameters. The method further includes determining (Block SI 15) and transmitting an indication indicating whether to start or stop vehicle idling based on the one or both of the battery parameter and the one or more additional parameters.

[0125] In some embodiments, the system 10 further includes one or both of a wireless device (WD) 34 and a management platform (MP) 36 including processing circuitry 98,84 configured to receive the indication and perform one or more actions based on the indication.

[0126] In some embodiments, the system 10 further includes a vehicle control system (VCS) 14 including processing circuitry 112 configured to receive the indication and perform one or more actions based on the indication. In some embodiments, the one or more actions include causing the vehicle 12 to start or stop idling.

[0127] In some embodiments, the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

[0128] In some embodiments, the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

[0129] In some embodiments, the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

[0130] In some embodiments, the indication is based on whether the one or more batteries 16 are predicted to meet or exceed a performance condition while the vehicle 12 is not idling.

[0131] In some embodiments, the indication to stop idling is based at least in part on determining that a state of the one or more batteries 16 will support a subsequent vehicle 12 cranking operation.

[0132] In some embodiments, when an engine of vehicle 12 is running, the state of charge is determined based at least in part on measured current from the one or more batteries 16 and the measured voltage of the one or more batteries 16 and / or battery cells 46.

[0133] FIG. 14 shows an example engine idling assessment method according to some embodiments of the present disclosure. At step SI 17, data collection is performed by sensor 50 and / or other sources 228 which may be any components of system 10. The data may include measurements associated with vehicle 12, battery 16, etc. The collected data is transmitted at step SI 19 for processing and / or storage at step S 121 , which may be performed by server 26. An indication such as an alert notification at step S123 is transmitted by server 26 to WD 34 and / or MP 36 (and / or VCS 14) which may indicate whether idling the engine of vehicle 12 is unnecessary to meet or exceed one or more battery parameters, etc. At step S125, WD 34 and / or MP 36 (and / or VCS 14) performs an idling assessment. For example, the user of WD 34 (which may be the driver of vehicle 12) may receive the indication (e.g., an SMS message) indicating that idling is not necessary, and the user may manually switch the engine to the off position, thereby discontinuing the engine idling. VCS 14 may also perform the idling assessment based on the indication and cause the engine to start or stop idling.

[0134] In some embodiments, the criteria that may be used for the idling assessment at step S125 may be selected to ensure that the vehicle’s engine can reliably crank whenever the driver or VCS 14 needs to restart the engine, whether for idling or for the next drive. Thus, a determination to stop idling may be based at least in part on determining that a state of battery 16 will support a subsequent vehicle 12 cranking operation. This idling assessment may be achieved using algorithms that estimate the current state of the vehicle’s battery 16 (or batteries 16) and overall system, as well being able to predict the vehicle’s future state, e.g., state of health and / or state of charge, at the time a restart will be needed. To do so, algorithms will periodically and / or continuously execute based on monitored parameters such as, but not limited to, the vehicle 12 battery 16 (or batteries 16) and / or cell 46 voltages and currents, and temperature, and other parameters related to the vehicle’s operating state (e.g., idling, parking, and / or driving). Additional diagnostic checks may be implemented to detect whether the vehicle 12 is using supplemental energy sources like solar panels or if the vehicle 12 is in a special operational state such as in silo operation, which helps improve the accuracy of determining the state of vehicle 12. Besides this real-time monitoring, weather forecasts and historical data for battery 16 and vehicle 12 parameters (e.g., timestamps, voltage, current, temperature, and whether the truck was idling, driving, or parked) may be stored on server 26. This historical and environmental data may be used to further improve the accuracy of the algorithm’s estimations of battery state (such as, for example, State of Charge, State of Health, and State of Function) and to predict the vehicle’s usage patterns. For example, tracking the current usage history of battery 16 (or batteries 16) significantly improves State of Charge estimations, since relying solely on voltage may not be accurate. This is the case as battery voltage is typically heavily influenced by recent usage and load conditions.

[0135] Conventional systems do not typically provide functionality to have a direct impact on fuel savings. For example, some conventional systems include an integrated heating, ventilation, and air conditioning (HVAC) systems and alternative power unit (APU) installation in vehicle cabs. Further, conventional systems do not identify excessive idling or directly address driver behaviors that reduce fuel consumption.

[0136] In some embodiments, engine idling is reduced, thereby reducing fuel consumption and carbon dioxide (CO2) emissions for heavy duty trucking operations. Some embodiments provide remotely monitoring battery parameters such as SoC and SoH. Excessive idle conditions may be identified in real time, and indications provided to drivers which suggest either stop idling or start idling depending on an accurate assessment of the battery parameters, e.g., SoC.

[0137] In some other embodiments, a sensor 50 and / or GW 52 are used to transmit key battery and vehicle signals to server 26 (e.g., which may be configured to perform one or more algorithms). Server 26 may monitor the SoC of the battery system or batteries 16 and alert the driver and / or fleet operator when idling the vehicle is unnecessary to maintain auxiliary and starting functions associated with batteries 16.

[0138] In one or more embodiments, one or more of the following may be performed:

[0139] 1. Data collection: Data may be collected through battery sensors 50 and vehicles telematics (i.e., other sources 228).

[0140] 2. Data flow: Sensor / Vehicle data may be transmitted via LTE to server 26 by GW 52.

[0141] 3. Data processing: Server 26 may process the data through analytics and artificial intelligence (e.g., machine learning) models and / or processes to one or more idling recommendations (e.g., provide vehicle identification number (VIN)-level idling recommendation).

[0142] 4. Alerts notification: Server 26 may provide vehicle specific idling recommendation through a SMS / text message to the driver or through an application programming interface (API) to a fleet management system (i.e., MP 36).

[0143] In some embodiments, server 26 (and / or any other component of system 10) may provide vehicle specific idling recommendations through an SMS / text message alert to the driver of a predetermined vehicle 12 suggesting whether engine idling is required or not based on battery SoC. A fleet partner may share drivers’ contact number for server 26 to send alerts. Further, fleet partner may share DriveroVIN pairing schedule whenever any DriveroVIN pairing changes, which may be used to make idling recommendations.

[0144] In some other embodiments, sensors 50 and / or GW 52 may collect and communicate battery sensor data (e.g., current, voltage, temperature etc.), battery specification (e.g., capacity), and vehicle data (e.g., location, speed, etc.) from the batteries 16 and vehicle 12.

[0145] In some embodiments, operational reports are provided to fleet operators (e.g., associated with MP 36) to analyze and compare idle rates for different vehicles / drivers by various operating characteristics. SMS guidance may be also provided to vehicle drivers so that the drivers can optimize idle time by reducing unnecessary engine idling. Drivers may also receive reports detailing their idling habits and comparing their performance to drivers of comparable vehicles and routes.

[0146] Final message content and format for SMS guidance and reporting will be developed during the pilot and communicated in detail to the fleet prior to being activated In some other embodiments, vehicle 12 may include commercial trucks which include a sleeper cabin and one or more batteries 16 such as AGM batteries. Some embodiments are beneficial for drivers that keep their vehicles 12 parked overnight and / or idling.

[0147] In some embodiments, any component of system 10 (e.g., VMS 22 and / or server 26 and / or WD 34 and / or MP 36) may perform one or more of the following non-limiting functions:

[0148] 1. Data collection a. Capture input signals within predetermined ranges: i. Current: -1500 to 1500 amps. ii. Voltage: 0-36 V. iii. Vehicle Speed: 0-300 Km / h. iv. Ambient temperature: -40 to 85 C.

[0149] 2. Data transmission: a. Transmit per predetermined period of time. b. Validate no data loss between GW 52 and server 26, which may depend on the networks 28, 30. This metric may be measured and reported to distinguish between data loss due to network connection and gateway performance. c. Optimize tradeoffs between transmission cost and algorithm performance In some embodiments, performance key performance indicators (KPIs) may be tracked, which may include total number of devices, total number of devices online (sending data), total number of devices offline, gateway health (each device), cellular signal Quality and / or Received Signal Strength Indicator (RSSI), how many times signals are out of range that is been flagged, notification to fleet management system (FMS) when truck is physically at stop / breakdown. In some other embodiments, KPIs may be adopted and / or used based on how many SMS it takes for driver to take action across a population, for each truck, % over a day per truck. Also, how much idling change was triggered by SMS alert may be considered, where drivers may acknowledge the SMS to identify change (or lack of) in idling is due to SMS alert. The number of times fleet drivers acted on idle recommendation / total instances of idle recommendations may be tracked. Whether a change in idle position is recorded within a predetermined time from an SMS alert to fleet drivers can also be used.

[0150] In some other embodiments, idle classification may be performed, and KPIs may be reduced. The point in time detecting a change in idling may be used to consider the start and end of excessive idling. Population idle rate may be considered, where a baseline idle rate for population of vehicles not part of the pilot may be used. Baseline idle rates such as baseline total / excessive idle rates of target population may be used. The percentage idle reduction in total idle hours of the target population when fleet driver follows SMS alerts (per day, per week, total during the pilot duration) may be determined. The percentage of reduction in excessive idle hours of the target population when fleet driver follows SMS alerts (per day, per week, total during the pilot duration) may also be determined.

[0151] It will be appreciated by persons skilled in the art that the present embodiments are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. CLAIMS1. A vehicle management system, VMS, (22) comprising a gateway, GW, (52) and a sensor (50) in communication with the GW (52), the sensor (50) being couplable to one or more terminals (44) of one or more batteries (16) associated with a vehicle (12), the VMS (22) comprising processing circuitry (58) configured to: measure, via the sensor (50), a battery parameter; and cause the GW (52) to transmit one or both of the battery parameter and one or more additional parameters, the transmitted one or both of the battery parameter and the one or more additional parameters being usable to determine an indication indicating whether to start or stop vehicle idling.

2. The VMS (22) of Claim 1, wherein the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

3. The VMS (22) of any one of Claims 1 and 2, wherein the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

4. The VMS (22) of any one of Claims 1-3, wherein the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

5. The VMS (22) of any one of Claims 1-4, wherein the indication is based on whether the one or more batteries (16) are predicted to meet or exceed a performance condition while the vehicle (12) is not idling.

6. The VMS (22) of any of Claims 1-5, wherein the indication to stop idling is based at least in part on determining that a state of the one or more batteries (16) will support a subsequent vehicle (12) cranking operation.

7. The VMS (22) of any one of Claims 1-6, wherein the VMS (22) is configured to communicate with a server (26), the one or both of the battery parameter and the one ormore additional parameters are transmitted to the server (26) and trigger the server (26) to determine and transmit the indication.

8. The VMS (22) of any of Claims 2-7, wherein when an engine of vehicle (12) is running, the state of charge is determined based at least in part on measured current from the one or more batteries (16) and the measured voltage of the one or more batteries (16) and / or battery cells (46).

9. A method implemented in a vehicle management system, VMS, (22) comprising a gateway, GW, (52) and a sensor (50) in communication with the GW (52), the sensor (50) being couplable to one or more terminals (44) of one or more batteries (16) associated with a vehicle (12), the method comprising: measuring, via the sensor (50), a battery parameter; and causing the GW (52) to transmit one or both of the battery parameter and one or more additional parameters, the transmitted one or both of the battery parameter and the one or more additional parameters being usable to determine an indication indicating whether to start or stop vehicle idling.

10. The method of Claim 9, wherein the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

11. The method of any one of Claims 9 and 10, wherein the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

12. The method of any one of Claims 9-11, wherein the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

13. The method of any one of Claims 9-12, wherein the indication is based on whether the one or more batteries (16) are predicted to meet or exceed a performance condition while the vehicle (12) is not idling.

14. The method of any one of Claims 9-13, wherein the indication to stop idling is based at least in part on determining that a state of the one or more batteries (16) will support a subsequent vehicle (12) cranking operation.

15. The method of any one of Claims 9-14, further comprising: communicating with a server (26); transmitting to the server (26) one or both of the battery parameter and the one or more additional parameters; and triggering the server (26) to determine and transmit the indication.

16. The method of any one of Claims 10-15, wherein when an engine of vehicle (12) is running, the state of charge is determined based at least in part on measured current from the one or more batteries (16) and the measured voltage of the one or more batteries (16) and / or battery cells (46).

17. A system (10) comprising vehicle management system, VMS, (22) and a server (26) in communication with the VMS (22), the VMS (22) including a gateway, GW, (52) and a sensor (50) in communication with the GW (52), the sensor (50) being couplable to one or more terminals (44) of one or more batteries (16) associated with a vehicle (12): the VMS (22) comprising processing circuitry (58) configured to: measure, via the sensor (50), a battery parameter; and transmit the measured battery parameter to the GW (52); the GW (52) comprising processing circuitry (142) configured to: receive the measured battery parameter; cause GW (52) to transmit one or both of the battery parameter and one or more additional parameters to the server (26); the server (26) comprising processing circuitry (72) configured to: receive one or both of the battery parameter and one or more additional parameters; and determine and transmit an indication indicating whether to start or stop vehicle idling based on the one or both of the battery parameter and the one or more additional parameters.

18. The system (10) of Claim 17, wherein the system (10) further includes one or both of a wireless device, WD, (34) and a management platform, MP, (36) comprising processing circuitry (98,84) configured to receive the indication and perform one or more actions based on the indication.

19. The system (10) of any one of Claims 17 and 18, wherein the system (10) further includes a vehicle control system, VCS, (14) comprising processing circuitry (112) configured to receive the indication and perform one or more actions based on the indication.

20. The system (10) of any one of Claims 18-19, wherein the one or more actions include causing the vehicle (12) to start or stop idling.

21. The system (10) of any one of Claims 17-20, wherein the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

22. The system (10) of any one of Claims 17-21, wherein the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

23. The system (10) of any one of Claims 17-22, wherein the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

24. The system (10) of any one of Claims 17-23, wherein the indication is based on whether the one or more batteries (16) are predicted to meet or exceed a performance condition while the vehicle (12) is not idling.

25. The system (10) of any of Claims 17-24, wherein the indication to stop idling is based at least in part on determining that a state of the one or more batteries (16) will support a subsequent vehicle (12) cranking operation.

26. The system (10) of any of Claims 21-25, wherein when an engine of vehicle (12) is running, the state of charge is determined based at least in part on measured currentfrom the one or more batteries (16) and the measured voltage of the one or more batteries (16) and / or battery cells (46).

27. A method implemented in a system (10) comprising a vehicle management system, VMS, (22) and a server (26) in communication with the VMS (22), the VMS (22) including a gateway, GW, (52) and a sensor (50) in communication with the GW (52), the sensor (50) being couplable to one or more terminals (44) of one or more batteries (16) associated with a vehicle (12), the method comprising: measuring, via the sensor (50), a battery parameter; transmitting the measured battery parameter to the GW(52); receiving, via the GW (52), the measured battery parameter; transmitting one or both of the battery parameter and one or more additional parameters to the server (26); receiving, via the server (26), one or both of the battery parameter and one or more additional parameters; and determining and transmitting an indication indicating whether to start or stop vehicle idling based on the one or both of the battery parameter and the one or more additional parameters.

28. The method of Claim 27, wherein the system (10) further includes one or both of a wireless device, WD, (34) and a management platform, MP, (36), the method further comprising receiving the indication and performing one or more actions based on the indication.

29. The method of any one of Claims 27 and 28, wherein the system (10) further includes a vehicle control system, VCS, (14) the method further comprising, receiving the indication and performing one or more actions based on the indication.

30. The method of any one of Claims 28 and 29, wherein the one or more actions include causing the vehicle (12) to start or stop idling.

31. The method of any one of Claim 27-30, wherein the battery parameter includes one or more of a state of charge, a state of health, a voltage, a current, and a temperature.

32. The method of any one of Claims 27-31, wherein the one or more additional parameters includes one or more of a vehicle parameter, a location, a position, and engine information.

33. The method of any one of Claims 27-32, wherein the indication indicating whether to start or stop vehicle idling is determined based on one or more of an artificial intelligence process, machine learning, and historical results.

34. The method of any one of Claims 27-33, wherein the indication is based on whether the one or more batteries (16) are predicted to meet or exceed a performance condition while the vehicle (12) is not idling.

35. The method of any of Claims 27-34, wherein the indication to stop idling is based at least in part on determining that a state of the one or more batteries (16) will support a subsequent vehicle (12) cranking operation.

36. The method of any of Claims 31-35, wherein when an engine of vehicle (12) is running, the state of charge is determined based at least in part on measured current from the one or more batteries (16) and the measured voltage of the one or more batteries (16) and / or battery cells (46).

Images