Application programming interface and hypergraph transfer protocol supporting a global hypergraph approach to reducing complexity for accelerated multi-disciplinary scientific discovery

• US 10,740,348 B2
• Filed: 06/05/2017
• Issued: 08/11/2020
• Est. Priority Date: 06/06/2016
• Status: Active Grant

• Current Assignee: Georgetown University
• Original Assignee: Georgetown University
• Inventors: Smart, J. Cory
• Primary Examiner(s): Alam, Shahid A
• Application Number:
  US15/614,131
• Publication Number:
  US 20170351742A1
• Time in Patent Office: 1,163 Days
• Field of Search: 707743
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/26 Visual data mining; Browsing structured data
• CPC Class Codes: G06F 16/367 Ontology
• CPC Class Codes: G06N 5/02 Knowledge representation; Symbolic representation
• CPC Class Codes: G06N 5/022 Knowledge engineering; Knowledge acquisition
• CPC Class Codes: H04L 12/00 Data switching networks interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge

Abstract

A system and method for connecting one or more client applications with one or more knowledge representation servers and communicating there between includes an application programming interface (API) and a hypergraph transfer protocol (HGTP), for facilitating communication between the one or more client applications and one or more knowledge representation servers responsive to a client application request. The client application request includes an API call for a specific entity that is received by a first knowledge representation server. If the first knowledge representation server does not manage the specific entity, the first knowledge representation server forwards the specific entity call to a second knowledge representation server via the HGTP using a universal unique identifier (UUID) associated with the specific entity having encoded therein a network address for the second knowledge representation server.

Claims

1. A system for connecting one or more client applications running on one or more clients with one or more knowledge representation servers, the system comprising:

an application programming interface (API); and

a hypergraph transfer protocol (HGTP), for facilitating communication between the one or more client applications and one or more knowledge representation servers responsive to a client application request; and

further wherein the client application request includes an API call for a specific entity that is received by a first knowledge representation server that does not manage the specific entity, the first knowledge representation server forwarding the specific entity call to a second knowledge representation server via the HGTP;

wherein the specific entity includes a universal unique identifier (UUID) having encoded therein a network address for the second knowledge representation server that manages the specific entity, the UUID consists of 128-bit values with the upper 32 bits designating a globally unique public host identifier, the next 32 bits designating a locally unique local host identifier, and the lower 64 bits designating a locally unique entity identifier; and

further wherein, the first knowledge representation server uses the UUID to forward the specific entity call to the second knowledge representation server via the HGTP; and

the second knowledge representation server forwards a message containing the specific entity responsive to the received request to the first knowledge representation server via the HGTP.

2. The system of claim 1, wherein the HGTP is a text-based socket stream protocol communicated between the one or more client applications and one or more knowledge representation servers via Transmission Control Protocol (TCP) or Transport Layer Security (TLS) protocol.

3. The system of claim 1, wherein the specific entity is an item of a knowledge space that is defined by an ontology.

4. The system of claim 3, wherein the HGTP is ontology-agnostic.

5. The system of claim 3, wherein the specific entity is selected from a group consisting of:

a person, a place and a thing.

6. The system of claim 5, wherein the specific entity includes one or more attributes.

7. The system of claim 6, wherein the one or more attributes are dynamic.

8. A process for facilitating a query within a dynamic knowledge space comprised of multiple distributed knowledge representation servers and at least one client, the system comprising:

issuing by the client a client application request related to a specific entity associated with the dynamic knowledge space from a first client application associated with a first distributed knowledge representation server via an application programming interface (API);

determining at the first distributed knowledge representation server that the specific entity is managed at a second distributed knowledge representation server, including reviewing a universal unique identifier (UUID) assigned to the specific entity to determine a network address encoded therein for the second distributed knowledge representation server wherein the UUID consists of 128-bit values with the upper 32 bits designating a globally unique public host identifier, the next 32 bits designating a locally unique local host identifier, and the lower 64 bits designating a locally unique entity identifier;

forwarding the client application request related to the specific entity to the second distributed knowledge representation server using a hypergraph transfer protocol (HGTP); and

receiving from the distributed knowledge representation server second distributed knowledge representation server using a hypergraph transfer protocol (HGTP) at the first distributed knowledge representation server, a message responsive to the client application request.

9. The process according to claim 8, wherein the API client application request establishes an open socket to the first distributed knowledge representation server for a predetermined period of time.

10. The process according to claim 9, wherein during the predetermined period of time, a second API client application request is made to the first distributed knowledge representation server through the open socket.

11. The process according to claim 9, wherein if no additional API client application request during is made to the first distributed knowledge representation server during the predetermined period of time, the client sends a BYE message to notify the server of a socket shutdown.

12. The process according to claim 9, wherein during the predetermined period of time is approximately 1 minute.