Patent Application
20160094425
This disclosure relates generally to telematics and, more particularly, to systems and methods for configuring telematics behavior.
Multiple number and types of machines operate within a remote worksite. Application of wireless communication technology to diagnose the machines from a remote location has improved maintenance process of the machines. Various data gathering systems may be used to collect data associated with state or condition of the monitored machines. The collected data may be transmitted to a central office system, which may subsequently transmit the collected data to customers associated with the machines, such that the customers can remotely monitor the machines based on the transmitted data. The monitoring of the vehicles and the associated data transmission is achieved by the use of telematics system.
The telematics system may include various components to collect data related to the machine performance. The telematics system may collect several types of data, for example, data regarding change in temperature of radiator coolant, change in speed, fuel injection frequency, location, and the like. The telematics system may transmit the collected data to the central office system after predefined time intervals or initiated in real time. The telematics system may transmit the collected data through a wired or wireless communication network, such as a Wi-Fi network, cellular network, a satellite network, and the like. In some cases, it is desirable to configure the behavior of the telematics system based on customer needs and available communication networks.
U.S. Pat. No. 7,551,063 (the '063) to Inbarajan discloses a vehicle email notification method and system that uses customer-selected severity settings to send special notifications to the subscriber. In particular, the '063 patent discloses that the vehicle email notification system builds and sends to the subscriber an email message that contains the dynamic vehicle information along with a diagnostic result indicative of the severity level of a vehicle condition, and that diagnostic result is compared to a customer-supplied severity setting to determine whether additional contact with the subscriber is needed. While the '063 patent may allow the subscriber to receive special notification based on customer-selected severity settings, the system of the '063 patent does not take into account the availability of the communication networks.
The disclosed methods and systems are directed to solve one or more of the problems set forth above and/or other problems of the prior art.
In one aspect, the present disclosure is directed to a machine. The machine includes at least one communication module for communication to and from the machine over a network, The machine also includes a memory. The machine further includes a processor configured to receive a telematics behavior configuration file associated with a subscription number, the telematics behavior configuration file comprising at least a file transfer rule for communication over the network. The processor is also configured to store the telematics behavior configuration file in the memory. The processor is further configured to determine whether the network is available and, in response to a determination that the network is available, transfer and receive data over the network according to the telematics behavior configuration file.
In another aspect, the present disclosure is directed to a central office. The central office includes a memory storing a plurality of telematics behavior configuration files, each one of the telematics behavior configuration files being associated with a subscription number. The central office also includes a processor configured to, in response to receiving an instruction to configure a telematics behavior of a machine according to a first subscription number, transfer a first telematics behavior configuration file associated with the first subscription number to the machine.
In yet another aspect, the present disclosure is directed to a method. The method includes receiving a telematics behavior configuration file associated with a subscription number, the telematics behavior configuration file comprising a file transfer rule for communication over a network. The method also includes storing the telematics behavior configuration file in a memory.
The method further includes determining whether the network is available and, in response to a determination that the network is available, transferring and receiving data over the network according to the telematics behavior configuration file.
Machine 110 may be a fixed machine or mobile machine that may perform some type of operation associated with a particular industry, such as mining, construction, farming, etc. and operate between or within work environments (e.g., a construction site, mine site, power plant, etc.). A non-limiting example of a fixed machine includes an engine system operating in a plant or off-shore environment (e.g., off-shore drilling platform). Non-limiting examples of mobile machines include commercial machines, such as trucks, cranes, earth moving vehicles, mining vehicles, backhoes, material handling equipment, farming equipment, marine vessels, on-highway vehicles, or any other type of movable machine that operates in a work environment.
Machine 110 may include a telematics unit 110a attached thereto. Telematics unit 110a may monitor the operation condition of machine 110, and generate telematics data of the corresponding machine 110. Telematics unit 110a may also periodically transmit at least part of the telematics data to back office 150 over one of satellite network 120 or cellular network 130. Back office 150 may then transmit the telematics data to central office 140 or to a customer associated with machine 110, such as a user, an owner, or a dealer of machine 110. The telematics data may include one or more of operational parameters of machine 110, such as runtime, idle time, fuel consumption, and oil pressure, etc. The telematics data may also include diagnostic result of machine 110, such as the amount of oil life remaining (e.g., on a percentage basis 0-100%), the severity of the machine condition, and whether some action is required to address one or more of the machine conditions.
Telematics unit 110a may have a specific telematics behavior, which may be preconfigured based on customer needs and/or available networks. The telematics behaviors may include at least one of a file storage rule, a power management rule, a file transfer rule, and a call-in interval. The telematics behavior (e.g. file transmission rule) of telematics unit 110a of machine 110 may be preconfigured in accordance with a telematics behavior configuration file stored on-board of machine 110. In addition, the telematics behavior of telematics unit 110a of machine 110 may be varied based on the connectivity between machine 110 and satellite network 120 or cellular network 130. In one exemplary embodiment, machine 110 may be a marine vessel which may be out to sea, and may only be connected to satellite network 120. As a result, marine vessel 110 may transmit only part of its telematics data over satellite network 120 once every week. However, when marine vessel 110 arrives at a port, marine vessel 110 may be connected to cellular network 130, which is relatively more cost effective than satellite network 120. As a result, marine vessel 110 may transmit all of its telematics data over cellular network 130 everyday.
Central office 140 may represent one or more computing systems of an entity associated with machine 110, such as manufacturer, dealer, retailer, or any other entity that manufactures and/or maintains machine 110. Central office 140 may include a processor 141 and a memory 142 storing a plurality of telematics behavior configuration files, each being associated with a subscription number. A customer, such as the user or the owner of machine 110, may select a subscription number for machine 110. Processor 141 may, in response to receiving an instruction to configure the telematics behavior of machine 110, transmit the telematics behavior configuration file corresponding to the selected subscription number to machine 110.
Back office 150 may represent one or more computing systems of an entity that serves as an interface between central office 140 and different network carriers, such as the network carriers of satellite network 120 and cellular network 130. As described previously, back office 150 may receive telematics data transmitted from machine 110, and transmit the telematics data to central office 140 or to a customer associated with machine 110, such as a user, an owner, or a dealer of machine 110. Alternatively, back office 150 may host a web-based application through which the user or the owner of machine 110 can view, sort, manage, and/or analyze the telematics data. Back office 150 may include a processor 151 and a memory 152. Memory 152 may store a map relating each of a plurality of subscription numbers to one of a plurality of combinations of network plans. The network plan may be a satellite plan for communication over satellite network 120, or a cell plan for communication over cellular network 130. The network plan may include the amount of data that may be transmitted and received over the network each month, and the monthly cost. Memory 152 may also store a map relating each of a plurality of machine serial numbers to one of the plurality of subscription numbers. Processor 151 may use the information stored in memory 152 to generate monthly bills to be sent to the user or the owner of machine 110.
Although telematics behavior configuration system 100 in
Processor 210 may include one or more processing devices. For example, processor 210 may include one or more microprocessors from the Pentium™ or Xeon™ family manufactured by Intel™, the Turion™ family manufactured by AMD™, or any other type of processors. As shown in
Sensors 221, 222, and 223 may gather data from various components and subsystems of machine 110. Sensors 221, 222, and 223 may be associated with and/or monitor a power source, a transmission, a traction device, a tool, an exhaust system, a suspension system, and/or other components and subsystems of machine 110. Sensors 221, 222, and 223 may measure and/or sense operational parameters based on the gathered sensor signals, such as, for example, engine RPM, ground speed, track/wheel slip, oil pressure, water temperature, boost pressure, oil contamination, exhaust temperature, NOx level, urea level, electric motor current, hydraulic pressure, system voltage, fuel consumption, payload weight, ground speed, distance traveled, transmission ratio, cycle time, start time, stop time, grade, a global or relative position of machine 110, brake temperature, etc. Sensors 221, 222, and 223 may each generate a signal corresponding to a value of the respective measured operational parameter (e.g., 170° F., 1.5 atm, 1,200 RPM, etc.). Sensors 221, 222, and 223 may generate or maintain other information such as, for example, time of day, date, etc. In some embodiments, sensors 221, 222, and 223 may be integrated within telematics unit 110a. In other embodiments, sensors 221, 222, and 223 may be distributed throughout machine 110. Although in the embodiment illustrated in
Communication modules 231 and 232 may include any hardware and/or software (e.g., a multiplexer/demultiplexer, a transceiver, a signal modulator, an amplifier, an antenna, etc.) that are configured to facilitate communications between machine 110 and central office 140 over respective networks 120 and 130. That is, communication module 231 may enable machine 110 to send and/or receive data over satellite network 120, and communication module 232 may enable machine 110 to send and/or receive data over cellular network 130.
Memory 240 may include a non-volatile, magnetic, semiconductor, tape, optical, removable, nonremovable, or other type of storage device or computer-readable medium. Memory 240 may store one or more telematics applications 241, telematics data 242, and a telematics behavior configuration file 243.
The one or more telematics applications 241 may enable processor 210 to analyze the data gathered by sensors 221, 222, and 223, and may generate diagnostic data regarding machine 110. One example of the telematics application 241 is a geo fence application, which may compare the current location of machine 110 to a predefined boundary, i.e., a geo fence, and may generate alert data when machine 110 approaches or move across the geo fence.
Telematics data 242 may include one or more of operational parameters of machine 110, such as runtime, idle time, fuel consumption, and oil pressure, etc. Telematics data 242 may also include diagnostic result of machine 110, such as the amount of oil life remaining (e.g., on a percentage basis 0-100%), the severity of the machine condition, and whether some action is required to address one or more of the machine conditions. Telematics data 242 may be stored in one or more tables, arrays, matrices, or other suitable data storage structures.
Telematics behavior configuration file 243 may be used to configure different types of telematics behaviors of machine 110. The different types of telematics behaviors may include at least one of a file storage rule, a power management rule, a file transfer rule, and a call-in interval. Some types of telematics behaviors, such as the file transfer rule and the call-in interval, may be further varied based on the connectivity between machine 110 and satellite network 120 or cellular network 130. Further description regarding telematics behavior configuration file 243 will be provided with reference to
Subscription 1 may be associated with a first telematics behavior configuration file, such that When a user or an owner of machine 110 selects subscription 1, processor 141 may transmit the first telematics behavior configuration file to machine 110. Subscription 1 may be applicable to a machine that includes only one communication module 232 for communication over cellular network 130. Subscription 1 may also be applicable to a machine that includes both of communication module 231 for communication over satellite network 120, and communication module 232 for communication over cellular network 130, but only communication module 232 is enabled. As illustrated in
Subscription 2 may be associated with a second telematics behavior configuration file, such that when the user or the owner of machine 110 selects subscription 2, processor 141 may transmit the second telematics behavior configuration file to machine 110. Subscription 2 may also be applicable to a machine that includes both communication module 231 for communication over satellite network 120 and communication module 232 for communication over cellular network 130. As illustrated in
The disclosed telematics system and method may configure telematics behavior of one or more machines by specifying a set of rules for file storage, power management, file transfer, and call-in interval. The set of rules may be further specified based on customer needs and available communication networks, such as a cellular network, a satellite network, a WiFi network, and an Ethernet network. The disclosed telematics system and method may facility a dual mode communication, i.e., communication over two different networks, or multi mode communication, i.e., communication over three or more networks. Specifically, the telematics behavior of machine 110 may be configured based on a customer-selectable subscription number. The customized telematics behavior provides for efficient communication and remote management of machines and fleets.
It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed telematics configuration system. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed parts forecasting system. It is intended that the specification and examples be considered as exemplary only, with a true scope being indicated by the following claims and their equivalents.
