IP Library Granted Patent US 10,645,197
Granted Patent B1
US 10,645,197 · App. 16/556,813 · Granted May 5, 2020

Method and a system for a secure link-up to a non-secure synchronous connection and a machine-readable carrier configured for performing the method

Inventors: Andrii Sharipov (Kyiv, UA); Iurii Skoliar (Kyiv, UA); Volodymyr Shelest (Kyiv, UA)
Assignee: Clario Tech Limited
H04L67/42G06F3/1236G06F3/1288H04L63/101H04L9/3247
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 10,645,197
App. No.
16/556,813
Granted
May 5, 2020
Kind
B1
Abstract

A computer system and methods for interaction between processes of software components of a computer system or elements of an operating system are provided. The method comprises: (i) making a request from the Client for a synchronous connection to the Server, (ii) verifying a unique name of the synchronous connection, (iii) making a request for a unique name of the synchronous connection via an asynchronous connection of the Client and Server, if there is no unique name of the synchronous connection among the created connections to the Server, (iv) verifying whether the Client is whitelisted in a list of Clients having permission to connect to the Server, (v) generating a unique name of the synchronous connection for Clients, (vi) creating a synchronous connection with the generated unique name, (vii) sending the name of the generated synchronous connection to the Client, (viii) linking up the Client to the Server.

Claims (40)

1. A method for providing a secure link-up to a non-secure synchronous connection, the method comprising:

(i) making a request from a Client for a synchronous connection to a Server,

(ii) verifying a unique name of the synchronous connection among created connections to the Server,

(iii) making a request for a unique name of the synchronous connection via an asynchronous connection of the Client and Server, if there is no unique name of the synchronous connection among the created connections to the Server,

(iv) verifying, by the Server, whether the Client is whitelisted in a list of Clients that are permitted to connect to the Server, according to a Client identifier, wherein a process identifier (process id) and/or a software application identifier (bundle id) and/or a digital signature is defined as the Client identifier,

(v) generating, by the Server, a unique name of the synchronous connection for Clients that are permitted to connect to the Server, wherein a key according to the UUID Standard is defined as the unique name of the synchronous connection,

(vi) creating, by the Server, a synchronous connection with the generated unique name,

(vii) sending, by the Server, the name of the generated synchronous connection to the Client via an asynchronous connection, and

(viii) linking up the Client to the Server via the created synchronous connection with the generated unique name.

2. The method according to claim 1 , wherein the making a request from the Client for a synchronous connection to the Server includes making a request for link-up to the Server via the Client synchronous connection and making a request for a unique name of the synchronous connection via the client asynchronous link-up.

3. The method according to claim 1 , wherein the verifying the unique name of the synchronous connection among the created connections to the Server includes making a request for a unique name of the synchronous connection from the Client to the Server via the asynchronous link-up.

4. A computer system for providing a secure link-up to a non-secure synchronous connection, the system comprising, coupled with each other via a communication interface, a processor device, a means for data operating storage and processing, and a means for data persistence that comprises a set of instructions for Client processes and Server processes, which are configured to be executed by the processor device by the means for data operating storage and processing, wherein the Client and Server are simultaneously connected by a synchronous and an asynchronous connection,

wherein the set of machine instructions for the Client processes is configured to:

send a request for a synchronous connection to the Server,

verify a unique name of the synchronous connection among the created connections to the Server, and

send a request for a unique name of the synchronous connection via an asynchronous connection between the Client and Server, if there is no unique name of the synchronous connection, and

wherein the set of machine instructions for the Server processes is configured to:

verify whether the Client is whitelisted in a list of Clients that have permission to connect to the Server, according to a Client identifier, wherein a process identifier (process id) and/or a software application identifier (bundle id) and/or a digital signature is defined as the Client identifier,

generate a unique name of the synchronous connection for the Clients that have permission to connect to the Server, wherein a key according to the UUID Standard is defined as the unique name of the synchronous connection,

create a synchronous connection with the generated unique name, send the name of the generated synchronous connection to the Client via the asynchronous connection, and

link up the Client to the Server via the created synchronous connection with the generated unique name.

5. The system according to claim 4 , wherein the set of machine instructions for the Client processes is further configured to send a request for link-up to the Server via the client synchronous connection and to send a request for a unique name of the synchronous connection via the client asynchronous link-up.

6. The system according to claim 4 , wherein the set of machine instructions for the Client processes is further configured to send a request for a unique name of the synchronous connection from the Client to the Server via the asynchronous link-up.

7. The system according to claim 4 , wherein the Client comprises a software visual shell that is configured to initiate processes of the synchronous and/or asynchronous connection to the Server.

8. The system according to claim 4 , wherein the Server comprises a software service module that is configured to execute processes initiated via the software visual shell of the Client.

9. The system according to claim 7 , wherein the Server comprises a software service module that is configured to execute processes initiated via the software visual shell of the Client.

10. A non-transitory computer readable medium comprising machine readable instructions executable by computing hardware, the non-transitory computer readable medium comprising instructions for:

sending a request for a synchronous connection to the Server,

verifying a unique name of the synchronous connection among the created connections to the Server,

sending a request for a unique name of the synchronous connection via an asynchronous connection between the Client and Server, if there is no unique name of the synchronous connection among the created connections to the Server,

wherein a set of machine instructions for the Server processes is configured to:

verify whether the Client is whitelisted in a list of Clients that have permission to connect to the Server, according to a Client identifier, wherein a process identifier (process id) and/or a software application identifier (bundle id) and/or a digital signature is defined as the Client identifier,

generate a unique name of the synchronous connection for the Clients that have permission to connect to the Server, wherein a key according to the UUID Standard is defined as the unique name of the synchronous connection,

create a synchronous connection with the generated unique name,

send the name of the synchronous connection to the Client via an asynchronous connection, and

link up the Client to the Server via the created synchronous connection with the generated unique name.

11. The non-transitory computer readable medium according to claim 10 , comprising a set of machine instructions for the Client processes that is further configured to send a request for link-up to the Server via the Client synchronous connection and to send a request for a unique name of the synchronous connection via the client asynchronous link-up.

12. The non-transitory computer readable medium according to claim 10 , comprising a set of machine instructions for the Client processes that is further configured to send a request for a unique name of the synchronous connection from the Client to the Server via an asynchronous link-up.

13. The non-transitory computer readable medium according to claim 10 , comprising a set of machine instructions, wherein the Client comprises a software visual shell that is configured to initiate processes of the synchronous and/or asynchronous connection to the server.

14. The non-transitory computer readable medium according to claim 13 , comprising a set of machine instructions, wherein the Server comprises a software service module that is configured to execute processes initiated by the software visual shell of the Client.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 19, 2025
From: CLARIO DMCC
To: ROCKET LIGHT LIMITED
Reel/Frame 072307/0564 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 10, 2023
From: CLARIO TECH LIMITED
To: CLARIO DMCC
Reel/Frame 064554/0303 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 18, 2021
From: KROMTECH ALLIANCE CORP.
To: CLARIO TECH LIMITED
Reel/Frame 056585/0798 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 3, 2020
From: KROMTECH ALLIANCE CORP.
To: CLARIO TECH LIMITED
Reel/Frame 051998/0420 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2019
From: SHARIPOV, ANDRII; SKOLIAR, IURII; SHELEST, VOLODYMYR
To: KROMTECH ALLIANCE CORP.
Reel/Frame 050568/0458 →
Priority Claims (1)
UA a 2019 04230 · Apr 19, 2019 · national