US2018349154A1PendingUtilityA1
System and method for configuring a platform instance at runtime
Est. expiryMar 23, 2035(~8.7 yrs left)· nominal 20-yr term from priority
G06F 8/656G06F 11/1438G06F 8/36G06F 9/44505G06F 1/24
51
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
An improved system and method are disclosed for configuring a platform instance at runtime using predefined configuration information and contexts that contain at least a portion of the predefined configuration information and also contain dynamically generated information that is not available until the platform instance is started. A core server of the platform instance is started and configured, contexts are created, and services and blocks are started and configured using the contexts.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method for configuring a platform instance at runtime, the method comprising:
configuring, by a core process of a platform instance running on a digital device and interacting with an operating system of the digital device, a core server for the platform instance using a predefined core configuration file; creating, by the core server, a core initialization context (CIC) that contains dynamically generated information about the platform instance, wherein the dynamically generated information only becomes available during configuration of the core server; creating, by the core server, a service initialization context (SIC) for a service that is to be run as part of the platform instance, wherein the SIC includes service configuration information from a predefined service configuration file and the CIC; configuring the service for operation within the platform instance using the service configuration information in the SIC; creating a block initialization context (BIC) for a block that is to be used to provide task specific functionality for the service, wherein the BIC includes block configuration information from a predefined block configuration file and the SIC; and configuring the block for operation within the service using the block configuration information in the BIC.
2 . The method of claim 1 further comprising:
creating a block router initialization context (BRIC); and
configuring a block router for the service using the BRIC so that the block router can route data between the block and at least one other block that is part of the service.
3 . The method of claim 1 further comprising:
starting, by the core server, at least one module that is capable of providing functionality to the service;
configuring the module using a predefined module configuration file, wherein the configuring generates module-specific information; and
updating the CIC with at least a portion of the module-specific information.
4 . The method of claim 3 further comprising:
detecting, by the core server, whether the service needs the functionality provided by the module; and
adding at least a portion of the module-specific information in the CIC to the SIC only if the service needs the functionality provided by the module.
5 . The method of claim 3 further comprising:
starting, by the core server, at least one core component of the core server;
configuring the core component using information from the CIC, wherein the configuring generates core component-specific information; and
updating the CIC with at least a portion of the core component-specific information.
6 . The method of claim 5 wherein the core component is configured after the CIC is updated with the module-specific information.
7 . The method of claim 1 wherein the SIC contains all the information sent to the service by the core server and contains all information about the platform instance needed by the service to operate.
8 . The method of claim 1 further comprising:
shutting down the service by the core server, wherein the core server continues running after shutting down the service; and
re-launching the service by the core server, wherein re-launching the service includes
creating a new SIC for the service;
configuring the service using the new SIC;
creating a new BIC for the block; and
configuring the block using the new BIC.
9 . The method of claim 8 further comprising:
pausing the service by the core server, wherein the service is paused with a first configuration; and
restarting the service by the core server after the service has been paused, wherein the service maintains the first configuration after being restarted.
10 . The method of claim 1 further comprising:
generating, within a configuration environment that is separate from the platform instance, the core configuration file, the service configuration file, and the block configuration file; and
making the core configuration file, the service configuration file, and the block configuration file accessible to the core process prior to configuring the core server.
11 . The method of claim 1 further comprising passing the SIC to the service, wherein the step of configuring the service for operation is performed by the service.
12 . The method of claim 1 further comprising passing the BIC to the block, wherein the step of configuring the block for operation is performed by the block.
13 . A method for configuring a platform instance at runtime, the method comprising:
configuring a core process of a platform instance using a core configuration file, wherein the core process is run on a digital device and interacts with an operating system of the digital device; creating, by the core process, a module context for at least one module; creating, by the core process, a service initialization context (SIC) for a service to be started by the core process, wherein the SIC includes information from the module context and a service configuration file corresponding to the service; launching, by the core process, the service; passing, by the core process, the SIC to the service; configuring, by the service, the service using the SIC; creating, by the service, a block initialization context (BIC) for each of a plurality of blocks to be used by the service, wherein each BIC includes information from the SIC and a block configuration file corresponding to the block for which the BIC is being created; launching, by the service, the plurality of blocks; passing, by the service, to each block the BIC corresponding to the block; configuring, by each block, the block using the BIC; creating, by the service process, a block router initialization context (BRIC); passing the BRIC to a block router of the service; and configuring, by the block router, the block router using the BRIC so that the block router can transfer information between the blocks.
14 . A system comprising:
a processor; and a memory coupled to the processor and containing instructions for execution by the processor, the instructions for:
launching a core process of a platform instance, wherein the core process is launched by the processor using an operating system stored in the memory;
configuring, by the core process, a core server for the platform instance using a predefined core configuration file;
creating, by the core server, a core initialization context (CIC) that contains dynamically generated information about the platform instance, wherein the dynamically generated information only becomes available during configuration of the core server;
creating, by the core server, a service initialization context (SIC) for a service that is to be run as part of the platform instance, wherein the SIC includes service configuration information from a predefined service configuration file and the CIC;
configuring the service for operation within the platform instance using the service configuration information in the SIC;
creating a block initialization context (BIC) for a block that is to be used to provide task specific functionality for the service, wherein the BIC includes block configuration information from a predefined block configuration file and the SIC; and
configuring the block for operation within the service using the block configuration information in the BIC.
15 . The system of claim 14 wherein the instructions further include instructions for:
creating a block router initialization context (BRIC); and
configuring a block router for the service using the BRIC so that the block router can route data between the block and at least one other block that is part of the service.
16 . The system of claim 14 wherein the instructions further include instructions for:
starting, by the core server, at least one module that is capable of providing functionality to the service;
configuring the module using a predefined module configuration file, wherein the configuring generates module-specific information; and
updating the CIC with at least a portion of the module-specific information.
17 . The system of claim 16 wherein the instructions further include instructions for:
detecting, by the core server, whether the service needs the functionality provided by the module; and
adding at least a portion of the module-specific information in the CIC to the SIC only if the service needs the functionality provided by the module.
18 . The system of claim 16 wherein the instructions further include instructions for:
starting, by the core server, at least one core component of the core server;
configuring the core component using information from the CIC, wherein the configuring generates core component-specific information; and
updating the CIC with at least a portion of the core component-specific information.
19 . The system of claim 18 wherein the core component is configured after the CIC is updated with the module-specific information.
20 . The system of claim 14 wherein the SIC contains all the information sent to the service by the core server and contains all information about the platform instance needed by the service to operate.Join the waitlist — get patent alerts
Track US2018349154A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.