Platform for computing at the mobile edge

1. A platform for computing within a wireless network, comprising:

a Mobile Edge Compute (“MEC”) Appliance comprising a hardware device capable of providing data services and security mechanisms for running programs associated with third party providers on a privately managed network, the MEC Appliance being placed at or near an edge of the privately managed network;

a MEC Controller capable for command and control of the MEC Appliance, the MEC Controller residing within a core network of the mobile network operator (“MNO”) and de-centralizing the MNO's core network; and

a Security Module comprising a plurality of components establishing a plurality of layers, each component structured to address various attack vectors and potential exploits at each layer, the Security Module being integral to a function of the MEC Controller and for which extends throughout the MEC Appliance, the plurality of layers comprising:

a first security layer encrypting keys stored on the MEC Appliance;

a security second layer verifying the integrity of an operating environment within the privately managed network; and

a security third layer for controlling interaction with network elements;

wherein the platform provides computational resources for hosting at least one third party application within an environment that is at least one of at a network perimeter of the privately managed network and near the network perimeter of the privately managed network, and

wherein the Security Module validates any action by any platform component within the environment that is at least one of at the network perimeter of the privately managed network and near the network perimeter of the privately managed network before being granted access to the privately managed network.

2. The platform recited in claim 1 , wherein the MEC Appliance is capable to serve as a data plane.

3. The platform recited in claim 1 , wherein MEC Controller is capable to serve as a control plane.

4. The platform recited in claim 1 , wherein the environment that is at least one of at the network perimeter of the privately managed network and near the network perimeter of the privately managed network is a distributed topology.

5. The platform recited in claim 1 , wherein the MEC Appliance is placed in-line between a small cell radio and a MNO.

6. The platform recited in claim 5 , wherein the MEC Appliance installs itself in a data path defined by an Internet Protocol security (“IPSec”) tunnel to the MNO's security gateway, acting as an IPSec server to the small cell radio and an IPSec client device to the MNO's security gateway servers.

7. The platform recited in claim 1 , wherein the MEC Controller further comprises a Core Services Platform designed as a micro-services architecture, providing central control and aggregation of all capabilities provided by the platform, capable of isolating a scope of specific functions to a set of dedicated instances for independent scaling, fault, and attack vector isolation.

8. The platform recited in claim 7 , wherein the Core Services Platform further comprises: an Appliance Module for communication with deployed MEC appliances; a Security Module for white-listed access and control of the platform; an EPC Module for integration and communication with the MNO EPC for network provisioning and policy enforcement; a Telemetry Module for statistics and logging; and a Public Gateway Module for providing a REST API endpoint to the platform for outside services and users.

9. The platform recited in claim 8 , wherein the Telemetry Module is capable of capturing all events and metrics from both the MEC Appliance and the MEC Controller.

10. The platform recited in claim 8 , wherein all event data processing is conducted via the Telemetry Module.

11. The platform recited in claim 1 , where the hardware device comprises an x86 hardware device.

12. The platform recited in claim 1 , further comprising a Discovery Service module responsible for provisioning of the MEC Appliance within the environment that is at least one of at the network perimeter of the privately managed network and near the network perimeter of the privately managed network.

13. A platform for computing within a network system, comprising:

a wireless network capable of connecting with a privately managed network;

a plurality of client devices, each associated with the privately managed network;

at least one server, being part of the wireless network, acting as a gateway between the wireless network and the privately managed network, enabling communication between each client device and the server;

an access node facilitating wireless connectivity between the plurality of client devices and the wireless network;

a Mobile Edge Compute (“MEC”) Appliance comprising a hardware device capable of providing data services and security mechanisms for running programs associated with third party providers on the privately managed network, the MEC Appliance being placed at or near an edge of the privately managed network;

a MEC Controller capable for command and control of the MEC Appliance, the MEC Controller residing within a core network of the MNO and de-centralizing the MNO's core network; and

a Security Module comprising a plurality of components establishing a plurality of layers, the Security Module validating any action by any platform component establishing communication with the MNO network;

wherein the plurality of layers comprises:

a first security layer encrypting keys stored on the MEC Appliance;

a security second layer verifying the integrity of an operating environment within the privately managed network; and

a security third layer for controlling interaction with network elements; and

wherein the platform provides computational resources for hosting at least one third party application used on at least one client device.

14. The platform recited in claim 13 , wherein the MEC Controller is further configured to de-centralize macro-cell network topologies associated with the MNO network.

15. The platform recited in claim 13 , wherein the MEC Appliance is capable to serve as a data plane.

16. The platform recited in claim 13 , wherein MEC Controller is capable to serve as a control plane.

17. The platform recited in claim 13 , wherein the MEC Appliance installs itself in a data path defined by an Internet Protocol security (“IPSec”) tunnel to the MNO's security gateway, acting as an IPSec server to the access node and the IPSec client device to the MNO's security gateway servers.

18. The platform recited in claim 17 , wherein the MEC Appliance is placed in-line between the access node and a MNO.

19. The platform recited in claim 17 , wherein the access node is a small cell radio.

20. The platform recited in claim 13 , wherein the MEC Controller further comprises a Core Services Platform designed as a micro-services architecture, the Core Services Platform providing central control and aggregation of all capabilities provided by the platform, and capable of isolating a scope of specific functions to a set of dedicated instances for independent scaling.

21. The platform recited in claim 20 , wherein the Core Services Platform further comprises a Telemetry Module capable of statistics and logging.

22. The platform recited in claim 13 , further comprising a Discovery Service module responsible for provisioning of the MEC Appliance.

23. The platform recited in claim 13 , where the hardware device comprises an x86 hardware device.

24. A platform for computing within a wireless network, comprising:

a Mobile Edge Compute (“MEC”) Appliance comprising an x86 hardware device capable of providing data services and security mechanisms for running programs associated with third party providers on a privately managed network, the MEC Appliance being placed in-line between a small cell radio and an MNO;

a MEC Controller capable for command and control of the MEC Appliance, the MEC Controller residing within the MNO's core network and de-centralizing the MNO's core network, the MEC Controller comprising:

a Core Services Platform designed as a micro-services architecture, providing central control and aggregation of all capabilities provided by the platform, capable of isolating a scope of specific functions to a set of dedicated instances for independent scaling, the Core Services Platform comprising:

a Security Module providing Authentication, Authorization, and Accounting to cryptographically authenticate and sign all actions;

an Appliance Module configured for a one-to-many management of a plurality of MEC Appliances;

a Telemetry Module configured capable of statistics and logging;

an Evolved Packet Core (“EPC”) Module configured for communication with the MNO's EPC components; and

a Public Gateway Module configured to provide the only public interface for the third party providers to access the Core Services Platform;

an Enterprise Services Gateway and a Carrier Services Gateway capable of providing web user interfaces for a client device user and a carrier operator user, respectively;

an Appliance Services Agent to serve as an interface between all components and services running in the MEC Appliance; and

a Discovery Service module as a component of the platform responsible for provisioning of the MEC Appliance; and

a Security Module comprising a plurality of components establishing a plurality of layers, each component structured to address various attack vectors and potential exploits at each layer, the Security Module being integral to a function of the MEC Controller and for which extends throughout the MEC Appliance, the plurality of layers comprising:

a first security layer encrypting keys stored on the MEC Appliance;

a security second layer verifying the integrity of an operating environment within the privately managed network; and

a security third layer for controlling interaction with network elements;

wherein the platform provides computational resources for hosting at least one third party application within an environment that is at least one of at a network perimeter of the privately managed network and near the network perimeter of the privately managed network; and

wherein the Security Module validates any action by any platform component within the environment that is at least one of at the network perimeter of the privately managed network and near the network perimeter of the privately managed network before being granted access to the privately managed network.