Source: http://www.google.com/patents/US6836892?dq=5319712
Timestamp: 2016-06-25 20:27:13
Document Index: 475924727

Matched Legal Cases: ['art. 2', 'art. 4', 'art 114', 'art 121', 'art 151', 'art 131', 'art 119', 'art 116', 'art 152', 'art 132', 'art 114', 'art 151', 'art 116', 'art 152', 'art 119', 'art 152', 'art 121', 'art 151', 'art 114', 'art 114', 'art 119', 'arts 116', 'art 116', 'art 121']

Patent US6836892 - Apparatus and method for use in distributed computing environment for ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsIn an object request broker (ORB) for processing requests or responses among distributed objects, a method and an apparatus for realizing a high processing speed of a process to convert from data (communication data) which is used in communication among the ORBs and is not specific to particular computers...http://www.google.com/patents/US6836892?utm_source=gb-gplus-sharePatent US6836892 - Apparatus and method for use in distributed computing environment for converting data format between program language-specific format used in respective computers and stream format used for communication among computersAdvanced Patent SearchPublication numberUS6836892 B2Publication typeGrantApplication numberUS 10/603,694Publication dateDec 28, 2004Filing dateJun 26, 2003Priority dateApr 28, 1998Fee statusLapsedAlso published asUS20040031037Publication number10603694, 603694, US 6836892 B2, US 6836892B2, US-B2-6836892, US6836892 B2, US6836892B2InventorsMikio Ikoma, Youji Fujihara, Takahiro TanidaOriginal AssigneeHitachi, Ltd.Export CitationBiBTeX, EndNote, RefManPatent Citations (4), Referenced by (24), Classifications (16), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetApparatus and method for use in distributed computing environment for converting data format between program language-specific format used in respective computers and stream format used for communication among computers
US 6836892 B2Abstract
In an object request broker (ORB) for processing requests or responses among distributed objects, a method and an apparatus for realizing a high processing speed of a process to convert from data (communication data) which is used in communication among the ORBs and is not specific to particular computers into a data format (program data) which is specific to a program language. A correspondence between the communication data which was transmitted and received by the ORB and the conversion into the program data corresponding thereto is stored in a cache which can be called at a high speed. When a receiving process of the same communication data cached at the second and subsequent times or a transmitting process of the program data occurs, the cached conversion result is used.
What is claimed is: 1. An apparatus for converting data of a first data format used on a particular computer into data of a second data format which is common to a plurality of computers in a distributed computing environment, comprising:
a caching part for storing data of the first data format and corresponding data of the second data format and correspondence between the data of the first data format and the corresponding data of the second data format; a marshalling part for discriminating whether at least a part of the data of the first data format to be converted has been stored in said caching part or not, for converting said data of the first data format to be converted into the data of the second format by using the correspondence stored in said caching part such that; for a part or whole of said data of the first format to be converted that matches the data of the first format stored in said caching part, conversion is made by using the correspondence and that; for another part of said data of the first format to be converted that does not match the data of the first format stored in said caching part, conversion is made with or without using said caching part depending upon a data type of said unmatched part of the data of the first data format; and a cache registering part for registering said converted data into said caching part. 2. An apparatus according to claim 1, wherein said first data format is a data format specific to a particular program language and said second data format is a stream data format.
3. An apparatus for converting data of a second data format which is common to a plurality of computers into data of a first data format used on a particular computer in a distributed computing environment, comprising:
a caching part for storing data of the second format and corresponding data of the first format and correspondence between the data of the second format and the corresponding data of the first format; an unmarshalling part for discriminating whether at feast a part of the data of the second data format to be converted has been stored in said caching part or not, for converting said data of the second data format to be converted into the data of the first data format by using the correspondence stored in said caching part such that; for a part or whole of said data of the second format to be converted that matches the data of the second format stored in said caching part, conversion is made by using the correspondence and that; for another part of said data of the second format to be converted that does not match the data of the second format stored in said caching part, conversion is made with or without using said caching part depending upon a data type of said unmatched part of the data of the second data format; and a cache registering part for registering said converted data of the first data format into said caching part. 4. An apparatus according to claim 3, wherein said first data format is a data format specific to a particular program language and said second data format is a stream data format.
5. A method of converting client program data of a client program into request communication data common to a plurality of program languages or computers in order to request a processing task from said client program to a server program on a server in a distributed computing environment, comprising the steps of:
discriminating whether at least a part of said client program data exists in a cache of said client program or not by referring to said cache, said cache storing client program data and corresponding request communication data and correspondence between the client program data and the request communication data; converting said client program data into said request communication data by using the correspondence stored in said cache such that; for a part or whole of the client program data to be converted that matches the client program data stored in said cache, conversion is made by using the correspondence and that; for another part of said data of the client program data to be converted that does not match the client program data stored in said cache, conversion is made with or without using said cache depending upon a data type of said unmatched part of the data of the client program data; storing the request communication data into said cache as a conversion result when said data does not exist; and transmitting said converted requesting communication data to said server program. 6. A method according to claim 5, wherein said client program data is specific to a particular program language describing said client program and said common communication data is stream data.
7. A method according to claim 3, wherein said method is stored on a computer-readable medium as a computer readable program.
8. A method of converting request communication data which is transmitted from a client and is common to a plurality of program languages or computers into program data of a program language describing a server program which operates on a server in a distributed computing environment and processing a processing task requested by the client, comprising the steps of:
receiving said request communication data by an unmarshalling part in said server; discriminating whether at least a part of said request communication data exists in a cache of said server program or not by referring to said cache, said cache storing the request communication data and corresponding program data and correspondence between the request communication data and the program data; converting said received requesting communication data into the program data of the program language describing said server program by using the correspondence stored in said cache such that; for a part or whole of the request communication data to be converted that matches the request communication data stored in said cache, conversion is made by using the correspondence and that; for another part of said data of the request communication data to be converted that does not match the request communication data stored in-said cache, conversion is made with or without using said cache depending upon a data type of said unmatched part of the data of the request communication data; storing the program data into said cache as a conversion result when said data does not exist; and processing the processing task requested by said client on the basis of said converted program data. 9. A method according to claim 8, wherein said step of processing the processing task requested by said client on the basis of said converted program data further comprising the steps of:
processing the processing task requested by said client on the basis of said converted program data and forming the resultant program data; discriminating whether at least a part of said resultant program data exists in said cache or not by referring to the cache in said server program; converting said resultant program data by using the program data on said cache into response communication data which is common to the plurality of computers or program language when said data exists, while converting said data by determining attributes of said resultant program data when said data does not exist; storing the response communication data into said cache as a conversion result when said data does not exist; and transmitting said converted response communication data to said client program. 10. A method according to claim 8, wherein said program data of a program lanugage describing a server program is specific to a particular program language describing a server program.
11. A method according to claim 4, wherein said method is stored on a computer-readable medium as a computer readable program.
12. A method whereby a client program receives and processes response communication data which is transmitted from a server and is common to a plurality of computers or program languages in a distributed computing environment, comprising the steps of:
receiving said response communication data by said client program; discriminating whether at least a part of said response communication data exists in a cache of said client program or not by referring to said cache, said cache storing response communication data and corresponding client program data and correspondence between the response communication data and the client program data; converting said received response communication data into client program data by using the correspondence stored in said cache such that; for a part or whole of the response communication data to be converted that matches the response communication data stored in said cache, conversion is made by using the correspondence and that; for another part of said data of the response communication data to be converted that does not match the response communication data stored in said cache, conversion is made with or without using said cache depending upon a data type of said unmatched part of the data of the response communication data; and storing the client program data into said cache as a conversion result when said data does not exist. 13. A computer software product including a computer-readable medium having a computer readable program embodied in the medium for making program data to be transmitted subject to a marshalling process to generate request communication data, said medium having stored thereon:
a program code portion for comparing said program data to be transmitted with program data on a cache, said cache storing a pair of contents of said program data and contents of communication data corresponding thereto for every type of the program data; a program code portion for, when the contents of said program data to be transmitted and the contents of the program data on said cache are matched, comparing subsequent program data to be transmitted with said program data on said cache until a difference is detected; a program code portion for copying the communication data on said cache corresponding to the program data which is matched until said difference is detected into request communication data; a program code portion for, when a difference is detected between contents of certain program data to be transmitted and contents of the program data on the cache, forming corresponding communication data from the program data in which said difference is detected in accordance with a type of the program data in which said difference is detected; a program code portion for storing a correspondence between the program data in which said difference is detected and said formed communication data onto said cache; and a program code portion for, when there is no transmission program data to be compared, copying the formed communication data remaining on said cache into said request communication data. 14. A product according to claim 13, wherein said program code portion for forming the corresponding communication data from said program data in which the difference is detected further has:
a program code portion for discriminating whether the type of said program data in which the difference is detected is a basic type or a user definition type; and a program code portion for, when the type of said program data in which the difference is detected is said basic type, recognizing an architecture or an identifier of said program data in which the difference is detected and converting into the communication data. 15. A product according to claim 13, wherein said program code portion for forming the corresponding communication data from said program data in which the difference is detected further has:
a program code portion for discriminating whether the type of said program data in which the difference is detected is a basic type or a user definition type; and a program code portion for, when the type of said program data in which the difference is detected is said user definition type, recursively calling said marshalling process by using said program data in which the difference is detected as a parameter. 16. A computer software product including a computer-readable medium having a computer readable program embodied in said medium for making received request communication data subject to an unmarshalling process to generate output program data, said medium having stored thereon:
a program code portion for comparing said received request communication data with communication data on a cache in units of a predetermined communication data length, said cache storing a pair of contents of said received request communication data and contents of the communication data corresponding thereto for every type of the received request communication data; a program code portion for, when the contents of said received request communication data and the contents of the communication data on said cache are identical, comparing subsequent received request communication data with said communication data on said cache until a difference is detected; a program code portion for copying the communication data on said cache corresponding to the received request communication data which is matched until said difference is detected into said output program data; a program code portion for, when a difference is detected between contents of certain received request communication data and contents of the communication data on the cache, forming corresponding program data from said received request communication data in which said difference is detected in accordance with a type of said received request communication data; a program code portion for storing a correspondence between said received request communication data in which said difference is detected and said formed corresponding program data onto said cache; and a program code portion for, when there is no received request communication data to be compared, copying the formed corresponding program data remaining on said cache into said output program data. 17. A product according to claim 16, wherein said program code portion for forming the corresponding output program data in accordance with the type of said received request communication data in which the difference is detected further has:
a program code portion for discriminating whether the type of said received request communication data in which the difference is detected is a basic type or a user definition type; and a program code portion for, when the type of said received request communication data in which the difference is detected is said basic type, converting said data into the output program data by discriminating attributes of said received request communication data in which the difference was detected. 18. A product according to claim 10, wherein said program code portion for forming the corresponding output program data in accordance with the type of said received request communication data in which the difference is detected further has:
a program code portion for discriminating whether the type of said received request communication data in which the difference is detected is a basic type or a user definition type; and a program code portion for, when the type of said received request communication data in which the difference is detected is said user definition type, recursively calling said unmarshalling process to said received requesting communication data in which the difference is detected.
This is a continuation of prior application Ser. No. 09/299,644, filed Apr. 27, 1999, now abandoned.
The invention relates to method and apparatus for converting a computer-dependent data format (that is, computer-specific data format) when data is communicated among a plurality of computers. More particularly, the invention relates to a method of converting a program language-dependent data format (that is, program language-specific data format) which is used for communication among distributed objects on a plurality of computers for performing a distributed computing and is used in each computer into a stream data format which is used for communication among the computers. The invention also relates to method and apparatus for converting a stream data format which is used in communication among the computers into a program language-specific data format which is used in each computer.
Generally, when calling from a certain program to another program, a transmission and a reception of data are performed on the same computer by using an interface which depends on a specific operating system and a specific program language. On the other hand, in a distributed computing environment, a plurality of programs (distributed objects) can exist over a plurality of computers and can transmit and receive data. A distributed object which requests a process is called a client object. A distributed object which processes the request from the client object is called a server object. A function for accepting the request from the client object, retrieving a proper server object to process the request, communicating with the computer in which the server object exists, and calling the server object is called an object request broker (ORB). In the case where the client object and the server object communicate among a plurality of computers, the ORB performs a data exchange by using data of a neutral stream format which is not specific to the architecture of a particular computer, a particular operating system, and a particular program language. Therefore, in order to incorporate an ORB, it is necessary to provide a process (marshalling) for converting from a format which is specific to the architecture of particular computer, particular operating system, and particular program language into a neutral data stream and a reverse process (unmarshalling).
Generally, the server object residentially or persistently exists on a certain computer and processes requests from many and unspecified client objects a plural number of times. Each time the request from the client object comes, the unmarshalling process occurs. Each time a reply to the request is returned, the marshalling process occurs.
An example of the unmarshalling process and marshalling process will be described with reference to FIG. 7.
In FIG. 7, in the unmarshalling process, stream data is divided from an identifier 10 describing a marshalling method written in the head of stream data 8 and an IDL (Interface Definition Language) 12 describing a structure of the stream data and is converted into the data which is specific to a particular program language while discriminating attributes of each of the divided data elements from the IDL. The IDL 12 includes, for example, information indicating such that the first data of the stream data is an integer type and the next data is a character type. In the marshalling process, first, a marshalling method is determined from the architecture of the computer which executes the marshalling process and the version of the ORB and the identifier 10 of the marshalling method is stored in the header of the stream. Subsequently, the attributes of the data are discriminated with respect to each of the program language-specific data and the program language-specific data is converted into the stream data. In those processes, it is necessary to understand the meaning of each of the inputted data in order to convert each inputted data. In the case where data of a complicated format such as data of a user definition type or the like is exchanged between the client and the server, a load of computing resources (CPU, main memory or other resources) which are required for the marshalling and unmarshalling is large.
It is an object of the invention to provide high-speed marshalling and unmarshalling processing methods and apparatus in the case where a transmission and a reception of data between a client and a server occur a plural number of times.
To accomplish the above object, according to one aspect of the invention, there is provided an apparatus for converting a data format which is specific to a particular program language on a particular computer into stream data which is not specific to, i.e., is common to particular computers, comprising: a caching part or component for storing a correspondence between a program language-specific data format and stream data; a marshalling part or component for retrieving whether all or a part of the data of the program language-specific format has been stored in the cache or not, for performing a conversion by using the data on the cache when the data exists on the cache, and for converting the data of the program language-specific format into the stream data without using the cache when the data does not exist on the cache; and a cache registering part or component for registering a result into the cache at the time of the conversion from the data of the program language-specific format into the stream data or the conversion from the stream data into the data of the program language-specific format.
In such a construction, when the data is transmitted, the marshalling part retrieves or discriminates whether the received data exists on the cache or not, converts the data at a high speed by referring to the cache when the data exists, and converts the data at a low speed by the foregoing method or another known method without using the cache when the data does not exist. When the data is converted by the method which does not use the cache, the conversion result is registered into the cache by using the cache registering part.
According to another aspect of the invention, there is provided an apparatus for converting stream data which is not specific to or is common to particular computers into the data of a format which is specific to a particular program language on a particular computer, comprising: a caching part or component for storing a correspondence between stream data and data of a program language-specific format; an unmarshalling part or component for discriminating whether all or a part of the stream data has been stored in the cache or not, for performing a conversion by using the data on the cache when the stream data exists on the cache, and for converting the stream data into the data of the program language-specific format without using the cache when the data does not exist on the cache; and a cache registering part or component for registering a result into the cache at the time of the conversion from the stream data into the data of the program language-specific format or the conversion from the data of the program language-specific format into the stream data. In such a construction, when the data is received, the unmarshalling part discriminates whether the received data exists on the cache or not, converts the data at a high speed by using the cache when the data exists, and converts the data at a low speed by the foregoing method or another known method without using the cache when the data does not exist on the cache. When the data is converted without using the cache, the conversion result is registered into the cache by using the cache registering part.
FIG. 1 is a diagram showing a constructional example of a distributed computing environment to which the invention is applied;
FIG. 2 is a diagram showing an ORB (object request broker) according to an embodiment of the invention;
FIG. 3 is a diagram showing a flow of data at the time of marshalling and a structure of a cache in the embodiment of FIG. 2;
FIG. 4 is a flowchart showing a flow of processes at the time of marshalling in the embodiment of FIG. 2;
FIG. 5 is a diagram showing a flow of data at the time of unmarshalling and a structure of a cache in the embodiment of FIG. 2;
FIG. 6 is a flowchart showing a flow of processes at the time of unmarshalling in the embodiment of FIG. 2; and
FIG. 7 is a diagram that is useful for explaining an example of a marshalling process which does not use a cache and an unmarshalling process.
An embodiment of the invention will now be described hereinbelow with reference to the drawings. Similar component elements in the diagrams are designated by the same reference numerals.
FIG. 1 is a diagram showing a construction of a distributed computing environment according to an embodiment of the invention.
In the diagram, a client program 602 on a small computer 1 requests a processing work to a server program 601 on a large computer 2 existing at a remote place and having a plenty of computing resources via a network 3. By receiving this request, the server program 601 processes the processing job or task and returns a result of the processing to the client program 602. FIG. 2 is a diagram showing a flow of data in such a construction.
In FIG. 2, a client program 111 has therein: program data 113 and 122 which is specific to a computer and a described program language; an ORB 141 which is used by the client program; and the like. The OBR 141 includes a marshalling part 114, a unmarshalling part 121, cache registering part 151 and a cache part 131. A server program 112 has therein: program data 117 and 118 which is specific to the computer and the described program language; and ORB 142 which is used by the server program; and the like. The OBR 142 includes a marshalling part 119, a unmarshalling part 116, cache registering part 152 and a cache part 132.
How to exchange the data between the client program 111 and server program 112 in FIG. 2 will now be described with respect to a flow of data. In the client program 11, to transmit the program data 113 of a data format specific to the computer on which the client program operates and the described program to the server program 112, a marshalling part 114 of the ORB 141 converts the program data 113 requesting communication data 115 which is not specific to particular computers or program languages and the cache registering part 151 registers the result of the conversion into the cache 131. In this instance, if all or a part of the program data 113 exists in a cache 131 of the client program by referring to the cache 131, the data is converted into the request communication data 115 by using the cache data. After completion of the conversion, the data 115 is transmitted to the server program 112.
In the server program 112, an unmarshalling part 116 of the ORB 142 converts the received request communication data 115 into the program data 117 of a format which is specific to the computer on which the server program operates or to the described program language and the cache registering part 152 registers the result of the conversion into the cache 132. In this instance, if all or a part of the request communication data 115 exists in a cache 132 of the server program by referring to the cache 132, the data is converted into the program data 117 by using the cache data.
After the server program processed the request from the client, to return the program data 118 as a processing result to the client program, the data is converted into response communication data 120 by a marshalling part 119 of the ORB 142 and the cache registering part 152 registers the result of the conversion into the cache 132. At this time, if all or a part of the program data 118 exists in the cache 132 of the server program with reference to the cache 132, the data is converted into the response communication data 120 by using the cache data. The response communication data 120 is transmitted to the client program.
In the client program 111, the received data is converted into the program data 122 of the client program language-specific format by an unmarshalling part 121 of the ORB 141 and the cache registering part 151 registers the result of the conversion into the cache 131. At this time, if all or a part of the response communication data 120 exists in a cache 131, the data is converted into the program data 122 by using the cache data. In this manner, the data transmission and reception can be performed between the distributed client and server programs at a high speed.
An embodiment of processes in the marshalling part 114 and 119 in FIG. 2 will now be described with reference to FIG. 3. Although the marshalling part 114 in FIG. 2 is used as an example in the description, a similar embodiment is also possible in the marshalling part 119.
FIG. 3 is a diagram showing a structure of the cache at the time of marshalling and a flow of data of the marshalling process. First, the structure of the cache will be explained. A pair of contents of the program data and contents of the communication data corresponding thereto have been stored in the cache every type of program data (in the example of FIG. 3, a pair of a program data cache 211 and a communication data cache 212 for an “aTable” struct). When the program data is based on the user definition type, every element (user definition type or basic type) of the user definition type data, an offset from the header of the communication data corresponding thereto is stored in the cache. In the example of FIG. 3, a system having the cache corresponding to every user definition type and basic type is shown. Although the case where the correspondence of the pair of communication data and program data is stored on the cache is shown in the diagram, a correspondence of a plurality of pairs of communication data and program data can be also provided on the cache. The “basic type” indicates data such as numeral, a single character, a character string, or the like. The “user definition type” indicates a set of basic type data and other user definition type data, which is generally complicated data. For example, a plurality of attributes of a particular employee such as name, age and employee identification number, can be represented by single user definition type data.
A flow of data of the marshalling process and a flow of control will now be described with reference to FIGS. 3 and 4. In the marshalling part, first, the program data 113 to be transmitted and the program data 211 on the cache corresponding to its type are compared (S311) and whether their contents are matched with each other or not is discriminated (S312). Even in the case where the data to be checked is the user definition type such as struct, union, or the like, it is not decomposed to respective elemental types constituting the user definition type, but the user definition type is compared, as is, on the memory. If it is determined that the contents match as a comparison result, the next data is checked. When there is a difference or unmatch between the contents, the communication data 212 on the cache corresponding to the program data which was identical or matched until the difference is detected is copied into the request communication data 115 (S313). Whether the program data with the difference or unmatch is the basic type or the user definition type is discriminated (S314). In case of the basic type, since it does not take a long time for the converting process, a process to convert the program data into the communication data is performed (S315). In case of the user definition type, the data is long in many cases and there is a possibility that the user definition type data has been registered in another cache. Therefore, the marshalling process is recursively called (S316). (In the example of FIG. 3, the marshalling process is recursively called by using the struct “aStr” in which the output program data 113 does not coincide or match as an argument.) A conversion result in step S315 or S316 is registered into the cache (S317). The processes in steps S311 to S317 are executed to all of the data. When there is no data to be processed (S310), the communication data remaining on the cache at this time point is copied (S318).
An embodiment of the processes in the unmarshalling parts 116 and 121 in FIG. 2 will now be described. Although the unmarshalling part 116 in FIG. 2 will be explained as an example, a similar embodiment is also possible even in the unmarshalling part 121.
FIG. 5 is a diagram showing a structure of the cache at the time of unmarshalling and a flow of data in the unmarshalling process. First, the structure of the cache will be explained. A pair of contents of the program data and contents of the communication data corresponding thereto have been stored in the cache every type of program data (in the example of FIG. 5, a pair of a communication data cache 411 for an “aTable” struct and a program data cache 412). When the program data is the user definition type, every element (user definition type or basic type) of the program data of the user definition type, an offset from the header of the communication data corresponding thereto is stored in the cache. By using this correlation, to which element in the program data an arbitrary offset of the communication data corresponds will be understood. In the example of FIG. 5, a system having the cache every user definition type and basic type is shown. Although the case where the correspondence of the pair of communication data and program data has been stored on the cache every type is shown in the diagram, a correspondence of a plurality of pairs of communication data and program data can be also provided on the cache.
A flow of data in the unmarshalling process and a flow of control will now be described with reference to FIGS. 5 and 6. In the unmarshalling part, the received request communication data 115 and the communication data 411 on the cache are compared on an octet unit basis as a unit of the communication data (S511). Whether they have the same value or not is discriminated (S512). Thus, if they have the same value, the next octet is checked. If they do not have the same value and there is a difference or unmatch, the program data 412 on the cache corresponding to the communication data which was identical or showed match until the difference or unmatch is detected is copied into the output program data 117 (S513). Whether the program data having the difference or unmatch is the basic type or user definition type is discriminated by looking at the program data or IDL 12 (S514). In case of the basic type, since it does not take a long time for the converting process, a process to convert the communication data into the program data is performed (S515). In case of the user definition type, the data is long in many cases and there is a possibility that the data of the user definition type has been registered in another cache (not shown). Therefore, the unmarshalling process is recursively called (S516). A conversion result in step S515 or S516 is registered into the cache (S517). The processes in steps S511 to S517 are executed to all of the octets of the communication data. When there is no data to be processed (S510), the program data remaining on the cache at this time point is copied (S518).
Generally, the server object residentially or persistently exists on a certain computer and processes similar requests from many and unspecified client objects a plural number of times. Hitherto, to independently execute the marshalling and unmarshalling processes in response to those similar processing requests of a plural number of times, in the case where a complicated data format is exchanged between the client and the server, a load of computing resources (CPU, main memory) which are required for the marshalling and unmarshalling is large. In the embodiment, the converting process which was once performed is stored into the cache and it is used from the next time, so that the computing resources which are required for the marshalling and unmarshalling can be reduced.
The procedures shown in FIGS. 4 and 6 and other procedures described herein can be stored into an ROM or a disk in each of the small computer 1 and large computer 2 or into another memory means.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5557798Dec 21, 1990Sep 17, 1996Tibco, Inc.Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processesUS5640564Jun 6, 1995Jun 17, 1997Sun Microsystems, Inc.Method and apparatus for generating and using short operation identifiers in object oriented systemsUS5793970Jul 11, 1996Aug 11, 1998Microsoft CorporationMethod and computer program product for converting message identification codes using a conversion map accesible via a data linkUS5860072Jul 11, 1996Jan 12, 1999Tandem Computers IncorporatedMethod and apparatus for transporting interface definition language-defined data structures between heterogeneous systemsReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7650405Sep 29, 2005Jan 19, 2010Rockwell Automation Technologies, Inc.Tracking and tracing across process boundaries in an industrial automation environmentUS7660638Feb 9, 2010Rockwell Automation Technologies, Inc.Business process execution engineUS7672737Mar 2, 2010Rockwell Automation Technologies, Inc.Hierarchically structured data model for utilization in industrial automation environmentsUS7676281Mar 9, 2010Rockwell Automation Technologies, Inc.Distributed database in an industrial automation environmentUS7734590Sep 30, 2005Jun 8, 2010Rockwell Automation Technologies, Inc.Incremental association of metadata to production dataUS7801628Sep 21, 2010Rockwell Automation Technologies, Inc.Industrial operator interfaces interacting with higher-level business workflowUS7809683Sep 29, 2005Oct 5, 2010Rockwell Automation Technologies, Inc.Library that includes modifiable industrial automation objectsUS7881812Sep 29, 2005Feb 1, 2011Rockwell Automation Technologies, Inc.Editing and configuring deviceUS7904488Jul 21, 2004Mar 8, 2011Rockwell Automation Technologies, Inc.Time stamp methods for unified plant modelUS8019796Jun 7, 2010Sep 13, 2011Rockwell Automation Technologies, Inc.Incremental association of metadata to production dataUS8060223Nov 15, 2011Rockwell Automation Technologies, Inc.Editing lifecycle and deployment of objects in an industrial automation environmentUS8086649Jun 7, 2010Dec 27, 2011Rockwell Automation Technologies, Inc.Incremental association of metadata to production dataUS8204609Jun 27, 2008Jun 19, 2012Rockwell Automation Technologies, Inc.Industrial operator interfaces interacting with higher-level business workflowUS8239837 *May 15, 2008Aug 7, 2012International Business Machines CorporationRemotely handling exceptions through STAFUS8275680Sep 25, 2012Rockwell Automation Technologies, Inc.Enabling transactional mechanisms in an automated controller systemUS8280537Oct 7, 2011Oct 2, 2012Rockwell Automation Technologies, Inc.Editing lifecycle and deployment of objects in an industrial automation environmentUS8438191Aug 19, 2011May 7, 2013Rockwell Automation Technologies, Inc.Incremental association of metadata to production dataUS8484250Sep 30, 2005Jul 9, 2013Rockwell Automation Technologies, Inc.Data federation with industrial control systemsUS8484401Apr 15, 2010Jul 9, 2013Rockwell Automation Technologies, Inc.Systems and methods for conducting communications among components of multidomain industrial automation systemUS8799800Sep 29, 2005Aug 5, 2014Rockwell Automation Technologies, Inc.Automatic user interface generationUS8855791Jun 1, 2012Oct 7, 2014Rockwell Automation Technologies, Inc.Industrial operator interfaces interacting with higher-level business workflowUS8984533Apr 15, 2010Mar 17, 2015Rockwell Automation Technologies, Inc.Systems and methods for conducting communications among components of multidomain industrial automation systemUS20070283092 *Jun 29, 2007Dec 6, 2007Cassell Loellyn JSystem and Method of Selection and Communication of a Disk for Storage of a CoredumpUS20080288924 *May 15, 2008Nov 20, 2008International Business Machines CorporationRemotely Handling Exceptions Through STAF* Cited by examinerClassifications U.S. Classification719/313, 719/310, 719/330, 709/246, 711/118International ClassificationG06F13/00, G06F15/16, G06F9/54, G06F9/46, G06F9/00, G06F3/00, G06F9/44Cooperative ClassificationG06F9/541, G06F9/548European ClassificationG06F9/54A, G06F9/54P1Legal EventsDateCodeEventDescriptionJul 7, 2008REMIMaintenance fee reminder mailedDec 28, 2008LAPSLapse for failure to pay maintenance feesFeb 17, 2009FPExpired due to failure to pay maintenance feeEffective date: 20081228RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services