Real-time distributed tree

• US 9,584,440 B1
• Filed: 10/12/2015
• Issued: 02/28/2017
• Est. Priority Date: 10/12/2015
• Status: Active Grant

• Current Assignee: Xirsys, LLC
• Original Assignee: Xirsys, LLC
• Inventors: Blakely, Richard, Turner, Ritchie
• Primary Examiner(s): Chang, Tom Y
• Application Number:
  US14/880,990
• Time in Patent Office: 505 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5051 Service on demand, e.g. definition and deployment of services in real time
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Some embodiments provide a real-time distributed tree (RDT) comprising scalability, protocol, and data layers for dynamically and in real-time defining and implementing customer applications over cloud operator resources. The RDT is a tree structure with customer branches comprising nodes hierarchically organizing domains, domain applications, and application rooms. Service layer service nodes can be linked to any customer branch node. Linking service nodes to the customer node reserves services represented by the service nodes for allocation to or scaling of any customer application or room under that customer branch. Linking service nodes to an application node or room node allocates the corresponding services to the application or room. The RDT moves linkages to maximize service usage and minimize wasted allocation. Protocol layer nodes modify signaling or messaging of the services implementing a customer application. Data layer nodes provide customizable four-dimensional storage of activity occurring anywhere in the customer branch.

Claims

1. A method comprising:

reconfigurably allocating a plurality of services across a plurality of cloud computing resources in dynamically implementing a plurality of applications, each service of the plurality of services executing different functionality using one or more cloud computing resources of the plurality of cloud computing resources;

reconfigurably linking a plurality of protocols to the plurality of services, each particular protocol of the plurality of protocols modifying signaling or messaging of at least one service linking to the particular protocol, the plurality of protocols comprising one or more of a first protocol encrypting messaging produced from a service of the plurality of services linked to the first protocol, a second protocol converting messaging in a first format produced from a service of the plurality of services linked to the second protocol to a different second format, and a third protocol communicably coupling a service of the plurality of services linked to the third protocol to a plurality of different user devices;

receiving from a particular customer over an online interface, input comprising (i) a first set of the plurality of services and a first set of the plurality of protocols used in implementing a first application and (ii) an expected usage of the first application by users;

determining a quantity of each of the first set services used in implementing the first application based on the expected usage;

generating in response to said input from the online interface by operation of a computer processor, a tree structure defining the first application implementation, the tree structure comprising a first layer with a branch having a first node identifying a domain of the particular customer and a second node identifying the first application, a second layer with a set of service nodes linked to the second node in the first layer, and a third layer with a set of protocol nodes linked to the set of service nodes in the second layer, wherein the set of services nodes represent the first set of services allocated to the first application and the set of protocol nodes represent the first set of protocols allocated to the first application based on said input and said quantity; and

implementing the first application according to said tree structure, wherein said implementing comprises (i) provisioning a set of the plurality of cloud computing resources for said first application, (ii) executing said quantity of the first set of services on behalf of the particular customer across the set of cloud computing resources, and (iii) adapting signaling or messaging of the first application with the first set of the plurality of protocols, wherein adapting said signaling or messaging comprises one or more of (a) encrypting messaging of at least one service of the first set of services in response to the third layer of the tree structure linking a protocol node of the first protocol to a service node of the at least one service in the second layer of the tree structure, (b) converting messaging format of at least one service of the first set of services from an original first protocol format to a different second protocol format in response to the third layer of the tree structure linking a protocol node of the second protocol to a service node of the at least one service in the second layer of the tree structure, and (c) establishing connections between at least one service of the first set of services and a set of devices in response to the third layer of the tree structure linking a protocol node of the third protocol to a service node of the at least one service in the third layer of the tree structure.

2. The method of claim 1 further comprising compiling the plurality of cloud computing resources from a plurality of cloud operators.

3. The method of claim 2, wherein executing said quantity of the first set of services comprises for each instance of a service from the first set of services up to said quantity, deploying said instance on a different subset of the set of cloud computing resources.

4. The method of claim 3, wherein compiling the plurality of cloud computing resources comprises qualifying each resource of the plurality of cloud computing resources based on geographic location where the resource operates, and wherein executing the first set of services comprises executing each service instance of the first set of services using the set of the plurality of cloud computing resources that is geographically proximate to a set of users using said service instance.

5. The method of claim 1 further comprising monitoring usage of the first application.

6. The method of claim 5 further comprising receiving from the particular customer, second input comprising a second set of the plurality of services and a second set of the plurality of protocols for implementing a second application.

7. The method of claim 6 further comprising deallocating one instance of a particular service from the first set of services of the first application in response to usage of the first application being less than a minimum usage threshold while the first application continues execution with a remainder of services from the first set of services.

8. The method of claim 7 further comprising reallocating said instance of the particular service from the first application to the second application, wherein said reallocating comprises executing the particular service as part of the second application and not the first application.

9. The method of claim 5 further comprising scaling the first application without involvement of the particular customer in response to usage of the first application exceeding a maximum usage threshold.

10. The method of claim 9, wherein scaling the first application comprises provisioning additional instances of the first set of services and executing said additional instances in connection with said quantity of the first set of services.

11. The method of claim 1 further comprising moving linkage of a particular service node from the second layer to the first layer, wherein moving said linkage deallocates a particular service associated with the particular service node from the first application such that the particular service does not execute as part of the first application.

12. The method of claim 1 further comprising moving linkage of a particular service node from the second node in the first layer to a third node in the first layer, wherein the third node identifies a second application of the particular customer, and wherein moving said linkage comprises reallocating a particular service associated with the particular service node from the first application to the second application.

13. The method of claim 1 further comprising linking a particular service from the first set of services to a particular protocol of the first set of protocols, wherein said linking comprises adapting signaling or messaging of the particular service to the particular protocol.

14. The method of claim 1 further comprising linking a storage node to a particular service of the first set of services, wherein said linking comprises tracking activity from the particular service to the storage node.

15. The method of claim 1, wherein said implementing further comprises tracking activity of the first set of services across four dimensions.

16. The method of claim 15, wherein tracking activity across four dimensions comprises tracking activity of the first set of services across path, key, layer, and time dimensions.

17. The method of claim 1, wherein the plurality of services comprises one or more of a first service instantiating a traversal using relays around network address translator (TURN) server on a set of the plurality of cloud computing resources allocated to the first service, a second service instantiating a session traversal of User Datagram Protocol (STUN) server on a set of the plurality of cloud computing resources allocated to the second service, and a third service instantiating a signaling server on a set of the plurality of cloud computing resources allocated to the third service.

18. The method of claim 17, wherein said executing comprises providing at least one of a chat, streaming, meeting, or collaboration application as the first application by instantiating one or more of said TURN server, STUN server, or the signaling server across the set of cloud computing resources in response to said quantity of a particular service of the first set of services.

19. The method of claim 1, wherein reconfigurably allocating the plurality of services comprises executing the first application with a particular service from the first set of services during a first interval, reallocating the particular service from the first application to a second application, and executing the second application with the particular service during a different non-overlapping second interval.