An operating system may be configured using a control flow graph that defines relationships between each executable module. The operating system may be configured by analyzing an application and identifying the operating system modules called from the application, then building a control flow graph for the configuration. The operating system may be deployed to a server or other computer containing only those components identified in the control flow graph. Such a lightweight deployment may be used on a large scale for datacenter servers as well as for small scale deployments on sensors and other devices with little processing power.

Claims

17 · 3 independent · depth 4

17 granted claims

›1.independentA method executed in a computer comprising a memory and a processor, comprising:nby the computer, determining a functionality to provide to a target d…+9

›2.↳ 1The method of claim 1, said control flow graph comprising executable elements from a plurality of application functions.d2+2

›5.↳ 1The method of claim 1 further comprising:nconfiguring said executable package for execution on said target device.d2+1

›7.↳ 1The method of claim 1 further comprising:nreceiving a request for executable code from said target device; andtransmitting said executable package to …d2+1

›9.↳ 1The method of claim 1 further comprising:nreceiving a first application, said first application comprising operating system calls;creating a first con…d2

›10.↳ 1The method of claim 1, wherein determining a feature set to enable the functionality comprises determining that the application is not capable of deco…d2

›11.independentA computer system comprising a processor and a memory, the computer system comprising instructions, which, when executed by the processor, configure i…+3

›15.independentA method executed in a computer comprising a memory and a processor, comprising:nby the computer, receiving a request for executable code from a targe…+2

Classifications

2 codes

IPC · International Patent Classification

Section G — Physics

G06F9/45
G06F9/445

Claim changes

Soon

Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this patent are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoom

USPTOApplicanthover for detail · click to open

Pendency

2.3 y

846 days filing → grant

Office actions

non-final + final

Responses

1 RCE

Examiner

Philip Wang

art unit 2197 · TC 2100

Law firm

Law firm · Log in to unlock

Citations: 33 back · 0 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Term & fees

See the term timeline — pendency span, in-force span, the maintenance fees paid and both computed expiry dates.

Priority chain

1 priority documents

›Priority documents — 1

Type	Document	Date
related publication	US 20130298112 A1	7 Nov 2013

Validity challenges

See the validity challenges on record — reexaminations, IPRs and PGRs, with their institution decisions and outcomes.

Citations

See every patent this one cites and every patent that cites it back — publication, assignee, and how each one was found.