Sign In to Follow Application
View All Documents & Correspondence

A System And A Method Of Securely Operating A Security Device Remotely

Abstract: A SYSTEM AND A METHOD OF SECURELY OPERATING A SECURITY DEVICE REMOTELY The present disclosure discloses a system and a method of securely operating a security device remotely. The method comprises receiving a request to unlock or lock a security device registered. The request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request. Further, the request is authenticated using the unique identification of a user device. Subsequently, a unique authentication key is generated to unlock or lock the security device based on the request. Further, the unique authentication key is transmitted to the security device to unlock or lock the security device corresponding to the request. Furthermore, the security device transmits health status of the security device to the system. In one implementation, the security device is configured to store the data in order to operate the security device in an offline mechanism i.e., without dynamically connected to the system.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
19 September 2018
Publication Number
12/2020
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
chandru619@gmail.com
Parent Application

Applicants

YUTU ELECTRONICS PRIVATE LIMITED
F - no - 902, Ittina Akkala Hoody, Rajpalya Bangalore North Bangalore KARNATAKA-560048, INDIA.

Inventors

1. ABHISHEK SRIVASTAVA
F - no - 902, Ittina Akkala Hoody, Rajpalya Bangalore North Bangalore KARNATAKA-560048, INDIA.
2. AMIT DIDWANIA
F - no - 902, Ittina Akkala Hoody, Rajpalya Bangalore North Bangalore KARNATAKA-560048 INDIA.

Specification

Claims:WE CLAIM:

1. A method of securely operating a security device remotely, the method comprising:
receiving, by a processor, a request to unlock or lock a security device registered, wherein the request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request;
authenticating, by the processor, the request received, wherein the request is authenticated using the unique identification of a user device;
generating, by the processor, a unique authentication key to unlock or lock the security device based on the request; and
transmitting, by the processor, the unique authentication key to the security device to unlock or lock the security device corresponding to the request.

2. The method as claimed in claim 1, further comprising receiving a notification from the security device indicating a status of unlock or lock of the security device corresponding to the request.

3. The method as claimed in claim 2, further comprising transmitting the notification received from the security device to the user device.

4. The method as claimed in claim 1, wherein the unique identification of the security device is generated using encryption algorithms.

5. The method as claimed in claim 1, further comprising receiving a health status and audit trails of the security device.

6. A system of securely operating a security device remotely, the system comprising:
a processor; and
a memory coupled to the processor, wherein the processor executes program instructions stored in the memory, to:
receive a request to unlock or lock a security device registered, wherein the request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request;
authenticate the request received, wherein the request is authenticated using the unique identification of a user device;
generate an unique authentication key to unlock or lock the security device based on the request; and
transmit the unique authentication key to the security device to unlock or lock the security device corresponding to the request.

7. The system as claimed in claim 6, wherein the security device comprises one of a padlock, smart lock, lever lock, a dead lock, a knob lock and a door latch.

8. The system as claimed in claim 6, wherein the security device further comprises a tamper sensor for detecting tampering of the security device.

9. The system as claimed in claim 6, wherein the processor further receives a notification from the security device indicating a status of unlock or lock of the security device corresponding to the request.

10. The system as claimed in claim 6, wherein the processor further transmits the notification received from the security device to the user device.

, Description:A SYSTEM AND A METHOD OF SECURELY OPERATING A SECURITY DEVICE REMOTELY

FIELD OF INVENTION

[01] The present disclosure relates to a field of electronic lockers. More particularly, the present disclosure relates to a system and a method of securely operating a security device remotely.

BACKGROUND

[02] It is known goods are transported using several means. For example, the goods may include precious jewelry, currency notes, bonds, electronic goods, furniture and so on. Typically, the goods may be transported by using roadways, waterways or by air. When the goods are being transported, an owner of the goods may transport the goods on his own or may engage a service provider to transport the goods from one place to another, e.g., from one city to another.

[03] Typically, the owner engages the service provider to transport the goods within a predefined time at a predefined cost. Generally, the service provider packs the goods and secures the goods using a lock. The lock may include a padlock, a lever lock, a dead lock, a knob lock and a door latch. It should be understood that the service provider locks a container carrying the goods at a pickup location. After locking, the service provider keeps the lock with himself and transports the goods to a destination. After reaching the destination, the service provider may unlock the lock and deliver the goods at the destination.

[04] It should be understood the service provider may easily tamper the lock and the goods may be altered in its transit. Further, if several service providers transport the goods, then the owner cannot trace the tampering of the lock and further cannot trace the goods altered. As a result, the owner may not be able to catch hold of the service provider who altered the goods by tampering the lock.

[05] Therefore, there is a need for an electronic lock that can be tracked by the user easily.

SUMMARY

[06] The problems in the existing art are met by providing a system and a method of securely operating a security device remotely.

[07] In one implementation, a method of securely operating a security device remotely is disclosed. The method comprises receiving, by a processor, a request to unlock or lock a security device registered. The request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request. The method further comprises authenticating, by the processor, the request received. The request is authenticated using the unique identification of a user device. The method further comprises generating, by the processor, a unique authentication key to unlock or lock the security device based on the request. The method further comprises transmitting, by the processor, the unique authentication key to the security device to unlock or lock the security device corresponding to the request.

[08] In another implementation, a system of securely operating a security device remotely is disclosed. The system comprises a processor and a memory coupled to the processor. The processor executes program instructions stored in the memory, to receive a request to unlock or lock a security device registered. The request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request. The processor further executes the program instructions stored in the memory to authenticate the request received. The request is authenticated using the unique identification of a user device. The processor further executes the program instructions stored in the memory to generate a unique authentication key to unlock or lock the security device based on the request. The processor further executes the program instructions stored in the memory to transmit the unique authentication key to the security device to unlock or lock the security device corresponding to the request.

[09] Further advantages and examples of the invention will be brought out in the following part of the specification, wherein detailed description is for the purpose of fully disclosing the invention without placing limitations thereon.

BRIEF DESCRIPTION OF FIGURES

[010] In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the disclosure, and the disclosure is not limited to the examples depicted in the figures.

[011] FIG. 1illustrates an environment of a system for securely operating a security device remotely, in accordance with one embodiment of the present disclosure;

[012] FIG. 2illustrates the security device, in accordance with one exemplary embodiment of the present disclosure;

[013] FIG. 3 illustrates a timing diagram for setting up of the security device and accessing the security device by a user device, in accordance with one exemplary embodiment of the present disclosure; and

[014] FIG. 4illustrates a method of securely operating a security device, in accordance with one exemplary embodiment of the present disclosure.

DETAILEDDESCRIPTION

[015] The following detailed description is intended to provide example implementations to one of ordinary skill in the art, and is not intended to limit the disclosure to the explicit disclosure, as one of ordinary skill in the art will understand that variations can be substituted that are within the scope of the disclosure as described.

[016] The present disclosure discloses a system and a method of securely operating a security device remotely. At first, a request is received to unlock or lock a security device registered. The request comprises a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request. Further, the request is authenticated using the unique identification of a user device. Subsequently, a unique authentication key is generated to unlock or lock the security device based on the request. Further, the unique authentication key is transmitted to the security device to unlock or lock the security device corresponding to the request.

[017] Various embodiments of the present disclosure for securely operating a security device remotely are explained with the help of FIGs 1-4.

[018] Referring to FIG. 1A, an environment 100 of a system 105 for securely operating a security device120 is illustrated, in accordance with various embodiments of the invention. The environment 100 includes the system 105, at least one user device 110, and the security device 120.

[019] Although the present disclosure is explained by considering that the system 105 is implemented on a server, it may be understood that the system 105 may also be implemented in a variety of computing systems, such as a mainframe computer, a network server, cloud, and the like. It will be understood that the system 105 may be accessed a user through the user device 110, or applications residing on the user devices 110. Examples of the user device 110 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. The user device 110 is communicatively coupled to the system 105 through a network 115.

[020] In one implementation, the network 115 may be a wireless network, a wired network or a combination thereof. The network 115 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 115 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 115 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

[021] Further, the system 105 is communicatively coupled to the security device 120 through the network 115. The security device 120 may include, but not limited to, a padlock, smart lock, lever lock, a dead lock, a knob lock and a door latch.

[022] As can be seen, the system 105 comprises at least one first processor 125, a first memory 130 and a first Input/Output (I/O) Interface 135. The at least one first processor 125 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one first processor 125 is configured to fetch and execute computer-readable instructions stored in the first memory 130.

[023] The first memory 130may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

[024] The first I/O interface 135 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The first I/O interface 135 may allow the system 105 to interact with the user device 110, and the security device 110. The first I/O interface 135 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, Bluetooth, Near Field Communication (NFC), Light Fidelity (Li-Fi), Wi-Fi, cellular, or satellite. The first I/O interface 135 may include one or more ports for connecting a number of devices to one another.

[025] In one embodiment, the system 105 may be communicatively coupled to a Hardware Security Module (HSM) 140. The function of the HSM module 140 is explained in later portions of the description.

[026] Referring to FIG. 2, the security device 120 comprises a second processor 150, a second memory 155, a second interface 160, a transceiver 165, a tamper sensor 170, an audio output 175, a battery 180, and a location sensor 185.

[027] The second processor 150 may be implemented as one or more microprocessors, microcomputers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the second processor 150 is configured to fetch and execute computer-readable instructions or program instructions stored in the second memory 155.

[028] The second memory 155 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, and so on.

[029] The second interface 160 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The second interface 160 may allow the security device 120 to interact with a user directly or through user devices 110 or the system 105.

[030] The transceiver 165is used to transmit and receive signal/data from the security device 120 to external devices such as system 105 or the user device 110.

[031] The tamper sensor 170 may indicate a sensor or an electronic circuit capable of detecting tampering of the security device 120.

[001] The audio output 175 may indicate a speaker to announce instructions provided by the second processor 150.

[002] The battery 180 is used to power the security device 120. The battery 180 may include a rechargeable battery e.g., a Lithium-Ion battery.

[003] The location sensor 185 may include but not limited to a Global Positioning System (GPS) sensor used to determine location of the security device 120.

[032] The security device 120 may be associated with a service provider. For example, considering that the security device 120 is used to lock a container (not shown)storing valuable items such as jewelry, bonds, household items and so on. As such, the security device 120 is registered with the system 105. In order to register the security device 120 with the system 105, the service provider may provide details such as a unique identification of the security device 120, location such as coordinates of the security device 120, unique features of the security device 120 and so on.

[033] Further, the system 105 upon receiving details of security device 120 stores the information in the first memory 130. In one example, the system 105 may store the information corresponding to the security device 120 in the HSM memory 140.

[034] Now referring to FIG. 3, a timing diagram 200 illustrating the setting up of the security device 120 and accessing the security device 120 by the user device 110 is explained, in accordance with one embodiment of the present disclosure.

[035] As specified above, the security device 120 comprises the unique identification. In order to register with the system 105, at first, the security device 120 initiates a request. In one example, the request may be sent using an encryption key, as shown at step 205. The request may comprise information corresponding to the security device 120 such as location, features of the security device 120 and so on.

[036] At step 210, based on the information received in the request, the system 105 generates a new encryption key and transmits to the security device 120. Subsequently, the security device 120 acknowledges the receipt of the new encryption key, as shown at step 215.

[037] At step 220, the system 105 generates authentication keys for the security device 120 and transmits to the security device 120. In one example, the system 105 generates the authentication keys using an AES encryption algorithm. The system 105 transmits the authentication keys to set up the security device 120.

[038] At step 225, after receiving the authentication keys, the security device 120 acknowledges the receipt.

[039] At step 230, the security device 120 transmits health parameters of the security device 120 at regular intervals. In one example, the interval time may be pre-defined by the user of the security device 120.

[040] After setting up the security device 120 i.e., registering the security device 120 with the system 105, the security device 120 may be accessed by the user device 110 via the system 105.

[041] In order to use the security device 120, a user of the user device 110 may have to register with the system 105. The user may register with the system 105 by providing details such as name, address, Date of Birth, Permanent Account Number, Unique identification Number of the user e.g., a social security number. After providing the details, the system 105 may request further details such as Unique Identification (ID) of the user device 110. The unique ID of the user device 110 may include the International Mobile Equipment Identity (IMEI) number. Further, the system 105 may request for Subscriber Identification Module (SIM) number of the user device 110. After receiving the details, the system 105 may send a One-Time Passcode (OTP) to authenticate the user device 110. Upon authentication, the system 105 registers the details of the user and the user device 110. The system 105 stores the details of the user and the user device 110 in the first memory 130.

[042] The current implementation is explained considering that the user wishes to use the security device 120 for locking a container (not shown) transporting goods from one place to another. As such, the security device 120 may be provided to lock the container. However, it should be understood that the current implementation is not construed to limit the invention. The security device 120 may be used to lock any other objects such as doors, vehicles and so on.

[043] It should be understood that the user may access the security device 120 remotely or coming in proximity to the security device 120. In order to access the security device 120 remotely, GPRS/GPRS/EDGE/3G/4G/5G/Wi-Fi and GPS and other wireless network may be used. Further, in order to access the security device 120 when in proximity, the user device 110 may utilize Bluetooth, NFC and so on.

[044] In order to access the security device 120, the user of the user device 110 may use the application in the user device 110. Further, the user may select the security device 120 he wishes to use for locking the container transporting the goods. The user may select the time period for which he wishes to use the security device 120. The user may access the security device 120 for performing various actions such as lock the security device 120, unlock the security device 120, request status of the security device 120, location of the security device 120, audit trial of the security device 120 and so on.

[045] In order to perform any of the actions specified, at first, the user of the user device 110 may raise a request to the security device 120, as shown at step 250 in FIG. 3. For example, consider that the user sends the request to unlock the security device 120, and then the request is sent to the security device 120. In one example, the user may send the request to the system 105 to unlock the security device 120. The request may comprise location of the user device 110 and phone number of the user device 110. If the request is sent to the security device 120, then the request is forwarded to the system 105 by the security device 120, as shown at step 255.

[046] At step 260, the system 105 checks the request i.e., checks whether the user device 105 is registered with the system 105. If the user device 110 details match with the information stored in the system 105, then the system 105 sends the authentication keys to the security device 120.

[047] Subsequently, the security device 120 unlocks based on the request. At step 265, the security device 120 sends acknowledgment or a notification to the user device 110. Subsequently, the security device 120 sends an unlock report packet to the system 105 to update the system 105. The unlock report packet may comprise details such as time, location, mobile number and other features of the security device 120.

[048] The above procedure is repeated to lock the security device 120. It should be understood that the user might send a request to the system, 105 or the security device 120 to get status of the security device 120.

[049] Further, the security device 120 employs the tamper sensor 170 to detect tampering of the security device 120. For example, if any unauthorized person tries to access the security device 120, then the tamper sensor 170 detects that the unauthorized usage and sends an alert to the system 105 and to the user device 110. In one example, the audio output 175 may be configured to generate an alarm when the tamper sensor 170 detects tampering of the security device 120.

[050] Further, the security device 120 stores log of each activity such as unlocks request, lock request, health status request and updates the details with the system 105.

[051] As explained above, the security device 120 comprises the location sensor 185. As such, the user may obtain the location of the security device 120 by sending a request to the security device 120 or the system 105.

[052] In one implementation, the security device 120 may be operated without being connected to the system 105 at all times. In order to operate the security device 120, at first, the authorization keys are transmitted to both the security device 120 and the user device 110. The security device 120 may identify the user device 110 using the known techniques such as using advertising packets. After identifying, the authentication keys are provided to the security device 120 to authenticate the user device 110. After authenticating, the use of the user device 110 may unlock the security device 120 and access the container.

[053] As such, the security device 120 may be used online and offline modes.

[054] Referring to FIG. 4, a method 300 of securely operating a security device remotely is shown in accordance with one embodiment of the present disclosure. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.

[055] The order in which the method 300 is described and is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the disclosure described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 300 may be implemented in the above-described system 105.

[056] At step 305, a request to unlock or lock or health status of a security device is received. The request may comprise a unique identification of the security device, a location of the security device, and a unique identification of a user device sending the request.

[057] At step 310, the request received may be authenticated using the unique identification of a user device.

[058] At step 315, a unique authentication key to unlock or lock or to update health status of the security device is generated based on the request.

[059] At step 320, the unique authentication key is transmitted to the security device to unlock or lock or to provide health status of the security device corresponding to the request.

[060] As it is evident from above description, location of the security device can be tracked in real time and lock and unlock operations may be tracked remotely by the system or the user device. In addition, the security device may be configured to lock itself in certain location by defining geo-locations in the set up phase. As such, the security device remains locked in certain locations.

[061] Further, the authentication key is generated using cryptography algorithms. As such, the lock and unlock operations by unauthorized users is not possible.

[062] Although the above examples are provided for illustration purpose, one skilled in the art will appreciate use of present disclosure to deliver or transport goods or home locks or in other applications such transportation, agricultural and other applications.

[063] Although embodiments of a method of securely operating a security device remotely have been described in a language specific to features and/or methods, it is to be understood that the description is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations of securely operating a security device remotely.

Documents

Application Documents

# Name Date
1 201841035254-STATEMENT OF UNDERTAKING (FORM 3) [19-09-2018(online)].pdf 2018-09-19
2 201841035254-REQUEST FOR EXAMINATION (FORM-18) [19-09-2018(online)].pdf 2018-09-19
3 201841035254-POWER OF AUTHORITY [19-09-2018(online)].pdf 2018-09-19
4 201841035254-OTHERS [19-09-2018(online)].pdf 2018-09-19
5 201841035254-FORM FOR STARTUP [19-09-2018(online)].pdf 2018-09-19
6 201841035254-FORM FOR SMALL ENTITY(FORM-28) [19-09-2018(online)].pdf 2018-09-19
7 201841035254-FORM 18 [19-09-2018(online)].pdf 2018-09-19
8 201841035254-FORM 1 [19-09-2018(online)].pdf 2018-09-19
9 201841035254-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [19-09-2018(online)].pdf 2018-09-19
10 201841035254-DRAWINGS [19-09-2018(online)].pdf 2018-09-19
11 201841035254-DECLARATION OF INVENTORSHIP (FORM 5) [19-09-2018(online)].pdf 2018-09-19
12 201841035254-COMPLETE SPECIFICATION [19-09-2018(online)].pdf 2018-09-19
13 201841035254-Proof of Right (MANDATORY) [24-09-2018(online)].pdf 2018-09-24
14 Correspondence by Applicant_DIPP Certificate_26-09-2018.pdf 2018-09-26
15 Correspondence by Applicant_Startup_30-11-2018.pdf 2018-11-30
16 201841035254-FER.pdf 2021-10-17

Search Strategy

1 2021-02-2522-23-33E_26-02-2021.pdf