DETAILED DESCRIPTION

[0020] Exemplary embodiments of the present invention and their advantages may be understood by referring to FIGS. 1-4 b , like numerals being used for like corresponding parts in the various drawings.

[0021] FIG. 1 shows a first exemplary embodiment of a system 100 which includes a first storage device 130 (e.g., RAM, hard drive, CD-ROM, etc.) that provides thereon a first software arrangement 110 , and has a first processing system 120 (eg., a first microprocessor). Referring to FIGS. 1 and 3 , this first software arrangement 110 may be executed by the first processing system 120 to convert a proprietary language Device Description file 180 shown in and/or a DDL source code associated with a certain/particular type of a field device 170 (e.g., a smart field device, such as a pressure sensor, a temperature sensor, a flow-rate sensor, etc. that are capable of performing operations) into a non-proprietary language Device Description file 190 (e.g., a non-binary coded Device Description file, such as an Extensible Markup Language (“XML”) Device Description file).

[0022] This first software arrangement 110 may also be executed by the first processing system 120 to associate an Extensible Stylesheet Language (“XSL”) Device Description file 195 (e.g., an XSL Device Description file including a script-type language source code, such as a Javescript® to language source code, a Visual Basic® language source code, etc.) with the non-proprietary language Device Description file 190 . The first software arrangement 110 may configure the first processing system 120 to transmit the XSL Device Description file 195 and the associated non-proprietary language Device Description file 190 . The XSL Device Description file 195 may be associated with the particular type of the field device 170 . Moreover, the particular script-type language source code can be located between tags of the XSL Device Description file 195 , and may include a code associated with one or more methods of implementing the field 170 and/or one or more functions performed by the field device 170 .

[0023] In the exemplary embodiment shown in FIG. 1 , the system 100 can also include a second storage device 135 (e.g., RAM, hard drive, CD-ROM, etc.) that stores thereon a second software arrangement 115 , and has a second processing system 140 (e.g., a second microprocessor). Moreover, the XSL Device Description file 195 and the associated non-proprietary language Device Description file 190 (both shown in FIG. 2 a ) may be transmitted to the second processing system 140 . Referring to FIGS. 1 and 2 a , the second software arrangement 115 can convert the non-proprietary language Device Description file 190 and the XSL Device Description file 195 into a platform-independent file/page 165 (e.g., a Hypertext Markup Language (“HTML”) file/page) having the script-type language source code embedded therein. The platform-independent file/page 165 can include one or more parameters associated with the particular type of the field device 170 , a link 175 to one or more methods for implementing the field device 170 and/or one or more functions performed by the field device 170 , etc.

[0024] When the link 175 is selected by a user of the second processing system 140 , e.g., by clicking on the link 175 , the second software arrangement 115 may execute the script-type language source code, and can also invoke and execute an operation of a particular component 185 (e.g., an Object Linked Embedded for Process Control component) of the first processing system 120 through a remote process call (“RPC”) (e.g., a Web Service, DCOM, COBRA, etc.). The particular component 185 can establish a communication with the field device 170 , and implement/execute the one or more methods included in the script-type language source code, e.g., to configure the field device 170 and/or obtain data from the field device 170 . Moreover, the particular component 185 can transmit the data obtained from the field device 170 to the second processing system 140 through the RPC, such that the second processing system 140 can display such data to the user.

[0025] As described above, in any of the exemplary embodiments of the present invention, the first software arrangement 110 may be resident on the first storage device 130 (e.g., a memory device, a hard drive, etc.) of the first processing system 120 , and/or can also be stored on an external storage device. Instead of using the first software arrangement 110 , it is possible to utilize a hardware arrangement, a firmware arrangement and/or a combination thereof which can implement the techniques described herein. Similarly, the second software arrangement 115 may be resident on the second storage device 135 (e.g., a memory device, a hard drive, etc.) of the second processing system 140 , and/or can also be stored on an external storage device. Similarly to the first software arrangement 110 , it is possible to utilize a hardware arrangement, a firmware arrangement and/or a combination thereof instead of using the second software arrangement 115 .

[0026] Web Services that can be utilized by the exemplary embodiments of the arrangements and methods of the present invention are programmable application logic accessible using standard Internet protocols. Unlike conventional component technologies, Web Services are not accessed via object-model-specific protocols, such as the Component Object Model, Remote Method Invocation, or Internet Inter-ORB Protocol. In contrast, Web Services may be accessed via ubiquitous Web protocols and data formats, such as Hypertext Transfer Protocol (“HTTP”) and XML. Moreover, a Web Service interface may be defined in terms of messages which the Web Service accepts and/or generates, and the Web Service can be used by applications implemented in any language for any platform. In this manner, the Web Services may be platform-independent, language-independent, and reusable.

[0027] FIG. 2 a shows a second exemplary embodiment of a system 200 according to the present invention which is substantially similar to the first embodiment of the system 100 illustrated in FIG. 1 , except as indicated below. In this exemplary system 200 , during operation, the first processing system 120 may receive the proprietary language Device Description file 180 and/or the DDL source code associated with the particular type of the field device 170 from a third processing system. For example, and referring to FIG. 2 b , the third processing system 150 may be a processing system of a manufacturer of a particular field device, a developer of a host application, the Fieldbus Foundation®, etc.

[0028] Referring again to FIG. 2 a , after the first processing system 120 receives the proprietary language Device Description file 180 and/or the Device Description language source code, the first processing system 120 can convert the proprietary language Device Description file 180 and/or the DDL source code into the non-proprietary language Device Description file 190 . The first processing system 120 can also associate the XSL Device Description file 195 including the script-type language source code with the non-proprietary language Device Description file 190 , and transmit the XSL Device Description file 195 and the associated non-proprietary language Device Description file 190 to the second processing system 140 . The particular script-type language source code can include code associated with one or more techniques of implementing the field device 170 and/or one or more functions performed by the field device 170 .

[0029] Moreover, the second processing system 140 (e.g., a parser of the second processing system 140 ) can convert the non-proprietary language Device Description file 190 and the XSL Device Description file 195 into the platform-independent file/page having the script-type language source code embedded therein. The platform-independent file/page 165 can include one or more parameters associated with the particular type of the field device 170 , the link 175 to the one or more procedures or techniques for implementing the field device 170 and/or one or more functions performed by the field device 170 , etc. When the link 175 is selected by the user of the second processing system 140 , e.g., by clicking on the link 175 , the second processing system 140 may execute the script-type language source code, and can also invoke and execute the operation of the particular component 185 (e.g., the Object Linked Embedded for Process Control component) of the first processing system 120 through the RPC. The particular component 185 can establish a communication with the field device 170 and implement/execute the one or more methods included in the script-type language source code (e.g., to configure the field device 170 and/or obtain data from the field device 170 ). Moreover, the particular component 185 can transmit the data obtained from the field device 170 to the second processing system 140 through the RPC, such that the second processing system 140 may display such data to the user.

[0030] FIG. 2 c shows a third exemplary embodiment of a system 200 ′ according to the present invention, which is substantially similar to the second embodiment of the system 200 illustrated in FIG. 2 a and/or FIG. 2 b , except as indicated below. In this exemplary embodiment of the present invention, the first processing system 120 (e.g., the parser of the first processing system 120 ) may can convert the non-proprietary language Device Description file 190 and the XSL Device Description file 195 into the platform-independent file/page 165 by executing the script-type language source code, and can also internally invoke and execute the operation of the particular component 185 . The particular component 185 can establish the communication with the field device 170 , and implement/execute the one or more techniques or procedures included in the script-type language source code, e.g., to configure the field device 170 and/or obtain data from the field device 170 . Moreover, the particular component 185 can transmit the data obtained from the field device 170 to the second processing system 140 through the RPC in a platform-independent format, such that the second processing system 140 may readily display such data to the user.

[0031] It will be readily understood by those of ordinary skill in the art that the system 100 , 200 illustrated in FIGS. 1, 2 a and/or 2 b may be used to associate different non-proprietary language Device Description files with various corresponding XSL Device Description files. Also, that the non-proprietary language Device Description files and the corresponding XSL Device Description files may be associated with different types of the field devices.

[0032] FIG. 4 a shows a first exemplary embodiment of a method 400 a according to the present invention for converting the proprietary language Device Description file 180 and/or the Device Description language source code associated with the field device 170 into a non-proprietary language Device Description file 190 , and for associating the XSL Device Description file 195 with the non-proprietary language Device Description file 190 . Particularly, in step 410 , the proprietary language Device Description file 180 and/or the Device Description language source code associated with a certain type of the field device 170 is converted into the non-proprietary language Device Description file 190 (e.g., by the first processing system 120 ). Then, in step 420 , the non-proprietary language Device Description file 190 is associated with the XSL Device Description file 195 . The XSL Device Description file 195 includes the script-type language source code. Moreover, the XSL Device Description file 195 is associated with the particular type of the field device 170 .

[0033] FIG. 4 b shows a second exemplary embodiment of a method 400 b according to the present invention. The exemplary method 400 b includes steps 410 and 420 of the method 400 a of FIG. 4 a , and also has steps 430 and 440 . In step 430 , the non-proprietary language Device Description file 190 and the XSL Device Description file 195 are converted (e.g., by the second processing system 140 ) into the platform-independent file/page 165 (e.g., a HTML file/page) having the script-type language source code embedded therein. Further, in step 440 , the script-type language source code may be executed (e.g., by the second processing system 140 ). Specifically, the script-type language source code may be executed and transmitted to the particular component 185 . The particular component 185 then may a communication with the field device 170 , and implement/execute the one or more techniques/procedures included in the script-type language source code (e.g., to configure the field device 170 and/or obtain data from the field device 170 ). Moreover, the particular component 185 can transmit the data obtained from the field device 170 to the second processing system 140 , such that the second processing system 140 may display such data to the user.

[0034] While the invention has been described in connecting with preferred embodiments, it will be understood by those of ordinary skill in the art that other variations and modifications of the preferred embodiments described above may be made without departing from the scope of the invention. Other embodiments will be apparent to those of ordinary skill in the art from a consideration of the specification or practice of the invention disclosed herein. It is intended that the specification and the described examples are considered as exemplary only, with the true scope and spirit of the invention indicated by the following claims.

[0035] FIG. 2 b shows a second exemplary embodiment of a system 200 according to the present invention which is substantially similar to the first embodiment of the system 100 illustrated in FIG. 1 , except as indicated below. In this exemplary system 200 , during operation, the first processing system 120 may receive the proprietary language Device Description file 180 and/or the DDL source code associated with the particular type of the field device 170 from a third processing system. For example, and referring to FIG. 2 b , the third processing system 150 may be a processing system of a manufacturer of a particular field device, a developer of a host application, the Fieldbus Foundation®, etc.