NL1001955C2 - Method for communicating data between differently structured data files. - Google Patents

Description

Method for communicating data between differently structured data files.

In practice, it is increasingly common for data to be exchanged between computer applications, which may be different file structures, installed on different computers, located more or less widely spaced and programmed, used and managed by different persons or organizations. Standard electronic mail software (Email) is used to transfer low volumes of data in an unstructured format. For the transfer of large volumes of data in a format agreed between users, use is made of “file transfer” developed for each specific type of transfer or of an EDI (electronic data interchange) system developed for each type of transfer. The invention describes a system (DPMS gene> iri) for the transfer of medium volumes with a non-solid or i-meal user-agreed format (see figure 1).

The method The method of the invention (DPMS = The Paket Message System) consists of the following parts and operations.

The sender of an amount of data to be transferred (hereinafter referred to as: a message) has a fixed program (hereinafter referred to as the Message writing program) with which it is possible to compile different messages (variable in structure and composition) from its own specific data set and prepare these messages as separate files for transmission. The message can then be sent using any of the standard data communication programs available on the market, using a protocol supported by the message recipient.

The message is received using one of the standard data communication programs available on the market, using the appropriate protocol.

35 The recipient of the message has a fixed program (hereinafter referred to as the Message Reading Program) with which it is possible to add the data from different messages (variable in structure and composition) to his own specific data collection - \ 0 0 1 9 5 5

No4o339 Yes / JS · 2 meling.

The fixed message writing program and the fixed message reading program can draw up or process the various messages by adding parameters to the programs that link the file structure of the own data files with their own different field names and / or descriptions with the data structure and field names and / or descriptions of the various messages.

For writing and reading messages, a table with message models (Message model table) is offered to the write / read software. For reading and writing own specific data files, a table with field names (Link table) is offered to the write / read software (see figure 2).

The Universal Message 15 The basis of the working method is a universal message. This is the description of all possible messages based on some fixed rules. All possible messages are therefore specific, but have a universal structure. The message contains fields of cells, each of which has a sequence number within the message. All that is sent is the sequence number of the cell within the message, followed by the contents of the cell. The sequence number is therefore the label of the subsequent value.

As field types, a message has cells in tables, cells in repeating groups and single cells. The following rules apply for this: - A table is a series of cells that always occurs once.

- A row is a repeating group of cells that does not or does not occur N times - A table, row or cell may or may not be mandatory.

30 - Tables and rows can occur within tables and rows.

- Cells can appear inside and outside tables and rows.

- The first table, row or cell within a table or row is always mandatory.

With these rules it is possible to create simple (flat file) messages, but also to create complex forms that are practically unlimited in length and dimensions by defining repeating groups within repeating groups.

Messages are prepared and read in the method by comparing the 1 00 1 9 5 Ej I »o40339 Ja / JSm 3 labels (field sequence number) with the corresponding unique element numbers as laid down in the message model to be consulted. Values are found and placed in the method by comparing the unique element number with the numbers in a couple-5 table, after which the place is stated in the own data structure.

Message model table

The message model table contains the following information: 10 Message name The DPMS name of the message

Field sequence number The sequence number of the field within the message Type T (table), R (Row or repeating group) or C (Cell)

Mandatory Field is mandatory or not

Parent Parent field sequence number in a hierarchy of 15 fields

Element number The unique DPMS number of the element to be entered in the field

In addition, additional information may be included to speed up and / or simplify the handling, for example: 20

Message number The unique DPMS number of the message

Message version The version of the message

Group name The name of a group (= table or row)

Status For example C (copy) F (fixed) P (Presentation) 25 0 (0 object)

Element name The unique DPMS name of the element

The linking table

The link table contains the following information: 30

Message number The unique DPMS number of the message

Element number The unique DPMS number of the element

Own application The name of the application from which this message is written or entered 35 Own file The name of the file within the application from which this message is written or entered

Own label The label of the own field within the own file 1001955 N040339 Yes / JSm 4 position for the relevant content

In addition, additional information may be included to speed up and / or simplify the handling, for example: 5 Message version The version of the message

Codes / indexes For example: bKey, bWile, bFor, bExpr, for a solution programmed in Clipper Format The format of the element (for example: numeric) 10 Code table The name of any code table to use

Element name The unique DPMS name of the element

Description The description of the element, which can also be used as Help text in the software. 15 Example of a Message model

Message name: Schoolchildren

Version number: 1.0 20 Sequential Element number Type Mandatory Parent number (Element and group names) 1 TJ 0 Control data 2 CJ 1 464661 Model name of the message 3 CJ 1 548957 Version number of the model name 25 4 CJ 1 98O93I Name of the sender 5 CN 1 989243 Transmitter data line number 6 CN 1 323499 Receiver name 7 CJ 1 187867 Receiver number line 8 RJ 0 Schools 30 9 CJ 8 565088 Name of school 10 RG 8 Classes 11 CJ 10 466610 Class designation 12 RN 10 Children 13 CJ 12 465683 Name of the child 35 14 CJ 12 654809 Age of the child

Example of a Message according to the above model 2, Schoolchildren 3.1.0 1001955 no40339 Ja / Js »5 3.1.0 4, van der Meer 7,0123-456789 9« De Windwijzer 5 11.class 2 13.Jan 14.7 13.Piet 14.8 10 9.The Circle 11, class 2 11, class 3 13, Klaas 14.8 15

The writing program

The Message writing program retrieves the model of the message to be produced from the Message model table. One by one, the program reads the sequence numbers with the corresponding DPMS element trimmers from the model. With the DPMS element number, it is searched in the own link table in which own application / file / field the corresponding value can be found. The value found is preceded by the field sequence number from the message model placed in the message. Once the message has been written it can be sent.

25

The reading program

When the message is received, the Message Reading program is started. The Message Reading Program extracts the model of the message received from the Message Model Table. The program reads the sequence numbers with the next value one by one from the message. By consulting the message model, the corresponding DPMS element number can be found for each sequence number. The DPMS element number is used to look up in your own linking table in which own application / file / field the corresponding value should be placed. The value received is placed in that field. When the message has been processed, the program is terminated.

1001955

Claims (9)

Method for communicating data by transferring messages between differently structured data files on the send and receive sides, in which data files the data are stored in fields with different field names or descriptions, which method is characterized by the combination of the next steps: a) the field names or descriptions of corresponding data 10 in the various files are each related to a set of standard labels, b) a transfer is given in a message on the send side combined with that label that is related to the field name of the field in which the data was stored and the receiving side 15, on the basis of the received label and the relations defined in the standard set, the field name of the transmitted data is obtained on the receiving side. 2. Method according to claim 1, characterized in that upon transfer of several data the labels with associated data are combined in a message in which the labels with associated data occur in a predetermined order. Method according to any one of the preceding claims, characterized in that the data to be transmitted on the transmission side are retrieved from the database by means of a form on which 25 input fields are present, the field names being formed by the names valid on the transmission side or descriptions. Method according to any one of the preceding claims, characterized in that the transmitted data on the receiving side are entered in a form on which there are input fields which are filled by the received data, the field names being formed by the valid on the receiving side names or descriptions. Method according to one of the preceding claims, characterized in that the descriptions on the transmitting side and on the receiving side are in different languages. Method according to any one of the preceding claims, characterized in that a table is added to each data file in which the descriptions with the associated labels are stored. 1 0 0 1 9 5 5 N040339 Yes / JSm 7 Method according to any one of the preceding claims, characterized in that a table is added to each data file in which a number of different forms are stored, each provided with a unique characteristic and in that this characteristic is added on the transmission side to the message 5 and on the receipt side is used to select the corresponding form. Method according to any one of the preceding claims, characterized in that a table is added to each data file in which the names of a number of different data files are stored, each provided with a unique characteristic and in that this characteristic is added to the message on the transmission side and on the receive side is used to select the corresponding database. Method according to any one of the preceding claims, characterized in that the data files are located on different computers and that the data is transferred via any available communication path. 1001955