WO1997023836A1 - Method for communicating data between differently structured data files - Google Patents

Method for communicating data between differently structured data files Download PDF

Info

Publication number
WO1997023836A1
WO1997023836A1 PCT/NL1996/000498 NL9600498W WO9723836A1 WO 1997023836 A1 WO1997023836 A1 WO 1997023836A1 NL 9600498 W NL9600498 W NL 9600498W WO 9723836 A1 WO9723836 A1 WO 9723836A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
message
field
descriptions
files
Prior art date
Application number
PCT/NL1996/000498
Other languages
French (fr)
Inventor
Bernard Munnik
Original Assignee
Bernard Munnik
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bernard Munnik filed Critical Bernard Munnik
Priority to AU20119/97A priority Critical patent/AU2011997A/en
Publication of WO1997023836A1 publication Critical patent/WO1997023836A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database

Definitions

  • EP 0,449,494 describes a system for transferring data between two systems each using its own data format and both using the same data structure.
  • data is transmitted by a sender in its own native format and converted by the receiver which for that purpose dis ⁇ poses of a dedicated conversion program. If differently structured data ⁇ bases are involved then each database should be related to a number of dedicated conversion programs to enable communication between the vari- ous databases.
  • US 5,119,465 describes a system for transferring data between two databases each using its own data format.
  • a format conversion system is developed.
  • the sender disposes of front end converter for converting a source data structure in a source format to data for an intermediary.
  • the back end converter converts the data from the intermediary to a target data structure m a target data format used by the receiver.
  • the intermediary includes a rather complicated domain conversion arrange ⁇ ment.
  • the various conversion processes are controlled by a converter executive.
  • This prior art system is destined to be used on one computer sys ⁇ tem to enable data transfer between applications with different data format and/or different data structure and is not suited for communicat ⁇ ing data between different computers using standard communication chan- nels and commercially available communication software.
  • EP 0,130,375 also describes a system for transferring data between two computers each using its own data format, both using the same data structure.
  • a format conver- sion system is developed for converting one specific format into another specific format.
  • This prior art system is restricted to the selected specific formats and structures and has therefore no universal applic ⁇ ability.
  • An object of the invention is now to provide a universally appli ⁇ cable system which is independent of the number of differently struc ⁇ tured databases and the number of computers involved and requires only a restricted amount of software.
  • the invention describes a system (called PMS) for transfer of medium large volumes in a format which is not fixed or formally agreed by the parties (see figure 1).
  • PMS Packet Message Sys- tem
  • the sender of an amount of data to be transferred disposes of a software program (hereinafter called the message writing program) offering the possibility to compile various messages (variable in structure and composition) from its own specific data collection and to get these messages as separate files ready for transmission. Thereafter, the message can be transmitted using one of the standard on the market available programs for data communication, using a protocol which is supported by the message receiver.
  • a software program hereinafter called the message writing program
  • the message is received with one of the standard on the market available data communication programs using the respective protocol.
  • the message receiver disposes of a software program (hereinafter called the message reading program) offering the possibility to add data from the various messages (variable in structure and composition) to its own specific data collection
  • the dedicated message writing program and the dedicated message reading program are able to compose or process respectively various messages by addjng parameters to the programs to connect the file struc ⁇ ture of the own data collection with its own different field names and/- or descriptions to the data structure and the field names and/or des- criptions of the various messages.
  • a table with message models (message model table) is offered to the writing/reading software
  • a table with field names (connecting table) is offered to the writing/reading software (see also figure 2) .
  • the Universal Message The basis of the method is a universal message. That is the des ⁇ cription of all possible messages based on some prescribed rules. All possible messages are specific but have a universal frame.
  • the message contains fields with cells each having a serial number within the mess ⁇ age. The only thing to be transmitted is the succession number of the cell within the message followed by the contents of the cell. In that way the serial number forms the label of the succeeding value.
  • a table is a series of cells which always appears only once.
  • - A row is a repetitive group of cells which either appear not or appear
  • a table, row, or cell can be obligatory or not.
  • - Cells can appear withm or outside tables and rows.
  • the first table, row, or cell within a table or row is always obliga ⁇ tory.
  • the message-model-table comprises the following data:
  • the connecting table comprises the following data:
  • Own label The label of the own field within the o.n file for the respective contents
  • Additional data can be included to speed up or simplify the pro ⁇ cessing, for instance:
  • the message-writing-program retrieves from the message model table the model of the message to be drafted.
  • the program reads one by one the serial numbers with corresponding PMS element numbers from the model.
  • the own connecting table is searched to retrieve the corresponding value in the own application/flle/fleld.
  • the retrieved value preceded by the field serial number fro ⁇ i the mess ⁇ age model, is placed in the message. As soon as the message is drafted the message is ready to be transmitted.
  • the message reading program After receiving the message the message reading program is start ⁇ ed.
  • the message reading program retrieves a model of the received mes ⁇ sage from the message model table.
  • the program reads one after the other the serial numbers with the succeeding values from the message.
  • the corresponding PMS- element number By con ⁇ sulting the message model for each serial number the corresponding PMS- element number can be found.
  • the own con ⁇ necting table van be searched to retrieve the own application/f le/field in which the corresponding value should be inserted.
  • the received value is input in the respective field.
  • the pro ⁇ gram After processing the message the pro ⁇ gram is fmnished.

Abstract

The invention relates to a method for communicating data by transmitting messages between differently structured data files, in which data files the data are stored in fields with different field names or field descriptions. The invention describes a method for data communication without fixed formats and protocols and being agreed between all parties, in which it is possible to transmit data of each application with any file structure to any other application, file structure and computer system.

Description

Method for communicating data between differently structured data files
In practice an increasing amount of data is exchanged between computer applications with different file structures, installed on dif- ferent computers, localized at more or less large mutual distance and programmed, used, and managed by different persons or organizations. For transferring low data volumes in an unstructured format standard elec¬ tronic mail software (Email) is used. For transferring large data vol¬ umes in a format, which is agreed by the users, use is made of a "file transfer" specifically developed for each type of transfer, or of an EDI (electronic data interchange) system, developed for each type of trans¬ fer.
EP 0,449,494 describes a system for transferring data between two systems each using its own data format and both using the same data structure. In principle data is transmitted by a sender in its own native format and converted by the receiver which for that purpose dis¬ poses of a dedicated conversion program. If differently structured data¬ bases are involved then each database should be related to a number of dedicated conversion programs to enable communication between the vari- ous databases.
US 5,119,465 describes a system for transferring data between two databases each using its own data format. To solve the data format prob¬ lem a format conversion system is developed. According to this prior art publication the sender disposes of front end converter for converting a source data structure in a source format to data for an intermediary. The back end converter converts the data from the intermediary to a target data structure m a target data format used by the receiver. The intermediary includes a rather complicated domain conversion arrange¬ ment. The various conversion processes are controlled by a converter executive.
This prior art system is destined to be used on one computer sys¬ tem to enable data transfer between applications with different data format and/or different data structure and is not suited for communicat¬ ing data between different computers using standard communication chan- nels and commercially available communication software.
EP 0,130,375 also describes a system for transferring data between two computers each using its own data format, both using the same data structure. To solve the data format problem a format conver- sion system is developed for converting one specific format into another specific format. This prior art system is restricted to the selected specific formats and structures and has therefore no universal applic¬ ability. An object of the invention is now to provide a universally appli¬ cable system which is independent of the number of differently struc¬ tured databases and the number of computers involved and requires only a restricted amount of software.
The invention describes a system (called PMS) for transfer of medium large volumes in a format which is not fixed or formally agreed by the parties (see figure 1).
The method
The method according to the invention (PMS = Packet Message Sys- tem) comprises the following components and procedures.
The sender of an amount of data to be transferred (hereinafter called: a message) disposes of a software program (hereinafter called the message writing program) offering the possibility to compile various messages (variable in structure and composition) from its own specific data collection and to get these messages as separate files ready for transmission. Thereafter, the message can be transmitted using one of the standard on the market available programs for data communication, using a protocol which is supported by the message receiver.
The message is received with one of the standard on the market available data communication programs using the respective protocol.
The message receiver disposes of a software program (hereinafter called the message reading program) offering the possibility to add data from the various messages (variable in structure and composition) to its own specific data collection The dedicated message writing program and the dedicated message reading program are able to compose or process respectively various messages by addjng parameters to the programs to connect the file struc¬ ture of the own data collection with its own different field names and/- or descriptions to the data structure and the field names and/or des- criptions of the various messages.
For writing and reading messages a table with message models (message model table) is offered to the writing/reading software For reading and writing the own specific data collections a table with field names (connecting table) is offered to the writing/reading software (see also figure 2) .
The Universal Message The basis of the method is a universal message. That is the des¬ cription of all possible messages based on some prescribed rules. All possible messages are specific but have a universal frame. The message contains fields with cells each having a serial number within the mess¬ age. The only thing to be transmitted is the succession number of the cell within the message followed by the contents of the cell. In that way the serial number forms the label of the succeeding value.
As field types the message distinguishes between cells in tables, cells in repetitive groups and single cells. The following rules apply:
- A table is a series of cells which always appears only once. - A row is a repetitive group of cells which either appear not or appear
N times.
- A table, row, or cell can be obligatory or not.
- Within tables and rows other tables and rows can be present.
- Cells can appear withm or outside tables and rows. - The first table, row, or cell within a table or row is always obliga¬ tory.
Using these rules it is possible to draft simple (flat file) mes¬ sages, however, also complex forms which are practically unlimited in length and dimensions can be drafted by defining repetitive groups with- m repetitive groups.
Messages are drafted in agreement with the method and read by comparing the labels (field serial number) to the corresponding unique element numbers as are defined in the message model to be consulted. According to the method values are retrieved and positioned by comparing the unique element number with the numbers in a connecting table in which the position in the own data structure is indicated.
Message-model-table
The message-model-table comprises the following data:
Message name The PMS name of the message
Field serial number The serial number of the field within the message Type T (table), R (row or repetitive group) or C (cell)
Obligatory Field is obligatory or not
Parent Higher order field serial number in a fleld hier¬ archy
Element number The unique PMS number of the element which should be inscribed in that field
Additional data can be added to simplify or speed up the process¬
Figure imgf000006_0001
Message number The unique PMS message number Message version The version of the message Group name The name of a group (= table or row) Status For instance C (copy) F (fixed) P (presentation)
0 (object)
Element name The unique PMS name of the element
The connecting table
The connecting table comprises the following data:
Message number The unique PMS number of the message Element number The unique PMS number of the element Own application The name of the application from which this message was drafted or in which the message will be input
Own file The name of the file inside the application from within the message was drafted or in which the mes¬ sage was input
Own label The label of the own field within the o.n file for the respective contents
Additional data can be included to speed up or simplify the pro¬ cessing, for instance:
Message version The version of the message Codes/Indexes For instance: bKey, bWhile, bFor, bExpr, for an application programmed in Clipper
Format The format of the element (for instance: numerical) Code table The name of a code table to be used eventually Element name The unique PMS name of the element Description The description of the element to be used also as Help-text in the software
Example of a message model
Message name School children Version number 1.0
Serial Element number Type Obligatory Parent number (Element and group names)
1 T Y 0 Control data
2 C Y 464661 Model name of the message
3 C Y 548957 Version number of the model name
4 c Y 980931 Name of the sender
5 c N 989243 Data line number of the sender
6 C N 323499 Name of the receiver
7 C Y 187867 Data line number of the receiver
8 R Y 0 Schools
9 C Y 8 565088 Name of the school
10 R Y 8 Classes
11 C Y 10 466610 Class indication
12 R N 10 Children
13 C Y 12 465683 Name of the child
14 C Y 12 654809 Age of the child
Example of a message in agreement with the above described model
2,School children 3,1.0 .van der Meer 7,0123-456789 9,The Weather-vane 11 ,class 2 13, an
14,7
13,Pιet
14,8
9, he Circle
11 ,class 2
11 ,class 3
13,Klaas
14,8
The writing program
The message-writing-program retrieves from the message model table the model of the message to be drafted. The program reads one by one the serial numbers with corresponding PMS element numbers from the model. On the basis of the PMS element number the own connecting table is searched to retrieve the corresponding value in the own application/flle/fleld. The retrieved value, preceded by the field serial number froτi the mess¬ age model, is placed in the message. As soon as the message is drafted the message is ready to be transmitted.
The reading program
After receiving the message the message reading program is start¬ ed. The message reading program retrieves a model of the received mes¬ sage from the message model table. The program reads one after the other the serial numbers with the succeeding values from the message. By con¬ sulting the message model for each serial number the corresponding PMS- element number can be found. With the PMS-ele ent number the own con¬ necting table van be searched to retrieve the own application/f le/field in which the corresponding value should be inserted. The received value is input in the respective field. After processing the message the pro¬ gram is fmnished.

Claims

Claims
1. Method for communicating data by transmitting messages between differently structured data files at the transmission side and the re- ceivmg side, in which data files the data are stored in fields with different field names or field descriptions, which method is character¬ ized by the combination of the following steps: a) the field names or field descriptions of corresponding data in various files are related to a set of standard labels, b) data to be transmitted is combined in a message at the trans¬ mission side with the label which is related to the field name of the field in which the data was stored and at the receiving side, the field name of the transmitted data at the reception side is obtained based on the received label and the defined relations in the standard set,
2. Method according to claim 1 , characterized in that in case multiple data are transmitted the labels with corresponding data are combined in a message in which the labels with corresponding data are appearing in a predetermined order.
3. Method according to one of the preceding claims, characterized in that at the transmission side the data to be transmitted are re¬ trieved by means of a form comprising fill in fields, whereby the field names are formed by the names or descriptions valid at the transmission side.
4. Method according to one of the preceding claims, characterized in that at the receiving side the transmitted data are inscribed in a form comprising fill in fields for filling in the received data, whereby the field names are formed by the names or descriptions valid at the reception side.
5. Method according to one of the preceding claims, characterized in that the descriptions at the transmission side and at the reception side are drafted in a different language.
6. Method according to one of the preceding claims, characterized in that to each data file a table is added in which the descriptions and the thereto related labels are stored.
7. Method according to one of the preceding claims, characterized in that to each data file a table is added in which a number of differ- ent forms are stored each comprising a unique parameter which parameter is added to the message at the transmission side and is used at the reception side to select the corresponding form.
8. Method according to one of the preceding claims, characterized in that to each data file a table is added in which the name∑. of a num¬ ber of different data files are stored each related to a unique parame¬ ter and that at the transmission side this parameter is added to the message and at the reception side the parameter is used to select the corresponding data file.
9 Method according to one of the preceding claims, characterized in that the data files are present on various computers and that the transmission of data is performed through an arbitrary available com¬ munication route.
10. Method accordmg to one of the preceding claims, characterized in that for communicating data from different data files a separate file is used, comprising a variable structure consisting of serial numbers and values, whereby the serial numbers for a predetermined structure are obtained by selecting from tables rows and cells a model.
PCT/NL1996/000498 1995-12-21 1996-12-23 Method for communicating data between differently structured data files WO1997023836A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU20119/97A AU2011997A (en) 1995-12-21 1996-12-23 Method for communicating data between differently structured data files

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NL1001955A NL1001955C2 (en) 1995-12-21 1995-12-21 Method for communicating data between differently structured data files.
NL1001955 1995-12-21

Publications (1)

Publication Number Publication Date
WO1997023836A1 true WO1997023836A1 (en) 1997-07-03

Family

ID=19762067

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/NL1996/000498 WO1997023836A1 (en) 1995-12-21 1996-12-23 Method for communicating data between differently structured data files

Country Status (3)

Country Link
AU (1) AU2011997A (en)
NL (1) NL1001955C2 (en)
WO (1) WO1997023836A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8010452B2 (en) 2000-12-06 2011-08-30 Open Business Exchange Limited Communication routing apparatus

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0130375A2 (en) * 1983-07-05 1985-01-09 International Business Machines Corporation Interactive control method for communicating data between incompatible information processing systems
EP0449494A2 (en) * 1990-03-27 1991-10-02 International Business Machines Corporation Method and apparatus for controlling the transfer of data between heterogeneous data base systems
US5119465A (en) * 1989-06-19 1992-06-02 Digital Equipment Corporation System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0130375A2 (en) * 1983-07-05 1985-01-09 International Business Machines Corporation Interactive control method for communicating data between incompatible information processing systems
US5119465A (en) * 1989-06-19 1992-06-02 Digital Equipment Corporation System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure
EP0449494A2 (en) * 1990-03-27 1991-10-02 International Business Machines Corporation Method and apparatus for controlling the transfer of data between heterogeneous data base systems

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8010452B2 (en) 2000-12-06 2011-08-30 Open Business Exchange Limited Communication routing apparatus

Also Published As

Publication number Publication date
NL1001955C2 (en) 1997-06-24
AU2011997A (en) 1997-07-17

Similar Documents

Publication Publication Date Title
US5778213A (en) Multilingual storage and retrieval
CA2379423C (en) Content based publish-and-subscribe system integrated in a relational database system
AU9652898A (en) Method of object oriented point-to-point communication and communication apparatus for carrying out such a method
CN108920675A (en) A kind of method, apparatus of information processing, computer storage medium and terminal
US20030028620A1 (en) Method of handling a data request
WO1997023836A1 (en) Method for communicating data between differently structured data files
KR20020041331A (en) Contents providing system
Buckland Combining electronic mail with online retrieval in a library context
Whitescarver et al. A network environment for computer-supported cooperative work
Kahn National information infrastructure components
Cullen et al. The use of FTAM to access graphical pictures across wide area networks
Meltsner Understanding the INTERNET: A guide for materials scientists and engineers
US20230328015A1 (en) Technique for exchanging information between at least two communication entities
JP3909820B2 (en) Electronic bulletin board system
Little et al. Standards for user procedures and data formats in automated information systems and networks
Mercurio The UCSD MSG System: Iterative Design in the UNIX Environment
JPS6376542A (en) Electronic mail system
Wallace The internet
Farrés Classifying electronic data interchanges
Penniman Systems interfaces revisited
Bush Internet Publishing: An Introduction and Discussion of Basics.
Crocker et al. Proposed official standard for the format of ARPA Network messages
John et al. The Internet Troubleshooter: Help for the Logged On and Lost
Bourne UKMARC: A format for the twenty‐first century?
McKenzie The academic online

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG US UZ VN AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 97523530

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase