CA2340708A1 - Method for converting different data formats - Google Patents
Method for converting different data formats Download PDFInfo
- Publication number
- CA2340708A1 CA2340708A1 CA002340708A CA2340708A CA2340708A1 CA 2340708 A1 CA2340708 A1 CA 2340708A1 CA 002340708 A CA002340708 A CA 002340708A CA 2340708 A CA2340708 A CA 2340708A CA 2340708 A1 CA2340708 A1 CA 2340708A1
- Authority
- CA
- Canada
- Prior art keywords
- processor
- format
- data
- conversion
- message
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
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
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Communication Control (AREA)
- Multi Processors (AREA)
Abstract
Current multi-processor systems, such as communication systems, are generall y provided with processors for processing various data formats. The informatio n exchanged between such processors must therefore be submitted to a format conversion. The state-of-the-art techniques involve heavy operations in the compiler or a standardised data format in the interface (e.g. ASN.1) in orde r to reach this goal. The present invention provides a more efficient method that involves using a tool for automatically introducing a conversion proces s in the software interface between the processors.
Description
Specification Method for converting different data formats The invention relates to a method according to the preamble of patent claim 1.
Modern communication systems are fashioned as multiprocessor systems. This means that the controlling of the system-internal processes is carried out by a multiplicity of processors.
As a rule, such communication systems are fashioned as heterogeneous systems.
This means that processors of various manufacturers are used in the communication system.
However, these processors thereby also operate according to manufacturer-specific standards. Thus, for example, data of the individual processors are stored in different formats in the respectively allocated memory. This does not result in a limitation of operation as long as programs, which as a rule are respectively allocated to one processor during their execution, read these data from the relevant memory, process them, and write them into the memory again, since in this case the same data format is always used. Problems most often arise when messages or data are exchanged between processors or, respectively, between programs running on these processors, because here, if necessary, these data must be adapted to the different data formats.
Thus, for example, data that are processed on processors of the Motorola family are stored by these processors in a LSB HI format (Least Significant Byte at Highest Address), also known as the Big Endian format. In contrast to this, data that are processed on processors of the Intel family are stored by these processors in a LSB LO format (Least Significant Byte at Lowest Address), also known as the Little Endian format. For this reason, in the case of a data exchange between these two types of processors the data have to be converted correspondingly.
For the solution of such problems with respect to different data formats in process communication in heterogeneous systems, in the prior art a specific transfer format is defined for the exchange of messages and data (e.g. ASN.1 ). This means that in general before every exchange of messages the processor-specific format is converted into a previously defined transmission format used only for the purpose of the exchange of messages.
Once the message has arrived at the target processor, the transmission format is converted back into the processor-specific format used there.
A problematic feature of such a procedure is that the programs that communicate with one another via the exchange of messages are each themselves responsible for the conversion of the messages to be exchanged between the processor-specific data format and the transfer format. However, all required format conversions must thereby be programmed explicitly by the developer of the application software in the coding of the respective program. In addition, in the use of this transfer format a total of two conversions must be carried out, namely on one hand a conversion of the format from the source processor into the transfer format, and from this format back into the format of the target processor.
Because, due to its structure, the transfer format is very extensive, the dynamics of the system is thereby adversely affected. Finally, with the strict application of this technique there is the problem that conversions from the processor-specific data format of the source processor into the transmission format and from the transmission format into the processor-specific data format of the target processor take place even given the sending of messages between programs that run on processors having one and the same data format. This has a further adverse effect on the dynamics of the system.
In addition, in the German patent application 19535306.4 a method is specified for the conversion of differing data formats with which messages are exchanged between processors on which different data formats are respectively used. For this purpose, the procedures required for the conversion of the data between the formats are already provided automatically during the translation process of the source programs. This is achieved in that the translation program, in accordance with the data types used in the source programs, produces conversion procedures during the course of the translation that are then called during the later execution of the translated programs, before the exchange of messages.
However, a problematic feature of such a procedure is that extensive interventions in the compiler must be carried out. For this purpose, detailed knowledge of the compiler is necessary, which makes this process expensive and uneconomical for the user.
The invention is based on the object of indicating a way in which the conversion of data formats can be controlled more efficiently without having to accept the disadvantages cited above.
In particular, an advantage of the invention is that before the commissioning [or: startup] of the multiprocessor system a tool is controlled by means of which, according to the definition of the interface stored in the data layout, a conversion procedure for the conversion of the data formats is produced, and in that, in a subsequent compiler run, the application programs are translated together with the conversion procedure [or: are translated together using the conversion procedure] and are linked in a linkage editor as a part of the communication handler. A conversion machine is thereby produced in fully automatic fashion from the interface definition. The required conversion is thereby carried out automatically during the exchange of messages.
The data structures can be transmitted in their original form, that is, without additional format information. In this way, a significantly higher level of performance is achieved. For this purpose, it is necessary that the source code of the data structures be known both to the sending and to the receiving processor.
Advantageous developments of the invention are indicated in the subclaims.
The invention is explained in more detail in the following on the basis of a graphically depicted exemplary embodiment.
According to the figure, as an example two processors P" P2 of a multiplicity of processors of a multiprocessor system are indicated. On both processors, programs are provided for execution that carry items of information and data having differing formats.
For example, it is assumed that data in the Big Endian format are carried and processed on the processor P,.
In contrast, assume that data in the Little Endian format are carried on the processor PZ.
Therefore, in the case of an exchange of data between these two types of processors the data to be exchanged must be converted in a corresponding manner. The conversion is thereby preferably to take place by means of a conversion procedure UP executed on the processor P, In addition, an interface S is arranged between the two processors P" P2. This interface represents a software interface between the programs running on the two processors. The interface S is to be defined upon commissioning of the system, which definition takes place via the corresponding data layout for this interface. In the data layout, it is defined which programs communicate with one another during the execution and which data types are carried in these programs. In addition, a communication handler KH, which controls the exchange of messages between the two processors, is arranged in the interface S.
According to the invention, a tool is provided that stands in effective connection with a compiler. The compiler is assumed to be a standard commercially available compiler. The tool is started during the production of the software for the processor P,. In the tool, according to the definition stored there in the data layout, the conversion procedure UP is produced on the source code plane. As a result, the conversion procedure UP
becomes independent of the compiler used and is simple to implement. In the subsequent compiler run, the programs are translated together with the conversion procedure UP
(or: are translated together, using the conversion procedure] and are linked in the linkage editoi as a part of the communication handler ICH. These actions are to be carried out before the commissioning of the multiprocessor system.
In the following, during running operation a message N is to be sent from the processor P, to the processor Pz. For this purpose, the processor P, first hands over the message N to the communication handler KH. There the format of the message N is determined and is converted, by the conversion procedure UP implemented there, into the target format of the processor P2. The conversion takes place automatically via the conversion procedure UP, without the piogrammer's having to make provisions for this. After the conversion of the format, the message N is supplied to the processor Pz in its processor-specific format.
According to the above exemplary embodiment, it was assumed that the conversion of the data formats takes place in the processor P,. However, this is not a limitation of the invention. The conversion can also take place in the processor Pz. Moreover, it can be defined that the conversion is to be carried out exclusively during the transmission of a message N, or exclusively during the reception.
Modern communication systems are fashioned as multiprocessor systems. This means that the controlling of the system-internal processes is carried out by a multiplicity of processors.
As a rule, such communication systems are fashioned as heterogeneous systems.
This means that processors of various manufacturers are used in the communication system.
However, these processors thereby also operate according to manufacturer-specific standards. Thus, for example, data of the individual processors are stored in different formats in the respectively allocated memory. This does not result in a limitation of operation as long as programs, which as a rule are respectively allocated to one processor during their execution, read these data from the relevant memory, process them, and write them into the memory again, since in this case the same data format is always used. Problems most often arise when messages or data are exchanged between processors or, respectively, between programs running on these processors, because here, if necessary, these data must be adapted to the different data formats.
Thus, for example, data that are processed on processors of the Motorola family are stored by these processors in a LSB HI format (Least Significant Byte at Highest Address), also known as the Big Endian format. In contrast to this, data that are processed on processors of the Intel family are stored by these processors in a LSB LO format (Least Significant Byte at Lowest Address), also known as the Little Endian format. For this reason, in the case of a data exchange between these two types of processors the data have to be converted correspondingly.
For the solution of such problems with respect to different data formats in process communication in heterogeneous systems, in the prior art a specific transfer format is defined for the exchange of messages and data (e.g. ASN.1 ). This means that in general before every exchange of messages the processor-specific format is converted into a previously defined transmission format used only for the purpose of the exchange of messages.
Once the message has arrived at the target processor, the transmission format is converted back into the processor-specific format used there.
A problematic feature of such a procedure is that the programs that communicate with one another via the exchange of messages are each themselves responsible for the conversion of the messages to be exchanged between the processor-specific data format and the transfer format. However, all required format conversions must thereby be programmed explicitly by the developer of the application software in the coding of the respective program. In addition, in the use of this transfer format a total of two conversions must be carried out, namely on one hand a conversion of the format from the source processor into the transfer format, and from this format back into the format of the target processor.
Because, due to its structure, the transfer format is very extensive, the dynamics of the system is thereby adversely affected. Finally, with the strict application of this technique there is the problem that conversions from the processor-specific data format of the source processor into the transmission format and from the transmission format into the processor-specific data format of the target processor take place even given the sending of messages between programs that run on processors having one and the same data format. This has a further adverse effect on the dynamics of the system.
In addition, in the German patent application 19535306.4 a method is specified for the conversion of differing data formats with which messages are exchanged between processors on which different data formats are respectively used. For this purpose, the procedures required for the conversion of the data between the formats are already provided automatically during the translation process of the source programs. This is achieved in that the translation program, in accordance with the data types used in the source programs, produces conversion procedures during the course of the translation that are then called during the later execution of the translated programs, before the exchange of messages.
However, a problematic feature of such a procedure is that extensive interventions in the compiler must be carried out. For this purpose, detailed knowledge of the compiler is necessary, which makes this process expensive and uneconomical for the user.
The invention is based on the object of indicating a way in which the conversion of data formats can be controlled more efficiently without having to accept the disadvantages cited above.
In particular, an advantage of the invention is that before the commissioning [or: startup] of the multiprocessor system a tool is controlled by means of which, according to the definition of the interface stored in the data layout, a conversion procedure for the conversion of the data formats is produced, and in that, in a subsequent compiler run, the application programs are translated together with the conversion procedure [or: are translated together using the conversion procedure] and are linked in a linkage editor as a part of the communication handler. A conversion machine is thereby produced in fully automatic fashion from the interface definition. The required conversion is thereby carried out automatically during the exchange of messages.
The data structures can be transmitted in their original form, that is, without additional format information. In this way, a significantly higher level of performance is achieved. For this purpose, it is necessary that the source code of the data structures be known both to the sending and to the receiving processor.
Advantageous developments of the invention are indicated in the subclaims.
The invention is explained in more detail in the following on the basis of a graphically depicted exemplary embodiment.
According to the figure, as an example two processors P" P2 of a multiplicity of processors of a multiprocessor system are indicated. On both processors, programs are provided for execution that carry items of information and data having differing formats.
For example, it is assumed that data in the Big Endian format are carried and processed on the processor P,.
In contrast, assume that data in the Little Endian format are carried on the processor PZ.
Therefore, in the case of an exchange of data between these two types of processors the data to be exchanged must be converted in a corresponding manner. The conversion is thereby preferably to take place by means of a conversion procedure UP executed on the processor P, In addition, an interface S is arranged between the two processors P" P2. This interface represents a software interface between the programs running on the two processors. The interface S is to be defined upon commissioning of the system, which definition takes place via the corresponding data layout for this interface. In the data layout, it is defined which programs communicate with one another during the execution and which data types are carried in these programs. In addition, a communication handler KH, which controls the exchange of messages between the two processors, is arranged in the interface S.
According to the invention, a tool is provided that stands in effective connection with a compiler. The compiler is assumed to be a standard commercially available compiler. The tool is started during the production of the software for the processor P,. In the tool, according to the definition stored there in the data layout, the conversion procedure UP is produced on the source code plane. As a result, the conversion procedure UP
becomes independent of the compiler used and is simple to implement. In the subsequent compiler run, the programs are translated together with the conversion procedure UP
(or: are translated together, using the conversion procedure] and are linked in the linkage editoi as a part of the communication handler ICH. These actions are to be carried out before the commissioning of the multiprocessor system.
In the following, during running operation a message N is to be sent from the processor P, to the processor Pz. For this purpose, the processor P, first hands over the message N to the communication handler KH. There the format of the message N is determined and is converted, by the conversion procedure UP implemented there, into the target format of the processor P2. The conversion takes place automatically via the conversion procedure UP, without the piogrammer's having to make provisions for this. After the conversion of the format, the message N is supplied to the processor Pz in its processor-specific format.
According to the above exemplary embodiment, it was assumed that the conversion of the data formats takes place in the processor P,. However, this is not a limitation of the invention. The conversion can also take place in the processor Pz. Moreover, it can be defined that the conversion is to be carried out exclusively during the transmission of a message N, or exclusively during the reception.
Claims (4)
1. Method for converting different data formats in a multiprocessor system, having at least two processors (P1, P2), on which application programs having data of differing formats are respectively processed, and between which an interface (S) is arranged, and between which messages (N) are exchanged under the control of a communication handler (KH), whereby the message (N) of the transmitting processor (P1) is converted into the format of the processor (P2) receiving the message (N), characterized in that before the commissioning of the multiprocessor system a tool is controlled by means of which, according to the definition of the interface (S) stored in the data layout, a conversion procedure (UP) for the conversion of the data formats is produced and is linked as a part of the communication handler (KH).
2. Method according to claim 1, characterized in that the conversion procedure (UP) is produced on the source code plane, and in that in a subsequent compiler run the application programs are translated together with the conversion procedure (UP) [or: are translated together, using the conversion procedure]
and are linked into the communication handler (KH) using a linkage [or:
connective]
program.
and are linked into the communication handler (KH) using a linkage [or:
connective]
program.
3. Method according to claim 1, 2, characterized in that the communication handler (KH) is an integral component of the interface (S).
4. Method according to claim 1 to 4, characterized in that first a message (N) is handed over by the sending processor (P1) to the communication handler (KH), where an evaluation of the data format of the sending processor (P1) and of the receiving processor (P2) is carried out, and in that a conversion of the data format of the message (N) into the data format of the processor (P2) receiving the message (N) is carried out, and in that the message is supplied in this format to the receiving processor.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE19837215.9 | 1998-08-17 | ||
| DE19837215 | 1998-08-17 | ||
| PCT/DE1999/002575 WO2000011560A2 (en) | 1998-08-17 | 1999-08-17 | Method for converting different data formats |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2340708A1 true CA2340708A1 (en) | 2000-03-02 |
Family
ID=7877761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002340708A Abandoned CA2340708A1 (en) | 1998-08-17 | 1999-08-17 | Method for converting different data formats |
Country Status (4)
| Country | Link |
|---|---|
| EP (1) | EP1105807B1 (en) |
| CA (1) | CA2340708A1 (en) |
| DE (1) | DE59901753D1 (en) |
| WO (1) | WO2000011560A2 (en) |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5287511A (en) * | 1988-07-11 | 1994-02-15 | Star Semiconductor Corporation | Architectures and methods for dividing processing tasks into tasks for a programmable real time signal processor and tasks for a decision making microprocessor interfacing therewith |
| DE19535306A1 (en) * | 1995-09-22 | 1997-03-27 | Siemens Ag | Process for converting different data formats |
-
1999
- 1999-08-17 CA CA002340708A patent/CA2340708A1/en not_active Abandoned
- 1999-08-17 DE DE59901753T patent/DE59901753D1/en not_active Expired - Fee Related
- 1999-08-17 EP EP99952427A patent/EP1105807B1/en not_active Expired - Lifetime
- 1999-08-17 WO PCT/DE1999/002575 patent/WO2000011560A2/en active IP Right Grant
Also Published As
| Publication number | Publication date |
|---|---|
| WO2000011560A3 (en) | 2000-05-25 |
| EP1105807A2 (en) | 2001-06-13 |
| WO2000011560A2 (en) | 2000-03-02 |
| DE59901753D1 (en) | 2002-07-18 |
| EP1105807B1 (en) | 2002-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6085203A (en) | Method for converting data formats which differ from one another | |
| US5428799A (en) | Redirection of interrupts to microprocessors | |
| KR890000734B1 (en) | Method of and apparatus for controlling automated device | |
| US6567837B1 (en) | Object oriented processor arrays | |
| US6477586B1 (en) | Remote procedure calls in distributed systems | |
| CA2340708A1 (en) | Method for converting different data formats | |
| JP2002259126A (en) | Software constituent for distributed control system, and method for designing control system | |
| EP0578496B1 (en) | Job execution method in multi-CPU system | |
| US7426531B1 (en) | Distributed electronic data processing | |
| US20210141357A1 (en) | Control System for an Automation System and Method for Operating an Automation System | |
| KR20010048804A (en) | Apparatus And Method For Remote Input/Output Control In Real-time System | |
| Baginski et al. | Open control-the standard for PC-based automation technology | |
| KR100388065B1 (en) | Method and apparatus for providing shared library on distributed system using UNIX | |
| JPH1065726A (en) | Distributed control system | |
| US6728252B1 (en) | LSI control apparatus for communication, method for controlling the same, and distributed control net work system having communication LSI control apparatus | |
| KR970078205A (en) | Client-server distributed transaction communication control method | |
| JPH09245003A (en) | Parallel distributed processing system and method therefor | |
| KR100276080B1 (en) | A translation method from process in sdl-92 to task in chill-96 | |
| KR920010411B1 (en) | Hardware installing testing program | |
| KR100229728B1 (en) | A device of implementation for covos in unix system | |
| JP2500006Y2 (en) | Programmable controller system | |
| EP1121628A2 (en) | Object oriented processor arrays | |
| CN114090292A (en) | Middleware calling method and system for Android intelligent device | |
| EP1133102A1 (en) | An interface to a network management system of a communication network | |
| JPH08272757A (en) | Multiprocessor system and program starting method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Dead |