Dynamic information technology multi-directional multi-protocol resource convergence system

• US 9,531,801 B1
• Filed: 08/06/2012
• Issued: 12/27/2016
• Est. Priority Date: 08/30/2011
• Status: Active Grant

• Current Assignee: MacStadium, Inc.
• Original Assignee: Virtual Command, LLC
• Inventors: Cantrell, Mark, Chapman, Chris, Russo, Robert
• Primary Examiner(s): KIM, EDWARD J
• Application Number:
  US13/567,800
• Time in Patent Office: 1,604 Days
• Field of Search: 709/217, 709/218, 709/219, 709/223, 709/225, 709/227, 709/228, 709/229, 709/249
• US Class Current: 1/1
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 92/18 between terminal devices

Abstract

A software platform preferably delivered via the internet provides access to and from web-enabled devices with the purpose of delivering and providing software applications, hardware resources, reporting, monitoring, tracking, virtual and cloud computing augmentation, all through a cross-end point unified user-based interface. Resources can be connected dynamically to other resources through the platform and, depending upon the decision of the user and the security settings, resources of the end-point device can be provided to other members in the same network.

Claims

1. A system comprising:

a processing device; and

a memory device, the memory device comprising

a service platform configured to

provide an aggregation point for computing devices to form a hardware-agnostic peer group of computing devices,

receive a request for access to a remote resource from at least one of the computing devices,

determine whether each computing device that sends the request for access to a remote resource comprises an end point agent,

transfer the end point agent to each computing device determined to not have the end point agent, and

provide a centralized access via an agent command channel connection to each computing device linked to the service platform by an application program interface (API),

a resource agent configured to establish a multi-directional link from each computing device to another computing device within the hardware-agnostic peer group of computing devices, and

a control manager configured to utilize the API to provide the hardware-agnostic peer group of computing devices access to web application connectivity and hosting, access to databases and database functions, customization of the API, administrative controls, and system security through one consistent interface for each computing device,

wherein the service platform, the control manager, and the resource agent together provide at least one remote resource through the API to each computing device.

2. The system of claim 1 wherein the API provides a view of all of the at least one remote resource to each computing device.

3. The system of claim 1 wherein the service platform is deployed as a software-based switch.

4. The system of claim 1 wherein the computing devices are end-point computing devices.

5. The system of claim 1 wherein the resource agent creates a dynamic, peer overlay network between each computing device.

6. The system of claim 1 wherein the resource agent provides access to services from a local device, network resources, and cloud-based resources.

14. The system of claim 1, wherein resource information is transmitted by a rendezvous agent in an encrypted message body that defines a status, and an inside and an outside address alias for a rendezvous node.

15. The system of claim 14, wherein the outside address alias is used by the rendezvous agent to provide a connection point to any node.

7. A system comprising:

a plurality of end-point computing devices, each end-point computing device including a resource and configured to send a request for access to a remote resource, wherein at least one of the plurality of end-point computing devices is a different operating system than at least another one of the plurality of end-point computing devices;

a switch appliance configured to

receive the request for access to the remote resource from at least one of the plurality of end-point computing devices,

determine whether each computing device that sends the request for access to the remote resource comprises a resource agent,

transfer the resource agent to each computing device determined to not have the resource agent,

provide a hardware-agnostic centralized access to the resources of the plurality of end-point computing devices linked thereto via an agent command channel connection, and

provide an application program interface (API) to unify the resources, the API configured to allow publishing, subscribing, and managing resources across a plurality of platforms and the plurality of end-point computing devices through one consistent interface for each computing device; and

a rendezvous node configured to publish and to relay peer group information across a network, and further configured to register a resource agent connection for each resource agent and publish a connection point and resource information for all permitted resources,

wherein each resource agent allows access to the resources through the API.

8. The system of claim 7, wherein access to the resources of the plurality of end-point computing devices is directed by a rendezvous agent.

9. The system of claim 7, wherein each resource agent includes an interface manager, a peer core, a transport manager, a protocol manager, a configuration manager and a data/services manager.

10. The system of claim 7, wherein the switch appliance includes a resource agent and a control manager.

11. The system of claim 10, wherein the switch appliance further includes an identity manager, file and printer manager, and capacity manager.

12. The system of claim 7, wherein each resource agent includes a java core framework, an agent configuration manager, a command channel and resource discover module, a security module, a protocol control module, a file management module, and a print control module.

17. The system of claim 7, wherein the resource information is transmitted in an encrypted message body that defines a status, and an inside and an outside address alias for the rendezvous node.

13. A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by a computer system, cause the computer system to:

provide an aggregation point for computing devices to form a hardware-agnostic peer group,

receive a request for access to a remote resource from at least one of the computing devices,

determine whether each computing device that sends the request for access to the remote resource comprises a resource agent,

transfer the resource agent to each computing device determined to not have the resource agent,

provide a centralized access via an agent command channel connection to each computing device linked to a service platform by an application program interface (API), wherein the resource agent is configured to establish a multi-directional link from each computing device to at least one other computing device within the hardware-agnostic peer group of the computing device;

register a resource agent connection;

publish a connection point and resource information to all permitted resources; and

provide at least one remote resource through the API to each computing device, wherein the API provides one consistent interface for each computing device.

16. The non-transitory computer-readable medium of claim 13, wherein the API provides a view of all of the at least one remote resource to each computing device.