Patent Grant
12081553
A data center may house computer systems and various networking, storage, and other related components. Data centers may, for example, be used by service providers to provide computing services to businesses and individuals as a remote computing service or provide “software as a service” (e.g., cloud computing). Service providers may also utilize edge sites that may include a geographically distributed group of servers and other devices that work together to provide delivery of content to end-users of data center services. The edge sites may be fixed or mobile and provide extend the data center's services to areas served by the edge sites.
It is with respect to these considerations and others that the disclosure made herein is presented.
In various embodiments, users of a computing service such as a cloud computing service may be provided use of such services via computing and storage resources of the computing service at a remote location (“edge site”). The users may continue to benefit from the computing services, while aspects of the services are incorporated into the edge sites. Edge sites enable a data center to extend cloud services to local deployments using a distributed architecture that enables federated options for local and remote data and control management.
In some cases, the cloud computing service provider may lose connectivity with an edge site. Additionally, disconnection with an edge site (e.g., a mobile edge site) may be designed for and planned as a management action or intentional disconnection. In the first scenario, connectivity may be lost for a variety of reasons, such as a physical event that causes loss of network services, a denial-of-service attack, or an undetected event that causes significant latency or loss of communications. The complexities of edge site implementations may present challenges when connectivity issues arise between the cloud computing service provider and the edge site, potentially preventing the edge site from operating properly due to the loss of connectivity or operating with limited connectivity. In the case of an intentional disconnection, an edge site may be intended to or otherwise expected to operate in a disconnected mode. For example, a mobile edge site may be intended to operate in an environment with little/no connectivity such as in a deep-sea environment.
One challenge is that while the edge site is disconnected, the edge site's integrity may be compromised or otherwise unknown, thus causing a security challenge for the services provided by the edge site and for the data center when the edge site attempts to reconnect to the data center. The present disclosure provides various techniques and functions that allow for a disconnected or compromised edge site to continue providing services to users serviced by the edge site in a trusted manner. Various implementations allow for the edge site to provide, in a trusted and secure manner, a range of functionality from complete service (no loss of functionality) or limited service while the edge site is disconnected. As used herein, an edge site that operates in a disconnected capacity may be referred to as operating in an autonomous mode.
When the disconnection is unplanned, the present disclosure includes mechanisms that allow the edge site to make a determination as to whether the edge site should enter the autonomous mode and invoke trust mechanisms to ensure trusted operation of the edge site. The edge site may have functionality to detect loss of connectivity or limited connectivity and automatically enter the autonomous mode and invoke the trust mechanisms.
The autonomous mode may also be entered manually, for example to test features of the autonomous mode. The edge site may have functionality to detect the recovery of connectivity and automatically exit the autonomous mode and initiate a process to re-establish trust with the data center. The process to re-establish trust with the data center may result in the re-establishment of trust between the edge site and the cloud computing service provider. If certain conditions are not met, then re-establishment of trust between the edge site and the cloud computing service provider may be prohibited.
The disclosed embodiments provide techniques for disconnecting and reconnecting a data center and an edge site, and reconciling/resynchronizing operations between the data center and edge site in a trusted and secure manner. Prior to disconnection, the data center and the edge site may establish a level of trust, which can be re-established when the edge site is to be re-connected.
The described techniques can allow for secure delivery of services by an edge computing network, maintaining security of data and data access, and prevention of data loss, while maintaining efficient use of computing resources such as processor cycles, memory, network bandwidth, and power during operation of the edge computing network during the described conditions.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify all of the key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
The Detailed Description is described with reference to the accompanying figures. In the description detailed herein, references are made to the accompanying drawings that form a part hereof, and that show, by way of illustration, specific embodiments or examples. The drawings herein are not drawn to scale. Like numerals represent like elements throughout the several figures.
In some computing environments that provide virtualized computing and storage services, various computing and network services may be configured to enable the service provider to deploy their footprints closer to the user's premises, thereby extending the reach of the computing and network services closer to the user premises. For example, an enterprise that provides network carrier services may want computing services located closer to their networks or their customers, or a manufacturer may want to deploy computing resources closer to their facilities. Users of virtualized computing resources may benefit in many ways by deploying resources such as virtual machines on resources that are located closer to their premises. Additionally, localization of computing and storage devices may enable some users to more effectively meet data residency, compliance, latency, and other requirements, while continuing to benefit from many of the advantages of utilizing remote and/or virtualized computing services, such as scalability and flexibility. As used herein, “resources” may refer to various types of multi-dimensional resources including CPU, GPU, memory, etc.
Efficient management of the end-to-end capability services by the service provider can enable an equivalent experience when using edge sites. The integration of local and remote resources with a comprehensive remote resource management approach can minimize the overhead for the service provider by maximizing the capabilities of the edge site. The effective distribution of the management functions can be determined based on the implications for various performance and security implications such as latency and data security.
The present disclosure enables the operation of edge sites in a trusted manner during periods of time when the edge site is operating in an autonomous mode, where the edge site has limited or no connectivity to the main data center. Various embodiment may enable the continued processing and distribution of tasks and workloads to computing resources so as to efficiently deliver services in a trusted manner and allow the service provider to continue delivering services in an effective manner.
The present disclosure provides various techniques and functions that allow for a disconnected or compromised edge site to continue providing services to users serviced by the edge site in a trusted manner. Various implementations allow for the edge site to provide a range of functionality from complete service (no loss of functionality) or limited service while the edge site is disconnected. As used herein, an edge site that operates in a disconnected capacity may be referred to as operating in an autonomous mode.
When the disconnection is unplanned, the present disclosure includes mechanisms that allow the edge site to make a determination as to whether the edge site should enter the autonomous mode and invoke trust mechanisms to ensure trusted operation of the edge site. The edge site may also make a determination that trust cannot be maintained and perform associated protection mechanisms to avoid security issues. The edge site may have functionality to detect loss of connectivity or limited connectivity and automatically enter the autonomous mode.
The autonomous mode may also be entered manually, for example to test features of the autonomous mode. The edge site may have functionality to detect the recovery of connectivity and automatically exit the autonomous mode and initiate a process to re-establish trust with the data center prior to reconnecting to the data center.
In some embodiments, trust management features of the edge site during autonomous operation may include identity and access management and providing the edge site with the ability to allow for continued secure access to data and resources by authorized users of the edge site. The management features of the edge site during autonomous operation may also provide for management of sensitive data including secrets (e.g., certificates, keys).
During autonomous operation, management features of the edge site may perform continuous tracking of the usage of various resources provided by the edge site at various levels of granularity including resource usage at a user level. The tracking of resource usage may enable the service provider to maintain data for billing and other purposes while the edge site is operating in autonomous mode. The management features of the edge site may select various metrics to track usage and performance, which may involve selection of key performance data at various levels of data granularity and frequency. The trust mechanism may provide for secure storage of the key performance data and secure transfer to the data center when reconnected.
In some embodiments, functional features of the edge site during autonomous operation may include the ability to provide communications services to trusted user devices of the edge site.
In an embodiment, a trust agent may be implemented as a service running on the edge site. The trust agent may be configured to monitor integrity of the edge site during disconnected operation. The trust agent may further be configured to monitor local copies of certificates and other security related data and ensure that the data is updated at the edge site in preparation for a disconnection.
The trust agent may be pre-configured to take specified actions in the event of a disconnection. For example, if data center communication is lost for a specified period of time, then any local APIs may either configured as “fail open” and allow for local modification at the edge site, or “fail close” to shut down and lock that API (in instances where there is a threat that the system is lost or compromised).
The present disclosure additionally describes methods for trusted reconciliation and resynchronization between the edge site and cloud computing service provider when connectivity is restored. Reconciliation and resynchronization may include synchronization of states due to local edge state changes which may be recorded while the edge site is operating in autonomous mode. Reconciliation and resynchronization may also include changes made at the cloud computing service provider that were not synchronized to the edge site during autonomous operation.
The data center may be configured to take actions in response to a potentially malicious disconnect, or in response to an edge site that is determined to be untrusted. Any connections to the untrusted edge may be isolated within the data center and network access to the rest of the data center may be disabled. If trust is established between the data center and the trust agent, a chain of trust can be established between the remote edge site and the data center. The chain of trust can enable a staged reconnection of the devices and services at the remote edge site.
Referring to the appended drawings, in which like numerals represent like elements throughout the several FIGURES, aspects of various technologies for remote management of computing resources will be described. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration specific configurations or examples.
With reference to
In one example, a connection event 110 may occur between cloud provider node 100 and edge site 1120. The connection/degradation event 110 may be a planned event or an unplanned event. Referring to
Referring to
In an embodiment, the root of trust may be based on a single source of truth, which in one embodiment may be the trust manager 215 at the cloud service provider 200. During the initial configuration of the edge site 220 and its trust agent 231, a time-based trust mechanism may be established so that actions and behaviors, (e.g., what services/functions are locked and what remains open), may be preconfigured and expire after a predetermined period of time. Thus, a first level of trust may be established, in which during the predetermined period of time with no connection to the cloud provider 200, the edge site may allow full access to its services. After a second predetermined time period with no connection to the cloud provider 200, some of the APIs and functions at the edge site 220 may be shut down. There may be additional time periods after which additional subsets of functions may be shut down, followed by a final stage where the edge site 220 may be shut down completely.
In one embodiment, when the edge site 220 enters autonomous mode, the cloud provider 200 may mark the edge site 220 as an untrusted entity. This may be set as an initial status. When the edge site 220 is reconnected with the cloud provider 200, the trust manager 215 may communicate to the trust agent 231 as well as other functions in the cloud provider 200, indicating that resources and data at the edge site 220 should be marked as lost or untrusted.
The autonomous mode agent 230 may be a service running on the on-premise/edge site 220 that is configured to monitor connectivity conditions and track workloads that are being processed at the edge site 220 and determine how to handle pending tasks in the event of a connectivity event. The autonomous mode agent 230 may monitor various metrics including availability and other local conditions. The autonomous mode agent 230 may be configured to receive requests for operations from the edge capacity orchestrator 210 at the data center 200.
The autonomous mode agent 230 may be configured to control interfaces of the edge site 220 when the edge site 220 is disconnected, whether the disconnection is planned or unplanned. In the event of an unplanned disconnection, or if there is an indication of potentially malicious activity, the interfaces of the edge site 220 may fail closed and block access to the interfaces in the event of a failure/exception. In other cases, the interfaces of the edge site 220 may fail open and allow access to the interfaces in the event of a failure/exception.
The architecture shown in
The edge capacity orchestrator 210 may be configured to receive information pertaining to connectivity conditions and resources in the edge site 220. The information may be used to determine whether workloads should be processed at the edge site 220 or whether a workload should be migrated to the data center 200 if there is a pending connectivity event.
A resource manager 214 at the data center 200 may be configured to maintain a list of all resources at the edge site 220, their capabilities, and what workloads are currently running on each resource. The reconciliation system 212 may access this information and identify what areas need to be reconciled when connectivity is resumed after an autonomous event. The performance/billing manager 216 may be configured to track metrics for potential billing to users during autonomous operation.
The functionality provided at the data center 200 and edge site 220 allow for the edge site 220 to operate as a disconnected or autonomous edge site and continue providing services to users serviced by the edge site 220. In an embodiment, the autonomous mode agent 230 determines whether the edge site should enter an autonomous mode in which the edge site operates in a disconnected manner or with otherwise reduced connectivity. The autonomous mode agent 230 may detect loss of connectivity or limited connectivity and automatically cause the edge site 220 to enter the autonomous mode. In an embodiment, the autonomous mode agent 230 may make the determination based on a threshold and a plurality of network metrics. In some embodiments, the autonomous mode may also be entered manually, for example to test features of the autonomous mode. The autonomous mode may also be entered when the edge site is intended to operate autonomously for at least a predetermined period of time.
If the edge site 220 enters autonomous mode due to an unplanned disconnection, the autonomous mode agent 230 may be configured to detect when connectivity is reestablished for a threshold period of time. The edge site 220 may automatically exit the autonomous mode based on the threshold and, in some embodiments, one or more parameters. The parameters may include network metrics, performance characteristics, and other types of parameters.
The autonomous mode agent 230 and performance/billing manager 216 may be configured to provide for management and tracking of the edge site 220 while the edge site is operating in autonomous mode. Management and tracking features of the edge site during autonomous operation may include the ability to modify or reconfigure software and data at the edge site. Additionally, the management and tracking features of the edge site may include the capability to observe and monitor system operation and health while the edge site is operating in autonomous mode. For example, the autonomous mode agent 230 and/or performance/billing manager 216 may monitor logs, metrics, KPIs, and other parameters.
In some embodiments, the edge site 220 may have an autonomous mode buffer 226 to record state data while the edge site 220 is operating in autonomous mode. The local orchestrator 234 may perform buffer management to ensure that data of interest is recorded and at an appropriate frequency and granularity. Data recording can be managed, in particular if the autonomous mode buffer 226 has a finite storage capacity. The local orchestrator 234 may employ various techniques to manage data recording to ensure that the most pertinent data is recorded and persisted. The techniques may include data rotation, automatic data aggregation/adaptation, and other techniques to avoid loss of data from data fall-off, for example if first-in-first-out recording is used.
The local orchestrator 234 may also adhere to a data prioritization scheme to ensure that higher priority data is recorded and persisted. One type of data that may be prioritized is billing data so that key metrics are captured that are used to bill services used at the edge site. For example, for 5G core services, billing may be based on the number of active users using the system, as well as the maximum throughput. Selected metrics may be captured to ensure that, even while in a disconnected state, the service provider can bill for usage. In the 5G core example, the local orchestrator 234 may ensure that the autonomous mode buffer 226 records and tracks the highest rate of both the number of active users using the system and the maximum throughput. Once the edge site is reconnected to the data center, the edge site can send those maximum values to the data center so that billing can be performed correctly. In such cases, when the edge site is to be disconnected for an extended time period, a high watermark may be logged for such parameters in order to avoid consuming storage capacity to continuously log values when the high watermark will suffice.
In some embodiments, the local orchestrator 234 and/or autonomous mode agent 230 may perform scaling of user services to manage capabilities due to reduced or lost connectivity. The local orchestrator 234 and/or autonomous mode agent 230 may further be configured to allow for new deployments while the edge site is disconnected. For example, deployment of new functions or updates to existing functions may be orchestrated by local orchestrator 234 while the edge site 220 is operating in autonomous mode.
In some embodiments, an identity and access manager 236 may perform identity and access management to allow for continued secure access by authorized users to access data and resources while the edge site 220 is operating in autonomous mode. In an embodiment, the identity and access manager 236 may cooperate with local orchestrator 234 and the trust agent 231 so that the edge site 220 locally maintains sufficient functionality and information to identify and authenticate users that have access to applications, data, and systems or networks based on established access rights. For any new connection requests, the identity and access manager 236 may cooperate with trust agent 231 to verify the new connection requests.
In some embodiments, the local orchestrator 234 and/or autonomous mode agent 230 may cooperate with the trust agent 231 to provide backdoor access to the edge site 220. In one embodiment, a backdoor access mechanism may be enabled during autonomous mode to enable authorized users to bypass security measures that may be in place when the edge site 220 is connected to data center 200. The trust agent 231 may ensure that network devices enforce access control at each port. The trust agent 231 may disable network access to unauthorized devices and discard all communications received from the unauthorized devices after an unauthorized physical access has been detected. In some embodiments, communications from a network device that has been subject to unauthorized access can be blocked entirely.
In some embodiments, the autonomous mode agent 230 and trust agent 231 may provide local management of sensitive data including secrets (e.g., certificates, keys). The local autonomous mode agent 230 and trust agent 231 may cooperate with the data center 200 to maintain an updated set of secrets that are securely stored at the edge site 220. The autonomous mode agent 230 and trust agent 231 may further be configured to maintain key/certificate best practices during autonomous operation, including certificate rotation/renewal.
The local orchestrator 234 and/or autonomous mode agent 230 may be configured to provide continuous tracking of resource usage (e.g., for billing purposes) and various metrics to track performance during autonomous operation. This may include selection of key performance data as well as data granularity and frequency.
The local orchestrator 234 and/or autonomous mode agent 230 may be configured to ensure the continued delivery of services to users of the edge site 220, such as the ability to provide device to device communication services.
In an embodiment, the autonomous mode agent 230 and trust agent 231 and/or resource manager agent 232 may cooperate with the trust manager 215 and reconciliation system 212 to provide for a trusted reconciliation and resynchronization process between the data center 210 and edge site 220 when connectivity is restored between the data center 210 and edge site 220. In an embodiment, the trust agent 231 and the trust manager 215 may initiate a process to re-establish trust between the edge site 220 and data center/cloud provider 200.
In various embodiments, reconciliation and resynchronization functionality provided by the local orchestrator 234 and/or autonomous mode agent 230 and/or resource manager agent 232 may include synchronization of states due to local edge state changes which are recorded while the edge site is in autonomous operation.
In an embodiment, local orchestrator 234 and/or autonomous mode agent 230 and/or resource manager agent 232 may cooperate with the reconciliation system 212 and edge capacity orchestrator 210 to perform specific synchronization actions which may be based on the disconnection time frame and parameters associated with the disconnection. For example, disconnects of shorter duration may result in full synchronization of data, whereas disconnects of longer durations that exceed a threshold may result in complete overwrite of the state data using the edge site's data.
In some embodiments, simulation techniques may be implemented to simulate interfaces to the data center 200 as well as other connected interfaces in order to facilitate autonomous operation of the edge site 200. In one embodiment, a digital twin may be implemented at the data center/cloud provider 200 and optionally at the edge site 220 to simulate operation of the edge site and/or the data center while the edge site is in autonomous mode.
In one embodiment, the edge capacity orchestrator 210 may intelligently place tasks and process at one or more edge sites 220 based on capacities, bandwidth, policies, and other inputs. In an embodiment, the local orchestrator 234 may communicate with the edge capacity orchestrator 210 to locally manage containers and other components running at the edge. The local orchestrator 234 and edge capacity orchestrator 210 may collectively monitor and manage available resources such as uplink and downlink capacity and computing capacity prior to the one or more edge sites 220 entering autonomous mode. The local orchestrator 234 may send information to the edge capacity orchestrator 210 that indicates the workload demands and availabilities at the edge. The edge capacity orchestrator 210 may analyze the information and send instructions to the edge sites 220 as to what processes should be run at the edge and if any changes are needed.
Within the confines of instructions provided by the edge capacity orchestrator 210, the local orchestrator 234 may locally manage workloads and other configurations at the edge sites 220 to efficiently utilize the available resources. The capacities at the edge sites 220 may continuously change, for example when new workloads are brought into the edge sites 220 (e.g., from local users at the edge network), and therefore the local compute capacity may change at any time. The local orchestrator 234 may provide the updated capacity information to the edge capacity orchestrator 210 which may generate updated instructions for redistributing workloads at the edge sites 220.
In some embodiments, various workload and other decisions that are made by the edge capacity orchestrator 210 may be delegated to the local orchestrator 234 during autonomous mode.
Referring to
The present disclosure may be implemented in a mobile edge computing (MEC) environment implemented in conjunction with a 4G, 5G, or other cellular network. MEC is a type of edge computing that uses cellular networks and 5G and enables a data center to extend cloud services to local deployments using a distributed architecture that provide federated options for local and remote data and control management. MEC architectures may be implemented at cellular base stations or other edge nodes and enable operators to host content closer to the edge of the network, delivering high-bandwidth, low-latency applications to end users. For example, the cloud provider's footprint may be co-located at a carrier site (e.g., carrier data center), allowing for the edge infrastructure and applications to run closer to the end user via the 5G network.
It should be appreciated that although the embodiments disclosed above are discussed in the context of virtual machines, other types of implementations can be utilized with the concepts and technologies disclosed herein. It should be also appreciated that the network topology illustrated in
Service provider 400 may have various computing resources including servers, routers, and other devices that may provide remotely accessible computing and network resources using, for example, virtual machines. Other resources that may be provided include data storage resources. Service provider 400 may also execute functions that manage and control allocation of network resources, such as a network manager 410.
Network 430 may, for example, be a publicly accessible network of linked networks and may be operated by various entities, such as the Internet. In other embodiments, network 430 may be a private network, such as a dedicated network that is wholly or partially inaccessible to the public. Network 430 may provide access to computers and other devices at the user site 440.
Data center 500 may correspond to cloud provider 100 in
Referring to
Communications network 550 may provide access to computers 505. Computers 505 may be computers utilized by users 500. Computer 505a, 505b or 505c may be a server, a desktop or laptop personal computer, a tablet computer, a smartphone, a set-top box, or any other computing device capable of accessing data center 500. User computer 505a or 505b may connect directly to the Internet (e.g., via a cable modem). User computer 505c may be internal to the data center 500 and may connect directly to the resources in the data center 500 via internal networks. Although only three user computers 505a,505b, and 505c are depicted, it should be appreciated that there may be multiple user computers.
Computers 505 may also be utilized to configure aspects of the computing resources provided by data center 500. For example, data center 500 may provide a Web interface through which aspects of its operation may be configured through the use of a Web browser application program executing on user computer 505. Alternatively, a stand-alone application program executing on user computer 505 may be used to access an application programming interface (API) exposed by data center 500 for performing the configuration operations.
Servers 556 may be configured to provide the computing resources described above. One or more of the servers 556 may be configured to execute a manager 550a or 550b (which may be referred herein singularly as “a manager 550” or in the plural as “the managers 550”) configured to execute the virtual machines. The managers 550 may be a virtual machine monitor (VMM), fabric controller, or another type of program configured to enable the execution of virtual machines 558 on servers 556, for example.
It should be appreciated that although the embodiments disclosed above are discussed in the context of virtual machines, other types of implementations can be utilized with the concepts and technologies disclosed herein.
In the example data center 500 shown in
It should be appreciated that the network topology illustrated in
It should also be appreciated that data center 500 described in
In some embodiments, users 500 may specify configuration information for a virtual network to be provided for the user, with the configuration information optionally including a variety of types of information such as network addresses to be assigned to computing endpoints of the provided computer network, network topology information for the provided computer network, network access constraints for the provided computer network. The network addresses may include, for example, one or more ranges of network addresses, which may correspond to a subset of virtual or private network addresses used for the user's private computer network. The network topology information may indicate, for example, subsets of the computing endpoints to be grouped together, such as by specifying networking devices to be part of the provided computer network, or by otherwise indicating subnets of the provided computer network or other groupings of the provided computer network. The network access constraint information may indicate, for example, for each of the provided computer network's computing endpoints, which other computing endpoints may intercommunicate with the computing node endpoint, or the types of communications allowed to/from the computing endpoints.
With reference to
The edge site 620 may include local trust agent 623, which may be a service running on the edge site 620 and configured to establish and maintain a root of trust at the edge site 620. The trust agent 623 may cooperate with trust manager 643 at cloud provider 640 to establish and maintain trust before the edge site 620 enters autonomous mode, and to re-establish trust after existing autonomous mode and before re-connecting with the cloud provider 640. The trust agent 623 and trust manager 643 may exchange trust data 615.
In one embodiment, a root of trust may be created via the local trust agent 623 through the use of platform integrity techniques such as TPM-based secure boot on at least one trusted device or system 627 operating at the edge site 620. In addition to TPM-based secure boot, other tools such as Public Key Infrastructure (PM) (certificate management) and active directory may be implemented. Certificates may be renewed, and certificates may expire. Active directory may be refreshed by synchronization with a master copy. When entering autonomous mode, a local cache of the certificate and/or active directly information may be used for local authentication, authorization and accounting (AAA) operations. Over time, the edge site may start to lose the initial state of trust as the edge will be unable to renew/refresh the trust data. In response, some functionality at the edge site may be locked down. The trusted device or system 627 may be a selected server and network device such as a switch that is exclusively controlled by the selected server. A chain of trust may be established to authenticate additional devices at the edge site 620 by the trusted device or system 627, such as user devices connected to the remote edge site 620 that may be issued certificates that chain back to the root of trust at trusted device or system 627. The trusted device or system 627 may disable (and by extension network access) to any ports that are connected to unauthorized devices. For example, trusted device or system 627 may execute containers that enforce access control at each port of the trusted network device at the trusted device or system 627.
In an embodiment, the trusted device or system 627 may store a record of any detected attempts to access the edge site 620 by unauthorized devices. The trusted device or system 627 may disable the associated port or discard all communications received from the port after the unauthorized access has been detected. The trusted device or system 627 may provide the record of activity by unauthorized devices in the trust data 615 sent to the trust manager 643 after re-connection. The trust manager 643 may make a determination as to whether the edge site 620 should be trusted based on the trust data 615. The trust manager 643 may also consider additional information such as how long the edge site 620 has been disconnected. For example, disconnects of longer duration may increase the likelihood that the edge site 620 may not be trusted by the trust manager 643. Alternatively, only some of the data provided by the edge site 620 may be trusted by the trust manager 643.
The reconciliation system 644 may run at the cloud provider 640. The reconciliation system 644 may be configured to receive synchronization data 610 pertaining to saved state information for resources at the edge site 620. The synchronization data 610 may be used to determine whether state data from the edge site 620 stored at storage 628 should be synchronized with state data stored at storage 650.
Turning now to
It should be understood by those of ordinary skill in the art that the operations of the methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, performed together, and/or performed simultaneously, without departing from the scope of the appended claims.
It should also be understood that the illustrated methods can end at any time and need not be performed in their entireties. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined herein. The term “computer-readable instructions,” and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.
It should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system such as those described herein) and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. Thus, although the routine 700 is described as running on a system, it can be appreciated that the routine 700 and other operations described herein can be executed on an individual computing device or several devices.
Referring to
Operation 701 may be followed by operation 703. Operation 703 illustrates in response to receiving a first indication of a disconnection or degradation of communications between the computing service provider and the edge computing network, initiating, by the edge computing network, an autonomous mode at the edge computing network. In an embodiment, the autonomous mode enables the edge computing network to continue providing computing and network services at the edge computing network during the disconnection or degradation of communications between the computing service provider and the edge computing network.
Operation 703 may be followed by operation 705. Operation 705 illustrates while the edge computing network is operating in the autonomous mode:
Operation 705 may be followed by operation 707. Operation 707 illustrates storing, by the trusted device, data pertaining to the new devices that attempted to access computing resources in the edge computing network and that were not authorized to access the computing resources in the edge computing network.
Operation 707 may be followed by operation 709. Operation 709 illustrates receiving a second indication of a reconnection or restoration of communications between the computing service provider and the edge computing network.
Operation 709 may be followed by operation 711. Operation 711 illustrates in response to receiving the second indication of the reconnection or restoration of communications between the computing service provider and the edge computing network, sending, by the trusted device to the computing service provider, the stored data pertaining to the new devices that attempted to access computing resources in the edge computing network and that were not authorized to access the computing resources in the edge computing network.
Operation 711 may be followed by operation 713. Operation 713 illustrates in response to receiving the second indication of the reconnection or restoration of communications between the computing service provider and the edge computing network:
The various aspects of the disclosure have been described herein with regard to certain examples and embodiments, which are intended to illustrate but not to limit the disclosure. It should be appreciated that the subject matter presented herein may be implemented as a computer process, a computer-controlled apparatus, a computing system, an article of manufacture, such as a computer-readable storage medium, or a component including hardware logic for implementing functions, such as a field-programmable gate array (FPGA) device, a massively parallel processor array (MPPA) device, a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), a multiprocessor System-on-Chip (MPSoC), etc.
A component may also encompass other ways of leveraging a device to perform a function, such as, for example, a) a case in which at least some tasks are implemented in hard ASIC logic or the like; b) a case in which at least some tasks are implemented in soft (configurable) FPGA logic or the like; c) a case in which at least some tasks run as software on FPGA software processor overlays or the like; d) a case in which at least some tasks run as software on hard ASIC processors or the like, etc., or any combination thereof. A component may represent a homogeneous collection of hardware acceleration devices, such as, for example, FPGA devices. On the other hand, a component may represent a heterogeneous collection of different types of hardware acceleration devices including different types of FPGA devices having different respective processing capabilities and architectures, a mixture of FPGA devices and other types hardware acceleration devices, etc.
In various embodiments, computing device 800 may be a uniprocessor system including one processor 810 or a multiprocessor system including several processors 810 (e.g., two, four, eight, or another suitable number). Processors 810 may be any suitable processors capable of executing instructions. For example, in various embodiments, processors 810 may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x88, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, each of processors 810 may commonly, but not necessarily, implement the same ISA.
System memory 88 may be configured to store instructions and data accessible by processor(s) 810. In various embodiments, system memory 88 may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions and data implementing one or more desired functions, such as those methods, techniques and data described above, are shown stored within system memory 820 as code 825 and data 828.
In one embodiment, I/O interface 830 may be configured to coordinate I/O traffic between the processor 810, system memory 88, and any peripheral devices in the device, including network interface 840 or other peripheral interfaces. In some embodiments, I/O interface 830 may perform any necessary protocol, timing, or other data transformations to convert data signals from one component (e.g., system memory 820) into a format suitable for use by another component (e.g., processor 810). In some embodiments, I/O interface 830 may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface 830 may be split into two or more separate components. Also, in some embodiments some or all of the functionality of I/O interface 830, such as an interface to system memory 820, may be incorporated directly into processor 810.
Network interface 840 may be configured to allow data to be exchanged between computing device 800 and other device or devices 880 attached to a network or network(s) 880, such as other computer systems or devices as illustrated in
In some embodiments, system memory 820 may be one embodiment of a computer-accessible medium configured to store program instructions and data as described above for
Various storage devices and their associated computer-readable media provide non-volatile storage for the computing devices described herein. Computer-readable media as discussed herein may refer to a mass storage device, such as a solid-state drive, a hard disk or CD-ROM drive. However, it should be appreciated by those skilled in the art that computer-readable media can be any available computer storage media that can be accessed by a computing device.
By way of example, and not limitation, computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computing devices discussed herein. For purposes of the claims, the phrase “computer storage medium,” “computer-readable storage medium” and variations thereof, does not include waves, signals, and/or other transitory and/or intangible communication media, per se.
Encoding the software modules presented herein also may transform the physical structure of the computer-readable media presented herein. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the computer-readable media, whether the computer-readable media is characterized as primary or secondary storage, and the like. For example, if the computer-readable media is implemented as semiconductor-based memory, the software disclosed herein may be encoded on the computer-readable media by transforming the physical state of the semiconductor memory. For example, the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. The software also may transform the physical state of such components in order to store data thereupon.
As another example, the computer-readable media disclosed herein may be implemented using magnetic or optical technology. In such implementations, the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.
In light of the above, it should be appreciated that many types of physical transformations take place in the disclosed computing devices in order to store and execute the software components and/or functionality presented herein. It is also contemplated that the disclosed computing devices may not include all of the illustrated components shown in
Although the various configurations have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended representations is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed subject matter.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
While certain example embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions disclosed herein. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of certain of the inventions disclosed herein.
It should be appreciated any reference to “first,” “second,” etc. items and/or abstract concepts within the description is not intended to and should not be construed to necessarily correspond to any reference of “first,” “second,” etc. elements of the claims. In particular, within this Summary and/or the following Detailed Description, items and/or abstract concepts such as, for example, individual computing devices and/or operational states of the computing cluster may be distinguished by numerical designations without such designations corresponding to the claims or even other paragraphs of the Summary and/or Detailed Description. For example, any designation of a “first operational state” and “second operational state” of the computing cluster within a paragraph of this disclosure is used solely to distinguish two different operational states of the computing cluster within that specific paragraph—not any other paragraph and particularly not the claims.
In closing, although the various techniques have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended representations is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed subject matter.
The disclosure presented herein also encompasses the subject matter set forth in the following clauses:
Clause 1: A method for managing a computing network comprising a computing service provider and an edge computing network, the edge computing network comprising computing and storage devices configured to extend computing services of the computing service provider to remote users of the computing service provider, the edge computing networking comprising at least a device designated as a trusted device, the method comprising:
Clause 2: The method of clause 1, further comprising executing a trust agent at the edge computing network, the trust agent configured to store the data pertaining to new devices that attempted to access computing resources in the edge computing network and that were not authorized to access the computing resources in the edge computing network.
Clause 3: The method of any of clauses 1-2, wherein the trust agent is configured to facilitate the storing of the state data.
Clause 4: The method of any of clauses 1-3, further comprising enabling a full set of services at the edge computing network during a first predetermined time period.
Clause 5: The method of any of clauses 1-4, further comprising disabling at least some of the full set of services at the edge computing network during a second predetermined time period.
Clause 6: The method of any of clauses 1-5, further comprising disabling all of the full set of services at the edge computing network after the second predetermined time period.
Clause 7: The method of clauses 1-6, wherein the trust agent is configured to monitor integrity of the edge computing network site while the edge computing network is operating in the autonomous mode.
Clause 8: The method of any of clauses 1-7, wherein the trust agent is configured to monitor local copies of certificates and security related data and ensure that the data is updated at the edge computing network in preparation for the autonomous mode.
Clause 9: An edge computing network configured to extend computing resources of a computing service provider to remote users of the computing service provider, the edge computing network comprising:
Clause 10: The edge computing network of clause 9, further comprising computer-readable instructions stored thereupon that, when executed by the one or more processors, cause the edge computing network to perform operations comprising:
Clause 11: The edge computing network of any of clauses 9 and 10, further comprising computer-readable instructions stored thereupon that, when executed by the one or more processors, cause the edge computing network to perform operations comprising:
Clause 12: The edge computing network of any clauses 9-11, wherein the permission to synchronize state data that was stored by the edge computing network during the autonomous mode with corresponding state data stored at the computing service provider is granted based on a length of time that the edge computing network was operating in the autonomous mode.
Clause 13: The edge computing network of any clauses 9-12, wherein the trust agent is configured to:
Clause 14: A computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by one or more processors of a computing device, cause the computing device to:
Clause 15: The computer-readable storage medium of clause 14, further comprising computer-executable instructions stored which, when executed by one or more processors of a computing device, cause the computing device to activate a backdoor access mechanism configured to enable authorized users to bypass security measures that were be in place prior to the disconnection.
Clause 16: The computer-readable storage medium of any of clauses 14 and 15, further comprising computer-executable instructions stored which, when executed by one or more processors of a computing device, cause the computing device to maintain an updated set of secrets that are securely stored at the edge computing network.
Clause 17: The computer-readable storage medium of any of the clauses 14-16, wherein permission to synchronize state data that was stored by the edge computing network during the autonomous mode with corresponding state data stored at the computing service provider is based on a time frame of the disconnection and parameters associated with the disconnection.
Clause 18: The computer-readable storage medium of any of the clauses 14-17, further comprising computer-executable instructions stored which, when executed by one or more processors of a computing device, cause the computing device to execute a trust agent at the edge computing network, the trust agent configured to store the data pertaining to new devices that were not authorized to access the computing resources in the edge computing network.
Clause 19: The computer-readable storage medium of any of the clauses 14-18, wherein the trust agent is configured to facilitate the storing of the state data.
Clause 20: The computer-readable storage medium of any of the clauses 14-19, wherein the trust agent is configured to monitor integrity of the edge computing network site while the edge computing network is operating in the autonomous mode.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9313299 | Carney | Apr 2016 | B2 |
| 11503119 | Burnett | Nov 2022 | B1 |
| 20180167483 | Cannon | Jun 2018 | A1 |
| 20180247083 | Rizzo | Aug 2018 | A1 |
| 20190109874 | Samuel | Apr 2019 | A1 |
| 20200019931 | Prabhakar | Jan 2020 | A1 |
| 20200142735 | Maciocco | May 2020 | A1 |
| 20200153623 | Asanghanwa | May 2020 | A1 |
| 20210144517 | Guim Bernat et al. | May 2021 | A1 |
| 20210158975 | Turney | May 2021 | A1 |
| 20220385488 | Kothuri | Dec 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 112448858 | Mar 2021 | CN |
| Entry |
|---|
| Echeverría, “Establishing Trusted Identities in Disconnected Edge Environments”, In proceedings of IEEE/ACM Symposium on Edge Computing (SEC), Oct. 27, 2016, pp. 51-62. |
| “International Search Report and Written Opinion Issued in PCT Application No. PCT/US23/019189”, Mailed Date: Jul. 24, 2023, 15 Pages. |
| Ren, et al., “A Survey on End-Edge-Cloud Orchestrated Network Computing Paradigms”, In journal of ACM Computing Surveys, vol. 52, Issue 6, Oct. 16, 2019, pp. 1-36. |
| Number | Date | Country | |
|---|---|---|---|
| 20230388309 A1 | Nov 2023 | US |
