Electrical computers and digital processing systems: multicomput – Remote data accessing – Using interconnected networks
Reexamination Certificate
1997-09-29
2001-07-03
Rinehart, Mark H. (Department: 2756)
Electrical computers and digital processing systems: multicomput
Remote data accessing
Using interconnected networks
C709S230000, C709S224000
Reexamination Certificate
active
06256667
ABSTRACT:
FIELD OF INVENTION
The present invention refers to systems and methods for electronic data interchange messaging, i.e. for the interchange of electronic messages comprising and transferring data provided in a predefined, preferably standardized structure or form in such a way that said data may be identified and used as data element values or strings in further processing functions by the receiving system or application.
TECHNICAL BACKGROUND AND PRIOR ART
In spite of the long driven computerization, still a large amount of the transfer of information between companies is today being done by use of paper documents. Essentially all information initially resides in a computer system, but when it is to be transferred to a business partner or the like, it is written out on paper, sent by facsimile, letter of delivery service to the receiver. The latter inputs the received information into his computer system manually. This procedure is repeated throughout a number of links in a distribution chain, and basically the same information is inputted manually in each step.
By the use of Electronic Data Interchange, the flow of information between different companies is automated. The companies' computer system or applications for ordering, storing, invoice handling, production, transportation and other functions may then automatically exchange information. This requires standardized or structured electronic messages sent via communication networks to the counterpart, which then automatically may process the information further in his internal computer system.
There data not exist any exact definition of electronic data interchange (EDI). However, it may be said that the following should be satisfied for electronic data interchange communication:
a) The communication between computer system shall be direct, internal or external, via communication networks, i.e. not via written papers, diskettes or magnetic tapes.
b) The information shall be structured;
c) The communication shall preferably make use of a communication standard, such as EDIFACT or X.12 or a similar defined structure agreed upon by the communicating parties; and
d) The information shall be directly computer processable at the receiver, being it a computer or an application, i.e. essentially without the need of manual operations to input the information at the receiver.
Two examples of such electronic data interchange standards is X.12 and EDIFACT (the Electronic Data Interchange For Administration, Commerce and Transport). EDIFACT is well established in Europe, and electronic data interchange system, EDIFACT provides a set of rules for, for example, the syntax and message meaning/sentence to be used within the EDIFACT system. X.12 is a similar standardized system used in the USA.
However, even though the use of EDI constitutes a essential leap forward in the automation of processes involving messaging, there is still a need for new techniques relating to how the system and/or system process shall be designed and implemented in order to provide a faster and simpler management the EDI messaging.
SUMMARY OF THE INVENTION
An object of the invention is to increase the speed and simplicity of the design, construction, implementation, management, maintenance and use of electronic data interchange systems and processes.
According to different aspects of the invention, the above mentioned and other objects are achieved by a method for electronic data interchange messaging, an electronic data interchange messaging system, a system for designing an electronic data interchange messaging process, and an article of manufacture as defined in the accompanying claims.
Hence, a computer software application according to the invention preferably comprises: a data definition defining the information that has to be successively stored and recalled by the application, said data definition being used for data mapping in relation to incoming/outgoing messages; a process describing the expected sequence of messages, event rules to be applied on the message data for detection of certain conditions, timers supervising deadlines of certain events or updates, and events to be issued due to timer expiring or other conditions; data mapping from message data to application data (IMA data); and data mapping from application data (IMA data) to event data when issuing an event. In this context, and according to the invention, terms such as electronic data interchange, electronic data interchange message, and the like refer to electronic messages comprising and transferring data provided in a predefined, preferably standardized structure or form in such a way that said data may be identified and used as data element values or strings in further processing functions by the receiving system or application. The term process execution is in the context of the present invention referring to the execution of a process from its initial start all the way to its end. That is, the executional steps made by a process after an event causes the process to resume execution, or before an event causes the process to make a temporary halt in the execution, are not considered as a process execution, but merely as a part thereof.
Consequently, a regular email text body, for example, does not constitute an electronic data interchange message according to the invention unless the body comprises data arranged in a predefined structure so that the receiving system or application may derive or extract said data therefrom. Note however that this does not mean that the sending/receiving of such unstructured text bodies may not be included in a process according to the invention, as an addition to the sending/receiving of true electronic data interchange messages.
A computer application according to the invention provides an electronic data interchange process working in intimate interaction with a data instance of a data definition associated with the specific process. The data definition for the process is defined in advance and is set to include primarily such data that are needed in downstream steps in the process.
In general, a process as a whole may deal with an amount of incoming or outgoing data, either in relation to electronic data interchange messages or in relation to a relational database, such as a SQL (Standard Query Language) database, or other formats, as well as processing data derived and/or used in the process itself. Some of these data are often needed for use in downstream steps in the process. According to the invention, it is preferable not to store such data in a SQL database, at least not exclusively, since this will require more access time in retrieving the data when needed for use in said downstream steps. The use of a SQL relational database requires the execution of a series of request or query steps for retrieving of the desired information.
Instead, according to a preferred embodiment of the invention, such data is preferably stored in a process specific, sequential and collected data instance of a process data definition, preferably stored in a sequential file system, preferably using predefined indices, so as to be easy and fast retrievable for the process execution.
Hence, a data definition, including a set of data elements to be provided with data need for expedient execution of the entire process, is defined in advance in relation to the definition of the process. Preferably, a new data instance of the data definition is created for each execution of the process. Also, all or part of the information successively provided in the data instance may be e.g. stored in a relational database at the end of the process, thereby reducing need for real-time process-database-interaction.
As a result of the use of a time sequential file system for storing said data instance, there is no need for mapping of data to and from a database, and also no need for SQL searches to find data for a specific process case.
As mentioned, in prior art, data received in for example a transportation order message is consecutively stored in one or more tables in a database, e
Nilsson Mikael
Skog Anders
Wåhlander Christer
Burns Doane Swecker & Mathis L.L.P.
Pierce, III Ivan C.
Rinehart Mark H.
Viewlocity AB
LandOfFree
Intelligent messaging does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Intelligent messaging, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Intelligent messaging will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2559104