Attestation token sharing in edge computing environments
US-2020084202-A1 · Mar 12, 2020 · US
US12095844B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12095844-B2 |
| Application number | US-202017069809-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 13, 2020 |
| Priority date | Oct 13, 2020 |
| Publication date | Sep 17, 2024 |
| Grant date | Sep 17, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, apparatus, systems and articles of manufacture for re-use of a container in an edge computing environment are disclosed. An example method includes detecting that a container executed at an edge node of a cloud computing environment is to be cleaned, deleting user data from the container, the deletion of the user data performed without deleting the container from the memory of the edge node, restoring settings of the container to a default state; and storing information identifying the container, the information including a flavor of the container, the storing of the information to enable the container to be re-used by a subsequent requestor.
Opening claim text (preview).
What is claimed is: 1. An apparatus for re-use of containers, the apparatus comprising: memory including machine-readable instructions; at least one processor to execute the machine readable instructions to at least: detect that a container executed at an edge node of a cloud computing environment is to be cleaned; delete user data from the container, the deletion of the user data performed without deleting the container from the memory of the edge node; restore settings of the container to a default state; and store information identifying the container, the information including a flavor of the container, the storing of the information to enable the container to be re-used by a subsequent requestor. 2. The apparatus of claim 1 , wherein the processor is further to, in response to detection of a subsequent request to access the container: identify the container based on a flavor identifier included in the subsequent request; and provide access to the container. 3. The apparatus of claim 2 , wherein the processor is further to, in response to the subsequent request requesting identity validation of the container, generate a proof of identity of the container. 4. The apparatus of claim 2 , wherein the processor is further to, in response to the subsequent request requesting validation of data stored in the container, validate the data stored in the container. 5. The apparatus of claim 1 , wherein the processor is further to detect that the container is to be cleaned in response to an indication that use of the container is complete. 6. The apparatus of claim 1 , wherein the processor is further to detect that the container is to be cleaned in response to a threshold amount of time since the container was last used having elapsed. 7. At least one non-transitory computer readable storage medium comprising instructions that, when executed, cause at least one processor to at least: detect that a container executed at an edge node of a cloud computing environment is to be cleaned; delete user data from the container, the deletion of the user data performed without deleting the container from a memory of the edge node; restore settings of the container to a default state; and store information identifying the container, the information including a configuration of the container, the storing of the information to enable the container to be re-used by a subsequent requestor. 8. The at least one non-transitory computer readable storage medium of claim 7 , wherein the processor is further to, in response to detection of a subsequent request to access the container: identify the container based on a configuration identifier included in the subsequent request; and provide access to the container. 9. The at least one non-transitory computer readable storage medium of claim 8 , wherein the processor is further to, in response to the subsequent request requesting identity validation of the container, generate a proof of identity of the container. 10. The at least one non-transitory computer readable storage medium of claim 8 , wherein the processor is further to, in response to the subsequent request requesting validation of the data stored in the container, validate data stored in the container. 11. The at least one non-transitory computer readable storage medium of claim 7 , wherein the processor is further to detect that the container is to be cleaned in response to an indication that use of the container is complete. 12. The at least one non-transitory computer readable storage medium of claim 7 , wherein the processor is further to detect that the container is to be cleaned in response to a threshold amount of time since the container was last used having elapsed. 13. A method for re-use of containers, the method comprising: detecting that a container executed at an edge node of a cloud computing environment is to be cleaned; deleting user data from the container, the deletion of the user data performed without deleting the container from a memory of the edge node; restoring settings of the container to a default state; and storing information identifying the container, the information including a flavor of the container, the storing of the information to enable the container to be re-used by a subsequent requestor. 14. The method of claim 13 , further including, in response to detection of a subsequent request to access the container: identifying the container based on a flavor identifier included in the subsequent request; and providing access to the container. 15. The method of claim 14 , further including, in response to the subsequent request requesting identity validation of the container, generating a proof of identity of the container. 16. The method of claim 14 , further including, in response to the subsequent request requesting validation of data stored in the container, validating the data stored in the container. 17. The method of claim 13 , wherein the detecting that the container is to be cleaned is performed in response to an indication that use of the container is complete. 18. The method of claim 13 , wherein the detecting that the container is to be cleaned is performed in response to a threshold amount of time since the container was last used having elapsed. 19. An apparatus for re-use of containers, the apparatus comprising: means for detecting that a container executed at an edge node of a cloud computing environment is to be cleaned; and means for cleaning to delete user data from the container, the deletion of the user data performed without deleting the container from a memory of the edge node, the means for cleaning to restore settings of the container to a default state, the means for cleaning to store information identifying the container, the information including a flavor of the container, the storing of the information to enable the container to be re-used by a subsequent requestor. 20. The apparatus of claim 19 , wherein the means for detecting is further to, in response to detection of a subsequent request to access the container: identify the container based on a flavor identifier included in the subsequent request; and provide access to the container. 21. The apparatus of claim 20 , further including means for attesting to, in response to the subsequent request requesting identity validation of the container, generate a proof of identity of the container. 22. The apparatus of claim 20 , further including means for attesting to, in response to the subsequent request requesting validation of data stored in the container, validate the data stored in the container. 23. The apparatus of claim 19 , wherein the means for detecting is to detect that the container is to be cleaned in response to an indication that use of the container is complete. 24. The apparatus of claim 19 , wherein the means for detecting is to detect that the container is to be cleaned in response to a threshold amount of time since the container was last used having elapsed.
Policies or rules for updating, deleting or replacing the stored data · CPC title
Hypervisor-specific management and integration aspects · CPC title
Network integration; Enabling network access in virtual machine instances · CPC title
Creating, deleting, cloning virtual machine instances · CPC title
Monitoring or debugging support · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.