US10075576B1 - Starting a machine through a mobile device - Google Patents

Starting a machine through a mobile device Download PDF

Info

Publication number
US10075576B1
US10075576B1 US15/654,818 US201715654818A US10075576B1 US 10075576 B1 US10075576 B1 US 10075576B1 US 201715654818 A US201715654818 A US 201715654818A US 10075576 B1 US10075576 B1 US 10075576B1
Authority
US
United States
Prior art keywords
mobile device
machine
random number
controller
key
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US15/654,818
Inventor
Jeffrey David Rule
Kirk Shively
Derek J. Light
Joshua Dean Reed
Bradley Bergerhouse
Arjun Veneshetty
Sudhakar Subramaniyan
Rohinikumar Adivi
Harold Duane Dabbs
Paul William Bierdeman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Caterpillar Inc
Original Assignee
Caterpillar Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Caterpillar Inc filed Critical Caterpillar Inc
Priority to US15/654,818 priority Critical patent/US10075576B1/en
Assigned to CATERPILLAR INC. reassignment CATERPILLAR INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BERGERHOUSE, Bradley, DABBS, HAROLD DUANE, SUBRAMANIYAN, SUDHAKAR, ADIVI, ROHINIKUMAR, BIERDEMAN, PAUL WILLIAM, RULE, JEFFREY DAVID, LIGHT, DEREK J., REED, JOSHUA DEAN, SHIVELY, KIRK, VENESHETTY, Arjun
Application granted granted Critical
Publication of US10075576B1 publication Critical patent/US10075576B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H04M1/72527—
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R25/00—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles
    • B60R25/20—Means to switch the anti-theft system on or off
    • B60R25/209—Remote starting of engine
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R25/00—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles
    • B60R25/20—Means to switch the anti-theft system on or off
    • B60R25/24—Means to switch the anti-theft system on or off using electronic identifiers containing a code not memorised by the user
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/20—Drives; Control devices
    • E02F9/2025—Particular purposes of control systems not otherwise provided for
    • E02F9/205—Remotely operated machines, e.g. unmanned vehicles
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72415—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories for remote control of appliances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F3/00—Dredgers; Soil-shifting machines
    • E02F3/04—Dredgers; Soil-shifting machines mechanically-driven
    • E02F3/28—Dredgers; Soil-shifting machines mechanically-driven with digging tools mounted on a dipper- or bucket-arm, i.e. there is either one arm or a pair of arms, e.g. dippers, buckets
    • E02F3/36—Component parts
    • E02F3/42—Drives for dippers, buckets, dipper-arms or bucket-arms
    • E02F3/43—Control of dipper or bucket position; Control of sequence of drive operations
    • E02F3/435—Control of dipper or bucket position; Control of sequence of drive operations for dipper-arms, backhoes or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces

Definitions

  • the present disclosure relates to remotely starting a machine. More particularly, the present disclosure relates to remotely starting a machine through a mobile device.
  • a more specific example can be considered of a worksite where multiple operators work with multiple machines. The operators, as per requirements on the worksite, are allowed to access the machines for which they are authorized through mobile devices.
  • the '127 reference discloses a working machine provided with a control device that can make wireless communication with a mobile terminal storing a mobile-use identification (ID) code and stores a working machine-use ID code.
  • the control device is provided with ID code checking means to check the mobile-use ID code obtained by ID code obtaining means and the working machine-use ID code with each other. Data communication between the mobile terminal and the control device is allowed once the matching between the ID codes is established.
  • the ID codes are fixed and once an operator knows the codes, he/she can always have access to the machine even if the authorization is revoked or changed.
  • a method to access a machine through a mobile device includes sending a machine key to a controller on-board the machine using a remote server.
  • the remote server is located at an off-board location relative to the machine.
  • the method includes sending a mobile device key to the mobile device using the remote server.
  • the method includes sending a mobile device ID associated with the mobile device to the controller using the mobile device.
  • the method includes determining the mobile device key based at least on the mobile device ID and the machine key through the controller.
  • the method includes sending a random number to the mobile device using the controller.
  • the method includes processing the random number based on the mobile device key to derive a first processed random number through the mobile device.
  • the method includes sending the first processed random number to the controller using the mobile device.
  • the method includes processing the random number based on the determined mobile device key to derive a second processed random number through the controller.
  • the method includes comparing the first processed random number and the second processed random number through the controller.
  • the method includes enabling a start button for sending a request to start the machine, when the first processed random number matches the second processed random number.
  • the method further includes starting the machine upon receiving the request to start the machine through the use of the start button.
  • a control system to access a machine includes a remote server located at an off-board location relative to the machine.
  • the remote server generates a mobile device ID, a mobile device key and a machine key.
  • the control system includes a mobile device having an associated mobile device ID and a mobile device key.
  • the mobile device receives the mobile device ID and the mobile device key from the remote server.
  • the control system further includes a controller on-board the machine.
  • the controller receives the mobile device ID from the mobile device.
  • the controller receives the machine key from the remote server.
  • the controller determines the mobile device key based on the mobile device ID and the machine key.
  • the controller sends a random number to the mobile device.
  • the controller receives a first processed random number from the mobile device.
  • the mobile device determines the first processed random number based on the mobile device key.
  • the controller processes the random number based on the determined mobile device key to determine a second processed random number.
  • the controller compares the first processed random number with the second processed random number.
  • the controller enables a start button for sending a request to start the machine, when the first processed random number matches the second processed random number. Furthermore, the controller starts the machine upon receiving the request to start the machine through the use of the start button.
  • a machine including a controller on-board the machine.
  • the controller receives a mobile device ID from a mobile device.
  • the controller receives a machine key from a remote server.
  • the controller determines a mobile device key based on the mobile device ID and the machine key.
  • the controller sends a random number to the mobile device.
  • the controller receives a first processed random number from the mobile device.
  • the mobile device determines the first processed random number based on the mobile device key received from the remote server.
  • the controller processes the random number based on the determined mobile device key to determine a second processed random number.
  • the controller compares the first processed random number with the second processed random number.
  • the controller enables a start button for sending a request to start the machine, when the first processed random number matches the second processed random number. Furthermore, the controller starts the machine upon receiving the request to start the machine through the use of the start button.
  • FIG. 1 shows an exemplary worksite showing an exemplary machine and an operator carrying a mobile device, according to an aspect of the present disclosure
  • FIG. 2 schematically shows a control system for starting the machine through the mobile device, according to an aspect of the present disclosure
  • FIG. 3 shows the remote server storing a list of operators and corresponding mobile device IDs, according to an aspect of the present disclosure
  • FIG. 4 shows a machine key being determined by the remote server based on various inputs, according to an aspect of the present disclosure
  • FIG. 5 shows a list of machines and corresponding operators authorized to operate the machine, according to an aspect of the present disclosure
  • FIG. 6 shows communication between a controller and the remote server, according to an aspect of the present disclosure
  • FIG. 7 shows a mobile device key being determined by the remote server based on various inputs, according to an aspect of the present disclosure
  • FIG. 8 shows communication between a mobile device and the remote server, according to an aspect of the present disclosure
  • FIG. 9 shows communication between the mobile device and the controller, according to an aspect of the present disclosure
  • FIG. 10 shows the mobile device key being determined by the controller based on various inputs, according to an aspect of the present disclosure
  • FIG. 11 shows a first processed random number being determined by the mobile device based on various inputs, according to an aspect of the present disclosure
  • FIG. 12 shows a second processed random number being determined by the controller based on various inputs, according to an aspect of the present disclosure
  • FIG. 13 shows a comparison data being determined by the controller based on various inputs, according to an aspect of the present disclosure
  • FIG. 14 shows steps taken after comparison data is determined, according to an aspect of the present disclosure
  • FIG. 15 shows communication between the mobile device and the controller, according to an aspect of the present disclosure.
  • FIG. 16 shows a flow chart of a method to start the machine through the mobile device, according to an aspect of the present disclosure.
  • FIG. 1 shows an exemplary machine 100 at a worksite 101 at which one or more machines 100 may be operating to perform various tasks.
  • the machine 100 is illustrated as a hydraulic excavator, the machine 100 may be any other type of a work machine as well which may perform a repetitive work cycle of operations associated with industries such as mining, construction, farming, transportation, landscaping, or the like. Examples of such machines may include wheel loaders, hydraulic shovels, dozers, dump trucks etc. While the following detailed description describes an exemplary aspect in connection with the hydraulic excavator, it should be appreciated that the description applies equally to the use of the present disclosure in other machines as well.
  • the machine 100 includes an operator station 102 to accommodate an operator 106 for operating the machine 100 to perform various tasks.
  • the operator station 102 includes various controls and input means through which the operator 106 may provide inputs to control the machine 100 .
  • the machine 100 includes an on-board controller 104 which may control various operational parameters of the machine 100 .
  • the controller 104 may be communicably coupled to various systems of the machine 100 such as an ignition system, a propulsion system, etc.
  • the controller 104 may control various functions of the machine 100 to operate the machine 100 in a desired manner.
  • the controller 104 may also be configured to communicate with devices or systems which may not be a part of the machine 100 through various communication medium such as Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, Near Field Communication (NFC), wireless communication systems, etc.
  • NFC Near Field Communication
  • FIG. 1 shows the operator 106 standing on the worksite 101 .
  • the operator 106 is illustrated as carrying a mobile device 108 in his hand.
  • the operator 106 may carry the mobile device 108 in his pocket or may hold the mobile device 108 in his hand while working on the worksite 101 .
  • the mobile device 108 may be a smart phone, a tablet, or any other such device which may be suitable for application in various aspects of the present disclosure.
  • the mobile device 108 may be configured to send/receive messages to other devices via Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc.
  • the operator 106 may use the mobile device 108 to start the machine 100 without requirement of any physical key.
  • the operator 106 may also use the mobile device 108 to start the machine 100 without being physically present on the machine 100 .
  • the operator 106 may be outside the operator station 102 , or near the machine 100 , or the operator 106 may also be at a remote back-office.
  • the illustrated embodiment shows only one operator 106 on the worksite 101 , there may be any number of operators 106 on the worksite 101 which may carry respective mobile devices 108 .
  • the mobile device 108 may have a mobile application installed, which may allow the mobile device 108 to start the machine 100 based on appropriate authentication procedures being followed. The authentication procedures will be described in detail in the forthcoming description.
  • the mobile application may store a list of machines 100 which the operator 106 carrying the mobile device 108 may be authorized to operate.
  • the operator 106 may run the mobile application on the mobile device 108 and select the machine 100 which the operator 106 wishes to operate.
  • FIG. 2 schematically illustrates a control system 200 to start the machine 100 through the mobile device 108 .
  • the control system 200 includes the mobile device 108 , the controller 104 and a remote server 202 .
  • the mobile device 108 includes one or more transceivers 204 to communicate with other devices and systems.
  • the transceiver 204 may send/receive messages or data through any suitable communication medium including one or more of Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc. Although, two transceivers 204 are illustrated, there may be any number of transceivers 204 provided on the mobile device 108 .
  • the mobile device 108 includes a processor 206 to perform various calculations and to process data which may be required for authentication procedures.
  • the mobile device 108 also includes a user interface 208 for enabling the operator 106 to operate the mobile device 108 .
  • the user interface 208 may be a touch screen, a keypad, or any other such kind of a user interface which may allow the operator 106 to provide desired inputs to the processor 206 of the mobile device 108 .
  • the user interface 208 is a touch screen through which the operator 106 may provide inputs to the mobile device 108 .
  • the mobile device 108 has an associated mobile device ID 209 .
  • the mobile device ID 209 may be a unique identification code which may be used to identify the mobile device 108 .
  • the mobile device ID 209 is a Universal Unique Identifier (UUID).
  • the mobile device ID 209 is an International Mobile Equipment Identity (IMEI) number of the mobile device 108 .
  • IMEI International Mobile Equipment Identity
  • the controller 104 has an associated memory 210 to store various operational parameters as well as other relevant information.
  • the controller 104 includes a processor 212 to perform various tasks and calculations required as per various aspects of the present disclosure.
  • the controller 104 also includes one or more transceivers 214 which may send and receive signals to communicate with other components of the control system 200 such as the mobile device 108 and the remote server 202 .
  • the transceivers 214 may send/receive messages or data through any suitable communication medium including Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc. It should be contemplated that although the FIG. 2 shows that the controller 104 includes two transceivers 214 , the controller 104 may have any suitable number of transceivers 214 which may suit the need of the present disclosure.
  • the controller 104 is coupled to an interface 216 such as a graphical user interface of the machine 100 so that the operator 106 may provide inputs for operating the machine 100 .
  • the interface 216 may be a touch screen, a keypad, a joystick or any other such kind of a user interface which may allow the operator 106 to provide desired inputs to the machine 100 .
  • the interface 216 may include a start button through which the operator 106 may send a request to the controller 104 to start the machine 100 .
  • the controller 104 is also coupled to an engine 218 of the machine 100 .
  • the machine 100 may be represented by an associated machine ID 219 .
  • the machine ID 219 may be any unique identifier which may be used to refer to or identify the machine 100 .
  • the machine ID 219 may be a unique serial number which may be assigned to the machine 100 .
  • the machine ID 219 may be a chassis number or a Vehicle Identification Number (VIN) which may be used to uniquely identify the machine 100 .
  • the machine ID 219 may be generated during or post manufacturing of the machine 100 .
  • the remote server 202 is located at an off-board location relative to the machine 100 .
  • the remote server 202 may be a back-office, a control room, or any other such type of location which may be used to remotely monitor and control the machine 100 .
  • the remote server 202 includes a processor 220 to perform various tasks.
  • the remote server 202 also includes one or more transceivers 222 to communicate with other devices and systems.
  • the remote server 202 is communicably coupled to the controller 104 and the mobile device 108 .
  • the controller 104 and the mobile device 108 are communicably coupled to each other as well.
  • the remote server 202 , the controller 104 , and the mobile device 108 may communicate to each other via Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc.
  • the remote server 202 may store information about the operators 106 and the machines 100 working on the worksite 101 . Each operator 106 carries the corresponding mobile device 108 .
  • the remote server 202 stores a list 300 of the operators 106 and the corresponding mobile device IDs 209 as shown in FIG. 3 .
  • the remote server 202 may store information about the operator 106 and link the mobile device ID 209 of the respective mobile device 108 to the operator 106 .
  • the controller 104 may also store the list 300 of authorized operators 106 allowed to operate the machine 100 .
  • the remote server 202 may send the list 300 of the operators 106 to the controller 104 .
  • the remote server 202 derives and stores a machine key 400 associated with each of the machines 100 operating on the worksite 101 .
  • the machine key 400 may be an encryption key which may be used to encrypt or decrypt any information which needs to be shared by the machine 100 or which is shared with the machine 100 .
  • FIG. 4 illustrates various components of the machine key 400 .
  • the remote server 202 may derive the machine key 400 from the machine ID 219 , a first key 402 , and a first fixed random data 404 .
  • the first key 402 may be a confidential serial number or an alpha numeric code or any other such set of characters which may be suitable for use in various aspects of the present disclosure.
  • the remote server 202 may generate the first key 402 , or a person who may be authorized to access information about all the machines 100 and the operators 106 may set the first key 402 .
  • the first fixed random data 404 may be a random data generated by any conventional random data generation algorithms already known in the art.
  • the remote server 202 may include any such algorithm which may generate the first fixed random data 404 .
  • FIG. 5 shows the remote server 202 stores a list 500 of the operators 106 authorized to operate each of the machines 100 .
  • the list 500 includes the operators 106 along with the corresponding mobile device IDs 209 which may be authorized to operate the machine 100 for each of the machines 100 .
  • FIG. 6 illustrates sequence of exchange of information between the remote server 202 and the controller 104 when the remote server 202 shares the machine key 400 with the controller 104 .
  • the controller 104 sends a request to the remote server 202 to send the machine key 400 to the controller 104 .
  • the controller 104 sends the machine ID 219 so that the remote server 202 may appropriately identify the machine 100 , and send the machine key 400 corresponding to the machine 100 from which the controller 104 has sent the request.
  • the remote server 202 sends the machine key 400 to the controller 104 .
  • the remote server 202 also sends the list 300 of authorized mobile device IDs 209 to the controller 104 .
  • the remote server 202 may be a website.
  • the controller 104 may be configured to periodically check the remote server 202 for machine key 400 files for the machine 100 . In case there is a new machine key 400 available for the machine 100 , the controller 104 may download the new machine key 400 by providing the machine ID 219 as credentials on the website to authenticate the download process.
  • the remote server 202 derives and stores a mobile device key 700 .
  • the mobile device key 700 may be an encryption key which may be used to encrypt or decrypt any information which needs to be shared by the mobile device 108 or which is shared with the mobile device 108 .
  • FIG. 7 illustrates various components of the mobile device key 700 .
  • the remote server 202 may derive the mobile device key 700 from the machine key 400 , the mobile device ID 209 , and a second fixed random data 702 . Any conventional random data generation algorithms already known in the art may be used to generate the second fixed random data 702 .
  • the remote server 202 may include any such algorithm which may generate the second fixed random data 702 .
  • FIG. 8 illustrates sequence of exchange of information between the mobile device 108 and the remote server 202 , when the remote server 202 shares the mobile device key 700 with the mobile device 108 .
  • the mobile device 108 sends a request to the remote server 202 to send the mobile device key 700 to the mobile device 108 .
  • the mobile device 108 sends a unique identifier 800 which may be unique to the mobile application installation so that the remote server 202 may appropriately identify the mobile device 108 , and send back the mobile device ID 209 corresponding to the mobile device 108 which has sent the request.
  • the remote server 202 may also send a list 500 of mobile device keys 700 along with corresponding machine IDs 219 for a given mobile device ID 209 .
  • the remote server 202 may be a website, or a web address.
  • the mobile device 108 may access the website and download the mobile device key 700 from the website.
  • the mobile device 108 may access the remote server 202 through a user login process, and then the mobile device 108 may send the unique identifier 800 to the remote server 202 , and the remote server 202 sends back the mobile device ID 209 to the mobile device 108 .
  • FIG. 9 schematically represents the sequence of communication occurring between the mobile device 108 and the controller 104 to authenticate the mobile device 108 for starting the machine 100 .
  • the mobile device 108 sends the mobile device ID 209 to the controller 104 .
  • the mobile device 108 sends the mobile device ID 209 to the controller 104 when the operator 106 is less than a pre-determined distance away from the machine 100 .
  • the controller 104 receives the mobile device ID 209 through the transceiver 214 .
  • the controller 104 determines the mobile device key 700 by using the received mobile device ID 209 as shown in FIG. 10 .
  • the controller 104 determines the mobile device key 700 from the mobile device ID 209 , the machine key 400 , and the second fixed random data 702 .
  • the controller 104 may receive the second fixed random data 702 from the remote server 202 .
  • the second fixed random data 702 is a fixed random data value which may be generated through any random data generation algorithm known in the art.
  • the controller 104 sends a random number 900 to the mobile device 108 .
  • the controller 104 may match the mobile device ID 209 with the list 300 of the mobile device IDs 209 stored in the memory 210 of the controller 104 .
  • the list 300 includes one or more pre-stored mobile device IDs 209 in the memory 210 of the controller 104 .
  • the controller 104 checks if the mobile device ID 209 matches any one of the pre-stored mobile device IDs 209 . When the mobile device ID 209 does not match any of the pre-stored mobile device IDs 209 , the controller 104 blocks the mobile device 108 from communicating with the controller 104 for a pre-determined time period.
  • the pre-determined time period may be one minute.
  • the pre-determined time period may be adjustable based on response frequency of the mobile device 108 and the controller 104 . No further processing is done when the mobile device ID 209 does not match any of the pre-stored mobile device IDs 209 .
  • the controller 104 sends the random number 900 to the mobile device 108 .
  • the controller 104 may also temporarily store the random number 900 in the memory 210 .
  • the random number 900 may be generated by any random data generation algorithm known in the art which may be suitable for the application in various aspects of the present disclosure.
  • the random number 900 may also be an alphanumeric code, a sequence of letters or any other such random sequence of characters.
  • the mobile device 108 receives the random number 900 from the controller 104 and processes the random number 900 as shown in FIG. 11 .
  • the mobile device 108 makes use of the mobile device key 700 to process the random number 900 and derives a first processed random number (FPRN) 1100 .
  • the FPRN 1100 is an outcome of the mobile device key 700 being used to encrypt the random number 900 by the mobile device 108 .
  • the mobile device 108 then sends the FPRN 1100 to the controller 104 .
  • the controller 104 may receive the FPRN 1100 through the transceiver 214 .
  • the controller 104 also processes the random number 900 as shown in FIG. 12 .
  • the controller 104 makes use of the determined mobile device key 700 to process the random number 900 .
  • the controller 104 processes the random number 900 to derive a second processed random number (SPRN) 1200 .
  • the SPRN 1200 is an outcome of the determined mobile device key 700 being used to encrypt the random number 900 by the controller 104 .
  • the controller 104 compares the FPRN 1100 and the SPRN 1200 as shown in FIG. 13 . Both the FPRN 1100 and the SPRN 1200 essentially represent the random number 900 processed by the mobile device key 700 , the only difference being that the FPRN 1100 is processed by the mobile device 108 , and the SPRN 1200 is processed by the controller 104 .
  • the controller 104 determines a comparison data 1300 from the comparison of the FPRN 1100 and the SPRN 1200 .
  • the controller 104 now sends an authentication response message 902 to the mobile device 108 after the comparison.
  • the authentication response message 902 may include information about results of the comparison between the FPRN 1100 and the SPRN 1200 .
  • FIG. 14 illustrates further steps after comparison data 1300 is determined.
  • the controller 104 compares the FPRN 1100 and the SPRN 1200 to check if the FPRN 1100 matches the SPRN 1200 .
  • the controller 104 may send an authentication verification message 1500 to the mobile device 108 , stating that the mobile device 108 is now authenticated and subsequently, enables the start button on the mobile device 108 and may be on the user interface 216 of the machine 100 .
  • the operator 106 uses the start button either on the mobile device 108 or the user interface 216 on the machine 100 to send a request 1502 , as shown in FIG. 15 to the controller 104 to start the machine 100 .
  • the controller 104 may receive the request 1502 to start the machine 100 through the use of the start button. Subsequently, in block 1406 , the controller 104 starts the machine 100 after receiving the request 1502 .
  • the controller 104 blocks the mobile device 108 from connecting with the machine 100 for a pre-determined time period.
  • the pre-determine time period may be one minute.
  • the pre-determined time period may be adjustable based on response frequency of the mobile device 108 and the controller 104 .
  • the present disclosure provides an improved method 1600 to start the machine 100 through the mobile device 108 as shown in FIG. 16 .
  • the remote server 202 sends the machine key 400 to the controller 104 .
  • the machine key 400 may be an encryption key.
  • the remote server 202 may derive the machine key 400 based on the machine ID 219 , the first key 402 , and the first fixed random data 404 . Any conventional random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, may generate the first fixed random data 404 .
  • the remote server 202 sends the mobile device key 700 to the mobile device 108 .
  • the mobile device key 700 may be an encryption key.
  • the remote server 202 may derive the mobile device key 700 from the machine key 400 , the mobile device ID 209 , and the second fixed random data 702 . Any conventional random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, may be used to generate the second fixed random data 702 .
  • the mobile device 108 sends the mobile device ID 209 associated with the mobile device 108 to the controller 104 .
  • the controller 104 may receive the mobile device ID 209 through the transceiver 214 .
  • the controller 104 determines the mobile device key 700 based at least on the mobile device ID 209 and the machine key 400 . In an embodiment, the controller 104 determines the mobile device key 700 based on the machine key 400 , the mobile device ID 209 , and the second fixed random data 702 . In block 1610 , the controller 104 sends the random number 900 to the mobile device 108 .
  • the controller 104 may use any suitable random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, to generate the random number 900 .
  • the mobile device 108 processes the random number 900 by using the mobile device key 700 to derive the FPRN 1100 .
  • the mobile device 108 sends the FPRN 1100 to the controller 104 .
  • the controller 104 processes the random number 900 based on the determined mobile device key 700 to derive the SPRN 1200 .
  • the controller 104 may process the random number 900 through the processor 212 which may be configured to perform such calculations.
  • the controller 104 compares the FPRN 1100 and the SPRN 1200 .
  • the controller 104 enables the start button to send the request 1502 to start the machine 100 , when the FPRN 1100 matches the SPRN 1200 .
  • the start button may be on the interface 216 of the machine 100 or the start button may be on the user interface 208 of the mobile application installed in the mobile device 108 .
  • the controller 104 starts the machine 100 upon receiving the request 1502 to start the machine 100 , using the start button.
  • the controller 104 may receive the request 1502 to start the machine 100 through the mobile device 108 or the operator 106 which may be present inside the machine 100 .
  • the mobile device 108 may send the request 1502 to start the machine 100 through the start button on the user interface 208 of the mobile application which gets enabled after the FPRN 1100 matches the SPRN 1200 .
  • the operator 106 may send the request 1502 to start the machine 100 by pressing the start button on the interface 216 of the machine 100 which gets enabled after the FPRN 1100 and the SPRN 1200 match.
  • the present disclosure makes use of encryption keys (the machine key 400 and the mobile device key 700 ) as well as random data (first fixed random data 404 and second fixed random data 702 ).
  • the method 1600 includes the controller 104 sending the random number 900 to the mobile device 108 , and the further steps of the authentication process are based on processing of the random number 900 .
  • the random numbers 900 may be generated for each instance of starting the machine 100 , so there is an additional level of security added to the authentication process allowing a more secure way of starting the machine 100 through the mobile device 108 .
  • the remote server 202 communicates with the controller 104 and the mobile device 108 , it facilitates easily providing access to a new operator, or revoking or changing access to an already authorized operator.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Mechanical Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Structural Engineering (AREA)
  • Civil Engineering (AREA)
  • Mining & Mineral Resources (AREA)
  • Power Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A system and method to access a machine through a mobile device includes sending a machine key to a controller on-board the machine, and a mobile device key to the mobile device using a remote server. The mobile device sends a mobile device ID to the controller. The controller determines the mobile device key based on the mobile device ID and the machine key. The controller sends a random number to the mobile device. The mobile device processes the random number to derive a first processed random number, and sends the first processed random number to the controller. The controller processes the random number to derive a second processed random number. The controller enables a start button to send a request to start the machine, when the first processed random number matches the second processed random number. The controller starts the machine upon receiving the request to start the machine.

Description

TECHNICAL FIELD
The present disclosure relates to remotely starting a machine. More particularly, the present disclosure relates to remotely starting a machine through a mobile device.
BACKGROUND
As technology has advanced in the field of mobile devices and communication systems, various applications of mobile devices have found their way into vehicles. Particularly, remote starting of vehicles through mobile devices provides a convenient means to access the vehicle without using a physical key. A more specific example can be considered of a worksite where multiple operators work with multiple machines. The operators, as per requirements on the worksite, are allowed to access the machines for which they are authorized through mobile devices.
Various systems and methods are known in the art which facilitate such a system to allow the operator to access the machine through the mobile device. However, it is of prime importance for the worksite to function efficiently, that the operators get access to only the machines for which they are authorized. Conventional systems typically make use of one-time-passwords, static passwords and many other such algorithms.
One such example is provided by the U.S. Pat. No. 9,165,127 (hereinafter referred to as the '127 reference). The '127 reference discloses a working machine provided with a control device that can make wireless communication with a mobile terminal storing a mobile-use identification (ID) code and stores a working machine-use ID code. The control device is provided with ID code checking means to check the mobile-use ID code obtained by ID code obtaining means and the working machine-use ID code with each other. Data communication between the mobile terminal and the control device is allowed once the matching between the ID codes is established. However, the ID codes are fixed and once an operator knows the codes, he/she can always have access to the machine even if the authorization is revoked or changed.
SUMMARY
In an aspect of the present disclosure, a method to access a machine through a mobile device is provided. The method includes sending a machine key to a controller on-board the machine using a remote server. The remote server is located at an off-board location relative to the machine. The method includes sending a mobile device key to the mobile device using the remote server. The method includes sending a mobile device ID associated with the mobile device to the controller using the mobile device. The method includes determining the mobile device key based at least on the mobile device ID and the machine key through the controller. The method includes sending a random number to the mobile device using the controller. The method includes processing the random number based on the mobile device key to derive a first processed random number through the mobile device. The method includes sending the first processed random number to the controller using the mobile device. The method includes processing the random number based on the determined mobile device key to derive a second processed random number through the controller. The method includes comparing the first processed random number and the second processed random number through the controller. The method includes enabling a start button for sending a request to start the machine, when the first processed random number matches the second processed random number. The method further includes starting the machine upon receiving the request to start the machine through the use of the start button.
In another aspect of the present disclosure, a control system to access a machine is provided. The control system includes a remote server located at an off-board location relative to the machine. The remote server generates a mobile device ID, a mobile device key and a machine key. The control system includes a mobile device having an associated mobile device ID and a mobile device key. The mobile device receives the mobile device ID and the mobile device key from the remote server. The control system further includes a controller on-board the machine. The controller receives the mobile device ID from the mobile device. The controller receives the machine key from the remote server. The controller determines the mobile device key based on the mobile device ID and the machine key. The controller sends a random number to the mobile device. The controller receives a first processed random number from the mobile device. The mobile device determines the first processed random number based on the mobile device key. The controller processes the random number based on the determined mobile device key to determine a second processed random number. The controller compares the first processed random number with the second processed random number. The controller enables a start button for sending a request to start the machine, when the first processed random number matches the second processed random number. Furthermore, the controller starts the machine upon receiving the request to start the machine through the use of the start button.
In yet another aspect of the present disclosure, a machine including a controller on-board the machine is provided. The controller receives a mobile device ID from a mobile device. The controller receives a machine key from a remote server. The controller determines a mobile device key based on the mobile device ID and the machine key. The controller sends a random number to the mobile device. The controller receives a first processed random number from the mobile device. The mobile device determines the first processed random number based on the mobile device key received from the remote server. The controller processes the random number based on the determined mobile device key to determine a second processed random number. The controller compares the first processed random number with the second processed random number. The controller enables a start button for sending a request to start the machine, when the first processed random number matches the second processed random number. Furthermore, the controller starts the machine upon receiving the request to start the machine through the use of the start button.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 shows an exemplary worksite showing an exemplary machine and an operator carrying a mobile device, according to an aspect of the present disclosure;
FIG. 2 schematically shows a control system for starting the machine through the mobile device, according to an aspect of the present disclosure;
FIG. 3 shows the remote server storing a list of operators and corresponding mobile device IDs, according to an aspect of the present disclosure;
FIG. 4 shows a machine key being determined by the remote server based on various inputs, according to an aspect of the present disclosure;
FIG. 5 shows a list of machines and corresponding operators authorized to operate the machine, according to an aspect of the present disclosure;
FIG. 6 shows communication between a controller and the remote server, according to an aspect of the present disclosure;
FIG. 7 shows a mobile device key being determined by the remote server based on various inputs, according to an aspect of the present disclosure;
FIG. 8 shows communication between a mobile device and the remote server, according to an aspect of the present disclosure;
FIG. 9 shows communication between the mobile device and the controller, according to an aspect of the present disclosure;
FIG. 10 shows the mobile device key being determined by the controller based on various inputs, according to an aspect of the present disclosure;
FIG. 11 shows a first processed random number being determined by the mobile device based on various inputs, according to an aspect of the present disclosure;
FIG. 12 shows a second processed random number being determined by the controller based on various inputs, according to an aspect of the present disclosure;
FIG. 13 shows a comparison data being determined by the controller based on various inputs, according to an aspect of the present disclosure;
FIG. 14 shows steps taken after comparison data is determined, according to an aspect of the present disclosure;
FIG. 15 shows communication between the mobile device and the controller, according to an aspect of the present disclosure; and
FIG. 16 shows a flow chart of a method to start the machine through the mobile device, according to an aspect of the present disclosure.
 DETAILED DESCRIPTION
Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. FIG. 1 shows an exemplary machine 100 at a worksite 101 at which one or more machines 100 may be operating to perform various tasks. Although, the machine 100 is illustrated as a hydraulic excavator, the machine 100 may be any other type of a work machine as well which may perform a repetitive work cycle of operations associated with industries such as mining, construction, farming, transportation, landscaping, or the like. Examples of such machines may include wheel loaders, hydraulic shovels, dozers, dump trucks etc. While the following detailed description describes an exemplary aspect in connection with the hydraulic excavator, it should be appreciated that the description applies equally to the use of the present disclosure in other machines as well.
The machine 100 includes an operator station 102 to accommodate an operator 106 for operating the machine 100 to perform various tasks. The operator station 102 includes various controls and input means through which the operator 106 may provide inputs to control the machine 100. The machine 100 includes an on-board controller 104 which may control various operational parameters of the machine 100. The controller 104 may be communicably coupled to various systems of the machine 100 such as an ignition system, a propulsion system, etc. The controller 104 may control various functions of the machine 100 to operate the machine 100 in a desired manner. The controller 104 may also be configured to communicate with devices or systems which may not be a part of the machine 100 through various communication medium such as Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, Near Field Communication (NFC), wireless communication systems, etc.
FIG. 1 shows the operator 106 standing on the worksite 101. The operator 106 is illustrated as carrying a mobile device 108 in his hand. The operator 106 may carry the mobile device 108 in his pocket or may hold the mobile device 108 in his hand while working on the worksite 101. The mobile device 108 may be a smart phone, a tablet, or any other such device which may be suitable for application in various aspects of the present disclosure. The mobile device 108 may be configured to send/receive messages to other devices via Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc. The operator 106 may use the mobile device 108 to start the machine 100 without requirement of any physical key. The operator 106 may also use the mobile device 108 to start the machine 100 without being physically present on the machine 100. The operator 106 may be outside the operator station 102, or near the machine 100, or the operator 106 may also be at a remote back-office.
Although, the illustrated embodiment shows only one operator 106 on the worksite 101, there may be any number of operators 106 on the worksite 101 which may carry respective mobile devices 108. The mobile device 108 may have a mobile application installed, which may allow the mobile device 108 to start the machine 100 based on appropriate authentication procedures being followed. The authentication procedures will be described in detail in the forthcoming description. The mobile application may store a list of machines 100 which the operator 106 carrying the mobile device 108 may be authorized to operate. The operator 106 may run the mobile application on the mobile device 108 and select the machine 100 which the operator 106 wishes to operate.
FIG. 2 schematically illustrates a control system 200 to start the machine 100 through the mobile device 108. The control system 200 includes the mobile device 108, the controller 104 and a remote server 202. Furthermore, the mobile device 108 includes one or more transceivers 204 to communicate with other devices and systems. The transceiver 204 may send/receive messages or data through any suitable communication medium including one or more of Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc. Although, two transceivers 204 are illustrated, there may be any number of transceivers 204 provided on the mobile device 108. The mobile device 108 includes a processor 206 to perform various calculations and to process data which may be required for authentication procedures.
The mobile device 108 also includes a user interface 208 for enabling the operator 106 to operate the mobile device 108. The user interface 208 may be a touch screen, a keypad, or any other such kind of a user interface which may allow the operator 106 to provide desired inputs to the processor 206 of the mobile device 108. In an embodiment, the user interface 208 is a touch screen through which the operator 106 may provide inputs to the mobile device 108. The mobile device 108 has an associated mobile device ID 209. The mobile device ID 209 may be a unique identification code which may be used to identify the mobile device 108. In an embodiment, the mobile device ID 209 is a Universal Unique Identifier (UUID). In another embodiment, the mobile device ID 209 is an International Mobile Equipment Identity (IMEI) number of the mobile device 108.
The controller 104 has an associated memory 210 to store various operational parameters as well as other relevant information. The controller 104 includes a processor 212 to perform various tasks and calculations required as per various aspects of the present disclosure. The controller 104 also includes one or more transceivers 214 which may send and receive signals to communicate with other components of the control system 200 such as the mobile device 108 and the remote server 202. In an embodiment, the transceivers 214 may send/receive messages or data through any suitable communication medium including Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc. It should be contemplated that although the FIG. 2 shows that the controller 104 includes two transceivers 214, the controller 104 may have any suitable number of transceivers 214 which may suit the need of the present disclosure.
The controller 104 is coupled to an interface 216 such as a graphical user interface of the machine 100 so that the operator 106 may provide inputs for operating the machine 100. The interface 216 may be a touch screen, a keypad, a joystick or any other such kind of a user interface which may allow the operator 106 to provide desired inputs to the machine 100. In an embodiment, the interface 216 may include a start button through which the operator 106 may send a request to the controller 104 to start the machine 100. The controller 104 is also coupled to an engine 218 of the machine 100.
The machine 100 may be represented by an associated machine ID 219. The machine ID 219 may be any unique identifier which may be used to refer to or identify the machine 100. The machine ID 219 may be a unique serial number which may be assigned to the machine 100. In an embodiment, the machine ID 219 may be a chassis number or a Vehicle Identification Number (VIN) which may be used to uniquely identify the machine 100. The machine ID 219 may be generated during or post manufacturing of the machine 100.
The remote server 202 is located at an off-board location relative to the machine 100. The remote server 202 may be a back-office, a control room, or any other such type of location which may be used to remotely monitor and control the machine 100. The remote server 202 includes a processor 220 to perform various tasks. The remote server 202 also includes one or more transceivers 222 to communicate with other devices and systems. The remote server 202 is communicably coupled to the controller 104 and the mobile device 108. The controller 104 and the mobile device 108 are communicably coupled to each other as well. The remote server 202, the controller 104, and the mobile device 108 may communicate to each other via Bluetooth®, Wi-Fi®, internet connectivity, cellular networks, NFC, wireless communication systems, etc.
The remote server 202 may store information about the operators 106 and the machines 100 working on the worksite 101. Each operator 106 carries the corresponding mobile device 108. The remote server 202 stores a list 300 of the operators 106 and the corresponding mobile device IDs 209 as shown in FIG. 3. In an embodiment, when the operator 106 is registered with the mobile device 108, the remote server 202 may store information about the operator 106 and link the mobile device ID 209 of the respective mobile device 108 to the operator 106. In an embodiment, the controller 104 may also store the list 300 of authorized operators 106 allowed to operate the machine 100. In another exemplary embodiment, the remote server 202 may send the list 300 of the operators 106 to the controller 104.
Furthermore, the remote server 202 derives and stores a machine key 400 associated with each of the machines 100 operating on the worksite 101. The machine key 400 may be an encryption key which may be used to encrypt or decrypt any information which needs to be shared by the machine 100 or which is shared with the machine 100. FIG. 4 illustrates various components of the machine key 400. The remote server 202 may derive the machine key 400 from the machine ID 219, a first key 402, and a first fixed random data 404. The first key 402 may be a confidential serial number or an alpha numeric code or any other such set of characters which may be suitable for use in various aspects of the present disclosure. The remote server 202 may generate the first key 402, or a person who may be authorized to access information about all the machines 100 and the operators 106 may set the first key 402. The first fixed random data 404 may be a random data generated by any conventional random data generation algorithms already known in the art. The remote server 202 may include any such algorithm which may generate the first fixed random data 404.
FIG. 5 shows the remote server 202 stores a list 500 of the operators 106 authorized to operate each of the machines 100. The list 500 includes the operators 106 along with the corresponding mobile device IDs 209 which may be authorized to operate the machine 100 for each of the machines 100. FIG. 6 illustrates sequence of exchange of information between the remote server 202 and the controller 104 when the remote server 202 shares the machine key 400 with the controller 104. In the illustrated embodiment, the controller 104 sends a request to the remote server 202 to send the machine key 400 to the controller 104. The controller 104 sends the machine ID 219 so that the remote server 202 may appropriately identify the machine 100, and send the machine key 400 corresponding to the machine 100 from which the controller 104 has sent the request. In response to the request by the controller 104, the remote server 202 sends the machine key 400 to the controller 104.
The remote server 202 also sends the list 300 of authorized mobile device IDs 209 to the controller 104. In an embodiment, the remote server 202 may be a website. The controller 104 may be configured to periodically check the remote server 202 for machine key 400 files for the machine 100. In case there is a new machine key 400 available for the machine 100, the controller 104 may download the new machine key 400 by providing the machine ID 219 as credentials on the website to authenticate the download process.
Furthermore, the remote server 202 derives and stores a mobile device key 700. The mobile device key 700 may be an encryption key which may be used to encrypt or decrypt any information which needs to be shared by the mobile device 108 or which is shared with the mobile device 108. FIG. 7 illustrates various components of the mobile device key 700. The remote server 202 may derive the mobile device key 700 from the machine key 400, the mobile device ID 209, and a second fixed random data 702. Any conventional random data generation algorithms already known in the art may be used to generate the second fixed random data 702. The remote server 202 may include any such algorithm which may generate the second fixed random data 702.
FIG. 8 illustrates sequence of exchange of information between the mobile device 108 and the remote server 202, when the remote server 202 shares the mobile device key 700 with the mobile device 108. The mobile device 108 sends a request to the remote server 202 to send the mobile device key 700 to the mobile device 108. The mobile device 108 sends a unique identifier 800 which may be unique to the mobile application installation so that the remote server 202 may appropriately identify the mobile device 108, and send back the mobile device ID 209 corresponding to the mobile device 108 which has sent the request. In an embodiment, the remote server 202 may also send a list 500 of mobile device keys 700 along with corresponding machine IDs 219 for a given mobile device ID 209. In another exemplary embodiment, the remote server 202 may be a website, or a web address. The mobile device 108 may access the website and download the mobile device key 700 from the website. The mobile device 108 may access the remote server 202 through a user login process, and then the mobile device 108 may send the unique identifier 800 to the remote server 202, and the remote server 202 sends back the mobile device ID 209 to the mobile device 108.
FIG. 9 schematically represents the sequence of communication occurring between the mobile device 108 and the controller 104 to authenticate the mobile device 108 for starting the machine 100. When the operator 106 carrying the mobile device 108 enters the worksite 101, the mobile device 108 sends the mobile device ID 209 to the controller 104. In an embodiment, the mobile device 108 sends the mobile device ID 209 to the controller 104 when the operator 106 is less than a pre-determined distance away from the machine 100. The controller 104 receives the mobile device ID 209 through the transceiver 214. The controller 104 then determines the mobile device key 700 by using the received mobile device ID 209 as shown in FIG. 10. The controller 104 determines the mobile device key 700 from the mobile device ID 209, the machine key 400, and the second fixed random data 702. The controller 104 may receive the second fixed random data 702 from the remote server 202. The second fixed random data 702 is a fixed random data value which may be generated through any random data generation algorithm known in the art.
With continued reference to FIG. 9, the controller 104 sends a random number 900 to the mobile device 108. In an embodiment, the controller 104 may match the mobile device ID 209 with the list 300 of the mobile device IDs 209 stored in the memory 210 of the controller 104. The list 300 includes one or more pre-stored mobile device IDs 209 in the memory 210 of the controller 104. The controller 104 checks if the mobile device ID 209 matches any one of the pre-stored mobile device IDs 209. When the mobile device ID 209 does not match any of the pre-stored mobile device IDs 209, the controller 104 blocks the mobile device 108 from communicating with the controller 104 for a pre-determined time period. In an embodiment, the pre-determined time period may be one minute. The pre-determined time period may be adjustable based on response frequency of the mobile device 108 and the controller 104. No further processing is done when the mobile device ID 209 does not match any of the pre-stored mobile device IDs 209.
When the mobile device ID 209 matches from any one of the pre-stored mobile device IDs 209 from the list 300, the controller 104 sends the random number 900 to the mobile device 108. The controller 104 may also temporarily store the random number 900 in the memory 210. The random number 900 may be generated by any random data generation algorithm known in the art which may be suitable for the application in various aspects of the present disclosure. In an embodiment, the random number 900 may also be an alphanumeric code, a sequence of letters or any other such random sequence of characters.
The mobile device 108 receives the random number 900 from the controller 104 and processes the random number 900 as shown in FIG. 11. The mobile device 108 makes use of the mobile device key 700 to process the random number 900 and derives a first processed random number (FPRN) 1100. The FPRN 1100 is an outcome of the mobile device key 700 being used to encrypt the random number 900 by the mobile device 108.
Referring to FIG. 9, the mobile device 108 then sends the FPRN 1100 to the controller 104. The controller 104 may receive the FPRN 1100 through the transceiver 214. The controller 104 also processes the random number 900 as shown in FIG. 12. The controller 104 makes use of the determined mobile device key 700 to process the random number 900. The controller 104 processes the random number 900 to derive a second processed random number (SPRN) 1200. The SPRN 1200 is an outcome of the determined mobile device key 700 being used to encrypt the random number 900 by the controller 104.
The controller 104 compares the FPRN 1100 and the SPRN 1200 as shown in FIG. 13. Both the FPRN 1100 and the SPRN 1200 essentially represent the random number 900 processed by the mobile device key 700, the only difference being that the FPRN 1100 is processed by the mobile device 108, and the SPRN 1200 is processed by the controller 104. The controller 104 determines a comparison data 1300 from the comparison of the FPRN 1100 and the SPRN 1200.
Referring to FIG. 9, the controller 104 now sends an authentication response message 902 to the mobile device 108 after the comparison. The authentication response message 902 may include information about results of the comparison between the FPRN 1100 and the SPRN 1200. FIG. 14 illustrates further steps after comparison data 1300 is determined. In block 1400, the controller 104 compares the FPRN 1100 and the SPRN 1200 to check if the FPRN 1100 matches the SPRN 1200.
In block 1402, when the FPRN 1100 matches the SPRN 1200, the controller 104 may send an authentication verification message 1500 to the mobile device 108, stating that the mobile device 108 is now authenticated and subsequently, enables the start button on the mobile device 108 and may be on the user interface 216 of the machine 100. The operator 106 uses the start button either on the mobile device 108 or the user interface 216 on the machine 100 to send a request 1502, as shown in FIG. 15 to the controller 104 to start the machine 100. In block 1404, the controller 104 may receive the request 1502 to start the machine 100 through the use of the start button. Subsequently, in block 1406, the controller 104 starts the machine 100 after receiving the request 1502.
When the FPRN 1100 and the SPRN 1200 do not match, then as shown in block 1408, the controller 104 blocks the mobile device 108 from connecting with the machine 100 for a pre-determined time period. In an embodiment, the pre-determine time period may be one minute. The pre-determined time period may be adjustable based on response frequency of the mobile device 108 and the controller 104.
INDUSTRIAL APPLICABILITY
The present disclosure provides an improved method 1600 to start the machine 100 through the mobile device 108 as shown in FIG. 16. In block 1602, the remote server 202 sends the machine key 400 to the controller 104. The machine key 400 may be an encryption key. The remote server 202 may derive the machine key 400 based on the machine ID 219, the first key 402, and the first fixed random data 404. Any conventional random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, may generate the first fixed random data 404.
In block 1604, the remote server 202 sends the mobile device key 700 to the mobile device 108. The mobile device key 700 may be an encryption key. The remote server 202 may derive the mobile device key 700 from the machine key 400, the mobile device ID 209, and the second fixed random data 702. Any conventional random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, may be used to generate the second fixed random data 702. In block 1606, the mobile device 108 sends the mobile device ID 209 associated with the mobile device 108 to the controller 104. The controller 104 may receive the mobile device ID 209 through the transceiver 214.
In block 1608, the controller 104 determines the mobile device key 700 based at least on the mobile device ID 209 and the machine key 400. In an embodiment, the controller 104 determines the mobile device key 700 based on the machine key 400, the mobile device ID 209, and the second fixed random data 702. In block 1610, the controller 104 sends the random number 900 to the mobile device 108. The controller 104 may use any suitable random data generation algorithm, which may be suitable for application with various aspects of the present disclosure, to generate the random number 900.
In block 1612, the mobile device 108 processes the random number 900 by using the mobile device key 700 to derive the FPRN 1100. In block 1614, the mobile device 108 sends the FPRN 1100 to the controller 104. In block 1616, the controller 104 processes the random number 900 based on the determined mobile device key 700 to derive the SPRN 1200. The controller 104 may process the random number 900 through the processor 212 which may be configured to perform such calculations.
In block 1618, the controller 104 compares the FPRN 1100 and the SPRN 1200. In block 1620, the controller 104 enables the start button to send the request 1502 to start the machine 100, when the FPRN 1100 matches the SPRN 1200. The start button may be on the interface 216 of the machine 100 or the start button may be on the user interface 208 of the mobile application installed in the mobile device 108. In block 1622, the controller 104 starts the machine 100 upon receiving the request 1502 to start the machine 100, using the start button. The controller 104 may receive the request 1502 to start the machine 100 through the mobile device 108 or the operator 106 which may be present inside the machine 100. The mobile device 108 may send the request 1502 to start the machine 100 through the start button on the user interface 208 of the mobile application which gets enabled after the FPRN 1100 matches the SPRN 1200. The operator 106 may send the request 1502 to start the machine 100 by pressing the start button on the interface 216 of the machine 100 which gets enabled after the FPRN 1100 and the SPRN 1200 match.
The present disclosure makes use of encryption keys (the machine key 400 and the mobile device key 700) as well as random data (first fixed random data 404 and second fixed random data 702). Furthermore, the method 1600 includes the controller 104 sending the random number 900 to the mobile device 108, and the further steps of the authentication process are based on processing of the random number 900. The random numbers 900 may be generated for each instance of starting the machine 100, so there is an additional level of security added to the authentication process allowing a more secure way of starting the machine 100 through the mobile device 108. Furthermore, as the remote server 202 communicates with the controller 104 and the mobile device 108, it facilitates easily providing access to a new operator, or revoking or changing access to an already authorized operator.
While aspects of the present disclosure have been particularly shown and described with reference to the embodiments above, it will be understood by those skilled in the art that various additional embodiments may be contemplated by the modification of the disclosed machines, systems and methods without departing from the spirit and scope of what is disclosed. Such embodiments should be understood to fall within the scope of the present disclosure as determined based upon the claims and any equivalents thereof.

Claims (20)

What is claimed is:
1. A method to start a machine through a mobile device, the method comprising:
sending, using a remote server, a machine key to a controller on-board the machine, wherein the remote server is at an off-board location relative to the machine;
sending, using the remote server, a mobile device key to the mobile device;
sending, using the mobile device, a mobile device ID associated with the mobile device to the controller;
determining, through the controller, the mobile device key based at least on the mobile device ID and the machine key;
sending, using the controller, a random number to the mobile device;
processing, through the mobile device, the random number based on the mobile device key to derive a first processed random number;
sending, using the mobile device, the first processed random number to the controller;
processing, through the controller, the random number based on the determined mobile device key to derive a second processed random number;
comparing, through the controller, the first processed random number and the second processed random number;
enabling, through the controller, a start button for sending a request to start the machine, when the first processed random number matches the second processed random number; and
starting the machine, through the controller, upon receiving the request to start the machine through a use of the start button.
2. The method of claim 1, wherein enabling the start button comprises enabling the start button on at least one of the mobile device or on an interface present on-board the machine.
3. The method of claim 1, further comprising:
blocking the mobile device, through the controller, from connecting with the machine for a pre-determined time period, when the first processed random number does not match the second processed random number.
4. The method of claim 1, wherein the remote server derives the machine key based on a machine ID, a first key, and a first fixed random data.
5. The method of claim 4, wherein the machine key comprises an encryption key.
6. The method of claim 1, wherein the remote server derives the mobile device key based on the machine key, the mobile device ID, and a second fixed random data.
7. The method of claim 5, wherein the mobile device key comprises an encryption key.
8. The method of claim 1, further comprising:
comparing, by the controller, the mobile device ID from a plurality of pre-stored mobile device IDs; and
sending, by the controller, the random number to the mobile device, when the mobile device ID matches one of the pre-stored mobile device IDs.
9. A control system to start a machine, the control system comprising:
a remote server located at an off-board location relative to the machine, wherein the remote server is configured to:
generate a mobile device ID;
generate a mobile device key; and
generate a machine key;
a mobile device configured to:
receive the mobile device ID from the remote server; and
receive the mobile device key from the remote server;
a controller on-board the machine, wherein the controller is configured to:
receive the mobile device ID from the mobile device;
receive the machine key from the remote server;
determine the mobile device key based on the mobile device ID and the machine key;
send a random number to the mobile device;
receive a first processed random number from the mobile device, wherein the mobile device determines the first processed random number based on the mobile device key;
process the random number based on the determined mobile device key to determine a second processed random number;
compare the first processed random number with the second processed random number;
enable a start button for sending a request to start the machine, when the first processed random number matches the second processed random number; and
start the machine, upon receiving the request to start the machine through a use of the start button.
10. The control system of claim 9, wherein enabling the start button comprises enabling the start button on at least one of the mobile device or on an interface present on-board the machine.
11. The control system of claim 9, wherein the controller is further configured to:
block the mobile device from connecting with the machine for a pre-determined time period, when the first processed random number does not match the second processed random number.
12. The control system of claim 9, wherein the remote server derives the machine key based on a machine ID, a first key, and a first fixed random data.
13. The control system of claim 12, wherein the machine key comprises an encryption key.
14. The control system of claim 9, wherein the remote server derives the mobile device key based on the machine key, the mobile device ID, and a second fixed random data.
15. The control system of claim 14, wherein the mobile device key comprises an encryption key.
16. The control system of claim 9, wherein the controller is further configured to:
compare the mobile device ID from a plurality of pre-stored mobile device IDs; and
send the random number to the mobile device, when the mobile device ID matches one of the pre-stored mobile device IDs.
17. A machine comprising:
a controller on-board the machine, wherein the controller is configured to:
receive a mobile device ID from a mobile device;
receive a machine key from a remote server;
determine a mobile device key based on the mobile device ID and the machine key;
send a random number to the mobile device;
receive a first processed random number from the mobile device, wherein the mobile device determines the first processed random number based on the mobile device key received from the remote server;
process the random number based on the determined mobile device key to determine a second processed random number;
compare the first processed random number with the second processed random number;
enable a start button for sending a request to start the machine, when the first processed random number matches the second processed random number; and
start the machine, upon receiving the request to start the machine through a use of the start button.
18. The machine of claim 17, wherein enabling the start button comprises enabling the start button on at least one of the mobile device or on an interface present on-board the machine.
19. The machine of claim 17, wherein the controller is further configured to:
block the mobile device from connecting with the machine for a pre-determined time period, when the first processed random number does not match the second processed random number.
20. The machine of claim 17, wherein the controller is further configured to:
compare the mobile device ID from a plurality of pre-stored mobile device IDs; and
send the random number to the mobile device, when the mobile device ID matches one of the pre-stored mobile device IDs.
US15/654,818 2017-07-20 2017-07-20 Starting a machine through a mobile device Active US10075576B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/654,818 US10075576B1 (en) 2017-07-20 2017-07-20 Starting a machine through a mobile device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/654,818 US10075576B1 (en) 2017-07-20 2017-07-20 Starting a machine through a mobile device

Publications (1)

Publication Number Publication Date
US10075576B1 true US10075576B1 (en) 2018-09-11

Family

ID=63406280

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/654,818 Active US10075576B1 (en) 2017-07-20 2017-07-20 Starting a machine through a mobile device

Country Status (1)

Country Link
US (1) US10075576B1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109837940A (en) * 2017-11-24 2019-06-04 诺瓦特伦有限公司 Control earth moving machine
CN111757320A (en) * 2019-03-28 2020-10-09 华为技术有限公司 Method for starting vehicle and related equipment
CN112977334A (en) * 2021-03-30 2021-06-18 三一汽车起重机械有限公司 Control method and device for engineering machinery and crane
US20220025611A1 (en) * 2020-07-27 2022-01-27 Caterpillar Inc. Method for remote operation of machines using a mobile device
US11343760B2 (en) 2020-06-15 2022-05-24 Caterpillar Inc. System, method, and device for providing local electronic servicing

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060143463A1 (en) * 2002-12-04 2006-06-29 Kabushiki Kaisha Toshiba Keyless entry system and keyless entry method
US20070040649A1 (en) * 2005-08-17 2007-02-22 Alps Automotive, Inc. Multifunction keyless entry system
US20070200671A1 (en) * 2006-02-28 2007-08-30 Kelley Nia L Methods and apparatuses for remote control of vehicle devices and vehicle lock-out notification
US20090292528A1 (en) * 2008-05-21 2009-11-26 Denso Corporation Apparatus for providing information for vehicle
US20100171642A1 (en) * 2007-06-19 2010-07-08 Hassan Hasib Mobile Control Node System and Method for Vehicles
US20100305779A1 (en) * 2007-06-19 2010-12-02 Hassan Hasib Remote vehicle control system utilizing multiple antennas
US20110197844A1 (en) * 2010-02-12 2011-08-18 Fujitsu Ten Limited Remote starting device and remote starting method
US8566203B1 (en) 2012-11-30 2013-10-22 Bank Of America Corporation User identification using mobile device
DE102012022786A1 (en) 2012-11-22 2014-05-22 Volkswagen Aktiengesellschaft Method for an access system for vehicle and for starting vehicle by mobile terminal, involves verifying identification information of identification device by control device, where control device checks based on identification information
US20150005984A1 (en) * 2013-06-27 2015-01-01 General Motors Llc Remote start system for a motor vehicle
US20150045013A1 (en) * 2013-08-09 2015-02-12 Directed, Llc Multi-level vehicle remote start authentication method & system
US20150073685A1 (en) * 2013-09-09 2015-03-12 Electronics And Telecommunications Research Institute General-purpose vehicle remote control device and method
US9008917B2 (en) 2012-12-27 2015-04-14 GM Global Technology Operations LLC Method and system for detecting proximity of an end device to a vehicle based on signal strength information received over a bluetooth low energy (BLE) advertising channel
US9165127B2 (en) 2011-07-25 2015-10-20 Kubota Corporation Working machine, data communcation system for working machine, operation system for working machine, and setting change system for working machine
US9305412B2 (en) 2013-11-22 2016-04-05 Volkswagen Ag Apparatus, system and method for vehicle authentication management and reporting
US20160150407A1 (en) * 2014-11-26 2016-05-26 Wind River Systems, Inc. Method And System For Connecting A Mobile Communication Device To An Automobile
US20160321566A1 (en) * 2015-04-29 2016-11-03 Ford Global Technologies, Llc Ride-sharing joint rental groups
US20160344747A1 (en) * 2015-05-22 2016-11-24 M2MD Technologies, Inc. Method and system for securely and automatically obtaining services from a machine device services server
US20160358389A1 (en) 2013-12-20 2016-12-08 Valeo Comfort And Driving Assistance Mobile telephone capable of automatically pairing with a motor vehicle, and automatic pairing method
US9544768B2 (en) 2015-03-20 2017-01-10 Hyundai Motor Company Method and apparatus for performing secure Bluetooth communication
US20170060559A1 (en) * 2015-08-25 2017-03-02 Ford Global Technologies, Llc Multiple-stage secure vehicle software updating
US20170267214A1 (en) * 2011-04-22 2017-09-21 Angel A. Penilla Vehicles and cloud systems for assigning temporary e-keys to access use of a vehicle

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060143463A1 (en) * 2002-12-04 2006-06-29 Kabushiki Kaisha Toshiba Keyless entry system and keyless entry method
US20070040649A1 (en) * 2005-08-17 2007-02-22 Alps Automotive, Inc. Multifunction keyless entry system
US20070200671A1 (en) * 2006-02-28 2007-08-30 Kelley Nia L Methods and apparatuses for remote control of vehicle devices and vehicle lock-out notification
US20100171642A1 (en) * 2007-06-19 2010-07-08 Hassan Hasib Mobile Control Node System and Method for Vehicles
US20100305779A1 (en) * 2007-06-19 2010-12-02 Hassan Hasib Remote vehicle control system utilizing multiple antennas
US20090292528A1 (en) * 2008-05-21 2009-11-26 Denso Corporation Apparatus for providing information for vehicle
US20110197844A1 (en) * 2010-02-12 2011-08-18 Fujitsu Ten Limited Remote starting device and remote starting method
US20170267214A1 (en) * 2011-04-22 2017-09-21 Angel A. Penilla Vehicles and cloud systems for assigning temporary e-keys to access use of a vehicle
US9165127B2 (en) 2011-07-25 2015-10-20 Kubota Corporation Working machine, data communcation system for working machine, operation system for working machine, and setting change system for working machine
DE102012022786A1 (en) 2012-11-22 2014-05-22 Volkswagen Aktiengesellschaft Method for an access system for vehicle and for starting vehicle by mobile terminal, involves verifying identification information of identification device by control device, where control device checks based on identification information
US8566203B1 (en) 2012-11-30 2013-10-22 Bank Of America Corporation User identification using mobile device
US9008917B2 (en) 2012-12-27 2015-04-14 GM Global Technology Operations LLC Method and system for detecting proximity of an end device to a vehicle based on signal strength information received over a bluetooth low energy (BLE) advertising channel
US20150005984A1 (en) * 2013-06-27 2015-01-01 General Motors Llc Remote start system for a motor vehicle
US20150045013A1 (en) * 2013-08-09 2015-02-12 Directed, Llc Multi-level vehicle remote start authentication method & system
US20150073685A1 (en) * 2013-09-09 2015-03-12 Electronics And Telecommunications Research Institute General-purpose vehicle remote control device and method
US9305412B2 (en) 2013-11-22 2016-04-05 Volkswagen Ag Apparatus, system and method for vehicle authentication management and reporting
US20160358389A1 (en) 2013-12-20 2016-12-08 Valeo Comfort And Driving Assistance Mobile telephone capable of automatically pairing with a motor vehicle, and automatic pairing method
US20160150407A1 (en) * 2014-11-26 2016-05-26 Wind River Systems, Inc. Method And System For Connecting A Mobile Communication Device To An Automobile
US9544768B2 (en) 2015-03-20 2017-01-10 Hyundai Motor Company Method and apparatus for performing secure Bluetooth communication
US20160321566A1 (en) * 2015-04-29 2016-11-03 Ford Global Technologies, Llc Ride-sharing joint rental groups
US20160344747A1 (en) * 2015-05-22 2016-11-24 M2MD Technologies, Inc. Method and system for securely and automatically obtaining services from a machine device services server
US20170060559A1 (en) * 2015-08-25 2017-03-02 Ford Global Technologies, Llc Multiple-stage secure vehicle software updating

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109837940A (en) * 2017-11-24 2019-06-04 诺瓦特伦有限公司 Control earth moving machine
US11486117B2 (en) * 2017-11-24 2022-11-01 Novatron Oy Controlling earthmoving machines
CN111757320A (en) * 2019-03-28 2020-10-09 华为技术有限公司 Method for starting vehicle and related equipment
US20220014906A1 (en) * 2019-03-28 2022-01-13 Huawei Technologies Co., Ltd. Method for starting vehicle and related device
EP3930363A4 (en) * 2019-03-28 2022-03-23 Huawei Cloud Computing Technologies Co., Ltd. Method for unlocking vehicle and related device
US11902774B2 (en) * 2019-03-28 2024-02-13 Huawei Cloud Computing Technologies Co., Ltd. Method for starting vehicle and related device
US11343760B2 (en) 2020-06-15 2022-05-24 Caterpillar Inc. System, method, and device for providing local electronic servicing
US20220025611A1 (en) * 2020-07-27 2022-01-27 Caterpillar Inc. Method for remote operation of machines using a mobile device
US11505919B2 (en) * 2020-07-27 2022-11-22 Caterpillar Inc. Method for remote operation of machines using a mobile device
CN112977334A (en) * 2021-03-30 2021-06-18 三一汽车起重机械有限公司 Control method and device for engineering machinery and crane

Similar Documents

Publication Publication Date Title
US10075576B1 (en) Starting a machine through a mobile device
US11023875B2 (en) Electronic credential management system
CN107085870B (en) Regulating vehicle access using encryption methods
US10882492B2 (en) Method and device for authenticating a user to a transportation vehicle
CN107251106B (en) Method for secure transmission of virtual keys and method for authentication of mobile terminals
CN107454999B (en) Method for automatic identification between a mobile device and a motor vehicle, capable of operating according to the bluetooth low energy protocol
CN109328348B (en) Service authentication method, system and related equipment
CN102546155B (en) On-demand safe key generates method and system
US11263329B2 (en) Method, computer-readable medium, system and vehicle comprising the system for providing a data record of a vehicle to a third party
CN105704131A (en) Vehicle lock control method and cloud management server
CN107666498B (en) Updating method and device of vehicle-mounted module, cloud server, system and vehicle
JP6583728B2 (en) Communications system
KR20080106954A (en) Method for the protection of a movable object, especially a vehicle, against unauthorized use
JP2006262184A (en) Authority possession apparatus, authority borrowing apparatus, control unit, authority delegation system, authority possession program and authority possession method
WO2015156035A1 (en) Locking control device, locking control system, and locking control method
CN112019340B (en) Authentication system
US9609512B2 (en) Wireless authentication system and wireless authentication method
CN104796262A (en) Data encryption method and terminal system
US11003744B2 (en) Method and system for securing bank account access
JP2020088408A (en) Authentication system and authentication method
US10263976B2 (en) Method for excluding a participant from a group having authorized communication
EP2650814A1 (en) Method for authenticating a user
US11974123B2 (en) Encrypted communication between an appliance and a device on a motor vehicle
CN112910652B (en) Remote controller identification method and remote controller identification device
US20230229994A1 (en) System, method, and program for controlling access to a machine or equipment

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4