Patent Publication Number: US-11394705-B2

Title: Systems and methods for verifying credentials to perform a secured operation in a connected system

Description:
FIELD 
     The present invention relates generally to a connected system, such as a security system or a home automation system. More particularly, the present invention relates to systems and methods for verifying credentials to perform a secured operation in the connected system. 
     BACKGROUND 
     Known systems and methods for controlling a connected system may use mobile or remote interface devices for initiating secured operations in the connected system. However, known systems and methods verify user credentials using only a single layer of security, such as password verification, thereby leaving the connected system vulnerable to hacking and other infiltration methods. Indeed, known systems and method are especially susceptible to these types of risks because of the mobile nature of the mobile and remote interface devices. 
     In view of the above, there is a continuing, ongoing need for improved systems and methods. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagram of a verification system in accordance with disclosed embodiments; 
         FIG. 2  is a flow diagram of a method in accordance with disclosed embodiments; and 
         FIG. 3  is a flow diagram of a method in accordance with disclosed embodiments. 
     
    
    
     DETAILED DESCRIPTION 
     While this invention is susceptible of an embodiment in many different forms, there are shown in the drawings and will be described herein in detail specific embodiments thereof with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention. It is not intended to limit the invention to the specific illustrated embodiments. 
     Embodiments disclosed herein may include systems and methods for verifying credentials to perform a secured operation in a connected system. For example, systems and methods disclosed herein may determine whether both a face in an image and an activation code received by a cloud server from a mobile interface device are valid or invalid. 
     Systems and methods as disclosed herein are described in connection with a verification system for connected systems, such as home automation systems and security systems. It is to be understood that such systems may include, but are not limited to systems that include the cloud server, the mobile interface device communicating with the cloud server, and a connected system controlled by the mobile interface device via the cloud server. 
     In accordance with disclosed embodiments, the mobile interface device may receive first user input indicative of a request to perform the secured operation in the connected system and, responsive thereto, systems and methods disclosed herein can execute an enhanced verification procedure as disclosed herein. In some embodiments, systems and methods disclosed herein can execute the enhanced verification procedure disclosed herein responsive to the request to perform the secured operation when the secured operation has been previously identified as one of a plurality of high level verification operations. Additionally or alternatively, in some embodiments, systems and methods disclosed herein can execute the enhanced verification procedure disclosed herein responsive to the request to perform any secured operation in the connected system. In some embodiments, the secured operation may include arming the connected system, disarming the connected system, or programing the connected system. 
     Responsive to the first user input and during the enhanced verification procedure disclosed herein, the mobile interface device may enter a facial recognition mode. In some embodiments, when in the facial recognition mode, the mobile interface device may activate a built-in camera to capture a first image of a field of view of the built-in camera and identify a presence of a face or an absence of the face in the first image. When the mobile interface device identifies the absence of the face in the first image, the mobile interface device may terminate the facial recognition mode and refrain from transmitting or executing the request to perform the secured operation identified in the first user input. However, when the mobile interface device identifies the presence of the face in the first image, the mobile interface device may solicit second user input indicative of an activation code. 
     In some embodiments, when in the facial recognition mode, the mobile interface device may activate the built-in camera to capture the first image of the field of view of the built-in camera and transmit the first image to the cloud server for identifying the presence of the face or the absence of the face in the first image. When the cloud server identifies the absence of the face in the first image, the cloud server device may instruct the mobile interface to terminate the facial recognition mode and refrain from transmitting or executing the request to perform the secured operation identified in the first user input. However, when the cloud server identifies the presence of the face in the first image, the cloud server can instruct the mobile interface device to solicit the second user input indicative of the activation code. 
     In some embodiments, when in the facial recognition mode, the mobile interface device may activate the built-in camera to capture the first image of the field of view of the built-in camera and solicit the second user input indicative the activation code regardless of any determination as to the presence of the face or the absence of the face in the first image. 
     In some embodiments, responsive to the first user input, the mobile interface device may solicit third user input accepting or rejecting the facial recognition mode. When the third user input accepts the facial recognition mode, the mobile interface device may enter the facial recognition mode. However, when the third user input rejects the facial recognition mode, the mobile interface device may refrain from entering the facial recognition mode and refrain from transmitting or executing the request to perform the secured operation identified in the first user input. 
     In some embodiments, the mobile interface device may initiate a timer upon entering the facial recognition mode and may identify the absence of the face in the first image when the mobile interface device fails to identify the presence of the face in the first image before the timer expires. 
     In accordance with disclosed embodiments, the mobile interface device may transmit the request to perform the secured operation, the first image, and the activation code to the cloud server, and the cloud server may determine whether the activation code and the face in the first image are valid or invalid. When both the activation code and the face in the first image are valid, the cloud server may transmit an instructional signal to the connected system to execute the secured operation. However, when at least one of the activation code and the face in the first image is invalid, the cloud server may refrain from transmitting the instructional signal to the connected system to execute the secured operation. In some embodiments, the cloud server may transmit an informational signal to the mobile interface indicative of whether or not the cloud server instructed the connected system to execute the secured operation. 
     In some embodiments, to determine whether the activation code is valid or invalid, the cloud server may compare the activation code to a preconfigured code stored in a memory of the cloud server. When the activation code matches the preconfigured code, the cloud server may determine that the activation code is valid, and when the activation code fails to match the preconfigured code, the cloud server may determine that the activation code is invalid. 
     In some embodiments, to determine whether the face in the first image is valid or invalid, the cloud server may compare the face in the first image to a second image of an authorized user stored in the memory of the cloud server. When the face in the first image matches the second image of the authorized user, the cloud server may determine that the face in the first image is valid, and when the face in the first image fails to match the second image of the authorized user, the cloud server may determine that the face in the first is invalid. 
     In some embodiments, to determine whether the activation code and the face in the first image are valid or invalid, the cloud server may compare the face in the first image to the second image of the authorized user to confirm that the face in the first image matches the second image of the authorized user and to identify the authorized user and may compare the activation code to the preconfigured code assigned to the authorized user. When the face in the first image matches the second image of the authorized user and the activation code matches the preconfigured code assigned to the authorized user, the cloud server may determine that the activation code is valid. However, when the face in the first image matches the second image of the authorized user, but the activation code fails to match the preconfigured code assigned to the authorized user, the cloud server may determine that the activation code is invalid. 
     In some embodiments, when the cloud server determines that the face in the first image and the activation code are valid, the cloud server may determine whether the authorized user is authorized for the secured operation. 
       FIG. 1  is a block diagram of a verification system  20  in accordance with disclosed embodiments. As seen in  FIG. 1 , the verification system  20  may include a connected system  22 , a mobile interface device  24  with a built-in camera  28 , and a cloud server  26  coupled to mobile interface device  24  and the connected system  22 . 
       FIG. 2  is flow diagram of a method  100  in accordance with disclosed embodiments. The method  100  may include the mobile interface device  24  receiving an activation code and using the built-in camera  28  to capture an image of a field of view of the built-in camera  28 , as in  102 . The method  100  may also include the mobile interface device  24  transmitting or uploading a request to perform a secured operation, the image, and the activation code to the cloud server  26 , as in  104 , and the cloud server  26  determining whether a face in the image and the activation code are valid, as in  106 . As seen in  FIG. 2 , when the cloud server determines that both the face in the image and the activation code are valid, the cloud server  26  may transmit a command to the connected system  22  to execute the secured operation, such as disarming the connected system  22 , as in  108 . 
       FIG. 3  is flow diagram of a method  200  in accordance with disclosed embodiments. The method  200  can include the mobile interface device  24  receiving the activation code and using the built-in camera  28  to capture the image of the field of view of the camera  28 , as in  202 . The method  200  may also include the mobile interface device  24  transmitting or uploading the request to perform the secured operation, the image, and the activation code to the cloud server  26 , as in  204 , and the cloud server  26  determining whether the face in the image and the activation code are valid, as in  206 . As seen in  FIG. 3 , when the cloud server determines that the face in the image is invalid, that the image fails to include any face, or that the activation code is invalid, the cloud server  26  may refrain from transmitting the command to the connected system  22  to execute the secured operation, as in  208 . 
     Although a few embodiments have been described in detail above, other modifications are possible. For example, the steps described above do not require the particular order described or sequential order to achieve desirable results. Other steps may be provided, steps may be eliminated from the described flows, and other components may be added to or removed from the described systems. Other embodiments may be within the scope of the invention. 
     From the foregoing, it will be observed that numerous variations and modifications may be effected without departing from the spirit and scope of the invention. It is to be understood that no limitation with respect to the specific system or method described herein is intended or should be inferred. It is, of course, intended to cover all such modifications as fall within the spirit and scope of the invention.