Resource management system featuring a sensor-agnostic software architecture

A computer-implemented method comprising:

• at least one client configured to perform at least one task corresponding to a given program component;
• a sensor domain;
• and
• providing a plurality of program components comprising:
• one or more sensor-agnostic components preestablished, wherein each sensor-agnostic component is configured to be independent of the sensor domain and one or more sensor-specific components included in the sensor domain, the one or more sensor-agnostic components including the at least one controller configured to execute the plurality of program components over a chosen sensor domain;
• the one or more sensor-specific components preestablished and being a separate and individual component from the one or more sensor-agnostic components, wherein each sensor-specific component is customizable for use with the chosen sensor domain;
• and
• a base subsystem manager (SSM) class configured to be instantiated into a first SSM for a first subsystem comprising one or more resources, wherein the first SSM is in signal communication with the at least one controller, and wherein at least one of the one or more resources of the first subsystem is an electronic sensor in signal communication with the at least one controller;
• and
• combining at least a subset of the one or more sensor-agnostic components and the one or more sensor-specific components into a program;
• wherein the one or more sensor-agnostic components and the one or more sensor-specific components are configured to interconnect in a plurality of combinations,
• wherein the one or more sensor-agnostic components further include a resource scheduler and allocator (RSA) in signal with the at least one controller and configured to communicate with the base SSM class to allocate a plurality of sensors in scheduling resource requests of each SSM instantiated from the base SSM class, to allot time on each sensor included in the scheduling resource requests, and to configure the sensor to perform sensor operation responsive to the schedule resource requests,
• wherein the one or more sensor-specific components comprise a first subsystem (SM) adapter configured to translate communications between the first SSM and the first subsystem, wherein the first SM adapter is customizable by a user to utilize native communications of the first subsystem,
• wherein the at least one client outputs at least one sensor request to at least one sensor among the plurality of sensors, and wherein the RSA receives the at least one sensor request, allots the time on the at least one sensor corresponding to the sensor request, and configures the at least one sensor to perform the sensor operations necessary for the client to perform the at least one task.

A Multi-Function Sensor System (MFSS) comprising:

• at least one client configured to perform at least one task corresponding to a given program component;
• a sensor domain;
• and
• an interface enabling access to a plurality of program components and enabling selection and combination of the plurality of program components to form a program, the plurality of program components comprising:
• one or more sensor-agnostic components preestablished, wherein each sensor-agnostic component is configured to be independent of the sensor domain and one or more sensor-specific components included in the sensor domain, the one or more sensor-agnostic components including the at least one controller configured to execute the plurality of program components over a chosen sensor domain;
• the one or more sensor-specific components preestablished and being a separate and individual component from the one or more sensor-agnostic components, wherein each sensor-specific component is customizable for use with the chosen sensor domain;
• and
• a base subsystem manager (SSM) class configured to be instantiated into a first SSM for a first subsystem comprising one or more resources, wherein the first SSM is in signal communication with the at least one controller, and wherein at least one of the one or more resources of the first subsystem is an electronic sensor in signal communication with the at least one controller;
• wherein the one or more sensor-agnostic components and the one or more sensor-specific components are configured to interconnect in a plurality of combinations,
• wherein the one or more sensor-agnostic components further include a resource scheduler and allocator (RSA) in signal with the at least one controller and configured to communicate with the base SSM class to allocate a plurality of sensors in scheduling resource requests of each SSM instantiated from the base SSM class, to allot time on each sensor included in the scheduling resource requests, and to configure the sensor to perform sensor operation responsive to the schedule resource requests,
• wherein the one or more sensor-specific component comprise a first subsystem (SM) adapter configured to translate communications between the first SSM and the first subsystem, wherein the first SM adapter is customizable by a user to utilize native communications of the first subsystem,
• wherein the at least one client outputs at least one sensor request to at least one sensor among the plurality of sensors, and wherein the RSA receives the at least one sensor request, allots the time on the at least one sensor corresponding to the sensor request, and configures the at least one sensor to perform the sensor operations necessary for the client to perform the at least one task.