Transferral of process state and/or components in computing environments

US11755364B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11755364-B2
Application numberUS-202117331177-A
CountryUS
Kind codeB2
Filing dateMay 26, 2021
Priority dateApr 4, 2019
Publication dateSep 12, 2023
Grant dateSep 12, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

This technology relates to transferring state information between processes or active software programs in a computing environment where a new instance of a process or software program may receive such state information even after an original or old instance of the process or software program that owned the state information has terminated either naturally or unnaturally.

First claim

Opening claim text (preview).

The invention claimed is: 1. A computing system, comprising: one or more computing devices including an operating system (OS) function, wherein the OS function is configured to: receive a first notification indicating that an update associated with a first process is available; in response to receiving the first notification: instantiate a second process, the second process being a new instance of the first process configured to replace the first process; and send a second notification to the first process indicating that the update is available, to cause the first process to capture state information, the state information including one or more resources established in running the first process; receive the state information captured by the first process; provide the state information to the second process such that the state information is available for operation of the second process in accordance with the update; and either: when the update is compatible with the state information provided to the second process, receive a notification from the second process that the update is ready, and when the state information has not changed, terminate the first process; or when the update is not compatible with the state information provided to the second process, receive a notification from the second process that the update is not compatible with the state information and terminate the second process. 2. The computing system of claim 1 , further comprising at least one memory device operatively coupled to the one or more computing devices, wherein the OS function stores state information associated with the first process in the at least one memory device upon receiving a system call. 3. The computing system of claim 1 , wherein the one or more resources include at least one of one or more handles, one or more threads or one or more memory objects. 4. The computing system of claim 1 , wherein the OS function is further configured to receive a request to recover the state information from the second process. 5. The computing system of claim 1 , wherein the OS function is further configured to determine whether or not the second process is authorized to receive the state information. 6. The computing system of claim 5 , wherein the OS function is further configured to transfer the state information to the second process when the OS function determines that the second process is authorized to receive the state information. 7. The computing system of claim 5 , wherein the OS function is further configured to deny the second process access to the state information when the OS function determines that the second process is not authorized to receive the state information. 8. The computing system of claim 1 , wherein the first process is currently running or active. 9. The computing system of claim 1 , wherein the first process suspends work in response to the first process receiving the first notification. 10. A method of updating a process using an operating system (OS) function in a computing system, the method comprising: receiving, by the OS function, a first notification indicating that an update associated with a first process is available; in response to receiving the first notification: instantiating, by the OS function, a second process, the second process being a new instance of the first process configured to replace the first process; and sending, by the OS function, a second notification to the first process indicating that the update is available, to cause the first process to capture state information, the state information including one or more resources established in running the first process; receiving, by the OS function, the state information captured by the first process; providing, by the OS function, the state information to the second process such that the state information is available for operation of the second process in accordance with the update; and either: when the update is compatible with the state information provided to the second process, receiving a notification from the second process that the update is ready, and when the state information has not changed, terminating the first process; or when the update is not compatible with the state information provided to the second process, receiving a notification from the second process that the update is not compatible with the state information and terminating the second process. 11. The method of claim 10 , further comprising: receiving, by the OS function, a system call; and in response to the system call, storing, by the OS function, state information associated with the first process in at least one memory device in communication with the OS function. 12. The method of claim 10 , wherein the one or more resources include at least one of one or more handles, one or more threads or one or more memory objects. 13. The method of claim 10 , further comprising receiving, by the OS function, a request to recover the state information from the second process. 14. The method of claim 10 , further comprising verifying, by the OS function, that the second process is authorized to receive the state information. 15. The method of claim 14 , further comprising transferring, by the OS function, the state information to the second process when the OS function verifies that the second process is authorized to receive the state information. 16. The method of claim 10 , further comprising denying, by the OS function, the second process access to the state information when the OS function is unable to verify the second process as being allowed to receive the state information. 17. A computing device, comprising: an operating system (OS) function; and a non-transitory computer-readable medium having instructions stored thereon that, when executed by the OS function, cause the OS function to perform operations comprising: receiving a first notification indicating that an update associated with a first process is available; in response to receiving the first notification: instantiating a second process, the second process being a new instance of the first process configured to replace the first process; and sending a second notification to the first process indicating that the update is available, to cause the first process to capture state information, the state information including one or more resources established in running the first process; receiving the state information captured by the first process; providing the state information to the second process such that the state information is available for operation of the second process in accordance with the update; and either: when the update is compatible with the state information provided to the second process, receiving a notification from the second process that the update is ready, and when the state information has not changed, terminating the first process; or when the update is not compatible with the state information provided to the second process, receiving a notification from the second process that the update is not compatible with the state information and terminating the second process. 18. The computing device of claim 17 , wherein the one or more resources include at least one of one or more handles, one or more threads or one or more memory objects. 19. The computing device of claim 17 , wherein the OS function is further configured to receive a request to recover the state information from the second process. 20. The computing device of claim

Assignees

Inventors

Classifications

  • G06F9/54Primary

    Interprogram communication · CPC title

  • G06F9/4843Primary

    by program, e.g. task dispatcher, supervisor, operating system · CPC title

  • Program initiating; Program switching, e.g. by interrupt · CPC title

  • while running · CPC title

  • during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow} · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11755364B2 cover?
This technology relates to transferring state information between processes or active software programs in a computing environment where a new instance of a process or software program may receive such state information even after an original or old instance of the process or software program that owned the state information has terminated either naturally or unnaturally.
Who is the assignee on this patent?
Google Llc
What technology area does this patent fall under?
Primary CPC classification G06F9/54. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 12 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).