Patent Grant
12095853
The present invention relates to multi-access edge computing, and more specifically to providing cellular network coverage and content delivery via an edge computing platform.
It is generally known in the prior art to provide edge computing solutions wherein an edge server is able to receive and fulfill requests from client devices. The prior art also describes edge servers operable to provide wireless network access.
Prior art patent documents include the following:
U.S. Pat. No. 10,778,794 for Modular telecommunication edge cloud system by inventors Wei, et al., filed Aug. 7, 2018 and issued Sep. 15, 2020, is directed to a telecommunications edge cloud (TEC) element deployed between a client and a packet network includes a TEC hardware layer including storage resources, networking resources, and computing resources, wherein the computing resources include a plurality of processors. A TEC operating system (TECOS) is coupled to the TEC hardware layer and configured to control and manage the storage resources, the networking resources, and the computing resources, wherein the TECOS is executed by one of the processors, a TEC application layer coupled to the TECOS, wherein the TEC application layer is configured to process a request from the client using the TECOS, wherein the computing resources are configured to provide a service to the client when the request is a service request, and wherein at least one of the networking resources and the storage resources is configured to provide data to the client when the request comprises a data request.
U.S. Pat. No. 10,341,868 for Platform for computing at the mobile edge by inventors Ross, et al., filed Feb. 24, 2017 and issued Jul. 2, 2019, is directed to a platform for providing computational resources at and/or near a mobile network perimeter. The platform may be used to provide computational resources adjacent a small cell radio via at least one Mobile Edge Compute (“MEC”) Appliance and at least one MEC Controller. The MEC Appliance can serve as the data plane to support data flow traffic. The MEC Controller can provide a micro-services architecture designed for resiliency, scalability, and extensibility. The platform can be used to de-centralize the mobile network operator's core network and/or associated macro-cell network topologies, generating a platform with enhanced flexibility, reliability, and performance. The platform can include a security architecture for effective privacy and access within a distributed topology of the network at and/or near the edge of the mobile network perimeter.
U.S. Pat. No. 10,938,916 for Methods circuits devices systems and functionally associated computer executable code for facilitating edge computing on a mobile data communication network by inventors Enat, et al., filed Jan. 9, 2019 and issued Mar. 2, 2021, is directed to methods, circuits, devices, systems and functionally associated computer executable code to Facilitate Edge Computing on a mobile communication network. The patent discloses a mobile data communication network comprising two or more Mobile Edge Computing MEC Zones, wherein a first MEC Zone is communicatively coupled to a first set of network access points which are adapted to communicated with User Equipment (UE) and includes at least one Edge Processing Host adapted to run a server-side application accessible to a client application running on an EU communicating with a network access point of the first set of network access points. The network may include an Edge Processing Connectivity Manager (“EPCM”) to provide application session continuity for the client application and the server-side application when the UE switches its network connection from an access point of said first MEC zone to an access point communicatively coupled to an access point coupled to a second MEC zone.
U.S. Patent Publication No. 20210044675 for Methods Circuits Devices Systems and Functionally Associated Computer Executable Code for Facilitating Edge Computing on a Mobile Data Communication Network by inventors Frydman, et al., filed Jul. 1, 2020 and published Feb. 11, 2021, is directed to methods, circuits, devices, systems and functionally associated computer executable code to Facilitate Edge Computing on a mobile communication network. The publication discloses a mobile data communication network comprising two or more Mobile Edge Computing MEC Zones, wherein a first MEC Zone is communicatively coupled to a first set of network access points which are adapted to communicated with User Equipment (UE) and includes at least one Edge Processing Host adapted to run a server-side application accessible to a client application running on an EU communicating with a network access point of the first set of network access points. The network may include an Edge Processing Connectivity Manager (“EPCM”) to provide application session continuity for the client application and the server-side application when the UE switches its network connection from an access point of said first MEC zone to an access point communicatively coupled to an access point coupled to a second MEC zone.
U.S. Patent Publication No. 20180041578 for Inter-Telecommunications Edge Cloud Protocols by inventors Lee, et al., filed Aug. 8, 2016 and published Feb. 8, 2018, is directed to a first telecommunications edge cloud (TEC) element deployed between a client and a packet network includes a TEC hardware layer including storage resources, networking resources, and computing resources, wherein the computing resources include a plurality of processors. The networking resources are configured to transmit a first general update message to a plurality of second TEC elements within a federation, transmit a first application-specific update message to the second TEC elements within the federation, and receive a plurality of second update messages from the second TEC elements that are associated with the federation. The federation includes the second TEC elements and the first TEC element and shares resources to provide data and services to a requesting client. The storage resources are coupled to the computing resources and the networking resources and configured to store a second generic resource container and second application-specific resource container for each of the second TEC elements.
U.S. Patent Publication No. 20200107403 for Methods circuits devices systems and functionally associated computer executable code for enabling applications to run at or near an edge of a mobile communication network by inventors Frydman, et al., filed Apr. 9, 2019 and published Apr. 2, 2020, is directed to methods, circuits, devices, systems and functionally associated computer executable code for enabling applications to run at or near the edge of wireless or mobile communication network. The publication discloses a UPF proxy at or near an edge of a network which communicates with network elements at or near a core of the network. The UPF proxy may enable applications, such as application server applications, to run on computing resources at edge of the network.
U.S. Patent Publication No. 20200159511 for Methods Circuits Devices Systems and Associated Computer Executable Code for Providing Application Data Services to a Mobile Communication Device by inventors Frydman, et al., filed Aug. 4, 2019 and published May 21, 2020, is directed to methods, circuits, devices, systems and associated computer executable code for providing application data services to a mobile communication device. A communication module, including communication circuits, receives application data services demand information relating to demand for a given application data service being experienced by one or more access nodes of the mobile communication network. A controller on the network adjusts at least one parameter of an application data service being provided by at least one network edge appliance of the mobile communication network accordingly.
U.S. Pat. No. 10,567,291 for Multi-access edge computing (MEC) service provision based on local cost measurements by inventors Sabella, et al., filed Oct. 2, 2018 and issued Feb. 18, 2020, is directed to systems, apparatuses, methods, and computer-readable media, for a multi-access edge computing (MEC) system. An apparatus for MEC may include a communication interface, a local cost measurements module, and a service allocation module. The communication interface may receive, from a UE, a request for a service to be provided to the UE. The local cost measurements module may collect a set of local cost measurements for the service. The service allocation module may determine to allocate the service to a MEC host based on an allocation policy related to a cost for the MEC host to provide the service or a cost for a service provider to provide the service in view of the one or more local cost measurements.
U.S. Pat. No. 10,122,547 for Enabling high-bandwidth, responsive mobile applications in LTE networks by inventors Mahindra, et al., filed Aug. 15, 2016 and issued Nov. 6, 2018, is directed to systems and methods for standards compatible Mobile Edge Computing (MEC), including splitting Serving gateways (SGWs) and Packet Data Network gateways (PDN-GWs) to provision sufficient resources to deploy data-plane entity instances locally at a Radio Access Network (RAN) edge with one or more cloudlets. One or more local controller nodes is deployed in one or more operator clouds, a dedicated bearer is leveraged to route traffic from the one or more cloudlets through the split SGWs and PDN-GWs, and the dedicated bearer is configured with a traffic flow template (TFT) including an Internet Protocol (IP) address of the one or more cloudlets. Efficient access to one or more MEC applications at the RAN edge is provided to one or more user devices using the dedicated bearer.
U.S. Pat. No. 10,334,446 for Private multefire network with SDR-based massive MIMO, multefire and network slicing by inventor Ashrafi, filed Aug. 2, 2018 and issued Jun. 25, 2019, is directed to a private wireless network for providing connections between a public wireless network and wireless devices includes a first interface to the public wireless network and at least one second interface to the wireless devices. A wireless communications network interconnecting the first interface and the second interface implementing a MulteFire wireless communications standard includes a first plurality of control layers. The wireless communications network further comprises a plurality of nodes within a mesh network. A plurality of transceivers is associated with each of the plurality of nodes within the mesh network. Each of the transceivers implement a software defined radio that may be configured within a plurality of transceiving configurations. At least one server implements at least a portion of the wireless communications network within the at least one server. The at least one server is configured to select a first slice portion of the first plurality of control layers of the wireless communications network and a first slice portion of at least a portion of the plurality transceivers in a first transceiving configuration to support operation of a first application or service and to select a second slice portion of the first plurality of control layers of the wireless communications network and a second slice portion of at least the portion of the plurality transceivers in a second transceiving configuration to support operation of a second application or service.
The present invention relates to systems and methods for providing multi-access edge computing in neutral host cellular networks.
It is an object of this invention to provide systems and methods for providing cellular services to devices in an integrated multi-access edge computing architecture.
In one embodiment, the present invention is a system for providing multi-access edge computing and content delivery including at least one cloud platform in network communication with at least one edge device and at least one server node, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the at least one cloud platform is in network communication with the at least one server node, wherein the at least one cloud platform is operable to fetch node data from the at least one server node, wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device, wherein the at least one cloud platform is operable to execute the HTTP request using the at least one server node, and wherein the at least one server node is operable to create a cellular network.
In another embodiment, the present invention is a system for providing multi-access edge computing and content delivery including at least one cloud platform in network communication with at least one edge device and a plurality of server nodes, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the at least one cloud platform is in network communication with the plurality of server nodes, wherein the plurality of server nodes is operable for network communication with each other, wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device, wherein the at least one cloud platform is operable to query the node database for a nearest node from the plurality of server nodes, wherein the at least one cloud platform is operable to execute the HTTP request using the nearest node, and wherein each of plurality of server nodes is operable to create a cellular network.
In yet another embodiment, the present invention is a method for providing multi-access edge computing and content delivery, including at least one cloud platform in network communication with at least one edge device and a plurality of server nodes resolving a hypertext transfer protocol (HTTP) request, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the plurality of server nodes is operable for network communication with each other, wherein the at least one cloud platform resolving the HTTP request comprises: the at least one cloud platform receiving an HTTP request from the at least one edge device, the at least one cloud platform querying the node database for a nearest node from the plurality of server nodes, and the at least one cloud platform executing the HTTP request on the nearest node, and the plurality of server nodes creating a cellular network.
These and other aspects of the present invention will become apparent to those skilled in the art after a reading of the following description of the preferred embodiment when considered with the drawings, as they support the claimed invention.
The present invention is generally directed to multi-access edge computing and content delivery.
In one embodiment, the present invention is a system for providing multi-access edge computing and content delivery including at least one cloud platform in network communication with at least one edge device and at least one server node, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the at least one cloud platform is in network communication with the at least one server node, wherein the at least one cloud platform is operable to fetch node data from the at least one server node, wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device, wherein the at least one cloud platform is operable to execute the HTTP request using the at least one server node, wherein the at least one server node is operable to create at least one cellular network, and wherein the at least one server node is operable to deliver cellular network services to the at least one edge device through the at least one cellular network.
In one embodiment, the at least one server node includes a node identifier (ID), an internet protocol (IP) address, a set of global positioning system (GPS) coordinates, a central processing unit (CPU) ID, a version number, an uptime value, a node heartbeat value, an edge executor, a plurality of v8 isolates, and/or time zone data. In another embodiment, the at least one server node is registered in a cloud platform global registry using an HTTP POST request to a global service address and wherein the cloud platform global registry is associated with the at least one cloud platform. In another embodiment, the at least one cloud platform is operable to fetch node data from the at least one server node using an object-oriented function and wherein the object-oriented function is a serverless function. In another embodiment, the at least one server node includes a radio network node. In one embodiment, the at least one server node is operable to perform at least one evolved packet core (EPC) function. In another embodiment, the at least one cellular network is a neutral host cellular network. In another embodiment, the at least one server node is operable to implement at least one access policy. In one embodiment, the at least one server node is operable to register the at least one edge device. In another embodiment, the at least one cloud platform is operable to implement quality of service (QoS) mechanisms on the at least one cellular network.
In another embodiment, the present invention is a system for providing multi-access edge computing and content delivery including at least one cloud platform in network communication with at least one edge device and a plurality of server nodes, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the at least one cloud platform is in network communication with the plurality of server nodes, wherein the plurality of server nodes is operable for network communication with each other, wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device, wherein the at least one cloud platform is operable to query the node database for a nearest node from the plurality of server nodes, wherein the at least one cloud platform is operable to execute the HTTP request using the nearest node, wherein each of the plurality of server nodes is operable to create at least one cellular network, and wherein each of the plurality of server nodes is operable to deliver cellular network services to the at least one edge device through the at least one cellular network.
In one embodiment, the at least one cloud platform selects the nearest node based on a geolocation of the at least one edge device and/or a latency value corresponding to the at least one edge device. In another embodiment, the system further includes at least one load balancer wherein the at least one load balancer is operable to distribute traffic across the plurality of server nodes. In one embodiment, the plurality of server nodes are microservers and wherein the plurality of server nodes is operable to form a global peer-to-peer (P2P) network. In one embodiment, each of the plurality of server nodes is operable to maintain a pool of persistent connections. In another embodiment, the plurality of server nodes is operable to store data in a content-addressable peer-to-peer storage network.
In yet another embodiment, the present invention is a method for providing multi-access edge computing and content delivery including at least one cloud platform in network communication with at least one edge device and a plurality of server nodes resolving a hypertext transfer protocol (HTTP) request wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component, wherein the plurality of server nodes is operable for network communication with each other, wherein the at least one cloud platform resolving the HTTP request includes the at least one cloud platform receiving an HTTP request from the at least one edge device, the at least one cloud platform querying the node database for a nearest node from the plurality of server nodes, and the at least one cloud platform executing the HTTP request on the nearest node, the plurality of server nodes creating at least one cellular network, and the plurality of server nodes delivering cellular network services to the at least one edge device through the at least one cellular network.
In one embodiment, the method further includes the at least one cloud platform selecting the nearest node based on a geolocation of the at least one edge device and/or a latency value corresponding to the at least one edge device. In another embodiment, the method further includes the plurality of server nodes forming a global peer-to-peer (P2P) network. In yet another embodiment, the at least one cellular network is a neutral host network.
Currently, mobile network operators rely on centralized switching centers to deliver wireless data services to devices. Each mobile network operator sets up its own base stations to create coverage areas. The physical infrastructure of each mobile network operator means that data packets requested by a device are sent from a base station to the centralized switch to fetch data and run apps, adding significant backhaul and latency of 40-150 ms on average. In roaming situations such as international travel, wherein a device uses (roams onto) a network that is different from its typical carrier, packets travel through the roaming network and then to the typical carrier's network, adding further delays. This process does not use edge processing or an edge-based infrastructure wherein the base stations are operable to access the internet and/or function as edge nodes. In order to provide true edge computing services to devices on their networks, mobile network operators would need to set up edge nodes throughout their coverage areas. The logistical requirements and financial costs of building this infrastructure for a single mobile network operator are prohibitive, resulting in the continued use of the current system of centralized servers. Furthermore, mobile network operators incur significant costs in transmitting data from the central switch to the mobile device and vice versa. The present invention improves on the existing framework by providing local internet breakout close to mobile subscribers and devices, dramatically reducing latency and cost. Further, it provides a method for multiple mobile operators to connect to the same localized compute infrastructure through neutral host functionality.
The present invention utilizes a distributed edge computing platform (sometimes referred to as “EDJX”) to deliver multi-access edge computing (MEC) and cellular network access on a mobile network and to any device. The edge computing platform reduces latency and increases network throughput to devices by locating edge server nodes in close proximity to the mobile devices. The edge computing platform of the present invention is operable to write, test, and deploy low-latency edge applications on the edge server nodes. The edge computing platform is further operable to execute serverless functions or otherwise retrieve data from the edge server nodes located in close proximity to the client. The edge computing platform is Application Programming Interface (API) compatible with cloud infrastructures including, but not limited to, GOOGLE CLOUD PLATFORM, AMAZON WEB SERVICES (AWS), and MICROSOFT AZURE.
The present invention includes a network of edge platform nodes operable to provide enhanced mobile coverage and accelerated content delivery for private and/or public mobile network operator (MNO) customers. The present invention is operable to create a private cellular network (e.g., a private wireless 4G/5G cellular network), wherein the private cellular network is also accessible by devices of mobile networks outside of the private cellular network while still maintaining necessary privacy and quality of service. The edge computing platform is operable to process data in real time and provide ultra-low latency cellular access, compute resources, and/or content delivery to mobile devices. In one embodiment, the edge computing platform is operable to use latency-based georouting to determine the nearest edge platform node in the network of edge platform nodes for ultra-low latency. In another embodiment, the edge computing platform is further operable to implement a content-addressed intelligent content delivery network (CDN) on the edge platform node to further reduce latency. The wireless network is operable to integrate with femtocells (e.g., 5G femtocells), WI-FI access points, and/or broadband customer premise equipment. The present invention is further operable to create a public cellular network (e.g., a public wireless 4G/5G cellular network) using the same node infrastructure and edge computing platform as the private cellular network.
An edge device is any device which provides an entry point into enterprise or service provider core networks. Examples include, but are not limited to, routers, routing switches, integrated access devices (IADs), multiplexers, metropolitan area network (MAN) access devices, wide area network (WAN) access devices, IoT devices, sensors, industrial machines, personal computing devices, laptop computing devices, tablet computing devices, mobile computing devices, cameras, smartphones, and any other device that produces and/or collects data. In one embodiment, an edge device is also operable for mobile broadband access and/or data roaming.
Referring now to the drawings in general, the illustrations are for the purpose of describing one or more preferred embodiments of the invention and are not intended to limit the invention thereto.
Edge Platform Nodes (EDJX-Node):
Nodes in the edge platform network are computing systems that run the edge platform software stack. In one embodiment, the edge platform software stack includes a client tier, a web tier, a business tier, and a database tier. In another embodiment, the edge platform software stack comprises an HTTP process, a query layer, an HTTP endpoint operable to interact with serverless functions, a runtime environment. In one embodiment, the runtime environment uses an event-driven architecture operable for asynchronous Input/Output (I/O). In one embodiment, the runtime environment is Node.js. In another embodiment, the runtime environment is operable to execute code outside of a browser. In one embodiment, the edge platform stack is a full stack. In one embodiment, at least part of the edge platform stack is coded in PUP. In another embodiment, at least part of the edge platform stack is coded in Javascript.
Nodes are identified by a globally unique identifier (GUID) that is generated the first time a node is powered on. In one embodiment, the system includes a plurality of node types including, but not limited to, a greedy node, a non-greedy node, a bootstrap node, and/or a super node. Edge platform nodes are responsible for serving HTTP requests from designated edge devices. Edge platform nodes themselves are HTTP clients of the edge platform. In one embodiment, each node in the edge platform network includes at least one v8 isolate. Isolates are lightweight contexts which group variables where code is allowed to mutate/change them. A single process is operable to run hundreds or thousands of isolates and seamlessly switch between them.
Mobile Edge Platform Node
In one embodiment, the edge platform node is a mobile edge Platform Node operable to provide MEC to a mobile device regardless of the MNO of the mobile device. Platform Nodes are customizable computer and storage hardware solutions that are operable to be sized for each use case with regard to number of subscribers and/or edge application compute requirements. The mobile edge platform node is operable to act as a radio access node, a compute node, and/or a content delivery node to at least one mobile device. In one embodiment, the mobile edge platform node is a radio mast with direct access to the internet to deliver wireless internet content. As a non-limiting example, the mobile edge platform node is as compact as a 40 cm by 20 cm structure. The mobile edge platform node is operable to extend the signal of an MNO to a user device (e.g., smartphone, tablet, laptop, edge device) and to run the software stack of the MNO and operate as a traditional base station subsystem in order to allow network access. In one embodiment, the mobile edge platform node is operable to generate a macrocell. Alternatively, the mobile edge platform node is operable to act as a picocell. In yet another embodiment, the mobile edge platform node is operable to integrate with picocells, femtocells, WI-FI access points, and/or other broadband customer premise equipment from a mobile network operator. In one embodiment, the mobile edge platform node integrates with existing MNO infrastructure at tower/mast locations. In one embodiment, the mobile edge platform node includes at least one network entry point (e.g., a fiber patch). The at least one network entry point feeds appropriate signaling to the edge computing platform. Data and applications then flow from the edge computing platform to mobile subscribers and/or edge devices. The mobile edge platform node is preferably a neutral host in that the mobile edge platform node is operable to provide cellular services to a device independent of the carrier typically used by the device. The mobile edge platform node is further operable to provide the same cellular services to devices across multiple different carriers. The cellular services include but are not limited to speech transcoding, radio channel allocation, paging, signal transmission, signal reception, content delivery, internet access, application execution, phone calls, broadcasting, and/or wireless broadband. The mobile edge platform node is connected directly to the internet and provides internet breakout to a device. As previously discussed, it is cost prohibitive for most carriers to build infrastructure for these services independently because the infrastructure only functions for the independent carrier. Advantageously, the mobile edge platform node is operable to function as a neutral host and provide services to devices from multiple carriers, thus providing a cost savings for MNOs.
In one embodiment, the mobile edge platform node includes a radio network node (“xNodeB”) wherein the radio network node is the hardware that is connected to a cellular network and that communicates with a user device and/or user equipment and wherein the radio network node facilitates wireless communication between the user device and/or user equipment and the cellular network. In one embodiment, the radio network node is operable to perform network control functions and/or create cellular network coverage. In one embodiment, the radio network node is an evolved NodeB (eNodeB) for 4G and/or LTE networks. The eNodeB is operable to use separate radio access technologies for uplink communications and downlink communications. As a non-limiting example, the eNodeB uses orthogonal frequency division multiple access (OFDMA) for the downlink communications and single carrier frequency division multiple access (SC-FDMA) for the uplink communications. Alternatively, the radio network node is a next-generation eNodeB (ng-eNB). In another embodiment, the radio network node is a next generation NodeB (gNB) for 5G networks. Alternatively, the radio network node is a NodeB for pre-4G networks. Radio network node infrastructure and/or base station infrastructure for networks beyond 5G are also compatible with the present invention. The radio network node is operable to manage radio resources in the surrounding cell in order to optimize communication between a wireless device and radio infrastructure. The radio network node functions for resource management include but are not limited to radio bearer control, radio admission control, connection mobility control, radio access functions, and/or dynamic allocation of resources in uplink and downlink communications. In another embodiment, the mobile edge platform node is operable to perform the radio network node functions as a replacement for a NodeB. Advantageously, the radio network node includes its own radio network control functionality and does not need a separate radio network controller (RNC). In one embodiment, the radio network node interfaces with the evolved packet core. In one embodiment, the radio network node implementation further reduces latency by 3rd generation partnership project (3GPP) protocol-defined stack cutting, which allows more direct transmission of data packets. The mobile edge platform node implements and adheres to mechanisms and protections provided by 3GPP standards including but not limited to the technical specifications described in “3GPP TS 33.501 V15.3.0 (2018 December) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspect; Security architecture and procedures for 5G system (Release 15),” which is incorporated herein by reference in its entirety.
Node Registry and Router (EDJX-Router):
The edge platform nodes periodically contact a centralized registry component (sometimes referred to as “EDJX-router”). This edge platform router is a distributed application that provides an interface for registering information about the edge platform nodes.
In one embodiment, the interface used is a Representational State Transfer (REST) interface. Separating the user interface concerns from the data storage concerns improves the flexibility of the interface across platforms and improves scalability by simplifying the server components. By using a REST interface, different clients hit the same REST endpoints, perform the same actions, and receive the same responses. Alternatively, the interface used for registering information about the edge platform nodes is another architectural style for distributed hypermedia systems, including but not limited to a GRAPHQL interface, a Falcor interface, or a Simple Object Access Protocol (SOAP) interface.
Node registrations, heartbeats, and other activities are conducted by a daemon on each edge platform node. The node process periodically collects system information and posts it to the edge platform API to be included among the nodes collection maintained by an edge platform router. The collected system information includes, but is not limited to, static information such as hardware data, baseboard data, bios data, OS, version data, Central Processing Unit (CPU) data, network interface data, memory, and/or disk layout, as well as dynamic data such as user data, CPU-speed, load data, processes, services, temperature, file system data, network data, and/or disk statistics.
Nodes register themselves in the edge platform's global registry by issuing an HTTP POST request to a global service address. The hostname resolves to a set of load balanced instances of the edge platform's API component. The edge platform's API component authenticates the API and proxies the request to the edge platform router service, which persists the data.
The HTTP POST request contains node information including, but not limited to, a GUID, a latitude, a longitude, a zip code, a street address, CPU information, a version number, an uptime, a time zone, and/or an Internet Protocol (IP) address. In one embodiment, the IP address is an IPv6 address. In another embodiment, the IP address is an IP version beyond IPv6.
The act of first-time node registration and subsequent node updates are not differentiated. Rather, the posting of a node to the nodes collection is a destructive update, and the update time is treated as a node heartbeat. A node heartbeat is a signal that is generated at regular intervals to indicate that the node is working correctly. If a node heartbeat is not sent, the node is considered to be unreachable. Regarding node heartbeats, there are two main values: a heartbeat interval and a heartbeat timeout. The heartbeat interval refers to an interval where a request is sent to a node at a set time interval, where the node responds to the request directly. If there is no response from the node, the request determines that the node is inactive. Heartbeat timeout refers to the time interval since the last heartbeat was received by the node. This heartbeat timeout value is greater than the heartbeat interval value. If a node has not received a response from the request in the time specified by the heartbeat timeout value, the node assumes the request has ended.
The present invention further includes load balancers. Load balancers are devices that act as reverse proxies and distribute network or application traffic across a number of servers. Load balancers are used to increase capacity (concurrent users) and reliability of applications. They improve overall performance of applications by decreasing the burden on servers associated with managing and maintaining application and network sessions, as well as performing application-specific tasks.
Node Database and Geolocation:
The edge platform router persists the node data to a table within a cloud platform database called an edge platform node database. The edge platform node database is operable to be queried and return a list and/or set of nodes. The edge platform node database is further operable to return an aggregated metric relating to node performance. In one embodiment, the edge platform node database is an object-relational database system. An object-relational database system is a database system that is similar to a relational database, except that it has an object-oriented database model. This system supports objects, classes and inheritance in database schemas and query language. In one embodiment, the edge platform node database is a PostgreSQL database. In one embodiment, the edge platform node database instance is extended by the PostGIS extension for geographic objects. PostGIS is a database extension for an object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.
According to one embodiment of the present invention, geolocation of an edge device is determined using a Global Positioning System (GPS). In another embodiment, the geolocation of an edge device is determined based on a Cell ID, where the edge device is a smart phone, cellular telephone, or any other device capable of communication with a cell tower. A Cell ID determines which sector of which base station a given edge device is using and, using a database of base-station identification numbers and locations, an edge device's location is associated with that of the identified cell tower.
In another embodiment, the geolocation of an edge device is determined based on WI-FI. Geolocation based on WI-FI makes use of received signal strength indication (RSSI), where signals detected by an edge device from nearby access points are referenced to a database of WI-FI networks. The database is operable to store location information for each uniquely identified access point. Using signal strength to determine distance from known access points, RSSI determines where an edge device is located in relation to the known access points. In one embodiment, the relative location is converted into an absolute location. In yet another embodiment, another form of WI-FI geolocation is used, e.g., wireless fingerprinting. Wireless fingerprinting uses profiles of WI-FI signals from multiple access points and/or devices to characterize an area. Each WI-FI access point is recorded along with a location and base station ID (BSSID) to create a fingerprint. The wireless fingerprint is then stored in a database. The database is used to determine the indoor location of a device based on the WI-FI environment relative to the device.
In another embodiment, the geolocation of an edge device is determined based on at least one sensor. As a non-limiting example, the at least one sensor is an inertial sensor. Inertial sensors keep track of an edge device's location using a combination of inputs including, but not limited to, a compass/magnetometer and an accelerometer. In another embodiment, the at least one sensor is a barometer. While outdoor navigation typically occurs on one level, either going straight or turning, elevation is a concern when navigating indoors. Since altitude is closely related to air pressure, the use of a barometer provides an accurate means of location.
In one embodiment, the geolocation of an edge device is determined based on ultrasonic technologies, such as radio-frequency identification (RFID) or near-field communications (NFC). In another embodiment, the geolocation of an edge device is determined based on BLUETOOTH beacons. BLUETOOTH beacons are placed every few meters and are operable to communicate with any device equipped with BLUETOOTH version 4.0, 4.1, 4.2, 5, 5.1, 5.2, or greater. In yet another embodiment, the geolocation of an edge device is determined based on terrestrial transmitters. Terrestrial transmitters are location transmitters that use the same principle as GPS, but are mounted on buildings and cell towers. Since the terrestrial transmitters are stationary and provide a much stronger signal to receivers than satellites do from space, the terrestrial transmitters are operable to pinpoint an edge device's location near-instantaneously.
In another embodiment, an edge device's geolocation is determined using Hyper Text Markup Language 5 (HTML5). HTML5 is the next major revision of the HTML standard superseding HTML 4.01, XHTML 1.0, and XHTML 1.1. HTML5 (e.g., HTML 5, HTML 5.1, HTML 5.2) is a standard for structuring and presenting web content on the World Wide Web. In another embodiment, an edge device's geolocation is determined using an HTML version beyond HTML5.
In another embodiment, an edge device's geolocation is determined using a combination of at least two of the previously mentioned geolocation techniques.
In one embodiment, the present invention provides systems and method for locating mobile edge platform nodes for edge devices using latency-based georouting and/or download time-based georouting in a distributed edge computing platform as described in U.S. Pat. No. 10,986,173, which is incorporated herein by reference in its entirety. Latency refers to the delay before a transfer of data begins following an instruction for its transfer and download time refers to the number of bytes per second that data travels from a remote and/or local server to a user's edge device. Georouting relies on geographical information such that a message from the device is routed to a destination edge platform node based on geographic location rather than network address. Georouting reduces latency by using the shortest path in physical distance and executing requests on a nearest node to the edge device. In one embodiment, the georouting and/or the detection of the nearest node does not require knowledge of network topology or a prior route discovery.
In one embodiment, a georouting system includes at least one edge device, at least one edge platform node, and at least one cloud platform. The at least one edge device is operable to store location information and contains a HyperText Transfer Protocol (HTTP) client. The at least one cloud platform includes a cloud platform DNS, an edge platform DNS, a plurality of edge platform APIs, an edge platform scheduler, a ledger containing a plurality of edge platform ledgers and operable to interact with at least one edge platform smart contract, a node database containing a plurality of edge platform routers, and/or a storage component for the cloud platform. The at least one edge platform node contains an Internet Protocol (IP) address, an edge platform executor, a plurality of v8 isolates, and/or at least one HTTP server program. The HTTP client of the at least one edge device is operable to communicate with both the cloud platform DNS and the edge platform DNS, where the edge platform DNS is in network communication with the plurality of edge platform routers in the node database.
In one embodiment, a georouting system includes a plurality of edge devices, a plurality of edge platform nodes, and/or at least one cloud platform. Each of the plurality of edge devices is operable to store location information and/or an HTTP client. The at least one cloud platform includes a cloud platform DNS, an edge platform DNS, a plurality of edge platform APIs, at least one edge platform scheduler, a ledger containing a plurality of edge platform ledgers operable to interact with at least one edge platform smart contract, at least one node database containing a plurality of edge platform routers, and/or a storage component for the cloud platform. The plurality of edge platform nodes store information relating to, but not limited to, an IP address, an edge platform executor, a plurality of v8 isolates, and/or at least one HTTP server program. The HTTP client of each of the plurality of edge devices is in network communication with the cloud platform DNS and the edge platform DNS, where the edge platform DNS is in network communication with the plurality of edge platform routers in the at least one node database. In one embodiment, the at least one cloud platform is public. In another embodiment, the at last one cloud platform is private. In another embodiment, the location information of the plurality of edge devices is real-time or near real-time location information.
In another embodiment, at least one edge device is in network communication with at least one cloud platform. The at least one edge device is operable to store location information and/or at least one HTTP client. The at least one cloud platform includes a cloud platform DNS, an edge platform DNS, a plurality of edge platform APIs in communication with a plurality of edge platform routers where the plurality of edge platform routers are stored in a cloud platform node database, an edge platform scheduler, a plurality of edge platform ledgers stored in at least one cloud platform ledger, and/or at least one cloud platform storage component. The at least one cloud platform ledger is operable to interact with edge platform smart contracts. The at least one edge device is in network communication with a plurality of edge platform nodes. The plurality of edge platform nodes each contain an IP address, a node ID, an edge platform executor, and/or a plurality of v8 isolates. The plurality of edge platform nodes is operable to receive an HTTP request from the at least one edge device. In one embodiment, the IP address is an IPv6 address. In another embodiment, the IP address is a future IP version beyond IPv6.
In one embodiment, an edge platform router and/or an edge platform API responds to an initial HTTP request from an edge device by injecting a HTML page that invokes a JavaScript function on the edge device. The edge device executes the JavaScript function, where the JavaScript function has been pre-populated with a subset of edge platform nodes in order to conduct its own latency-based geolocation of the edge device. In this embodiment, geolocation is an initial estimate of the edge device's general vicinity. The function uses latency and other measures to select at least one nearest edge platform node to the edge device. The combination of geolocation and latency, and/or other measures, completes the georouting process. Other measures include, but are not limited to, download speed/time, upload speed, and/or response time. In one embodiment, the latency-based georouting distinguishes between successful HTTP requests and unsuccessful HTTP requests when calculating latency, download speed/time, upload speed, response time, and/or combinations thereof.
In one embodiment, at least one edge device is directed to at least one nearest edge platform node. Alternatively, the at least one edge device acts as an edge platform node. The at least one edge device is in network communication with a cloud platform. The at least one edge device is operable to store location information and/or an HTTP client. The cloud platform includes a cloud platform DNS, an edge platform DNS, a plurality of edge platform APIs, an edge platform scheduler, a plurality of edge platform ledgers in communication with a cloud platform ledger wherein the cloud platform is operable to interact with at least one edge platform smart contract, a cloud platform storage component, and/or a cloud platform node database operable to store a plurality of edge platform routers, wherein the plurality of edge platform routers are in network communication with the plurality of edge platform APIs. The HTTP client of the at least one edge device queries the plurality of edge platform APIs for a hostname, where the at least one edge device's current location is appended as query parameters to the Uniform Resource Identifier (URI). The plurality of edge platform APIs replies to the at least one edge device's request with a HTML page, wherein the HTML page contains at least one JavaScript function. The at least one JavaScript function is operable to fetch information from the plurality of edge platform nodes. The HTTP client of the at least one edge device executes each request to the plurality of edge platform nodes in parallel. The HTTP client of the at least one edge device determines the best host edge platform node using latency-based or download time-based georouting. Alternatively, the at least one JavaScript function is operable to fetch an object from a plurality of edge platform nodes, where each request is performed in parallel.
In one embodiment, a nearest edge platform node is located using Johnson's All Pairs Shortest Path Algorithm. In another embodiment, the algorithm used is Floyd-Warshall's All Pairs Shortest Path algorithm. Alternatively, the nearest edge platform node is solved using another algorithm, for example but not for limitation, Shortest Path A*, Bi-Directional Dijkstra Shortest Path, Bi-Directional A* Shortest Path, Shortest Path Dijkstra, Driving Distance, K-Shortest Path (Multiple Alternative Paths), K-Dijkstra (One to Many Shortest Path), Traveling Sales Person, and/or Turn Restriction Shortest Path (TSRP).
In another embodiment, an HTTP client of an edge device queries an edge platform API and/or an edge platform router. The edge platform API and/or the edge platform router responds to the query of the edge device with a HTML page containing at least one JavaScript function. The at least one JavaScript function is pre-populated to request information from a plurality of edge platform nodes. The edge device executes each request from the plurality of edge platform nodes in parallel. The edge device determines the best host edge platform node using latency-based georouting and/or download time-based georouting. Alternatively, the HTML page contains at least one function in a programming language other than JavaScript.
Content Delivery Network
The network of mobile edge platform nodes is operable to create a content delivery network (CDN) for delivering content to edge devices. A CDN is a network of servers and data centers geographically distributed over an area to increase availability and performance by locating services closer to end users. CDNs provide internet content including but not limited to web objects (e.g., text, images, scripts), downloadable objects (e.g., media files, software), applications, and streaming. In a preferred embodiment, the mobile edge platform nodes of the CDN of the present invention are operable to provide content to devices regardless of the MNO associated with each of the devices.
The platform of the present invention provides a content-addressed data network (sometimes referred to as “EdjNet”) as described in U.S. Provisional Patent Application No. 63/090,265 which is incorporated herein by reference in its entirety, which enables the transparent, opportunistic, and secure dissemination of data between nodes in a peer-to-peer network. The platform includes a peer-to-peer protocol that uses cryptographic identities, delegation of trust, and end-to-end encryption, to create a global namespace for self-validating data that runs transparently over IPv4 and/or IPv6 networks. In a preferred embodiment, the system encrypts data including, but not limited to, network traffic, stored data, and logs.
Modern CDNs operate with tens to hundreds of points of presence (POPs) in major metropolitan areas. These POPs are generally co-located in carrier-neutral data centers. The CDNs provide value by caching content in these POPs and servicing users in the general vicinity through local last-mile networks. The CDN of the present invention extends even further from these POPs to get closer to end users and devices than previously possible. The POPs of the present invention not only include carrier-neutral data centers, but office buildings, residential buildings, industrial sites, 5G microcells and femtocells, WI-FI access points, etc. The CDN of the present invention forms a “far edge” at the extreme border of the network (e.g., on the same local area network (LAN) or 5G cell as a user or edge device).
A key weakness of modern CDNs is that POPs are essentially islands of infrastructure. There is no intelligent network between nodes in a CDN-POP. Therefore, cache misses to a POP always result in origin fetches, even if another nearby CDN-POP already has a cached copy of the data. The CDN of the present invention is formed of not only data center POPs, but tiny points of presence deployed across an area (e.g., city). Nodes in the present invention cooperate intelligently as a network to overcome the limitations of modern CDNs and clouds. The nodes form a decentralized cache, eliminating origin prefetches when nearby nodes have copies of the data or fragments of the data.
Another problem in modern CDNs is the origin fetch itself. The further the origin server is from the CDN proxy, the higher the latency, and the longer it takes to establish a connection and retrieve data for a user. Advantageously, the nodes of the present invention are operable to cooperate to maintain a pool of persistent connections to as many other proxy nodes as reasonable, which are then operable to be used for proxy requests. The present invention uses a peer-to-peer network as a basis for the CDN to reduce latency and increase throughput in serving requests.
Nodes in the distributed edge computing platform (sometimes referred to as “EDJX nodes”) are zero-configuration nodes, meaning the nodes are operable to acquire any configuration dynamically and on-the-fly from the ad-hoc environment. Consequently, all nodes are identical from a software stack and configuration point of view, removing the need for orchestration and configuration management. In a preferred embodiment, every node in the distributed edge computing platform is designed for zero-configuration and all nodes are essentially identical. In one embodiment, the distributed edge computing platform dynamically allocates and schedules resources based on individual node capabilities without operator intervention. Advantageously, this allows developers to focus on building critical functionality because there are no infrastructure dependencies or complex orchestration systems to manage.
Every node in the distributed edge computing platform exposes a number of protocol endpoints, based on network policy, to enable proximal cloud services: (1) HTTP and Hypertext Transfer Protocol Secure (HTTPS), (2) Message Queuing Telemetry Transport (MQTT), (3) Object Storage, and/or (4) Domain Name System (DNS).
HTTP and HTTPS services include, but are not limited to, request routing, rewriting, redirecting, and/or triggering serverless functions. The platform is preferably operable to perform proximity-based routing of HTTP and/or HTTPS requests to the closest content-addressed data network-enabled node. In one embodiment, the proximity-based routing is based on at least one proximity metric including, but not limited to, availability, performance, latency, and/or other criteria. In one embodiment, the platform is operable to create global rewrite rules to transparently rewrite uniform resource identifiers (URIs). In one embodiment, the platform is operable to create global redirect rules to transparently redirect URIs. In one embodiment, the platform is operable to trigger serverless functions based on HTTP request, URI, etc.
Object storage services include, but are not limited to, key-value storage, triggering serverless functions, durability, policies, and/or encryption. In one embodiment, the platform is operable to persist data using key-value storage under a single, global namespace over HTTP and HTTPS. In one embodiment, the platform is operable to trigger serverless functions based on creation, deletion, or updates to data objects. The platform preferably is operable to perform transparent and opportunistic replication of data ensuring durability through eventual consistency. In one embodiment, the platform controls access to data based on Identity and Access Management (IAM) policies which dynamically replicate. In one embodiment, the platform includes full end-to-end encryption of data in transit and at rest with optional encryption of payloads based on cryptographic identities tied to IAM policies. The platform preferably includes a log of where data originated, user(s) who have accessed the data, and how the data has changed over time.
As previously described, in one embodiment, the system provides a content delivery network as shown in
The user device makes an HTTP connection to the nearest node (Step 3). The nearest node determines if the HTTP request is already in the cache or if the HTTP request is operable to be resolved using peer nodes. If the HTTP request is operable to be resolved by the nearest node (with or without the use of peer nodes), a response is returned to the user device (Step 6). If the HTTP request cannot be resolved by the nearest node, the content is fetched from the origin server (Step 4), cached (Step 5), and returned to the user device in near real time (Step 6).
DNS services include, but are not limited to, routing and/or delegating authority. In one embodiment, the platform responds to DNS requests using at least one DNS metric. In one embodiment, the at least one DNS metric includes, but is not limited to, geospatial proximity, performance, and/or availability. The platform is preferably operable to dynamically direct clients to edge nodes. In one embodiment, the platform is operable to delegate DNS authority to the content-addressed data network to disseminate DNS information and routing rules to the global network.
Content-addressed data network nodes coordinate dynamically to deliver cloud services at the far-edge of modern communication networks, across a range of hardware platforms (e.g., IoT, mobile, server, etc.). The content-addressed data network federates a diverse set of physical infrastructures to create a single, global data network, in which data is securely persisted and replicated with assured integrity. Working together, nodes on the distributed edge computing platform deliver cloud services over standard protocols and interfaces.
Advantageously, the distributed edge computing platform of the present invention provides increased responsiveness, improved agility, simplified operations and increased data integrity. The distributed edge computing platform enables proximal data processing and computation in order to reduce application latencies and increase responsiveness. Building decentralized applications with the distributed edge computing platform of the present invention enables near real-time data fusion and algorithms to work seamlessly across a plurality of connected devices.
Additionally, the distributed edge computing platform of the present invention helps developers build distributed applications at planet-scale. All serverless functions are stored on the content-addressed data network as content-addressed data blocks and opportunistically disseminated among the plurality of the content-addressed data network nodes. There is no software to deploy or maintain on edge computing nodes. As a result, deploying functions, cache purges, and/or rolling back or forward between versions of serverless functions are nearly instantaneous.
Neutral Host Cellular Network
The mobile edge platform nodes and the content delivery network of the present invention are operable to be used to create a neutral host cellular network. A neutral host network is carrier-independent in that each mobile edge platform node is operable to provide broadband and other wireless MNO services to a device regardless of which carrier the device uses. Advantageously, developing an effective neutral host cellular network eliminates the need for an individual MNO to create its own edge infrastructure for providing cellular services. Edge compute and access to the internet via a mobile edge platform node reduces dependency on the backhaul network and a cloud and/or local data center, thus reducing latency as well as costs associated with maintaining non-distributed networks and systems.
In one embodiment, the edge computing platform is operable to establish a private cellular network using at least one mobile edge platform node. In one embodiment, the private cellular network is a Long-Term Evolution (LTE) network. Alternatively, the private cellular network is a 4G/5G network, thus taking advantage of 5G low latency. Network protocols beyond 5G are also compatible with the present invention. In one embodiment, the private cellular network is a standalone network (e.g., a 5G network) and does not have legacy network (e.g., 4G LTE network) dependencies. Alternatively, the private cellular network is non-standalone and includes both 5G and 4G LTE infrastructure. A private 4G/5G network has advantages over a WI-FI network. WI-FI networks are susceptible to congestion and interference, and have shorter ranges than private 4G/5G networks. In addition, private 4G/5G networks use security protocols adapted from wireless cellular networks, e.g., subscriber identification module (SIM)-based security, which can be more secure than WI-FI networks. Private 4G/5G networks are especially advantageous when large amounts of data are continuously transported across the network, for example in facilities with many Internet of Things (IoT) devices that are continuously collecting and analyzing data. Private 4G/5G networks also enable more stable and secure video surveillance systems or video-as-a-sensor systems.
Enabling edge computing and a content delivery network on a private cellular network (e.g., private 4G/5G network) further improves the private cellular network by reducing latency for compute services and internet access in a consolidated edge platform mobile node infrastructure. Additionally, the private cellular network is operable to be customized according to the security and latency needs of an organization. The organization includes but is not limited to a hospital, a port, an airport, a factory, a mine, a manufacturing facility, a shipping facility, an office center, a campus, a stadium, a business, a shopping center, a performance venue, a smart city, a public space, and/or a location with a population density above a set threshold for a set period of time.
The private cellular network (e.g., private 4G/5G network) is implemented via at least one mobile edge platform node wherein the at least one mobile edge platform node functions as an access node for internet and radio access, an edge compute node, and/or a content delivery network node. In one embodiment, the private cellular network uses georouting for locating edge nodes to reduce latency. The at least one mobile edge platform node is preferably a neutral host in that it is carrier independent. As previously addressed, the at least one mobile edge platform node is operable for internet access and packet processing directly at the edge, thus eliminating the need to send packets through the backhaul network of a specific MNO. In an embodiment wherein the private cellular network is implemented on a plurality of mobile edge platform nodes, the edge computing platform is operable to synchronize the plurality of mobile edge platform nodes. In one embodiment, the plurality of mobile edge platform nodes is operable to support precision time protocol (PTP) for accurate synchronization. The edge computing platform is operable to establish a private cellular network (e.g., private 4G/5G network) on licensed, unlicensed, and/or shared spectrum. In one embodiment, the private cellular network (e.g., private 4G/5G network) co-exists with a WI-FI network and/or other cellular networks.
Advantageously, the use of the mobile edge platform node as a neutral host allows any MNO to use the private cellular network (e.g., private 4G/5G network). In addition, any MNO can deliver content through the CDN established by the edge computing platform and the mobile edge platform nodes on the private cellular network. The edge computing platform is operable to allow access to an MNO through a standard S1 interface.
In one embodiment, the edge computing platform implements configurable quality of service (QoS) protocols to create multiple layers of prioritization in the private cellular network. In one embodiment, the QoS protocol includes a sensing function, a processing function, and an acting function as described in U.S. Patent Publication No. 2020/0244547, filed Oct. 10, 2019, which is incorporated herein by reference in its entirety. The sensing function includes a sensing application on the device wherein the sensing application is operable to be accessed via an API call. The sensing application is operable to detect sensing data including signal strength, content delivery network metrics, and/or other network parameters in real time or near real time. The sensing function is then operable to send the sensing data to the processing function. In one embodiment, the processing function is executed by the edge computing platform. Alternatively, the processing function is operable to be executed on the mobile edge platform node. The processing function includes but is not limited to authenticating the device, analyzing network conditions, and/or determining the compute and/or resource needs of the current session of the device. The acting function is executed by the edge computing platform by initiating a request for service conditions from a mobile edge platform node. In one embodiment, the mobile edge platform node is the nearest node to the edge device as determined by georouting. In another embodiment, the request for service conditions, e.g., for additional bandwidth, is made to a policy server. Alternatively, the request for service conditions is a recommended transport bit rate as described in U.S. Patent Publication No. 2020/0084257, filed Nov. 14, 2019, which is incorporated herein by reference in its entirety. The mobile edge platform node then delivers the requested service conditions. In one embodiment, the mobile edge platform node is operable to perform base station node functions in order to deliver the requested service conditions. In another embodiment, the mobile edge platform node is operable for cellular handover to a second mobile edge platform node.
In one embodiment, the mobile edge platform nodes are monitored as described in U.S. Patent Publication No. 2018/0376358, filed Jun. 19, 2018, which is incorporated herein by reference in its entirety. Advantageously, the sensing function on the device itself means that the request for service conditions is only made when immediately necessary and that the request is specific to a device and a session. The solution provides for Quality of Service improvement to mobile subscribers by setting up a dedicated bearer to the user in the last mile, ensuring that sufficient bandwidth is available and guaranteed, enhancing customer experience.
In one embodiment, the private cellular network (e.g., private 4G/5G network) includes a virtual private cellular network (e.g., virtual private 4G/5G network). A virtual private cellular network is useful when an organization has multiple sites and requires that mobile devices that move between the sites connect and reconnect to the same private cellular network. In one embodiment, the edge computing platform is operable for virtualization and network slicing. In one embodiment, the edge computing platform is operable for dynamic network slicing as described in U.S. Pat. No. 10,841,399, filed Oct. 3, 2019 and issued Nov. 17, 2020, which is incorporated herein by reference in its entirety. In one embodiment, a slice of a cellular network is operable to selectively access a mobile edge platform node.
In one embodiment, the edge computing platform is operable to authenticate devices accessing the private cellular network. The devices include, but are not limited to, a computer, a tablet, a mobile phone (e.g., a smartphone), a wearable, a camera, a sensor (e.g., a temperature sensor, a humidity sensor, a scale, a motion sensor), a tracker, a smart appliance, a vehicle (e.g., a commercial vehicle, an industrial vehicle), heavy equipment, and/or machinery. The edge computing platform is operable to implement at least one access policy on the private cellular network.
In one embodiment, a mobile edge platform node is operable to register and authenticate a device when the device requests wireless services from the mobile edge platform node. In one embodiment, the registration and authentication are automatic. After registering the device, the mobile edge platform node is operable to determine which MNO services the device and access an MNO account associated with the device. The mobile edge platform node is then operable to track the wireless services used by the device and bill the associated MNO account accordingly. Multiple billing schemes for each MNO are operable to be implemented on the mobile edge platform node simultaneously. The mobile edge platform node is further operable to share account information and/or usage information with other edge platform nodes. In one embodiment, the mobile edge platform node is operable to implement overdraft protection for an MNO account. In another embodiment, the mobile edge platform node is operable to deny a mobile device from accessing wireless services based on the associated MNO account.
Evolved Packet Core
The edge computing platform of the present invention is operable to establish an Evolved Packet Core (EPC) architecture for LTE and/or 5G NR wireless broadband communications when creating a wireless network. Alternative EPC architectures beyond 5G are also compatible with the present invention. EPC is a flat architecture with certain node functions and subcomponents including but not limited to a mobile management entity (MME), a home subscriber server (HSS), a serving gateway (SGW), a packet data network gateway (PGW), a policy and charging rules function (PCRF), and an access network discovery and selection function (ANDSF). In one embodiment, a mobile edge platform node is operable to perform at least one of the EPC node functions. Advantageously, pushing the EPC to the edge eliminates the need to transport packets through the backhaul network to an EPC of a specific MNO, thus reducing latency and providing accelerated content delivery. In addition, incorporating the EPC on the mobile edge platform node provides enhanced mobile coverage. In one embodiment the control plane and the user plane of the EPC are disaggregated, allowing rapid dissemination of Platform Nodes and complete control of data paths by the edge computing platform. The control plane includes in one embodiment radio-specific functionality which depends on the connection state of the user device and/or the mobile edge platform node. The user plane includes packet data convergence protocol (PDCP), radio link control (RLC), and/or medium access control (MAC). The user plane is operable for tunneling protocols including but not limited to GPRS tunneling protocol (GTP). In one embodiment, the EPC is integrated into the platform node at the user plane and the user plane functions are deployed to platform nodes. The platform nodes interface with the base station node radio hardware and software. In one embodiment, the neutral host platform node and the EPC of the edge computing platform interface with the EPC of the MNO through a standard S1 interface. The interface between the MNO EPC and the edge computing platform EPC allows for authentication of subscribers as well as policy management of data traffic. In one embodiment, quality of service and delivery occur locally at each mobile edge platform node.
Federated Network
The edge computing platform of the present invention is further operable to create a neutral host public cellular network (e.g., neutral host public 4G/5G network) along with the private cellular network (e.g., private 4G/5G network) wherein the mobile edge platform nodes that are used to create the private cellular network are also operable to provide a public cellular network (e.g., public 4G/5G network) to devices. Advantageously, implementing a public cellular network and a private cellular network on the same mobile edge platform nodes extends the far edge and increases access to edge computing, wireless services, and the content delivery network. MNOs do not have to invest in software or hardware infrastructure to extend coverage of their wireless services because the public cellular network of the present invention is carrier-independent and can be accessed by any device. The edge CDN infrastructure of the present invention also allows a plurality of MNOs to deliver content through the edge CDN using the same mobile edge computing platform node. In one embodiment, the private cellular network and the public cellular network have the same area of coverage.
The edge computing platform of the present invention is operable to determine whether a device has access to the private cellular network or the public cellular network. In one embodiment, the access is based on location. For example, a private cellular network is established inside a building and a public cellular network is established outside the building. Devices of passerby who walk past the building are granted access to the public cellular network created from the same mobile edge platform node. Devices that are located inside the building, e.g., a security camera, are connected to the private cellular network. In another embodiment, access to the private cellular network and/or the public cellular network is based on at least one access policy. For example, devices registered to employees in the building are granted access to the private cellular network while unregistered devices are granted access to the public cellular network. In another embodiment, only devices that can access the private cellular network are able to access the public cellular network. In one embodiment, the at least one access policy is operable to be established by a network operator. Alternatively, the at least one access policy is operable to be established by an administrator, e.g., a building manager.
In one embodiment, the public cellular network (e.g., public 4G/5G network) allows for roaming, whereby a device is operable to access the public cellular network via a roaming carrier if the carrier for the device is not delivering services through the public cellular network. The mobile edge platform node is operable to recognize when a device is roaming. In another embodiment, the private cellular network is also operable for roaming (e.g., private 4G/5G network). The edge computing platform is operable to implement security and access policies such that sensitive data stored on the CDN of the private cellular network are protected from being accessed by unauthorized mobile devices. In one embodiment, the private cellular network includes a whitelist of authorized mobile devices. In another embodiment, all devices connected to the mobile edge platform node and the EPC are subject to the complete security framework of the relevant 3GPP standards.
A non-limiting implementation of the private cellular network (e.g., private 4G/5G network) and the public cellular network (e.g., public 4G/5G network) is at a port. A port serves many functions, including as a dock for cargo shipments, cruise/passenger ships, and individual watercraft. In addition, a port may include a marina with various commercial establishments (e.g., restaurants, retail services), which is a popular destination for visitors who expect accessible wireless services. Freight companies need to keep track of cargo shipments passing through a port and deploy a number of devices to do so, including, but not limited to, smartphones, computers, tablets, IoT sensors, video cameras, and/or scanners. The data from these devices is continuously updated and shared between devices and users to streamline the tracking and processing of cargo. The edge computing platform of the present invention is operable to establish a private cellular network for the port staff and visitors using at least one mobile edge platform node. The private cellular network can be illustrated as an “inner ring.” The at least one mobile edge platform node acts as a radio node for network access (e.g., 4G/5G network access), an edge computing node, and a content delivery network node. The private cellular network provides higher speeds, lower delays, and guaranteed quality to devices associated with port staff and visitors. The private cellular network is also operable to host a variety of applications, including but not limited to port navigation, warehouse logistics and automation, facility and machinery management, lorry fleet management, and emergency services. The private cellular network is configured such that the visitors to the port only have access to certain applications, e.g., navigation and emergency services, while the staff of the port have access to additional applications, e.g., warehouse logistics and facility management. In one embodiment, the edge computing platform establishes different network slices in the private cellular network for each port stakeholder (e.g., shop owners, administration, operators). The same at least one mobile edge platform node that establishes the private cellular network is also operable to establish a public cellular network in the city surrounding the port. The public cellular network can be illustrated as an “outer ring.” The public cellular network is accessible to port staff in the city and provides the same advantages of the private cellular network. In one embodiment, a device is further able to roam onto the inner ring for coverage via the MNO of the device.
An alternative non-limiting implementation of the private cellular network and the public cellular network is in a hospital. At least one mobile edge platform node establishes a private cellular network in the hospital wherein the private cellular network is only accessible by devices in the hospital's IT system. Advantageously, the at least one mobile edge platform node is operable to implement data privacy and security protocols in order to prevent breaches of the Health Insurance Portability and Accountability Act (HIPAA) and other compliance issues. For example, the at least one mobile edge platform node is operable to implement a blacklist filter on the internet services to blacklist websites that are likely to contain viruses or other threats to data privacy. As another non-limiting example, the at least one mobile edge platform node is operable to encrypt medical data before performing edge compute services. The at least one mobile edge platform node is also operable to establish a public cellular network in the hospital wherein the public cellular network is accessible by any devices in the hospital. Thus, patients, visitors, and hospital staff with personal devices are only able to access the public cellular network while the hospital devices that are used for storing and updating medical data are able to access the private cellular network.
Yet another alternative non-limiting implementation of the private cellular network and the public cellular network is in supply chain management. Internet of Things (IoT) devices are placed on base materials, individual components, equipment and machinery, products, packaging, shipping containers, and/or vehicles to label and identify each item. A facility such as a warehouse is also equipped with IoT sensors such as video cameras, smart gateways, and/or scanners that record the location and movement of IoT devices throughout the facility. The IoT sensors are also operable to detect defects, breakdowns, and/or status updates. This system helps businesses accurately track their products and capture the full supply chain, as well as identify delays and issues easily. As a result, businesses are able to accurately estimate capacity, volume, and transportation timelines to ensure that all product demands are met. IoT devices and IoT sensors that run continuously generate large amounts of data that must be processed, analyzed, and stored in order to serve as an effective automated system. Edge computing allows these functions to be performed closer to the IoT devices and sensors, thus reducing latency and dependency on a centralized data server. In one embodiment, the edge computing platform of the present invention establishes a private cellular network (e.g., private 4G/5G network) using at least one mobile edge platform node located in a warehouse. The IoT devices and the IoT sensors used to track the products manufactured and shipped from the warehouse connect to the private cellular network. Processing and analysis of the data from the IoT devices and the IoT sensors is done by the at least one mobile edge platform node. The at least one mobile edge platform node also provides internet access and the content delivery network to any of the devices in the factory based on at least one access policy. The at least one mobile edge platform node also creates a public cellular network (e.g., public cellular network) in the area surrounding the factory. Internet access and the content delivery network are available through the public cellular network of the at least one mobile edge platform node to devices that are not granted access to the private cellular network. The devices on the public cellular network are not able to view the IoT devices and the IoT sensors on the private cellular network.
The edge computing platform is operable to utilize a plurality of learning techniques including, but not limited to, machine learning (ML), artificial intelligence (AI), deep learning (DL), neural networks (NNs), artificial neural networks (ANNs), support vector machines (SVMs), Markov decision process (MDP), and/or natural language processing (NLP). The edge computing platform is operable to use any of the aforementioned learning techniques alone or in combination.
Further, the edge computing platform is operable to utilize predictive analytics techniques including, but not limited to, machine learning (ML), artificial intelligence (AI), neural networks (NNs) (e.g., long short term memory (LSTM) neural networks), deep learning, historical data, and/or data mining to make future predictions and/or models. The edge computing platform is preferably operable to recommend and/or perform actions based on historical data, external data sources, ML, AI, NNs, and/or other learning techniques. The edge computing platform is operable to utilize predictive modeling and/or optimization algorithms including, but not limited to, heuristic algorithms, particle swarm optimization, genetic algorithms, technical analysis descriptors, combinatorial algorithms, quantum optimization algorithms, iterative methods, deep learning techniques, and/or feature selection techniques.
Location data is created in the present invention using one or more hardware and/or software components. By way of example and not limitation, location data is created using the Global Positioning System (GPS), low energy BLUETOOTH based systems such as beacons, wireless networks such as W-IFI, Radio Frequency (RF) including RF Identification (RFID), Near Field Communication (NFC), magnetic positioning, and/or cellular triangulation. By way of example, location data is determined via an Internet Protocol (IP) address of a device connected to a wireless network. A wireless router is also operable to determine identities of devices connected to the wireless network through the router, and thus is operable to determine the locations of these devices through their presence in the connection range of the wireless router.
The server 850 is constructed, configured, and coupled to enable communication over a network 810 with a plurality of computing devices 820, 830, 840. The server 850 includes a processing unit 851 with an operating system 852. The operating system 852 enables the server 850 to communicate through network 810 with the remote, distributed user devices. Database 870 is operable to house an operating system 872, memory 874, and programs 876.
In one embodiment of the invention, the system 800 includes a network 810 for distributed communication via a wireless communication antenna 812 and processing by at least one mobile communication computing device 830. Alternatively, wireless and wired communication and connectivity between devices and components described herein include wireless network communication such as WI-FI, WORLDWIDE INTEROPERABILITY FOR MICROWAVE ACCESS (WIMAX), Radio Frequency (RF) communication including RF identification (RFID), NEAR FIELD COMMUNICATION (NFC), BLUETOOTH including BLUETOOTH LOW ENERGY (BLE), ZIGBEE, Infrared (IR) communication, cellular communication, satellite communication, Universal Serial Bus (USB), Ethernet communications, communication via fiber-optic cables, coaxial cables, twisted pair cables, and/or any other type of wireless or wired communication. In another embodiment of the invention, the system 800 is a virtualized computing system capable of executing any or all aspects of software and/or application components presented herein on the computing devices 820, 830, 840. In certain aspects, the computer system 800 is operable to be implemented using hardware or a combination of software and hardware, either in a dedicated computing device, or integrated into another entity, or distributed across multiple entities or computing devices.
By way of example, and not limitation, the computing devices 820, 830, 840 are intended to represent various forms of electronic devices including at least a processor and a memory, such as a server, blade server, mainframe, mobile phone, personal digital assistant (PDA), smartphone, desktop computer, netbook computer, tablet computer, workstation, laptop, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the invention described and/or claimed in the present application.
In one embodiment, the computing device 820 includes components such as a processor 860, a system memory 862 having a random access memory (RAM) 864 and a read-only memory (ROM) 866, and a system bus 868 that couples the memory 862 to the processor 860. In another embodiment, the computing device 830 is operable to additionally include components such as a storage device 890 for storing the operating system 892 and one or more application programs 894, a network interface unit 896, and/or an input/output controller 898. Each of the components is operable to be coupled to each other through at least one bus 868. The input/output controller 898 is operable to receive and process input from, or provide output to, a number of other devices 899, including, but not limited to, alphanumeric input devices, mice, electronic styluses, display units, touch screens, signal generation devices (e.g., speakers), or printers.
By way of example, and not limitation, the processor 860 is operable to be a general-purpose microprocessor (e.g., a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated or transistor logic, discrete hardware components, or any other suitable entity or combinations thereof that can perform calculations, process instructions for execution, and/or other manipulations of information.
In another implementation, shown as 840 in
Also, multiple computing devices are operable to be connected, with each device providing portions of the necessary operations (e.g., a server bank, a group of blade servers, or a multi-processor system). Alternatively, some steps or methods are operable to be performed by circuitry that is specific to a given function.
According to various embodiments, the computer system 800 is operable to operate in a networked environment using logical connections to local and/or remote computing devices 820, 830, 840 through a network 810. A computing device 830 is operable to connect to a network 810 through a network interface unit 896 connected to a bus 868. Computing devices are operable to communicate communication media through wired networks, direct-wired connections or wirelessly, such as acoustic, RF, or infrared, through an antenna 897 in communication with the network antenna 812 and the network interface unit 896, which are operable to include digital signal processing circuitry when necessary. The network interface unit 896 is operable to provide for communications under various modes or protocols.
In one or more exemplary aspects, the instructions are operable to be implemented in hardware, software, firmware, or any combinations thereof. A computer readable medium is operable to provide volatile or non-volatile storage for one or more sets of instructions, such as operating systems, data structures, program modules, applications, or other data embodying any one or more of the methodologies or functions described herein. The computer readable medium is operable to include the memory 862, the processor 860, and/or the storage media 890 and is operable be a single medium or multiple media (e.g., a centralized or distributed computer system) that store the one or more sets of instructions 900. Non-transitory computer readable media includes all computer readable media, with the sole exception being a transitory, propagating signal per se. The instructions 900 are further operable to be transmitted or received over the network 810 via the network interface unit 896 as communication media, which is operable to include a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal.
Storage devices 890 and memory 862 include, but are not limited to, volatile and non-volatile media such as cache, RAM, ROM, EPROM, EEPROM, FLASH memory, or other solid state memory technology; discs (e.g., digital versatile discs (DVD), HD-DVD, BLU-RAY, compact disc (CD), or CD-ROM) or other optical storage; magnetic cassettes, magnetic tape, magnetic disk storage, floppy disks, or other magnetic storage devices; or any other medium that can be used to store the computer readable instructions and which can be accessed by the computer system 800.
In one embodiment, the computer system 800 is within a cloud-based network. In one embodiment, the server 850 is a designated physical server for distributed computing devices 820, 830, and 840. In one embodiment, the server 850 is a cloud-based server platform. In one embodiment, the cloud-based server platform hosts serverless functions for distributed computing devices 820, 830, and 840.
In another embodiment, the computer system 800 is within an edge computing network. The server 850 is an edge server, and the database 870 is an edge database. The edge server 850 and the edge database 870 are part of an edge computing platform. In one embodiment, the edge server 850 and the edge database 870 are designated to distributed computing devices 820, 830, and 840. In one embodiment, the edge server 850 and the edge database 870 are not designated for distributed computing devices 820, 830, and 840. The distributed computing devices 820, 830, and 840 connect to an edge server in the edge computing network based on proximity, availability, latency, bandwidth, and/or other factors.
It is also contemplated that the computer system 800 is operable to not include all of the components shown in
The above-mentioned examples are provided to serve the purpose of clarifying the aspects of the invention, and it will be apparent to one skilled in the art that they do not serve to limit the scope of the invention. By nature, this invention is highly adjustable, customizable and adaptable. The above-mentioned examples are just some of the many configurations that the mentioned components can take on. All modifications and improvements have been deleted herein for the sake of conciseness and readability but are properly within the scope of the present invention.
This application is related to and claims priority from the following U.S. patents and patent applications. This application is a continuation-in-part of U.S. application Ser. No. 17/226,716, filed Apr. 9, 2021, which is a continuation of U.S. application Ser. No. 16/831,069, filed Mar. 26, 2020, and this application claims the benefit of and priority from U.S. Provisional Application No. 63/090,265, filed Oct. 11, 2020, each of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6661799 | Molitor | Dec 2003 | B1 |
| 6829654 | Jungck | Dec 2004 | B1 |
| 7032031 | Jungck | Apr 2006 | B2 |
| 8392912 | Davis | Mar 2013 | B2 |
| 8539079 | Thireault | Sep 2013 | B2 |
| 8694610 | Jungck | Apr 2014 | B2 |
| 9391856 | Kazerani | Jul 2016 | B2 |
| 9444858 | Boyle et al. | Sep 2016 | B1 |
| 9713000 | Oertle et al. | Jul 2017 | B2 |
| 9787560 | Maddux | Oct 2017 | B2 |
| 10122547 | Mahindra et al. | Nov 2018 | B2 |
| 10334446 | Ashrafi | Jun 2019 | B2 |
| 10341868 | Ross et al. | Jul 2019 | B2 |
| 10567291 | Sabella et al. | Feb 2020 | B2 |
| 10575244 | Gustafson et al. | Feb 2020 | B1 |
| 10778794 | Wei et al. | Sep 2020 | B2 |
| 10938916 | Enat | Mar 2021 | B2 |
| 20010047241 | Khavakh | Nov 2001 | A1 |
| 20030065763 | Swildens | Apr 2003 | A1 |
| 20040064693 | Pabla et al. | Apr 2004 | A1 |
| 20050210149 | Kimball | Sep 2005 | A1 |
| 20050273593 | Seminaro et al. | Dec 2005 | A1 |
| 20080060054 | Srivastava | Mar 2008 | A1 |
| 20100223364 | Wei | Sep 2010 | A1 |
| 20100287019 | Guo | Nov 2010 | A1 |
| 20120076134 | Brownrigg | Mar 2012 | A1 |
| 20120221652 | Sainio et al. | Aug 2012 | A1 |
| 20130103785 | Lyon | Apr 2013 | A1 |
| 20130111024 | Setia et al. | May 2013 | A1 |
| 20130297669 | Wang | Nov 2013 | A1 |
| 20130332559 | Ivars et al. | Dec 2013 | A1 |
| 20140136952 | Zhu et al. | May 2014 | A1 |
| 20140164563 | Leekley et al. | Jun 2014 | A1 |
| 20150074296 | Eidelman | Mar 2015 | A1 |
| 20170366591 | Thomas | Dec 2017 | A1 |
| 20180041578 | Lee et al. | Feb 2018 | A1 |
| 20180052839 | Sharma | Feb 2018 | A1 |
| 20180130098 | Swanson et al. | May 2018 | A1 |
| 20180132015 | Borrelli et al. | May 2018 | A1 |
| 20180241814 | Kristiansson | Aug 2018 | A1 |
| 20180288091 | Doron | Oct 2018 | A1 |
| 20180302440 | Hu et al. | Oct 2018 | A1 |
| 20190007521 | Lipstone | Jan 2019 | A1 |
| 20190188581 | Chabin et al. | Jun 2019 | A1 |
| 20200008007 | Belghoul | Jan 2020 | A1 |
| 20200107403 | Frydman et al. | Apr 2020 | A1 |
| 20200159511 | Frydman et al. | May 2020 | A1 |
| 20200177606 | Valluri et al. | Jun 2020 | A1 |
| 20200259836 | Kumar | Aug 2020 | A1 |
| 20200296155 | McGrath et al. | Sep 2020 | A1 |
| 20210044675 | Frydman | Feb 2021 | A1 |
| 20210233045 | Singh | Jul 2021 | A1 |
| 20210400485 | Ergen et al. | Dec 2021 | A1 |
| 20220201056 | Zajac et al. | Jun 2022 | A1 |
| 20220224759 | Khosrowpour | Jul 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 111226429 | Jun 2020 | CN |
| 101823293 | Jan 2018 | KR |
| 101925268 | Feb 2019 | KR |
| Number | Date | Country | |
|---|---|---|---|
| 63090265 | Oct 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16831069 | Mar 2020 | US |
| Child | 17226716 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17226716 | Apr 2021 | US |
| Child | 17307676 | US |
