U.S. patent application number 15/499356 was filed with the patent office on 2018-11-01 for mobile-based equipment service system using encrypted code offloading.
The applicant listed for this patent is OTIS ELEVATOR COMPANY. Invention is credited to Michael Garfinkel, Arthur T. Grondine, Teems E. Lovett, Devu Manikantan Shila.
Application Number | 20180316652 15/499356 |
Document ID | / |
Family ID | 62091708 |
Filed Date | 2018-11-01 |
United States Patent
Application |
20180316652 |
Kind Code |
A1 |
Shila; Devu Manikantan ; et
al. |
November 1, 2018 |
MOBILE-BASED EQUIPMENT SERVICE SYSTEM USING ENCRYPTED CODE
OFFLOADING
Abstract
A mobile-based equipment service system includes a remote
server, a mobile device, and at least one equipment controller. The
mobile device includes a user interface, and is configured to send
a user authentication message, initiated by a user via the user
interface, to the remote server. The remote server is configured to
verify the user via the user authentication message and once
verified, send an encrypted blob to the mobile device in response
to the user authentication message. At least one equipment
controller is configured to receive and decrypt the encrypted blob
from the mobile device.
Inventors: |
Shila; Devu Manikantan;
(West Hartford, CT) ; Grondine; Arthur T.; (Deep
River, CT) ; Garfinkel; Michael; (West Hartford,
CT) ; Lovett; Teems E.; (Glastonbury, CT) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
OTIS ELEVATOR COMPANY |
Farmington |
CT |
US |
|
|
Family ID: |
62091708 |
Appl. No.: |
15/499356 |
Filed: |
April 27, 2017 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04L 67/10 20130101;
H04L 63/0428 20130101; H04L 63/08 20130101; B66B 2201/4676
20130101; H04L 63/0485 20130101; G06F 21/572 20130101; H04W 12/0602
20190101; H04L 63/083 20130101; H04W 88/02 20130101; H04L 63/0442
20130101; B66B 1/3461 20130101; H04L 63/0853 20130101; H04L 63/0884
20130101 |
International
Class: |
H04L 29/06 20060101
H04L029/06; H04W 12/06 20060101 H04W012/06; B66B 1/34 20060101
B66B001/34 |
Claims
1. A mobile-based equipment service system applied by a user, the
mobile-based equipment service system comprising: a remote server
including a computer processor, a non-transitory storage medium, an
application executed by the computer processor and stored in the
non-transitory storage medium, a user authentication database
stored in the non-transitory storage medium and applied by the
application; a mobile device including a user interface, the mobile
device being configured to send a user authentication message
initiated by the user via the user interface to the remote server,
wherein the application is configured to verify the user by
comparing the user authentication message to the user
authentication database, and once verified, develop and effect the
sending of an encrypted blob to the mobile device in response to
the user authentication message; at least one equipment controller
including a computer processor, a non-transitory storage medium,
executable code, executed by the computer processor and stored in
the non-transitory storage medium; at least one site, wherein each
site of the at least one site includes at least one respective
equipment controller of the at least one equipment controller, and
the encrypted blob is secured by the remote server via a site
specific private key associated with a respective site of the at
least one site, the authentication message including user
credentials and a selected site of the at least one site selected
by the user, wherein the computer processor of the equipment
controller is configured to receive the encrypted blob and the
executable code is configured to decrypt the encrypted blob
received from the mobile device and utilizing the site specific
private key.
2-3. (canceled)
4. The mobile-based equipment service system set forth in claim 1,
wherein the encrypted blob includes firmware and a header
configured to be extracted by the executable code.
5. The mobile-based equipment service system set forth in claim 4,
wherein the header includes the site specific private key, and a
duration to authenticate.
6. The mobile-based equipment service system set forth in claim 5,
wherein the header includes a version that is verified by the
executable code.
7. The mobile-based equipment service system set forth in claim 1,
wherein the at least one site is a plurality of buildings.
8. The mobile-based equipment service system set forth in claim 1,
wherein the at least one site is a plurality of geographic
regions.
9. The mobile-based equipment service system set forth in claim 1,
wherein the at least one equipment controller is at least one
elevator controller.
10. The mobile-based equipment service system set forth in claim 1,
wherein the at least one equipment controller does not have
internet connectivity.
11. The mobile-based equipment service system set forth in claim 1,
wherein the at least one equipment controller is configured to
reply to the mobile device by requesting the user authentication
message from the user.
12. The mobile-based equipment service system set forth in claim 1,
wherein the encrypted blob is asymmetric encrypted.
13. A method of operating a mobile-based equipment service system
comprising: sending a selected site from a mobile device to a
remote server; encrypting a blob by an application executed by a
processor of the remote server using a private key associated with
the selected site and preprogrammed into the remote server as part
of a database stored in a non-transitory storage medium of the
remote server; sending the encrypted blob to the mobile device;
sending the encrypted blob from the mobile device to a controller
associated with the selected site; and decrypting the encrypted
blob by an executable code executed by a processor of the
controller utilizing the private key preprogrammed into the
controller.
14. The method set forth in claim 13, wherein the selected site is
selected by a user of the mobile device and is sent to the remote
server as part of an authentication message that includes
credentials of the user.
15. The method set forth in claim 13 further comprising: sending a
credential request from the controller to the mobile device;
entering of credentials by a user into the mobile device; and
sending the credentials from the mobile device to the
controller.
16. The method set forth in claim 15 further comprising: comparing
the credentials sent from the mobile device to a hash of
credentials sent as part of the encrypted blob by the
controller.
17. The method set forth in claim 13, wherein the remote server is
cloud-based.
18. The method set forth in claim 13, wherein the mobile device is
a smartphone.
19. The method set forth in claim 13, wherein the selected site is
a building and the controller is an elevator controller.
Description
BACKGROUND
[0001] The present disclosure relates to equipment service system,
and more particularly, to mobile-based equipment service systems
using encrypted code offloading.
[0002] Current service tools used for accessing equipment
controllers (e.g., elevator controllers) may rely on using a
separate hardware tool that may securely authenticate to the
controllers while preventing reverse engineering of proprietary
codes and tampering attacks. Unfortunately, such hardware based
capabilities may not be cost effective. Alternatively, use of
mobile devices as a service tool may be feasible, but such mobile
devices are not in control of the company providing the equipment
services. It may further be difficult to enforce security
requirements to facilitate tamper-proof hardware and an execution
environment.
BRIEF DESCRIPTION
[0003] A mobile-based equipment service system applied by a user,
the mobile-based equipment service system according to one,
non-limiting, embodiment of the present disclosure includes a
remote server, a mobile device including a user interface, the
mobile device being configured to send a user authentication
message initiated by the user via the user interface to the remote
server, wherein the remote server is configured to verify the user
via the user authentication message and once verified, send an
encrypted blob to the mobile device in response to the user
authentication message, and at least one equipment controller
configured to receive and decrypt the encrypted blob from the
mobile device.
[0004] Additionally to the foregoing embodiment, the mobile-based
equipment service system includes at least one site, wherein each
site of the at least one site includes at least one respective
equipment controller of the at least one equipment controller,
wherein the encrypted blob is secured by the remote server via a
unique private key associated with a respective site of the at
least one site.
[0005] In the alternative or additionally thereto, in the foregoing
embodiment, the user authentication message includes a selected
site of the at least one site selected by the user.
[0006] In the alternative or additionally thereto, in the foregoing
embodiment, the encrypted blob includes firmware and a header
configured to be extracted by a respective equipment controller of
the at least one equipment controller.
[0007] In the alternative or additionally thereto, in the foregoing
embodiment, the header includes the unique private key, and a
duration to authenticate.
[0008] In the alternative or additionally thereto, in the foregoing
embodiment, the header includes a version that is verified by the
respective equipment controller.
[0009] In the alternative or additionally thereto, in the foregoing
embodiment, the at least one site is a plurality of buildings.
[0010] In the alternative or additionally thereto, in the foregoing
embodiment, the at least one site is a plurality of geographic
regions.
[0011] In the alternative or additionally thereto, in the foregoing
embodiment, the at least one equipment controller is at least one
elevator controller.
[0012] In the alternative or additionally thereto, in the foregoing
embodiment, the at least one equipment controller does not have
internet connectivity.
[0013] In the alternative or additionally thereto, in the foregoing
embodiment, the at least one equipment controller is configured to
reply to the mobile device requesting the user authentication
message from the user.
[0014] In the alternative or additionally thereto, in the foregoing
embodiment, the encrypted blob is asymmetric encrypted.
[0015] A method of operating a mobile-based equipment service
system according to another, non-limiting, embodiment includes
sending a selected site from a mobile device to a remote server,
encrypting a blob by the remote server using a private key
associated with the selected site and preprogrammed into the remote
server, sending the encrypted blob to the mobile device, sending
the encrypted blob from the mobile device to a controller
associated with the selected site, and decrypting the encrypted
blob by the controller utilizing the private key preprogrammed into
the controller.
[0016] Additionally to the foregoing embodiment, the selected site
is selected by a user of the mobile device and is sent to the
remote server as part of an authentication message that includes
credentials of the user.
[0017] In the alternative or additionally thereto, in the foregoing
embodiment, the method includes sending a credential request from
the controller to the mobile device, entering of credentials by a
user into the mobile device, and sending the credentials from the
mobile device to the controller.
[0018] In the alternative or additionally thereto, in the foregoing
embodiment, the method includes comparing the credentials sent from
the mobile device to a hash of credentials sent as part of the
encrypted blob by the controller.
[0019] In the alternative or additionally thereto, in the foregoing
embodiment, the remote server is cloud-based.
[0020] In the alternative or additionally thereto, in the foregoing
embodiment, the mobile device is a smartphone.
[0021] In the alternative or additionally thereto, in the foregoing
embodiment, the selected site is a building and the controller is
an elevator controller.
[0022] The foregoing features and elements may be combined in
various combinations without exclusivity, unless expressly
indicated otherwise. These features and elements as well as the
operation thereof will become more apparent in light of the
following description and the accompanying drawings. However, it
should be understood that the following description and drawings
are intended to be exemplary in nature and non-limiting.
BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Various features will become apparent to those skilled in
the art from the following detailed description of the disclosed
non-limiting embodiments. The drawings that accompany the detailed
description can be briefly described as follows:
[0024] FIG. 1 is a schematic of a mobile-based equipment service
system as one, non-limiting, exemplary embodiment of the present
disclosure; and
[0025] FIG. 2 is a flowchart illustrating a method of operating the
mobile-based equipment service system.
DETAILED DESCRIPTION
[0026] Referring to FIG. 1, an exemplary embodiment of an equipment
service system 20, which may be mobile-based, generally employs
code offloading architecture and asymmetric encryption. The
equipment service system 20 may include, or may use portions of, a
mobile device 22, a remote server 24, and at least one equipment
controller 26. The mobile device 22 may communicate with the remote
server 24 and the equipment controller 26 over respective pathways
28, 30 that may be wired or wireless. If wireless, the pathways 28,
30 may be association with such communication protocols as
Bluetooth.RTM., Wi-Fi, Near Field Communications (NFC), and others.
The mobile device 22 may include a user interface 32 that
facilitates system interaction with a user (e.g., equipment
repairman). Non-limiting examples of the mobile device 22 may
include a smartphone, a tablet, and others. The remote server 24
may be cloud-based (i.e., cloud 24). The equipment service system
20 generally enables the execution of code at the cloud 24 and/or
the equipment controller 26. The mobile 22 may not execute code,
and instead, may simply be a carrier of the code. In one
embodiment, the remote server 24 and the controller 26 may be owned
and controlled by a common company.
[0027] The equipment service system 20 may further include at least
one site (i.e., two illustrated as 34, 36 in FIG. 1). Each site 34,
36 may include at last one equipment controller 26 (i.e., three
illustrated for each site 34, 36). Non-limiting examples of sites
34, 36 may be a building, a geographic region, and others. A
non-limiting example of an equipment controller 26 may be an
elevator controller that may be serviced by the manufacturer of the
elevator. The mobile device 22, the remote server 24, and the
equipment controller 26 may each include respective processors 38,
40, 42 (e.g., microprocessors), and storage mediums 44, 46, 48 that
may be computer writeable and readable.
[0028] Referring to FIG. 2, a method of operating the equipment
service system 20 is illustrated. At block 100, a user selects a
site 34, 36 and enters the selected site into the mobile device 22
via the user interface 32. In one embodiment, the user may also
enter user credentials into the mobile device 22 for security
reasons. Alternatively, the mobile device 22 may include an
application that may recognize the user credentials internally. At
block 102, the user credentials and selected site are sent to the
remote server 24 as a user authentication message (see arrow
50).
[0029] At block 104, the remote server 24 encrypts a blob with a
site-based private key associated with selected site provided by
the user. The remote server 24 may include an application that is
preprogrammed with and stores a unique private key for each
respective site 34, 36. That is, site 34 is assigned a private key
that is different than a private key of the site 36. The encryption
of the blob 52 may be an asymmetric encryption employed to protect
proprietary information contained within the blob 52. At block 106,
the remote server 24 sends the encrypted blob (see arrow 52) to the
mobile device 22.
[0030] The blob 52 may include a header and firmware. The header
may include a version (i.e., a version of the blob), a duration, a
hash of user credentials (e.g., user password), an equipment
controller identification, and a region or building code that the
equipment belongs to. The version may generally be an index. The
duration may be an authentication duration intended to provide a
validity time limit that a particular executable is valid. The hash
of user credentials is intended for use by the controller 26.
[0031] At block 108, the mobile device 22 may store the encrypted
blob 52. The user of the mobile device 22 may not be, or need not
be, aware of the encrypted blob 52 being received and/or stored by
the mobile device 22. At block 110, the mobile device 22 may send
the encrypted blob 52 to the controller 26 selected by the user
based on need and at the user selected site (i.e., site 34, or site
36. That is, when the user authenticates to the Cloud initially,
the user may request access to a given site. The Cloud may include
a database internally to check whether the requesting user has
permissions to access the associated site and/or controller, and
may then generate the blob for that controller. At block 112, the
controller 26 that receives the encrypted blob 52 may decrypt the
blob using the private key of the site receiving the blob. At block
114, the controller 26 may then extract the header, verify the
version and also note the duration that any proprietary information
is valid. At block 116, the controller 26 may request confirmation
of the user credentials by sending a credential request (see arrow
54) to the mobile device 22. At block 118, the user may input the
requested credentials (e.g., user password) via the user interface
32. At block 120, the mobile device 22 may send a credential
response (see arrow 56) to the requesting controller 26. At block
122, the controller may confirm the user by comparing the
credential response to the hash of user credentials extracted from
the header.
[0032] At block 124, the controller 26 may send an authentication
audit report (see arrow 58) through the mobile device 22, and to
the remote server 24. The authentication audit report may include
the site-based private key, thereby notifying the remote server 24
of the source of the audit report. At this point, the user may now
have access to commands via, for example, a menu.
[0033] Advantages and benefits of the present disclosure include
the secure use of a mobile device between a company cloud and a
controller. Other advantages include proprietary information that
is never exposed to undesired individuals, a system where an
attacker cannot perform dynamic memory analysis, a code that cannot
be tampered with or modified, a coding system with duration of time
limits for added security, and the prevention of user spoofing with
encoding user identity.
[0034] The various functions described above may be implemented or
supported by a computer program that is formed from computer
readable program codes and that is embodied in a computer readable
medium. Computer readable program codes may include source codes,
object codes, executable codes, and others. Computer readable
mediums may be any type of media capable of being accessed by a
computer, and may include Read Only Memory (ROM), Random Access
Memory (RAM), a hard disk drive, a compact disc (CD), a digital
video disc (DVD), or other forms.
[0035] Terms used herein such as component, module, system, and the
like are intended to refer to a computer-related entity, either
hardware, a combination of hardware and software, or software
execution. By way of example, a component may be, but is not
limited to, a process running on a processor, a processor, an
object, an executable, a thread of execution, a program, and/or a
computer. It is understood that an application running on a server
and the server may be a component. One or more components may
reside within a process and/or thread of execution and a component
may be localized on one computer and/or distributed between two or
more computers.
[0036] While the present disclosure is described with reference to
exemplary embodiments, it will be understood by those skilled in
the art that various changes may be made and equivalents may be
substituted without departing from the spirit and scope of the
present disclosure. In addition, various modifications may be
applied to adapt the teachings of the present disclosure to
particular situations, applications, and/or materials, without
departing from the essential scope thereof. The present disclosure
is thus not limited to the particular examples disclosed herein,
but includes all embodiments falling within the scope of the
appended claims.
* * * * *