EP1535148A1 - Systeme et procede de generation automatique d'un reseau automatise de capteurs - Google Patents

Systeme et procede de generation automatique d'un reseau automatise de capteurs

Info

Publication number
EP1535148A1
EP1535148A1 EP03763139A EP03763139A EP1535148A1 EP 1535148 A1 EP1535148 A1 EP 1535148A1 EP 03763139 A EP03763139 A EP 03763139A EP 03763139 A EP03763139 A EP 03763139A EP 1535148 A1 EP1535148 A1 EP 1535148A1
Authority
EP
European Patent Office
Prior art keywords
component
components
application software
software
system recited
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP03763139A
Other languages
German (de)
English (en)
Other versions
EP1535148A4 (fr
Inventor
Minakshisundaran B. Anand
Rajesh Thakkar
Prakash R. Chakravarthi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cooper Technologies Co
Original Assignee
Eka Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Eka Systems Inc filed Critical Eka Systems Inc
Publication of EP1535148A1 publication Critical patent/EP1535148A1/fr
Publication of EP1535148A4 publication Critical patent/EP1535148A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0426—Programming the control sequence
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/23—Pc programming
    • G05B2219/23293—Automated assembly of machine control software, reusable software components

Definitions

  • This invention relates, in general, to sensor networking applications and, in particular, to the automatic generation of all the components of a sensor networking system to suit a particular application.
  • the application software is automatically constructed using a common framework that allows multiple components to co-exist and co-operate.
  • Each component is provided with standard interfaces that allow it plug into the framework. Further, such standard interfaces can also be automatically constructed given a functional software core.
  • Each component is also provided with a shell that contains metric information, thus allowing the calculation of performance metrics. The shell can be stripped from components when the application software is constructed to eliminate resource waste.
  • the present invention is a system for automatically generating an application software unit.
  • the system includes a component repository comprising one or more components.
  • An application framework stores parameter information regarding how the application software unit is to be built and operate.
  • the system includes an application composer that uses information in the application framework to extract one or more components from the component registry and configure the one or more components according to the information in the application framework to generate the application software unit.
  • the present invention is a method for automatically generating an application software unit.
  • the method begins with the step of receiving values of one or more configurable parameters.
  • the method continues with the step of extracting one or more components from a component registry in accordance with the received values.
  • the method then continues with the step of combining the components with an application framework to generate the application software component.
  • the present invention is a system for automatically generating an application software unit.
  • the system includes means for receiving values of one or more configurable parameters and means for extracting one or more components from a component registry in accordance with the received values.
  • the system also includes means for combining the components with an application framework to generate the application software component.
  • Fig. 1 is a schematic diagram of a network of actuators and/or sensors using automatically generated application software units according to an embodiment of the present invention.
  • Fig. 2 is a schematic diagram of a common structure for constructing application software units according to an embodiment of the present invention.
  • Fig. 3 a is a schematic diagram of a structure allowing components in an application software unit to interact according to one embodiment of the present invention.
  • Fig. 3b is a schematic diagram of a structure allowing components in an application software unit to interact according to another embodiment of the present invention.
  • Fig. 4 is a schematic diagram of a system for automatically generating software application units according to an embodiment of the present invention.
  • Fig. 20 Fig.
  • FIG. 5 is a schematic diagram of a component as stored in a component repository according to an embodiment of the present invention.
  • Fig. 6 is a flow chart for automatically generating a software component according to an embodiment of the present invention.
  • Fig. 7 is a schematic diagram of a system for automatically generating test scripts according to an embodiment of the present invention.
  • Fig. 8 is a schematic diagram of a system for generating components to store in a component registry according to an embodiment of the present invention.
  • Fig. 1 shows the conceptual diagram of a sensor or actuator network.
  • the dark circles in the figure denote sensor or actuator nodes and the bi-directional arrows indicate bi-directional communication channels.
  • the automatically generated executable application software 100 comprises three units: an executable software unit 101 resident on embedded sensor or actuator nodes, an executable software unit 102 resident on gateways which collect data from or control the operation of a plurality of said sensor nodes, and an executable software unit 103 resident on a server which collects data from or controls the operation of a plurality of said gateways.
  • the software unit 101 resides in the embedded sensor or actuator nodes and may, for example, perform functions such as: i) monitoring and control functions such as periodically or continuously monitoring sensor data, monitoring sensor data upon receipt of appropriate commands from the gateway and controlling an actuator upon receipt of appropriate commands from the gateway, ii) performing data processing functions on the monitored data to obtain derived data quantities, iii) storing samples of the data at periodic intervals for later retrieval, iv) sending out alarm signals over a communications link to the gateway based on certain conditions such as the monitored data exceeding preset thresholds, and v) responding to various commands from the gateway for configuring embedded sensor or actuator nodes or for performing monitoring and control functions.
  • monitoring and control functions such as periodically or continuously monitoring sensor data, monitoring sensor data upon receipt of appropriate commands from the gateway and controlling an actuator upon receipt of appropriate commands from the gateway, ii) performing data processing functions on the monitored data to obtain derived data quantities, iii) storing samples of the data at periodic intervals for later retrieval, iv) sending out alarm signals over a communications
  • the data processing functions performed by the software unit 101 may, for example, include filtering of digital sample data from the sensors, compression of data, performing mathematical calculations such as derivative calculation and integration, and performing transformations according to mathematical functions such as Fourier transforms.
  • the software unit 101 should provide various configuration parameters which may, for example, include, number of channels of data, types and sizes of data for each channel, units of measure of data, periodicity of data collection, alarm thresholds and periodicity and time-of-day of reporting stored data to the gateways. While these parameters will be programmable if necessary when the sensor or actuator network is in operation, the software unit 101 will have default values for each of these parameters.
  • the main function of the executable software unit 102 that resides in the gateways is to manage multiple sensors or actuators. It may, for example, perform functions such as: i) storing data reported by the sensors as well as all configuration information for each sensor or actuator, ii) monitoring the correct operation of sensor or actuator nodes, iii) storing alarms reported by sensors or actuators and forwarding alarms to server systems, iv) responding to various commands from the server systems for retrieving stored data, checking the configuration and status of sensors or actuators, and v) providing a command interface for allowing a server system to configure sensor or actuator nodes or for sending commands to sensor or actuator nodes to perform monitoring and control functions.
  • the software unit 102 should provide various configuration parameters which may, for example, include, the maximum number of sensors to manage, amount of data storage to allocate to each sensor, indication of whether a sensor will report automatically at pre-determined times or the gateway should actively collect data from the sensor, periodicity and time of data collection or reporting from sensors, parameters pertaining to the servers that the gateway would be communicating with such as a server Internet address or telephone number (in case of a modem connection). While these parameters will be programmable if necessary when the gateway is in operation, the software unit 102 will have default values for each of these parameters.
  • the software unit 103 resides in a server system and may, for example, perform such functions as: i) collecting data from multiple gateways periodically, ii) performing data conversion to other formats for export to other server systems, iii) presenting alarms reported by sensors or actuators and forwarded by gateways through an user interface, iv) allowing a user to check the status of any sensor or actuator through a user interface that shows the whole sensor or actuator network and associated gateways, and v) allowing a user configure a sensor or actuator or a group of sensors or actuators through the user interface.
  • the software unit 103 is of a fundamentally uniform nature without regard to the type of the type of sensor or actuator network.
  • the software unit 103 performs similar functions, but may differ in its operation only in such respects as the periodicity of the data collection, the format of the data and the total number of gateways and sensors it manages. [0033] It is thus seen from the above the description of the executable application software units 101, 102 and 103 that constitute the executable application software 100 of a sensor or actuator network that all these units are of a fundamentally similar nature. However, between one type of sensor or actuator network and another, they differ in two respects: i) various parameters that control the behavior of the application software units differ from one network to the other, and ii) the required functional components of the units differ from one network or the other.
  • each of the application software units is constructed according to a common structure which facilitates automatic generation of the units for various sensor or actuator networks.
  • This common structure is shown in Fig. 2.
  • Each software unit is constructed with a common structure 200 that comprises two elements: a set of components 201 that perform the functions of the software unit and a framework 202.
  • Each component in the set of components 201 performs one or more logically related functions. Examples of such components are: data collection, data storage, data reporting, command processing and alarm generation in an embedded sensor software unit; sensor monitoring, management and data storage in a gateway software unit; and user interface, data collection and conversion in a server software unit.
  • each component itself has a common structure comprising a functional core 2011 and an interface 2012 that allows it communicate with other components. The means provided in the structure 200 for this communication between components is described in detail below.
  • the framework 202 further comprises two elements, a configurable parameter storage element 2021 and a structure definition element 2022.
  • the configurable parameter storage 2021 stores all the configurable parameters of the software unit described earlier.
  • the components 201 perform their respective functions according to parameter values stored in the parameter storage element 2021.
  • the structure definition element 2022 provides a mechanism that allows the components 201 to co-exist and co-operate within the common structure 200.
  • the structure definition element 2022 provides the means for the components 201 to communicate with each other, or cause certain actions to be taken in one or more components upon the occurrence of a certain event in another component, and thus is the common thread that ties all components together to form a complete functioning application software unit.
  • a message bus 302 allows any component to send or receive a message.
  • the format of the messages is pre-defined and each component is provided with a unique address on the message bus, thus enabling each component to communicate with any other component through a common language.
  • Another means for the component interaction is shown in Fig. 3b.
  • an event notification registry 20221 is provided in the structure definition element 2022.
  • Event notification registry 20221 provides a place where each component can register both the events it will supply and the events it wishes to be notified of.
  • an event dispatcher 20222 in the structure definition element 2022 is notified of the occurrence of the event.
  • the event dispatcher 20222 consults the event registry to send notifications of the event to each component that has registered to be notified of that event. The components that receive the event can then take appropriate action as required.
  • the means for providing component interaction illustrated in Figs. 3a and 3b can be combined.
  • the event notification scheme shown in Fig. 3b may be used to notify components of events that have occurred in a component.
  • the receiving components may then communicate with the originating component through the message bus 302 to perform additional actions as shown in Fig. 3a.
  • FIG. 4 A conceptual block diagram of the system 400 according to the present invention that is capable of generating the executable application software 100 is shown in Fig. 4.
  • the system 400 comprises a graphical user interface 401, a repository of components 402, an application composer 403 and the application framework 202.
  • the graphical user interface 401 obtains user input regarding the various configurable parameters of sensor or actuator network. Examples of these configurable parameters were provided earlier.
  • the graphical user interface 401 may, for example, follow a "wizard" format guiding the user step-by-step through the process of inputting various values for the configurable parameters. It may also, for example, organize the configurable parameters in a plurality of logically related groups and allow the user to input the parameter values in each group separately.
  • the repository of components 402 contains all the components (described earlier), for constructing the application software units.
  • the repository may, for example, be structured as a database of components or as an indexed directory of files.
  • the components contained in the repository are of a structure that is somewhat different from the structures described earlier in Fig. 2.
  • the structure of the components in the repository 402 is shown in Fig. 5.
  • the repository components are further provided with a shell 2013.
  • This shell 2013 contains information pertaining to the component according to a pre-defined format.
  • the shell 2013 may provide descriptive elements such as the name of component, the function it provides and the algorithm and methods it uses.
  • the shell 2013 may also contain further information concerning the performance metrics of the component.
  • the shell 2013 may also provide elements such as memory usage, code size and computation power required in millions of instructions per second.
  • the application composer 403 is responsible for automatically generating the application software units.
  • the means by which the composer 403 achieves this task is now described with reference to Fig. 6.
  • the composer receives these values from the graphical user interface 401 in step 604.
  • the composer 403 retrieves components required to constitute the application software unit from the repository 402.
  • the shells of the components are removed and stored separately.
  • these components whose shells have been removed are combined with the application framework 202 to produce executable software units.
  • step 612 the removed shells are examined and information is extracted from the shells to produce reports of, for example, which components were used to generate the application software unit, as well performance metrics for the whole application software unit such as total memory usage, total code size and total computation power required in millions of instructions per second.
  • the embodiment according to the present invention described above achieves the objective of automatically generating the application software units of a network of sensors or actuators by utilizing a common application framework that allows multiple components to co-exist and co-operate, a repository of components, each of which is structured in a pre-determined manner, and a user interface that allows a user to set various parameters that govern the type and nature of sensor or actuator networking application to be generated. Further, the invention described above also achieves the objective of generating total performance metrics for generated software units. [0044] Further modifications and variations to the embodiment described above can be made to achieve various enhancements. One such enhancement would be to perform the further step of combining the generated application software units with a pre-existing operating system or other pre-existing libraries or hardware drivers that provide various system services to automatically generate entire system software units.
  • a second enhancement would be to allow the user to set constraints regarding the memory usage, code size and computational resources available.
  • the composer could then examine the performance metrics calculated for the entire software and check whether these metrics fall within the constraints imposed by the user. If they do not, user could be warned so that corrective action for optimizing particular components or changing the parameters of the network can be performed.
  • test scripts describe the system to be tested, the operational parameters of the system, and the tests to be conducted to verify the operation of the system.
  • all such networks are of a fundamentally similar nature but only differ in their operational parameters.
  • these operational parameters are defined through a user interface.
  • a pre-defined test script document template 404 is used by a test script composer 405.
  • the test script composer 405 receives the configurable parameter values from the user interface in a manner similar to the application composer 403.
  • the test script composer 405 then combines these parameter values with the template 404 through the means of replacing fields in the document template with the obtained values to automatically generate test scripts.
  • a third embodiment of the present invention relates to the construction of the components themselves.
  • a component consists of a functional core, an interface and a shell that provides information regarding the component.
  • the functional core is typically programmed by a human to perform one or more logically related functions and unit tested to verify its operation. Once this human task has been completed, the task of componentizing this functional core can also be automated as described in this embodiment.
  • Fig. 8 shows the conceptual block diagram of a componentizer 500.
  • the componentizer 500 comprises a graphical user interface 501, an interface generator 502, a shell generator 503 and a component composer 504.
  • the graphical user interface 501 allows a user to pick a functional core 510 through the means of, for example, choosing a source code file, choosing a precompiled object code file or choosing an intermediate bytecode object file to be interpreted by an interpreter.
  • the user interface 501 further allows the user to specify the interface elements of the component according to a pre-defined format. This predefined format may, for example, comprise a specification of the events the components will generate and the events that the component should be registered for and a specification of the interface function or method names in the functional core that will generate and respond to events or, generate and send messages to other components.
  • the user interface 501 further allows the user to input information regarding the component shell such as the name of component, the function it provides and the algorithm and methods it uses, and performance metrics of the component such as memory usage, code size and computation power required in millions of instructions per second.
  • the interface generator 502 obtains the information regarding the component interface input through the user interface 501 and generates the component interface 5021 in a pre-defined format.
  • the shell generator 503 obtains the information regarding the shell from the user interface and generates the shell 5031 in a pre-defined format.
  • the component composer 504 combines the functional core 510 with the interface 5021 and the shell 5031 to produce a finished component 511, which can then be stored in a component repository.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Software Systems (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention porte sur un générateur de logiciel d'application qui génère automatiquement un module logiciel d'application. Le générateur logiciel d'application comprend un composeur (403) qui combine des composants extraits d'un référentiel (402) avec un cadre d'application (202) afin de générer le module logiciel d'application (101, 102 ou 103). Chaque composant du référentiel comprend une coquille, une interface et un noyau. Le cadre d'application comprend des paramètres configurables qui déterminent la façon dont est générée et fonctionne le module logiciel d'application. Les paramètres configurables peuvent être introduits par un utilisateur au moyen d'une interface graphique utilisateur (401). L'utilisateur peut être assisté par un format assistant. Le cadre d'application crée également une connectivité entre des composants de sorte que ceux-ci puissent se faire passer des messages. La connectivité peut être, par exemple, par un bus message ou un registre d'événements ou une distribution d'événements. Les composants eux-mêmes peuvent être automatiquement générés par le générateur de logiciel d'application. Les utilisations du générateur de logiciel d'application comprennent la création de réseaux de capteurs/actionneurs et la génération de script de test.
EP03763139A 2002-07-05 2003-07-03 Systeme et procede de generation automatique d'un reseau automatise de capteurs Withdrawn EP1535148A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/188,861 US7346891B2 (en) 2002-07-05 2002-07-05 System and method for automating generation of an automated sensor network
US188861 2002-07-05
PCT/US2003/020900 WO2004006093A1 (fr) 2002-07-05 2003-07-03 Systeme et procede de generation automatique d'un reseau automatise de capteurs

Publications (2)

Publication Number Publication Date
EP1535148A1 true EP1535148A1 (fr) 2005-06-01
EP1535148A4 EP1535148A4 (fr) 2007-12-12

Family

ID=29999558

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03763139A Withdrawn EP1535148A4 (fr) 2002-07-05 2003-07-03 Systeme et procede de generation automatique d'un reseau automatise de capteurs

Country Status (5)

Country Link
US (2) US7346891B2 (fr)
EP (1) EP1535148A4 (fr)
AU (1) AU2003248800B2 (fr)
CA (1) CA2491630C (fr)
WO (1) WO2004006093A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103544108A (zh) * 2013-11-12 2014-01-29 福建联迪商用设备有限公司 嵌入式软件集成强度的测试系统及方法

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7613881B2 (en) * 2004-06-08 2009-11-03 Dartdevices Interop Corporation Method and system for configuring and using virtual pointers to access one or more independent address spaces
US20060195411A1 (en) * 2005-02-28 2006-08-31 Microsoft Corporation End user data activation
EP1907930A1 (fr) * 2005-07-26 2008-04-09 Sinovia Systeme ouvert d'integration et de gestion de composants informatiques representant une fonctionnalite specifique d'une application determinee
US9015652B2 (en) * 2005-12-21 2015-04-21 Sap Se Dynamically-generated operating system for sensor networks
WO2007092369A2 (fr) * 2006-02-06 2007-08-16 Keystone Software, Inc. Procede pour fournir des services de developpement de logiciels
US8065168B2 (en) * 2006-04-25 2011-11-22 Acs State And Local Solutions, Inc. Method, system and computer program code for automatically generating software for reformatting incoming data
US9990110B1 (en) 2006-08-14 2018-06-05 Akamai Technologies, Inc. Private device cloud for global testing of mobile applications
US9720569B2 (en) 2006-08-14 2017-08-01 Soasta, Inc. Cloud-based custom metric/timer definitions and real-time analytics of mobile applications
US7844036B2 (en) * 2006-08-14 2010-11-30 Soasta, Inc. Visual test automation tool for message-based applications, web applications and SOA systems
US9154611B1 (en) 2006-08-14 2015-10-06 Soasta, Inc. Functional test automation for gesture-based mobile applications
US8789013B1 (en) 2006-08-28 2014-07-22 Rockwell Automation Technologies, Inc. Ordered execution of events in a data-driven architecture
CA2667168A1 (fr) * 2006-10-18 2008-04-24 Iscopia Software Inc. Outil logiciel permettant d'ecrire un logiciel pour la gestion de qualification en ligne
US7676292B2 (en) * 2006-10-20 2010-03-09 Rockwell Automation Technologies, Inc. Patterns employed for module design
JP5072372B2 (ja) 2007-01-16 2012-11-14 株式会社東芝 遠隔監視・診断システム
US9104430B2 (en) * 2008-02-11 2015-08-11 Palo Alto Research Center Incorporated System and method for enabling extensibility in sensing systems
JP4613214B2 (ja) * 2008-02-26 2011-01-12 日立オートモティブシステムズ株式会社 ソフトウェア自動構成装置
US8436542B2 (en) 2009-05-04 2013-05-07 Hubbell Incorporated Integrated lighting system and method
KR101155244B1 (ko) * 2010-02-04 2012-06-13 엘지전자 주식회사 시운전 제어 장치 및 그 방법
US8195982B2 (en) * 2010-06-22 2012-06-05 TestPro Pty Ltd Systems and methods for managing testing functionalities
US9495473B2 (en) 2010-07-19 2016-11-15 Soasta, Inc. Analytic dashboard with user interface for producing a single chart statistical correlation from source and target charts during a load test
US9229842B2 (en) 2010-07-19 2016-01-05 Soasta, Inc. Active waterfall charts for continuous, real-time visualization of website performance data
US8341462B2 (en) 2010-07-19 2012-12-25 Soasta, Inc. System and method for provisioning and running a cross-cloud test grid
US9436579B2 (en) * 2010-07-19 2016-09-06 Soasta, Inc. Real-time, multi-tier load test results aggregation
US9021362B2 (en) 2010-07-19 2015-04-28 Soasta, Inc. Real-time analytics of web performance using actual user measurements
US9251035B1 (en) 2010-07-19 2016-02-02 Soasta, Inc. Load test charts with standard deviation and percentile statistics
JP5635873B2 (ja) * 2010-11-08 2014-12-03 アズビル株式会社 エンジニアリング装置およびポイント情報作成方法
US10564613B2 (en) 2010-11-19 2020-02-18 Hubbell Incorporated Control system and method for managing wireless and wired components
US8869095B2 (en) * 2010-12-10 2014-10-21 Atmel Corporation Software framework and development platform for multi-sensor systems
US9785533B2 (en) 2011-10-18 2017-10-10 Soasta, Inc. Session template packages for automated load testing
KR101907422B1 (ko) * 2012-02-10 2018-10-12 한국전자통신연구원 네트워크 애플리케이션 통합 개발장치, 그 통합 개발방법 및 그것을 이용하는 서버
US9858809B2 (en) 2012-11-08 2018-01-02 Qualcomm Incorporated Augmenting handset sensors with car sensors
US9772923B2 (en) 2013-03-14 2017-09-26 Soasta, Inc. Fast OLAP for real user measurement of website performance
CN103150189B (zh) * 2013-03-19 2016-03-30 青岛乾程科技股份有限公司 一种智能电能表参数的设置方法
CN103345239B (zh) * 2013-06-19 2015-08-19 深圳市国电科技通信有限公司 基于安卓平台的宽带用电信息采集系统现场调测工具
CN103760872A (zh) * 2014-01-27 2014-04-30 林兴志 精细化农业农作物生长告警与干预装置
US10601674B2 (en) 2014-02-04 2020-03-24 Akamai Technologies, Inc. Virtual user ramp controller for load test analytic dashboard
US10346431B1 (en) 2015-04-16 2019-07-09 Akamai Technologies, Inc. System and method for automated run-tme scaling of cloud-based data store
US10140191B2 (en) 2015-07-24 2018-11-27 Accenture Global Services Limited System for development of IoT system architecture
US10673917B2 (en) * 2016-11-28 2020-06-02 Microsoft Technology Licensing, Llc Pluggable components for augmenting device streams
US10884717B2 (en) * 2019-04-09 2021-01-05 Raytheon Company Resource management system featuring a sensor-agnostic software architecture
US11556862B2 (en) 2019-09-14 2023-01-17 Oracle International Corporation Techniques for adaptive and context-aware automated service composition for machine learning (ML)
US11663523B2 (en) 2019-09-14 2023-05-30 Oracle International Corporation Machine learning (ML) infrastructure techniques
US11562267B2 (en) 2019-09-14 2023-01-24 Oracle International Corporation Chatbot for defining a machine learning (ML) solution
CN116820432B (zh) * 2023-08-30 2023-11-21 中国人民解放军国防科技大学 一种bmc固件自动适配主板传感器的方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205362B1 (en) * 1997-11-24 2001-03-20 Agilent Technologies, Inc. Constructing applications in distributed control systems using components having built-in behaviors

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63181033A (ja) * 1987-01-23 1988-07-26 Hitachi Ltd プログラム自動生成方式
JP2592955B2 (ja) * 1989-04-04 1997-03-19 株式会社東芝 プログラム自動生成装置
JPH04241023A (ja) * 1991-01-25 1992-08-28 Hitachi Ltd プログラム合成方法
JPH07306778A (ja) * 1994-05-16 1995-11-21 Fujitsu Ltd ソフトウェアの分散開発環境における開発管理方式
US5815717A (en) * 1995-10-27 1998-09-29 Authorgenics, Inc. Application program and documentation generator system and method
EP0888585A1 (fr) * 1996-03-19 1999-01-07 Massachusetts Institute Of Technology Systeme et procede informatiques servant a representer des descriptions de systemes logiciels et a generer des programmes informatiques executables et des configurations de systemes a partir de ces descriptions
US6317872B1 (en) * 1997-07-11 2001-11-13 Rockwell Collins, Inc. Real time processor optimized for executing JAVA programs
US6202207B1 (en) * 1998-01-28 2001-03-13 International Business Machines Corporation Method and a mechanism for synchronized updating of interoperating software
US6718533B1 (en) * 1999-02-26 2004-04-06 Real-Time Innovations, Inc. Method for building a real-time control system with mode and logical rate
US6339832B1 (en) * 1999-08-31 2002-01-15 Accenture Llp Exception response table in environment services patterns
US6691298B1 (en) * 1999-09-20 2004-02-10 Texas Instruments Incorporated Memory management in embedded system with design time object instantiation
US6487713B1 (en) * 1999-09-24 2002-11-26 Phoenix Technologies Ltd. Software development system that presents a logical view of project components, facilitates their selection, and signals missing links prior to compilation
US8302072B2 (en) * 2000-06-05 2012-10-30 National Instruments Corporation System and method for programmatically generating a graphical program based on a sequence of motion control, machine vision, and data acquisition (DAQ) operations
US7100124B2 (en) * 2000-07-03 2006-08-29 Cadence Design Systems, Inc. Interface configurable for use with target/initiator signals
US20030023950A1 (en) * 2001-01-10 2003-01-30 Wei Ma Methods and apparatus for deep embedded software development

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6205362B1 (en) * 1997-11-24 2001-03-20 Agilent Technologies, Inc. Constructing applications in distributed control systems using components having built-in behaviors

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
HARDY D ET AL: "Specification and-production techniques for portable software components" XIII INTERNATIONAL SWITCHING SYMPOSIUM, vol. 2, 27 May 1990 (1990-05-27), pages 183-189, XP010330647 *
J. KRAMER: "Configuration programming-a framework for the development of distributable systems" PROCEEDINGS OF THE 1990 IEEE INTERNATIONAL CONFERENCE ON COMPUTER SYSTEMS AND SOFTWARE ENGINEERING, COMPEURO 90, [Online] 8 May 1990 (1990-05-08), pages 374-384, XP002455352 Tel Aviv, Israel ISBN: 0-8186-2041-2 Retrieved from the Internet: URL:http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=113648> [retrieved on 2007-10-11] *
JINGWEN CHENG: "PARAMETERIZED SPECIFICATIONS FOR SOFTWARE REUSE" SOFTWARE ENGINEERING NOTES, ACM, NEW YORK, NY, US, vol. 17, no. 4, 1 October 1992 (1992-10-01), pages 53-59, XP000362634 ISSN: 0163-5948 *
R. VAN OMMERING, F. VAN DER LINDEN, J. KRAMER, J. MAGEE: "The Koala component model for consumer electronics software" IEEE COMPUTER, [Online] vol. 33, no. 3, March 2000 (2000-03), pages 78-85, XP002455351 ISSN: 0018-9162 Retrieved from the Internet: URL:http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=825699> [retrieved on 2007-10-11] *
See also references of WO2004006093A1 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103544108A (zh) * 2013-11-12 2014-01-29 福建联迪商用设备有限公司 嵌入式软件集成强度的测试系统及方法

Also Published As

Publication number Publication date
CA2491630A1 (fr) 2004-01-15
US20080059947A1 (en) 2008-03-06
AU2003248800A1 (en) 2004-01-23
CA2491630C (fr) 2012-09-18
AU2003248800B2 (en) 2009-07-23
US8271937B2 (en) 2012-09-18
EP1535148A4 (fr) 2007-12-12
US7346891B2 (en) 2008-03-18
WO2004006093A1 (fr) 2004-01-15
US20040006761A1 (en) 2004-01-08

Similar Documents

Publication Publication Date Title
US8271937B2 (en) System and method for automating generation of an automated sensor network
JP7359354B2 (ja) 分散型工業パフォーマンス監視及び分析
US10386827B2 (en) Distributed industrial performance monitoring and analytics platform
US10866952B2 (en) Source-independent queries in distributed industrial system
US10649449B2 (en) Distributed industrial performance monitoring and analytics
Prowell JUMBL: A tool for model-based statistical testing
US7739216B2 (en) Methods and systems for monitoring and diagnosing machinery by incremently testing a rule
CN101315558B (zh) 用于存取与过程控制系统有关的信息的设备及方法
US20170102693A1 (en) Data analytic services for distributed industrial performance monitoring
Gardner et al. Methods and systems for alarm correlation
US20080065706A1 (en) Process Data Storage For Process Plant Diagnostics Development
US20080125877A1 (en) Process data collection system configuration for process plant diagnostics development
US20080065705A1 (en) Process Data Collection for Process Plant Diagnostics Development
CN1280684A (zh) 具有分布式控制功能的过程控制网中的远程诊断
CN110865941A (zh) 接口测试用例生成方法、装置和系统
CN112686773A (zh) 一种基于融合业务拓扑的电力计量全链路关键业务异常定位模型构建方法
Van Den Berg et al. Designing cyber-physical systems with aDSL: A domain-specific language and tool support
McArthur et al. Automated post-fault diagnosis of power system disturbances
CN115755819A (zh) 一种工程安全自动化设备数据采集控制方法及系统
CN117555778A (zh) 一种航电系统的软件故障注入方法、装置及相关介质
CN117813562A (zh) 用于基于模块化设备的数字孪生模型来编排模拟的配置的计算机实现的方法和编排系统

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20041231

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20071113

17Q First examination report despatched

Effective date: 20080409

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: EKA SYSTEMS INC.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: COOPER TECHNOLOGIES COMPANY

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20150203