WO2017132120A1

WO2017132120A1 - Systems and methods for analyzing mobile equipment operations

Info

Publication number: WO2017132120A1
Application number: PCT/US2017/014684
Authority: WO
Inventors: Philip Rodoni
Original assignee: Rubicon Global Holdings, Llc
Priority date: 2016-01-25
Filing date: 2017-01-24
Publication date: 2017-08-03

Abstract

A system is disclosed for analyzing operation of a service vehicle. The system may have a server, a data collection device, a memory for storing a set of instructions, and a processor In communication with the server, the data collection device, and the memory. The processor may be configured to execute the set of instructions to receive, from the data collection device, fuel consumption data associated with the service vehicle, and to determine time and iocation information associated with the service vehicle. The processor may also be configured to execute the set of instructions to determine an operation being performed by the service vehicle, and to selectively transmit the fuel consumption data to the server based on the operation being performed and the time and Iocation information.

Description

SYSTEMS AND METHODS FOR ANALYZING

MOBILE EQUIPMENT OPERATIONS

DESCRIPTION

Related Applications

[001] This application claims the benefit of priority to, Provisional Application No. 62/286,880 filed on January 25, 2016, the contents of which are expressly incorporated herein by reference.

Teghnical Field

[002] This disclosure generally relate to a tool that assists operation analysis, and more particularly, relates to a tool provided via a mobile device that provides an operation analysis of mobile equipment.

Background

[003] Existing technologies allow a user to monitor the operation of mobile equipment (e.g., a service vehicle) as well as behavior of the driver of the service vehicle. The monitoring can be performed for various purposes, such as promoting safe driving habits, improving security, tracking and reducing fuel consumption of the service vehicle. Under existing technologies, the monitoring system can monitor and log the locations of the service vehicle, and/or the distances travelled by the service vehicle within a pre-determined period. Such a period can be, for example, classified by the driver of the service vehicle as a time during which the service vehicle is being operated for a specific purpose (e.g., for a business use versus for a personal use).

[004] There are a few short-comings with such an arrangement. For example, the driver, when classifying a certain operation of the service vehicle as for a business use (or for a personal use) can introduce errors in the logging, especially when that operation does not fall within the normal course of operation of the service vehicle. The error can be further exacerbated when the monitoring system does not take into consideration the type of the service vehicle (e.g., whether the service vehicle is a piece of mobile equipment specially designed for non-transportation functions), the type of road the service vehicle operates in, and the action taken during the operation of the service vehicle. As a result, the logged data may not be useful for tracking and analyzing the normal operation of the service vehicle. SUMMARY

[005] In one aspect, the disclosure is directed toward a system for analyzing operation of a service vehicle. The system may include a server, a data collection device, a memory for storing a set of instructions, and a processor in communication with the server, the data collection device, and the memory. The processor may be configured to execute the set of instructions to receive, from the data collection device, fuel consumption data associated with the service vehicle, and to determine time and location information associated with the service vehicle. The processor may also be configured to execute the set of instructions to determine an operation being performed by the service vehicle, and to selectively transmit the fuel consumption data to the server based on the operation being performed and the time and location information.

[006] In another aspect, the disclosure is directed toward a method for analyzing a service vehicle. The method may include collecting fuel consumption data associated with the service vehicle, and generating time and location information associated with the service vehicle. The method may also include determining an operation being performed by the service vehicle and selectively transmitting the fuel consumption data to a server based on the operation being performed and the time and location information.

[007] In yet another aspect, the disclosure is directed toward a mobile device for analyzing a service vehicle. The mobile device may include a memory for storing a set of instructions, and a processor in communication with the server, the data collection device, and the memory. The processor may be configured to execute the set of instructions to receive, from an onboard data collection device, fuel consumption data associated with the service vehicle, and to determine time and location information associated with the service vehicle. The processor may also be configured to execute the set of instructions to determine an operation being performed by the service vehicle and to selectively transmit the fuel consumption data to a remote server based on the operation being performed and the time and location information.

[008] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosed embodiments, as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and, together with the description, serve to explain the disclosed embodiments. In the drawings:

[010] Fig. 1 is a block diagram of an exemplary system for analyzing an operation of mobile equipment, consistent with disclosed embodiments;

[011] Fig. 2 is a block diagram of an exemplary server for analyzing an operation of mobile equipment, consistent with disclosed embodiments;

[012] Fig. 3 is a block diagram of an exemplary system for analyzing an operation of mobile equipment consistent with disclosed embodiments;

[013] Fig. 4 is a block diagram of an exemplary mobile application device for analyzing an operation of mobile equipment, consistent with disclosed embodiments;

[014] Fig. 5 is a flowchart of an exemplary method for analyzing an operation of mobile equipment, consistent with disclosed embodiments;

[015] Fig. 6 is a flowchart of an exemplary method for analyzing an operation of mobile equipment, consistent with disclosed embodiments;

[016] Figs. 7A and 7B are illustrations of an exemplary user interface for monitoring an operation of mobile equipment, consistent with disclosed

embodiments; and

[017] Figs. 8A and 8B are illustrations of an exemplary user interface for displaying an analysis of an operation of mobile equipment, consistent with disclosed embodiments.

DETAILED DESCRIPTION

[018] Reference will now be made in detail to the disclosed embodiments, examples of which are illustrated in the accompanying drawings. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[019] In one aspect, a mobile device for analyzing an operation of mobile equipment is provided. The mobile device may include a memory device for storing a set of instructions, and one or more hardware processors configured to execute the set of instructions to receive, from one or more data collection devices, fuel consumption data associated with the mobile equipment, and to determine time and location information associated with the mobile equipment. The one or more hardware processors of the mobile device can also be configured to determine, based on the time and location information, an operation by the mobile equipment; to transmit data representing the operation to a server; and to receive, from the server, data representing an analysis of the data representing the operation.

[020] The exemplary disclosed embodiments allow the analysis of an operation of mobile equipment based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the analysis can be more specific, efficient, and accurate. A result of the analysis can be provided to a user, through a mobile application on a mobile device. The mobile application also allows the user to configure the logging of the operation, to further improve the specificity and efficiency of the analysis.

[021] Fig. 1 is a diagram illustrating an exemplary system 100 for analyzing an operation of mobile equipment, consistent with the disclosed embodiments. The mobile equipment can include, for example, a service vehicle that is designed for transportation (e.g., a trash-hauler), equipment designed for non-transportation function (e.g., a mobile office trailer, a mobile crane, etc.), etc. In one embodiment, system 100 may include a mobile equipment operation analyzing device 110, one or more data collection devices 120, client device 130, and a network 140. The components and arrangement of the components included in the system 100 may vary. Thus, the system 100 may further include other components that perform or assist in the performance of one or more processes consistent with the disclosed embodiments.

[022] Mobile equipment operation analyzing device 110 may include one or more computing systems that are configured to execute software instructions stored on one or more memory devices to perform one or more operations consistent with the disclosed embodiments. Mobile equipment operation analyzing device 110 may include one or more of a server, a computer, an embedded system, or a dedicated hardware device. In certain embodiments, mobile equipment operation analyzing device 110 may be configured as a particular apparatus, system, and the like based on the storage, execution, and/or implementation of the software instructions that perform one or more operations consistent with the disclosed embodiments.

[023] In some embodiments, mobile equipment operation analyzing device 110 may include hardware and/or software components configured to determine an operation performed by the mobile equipment based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. Mobile equipment operation analyzing device 110 can then determine whether to log the operation data based on the determined operation. As an illustrative example, based on a determination that a certain service vehicle is a trash-hauler, and that the service vehicle is located within a boundary of a landfill site during a certain time and on a certain date when the landfill site is open for business, mobile equipment operation analyzing device 110 can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road. Based on this determination, mobile equipment operation analyzing device 110 can then determine to log operation data (e.g., fuel consumption, distance travelled, etc.) associated with the trash-dumping operation during that certain time and on that certain date. As another illustrative example, mobile equipment operation analyzing device 110 can also determine not to log the operation data of that service vehicle, when mobile equipment operation analyzing device 110 determines that the service vehicle is travelling on a public road outside the boundary of the landfill site.

[024] As discussed below, mobile equipment operation analyzing device 110 can perform the determination of analyzing (or not analyzing) operation data based on data provided by data collection devices 120 (e.g., via client device 130), and based on information from a configuration database and a location database (not shown in Fig. 1). Mobile equipment operation analyzing device 110 can also provide a result of the analysis to, for example, client device 130, or other devices for displaying and/or further analysis.

[025] Data collection devices 120 can include hardware and software systems configured to obtain operation data of mobile equipment. The operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment. Although Figs. 1 and 3 illustrate data collection devices 120 and client device 130 are separate devices, it is understood that in some embodiments, at least a part of data collection devices 120 can also be included in client device 130.

[026] The location information can include but not limited to: longitude and latitude of the mobile equipment, direction and speed of movement of the mobile equipment, etc. For example, data collection devices 120 can include a global positioning satellite (GPS) receiver, an accelerometer, a gyroscope, an electronic compass, etc., to provide the aforementioned location information.

[027] The fuel consumption information can be obtained from, for example, an onboard diagnostic (OBD) port that conforms to OBD-II standard, and data collection devices 120 can include hardware and software interfaces to an OBD port to acquire the fuel consumption information. Data indicative of fuel consumption (e.g., distance travelled, odometer reading, engine fuel settings, engine speed and load, etc.) can also be acquired from the OBD port.

[028] Timing information can include times and dates associated with the location and fuel consumption information, and data collection devices 120 can include hardware and software (e.g., a timer) to determine the times and dates. In some embodiments, the timing information can also be obtained by a GPS receiver included in data collection devices 120.

[029] Attribute information can include information that can be used to identify and/or to classify the mobile equipment. The information can include, for example, a service vehicle identification number (VI N), a serial number, a model number, or any information that can be used to determine a type of the mobile equipment (e.g., whether it is a trash-hauler, a mobile office trailer, a mobile crane, etc.). In some embodiments, data collection devices 120 can acquire at least some of the information (e.g., a VIN number) from the OBD port.

[030] Data collection devices 120 can also be configured (e.g., by client device 130) to collect the operation data at a pre-determined rate (e.g., once every minute), and to transmit the operation data (e.g., wirelessly or using any suitable means) to client device 130 and/or mobile equipment operation analyzing device 110.

[031] Client device 130 may be one or more computing systems that are configured to execute software instructions for performing one or more operations consistent with the disclosed embodiments. In some embodiments, client device 130 may be a mobile device (e.g., a tablet, smartphone, etc.), a laptop, a desktop computer, a server, an embedded system, a dedicated hardware device, etc. Client device 130 may include one or more processors configured to execute software instructions stored in memory. Client device 130 may also include software that, when executed by a processor, performs known network-related communication and content display processes. For example, client device 130 may execute browser software that generates and displays interface screens including content on interface hardware (e.g., a display device) included in, or connected to, client device 130. Client device 130 may also execute software that packetizes operation data received from one or more data collection devices 120 according to any suitable protocol (e.g., Transmission Control Protocol/Internet Protocol (TCP/IP)), and transmits the packetized operation data to mobile equipment operation analyzing device 110 via network 140.

[032] In some embodiments, client device 130 may be a mobile device configured to execute one or more mobile applications ("apps"). The app can be mobile equipment monitoring app that provides an interface to receive and display configuration information from a user. Client device 130 can then configure the one or more data collection devices 120 based on the received configuration information. As an illustrative example, based on the configuration information, client device 130 can configure data collection devices 120 to collect specific categories of operation data (e.g., fuel consumption) at a particular location and at a particular time and date.

[033] In some embodiments, the app can also cause client device 130 to perform some of the functionalities of mobile equipment operation analyzing device 110. For example, it may also determine an operation performed by the mobile equipment based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. The app can then determine whether to transmit the operation data to mobile equipment operation analyzing device 110 based on the determined operation. Using the illustrative example discussed above, based on a determination that a certain service vehicle is a trash- hauler, and that the service vehicle is located within a boundary of a landfill site during a certain time and on a certain date when the landfill site is open for business, the app can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road. Based on this determination, the app can determine to cause client device 130 to transmit operation data (e.g., fuel consumption, distance travelled, etc.) associated with that trash-dumping operation during that certain time and on that certain date to mobile equipment operation analyzing device 110, which can then log the data and provide the data for displaying and/or further analysis. As another illustrative example, the app can also determine to instruct client device 130 not to transmit the operation data of that service vehicle, after determining that the service vehicle is travelling on a public road outside the boundary of the landfill site. The app can determine the operation based on operation data received from data collection devices 120, and based on information from a configuration database and a location database (not shown in Fig. 1). With such an arrangement, client device 130 can reduce wireless transmissions to mobile equipment operation analyzing device 110 to reduce power consumption.

[034] Network 140 may be any type of network configured to provide communications between components of system 100. For example, network 140 may be any type of network (including infrastructure) that provides communications, exchanges information, and/or facilitates the exchange of information, such as the Internet, a Local Area Network, Near Field Communication (NFC), WIFI, Bluetooth ®, or other suitable connection(s) that enables the sending and receiving of information between the components of system 100. In other embodiments, one or more components of system 100 may communicate directly through a dedicated communication link(s) (not shown), such as a link between mobile equipment operation analyzing device 110 and client device 130.

[035] Fig. 2 shows an exemplary server 200 for analyzing an operation of mobile equipment, consistent with the present disclosure. In some embodiments, server 200 may correspond to mobile equipment operation analyzing device 110. It should be understood, however, that variations of server 200 may correspond to client device 130, and/or components thereof.

[036] In some embodiments, server 200 may include one or more

processors 210, one or more memories 220, and one or more input/output (I/O) devices 230. According to some embodiments, server 200 may be an embedded system or similar computing device(s) that generate, maintain, and provide web site(s) and/or mobile applications consistent with disclosed embodiments. Server 200 may be standalone, or it may be part of a subsystem, which may be part of a larger system. For example, server 200 may represent distributed servers that are remotely located and communicate over a network (e.g., network 140) or a dedicated network, such as a LAN.

[037] Processor 210 may include one or more known processing devices, such as a microprocessor from the Pentium™ or Xeon™ family manufactured by Intel™, the Turion™ family manufactured by AMD™, or any of various processors manufactured by Sun Microsystems. The disclosed embodiments are not limited to any type of processor(s) configured in server 200.

[038] Memory 220 may include one or more storage devices configured to store instructions used by processor 210 to perform functions related to disclosed embodiments. For example, memory 220 may be configured with one or more software instructions, such as prograrh(s) 222 that may perform one or more operations when executed by processor 210. The disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, memory 220 may include a single program 221 that performs the functions of the server 200, or program 222 could comprise multiple programs.

Additionally, processor 210 may execute one or more programs located remotely from server 200. For example, mobile equipment operation analyzing device 110 and client device 130 may, via server 200, access one or more remote programs that, when executed, perform functions related to certain disclosed embodiments.

Memory 220 may also store data 224 that may reflect any type of information in any format that the system may use to perform operations consistent with the disclosed embodiments.

[039] I/O devices 230 may be one or more devices configured to allow data to be received and/or transmitted by server 200. I/O devices 230 may include one or more digital and/or analog communication devices that allow server 200 to communicate with other machines and devices, such as other components of system 100.

[040] Server 200 may also be communicatively connected to one or more database(s) 240. Server 200 may be communicatively connected to database(s) 240 through network 140. Database 240 may include one or more memory devices that store information and are accessed and/or managed through server 200. By way of example, database(s) 240 may include MS SQL, Oracle™ databases, Sybase™ databases, or other relational databases or non-relational databases, such as Hadoop sequence files, HBase, or Cassandra. The databases or other files may include, for example, data and information related to the source and destination of a network request, the data contained in the request, etc. Systems and methods of disclosed embodiments, however, are not limited to separate databases. In one aspect, system 100 may include database 240. Alternatively, database 240 may be located remotely from the system 100. Database 240 may include computing components (e.g., database management system, database server, etc.) configured to receive and process requests for data stored in memory devices of database(s) 240 and to provide data from database 240.

[041] Fig. 3 is a diagram illustrating an exemplary configuration of the components of system 100, including various additional components and features thereof. It should be understood that the configuration of system 100 depicted in Fig. 3 is exemplary, and that other configurations, including additional and/or alternative components and features are possible.

[042] In some embodiments, mobile equipment operation analyzing device 110 may include features configured to monitor an operation of mobile equipment, and to provide a result of the monitoring (e.g., a log) to client device 130. For example, mobile equipment operation analyzing device 110 may include an equipment operation determination module 302, a fuel consumption determination module 304, and a log generation module 306. For the purposes of this disclosure, "modules" (also known as "engines") may be implemented in software, hardware, firmware, a mix of any of those, or the like. For example, if the disclosed "modules" are implemented in software, they may be stored in a memory associated with mobile equipment operation analyzing device 110. Processors, I/O devices, and memory devices may be used to perform processes to implement and facilitate operations of the modules. Thus, the modules may include code instructions executable by one or more processors, alone or in various combinations with other modules disclosed in this or other embodiments. For example, as shown in Fig. 3, equipment operation determination module 302, fuel consumption determination module 304, and log generation module 306 may be configured to interact with each other, and/or with other modules of mobile equipment operation analyzing device 110, shown or not shown in Fig. 3, to perform functions consistent with disclosed embodiments. In other embodiments, if the disclosed "modules" are implemented in hardware, they may comprise an embedded system or other dedicated hardware configured by machine code, assembly code, or the like to interact with other modules of mobile equipment operation analyzing device 110 to perform functions consistent with disclosed embodiments.

[043] In some embodiments, equipment operation determination module 302 can determine an operation performed by the mobile equipment. For example, equipment operation determination module 302 may be configured to execute software instructions to determine the operation based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. Using the illustrative example discussed above, based on a

determination that a certain service vehicle is a trash-hauler, and that the service vehicle is located within a boundary of a landfill site during a certain time and on a certain date when the landfill site is open for business, mobile equipment operation analyzing device 110 can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road.

[044] Equipment operation determination module 302 can interact with other components of system 100 to collect data for the determination. For example, as shown in Fig. 3, system 100 can also include configuration database 310 and location database 320. Configuration database 310 can store configuration information related to the mobile equipment. For example, configuration database 310 can store a mapping between a VIN number and a type of a service vehicle (e.g., a trash-hauler), or a mapping between any kind of identifier (e.g., a serial number) and any attribute of the mobile equipment (e.g., a mobile crane). By querying configuration database 310, equipment operation determination module 302 can determine a type of the service vehicle (or mobile equipment) for a set of operation data received from data collection devices 120 (via client device 130). For example, equipment operation determination module 302 can match the VIN number included in the operation data (received from OBD of the service vehicle by data collection devices 120) with the data stored in configuration database 310 to determine that operation data is associated with a trash-hauler.

[045] Location database 320 can store information related to different sites where the mobile equipment may be located. For example, location database 320 can store the coordinates (e.g., latitude, longitude, etc.) of various sites (e.g., a landfill site), the operating hours of these sites, etc. As discussed above, mobile equipment operation analyzing device 110 can obtain, as part of operation data, location information and time information from data collection devices 120 (via client device 130). Equipment operation determination module 302 can then compare the location information and time information against the data stored in location database 320, to determine that a service vehicle is operating at a landfill site. Based also on a determination that the service vehicle is trash-hauler, equipment operation determination module 302 can then determine that a set of operation data is associated with a trash-dumping operation at landfill site.

[046] In some embodiments, fuel consumption determination module 304 can determine an amount of fuel consumption during an operation (e.g., determined by equipment operation determination module 302) by the mobile equipment, based on the operation data received from data collection devices 120 and information from configuration database 310. For example, in a case where fuel consumption data is not available from the operation data received from data collection devices 120, fuel consumption determination module 304 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), etc. For example, configuration database 310 can store historical data of fuel consumption of the equipment. The historical data can be associated with a certain speed of movement of the equipment, or with a certain location that indicates a certain operation being performed by the equipment. Based on the operating data (e.g., speed, location, etc.) of tine equipment and the historical data stored at configuration database 310, fuel consumption determination module 304 can then determine an amount of fuel consumption during an operation determined by equipment operation determination module 302. Referring back to the illustrative example above, fuel consumption determination module 304 can estimate an amount of fuel consumption by the trash-hauler within the duration when the trash-hauler operates at a landfill site, based on the speed of movement of the trash- hauler, historical data that reflects a rate of fuel consumption by the trash-hauler when operating at a landfill site, and the amount of time spent by the trash-hauler at the landfill site.

[047] In some embodiments, log generation module 306 can generate data that represent a result of analyzing an operation of the mobile equipment. For example, log generation module 306 can provide a log of fuel consumption by the mobile equipment, as determined by fuel consumption determination module 304, for a specific operation identified by equipment operation determination module 302. For example, based on a determination that a trash-hauler performs trash-dumping at a landfill site during a specific time and on a specific date, by equipment operation determination module 302, log generation module 306 can determine to provide a log of fuel consumption by the trash-hauler when performing the trash-dumping during that specific time and on that specific date. As another example, instead of (or in addition to) fuel consumption, log generation module 306 can also determine to provide a log of speed of movement of the trash-hauler in the landfill site. Further, log generation module 306 can also determine to omit some of the operation data from logging. For example, log generation module 306 can determine to omit the fuel consumption data of the trash-hauler during the time when it is determined to be travelling on a public road. Log generation module 306 can also determine to omit the fuel consumption data of the trash-hauler at a landfill site, if equipment operation determination module 302 determines, based on information stored in location database 320, that the landfill site was not open for business at the time when the trash-hauler is at the landfill site.

[048] In some embodiments, configuration database 310 can store a set of rules governing analysis of operation data, log generation, and/or operation data transmission, and log generation module 306 can determine the scope of data to be analyzed and included in a logging result, based on the rules stored at configuration database 310. As an illustrative example, the rules can define that operation data generated when the mobile equipment is at a certain location is to be logged. As another illustrative example, the rules can also define that operation data generated when the mobile equipment is travelling on a public road is not to be logged. The rules can also define the operation data to be logged (e.g., fuel consumption, duration, distance travelled, etc.). The rules can also be associated with a particular type of mobile equipment, and can have different definitions for different types of mobile equipment (e.g., a trash-hauler versus an a mobile crane).

[049] In some embodiments, some of the rules can be provided by client device 130. For example, as discussed above, client device 130 can provide an interface to receive and display configuration information from a user. After receiving configuration information from the user, client device 130 can also store the received configuration information at configuration database 310.

[050] After performing the analysis of the operation data and generating a logging result, mobile equipment operation analyzing device 110 can then transmit the logging result to a client device (e.g., client device 130) for displaying and/or further analysis. Mobile equipment operation analyzing device 110 can also store the logging result in a database for future analysis. [051] In some embodiments, device 130 may be a mobile device configured to execute mobile application 332. Mobile application 332 can provide an interface to receive and display configuration information from a user. Client device 130 can then configure the one or more data collection devices 120 based on the received configuration information. In some embodiments, Mobile application 332 can also cause client device 130 to perform some of the functionalities of mobile equipment operation analyzing device 110. For example, mobile application 332 can provide at least some of the functionalities of equipment operation determination module 302 and fuel consumption determination module 304, and can cause client device 130 to interact with configuration database 310 and location database 320, to determine an operation of the mobile equipment and the fuel consumption during that operation. Based on the rules governing analysis and log generation stored at configuration database 310, mobile application 332 can cause client device 130 to selectively transmit operation data to log generation module 306 of mobile equipment operation analyzing device 110, which can cause some of the operation data (generated by data collection devices 120) to be omitted from analysis and log generation. With such an arrangement, power consumption of client device 130 can be reduced.

[052] Fig. 4 depicts an exemplary client device 130 in more detail, consistent with disclosed embodiments. Client device 130 may include memory hardware 410, processing hardware 420, and interface hardware 430. Other features of client device 130 may include a location device (e.g., a GPS device) configured to determine a location of client device 130, and may also include a connection device configured to wirelessly connect to network 140 (e.g., a cellular communication device, Wi-Fi Device, etc.).

[053] Client device 130 may be configured to execute a mobile application 450 stored in memory hardware 410. For example, client device 130 may be a smartphone, tablet, or watch configured to run a mobile operating system (e.g., iOS, Android, etc.) which may be compatible with a variety of mobile applications provided by third-party providers. In some embodiments, mobile application 450 provides at least some of the functionalities of mobile application 332 of Fig. 3, which enables client device 130 to provide monitoring of an operation of mobile equipment to a user of client device 130 via mobile application 450.

[054] Client device 130 may operate in conjunction with other devices in order to provide monitoring of an operation of mobile equipment. For example, client device 130 may communicate with mobile equipment operation analyzing device 110, configuration database 310 and location database 320 via network 140, and with data collection devices 120.

[055] Fig. 5 is a flowchart of an exemplary method 500 for analyzing an operation of mobile equipment, consistent with the present disclosure. Method 500 can be performed by client device 130 when executing instructions (e.g., mobile application 332) via processing hardware 420. Client device 130 can be

communicatively coupled (e.g., via network 140) with a remote server that performs at least some of the functionalities (e.g., logging a monitoring result) of mobile equipment operation analyzing device 110, and with data collection devices 120 configured to provide operation data of the mobile equipment.

[056] In step 502, client device 130 may receive operation data of mobile equipment. The operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment. Client device 130 may receive the operation data from data collection devices 120, which can include, for example, a GPS receiver, an interface to OBD ports, a timer, etc.

[057] In step 504, client device 130 may determine configuration information for analyzing the received data. The configuration information may include, for example, a set of rules governing analysis of operation data, log generation and/or transmission of operation data. As an example, as discussed above, the rules can define that operation data generated when the mobile equipment is travelling on a public road is not to be logged. As an extension of such a rule, operation data generated when the mobile equipment is travelling on a public road are is not to be transmitted to the server for logging. Similarly, the rules can also define that operation data generated when the mobile equipment is at a certain location is to be logged, and such operation data is to be transmitted to the server for analysis and logging. Client device 130 can determine the configuration information based on, for example, data stored in configuration database 310, and information provided by a user via an interface provided by the execution of mobile application 332 by client device 130.

[058] In step 506, client device 130 can determine whether to transmit the received operation data to the server, based on the configuration information determined in step 504. For example, based on the configuration information and the operation data (e.g., a VIN number, location and time information, etc.), client device 130 can determine that the operation data is associated with a certain type of service vehicle (e.g., a trash-hauler), and that the operation data is generated when the trash-hauler is operating at a certain landfill rather than travelling on a public road. If the rules in the configuration information define that operation data generated when a trash-hauler is operating at that landfill is to be logged, client device 130 can then determine to transmit the received operation data to the server. On the other hand, if the operation data indicates that the trash-hauler is travelling on a public road, client device 130 can determine not to transmit the received operation data to the server.

[059] If client device 130 determines to transmit the received operation data, in step 508, client device 130 can then transmit the received operation data to the server, in step 510. In some embodiments, client device 130 can also perform additional analysis on the received operation data, and transmit a result of the additional analysis to the server, in step 510. For example, in a case where fuel consumption data is not available from the operation data received from data collection devices 120, client device 130 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), etc. For example, configuration database 310 can store historical data of fuel consumption of the equipment. The historical data can be associated with a certain speed of movement of the equipment, or with a certain location that indicates a certain operation being performed by the equipment. Based on the operating data (e.g., speed, location, etc.) of the equipment and the historical data stored at configuration database 310, client device 130 can then determine an amount of fuel consumption, and transmit data that reflects the amount of fuel consumption (as well as other information such as a location and a time/date associated with tine fuel consumption) to the server, in step 510. Client device 130 can packetize the operation data into data packets according to any suitable protocol (e.g., TCP/IP), and then transmit the packets to the server via network 140. On the other hand, if client device 130 determines not to transmit the received operation data (in step 508), client device 130 can proceed to stop the performance of method 500. [060] Fig. 6 is a flowchart of an exemplary method 600 for analyzing an operation of mobile equipment, consistent with the present disclosure. Method 600 can be performed by a server (e.g., server 200 of Fig. 2) when executing instructions (e.g., programs 222) via processors 210 to perform at least some of the

functionalities of mobile equipment operation analyzing device 110. Server 200 can be communicatively coupled with a client device (e.g., client device 130) configured to transmit operation data of the mobile equipment.

[061] In step 602, server 200 may receive operation data of mobile equipment, in step 602. The operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment. Server 200 may receive the operation data from client device 130 via network 140.

[062] In step 604, server 200 may determine configuration information for analyzing the received data. The configuration information may include, for example, a set of rules governing log generation. Server 200 can determine the configuration information based on, for example, data stored in configuration database 310, and information provided by a user via an interface provided by the execution of mobile application 332 by client device 130.

[063] In step 606, server 200 can determine whether to generate a logging report for the received operation data, based on the configuration information determined in step 604. For example, based on the configuration information and the operation data (e.g., a VIN number, location and time information, etc.), server 200 can determine that the operation data is associated with a certain type of service vehicle (e.g., a trash-hauler), and that the operation data is generated when the trash-hauler is operating at a certain landfill rather than travelling on a public road. If the rules in the configuration information define that operation data generated when a trash-hauler is operating at that landfill is to be logged, server 200 can then determine to log the received operation data. On the other hand, if the operation data indicates that the trash-hauler is travelling on a public road, server 200 can determine to omit the received operation data from logging. In some embodiments, at least part of step 606 can be performed by equipment operation determination module 302 of Fig. 3. [064] If server 200 determines to generate a logging report for the received operation data, in step 608, server 200 can then generate a logging report in step 610. In some embodiments, server 200 can also perform additional analysis on the received operation data before generating the logging report in step 610. For example, in a case where fuel consumption data is not available from the operation data received from client device 130, server 200 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), as well as historical data of fuel consumption of the equipment Based on the operating data (e.g., speed, location, etc.) of the equipment and the historical data stored at configuration database 310, server 200 can then determine an amount of fuel consumption, and associate the amount with other information, such as a location and a time/date, in step 610.

Server 200 can then include the fuel consumption and location and time/date information in the log. Server 200 can also include other operation information, such as a moving speed of the mobile equipment, in the logging report as well. In some embodiments, at least a part of step 610 can be performed by fuel consumption determination module 304 and log generation module 306 of Fig. 3.

[065] Server 200 can provide the logging report in various ways. For example, server 200 can host a web site that includes the logging report. The client device 130 (or any other devices) can then access the web site and display the logging report in a browser. Server 200 can also generate a file (e.g., a spreadsheet, a document file, etc.) that includes data of the logging report, and transmit the file to client device 130 or to any other devices that have suitable software to open and render the file for displaying.

[066] Through the exemplary systems of Figs. 1-4 and exemplary methods of Figs. 5 and 6, the logging of an operation of mobile equipment can be performed based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the logging can be more specific and efficient, which allows more accurate analysis of the operation of the mobile equipment.

[067] Figs. 7A and 7B are illustrations of an exemplary user interface 700 for an monitoring operation of mobile equipment, consistent with the present disclosure. In some embodiments, interface 700 can be provided by client device 130 when executing mobile application 332. As shown in Figs. 7A and 7B, interface 700 includes a map 702, an equipment attribute field 712, and options 722, 724, and 726.

[068] In some embodiments, map 702 provides a graphical representation of an area within which the mobile equipment is located. Map 702 includes

representation of different sites (e.g., recycle centers A and B, landfill site C, construction site D, etc.), the associated boundaries (e.g., boundary 703), and thoroughfares (e.g., public roads X and Y). Map 702 can also include an indication of the location of the mobile equipment (e.g., as denoted by symbol 704). The display of map 702 can be generated and updated based on location information of the mobile equipment (e.g., based on location information provided by data collection devices 120). In some embodiments, interface 700 can also provide other options (not shown in Figs. 7A-C) for manipulating the display of map 702, such as zooming in and out of a particular area in the map.

[069] In some embodiments, equipment attribute field 712 can provide an indication about a type of the mobile equipment of which an operation is being monitored. For example, as shown in Fig. 7 A, an operation of a trash-hauler is being monitored. The type of mobile equipment can be determined based on, for example, VI N number received as part of the operation data provided by data collection devices 120.

[070] In some embodiments, options 722, 724, and 726 may allow a user to select locations and data to be monitored. For example, as shown in Fig. 7 A, option 722 allows a user to select one or more locations from recycle centers A and B, landfill site C, and construction site D, for logging operation data. As an illustrative example, if client device 130 detects a selection of recycle center B from option 722, client device 130 can start logging operation data of the mobile equipment when the mobile equipment is detected to be within boundary 703 (for example, based on the location information from data collection devices 120). Option 724 allows a user to select logging operation data when the mobile equipment is on a public road (e.g., public roads X and Y). As an illustrative example, if client device 130 detects a selection of option 724, client device 130 can start logging operation data of the mobile equipment when the mobile equipment is detected to be on public road Y. Option 726 allows a user to select a certain type of operation data to be logged. For example, as shown in Fig. 7A, option 726 allows a user to select one or more data type to be logged from distance travelled, fuel consumption, or duration. [071] In some embodiments, available options 722, 724, and 726 can be updated based on a type of the mobile equipment. As an illustrative example, as shown in Fig. 7A, option 724 (for logging of operation on a public road) is not available for a trash-hauler. The unavailability can be indicated by, for example, graying-out of the option. However, as shown in Fig. 7B, option 724 is available for a mobile crane. Also, for a trash-hauler, fuel consumption data logging option is provided in option 726, while for a mobile crane, fuel consumption data logging option is not available, and has been grayed-out. Further, options 722 (for selecting a location for logging) can also be updated based on the location of the mobile equipment.

[072] Figs. 8A and 8B are illustrations of an exemplary user interface 800 for displaying operation logs of mobile equipment, consistent with disclosed

embodiments. In some embodiments, interface 800 can include a browser interface configured to display a webpage that includes operation log data hosted by server 200, or any suitable interface configured to display the content of a file transmitted by server 200 that includes the log data. In some embodiments, interface 800 can be provided by client device 130 when executing mobile application 332. As shown in Figs. 8A-B, interface 800 includes an equipment identification field 802, an equipment type field 804, a monitoring period field 806, and a table 808. Table 808 can further include columns 810, 812, 814, 816, and 818.

[073] In some embodiments, equipment Identification field 802 is configured to display identification information of the mobile equipment. The identification information can include, for example, a service vehicle VI N number (as shown in Fig. 8A), an equipment serial number (as shown in Fig. 8B), or any other kinds of information that can be used to identify the equipment. The identification can be part of operation data received by data collection devices 120 (e.g., a VIN number), or determined by client device 130 (e.g., input by a user). Equipment type field 804 is configured to display information that indicates a type of the mobile equipment (e.g., a trash-hauler, a mobile crane, etc.). The type information can be generated by server 200 based on the equipment identification information and configuration data stored in configuration database 310. Monitoring period field 806 is configured to display time and date information of a period within which the monitoring was performed. For example, in this illustrative example, interface 800 displays a result of monitoring within a period between January 1 , 2015 to January 7, 2015. [074] In some embodiments, table 808 is configured to display operation log data generated based on the rules governing log generation stored in configuration database 310. In the illustrative example discussed above, the rules can define that the fuel consumption of a trash-hauler when operating away from a public road is to be logged, as reflected in the data displayed in table 808 of Fig. 8A. In this example, column 810 shows the locations of the trash-hauler where operation data was logged, including recycle centers A and B. Columns 812 and 814 shows the date and time of the operations, while column 816 shows an amount of fuel consumed (in gallons) during the operations.

[075] On the other hand, the rules can also define that the fuel consumption of a mobile crane can be logged regardless of whether the mobile crane is traveling on a public road or being operated on a site. For example, as shown in Fig. 8B, column 810 shows that the fuel consumption of the mobile crane is logged when the mobile crane is within construction site D, and when the mobile crane is travelling on public road Y. Additional information can also be shown in table 808. In this illustrative example, as shown in Fig. 7B, fuel consumption data is not available in the operation data provided by data collection devices 120, but data representing the distances travelled is available. Therefore, in Fig. 8B, an additional column 818 is provided to display information about distance travelled. Further, column 816 of Fig. 8B also includes an indication that the fuel consumption figure is an estimate, while in Fig. 8A, column 816 includes an indication that the figure represents actual fuel consumption.

[076] The exemplary disclosed embodiments allow the analysis of an operation of mobile equipment based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the analysis can be more specific, efficient, and accurate. A result of the analysis can be provided to a user, through a mobile application on a mobile device. The mobile application also allows the user to configure the logging of the operation, to further improve the specificity and efficiency of the analysis.

[077] Computer programs created on the basis of the written description and methods of this specification are within the skill of a software developer. The various programs or program modules can be created using a variety of programming techniques. For example, program sections or program modules can be designed in or by means of Java, C, C++, assembly language, or any such programming languages. One or more of such software sections or modules can be integrated into a computer system, computer-readable media, or existing communications software.

[078] Moreover, while illustrative embodiments have been described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various

embodiments), adaptations or alterations based on the present disclosure. The elements in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering steps or inserting or deleting steps. It is intended, therefore, that the specification and examples be considered as example only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.

Claims

WHAT IS CLAIMED IS:

1. A system for analyzing operation of a service vehicle, comprising: a server; a data collection device; a memory for storing a set of instructions; and a processor in communication with the server, the data collection device, and the memory, the processor being configured to execute the set of instructions to:

receive, from the data collection device, fuel consumption data associated with the service vehicle;

determine time and location information associated with the service vehicle;

determine an operation being performed by the service vehicle; and selectively transmit the fuel consumption data to the server based on the operation being performed and the time and location information.

2. The system of claim 1 , wherein the processor is further configured to execute the set of instructions to receive, from the server, an analysis of the fuel consumption data.

3. The system of claim 1 , wherein the processor is further configured to execute the set of instructions to associate the fuel consumption data with the time and location information.

4. The system of claim 3, wherein the processor is further configured to execute the set of instructions to store an association of the fuel consumption data and the time and location information in the memory as historical data.

5. The system of claim 4, wherein the processor is further configured to execute the set of instructions to determine the fuel consumption data based on the historical data when the fuel consumption data is unavailable from the data collection device.

6. The system of claim 4, wherein the processor is further configured to execute the set of instructions to transmit the association along with the fuel consumption data to the server.

7. The system of claim 1 , wherein the processor is further configured to execute the set of instructions to determine, based on at least one of the fuel consumption data and the time and location information, a type of the service vehicle.

8. The system of claim 7, wherein the processor is further configured to determine the operation being performed based on the time and location information and the type of the service vehicle.

9. The system of claim 1 , wherein the data collection device is mounted onboard the service vehicle.

10. The system of claim 1 , wherein the data collection device, the memory, and the processor form a portion of a mobile device.

11. The system of claim 1 , further including a display, wherein the processor is further configured to execute the set of instructions to show on the display an analysis of the fuel consumption data.

12. The system of claim 1 , wherein the processor is configured to transmit the fuel consumption data based on the operation being performed on or off a public road.

13. The system of claim 1 , further including at least one of a GPS receiver, an accelerometer, a gyroscope, and an electronic compass configured to provide the location information to the processor.

14. The system of claim 1 , wherein the processor is configured to , determine the location information based on the operation being performed by the service vehicle.

15. A method of analyzing operation of a service vehicle, comprising: collecting fuel consumption data associated with the service vehicle; generating time and location information associated with the service vehicle; determining an operation being performed by the service vehicle; and selectively transmitting the fuel consumption data to a server based on the operation being performed and the time and location information.

16. The method of claim 15, further including receiving, from the server, an analysis of the fuel consumption data.

17. The method of claim 16, further including displaying the analysis of the fuel consumption data inside the service vehicle.

18. The method of claim 15, further including making an association of the fuel consumption data with the time and location information.

19. The method of claim 18, further including storing the association of the fuel consumption data and the time and location information in memory as historical data.

20. The method of claim 19, further including determining the fuel consumption data based on the historical data when the fuel consumption data is unavailable.

21. The method of claim 19, further including transmitting the association along with the fuel consumption data to the server.

22. The method of claim 15, further including determining, based on at least one of the fuel consumption data and the time and location information, a type of the service vehicle.

23. The method of claim 22, determining the operation includes

determining the operation based on the time and location information and the type of the service vehicle.

24. A mobile device for analyzing a service vehicle, comprising:

a memory for storing a set of instructions; and a processor configured to execute the set of instructions to:

receive, from an onboard data collection device, fuel consumption data associated with the service vehicle;

determine time and location information associated with the service vehicle;

determine an operation being performed by the service vehicle; and selectively transmit the fuel consumption data to a remote server based on the operation being performed and the time and location information.

25. The mobile device of claim 24, wherein the processor is further configured to execute the set of instructions to determine, based on at least one of the fuel consumption data and the time and location information, a type of the service vehicle.

26. The mobile device of claim 24, further including a display, wherein the processor is further configured to execute the set of instructions to show on the display an analysis of the fuel consumption data.

27. The mobile device of claim 24, wherein the processor is configured to transmit the fuel consumption data based on the operation being performed on or off a public road.

28. The mobile device of claim 24, further including at least one of a GPS receiver, an accelerometer, a gyroscope, and an electronic compass configured to provide the location information to the processor.