US2019196882A1PendingUtilityA1
Configurable Platform Architecture And Method For Use Thereof
Est. expiryAug 22, 2032(~6.1 yrs left)· nominal 20-yr term from priority
G06F 9/541G06F 9/4843G06F 9/542
57
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
A platform architecture that is configurable to provide task specific application instances compatible with one or more hosts is provided with a method for using the architecture. In one example, the platform architecture provides a transducer functionality block, a conduit functionality block, an application functionality block, and an application programming interface (API) functionality block on which each task specific application instance is based.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A platform architecture that is configurable to provide task specific application instances compatible with one or more hosts, wherein the platform architecture provides a transducer functionality block, a conduit functionality block, an application functionality block, and an application programming interface (API) functionality block on which each task specific application instance is based, the platform architecture comprising:
computer-executable instructions for providing the transducer functionality block and for configuring the transducer functionality block to provide transducer threads needed for the task specific application instance, wherein a transducer thread is adapted to receive input signals of a specified type in real time from a signal source, generate signal objects representing the input signals if the input signals are not already signal objects, wherein a signal object is an object structure that can be handled by the conduit functionality block and the application functionality block, and asynchronously publish the signal objects to at least one of the conduit functionality block and the application functionality block; computer-executable instructions for providing the conduit functionality block and for configuring the conduit functionality block to dynamically allocate conduits needed for the task specific application instance, wherein a conduit is a queue that receives signal objects of a particular type from at least one of a transducer, the application functionality block, and the API functionality block, and queues the signal objects for consumption by at least one of the transducer functionality block, the application functionality block, and the API functionality block; computer-executable instructions for providing the application functionality block and for configuring the application functionality block to receive signal objects from at least one of a conduit and a transducer, process the signal objects based on at least one script that is specifically adapted to perform processing needed for the task specific application instance, and perform an action based on the processing, wherein no storage of an input signal or a signal object that corresponds to the input signal occurs from the time the input signal is received until the action is performed except for queuing; and computer-executable instructions for providing the API functionality block, wherein the API functionality block provides an interface for sending signal objects to and receiving signal objects from the conduit functionality block, and wherein the transducer threads and the script are started and stopped via the API functionality block.
2 . The platform architecture of claim 1 wherein processing a signal object includes adding dynamic context to the signal object based on at least one of a time criterion, a space criterion, and a state criterion.
3 . The platform architecture of claim 2 wherein adding dynamic context is performed by at least one of a pre-adapter, a dynamic context block, a post-adaptor, and an action in the application functionality block.
4 . The platform architecture of claim 3 wherein the pre-adapter block is executed before any dynamic context block is executed and the post-adapter block is executed after any dynamic context block is executed.
5 . The platform architecture of claim 3 wherein both the pre-adaptor block and the post-adaptor block are adaptable to generate a new signal object based on an existing signal object.
6 . The platform architecture of claim 1 wherein the conduit functionality block is managed via a management conduit that is configured to de-allocate a signal object from a conduit if neither the application functionality block nor the API functionality block have subscribed to the conduit.
7 . The platform architecture of claim 6 wherein the management conduit is further configured to de-allocate a conduit if the conduit is not associated with a transducer, the application functionality block, or the API functionality block.
8 . The platform architecture of claim 6 wherein the management conduit is further configured to allocate a conduit for signal objects of a specified type if needed by at least one of a transducer, the application functionality block, and the API functionality block, and if a conduit is not currently allocated for signal objects of that specified type.
9 . The platform architecture of claim 1 wherein the application functionality block is further configured to generate a new signal object upon the occurrence of a specified condition, wherein the new signal object is associated within the application functionality block with an existing signal object generated by the transducer functionality block.
10 . The platform architecture of claim 9 wherein the application functionality block is further configured to de-allocate the existing signal object.
11 . A platform architecture that is configurable to provide customized application instances via one or more hosts, the platform architecture comprising:
computer-executable instructions for providing a transducer functionality block having input functionality and for configuring the transducer functionality block to receive input signals of a particular type in real time from a signal source, generate signal objects representing the input signals if the input signals are not already signal objects, and asynchronously publish the signal objects within an application instance; computer-executable instructions for providing a conduit functionality block having queuing functionality and for configuring the conduit functionality block to receive published signal objects of a specified type and queue the signal objects for consumption within the application instance in at least one dynamically allocated queue; computer-executable instructions for providing an application functionality block having processing functionality and for configuring the application functionality block to receive signal objects from the queue, process the signal objects based on defined processing instructions specifically adapted for the application instance, and perform an action based on the processing, wherein no storage of an input signal or a signal object that corresponds to the input signal occurs from the time the input signal is received from the signal source until the action is performed except for queuing; and computer-executable instructions for providing an application programming interface (API) functionality block configured to start and stop the transducer functionality block and the application functionality block.
12 . The platform architecture of claim 11 wherein the host is at least one of a device, a network router, a network switch, a cloud, and a hybrid host architecture.
13 . The platform architecture of claim 12 wherein the device is at least one of a single-board computing (SBC) platform, an onboard computing (OBC) platform, a cellular telephone, a personal digital assistant (PDA), a netbook, a tablet, a laptop, a desktop, a workstation, and a server.
14 . The platform architecture of claim 12 wherein the device is part of a system.
15 . The platform architecture of claim 11 wherein the computer-executable instructions for providing and configuring the transducer functionality block, the conduit functionality block, the application functionality block, and the API functionality block are operating system neutral.
16 . The platform architecture of claim 11 wherein the application instance is configured to provide self-awareness by monitoring a current state of the host.
17 . The platform architecture of claim 11 wherein the application instance is configured for installation as an application on the host.
18 . The platform architecture of claim 11 wherein the application instance is configured for embedding in the host.
19 . The platform architecture of claim 11 wherein the application instance is configured for distribution between at least two hosts.
20 . A method for processing a plurality of input signals by a platform operating on a network accessible host, wherein the platform includes a transducer, an input conduit, an application, and an output conduit, the method comprising:
receiving, by the transducer, a plurality of input signals from a source external to the platform, wherein the input signals are received in real time from the source; generating, by the transducer, a new signal object for each of the input signals; publishing, by the transducer, the signal objects to the input conduit, wherein the input conduit is configured to receive signal objects having a type corresponding to the generated signal objects and is subscribed to the transducer; maintaining, by the input conduit, the signal objects until the signal objects are removed from the input conduit by the application, wherein the application is subscribed to the conduit; removing, by the application, the signal objects from the conduit; adding, by the application, dynamic context to the signal objects to identify a set of specified signal objects, wherein all signal objects not in the set of specified signal objects are discarded; processing, by the application, the set of specified signal objects based on at least one of a time criterion, a space criterion, and a state criterion; and sending, by the application, an output signal to the output conduit, wherein the output signal is based on the processing of the set of specified signal objects, and wherein no storage of an input signal or a signal object occurs from the time the input signal is received from the source until the output signal is sent except for queuing needed to maintain the signal objects by the input conduit.Join the waitlist — get patent alerts
Track US2019196882A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.