JP4241717B2 - Service providing apparatus for embedded device using message storage, method for providing service to multiple embedded devices, and system for providing service to embedded device - Google Patents

Description

  The present invention relates to computer software, and more particularly to a new system and method for providing access and services to embedded devices over a computer network.

  In recent years, the amount of computer technology related to daily life has greatly increased. In today's world, computer technology is involved in many aspects of an individual's day. Many devices used today by consumers have a small computer inside the device. These small computers are offered in various sizes and precisions. These small computers include everything from microcontrollers to fully functional complete computer systems. For example, these small computers may be a one-chip controller such as a microcontroller, a one-board computer such as a controller, a typical desktop computer such as an IBM-PC compatible machine, or the like.

  Small computers (which may be slightly larger computers depending on the specific needs being met by the computer) almost always have one or more processors at the heart of the computer. The processor (s) are typically interconnected with various external inputs and outputs and functions for managing a particular device. The processor in the vending machine for carbonated drinks includes buttons used to select carbonated drinks, switches that allow carbonated drinks to fall to the user, and certain varieties of carbonated drinks where the machine is. May be connected to a light to indicate that it no longer has.

  Computer technology is involved in many aspects of today's world. Many devices, devices, etc. are equipped with one or more small computers. For example, refrigerators, telephones, typewriters, automobiles, vending machines, and many different types of industrial equipment all have small computers or processors within them. Computer software runs the processors of these computers and tells them what to do to perform specific tasks. For example, computer software running on a processor in a vending machine causes the carbonated beverage to fall to the user when the correct change is inserted by the user.

  These types of small computers that are part of devices, equipment, tools, etc. are often referred to as embedded systems. The term “embedded system” typically refers to computer hardware and software that are part of a larger system. Embedded systems typically do not have typical input / output devices such as a keyboard, mouse, and / or monitor. In general, there is one or more processors at the heart of each implantation system.

  Typically, embedded systems used today with a variety of equipment, devices, etc. do not have much storage capability. As a result, the amount of data that can be stored by the embedded system is limited. Due to limited storage space, an embedded system may not have as many functions and capabilities as would have had more available storage space. Memory is often saved in these embedded systems that monitor, control and otherwise use electronic devices.

  Almost all desktop computer systems include memory management functions at the processor level (hardware), firmware level (software embedded in the hardware), and operating system level. However, many embedded devices cannot use these types of memory management functions. For example, many embedded environments include 8-bit or 16-bit microcontrollers that lack substantial operating system or memory management functions. In these types of environments, program code is typically created and loaded onto the embedded device by the manufacturer before the device is shipped, and software updates are rarely performed after shipment, even if considered. I will not.

  Many embedded devices do not have extensive memory management capabilities, so often they can easily update software, update modules, update components, and / or new software, new components Adding new modules, new functions, new extensions, etc. is difficult. Some embedded systems are connected to a computer network to allow some communication between the embedded system and a larger computer system. However, because embedded systems often do not have the functionality to communicate effectively and efficiently with other computer systems, communication functions are usually limited. In addition, the means for communicating with the embedded system is often a slower communication path so that only a limited amount of data is exchanged with the embedded system.

  Due to the limited memory resources on the embedded system and usually due to limited communication means, often only limited interaction from the computer network with the embedded system is available. This interaction often has a limited effect due to difficulties in communicating with various parts of the embedded system.

  As stated, it is often difficult to easily update embedded system software once it is out of the field and used. As a result, newer embedded systems have newer software installed, while older embedded systems usually have older versions of software. When a computer system on a computer network needs to communicate with multiple embedded systems or devices, it needs to be programmed to communicate with each specific version of software that can be installed on the embedded system. Let's go. Programming and maintaining a computer on a computer network to communicate with many different versions of software in an embedded system is many companies whose main focus is not simply providing services to the embedded system and / or It will be burdensome and difficult for the manufacturer.

  As the use of computer techniques and embedded systems continues to expand and continue to be used in further areas, the need to be able to communicate and interact with these embedded systems increases. Furthermore, there will be a growing need in the area of controlling, monitoring, updating and otherwise providing services for embedded systems and / or devices.

  To achieve the above object, a service providing apparatus for an embedded device according to claim 1 is a computer including communication hardware for communicating on a computer network, the computer including a storage device, and the computer. A computer network communication module for communicating with a computer via a network, configured to communicate with a message storage / transmission device via the computer network, wherein the message storage / transmission device is connected via the computer network A computer network communication module capable of communicating with one or more embedded devices, and a database of service information obtained from the computer network, through the message storage / transmission device A database whose serial implantation device can be used, and summarized in that and a database interface module for accessing the service information in the service information database.

  A service providing apparatus for an embedded device according to a second aspect is the service providing apparatus for an embedded device according to the first aspect, wherein the message storage / transmission apparatus includes a mail server.

  A service providing apparatus for an embedded device according to a third aspect is the service providing apparatus for an embedded device according to the first aspect, wherein the message storage / transmission apparatus includes a message queue.

  The service providing apparatus for the embedded device according to claim 4 is the service providing apparatus for the embedded device according to claim 1, wherein the service network searches for the computer network and updates the service information from the computer network. The gist of the present invention is to further include an information collection manager for accessing and acquiring.

  6. The service providing apparatus for an embedded device according to claim 5, wherein the updated service information acquired from the computer network is stored on the embedded device according to claim 4. It is related to the computer program code.

  The service providing apparatus for an embedded device according to claim 6 is the service providing apparatus for embedded device according to claim 4, wherein the updated service information acquired from the computer network is stored in the embedded device. The gist is related to location.

  8. The service providing apparatus for an embedded device according to claim 7, further comprising an embedded device communication module for processing communication with the message storage / transmission apparatus in the service providing apparatus for the embedded device according to claim 1. The gist is to provide.

  9. The service providing apparatus for an embedded device according to claim 8, wherein said embedded device communication module includes an embedded device identifier, in said service storing apparatus for embedded device. The gist is to process at least one communication.

  The service providing apparatus for an embedded device according to claim 9, further comprising schedule data in the service providing apparatus for embedded device according to claim 1, wherein the schedule data includes an embedded device identification, and the schedule The gist is that data is used to control the monitoring of the embedded device.

  The service providing apparatus for an embedded device according to claim 10 is the service providing apparatus for the embedded device according to claim 1, wherein the providing apparatus acquires a device description from the message storage / transmission apparatus, and The gist of the device description is that it was previously transmitted from the embedded device to the message storage / transmission device.

  The service providing apparatus for an embedded device according to claim 11 is the service providing apparatus for the embedded device according to claim 10, wherein the device description includes a function, a variable, a data type, an event, and a file. The main point is to be selected from a group.

  13. The service providing apparatus for an embedded device according to claim 12, wherein the service providing apparatus for the embedded device according to claim 1 is configured such that the providing apparatus transfers the embedded device from the embedded device to the message storage / transmission apparatus. The interface data transmitted in the past is monitored by periodically acquiring from the message storage / transmission device, and the providing device stores the interface data in the storage device.

  The service providing apparatus for an embedded device according to claim 13 is the service providing apparatus for an embedded device according to claim 12, wherein the providing apparatus stores monitoring data created from the received interface data The providing apparatus further provides the requester with the monitoring data through the computer network.

  The service providing apparatus for the embedded device according to claim 14 is the service providing apparatus for the embedded device according to claim 9, wherein the providing apparatus affects the operation of the embedded device. Control data is periodically transmitted to computer program code loaded in the embedded device, and the periodic transmission is based on the schedule data, and the control data is transmitted from the providing apparatus to the message. It is transmitted to the storage / transmission apparatus, and then transmitted from the message storage / transmission apparatus to the embedded device.

  The service providing apparatus for an embedded device according to claim 15 is the service providing apparatus for the embedded device according to claim 1, wherein the providing apparatus receives the computer program code updated via the computer network. A computer on the embedded device by obtaining and notifying the embedded device of available updates, and further sending the updated computer program code to the embedded device through the message store / transmit device The main point is to update the program code.

  In order to achieve the above object, a service providing apparatus for an embedded device according to claim 16 is communication hardware for communicating on a computer network, and stores / transmits a message via the computer network. An embedded device information database configured to communicate with an apparatus, wherein the message storage / transmission apparatus can communicate with one or more embedded devices through the computer network, memory, and embedded device information. An embedded device information database that can be used by a communication network, and a service information database that includes service information acquired from the computer network, the embedded information through the message storage / transmission configuration win A service information database available to the device; a processor, receiving a message from the message storage / transmission device having information previously received from the embedded device; and storing the information in the message storage / transmission Identifying the embedded device transmitted to the device; accessing the embedded device information database; and transmitting information to the message storage / transmission device which is subsequently transmitted to the embedded device by the message storage / transmission device. The gist of the present invention is to include a processor that executes a command for realizing a method including a step and a step of storing device information that describes a transaction.

  The service providing apparatus for an embedded device according to claim 17 is the service providing apparatus for an embedded device according to claim 16, wherein the service information database is acquired via the computer network. Is further included.

  19. The service providing apparatus for an embedded device according to claim 18, wherein the embedded device information database includes a specific embedded in specific updated service information. The gist is to further include link data for linking device information, a plurality of embedded device identifiers, and a plurality of function tables.

  A service providing apparatus for an embedded device according to claim 19, further comprising schedule data in the service providing apparatus for embedded device according to claim 18, wherein the schedule data includes embedded device identification and routing data. And the schedule data is used to control the monitoring of a plurality of embedded devices.

  20. The service providing apparatus for an embedded device according to claim 20, wherein the embedded device information database is received from the message mechanism and the transmitting apparatus in the service providing apparatus for the embedded device according to claim 19. Data is further provided, and the interface data has been previously transmitted from the embedded device to the message storage / transmission device.

  22. The service providing apparatus for an embedded device according to claim 21, wherein the service providing apparatus for the embedded device according to claim 20 is transmitted to the message storage / transmission apparatus and then transmitted to the embedded device. The gist of the invention is that it further includes control data, and the control data can affect the operation of the embedded device.

  23. The service providing apparatus for an embedded device according to claim 22, wherein the embedded device information database is acquired via the computer network in the service providing apparatus for the embedded device according to claim 21. The gist further comprises a plurality of files of updated computer program code that can be used to update the program code above.

  In order to achieve the above object, a method for providing a service to a plurality of embedded devices according to claim 23 provides electronic communication between a service providing apparatus for the embedded device and a communication network. Receiving from the message storage / transmission device a communication including information previously transmitted to the message storage / transmission device by the embedded device via the communication network; and sending the information to the message storage / transmission device. Identifying the transmitted embedded device, accessing an embedded device information database, and communication including information transmitted later to the embedded device by the message storage / transmission device to the message storage / transmission device Sending over the network and And storing the device information describing the action, and subject matter to include.

  In order to achieve the above object, a system for providing services to an embedded device according to claim 24 is one or more service providing apparatuses for an embedded device, each of which is provided for an embedded device. The service providing apparatus includes a computer including communication hardware for communicating on a computer network, the computer including a storage device, a database, and a computer network communication module for communicating with the computer via the computer network. A computer configured to communicate with a message storage / transmission device via the computer network, wherein the message storage / transmission device can communicate with one or more embedded devices via the computer network. A network communication module; a database interface module for accessing information in the database; and a central providing device for electronically communicating with the plurality of service providing devices for the embedded device, the embedded device; In order to provide communication between service providing devices for the embedded device and to coordinate collecting updated information from the computer network in relation to the embedded device, the updated to the embedded device. And a central providing device that operates to coordinate spreading information.

  According to the present invention, it is possible to communicate and interact with the embedded system, and to create an environment in which the embedded system can be controlled, monitored, and updated.

  Exemplary embodiments of the present invention will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. With the understanding that these drawings depict only exemplary embodiments and therefore should not be considered as limiting the scope of the present invention, the exemplary embodiments of the present invention have additional specificity through the use of the accompanying drawings. And will be described in detail.

  In accordance with the embodiments broadly described herein, a service providing apparatus for an embedded device is disclosed for controlling, monitoring and / or updating an embedded device. The service providing apparatus includes a computer having communication hardware for communicating on a computer network. The computer also includes at least one storage device and at least one processor. The service providing apparatus further includes a computer network communication module for communicating with a computer via a computer network. The computer network communication module is also configured to communicate with the message storage / transmission device via the computer network. Instead, the message store / send device can communicate with one or more embedded devices through a computer network. The service information database is also added to the service providing apparatus. This database of service information is available to the embedded device through a message store / send device. The service providing apparatus also has a database interface module for accessing information in the embedded device information database.

  Additional embodiments may also be configured to include an information collection manager for the service providing apparatus to search the computer network and to access and obtain updated information from the computer network associated with the embedded device. . Additional embodiments may include an embedded device communication module that handles communication with the message storage / transmission device in the providing device.

  Further, additional embodiments may be constructed in which the providing device controls the embedded device by periodically sending control data to computer program code loaded on the embedded device. This control data will likely affect the operation of the embedded device. Typically, this periodic transmission of control data is based on schedule data found at the providing device. In some embodiments, this transmission of control data is accomplished by sending data from the provider to the message store / transmitter, and then instead sending data from the message store / transmitter to the embedded device. The

  A method for using / implementing the embodiments described herein may be accomplished by first providing electronic communication between a service provider for an embedded device and a communication network. Once this communication is established, the communication is received from the message store / send device. Typically, this communication from the message storage / transmission device includes information previously transmitted from the embedded device to the message storage / transmission device. Next, the providing apparatus starts to identify the embedded device that transmitted the information to the message storage / transmission apparatus. Once the embedded device is identified, the embedded device information database is accessed by the providing device and communication is transmitted from the providing device to the message storage / sending device. This sent message contains information (control data, updated computer code sugar) that can be sent later to the embedded device by the message store / send device. Finally, information about this transaction can then be stored by the provider in the storage database for future reference.

  The system is also disclosed for providing a service to an embedded device, the system comprising a plurality of service providing devices for the embedded device. Generally, the at least one of the service providing apparatuses includes a computer network communication module for communicating with a computer via a computer network. The computer network communication module is also configured to communicate with the message storage / transmission device via the computer network. Similarly, a message store / send device can communicate with one or more embedded devices through a computer network. The system also includes a central provider in electronic communication with a plurality of service providers for the embedded device. The central provider operates to coordinate communication between the embedded device and the service provider for the embedded device and to coordinate dissemination of updated information to the embedded device.

  It will be readily appreciated that the apparatus of the embodiments could be arranged and designed in a wide variety of different configurations, generally as described and illustrated in the figures herein. Thus, the following more detailed description of the system and method embodiments, as represented in FIGS. 1-16, is intended to limit the scope of the invention as claimed. Rather, it merely represents an embodiment of the present invention.

  The present invention is best understood by referring to the drawings, wherein like parts are designated with like numerals throughout.

  The service providing apparatus 20 for an embedded device is disclosed as including a computer having communication hardware for communicating over a computer network 22. The computer also includes at least one storage device and at least one processor. The service providing apparatus 20 further includes a database of embedded device information and / or a database of service information acquired from the computer network 22. The embedded device communication module is used by the service providing apparatus 20 to communicate with many embedded devices 24. The service providing apparatus 20 further includes a computer network communication module for communicating with a computer via the computer network 22. Furthermore, the service providing apparatus 20 has a database interface module for accessing information in a database (a plurality of cases).

  The service providing apparatus 20 may also include an information collection manager for searching the computer network 22 and for accessing and obtaining updated information from the computer network 22 in connection with the embedded device 24. The providing device 20 may link specific information in the embedded device information database to specific updated information. Among items that may be stored in the embedded device information database, there may be a plurality of function tables.

  In communicating with the embedded device 24, the embedded device communication module may receive at least one message from the embedded device 24 that includes an embedded device identifier. Communication with one or more embedded devices 24 may be scheduled using schedule data. The schedule data may include embedded device identification and transmission data. The schedule data may be used to control the monitoring of the embedded device 24.

  The control of the one or more embedded devices 24 is performed by periodically transmitting control data to computer program code loaded on the embedded device 24 in order to influence the operation of the embedded device 24, thereby providing the service providing apparatus 20. May be provided by. The periodic transmission may be based on schedule data. In addition, the providing device 20 obtains the updated computer program code via the computer network 22 and notifies the embedded device 24 of available updates, and the computer updated to the embedded device 24. Further transmission of the program code may cause the computer program code on the embedded device 24 to be updated.

  The providing apparatus 20 may monitor the embedded device 24 via the embedded device communication module by periodically obtaining interface data from computer program code loaded on the embedded device 24. The providing device 20 may store the interface data in the storage device. Further, the providing device 20 may collect information on the monitoring data created from the received interface data. This monitoring data may be provided to the requester through the computer network 22.

  The providing apparatus 20 may communicate with the embedded device 24 via an embedded device communication module to obtain a device description from computer program code loaded on the embedded device 24. The device description may comprise a list of functions, variables, data types, events and files.

  A method practiced according to embodiments herein includes providing electronic communication between a service providing apparatus 20 for an embedded device and a telecommunications network 22, receiving a message from the embedded device 24, received Identifying the embedded device 24 through use of the message, accessing an embedded device information database, sending a send message to the embedded device 24, and storing device information describing the transaction. .

  The method may also include collecting updated information from the computer network 22 associated with the embedded device 24 and linking specific information in the embedded device information database to the specific updated information. Further, the method may include parsing a message from the embedded device 24 to obtain an embedded device identifier.

  A system for providing a service to the embedded device 24 comprising a plurality of service providing devices 20 for the embedded device 24 is also disclosed. The system also includes a central provider that electronically communicates with a plurality of service providers 20 for the embedded device 24. The central provider operates to coordinate communication between the embedded device 24 and the service provider 20 for the embedded device 24. The central provider may coordinate collecting updated information from the computer network 22 in connection with the embedded device 24 and may coordinate disseminating the updated information to the embedded device 24. .

  Of course, those skilled in the art will appreciate that the method may be embodied by executable instructions stored on a computer-readable medium.

  FIG. 1 is a block diagram depicting the main components typically utilized in the use of a service providing apparatus 20 for an embedded device 24 and the embodiments disclosed herein. In the present embodiment, the service providing apparatus 20 electronically communicates with one or a plurality of embedded devices 24 (or embedded systems 24), and also communicates electronically with one or a plurality of embedded device networks 26. . These electronic communications may be direct dial-up connections, LANs, WANs, and connections through intranets, the Internet, or other means of electronic communications. As shown, the computer network 22 may provide electronic communication between the service providing device 20 and many other components. In the present embodiment, the computer network 22 includes the Internet.

  Device manufacturer 28 may communicate with computer network 22. For example, device A manufacturer 28a and device B manufacturer 28b may electronically communicate with computer network 22 as depicted. The device manufacturer 28 may be the manufacturer of the embedded device 24, the processor used by the embedded device 24, the software used by the embedded device 24 and / or the processor. Some examples of companies that would be typical device manufacturers 28 are Motorola, Intel, AMD, Nokia, Hewlett Packard, Microchip, Siemens. (Siemens). These examples are merely intended to be illustrative and are not intended to limit the broad scope of what may be considered device manufacturer 28.

  In many cases, the device manufacturer 28 recognizes the device update regardless of whether it is hardware, software, or any problem of the device. The service providing apparatus 20 may obtain information from a device manufacturer 28 that is used to update, monitor and control the embedded device 24 or otherwise provide a service.

  Information provider 30 may be in electronic communication with computer network 22. The information provider 30 is any provider of information that may be valid in a sense by the embedded device 24 and / or by the embedded device service providing apparatus 20. For example, weather information may be provided by a website of the world wide web portion of the internet. This device for providing weather information would be in the range of the information provider 30. Furthermore, the current date and time may also be provided by the information provider 30. Another information provider may provide consumer goods identification information, and another information provider 30 may provide map information.

  Data collector 32 may be in electronic communication with computer network 22. Data collector 32 is any entity engaged in collecting data from embedded device 24. Data collector 32 may be referred to as a requester in that it requests data from embedded device 24. In the present embodiment, the service providing apparatus 20 facilitates collection of data from the embedded device 24 by communicating with the embedded device 24 and at some point providing this data or related information to the data collector 32. To. An example of a data collector 32 would be a utility company with a need to collect and aggregate usage data from meters that measure usage by various consumers. An embedded device 24 that implements these meters or communicates electronically with these meters can read usage data and provide it to the service provider 20. Next, the service providing apparatus 20 can provide the acquired usage data to the data collector 32. Many other data collection needs may be met by the data collector 32. For example, collecting data regarding which consumer items have been purchased, their current status, and / or where the consumer items are is valid information that may be collected by the data collector 32 There is.

  A service 34 that controls and / or monitors the embedded device 24 and / or the embedded network 26 may be in electronic communication with the computer network 22. The control / monitoring service 34 may be any service that provides control for the embedded device 24 and / or provides monitoring of the embedded device 24. In some situations, the data collector 32 is similar to a service that provides monitoring. However, the control and / or monitoring service 34 provides a more active role than the data collector 32. In some embodiments, the monitoring service 34 periodically monitors one or more embedded devices 24 to see if the device 24 is operating within normal parameters. In certain embodiments, the control service 34 provides one or more embedded devices 24 by transmitting control data to the one or more embedded devices 24. For example, a particular set of embedded devices 24 may require weather information for proper operation (eg, a sprinkler controller), and the control service 34 may provide control data based on the weather information and location. . For example, the control service 34 may send a command to instruct a particular embedded device sprinkler controller not to water the controller.

  FIG. 2 is a block diagram of data available from the device manufacturer 28. Device manufacturer 28 may recognize embedded software update 36 and have a copy thereof. For example, a newer version of software running on the embedded device 24 microcontroller is available from the device manufacturer 28. The device manufacturer 28 may make this updated software 36 available.

The device manufacturer 28 can also recognize various functions of the device 24 that it manufactures. In this regard, the device manufacturer 28 may make a functional description 38 available for the device 24. Basic information about the embedded device 24, its characteristics and functions is useful for those who somehow want to interact with it. Such basic information may be stored by the device manufacturer 28 in the function description 38 or the function table 38. The function table 38 may be stored as a file. One skilled in the art will appreciate that there are a variety of ways to store the basic functionality of the embedded device 24 and its connected input and / or output devices. Table 1 includes pseudo code that describes what type of information may be stored in the functional description 38 or table 38.

  As depicted in Table 1, the function table 38 may include an indication of which interface definition (1A) the embedded device 24 supports. The interface definition (1A) field and its use are described more fully herein. The function table 38 may also indicate the byte order type indicated by row (1B). This byte ordering type (1B) may indicate whether the embedded device is big endian or small endian. Table 38 may also indicate which device identification shown in row (1C) is for a particular embedded device 24. The device address shown in row (1D), if any, may also be stored in function table 38.

  For compatibility purposes, the version number shown in line (1E) for the software being used may also be stored. Similarly, the communication protocol version number shown in the row (1F) may be stored. Details about the communication may also be stored. For example, as shown in Table 1, the maximum communication packet size shown in the row (1G) may be stored.

  The non-volatile storage flag shown in row (1H) may indicate whether there is a non-volatile storage accessible by the embedded device 24. Related information about the non-volatile storage device such as the non-volatile storage device size and its start address shown in row (1I) may also be stored. The static file system flag shown in line (1J) may indicate whether there is a static file system. Similarly, the dynamic file system flag shown in line (1K) may indicate whether there is a dynamic file system.

  The function table 38 is effective in that the developer or engineer can obtain the function table 38 and confirm the characteristics and functions of the embedded device 24.

  The device manufacturer 28 may have other device information 40. For example, device manufacturer 28 may have this information if it was known that a particular embedded device 24 would fail after a certain period of time. Further, the manufacturer 28 may be aware of certain parts of the embedded device 24 that are known to wear out over time and produce incorrect data. Device manufacturer 28 will probably also recognize the embedded device 24 recall. As will be appreciated by those skilled in the art, the device manufacturer 28 may recognize many other items 42 or things that may be associated with the embedded device 24. The device manufacturer 28 may also make other information 42 available.

  FIG. 3 is a block diagram of data or information that may be available from the information provider 30. The information provider 30 is an entity that provides any type of data or information. Typically, data or information is provided in the form of electronic communication. FIG. 3 depicts an example of data that may be provided by the information provider 30. Weather information 44 may be provided. Date and time information 46 may be provided. Barcode information 48 may also be provided, such as which consumer goods are identified with a particular barcode. Status information 50 about a particular item, matter or location may also be provided. Of course, those skilled in the art will recognize that many other types of information 52 may also be provided.

  FIG. 4 is a block diagram of data or information that may be collected by the data collector 32 or requester. Data collector 32 is an entity that collects and / or stores information or data. Typically, data or information is transmitted to the data collector 32 in electronic form. The items shown in FIG. 4 show examples of data that can be collected by the data collector 32 related to monitoring items for a utility company or the like. The meter reading 54 portion of data may indicate how many meters and which meters have been read within a particular area. The billing issuance data 56 may indicate past bills for a particular customer and whether they have been paid. Rate information 58 includes a variety of rates and may indicate to which customer each rate must be charged. The usage data 60 may store past usage information to indicate usage increases and decreases by individual consumers as well as groups of consumers. The performance information 62 includes various embedded devices 24 and their associated components, how they function in the field, how long they typically last, and what kind of problems are occurring in the field. It may be information about etc. Status and / or maintenance data 64 may also be stored. This data 64 may include the current status of a particular embedded device 24 and / or a larger group of embedded devices. It may include maintenance history as well as planned maintenance activities in the future. Of course, those skilled in the art will appreciate that other data or information may be collected by the data collector 32. FIG. 4 merely illustrates the types of information that may be collected and stored by the data collector 32 and is not intended to limit the broad scope and usefulness of this embodiment.

  FIG. 5 is a block diagram of modules and data or information that may be used by the control / monitoring service 34. An information database 66 containing embedded devices 24 that need to be controlled and / or monitored can be used. Information in this database 66 may include device identification, routing information, location, device function, and the like. In addition, this database 66 may also include what control must be achieved for each device and the specific control commands that must be transmitted. One skilled in the art will recognize that data relating to or associated with the embedded device 24 may be stored in this database 66. Needless to say, this database 66 may actually be many databases or many files.

  Notification database 68 may include owner information and technical contact information. For example, for each device 24 being monitored and / or controlled, there may be not only a technical contact person to contact when a particular event occurs, but also a listed owner who will probably pay for the service. For example, if the embedded device 24 stops functioning, the control / monitoring service 34 may be instructed to immediately contact a technical contact person via a pager, e-mail, phone, etc.

  The management module 70 may manage control and / or monitoring operations by reading or reading data indicating which actions should occur, or writing or writing any output data. The communication module 72 can process communication functions. A separate monitoring function 74 is accessed and used to monitor the embedded device 24. For example, a library of monitoring functions 74 may be compiled to access and execute when monitoring various embedded devices 24. Typically, when an engineer develops software to monitor a particular type of embedded device 24, these functions for monitoring can be used to monitor the bias 24 with the same or similar type of implant. Can be reused at Similarly, the control function 76 may be usable and may be reused with similar types of devices 24.

  FIG. 6 is a block diagram depicting the major hardware components typically utilized in the embedded device 24 or embedded system, and embodiments herein. Embedded device 24 typically includes a processor 78 or an embedded computer 78 in electronic communication with input device 80 and / or output device 82. The embedded computer 78 is operatively connected to an input 80 device and / or output device 82 that can be in electronic communication with the embedded computer 78, or in other words, to a device that can input and / or output in the form of electrical signals. Is done. Sometimes the input device and output device (s) 80, 82 and the embedded computer 78 or processor 78 are housed together in the same physical structure. Input and / or output data that is transmitted and / or received may be referred to herein as interface data.

  FIG. 7 is a block diagram depicting the major hardware components typically utilized in the embedded device network 26 and embodiments herein. The embedded device network 26 typically includes a host computer 84 or gateway computer 84 that is networked with one or more embedded devices 24. The host computer 84 serves as a gateway between the embedded device 24 and other computers (eg, other computers on the computer network 22). In the present embodiment, the systems and methods herein are used to access a networked computer system in which a host computer 84 is connected to one or more embedded devices 24. Typically, the embedded device 24 includes an embedded computer 78 connected to input devices and output devices 80, 82. In particular, in this embodiment, the embedded computer 78 is typically a microcontroller (not shown). However, the functions and processes normally performed by a microcontroller can be performed by a larger processor, regardless of whether they are part of a larger controller or a typical computer system. It will be understood by those skilled in the art.

  The embedded computer 78 is typically remote from the host computer 84 in that the embedded computer 78 and the host computer 84 can each function independently. In many embodiments, the host computer 84 is at a different location than the embedded computer 78, but the term “distant” does not necessarily mean that the embedded computer 78 is at a different location than the host computer 84. Those elements described as being stored and / or implemented by the remote computer 78 could be stored and / or implemented in the host computer 84 in some situations.

  The system and method have a wide range of applications for many types of computer networks. In general, the embodiment of the embedded device service providing apparatus 20 provides monitoring and / or control of the embedded device 24. The embedded computer 78 is operatively connected to input and / or output devices 80, 82 that can be in electronic communication with the remote controller 78, or in other words to devices that can input and / or output in the form of electrical signals. The service providing apparatus 20 transmits and / or receives input and / or output data, thereby establishing communication with the embedded device 24 to interact with the embedded device 24.

  The gateway computer 84 or the host computer 84 is a widely defined digital computer. The embedded device 24 or embedded system 24 includes a digital computer, but does not have typical input and / or output devices such as a keyboard, mouse and / or monitor. A computer as used herein is any device that includes a digital processor capable of receiving and processing data. Computers include microcontrollers, handheld computers, personal computers, servers, mainframes, supercomputers and any variants or related devices.

  Input and output devices 80, 82 include any component, element, mechanism, device, etc. that can receive and / or generate electrical signals. Examples of devices that fall within the term device include vending machines, telephones, door locks, temperature sensors, motors, switches, lights, and the like.

In the current design, the gateway computer 84, typically, Linux (registered trademark), an IBM compatible personal computer running Microsoft Windows (registered trademark) 95/98/2000 or Microsoft Windows (registered trademark) NT operating system.

  One possible item that may be used here with embodiments is a vending machine (not shown). Many vending machines include one or more microcontrollers for controlling various parts of the vending machine. These microcontrollers fall within the scope of embedded computers. Input and output devices emit buttons to select items from the vending machine, a switch to allow the user to drop those items, a light to indicate which items are exhausted, and coins For example, a coin change release. As is known in the art, this vending machine embodiment includes input and output devices 80, 82 and remote computer (s) integrated within the same structure. One skilled in the art will also recognize that the embedded computer 78 may have separate structures for its attached input device and output device (s) 80,82. Many modern devices are equipped with embedded microcontrollers, for example mobile phones, pagers, etc. are equipped with embedded microcontrollers.

  The host computer 84 or gateway computer 84 may be connected to the embedded device 24 through a variety of connections including RS232, RS485, modem, power line, wired connection, wireless connection, and the like. Similarly, the embedded computer 78 may be connected to the input and output devices 80, 82 in a variety of ways. As mentioned, the remote computer 78 typically includes a microcontroller (not shown). Microcontrollers often have input / output ports for communicating with external devices. The specific microcontroller specification often determines how the device is connected to the microcontroller. Those skilled in the art understand how different devices are connected to a computer, whether they are embedded computers, standard desktop computers, mainframes, or the like.

  FIG. 8 depicts a block diagram of the main hardware and software components of an embodiment of the embedded device network 26. As shown, the hardware elements of FIG. 8 correlate with the hardware elements of FIG. Those skilled in the art have a wide variety of ways to interconnect various hardware components, and one or more of the hardware elements move functionality from one hardware element to another It will be appreciated that there are a variety of configurations that may be eliminated by doing so.

  According to this embodiment, the user can monitor and / or control the service provided by the embedded device 24 through the service providing apparatus 20. The services of the embedded devices 24 may be exposed by the embodiments so that they can be accessed efficiently over the computer network 22.

  In this embodiment, data from input devices and / or output devices 80, 82 is read and / or written through input port / output port 86. Embedded application program 88 includes executable instructions that connect directly to these input and / or output ports 86. Typically, the embedded application 88 has a main loop that is repeated many times. Of course, an embedded application developer may write an application that does not have a main loop that is continuously iterated. The principles here apply to those applications that do not have a main loop, and could provide substantially the same benefits as realized in this embodiment.

Through software executed on the embedded device service providing apparatus 20, the user may desire to access a specific service provided by the embedded device 24. Services include various functions, variables, events and / or files. For example, a user may wish to execute a specific function, access a specific variable, check a specified event, or access a specific file. In the current design, services that may need access are identified and listed. Service identification also includes information about a particular service. Identification of a particular service can be accomplished in a variety of ways. For example, in the current design, the service table 90 can be stored in the embedded computer 78. Service table 90 may be stored as a file, or it may be stored as static data compiled by application 88, or it may be stored on remote computer 78 in an external storage device (not shown). . Those skilled in the art will appreciate that there are a variety of ways to store basic information about a particular service provided by application code running on the embedded computer 78. Table 2 includes pseudo code indicating what kind of information may be stored in the service table 90.

  As depicted in Table 2, the service table 90 includes the name or identification of the service, the type of service (eg, whether it is a function, a variable, an event, a file, etc.), It may include the input parameter type, if any, the return type, if any, and the service address. The information about function FunctionA shown in line (2A) is that it is a function, it takes a word as an input parameter, it returns nothing (void), and its address is indicated by & FunctionA. It is drawn to show that. Line (2B) shows information about another function FunctionB. Information related to the variables is shown in rows (2C) to (2D). Information about the event is shown in rows (2E) to (2F). An event may be any type of data. For example, an event may be a variable, a specific register, an interrupt, etc. Events may be particularly useful for items that occur asynchronously. Asynchronous examples of events include alarms that suddenly sound or external LEDs change. Information about a particular file is depicted in lines (2G) and (2H).

  By storing information about a specific service in the remote computer 78 or the embedded device 24, the software in the embedded device service providing apparatus 20 can easily check which services are available in the embedded device 24. Normally, application code 88 defines a service. The service table 90 functions to provide information about a specific service, and whether the information is valid for the user of the host computer 84, valid for the service providing apparatus 20, or the requester in the entire computer network 22. Would be effective. The function table 98 can also be provided by the embedded computer 78.

  In the current design, the embedded interface module 92 provides access between software running on the embedded computer 78 and software running on the host computer 84 and / or access to software running on the embedded device service provider 20. provide. In the present embodiment, interface module 92 uses information in service table 90 to access the desired service at remote computer 78. Further, in the presently preferred embodiment, interface module 92 is reentrant code.

  Interface module 92 communicates through communication port 94. Currently in design, the connection module 96 provides communication using the communication port 94. However, those skilled in the art will recognize that the interface module 92 may include the code necessary to connect directly with the communication port 94 at the remote computer 78. The communication module 96 or code can access the communication port, ensuring that data is provided to the communication port 94 as appropriately sized and formatted pieces, and that data received from the communication port 94 is read correctly from the port 94. To do.

  The host computer 84 includes a communication port 100 that communicates electronically with the communication port 94 of the embedded device 24. As described above, there are a variety of such ports that can be used with a computer that can connect to a remote computer port and / or an embedded computer port. Communication module 102 provides functions similar to those provided by communication module 96 of embedded computer 78. The communication module 102 correctly formats the data written to and read from the communication port 100.

  Host computer 84 can access services provided by embedded computer 78 and embedded device 24. In this embodiment, a part of the function table 98, that is, the information supported by the interface is retrieved from the embedded device 24 and based on it at the host computer 84 and / or at the service providing device 20 that substantially matches the service table 90. A list of services is created. A list of services at the host computer 84 is referred to in FIG. The service information 104 indicates which services are available on the embedded device 24 and in some cases which data types are used with individual services. This facilitates access to the embedded device 24 via the host computer 84.

  In the current design, the process is initially initiated at the host computer 84 that causes the service information 104 to be created and / or by the service provider 20. Device access controller 106 provides this initial instruction in the current design.

  As described above, embodiments may provide access to services of the embedded device 24 to computers that are in electronic communication with the computer network 22 and to the service providing apparatus 20. In order to facilitate access by a computer, the host computer 84 and / or the service providing apparatus 20 may include a server. The web server 108 may be started with the host and the computer 84 and / or with the service providing device 20. Web server 108 may provide a web interface for services on embedded device 24. For example, the data and / or services of the embedded device 24 may be represented graphically through an HTML page. In this manner, device access controller 106 may create web pages (not shown) from services available on embedded device 24 and web server 108 may satisfy HTTP requests for these web pages.

  The device access server 110 may be included in the host and computer 84 and / or in the service provider 20 to satisfy client requests for the embedded device 24. In the current design, the device access server 110 accesses service information 104 that can be used by clients of client computers throughout the computer network 22 (eg, the data controller 32 and / or the control / monitoring service 34). Like that.

FIG. 9 depicts software components and data components that may be utilized in an embodiment of a service providing apparatus 20 for an embedded device. The service providing apparatus 20 includes an embedded device information database 112. The database 112 can be used by a computer that is in electronic communication with the computer network 22 or can be accessed by a computer that is in electronic communication with the computer network 22. A database as used herein refers to any one or more data structures used to store data. The database may be one or more files, such as a commercially available database package. The embedded information database 112 may include specific information needed by those skilled in the art to provide services to the embedded device 24. The embodiment of the embedded device information database 112 depicted in FIG. 9 depicts what kind of data may be stored in the embedded device information database 112. A device interface definition 114 that defines how to communicate with or connect to the embedded device 24 may be included. Table 3 includes pseudo code indicating what type of information is defined and may be included in the interface definition 114.

  As depicted in Table 3, the interface definition is the name or identification of the service, the type of service (eg whether it is a function, a variable, an event, a file, etc.), It may include the input parameter type if present, the return type if present, and the address of the service. The information about function FunctionA shown in line (3A) is that it is a function, it takes a word as an input parameter, it returns nothing (void), and its address is indicated by & FunctionA. It is drawn to show that. Line (3B) shows information about another function FunctionB. The relevant information about the variables is shown in lines (3C) to (3D).

  Information about the event is shown in lines (3E) to (3F). An event may be any kind of data. For example, an event may be a variable, a specific register, an interrupt, etc. Events may be particularly useful for items that occur asynchronously. Asynchronous examples of events include alarms that suddenly sound or external LEDs change.

  Information about a particular file is depicted in lines (3G) and (3H). State information (3I) may also be included. The state information (3I) defines how the embedded device 24 can be in various states, and the information defines any state machine, such as the embedded computer 78. The operational information (3J) may indicate how the embedded computer 78 reacts and operates taking into account a particular set of inputs, outputs and / or states. Of course, other (3K) definition information may also be included as appropriate to those skilled in the art.

  The device type 112a data structure may include information about which embedded devices 24 are accessible and the logical groupings of these devices 24. The device function 112b data structure may include information about what function each particular embedded device 24 has, similar to the function table described above. The device registered 112c information may include information regarding which embedded device 24 is in contact with the service providing apparatus 20, which device's service has been paid, and the like. The device location 112d may indicate where the embedded device 24 is located, either in geographic terms or electronic terms (eg, phone numbers, IP addresses, routing information, etc.).

  The information in the embedded device information database 112 may be created without accessing the embedded device 24 or it may be created from information obtained from the embedded device 24.

  The embodiments here may also implement security measures. For example, there may be an embedded device and / or a specific service of the embedded device 24 that must be accessed only by an entity with appropriate authority. A more specific example of this is a vending machine. Vending machines may need to be accessed only by certain entities, or it may change certain items, drop certain items without payment, or not purchase certain items, for example May have certain functions that must be accessed only by authorized entities, such as isolating. In order to provide appropriate authentication and access to the embedded device 24, the service providing apparatus 20 may include a security code 112e or information for verifying proper client access. The username and password may be stored in security code 112e to confirm proper authentication.

  The device for updating the 112f information may be a listing of the embedded device 24 that requires some kind of update. The transfer data 112g may include where data from or with respect to the embedded device 24 should be transferred.

  Another database 116 may be used by the service provider 20 to store information regarding entities, information, etc. in the computer network 22, and / or information in this database 116 may be used by the embedded device 24. May be done. The service information database 116 may include not only the manufacturer data 116b but also the manufacturer location 116a. Further, it may store information provider location 116 c and information data 116 d provided by information provider 30. Data collector location 116e may be stored along with what data is requested by data collector 32. The control / monitoring service location 116g and its request 116h may be stored. Control / monitor request data 116h may include schedule data 116i indicating which devices must be controlled / monitored and how often they must be controlled / monitored. Schedule data 116i may include embedded device identification and routing data.

  Further, other collected data 116j may be stored in the service information database 116. In this embodiment, the stored location is in the form of an IP address, but it will be appreciated by those skilled in the art that other types of data may be stored that would indicate how to contact a particular entity. I will.

  The information collection manager module 118 may manage data stored in and read from the service information database 116. Similarly, the embedded device manager 120 may manage data stored in and read from the embedded device information database 112. The administrator module 122 may coordinate the operation of the service providing apparatus and communication between the management modules 118 and 120 and other modules included with the service providing apparatus 20.

  As described with respect to FIG. 8, the web server 124 and the device access server 126 may be included in the service providing apparatus 20 to facilitate providing the embedded service 24 or services for the embedded device 24. . Computer network communication module 128 may process communications achieved via computer network 22. The embedded device communication module 130 may process communication with the embedded device 24. Embedded device communication module 130 may include both hardware and software components. For example, when the embedded device 24 can directly dial in to the service providing apparatus 20, the embedded device communication module 130 not only includes communication software for processing incoming calls and data communication but also a modem bank (not shown). May be included. However, the embedded device communication module 130 may use other communication hardware shared by other resources. In this case, the embedded device communication module 130 will typically include software for handling the communication that it must receive. Those skilled in the art will recognize many communication packages and alternatives, both hardware and software, that may be utilized in embodiments of the service providing device 20.

  FIG. 10 is a block diagram depicting a system 132 for providing services to the embedded device 24. As shown, the system 132 may include a plurality of embedded device service providers 20 that are coordinated by the telephone exchange 134. Telephone exchange pole 134 may coordinate communication with manufacturer 28, information provider 30, data collector 32, and control / monitoring service 34 via computer network 22. The individual service providing devices 20 of the embedded device 24 may be located at various locations to serve properly the embedded device 24 being used in the field. Depending on the particular embedded device 24, some service providing devices 20 may need to be closer to the embedded device 24. The other service providing devices 20 need not be in close proximity, but may only require an electronic connection regardless of whether they are physically close or far away from the embedded device 24.

  FIG. 11 is a flow diagram depicting the steps of an embodiment method for servicing a plurality of embedded devices 24. Electronic communication is provided 136 between the service providing apparatus 20 for the embedded device and the embedded device 24. A message is then received from the embedded device 24 (138). The embedded device 24 is identified using the received message (140). This identification is either a specific embedded device 24 or the type of embedded device 24. The service providing apparatus 20 accesses the embedded device information database (142). In this embodiment, the service providing apparatus 20 can specify the embedded device 24 after accessing the embedded device information database 112. Thus, those skilled in the art will appreciate that many of the steps herein may be performed in a variety of orders to achieve substantially similar results. The service providing apparatus 20 may transmit a transmission message to the embedded device 24 (144) and store device information describing the transaction (146). Information about the transaction (about the message (s) sent or received) may be used for billing and issuance purposes.

  Other steps may also be performed when implementing this embodiment. For example, newly acquired information from a computer network (stored in the service information database 116) may be linked to specific information in the embedded device information database 112. Accordingly, the service providing apparatus 20 will notice updated information when dealing with a particular device 24 or device type. Messages received from the embedded device 24 may be parsed to obtain an embedded device identifier, which may be a number, text string, etc. The method practiced here may also use control / monitoring request schedule data to monitor or control the embedded device.

  FIG. 12 is a flow diagram depicting the steps of an embodiment method for providing services to multiple embedded devices 24. The requester (user, company or other entity) asks the embodiment of the service provider 20 to monitor and / or control one or more embedded devices 24 (148). The requester provides the service providing device 20 with the location (whether it is an electronic address or a physical location) or identification of the embedded device 24 (150). The service provider 20 obtains any data or software updates that may be needed by the embedded device 24 (152). This may be done by accessing the manufacturer's 28 website.

  The service providing apparatus 20 then enters an iterative loop to control / monitor the embedded device 24. The providing apparatus 20 acquires the next device 24 for monitoring or controlling (154). Depending on whether this is the first iteration through a specific list of devices to monitor / control, whether this step acquires the next device in the specific list or acquires the first device It can be either. Next, the service providing apparatus 20 transmits a message to the device (156) and establishes communication. The providing apparatus 20 requests data 158 that may be interface data from the device, and stores the acquired data. When the control is requested, the service providing apparatus 20 transmits control data to the device 24 (162). This control data may include instructions or instructions for the device 24 to facilitate control. When the requester requests a report or status, the service providing apparatus 20 transmits the report or status to the requester (164). Then, the service providing apparatus 20 acquires the next device and repeats the steps periodically for each additional device.

  Embedded Micro Internetworking Technology (EMIT) software aims to move most of the software from the embedded microcontroller and distribute it to more capable computers on the network. It was also developed to take advantage of Internet technology.

  The use of EMIT software requires a variety of components, including customer embedded applications, emMic software (correlated to embedded interface modules), and customer monitoring / control applications. These embedded environments include embedded systems, host computers, and client computers.

  Referring now to FIG. 13, a block diagram of the major components of an additional embodiment is depicted. As can be seen in FIG. 13, this view is similar to FIG. 1 described above. Accordingly, it will be appreciated that much of the above description of FIG. 1 and other figures applies equally to the embodiment illustrated in FIG. However, much of this description will not be repeated for the sake of brevity.

  The embodiment shown in FIG. 13 includes an embedded device service providing apparatus 220 that may be similar to and / or identical to the service providing apparatus 20 described above. However, in the embodiment illustrated in FIG. 13, the service providing device 220 is described above in that the service providing device 220 is not in direct electronic communication with the one or more embedded devices 24. Different from the service providing apparatus 20. Rather, the service provider 220 communicates with the embedded device 24 through the computer network 22 and a message store / transmitter (“MSTC”) 202, as described in more detail below.

  The MSTC 202 is a device or component that communicates with the computer network 22. Accordingly, various types of hardware and software known in the art may be used or included as part of the MSTC 202. In some embodiments, the MSTC 202 comprises a mail server 204 that communicates with the computer network 22 by sending and / or receiving email messages over the computer network 22. In other embodiments, the MSTC 202 may comprise a message queue 206 that sends / receives messages over the network 22. Of course, those skilled in the art will recognize that other types of devices may also be used.

  Further, the MSTC 202 communicates with the service providing apparatus 220 via the communication network 22. In some embodiments, this communication occurs via a computer network communication module 228 that can be added to the service provider 220. In general, computer network communication module 228 is a component that is specifically designed / programmed to handle communications achieved over computer network 22 and is similar to computer network communication module 128 described above. And / or may be the same. In general, the computer network communication module 228 includes various software and / or hardware components that facilitate communication and / or allow communication to occur via the network 22.

  The embedded device communication module 230 may be added to the service providing apparatus 220 and may be used to process communication with the MSTC 202. More specifically, the embedded device communication module 230 may be used to process / interpret information for communications received from the MSTC 202 and / or to determine appropriate / necessary responses.

  Referring now to FIG. 14, a block diagram depicts a system 232 for providing services to the embedded device 24. The system illustrated in FIG. 14 is similar to the system 132 outlined above in connection with FIG. However, system 232 includes the system described above and one or more service providing devices 220 that are designed to communicate indirectly with embedded device 24 ′ via computer network 22 ′ and MSTC 202. Is different. As illustrated in FIG. 14, the service providing apparatus 220 may be configured such that it can communicate directly with other embedded devices 24 as described above.

  In FIG. 14, the computer network 22 ′ is shown as a separate and distinct element from the computer network 22. However, such representations are only made for clarity of the drawings and should not be construed as limiting. Other embodiments in which the computer network 22 'is the same as the computer network 22 may also be made.

  The system 232 shown in FIG. 14 is configured such that the telephone exchange 134 communicates with the MSTC 202 via the network 22 '. Of course, other embodiments have been made in which the telephone exchange 134 communicates only with the service provider 220 that instead transmits / forwards information transmitted by the telephone exchange 134 to the MSTC 202 via the network 22 '. Good.

  Referring now to FIG. 15, a method by which the service provider 220 can be used to provide services to the embedded device 24 is depicted. In particular, FIG. 15 is a flow diagram depicting the steps of an embodiment method 300 for servicing multiple embedded devices 24. First, electronic communication is provided between the service providing apparatus 220 for the embedded device and the communication network 22 (302). Next, the message transmitted from the MSTC 202 is received by the service providing apparatus 220 (304). In general, this message sent by the MSTC 202 includes information previously sent from the embedded device 24 to the MSTC 202. In some embodiments, this step is accomplished by having the embedded device 24 send an initial email to the MSTC 202 over the computer network 22. This initial e-mail and / or information derived from this initial e-mail is then transmitted / forwarded to the service providing device 22 through the network 22. Needless to say, other methods for causing the providing device 220 to receive information previously transmitted by the embedded device 24 to the MSTC 202 may also be used.

  The next step of the method 300 includes identifying a particular embedded device 24 that transmitted information to the MSTC 202 (306). This identification may be either a specific embedded device 24 or the type of embedded device 24. In some embodiments, the information is accomplished by including a device identifier in the message sent from the MSTC 202, as described in detail above. In additional embodiments, this identification may also require the device description to be included in messages sent from the MSTC 202. As described above, this type of device description may include information related to functions, variables, data types, events, files, and / or other information collected or stored by the embedded device 24.

  Still further embodiments may be constructed in which the embedded device 24 sends interface data to the MSTC 202 and the interface data is sent by the MSTC 202 to the service providing device 220. As described above, this interface data may be stored in the storage device by the providing device 220 and / or converted into monitoring data that may be transmitted to the requestor or other third party via the computer network 22. Good.

  Once the embedded device 24 is identified, the next step of the method 300 includes causing the provider 220 to access the embedded device information database (308). The service providing apparatus 220 transmits a transmission message including information that can be transmitted by the MSTC 202 to the identified embedded device 24 to the MSTC 202 (310). Again, in some embodiments, this step is accomplished by having the provider 220 send an email message containing information to the MSTC 202 over the network 22. The MSTC 202 may send this email message to the embedded device 24 and / or the MSTC 202 may extract all or part of the information from the email and send a new communication to the embedded device 24.

  Some embodiments may also be made in which the message sent to the MSTC 202 includes control data designed to be sent by the MSTC 202 to the embedded device 24. As described in further detail above, this control data may be designed such that it interacts with computer code loaded into the embedded device to affect the operation and / or characteristics of the embedded device. In additional embodiments, the schedule data 116 i loaded into the service providing device 220 may determine when this periodic control data is sent to the MSTC 202. Computer program code updates (obtained from device manufacturers), updated service information, information obtained from information provider 30 (such as weather information), monitoring data, and / or other types of information / Other types of information including data may also be sent to the MSTC 202 so that it can be sent to the embedded device 24.

  Finally, the last step of method 300 includes storing (312) device information describing the transaction. Information about the transaction (for the message (s) sent or received) may be used for billing issuance or other purposes.

  Other steps may be performed in practicing this embodiment. For example, newly obtained information from a computer network (stored in the service information database 116) may be linked to specific information in the embedded device information database 112. In this way, the service providing apparatus 220 will notice updated information when processing a particular device 24 or device type. Messages received from the embedded device 24 may be parsed to obtain an embedded device identifier, which may be a number, text string, etc. The method practiced herein may also use control / monitoring request schedule data to monitor or control the embedded device.

  FIG. 16 is a flow diagram depicting the steps of an embodiment method 400 for providing services to multiple embedded devices 24. A requester (user, company, or other entity) asks an embodiment of the service provider 220 to monitor and / or control one or more embedded devices 24 (402). The requester provides the service provider 220 with the location or identification of the embedded device 24 (whether it is an electronic address or a physical location) (404). An example of identification of the embedded device 24 may be an email address. Service provider 220 obtains any data or software updates that may be required by embedded device 24 (406). This may be done, for example, by accessing the manufacturer's 28 website.

  The service providing device 220 then inputs an iterative loop to control / monitor the embedded device 24. The providing device 220 obtains the next device 24 to monitor or control (408). Depending on whether this is the first iteration through a specific list of devices to monitor / control, this step will acquire the next device in the specific list or acquire the first device It can be either.

  Instead, the service providing apparatus 220 sends a message to the MSTC 202 that communicates with the embedded device 24 (410). The providing apparatus 220 transmits a message from the device 24 to the MSTC 202 that requests data (412). Again, this message and / or the information contained therein is sent by the MSTC 202 to the embedded device 24. In some embodiments, the information requested by the service providing device 220 may be interface data and / or other data regarding the status / status of the embedded device 24.

  Once the embedded device 24 receives a request for information from the MSTC 202, the embedded device 24 sends a response (414) to the MSTC 202. Again, this response and / or information contained in the response is transmitted by the MSTC 202 to the service providing apparatus. If needed or desired, the service provider 220 stores the data / information transmitted by the embedded device 24 (416).

  When control of the embedded device 24 is requested, the service providing apparatus 220 transmits control data to the device 24 (418). This control data may include instructions or instructions for the device 24 to facilitate control. When the requester requests a report or status, the service providing apparatus 220 transmits the report or status to the requester (420). Then, the service providing apparatus 220 acquires the next device and repeats the steps periodically for each additional device.

  Although the methods listed above provide a specific order in which the steps may be performed, those skilled in the art may perform many steps herein in a variety of orders to achieve substantially similar results. You will recognize that.

  From the above description, it will be understood that the present embodiment provides a service providing apparatus for an embedded device and / or an embedded system.

  The embodiments herein may be embodied in other specific forms without departing from their spirit or essential characteristics. The described embodiments are not limiting and are to be considered merely exemplary in all respects. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims should be admitted within their scope.

  While specific embodiments and applications of the invention have been illustrated and described, it should be understood that the invention is not limited to the precise configuration and components disclosed herein. Various modifications, changes and variations that may be apparent to those skilled in the art may be made in the arrangement, operation and details of the methods and systems of the invention without departing from the spirit and scope of the invention.

FIG. 2 is a block diagram depicting the main components normally utilized in the use of an embedded device and service providing apparatus for the embodiments disclosed herein. FIG. 6 is a block diagram of data that can be obtained from a device manufacturer. A block of data or information available from an information provider. FIG. 3 is a block diagram of data or information that can be collected by a data collector. FIG. 2 is a block diagram of modules and data or information that may be used by a control / monitoring service. FIG. 2 is a block diagram depicting major hardware components that are typically utilized in embedded devices. FIG. 2 is a block diagram depicting the main hardware components typically utilized in an embedded device network. FIG. 2 is a block diagram of the main hardware and software components of an embodiment of an embedded device network. Fig. 5 illustrates software components and data components that may be utilized in an embodiment of a service providing apparatus for an embedded device. 1 is a block diagram depicting a system for providing services to an embedded device. 2 is a flow diagram depicting the steps of an embodiment method for servicing multiple embedded devices. 2 is a flow diagram depicting the steps of an embodiment method for servicing multiple embedded devices. It is a block diagram which depicts the main components normally utilized in the use of the service providing apparatus of the new embodiment and how it may be used. FIG. 3 is a block diagram depicting another embodiment of a system for providing services to an embedded device. 6 is a flow diagram depicting steps of another embodiment method for providing services to multiple embedded devices. 6 is a flow diagram depicting steps of another embodiment method for providing services to multiple embedded devices.

Explanation of symbols

20 Service Provider 22 Computer Network 24 Embedded Device 26 Device Network 28 Device Manufacturer 30 Information Provider 32 Data Collector 34 Control / Monitoring Service 36 Embedded Software Update 38 Function Table 40 Device Information 42, 52 Other Information 44 Weather Information 46 Date / Time information 48 Barcode information 50 Status information 54 Meter reading 56 Billing issuance data 58 Rate information 60 Usage data 62 Performance information 64 Status / maintenance data 66 Information database 68 Notification database 70 Management module 72 Communication module 74 Monitoring function 76 Control function 78 Embedded computer 80 Input device 82 Output device 84 Gateway computer 86 Input / output port 88 Fill Embedded application program 90 service table 92 interface module 94, 100 communication port 96, 102 communication module 104 service information 106 device access controller 108 web server 110 device access server 112 embedded device information database 114 device interface definition 116 service information database 118 information collection manager Module 120 Embedded Device Manager 122 Administrator Module 124 Web Server 126 Device Access Server 128 Computer Network Communication Module 130 Embedded Device Communication Module 132 System 134 Telephone Switching Center

Claims (24)

A computer including communication hardware for communicating over a computer network, the computer including a storage device;
A computer network communication module for communicating with a computer via the computer network, the computer network communication module configured to communicate with a message storage / transmission device via the computer network, the message storage / transmission device comprising the computer network A computer network communication module capable of communicating with one or more embedded devices via
A database of service information obtained from the computer network that can be used by the embedded device through the message storage / transmission device;
A database interface module for accessing the service information in the service information database;
A service providing apparatus for an embedded device. The providing apparatus according to claim 1, wherein the message storage / transmission apparatus includes a mail server. The providing device according to claim 1, wherein the message storage / transmission device comprises a message queue. The providing apparatus according to claim 1, further comprising an information collection manager for searching the computer network and accessing and obtaining updated service information from the computer network. The providing apparatus according to claim 4, wherein the updated service information obtained from the computer network relates to a computer program code on an embedded device. The providing apparatus according to claim 4, wherein the updated service information obtained from the computer network is related to an embedded device location. The providing apparatus according to claim 1, further comprising an embedded device communication module that processes communication with the message storage / transmission apparatus. 8. The providing apparatus according to claim 7, wherein the embedded device communication module processes at least one communication from the message storage / transmission apparatus including an embedded device identifier. The providing apparatus according to claim 1, further comprising schedule data, wherein the schedule data includes an embedded device identification, and the schedule data is used to control monitoring of the embedded device. 2. The providing apparatus according to claim 1, wherein the providing apparatus acquires a device description from the message storage / transmission apparatus, and the device description has been transmitted from the embedded device to the message storage / transmission apparatus in the past. The providing device according to claim 10, wherein the device description is selected from a group consisting of a function, a variable, a data type, an event, and a file. The providing apparatus monitors the embedded device by periodically obtaining interface data previously transmitted from the embedded device to the message storage / transmission apparatus from the message storage / transmission apparatus, and the provision apparatus The providing device according to claim 1, wherein the interface data is stored in a device. The providing apparatus according to claim 12, wherein the providing apparatus stores monitoring data created from the received interface data, and the providing apparatus further provides the monitoring data to a requester through the computer network. The providing apparatus controls an embedded device by periodically transmitting control data to computer program code loaded into the embedded device to affect the operation of the embedded device, wherein the periodic transmission includes the 10. The providing apparatus according to claim 9, wherein the providing data is based on schedule data, and the control data is transmitted from the providing apparatus to the message storage / transmission apparatus, and then transmitted from the message storage / transmission apparatus to the embedded device. . The providing device further obtains the updated computer program code via the computer network, and notifies the embedded device of available updates, further through the message storage / sending device The providing apparatus according to claim 1, wherein the computer program code on the embedded device is updated by transmitting the computer program code to the embedded device. Communication hardware for communicating over a computer network, configured to communicate with a message storage / transmission device over the computer network, wherein the message storage / transmission device is one or more over the computer network Communication hardware that can communicate with other embedded devices,
Memory,
An embedded device information database including embedded device information, which can be used by a communication network; and
A service information database including service information obtained from the computer network, wherein the embedded device is usable through the message storage / transmission configuration win; and
A processor,
Receiving a message from the message storage / sending device having information previously received from the embedded device;
Identifying the embedded device that transmitted the information to the message storage / transmission device;
Accessing the embedded device information database;
Transmitting to the message storage / transmission device information to be transmitted later to the embedded device by the message storage / transmission device;
Storing device information describing the transaction;
A processor that executes instructions for implementing a method comprising:
An embedded device service providing apparatus comprising: The providing device according to claim 16, wherein the service information database further includes updated service information acquired via the computer network. The embedded device information database is
Link data that links specific embedded device information to specific updated service information;
Multiple embedded device identifiers;
Multiple function tables,
The providing device according to claim 16, further comprising: The providing apparatus according to claim 18, further comprising schedule data, wherein the schedule data includes embedded device identification and routing data, and the schedule data is used to control monitoring of a plurality of embedded devices. 20. The embedded device information database further comprises interface data received from the message mechanism and transmission device, and the interface data has been previously transmitted from the embedded device to the message storage / transmission device. The providing device according to the description. 21. The providing apparatus according to claim 20, further comprising control data transmitted to the message storage / transmission apparatus and then transmitted to the embedded device, the control data being capable of affecting the operation of the embedded device. The providing apparatus according to claim 21, wherein the embedded device information database further comprises a plurality of files of updated computer program code that are obtained via the computer network and that can be used to update the program code on the embedded device. . A method for providing services to multiple embedded devices, comprising:
Providing electronic communication between a service providing apparatus for an embedded device and a communication network;
Receiving from the message storage / transmission device communication including information previously transmitted by the embedded device to the message storage / transmission device via the communication network;
Identifying the embedded device that transmitted the information to the message storage / transmission device;
Accessing the embedded device information database;
Transmitting a communication including information to be transmitted later to the embedded device by the message storage / transmission device to the message storage / transmission device via the communication network;
Storing device information describing the transaction;
Including methods. One or more service providing apparatuses for the embedded device, each service providing apparatus for the embedded device comprising:
A computer including communication hardware for communicating over a computer network, the computer including a storage device;
A database,
A computer network communication module for communicating with a computer via the computer network, the computer network communication module configured to communicate with a message storage / transmission device via the computer network, the message storage / transmission device comprising the computer network A computer network communication module capable of communicating with one or more embedded devices via
A database interface module for accessing information in the database;
A central providing device in electronic communication with the plurality of service providing devices for an embedded device, for providing communication between the embedded device and the service providing device for the embedded device, and the embedded device A central providing device operable to coordinate collecting updated information from the computer network in relation to, further coordinating disseminating the updated information to an embedded device;
A system for providing services to an embedded device comprising:

Images