US20040054773A1 - Data-transparent measurement management system - Google Patents
Data-transparent measurement management system Download PDFInfo
- Publication number
- US20040054773A1 US20040054773A1 US10/409,418 US40941803A US2004054773A1 US 20040054773 A1 US20040054773 A1 US 20040054773A1 US 40941803 A US40941803 A US 40941803A US 2004054773 A1 US2004054773 A1 US 2004054773A1
- Authority
- US
- United States
- Prior art keywords
- measurement
- data
- management system
- information
- format
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- the present invention relates to measurement management systems.
- Measurement instruments are applied to execute various measurement tasks in order to measure any kind of physical parameter.
- Most of today's measurement instruments use a bus architecture applying a command and communication standard to implement test and measurement, as explained in detail in the article “Bus-Architekturen für die Messtechnik” by John Pieper and Carsten Schilling in Elektronik-Industrie, 11-1999.
- Each instrument has a specific driver with instrument specific commands.
- a programming software implements interfaces to each measurement instrument and converts the measurement instrument specific information in order to communicate with the measurement instrument.
- the programming software further stores resulting data in a database and allows visualizing or manipulating such resulting data using various user interfaces.
- a measurement management system adapted to communicate with one or more measurement instruments (MI).
- the measurement management system comprises at least one driver each for communicating with at least one measurement instrument, a database adapted for storing information, and a processing unit adapted for processing information.
- the measurement management system might further comprise at least one user interface allowing giving access to a user to the measurement management system.
- user interface might comprise at least one of the following: a reporting tool for reporting measurement related data, a graphical user interface for graphically representing information, a non-graphical user interface for representing information in text format only, an interface to provide access to the internet or a mobile device (such as a cell-phone, PDA, pocket PC, etc.), etc.
- Data communication within the measurement management system is provided using an MMS data format.
- MMS data format data content is separated from information about presentation or representation of the data content, or in other words, data content is separated from its presentation.
- Data is preferably represented in a string, and more preferably in a generic string, which is not device specific.
- the invention thus provides a transparent data communication within the measurement management system.
- the MMS data format of data communication within the measurement management system is provided using a standard XML (extensible Markup Language) as defined in e.g. by the World Wide Web Consortium (W3C) as described e.g. under http://www.w3.orq/XML/.
- XML data might be transformed in other kind of XML data using e.g. the extensible Stylesheet Language (XSL) and represented in any kind of graphical user interface using e.g. the so-called XML Stylesheets.
- XSL extensible Stylesheet Language
- the coupled measurement instrument(s) supporus data communication using the MMS data format
- no data format conversion is required e.g. for a data communication between a specific user interface and a specific measurement instrument, thus providing a fully transparent data communication between measurement interface to user interface.
- the invention can be partly or entirely embodied or supported by one or more suitable software programs, which can be stored on or otherwise provided by any kind of data carrier, and which might be executed in or by any suitable data processing unit.
- FIG. 1 illustrates an example according to the present invention.
- the MMS 10 comprises a user interface 50 A as a reporting tool for reporting measurement related data, a graphical user interface 50 B for graphically representing information, a non-graphical user interface 50 C for representing information in text format only, an interface 50 D to provide access to the internet, and an interface 50 E to provide access to a mobile device (such as a cell-phone, PDA, pocket PC, etc.).However, other or further interfaces might be provided accordingly.
- a user interface 50 A as a reporting tool for reporting measurement related data
- a graphical user interface 50 B for graphically representing information
- a non-graphical user interface 50 C for representing information in text format only
- an interface 50 D to provide access to the internet
- an interface 50 E to provide access to a mobile device (such as a cell-phone, PDA, pocket PC, etc.).However, other or further interfaces might be provided accordingly.
- a mobile device such as a cell-phone, PDA, pocket PC, etc.
- Appendix A describes as an example a Time Domain Reflection Measurement Instruction.
- the XML Data example “Meas1” contains key words like “time domain reflection” describing the measurement function for optical time domain reflector instruments. Also the data describes physical settings for the instruments like: “threshold” with “Link Loss”, “Reflectance”, “Insertion Loss” and “Attenuation”. These are parameter settings for the instruments.
- Additional measurement schedules are defined in this example, like measurement periods of 3 seconds. All these information are analyzed from the instrument and executed in the instrument.
- the physical parameters are settings or execution rules for the instrument, see in between the tags ⁇ physical>and ⁇ /physical>, and the number are variable for each different measurement function.
- the measurement result can as well be described in different ways, as shown in an example in Appendix B.
- the XML Data result contains also key words like “measurements”, “general”, “physical” and “result”.
- the result is a trace spectrum for a time domain reflection measurement.
- predefined key words are the assumption both the instrument to understand the process settings and instruction and the user interface to setup the instruction and displays the data.
- the rest of the system and the transfer medium have no constraints about any names and text data.
- XML Data Format is just an example for a useful generic format, but any kind of generic data description, running at different operation systems and different kind of devices like “XML Data as text file” do, can be used according to the present invention.
Abstract
Description
- The present invention relates to measurement management systems.
- Measurement instruments are applied to execute various measurement tasks in order to measure any kind of physical parameter. Most of today's measurement instruments use a bus architecture applying a command and communication standard to implement test and measurement, as explained in detail in the article “Bus-Architekturen für die Messtechnik” by John Pieper and Carsten Schilling in Elektronik-Industrie, 11-1999. Each instrument has a specific driver with instrument specific commands. In an application layer, a programming software implements interfaces to each measurement instrument and converts the measurement instrument specific information in order to communicate with the measurement instrument. The programming software further stores resulting data in a database and allows visualizing or manipulating such resulting data using various user interfaces.
- It is an object of the present invention to provide an improved application layer for measurement instruments. The object is solved by the independent claims. Preferred embodiments are shown by the dependent claims.
- According to present invention, a measurement management system (MMS) is provided adapted to communicate with one or more measurement instruments (MI). The measurement management system comprises at least one driver each for communicating with at least one measurement instrument, a database adapted for storing information, and a processing unit adapted for processing information.
- The measurement management system might further comprise at least one user interface allowing giving access to a user to the measurement management system. Such user interface might comprise at least one of the following: a reporting tool for reporting measurement related data, a graphical user interface for graphically representing information, a non-graphical user interface for representing information in text format only, an interface to provide access to the internet or a mobile device (such as a cell-phone, PDA, pocket PC, etc.), etc.
- Data communication within the measurement management system is provided using an MMS data format. In the MMS data format, data content is separated from information about presentation or representation of the data content, or in other words, data content is separated from its presentation. Data is preferably represented in a string, and more preferably in a generic string, which is not device specific.
- The MMS data format preferably has a generic format, so that e.g. data doesn't describe specific measurement settings for a specific measurement instrument but measurement methods valid for each measurement instrument. Thus, the measurement instrument can be replaced with another instrument, and the data communication keeps the same.
- Using the MMS data format, the data communication does not need a translation at each recipient (e.g. a specific measurement instrument). In case the data with the MMS data format is transferred at many points, only each end recipient might need to provide a translation of the data format. For transferring only, the data communication need not be migrated or translated.
- The invention thus provides a transparent data communication within the measurement management system.
- In one preferred embodiment, the MMS data format of data communication within the measurement management system is provided using a standard XML (extensible Markup Language) as defined in e.g. by the World Wide Web Consortium (W3C) as described e.g. under http://www.w3.orq/XML/. XML data might be transformed in other kind of XML data using e.g. the extensible Stylesheet Language (XSL) and represented in any kind of graphical user interface using e.g. the so-called XML Stylesheets.
- In a preferred embodiment, at least one driver of the measurement management system is adapted to provide data communication with one or more measurement instruments also using the same MMS data format. The driver thus represents a generic interface towards each coupled measurement instrument. This, however, requires that each thereto-coupled measurement instrument supports data communication using the MMS data format. In case the measurement instrument does not support such data communication, a measurement instrument specific driver might be provided for the measurement management system in order to establish data communication there between.
- In operation, the measurement management system might initiate and/or control a measurement task to be executed by a coupled measurement instrument, and/or request or receive status information or measurement related data from a coupled measurement instrument. It goes without saying that multi-tasking might be provided in e.g. in order to initiate or control plural measurement tasks or send or receive information with one or more coupled measurement instruments.
- In case data from the measurement instrument is provided to the driver of the measurement management system already using the MMS data format, all data communication within the measurement management system can then be executed without requiring to (re-)convert or translate the MMS data format e.g. for storing in the database or processing the processing unit. This is since the transition doesn't need the knowledge of the semantic of the data, because the data is transferred but not manipulated or presented. If the computer platforms, the data storages, and the data communication buses support the same technology, the data can be parsed and stored without data translation or migration. Accordingly, a data communication from a provided user interface of the measurement management system can be handled and transferred within the measurement management system without requiring data format conversion. In case that the coupled measurement instrument(s) supporus data communication using the MMS data format, no data format conversion is required e.g. for a data communication between a specific user interface and a specific measurement instrument, thus providing a fully transparent data communication between measurement interface to user interface.
- The invention can be partly or entirely embodied or supported by one or more suitable software programs, which can be stored on or otherwise provided by any kind of data carrier, and which might be executed in or by any suitable data processing unit.
- Other objects and many of the attendant advantages of the present invention will be readily appreciated and become better understood by reference to the following detailed description when considering in connection with the accompanied drawings. Features that are substantially or functionally equal or similar will be referred to with the same reference sign(s).
- FIG. 1 illustrates an example according to the present invention.
- In FIG. 1, a measurement management system (MMS)10 comprises a
driver 20, adatabase 30, aprocessing unit 40 and a plurality ofuser interfaces 50A-50E. Measurement instruments (MI) 60A, 60B etc. can be coupled to thedriver 20 through any kind ofdata communication network 70, which might be wired or wireless. - In the example of FIG. 1, the
MMS 10 comprises auser interface 50A as a reporting tool for reporting measurement related data, agraphical user interface 50B for graphically representing information, anon-graphical user interface 50C for representing information in text format only, aninterface 50D to provide access to the internet, and aninterface 50E to provide access to a mobile device (such as a cell-phone, PDA, pocket PC, etc.).However, other or further interfaces might be provided accordingly. - Data communication within the
MMS 10 is provided using an MMS data format. In the MMS data format, data content is separated from information about presentation or representation of the data content. In the example here, data is represented in a generic string, which is not device specific, and using the aforementioned generic and transparent XML data. The MMS data format describes constant function (e.g. reset) or measurement functions (for example a time domain reference measurement), which can be translated from all instruments, vendor independent and instrument independent. The measure function description, the physical data and measure instructions have specific meanings for different instruments. For that, the XML Data of the MMS data format uses key words, as standard definitions, which can be understood by each measuring instrument. - Appendix A describes as an example a Time Domain Reflection Measurement Instruction. The XML Data example “Meas1” contains key words like “time domain reflection” describing the measurement function for optical time domain reflector instruments. Also the data describes physical settings for the instruments like: “threshold” with “Link Loss”, “Reflectance”, “Insertion Loss” and “Attenuation”. These are parameter settings for the instruments.
- Additional measurement schedules are defined in this example, like measurement periods of 3 seconds. All these information are analyzed from the instrument and executed in the instrument.
- Other information like measurement names, include with <general>. . . </general>tags, are useful information for the presentation, like user interfaces (
nr 50A to 50E in FIG. 1). There is no limit about the number of that information. - The physical parameters are settings or execution rules for the instrument, see in between the tags <physical>and </physical>, and the number are variable for each different measurement function.
- The measurement result can as well be described in different ways, as shown in an example in Appendix B. The XML Data result contains also key words like “measurements”, “general”, “physical” and “result”. In this example the result is a trace spectrum for a time domain reflection measurement. Using predefined key words are the assumption both the instrument to understand the process settings and instruction and the user interface to setup the instruction and displays the data. The rest of the system and the transfer medium have no constraints about any names and text data.
- All kind of user interfaces or tools like—in the example of FIG. 1—the
reporting user interface 50A, theweb interface 50D, graphical 50B and non-graphical 50C interfaces, mobiledevice user interfaces 50E, and other (non-shown) GUI's all use as basis the same XML Data (see “Meas1” measurement function in Appendix A, and” and “Meas1Result” result data in Appendix B). With different XML style sheets and different processing (provided by the processing unit 40) the instrument setup, start of measurement and analyzing of result data is translated to the different presentation. - Information with the same format, for example “Meas1” XML Data have simple and generic interfaces, like “Setup Instrument”, “Start Measurement” and “Measurement Results”. Those simple interfaces can be the same for all instruments, the user interface communicates and controls the instrument with these simple mechanisms. The data above may have different information for different instruments, and the information bus is always the same for all instruments, just parsing the data file in all directions.
- Each application system needs only one
driver 20, which parses the generic text files to the instruments 60 or the result from the instrument to the application. (Today each instruments needs a specific driver on the client, which knows the instrument and the available command set). With this solution, the data with the generic format describes the function and only the instrument 60 has to translate the data and process the functions. - Storing these data in the
database 30 and transferring data to the user interfaces 50 has always the same mechanism, the whole data file can be stored in thedatabase 30 without interpretation data. The access to the data and the transport of the data is always the same simple way. Also modeling of different instrument architectures in the database or in the application is not required. -
Claims (9)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP02020359.2 | 2002-09-12 | ||
EP02020359A EP1315358A1 (en) | 2002-09-12 | 2002-09-12 | Data-transparent management system for controlling measurement instruments |
Publications (2)
Publication Number | Publication Date |
---|---|
US20040054773A1 true US20040054773A1 (en) | 2004-03-18 |
US7469286B2 US7469286B2 (en) | 2008-12-23 |
Family
ID=8185479
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/409,418 Active 2025-08-16 US7469286B2 (en) | 2002-09-12 | 2003-04-08 | Data-transparent measurement management system |
Country Status (2)
Country | Link |
---|---|
US (1) | US7469286B2 (en) |
EP (1) | EP1315358A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060242233A1 (en) * | 2005-04-20 | 2006-10-26 | International Business Machines Corporation | Utilizing group statistics for groups of participants in a human-to-human collaborative tool |
US20070006188A1 (en) * | 2005-05-19 | 2007-01-04 | Albrecht Schroth | Modular code generation |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040243935A1 (en) * | 2003-05-30 | 2004-12-02 | Abramovitch Daniel Y. | Systems and methods for processing instrument data |
DE602005005924T2 (en) | 2005-09-19 | 2008-07-17 | Agilent Technologies, Inc. - a Delaware Corporation -, Santa Clara | Uniform data format for measuring instruments |
US8843437B2 (en) * | 2007-10-18 | 2014-09-23 | Agilent Technologies, Inc. | Measurement data management with combined file database and relational database |
CN102148849B (en) * | 2010-06-30 | 2014-01-08 | 华为技术有限公司 | Data processing method, device and system for audience measurement |
Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5999947A (en) * | 1997-05-27 | 1999-12-07 | Arkona, Llc | Distributing database differences corresponding to database change events made to a database table located on a server computer |
US6064812A (en) * | 1996-09-23 | 2000-05-16 | National Instruments Corporation | System and method for developing automation clients using a graphical data flow program |
US6201996B1 (en) * | 1998-05-29 | 2001-03-13 | Control Technology Corporationa | Object-oriented programmable industrial controller with distributed interface architecture |
US20020016815A1 (en) * | 2000-06-30 | 2002-02-07 | Schneider Automation | Web function block in automation equipment |
US6370569B1 (en) * | 1997-11-14 | 2002-04-09 | National Instruments Corporation | Data socket system and method for accessing data sources using URLs |
US20020062068A1 (en) * | 2000-11-22 | 2002-05-23 | Siemens Ag | Medical diagnosis management system |
US6430615B1 (en) * | 1998-03-13 | 2002-08-06 | International Business Machines Corporation | Predictive model-based measurement acquisition employing a predictive model operating on a manager system and a managed system |
US6437805B1 (en) * | 1996-09-23 | 2002-08-20 | National Instruments Corporation | System and method for accessing object capabilities in a graphical program |
US6449624B1 (en) * | 1999-10-18 | 2002-09-10 | Fisher-Rosemount Systems, Inc. | Version control and audit trail in a process control system |
US20020161606A1 (en) * | 2001-02-16 | 2002-10-31 | Bennett Richard Joseph | Method and system for ordering a laboratory test for a patient and obtaining results thereof |
US6502131B1 (en) * | 1997-05-27 | 2002-12-31 | Novell, Inc. | Directory enabled policy management tool for intelligent traffic management |
US6513019B2 (en) * | 1999-02-16 | 2003-01-28 | Financial Technologies International, Inc. | Financial consolidation and communication platform |
US20030023459A1 (en) * | 2001-03-09 | 2003-01-30 | Shipon Jacob A. | System and method for audio-visual one-on-one realtime supervision |
US20030037119A1 (en) * | 1997-11-14 | 2003-02-20 | National Instruments Corporation | Graphical programming system and method including nodes for programmatically accessing data sources and targets |
US20030061212A1 (en) * | 2001-07-16 | 2003-03-27 | Applied Materials, Inc. | Method and apparatus for analyzing manufacturing data |
US20030083910A1 (en) * | 2001-08-29 | 2003-05-01 | Mehmet Sayal | Method and system for integrating workflow management systems with business-to-business interaction standards |
US20030163555A1 (en) * | 2001-02-28 | 2003-08-28 | Abdella Battou | Multi-tiered control architecture for adaptive optical networks, and methods and apparatus therefor |
US6625651B1 (en) * | 1999-11-30 | 2003-09-23 | Accenture Llp | On-line transaction control during activation of local telecommunication service |
US6640145B2 (en) * | 1999-02-01 | 2003-10-28 | Steven Hoffberg | Media recording device with packet data interface |
US20030233250A1 (en) * | 2002-02-19 | 2003-12-18 | David Joffe | Systems and methods for managing biological data and providing data interpretation tools |
US20050138083A1 (en) * | 1999-11-30 | 2005-06-23 | Charles Smith Enterprises, Llc | System and method for computer-assisted manual and automatic logging of time-based media |
US6938080B1 (en) * | 2000-06-07 | 2005-08-30 | Nortel Networks Limited | Method and computer system for managing data exchanges among a plurality of network nodes in a managed packet network |
US20050250440A1 (en) * | 2000-06-30 | 2005-11-10 | Zhou Peter Y | Systems and methods for monitoring and tracking |
US6993527B1 (en) * | 1998-12-21 | 2006-01-31 | Adobe Systems Incorporated | Describing documents and expressing document structure |
US7023979B1 (en) * | 2002-03-07 | 2006-04-04 | Wai Wu | Telephony control system with intelligent call routing |
US7028225B2 (en) * | 2001-09-25 | 2006-04-11 | Path Communications, Inc. | Application manager for monitoring and recovery of software based application processes |
US20060200253A1 (en) * | 1999-02-01 | 2006-09-07 | Hoffberg Steven M | Internet appliance system and method |
US20060294183A1 (en) * | 2002-02-15 | 2006-12-28 | Agnoli Giovanni M | System, method, and computer program product for media publishing request processing |
US7158943B2 (en) * | 2001-09-04 | 2007-01-02 | Ramon Van Der Riet | Marketing communication and transaction/distribution services platform for building and managing personalized customer relationships |
US7188003B2 (en) * | 1994-12-30 | 2007-03-06 | Power Measurement Ltd. | System and method for securing energy management systems |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2002344C (en) * | 1989-03-29 | 2000-03-28 | John C. Eidson | Measurement system control using real-time clocks and data buffers |
EP1092972B1 (en) * | 1999-10-11 | 2004-08-18 | Gretag-Macbeth AG | Apparatus for automatic measurements on measuring fields |
-
2002
- 2002-09-12 EP EP02020359A patent/EP1315358A1/en not_active Withdrawn
-
2003
- 2003-04-08 US US10/409,418 patent/US7469286B2/en active Active
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7188003B2 (en) * | 1994-12-30 | 2007-03-06 | Power Measurement Ltd. | System and method for securing energy management systems |
US6437805B1 (en) * | 1996-09-23 | 2002-08-20 | National Instruments Corporation | System and method for accessing object capabilities in a graphical program |
US6064812A (en) * | 1996-09-23 | 2000-05-16 | National Instruments Corporation | System and method for developing automation clients using a graphical data flow program |
US6321236B1 (en) * | 1997-05-27 | 2001-11-20 | Arkona, Inc. | Distributing database differences corresponding to database change events made to a database table located on a server computer |
US6502131B1 (en) * | 1997-05-27 | 2002-12-31 | Novell, Inc. | Directory enabled policy management tool for intelligent traffic management |
US5999947A (en) * | 1997-05-27 | 1999-12-07 | Arkona, Llc | Distributing database differences corresponding to database change events made to a database table located on a server computer |
US20030037119A1 (en) * | 1997-11-14 | 2003-02-20 | National Instruments Corporation | Graphical programming system and method including nodes for programmatically accessing data sources and targets |
US6370569B1 (en) * | 1997-11-14 | 2002-04-09 | National Instruments Corporation | Data socket system and method for accessing data sources using URLs |
US6430615B1 (en) * | 1998-03-13 | 2002-08-06 | International Business Machines Corporation | Predictive model-based measurement acquisition employing a predictive model operating on a manager system and a managed system |
US6201996B1 (en) * | 1998-05-29 | 2001-03-13 | Control Technology Corporationa | Object-oriented programmable industrial controller with distributed interface architecture |
US6993527B1 (en) * | 1998-12-21 | 2006-01-31 | Adobe Systems Incorporated | Describing documents and expressing document structure |
US6640145B2 (en) * | 1999-02-01 | 2003-10-28 | Steven Hoffberg | Media recording device with packet data interface |
US20060200253A1 (en) * | 1999-02-01 | 2006-09-07 | Hoffberg Steven M | Internet appliance system and method |
US6513019B2 (en) * | 1999-02-16 | 2003-01-28 | Financial Technologies International, Inc. | Financial consolidation and communication platform |
US6449624B1 (en) * | 1999-10-18 | 2002-09-10 | Fisher-Rosemount Systems, Inc. | Version control and audit trail in a process control system |
US20050138083A1 (en) * | 1999-11-30 | 2005-06-23 | Charles Smith Enterprises, Llc | System and method for computer-assisted manual and automatic logging of time-based media |
US6625651B1 (en) * | 1999-11-30 | 2003-09-23 | Accenture Llp | On-line transaction control during activation of local telecommunication service |
US6938080B1 (en) * | 2000-06-07 | 2005-08-30 | Nortel Networks Limited | Method and computer system for managing data exchanges among a plurality of network nodes in a managed packet network |
US20020016815A1 (en) * | 2000-06-30 | 2002-02-07 | Schneider Automation | Web function block in automation equipment |
US20050250440A1 (en) * | 2000-06-30 | 2005-11-10 | Zhou Peter Y | Systems and methods for monitoring and tracking |
US20020062068A1 (en) * | 2000-11-22 | 2002-05-23 | Siemens Ag | Medical diagnosis management system |
US20020161606A1 (en) * | 2001-02-16 | 2002-10-31 | Bennett Richard Joseph | Method and system for ordering a laboratory test for a patient and obtaining results thereof |
US20030163555A1 (en) * | 2001-02-28 | 2003-08-28 | Abdella Battou | Multi-tiered control architecture for adaptive optical networks, and methods and apparatus therefor |
US20030023459A1 (en) * | 2001-03-09 | 2003-01-30 | Shipon Jacob A. | System and method for audio-visual one-on-one realtime supervision |
US20030061212A1 (en) * | 2001-07-16 | 2003-03-27 | Applied Materials, Inc. | Method and apparatus for analyzing manufacturing data |
US20030083910A1 (en) * | 2001-08-29 | 2003-05-01 | Mehmet Sayal | Method and system for integrating workflow management systems with business-to-business interaction standards |
US7158943B2 (en) * | 2001-09-04 | 2007-01-02 | Ramon Van Der Riet | Marketing communication and transaction/distribution services platform for building and managing personalized customer relationships |
US7028225B2 (en) * | 2001-09-25 | 2006-04-11 | Path Communications, Inc. | Application manager for monitoring and recovery of software based application processes |
US20060294183A1 (en) * | 2002-02-15 | 2006-12-28 | Agnoli Giovanni M | System, method, and computer program product for media publishing request processing |
US20030233250A1 (en) * | 2002-02-19 | 2003-12-18 | David Joffe | Systems and methods for managing biological data and providing data interpretation tools |
US7023979B1 (en) * | 2002-03-07 | 2006-04-04 | Wai Wu | Telephony control system with intelligent call routing |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060242233A1 (en) * | 2005-04-20 | 2006-10-26 | International Business Machines Corporation | Utilizing group statistics for groups of participants in a human-to-human collaborative tool |
US8918458B2 (en) * | 2005-04-20 | 2014-12-23 | International Business Machines Corporation | Utilizing group statistics for groups of participants in a human-to-human collaborative tool |
US20070006188A1 (en) * | 2005-05-19 | 2007-01-04 | Albrecht Schroth | Modular code generation |
Also Published As
Publication number | Publication date |
---|---|
US7469286B2 (en) | 2008-12-23 |
EP1315358A1 (en) | 2003-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7509649B2 (en) | System and method for conversion of generic services' applications into component based applications for devices | |
US9244709B2 (en) | Automatic recognition of web application | |
US7650590B2 (en) | Flexible code generation | |
CN106663002B (en) | REST service source code generation | |
US20040128584A1 (en) | Method and system for determining computer software test coverage | |
US20060200748A1 (en) | System and method for applying workflow of generic services' to component based applications for devices | |
US20050256882A1 (en) | Systems and methods for web service function, definition, implementation, and/or execution | |
US20080209392A1 (en) | Systems and Methods for Definition and Execution of Batch Processing Services | |
US20060230057A1 (en) | Method and apparatus for mapping web services definition language files to application specific business objects in an integrated application environment | |
US20050091386A1 (en) | Method and apparatus for interfacing with a distributed computing service | |
US20040167749A1 (en) | Interface and method for testing a website | |
US9934029B2 (en) | Annotation driven representational state transfer (REST) web services | |
US7975255B2 (en) | Method, apparatus, and program product for building integration workflow endpoints into web components | |
CA2498539C (en) | A system and method for building component applications using metadata defined mapping between message and data domains | |
CA2538561C (en) | System and method for conversion of web services applications into component based applications for devices | |
MXPA06000106A (en) | Web application architecture. | |
TW201142709A (en) | A method, system and computer program for deciding whether to install a first application within one of a plurality of candiate environments | |
US20090097069A1 (en) | Extensible framework for parsing varying formats of print stream data | |
US7328234B1 (en) | Agent architecture for triggering remotely initiated data processing operations | |
US20040054773A1 (en) | Data-transparent measurement management system | |
US8095569B2 (en) | Customized context menu for files based on their content | |
JP2006510955A (en) | Context-independent framework system and method for managing and executing XML processing tasks | |
Pietschmann et al. | Dynamic composition of service-oriented web user interfaces | |
US7263696B1 (en) | Dynamic web based jar file finder | |
CN113568622A (en) | Method and device for converting codes and electronic equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AGILENT TECHNOLOGIES, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AGILENT TECHNOLOGIES DEUTSCHLAND GMBH;REEL/FRAME:014181/0285 Effective date: 20030515 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |