IP Library Granted Patent US 11,838,180
Granted Patent B2
US 11,838,180 · App. 17/962,333 · Granted Dec 5, 2023

Cloud connector system for establishing a secure connection between cloud server and a tenant

Inventors: Anand Purusothaman (Coimbatore, IN); Sunil Kumar Poozhikunnath Ramakrishnan (Palakkad, IN); Rajesh Kumar Kunnathuvayalil Velayudhan (Kerala, IN); Aishwarya Ramachandran (Coimbatore, IN)
Assignee: APPVIEWX INC.
H04L41/082H04L67/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,838,180
App. No.
17/962,333
Granted
Dec 5, 2023
Kind
B2
Abstract

A computer-implemented method for enabling a cloud connector system ( 100 ) to establish a secure connection between on-premise devices and a cloud server ( 108 ) hosting a cloud Certificate Lifecycle Management as a Service (CLMaaS) for validating and upgrading a certificate on the on-premise devices is provided. The method includes implementing a plurality of cloud connectors ( 102 A-N) in a tenant premise comprising a plurality of on-premise devices ( 104 A-N) to establish a full-duplex connection between the plurality of on-premise devices and the CLMaaS, performing a runtime analysis of the connection between the cloud server and the plurality of cloud connectors, routing the requests from the cloud CLMaaS to the plurality of on-premise devices through the plurality of cloud connectors based on the run time analysis of the connection, and enabling the cloud connector system to execute the certificate validation and upgradation in the on-premise devices based on the request from the cloud CLMaaS.

Claims (27)

1. A method of enabling a cloud connector system ( 100 ) to establish a secure connection between on-premise devices and a cloud server ( 108 ) hosting a cloud Certificate Lifecycle Management as a Service (CLMaaS) for validating and upgrading a certificate on the on-premise devices, the method comprises:

implementing, a plurality of cloud connectors ( 102 A-N) in a tenant premise comprising a plurality of on-premise devices ( 104 A-N) to establish a full-duplex connection between the plurality of on-premise devices ( 104 A-N) and the cloud Certificate Lifecycle Management as a Service (CLMaaS) hosted on the cloud server ( 108 ) with the plurality of cloud connectors ( 102 A-N), wherein the plurality of cloud connectors ( 102 A-N) are configured to accept requests related to certificate validation and upgradation from the cloud CLMaaS through a cloud connector proxy server and execute the requests in the plurality of on-premise devices ( 104 A-N) on behalf of device communication layer of the cloud CLMaaS, wherein the plurality of cloud connectors ( 102 A-N) are hosted with in a datacenter;

performing, a runtime analysis of the connection between the cloud server ( 108 ) and the plurality of cloud connectors ( 102 A-N), wherein the runtime analysis of the connection is performed based on the number of requests received per minute from the cloud CLMaaS to the plurality of cloud connectors ( 102 A-N);

routing, the requests from the cloud CLMaaS to the plurality of on-premise devices ( 104 A-N) through the plurality of cloud connectors ( 102 A-N) based on the runtime analysis of the connection, wherein a data center routes the requests between the plurality of cloud connectors ( 102 A-N) based on the runtime analysis of the connection; and

enabling the cloud connector system ( 100 ) to execute the certificate validation and upgradation in the on-premise devices based on the request from the cloud CLMaaS.

2. The method as claimed in claim 1 , wherein the cloud connector system ( 100 ) routes the requests between the plurality of cloud connectors ( 102 A-N) within the data center.

3. The method as claimed in claim 1 , wherein the device communication layers communicate through common libraries comprising at least one of SSH connector, REST connector, SFTP connector, Email Connector.

4. The method as claimed in claim 1 , wherein the cloud connector proxy server accepts requests from the device communication layers and routes the requests to the plurality of cloud connectors ( 102 A-N).

5. The method as claimed in claim 1 , wherein the plurality of cloud connectors ( 102 A-N) employs mTLS and AES256 authentication to communicate with the plurality of on-premise devices ( 104 A-N) and the cloud server ( 108 ).

6. The method as claimed in claim 1 , wherein the plurality of cloud connectors ( 102 A-N) run in an internal network of the plurality of on-premise devices ( 104 A-N).

7. The method as claimed in claim 1 , wherein each of the cloud connectors comprises a dedicated channel for communication with each of the on-premise devices.

8. The method as claimed in claim 1 , wherein the runtime analysis of the connection provides a health status of the connection indicated as (i) “good” when the number of requests is >=9 out of 10, (ii) “poor” when the number of requests is >=1 out of 10, (iii) “failed” when the number of requests is 0 out of 10, wherein the health status of the plurality of cloud connectors ( 102 A-N) are indicated as color codes.

9. The method as claimed in claim 1 , wherein the method includes passing previously managed certificates in the cloud CLMaaS to the plurality of on-premise devices ( 104 A-N) through the plurality of cloud connectors ( 102 A-N) based on the runtime analysis of the connection.

10. A cloud connector system ( 100 ) for establishing a secure connection between on-premise devices and a cloud server ( 108 ) hosting a cloud Certificate Lifecycle Management as a Service (CLMaaS) for validating and upgrading a certificate on the on-premise devices, the system comprises:

a memory unit that stores a database and a set of instructions; and

a processor that executes the set of instructions and is configured to:

implementing, a plurality of cloud connectors ( 102 A-N) in a tenant premise comprising a plurality of on-premise devices ( 104 A-N) to establish a full-duplex connection between a plurality of on-premise devices ( 104 A-N) and the cloud Certificate Lifecycle Management as a Service (CLMaaS) hosted on the cloud server ( 108 ) with a plurality of cloud connectors ( 102 A-N), wherein the plurality of cloud connectors ( 102 A-N) are configured to accept requests related to certificate validation and upgradation from the cloud CLMaaS through a cloud connector proxy server and execute the requests in the plurality of on-premise devices ( 104 A-N) on behalf of device communication layers of the cloud CLMaaS, wherein the plurality of cloud connectors ( 102 A-N) are hosted with in a datacenter;

performing, a runtime analysis of the connection between the cloud server ( 108 ) and the plurality of cloud connectors ( 102 A-N), wherein the runtime analysis of the connection is performed based on the number of requests received per minute from the cloud CLMaaS to the plurality of cloud connectors ( 102 A-N);

routing, the requests from the cloud CLMaaS to the plurality of on-premise devices ( 104 A-N) through the plurality of cloud connectors ( 102 A-N) based on the runtime analysis of the connection, wherein the data center routes the requests between the plurality of cloud connectors ( 102 A-N) within a datacenter based on the runtime analysis of the connection; enabling the cloud connector system ( 100 ) to execute the certificate validation and upgradation in the on-premise devices based on the request from the cloud CLMaaS.

11. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the cloud connector system ( 100 ) routes the requests between the plurality of cloud connectors ( 102 A-N) within the data center.

12. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the device communication layer communicate through common libraries comprising at least one of SSH connector, REST connector, SFTP connector, Email Connector.

13. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the cloud connector proxy server accepts requests from the device communication layers and routes the requests to the plurality of cloud connectors ( 102 A-N).

14. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the plurality of cloud connectors ( 102 A-N) employs mTLS and AES256 authentication to communicate with the plurality of on-premise devices ( 104 A-N) and the cloud server ( 108 ).

15. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the plurality of cloud connectors ( 102 A-N) run in an internal network of the plurality of on-premise devices ( 104 A-N).

16. The cloud connector system ( 100 ) as claimed in claim 10 , wherein each of the cloud connector comprises a dedicated channel for communication with each of the on-premise devices.

17. The cloud connector system ( 100 ) as claimed in claim 10 , wherein the runtime analysis of the connection provides a health status of the connection indicated as (i) “good” when the number of requests is >=9 out of 10, (ii) “poor” when the number of requests is >=1 out of 10, (iii) “failed” when the number of requests is 0 out of 10, wherein the health status of the plurality of cloud connectors ( 102 A-N) are indicated as color codes.

18. A one or more non-transitory computer-readable storage mediums storing the one or more sequences of instructions, which when executed by the one or more processors, causes to perform a method of enabling a cloud connector system ( 100 ) to establish a secure connection between on-premise devices and a cloud server ( 108 ) hosting a cloud Certificate Lifecycle Management as a Service (CLMaaS) for validating and upgrading a certificate on the on-premise devices, the method comprising: implementing, a plurality of cloud connectors ( 102 A-N) in a tenant premise comprising a plurality of on-premise devices ( 104 A-N) to establish a full-duplex connection between the plurality of on-premise devices ( 104 A-N) and the cloud Certificate Lifecycle Management as a Service (CLMaaS) hosted on the cloud server ( 108 ) with a plurality of cloud connectors ( 102 A-N), wherein the plurality of cloud connectors ( 102 A-N) are configured to accept requests related to certificate validation and upgradation from the cloud CLMaaS through a cloud connector proxy server and execute the requests in the plurality of on-premise devices ( 104 A-N) on behalf of device communication layers of the cloud CLMaaS, wherein the plurality of cloud connectors ( 102 A-N) are hosted with in a datacenter; performing, a runtime analysis of the connection between the cloud server ( 108 ) and the plurality of cloud connectors ( 102 A-N), wherein the runtime analysis is performed based on the number of requests received per minute from the cloud CLMaaS to the plurality of cloud connectors ( 102 A-N); routing, the requests from the cloud CLMaaS to the plurality of on-premise devices ( 104 A-N) through the plurality of cloud connectors ( 102 A-N) based on the runtime analysis of the connection, wherein the data center routes the requests between the plurality of cloud connectors ( 102 A-N) within a datacenter based on the runtime analysis of the connection; and enabling the cloud connector system ( 100 ) to execute the certificate validation and upgradation in the on-premise devices based on the request from the cloud CLMaaS.

Assignments (2)
SECURITY INTEREST/INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 24, 2024
From: APPVIEWX, INC.
To: AB PRIVATE CREDIT INVESTORS LLC
Reel/Frame 069775/0588 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2022
From: PURUSOTHAMAN, ANAND; POOZHIKUNNATH RAMAKRISHNAN, SUNIL KUMAR; KUNNATHUVAYALIL VELAYUDHAN, RAJESH KUMAR; RAMACHANDRAN, AISHWARYA
To: APPVIEWX INC.
Reel/Frame 061383/0442 →
Continuity (2)
Provisional Application 63253460 · Oct 7, 2021
Related Publication 20230114232A1 · Apr 13, 2023