JPH01228043A - Method for communicating data between communication systems using different types of machines - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

DETAILED DESCRIPTION OF THE INVENTION Industrial Field of Application The present invention is directed to O3! Oven systems interconnection
The present invention relates to a data communication method between different types of communication systems in a network system based on a communication protocol.

2. Description of the Related Art A conventional method of data communication between different types of communication systems is shown, for example, in the tSO standard (ISO8B22). FIG. 5 is an explanatory diagram of a network system to which the present invention and the conventional data communication method between different types of communication systems are applied. In FIG. 5, 20 and 20' are application processes that implement communication functions using the O81 protocol;
1 and 21' are communication systems in which OSI protocol processing programs are implemented; 22 is a transmission path that physically connects the communication systems; and 23 to 29 are OSI protocol processing programs that are modularized for each layer. The communication system 1121 implements the communication-related portion of the application interface 20 by programs of layers 23 to 29. The application layer 23 manages communication functions according to various business contents of the application process 20. presentation layer 2
Step 4 converts the data structure unique to the application process and the common data structure (transfer syntax) required for transfer, allowing data to be accurately sent and received between processes even if each application process has a different data structure. Provide functions that can be used. The session layer 25 provides a function to transfer data while maintaining synchronization between processes that are communicating. Transport layer 26 ensures that data is transferred between communicating processes. The network layer 27 manages relaying and routing functions for establishing a communication path with a communication partner system. data link pM
28 detects bit errors occurring on the transmission line 22-;
Recovery means are provided to ensure the transmission of data frame J1. The physical N29 manages the electrical, mechanical, and physical conditions for using the transmission line 22 as a communication line, and guarantees the transmission of bit strings.

Fig. 6 shows a conceptual diagram of a processing module of the presentation layer for implementing the conventional method of data communication between systems. In Fig. 6, 1 is the presentation layer. 2 is a user interface unit that interfaces with each protocol of the application layer that is a presentation user; 3 is a protocol control unit that controls execution of the presensation protocol; 5 is a protocol control unit; The encoding section E5 converts the abstract syntax data structure used in Part 3 into a transfer syntax, and the E5 converts the transfer syntax received from the session interface section 7 into an abstract syntax data structure. The decoding unit 7 that transfers the data is a session interface unit that interfaces with the session layer.

In the configuration example described in (1)-4, conversion from abstract syntax to transfer syntax is performed as follows. Data manually entered by a presentation user via the user interface section 2 is expressed in one to L abstract syntax, and the protocol control section 3 adds header information to this input data. This header information is also written in abstract syntax. The data written in these abstract syntaxes is sent to the transmission/reception communication system,
the transfer syntax agreed upon by the river. At this time, there is only one transfer syntax base that has been agreed upon for one abstract syntax, and the correspondence relationship is notified in advance from the protocol control unit 3 to the encoding unit 5 and decoding unit 6, so the encoding unit 5 can refer to that information and perform appropriate encoding.

Further, the conversion from the transfer syntax to the abstract syntax is similarly performed by the decoding unit 6 with reference to the information on their correspondence.

FIG. 7 is an explanatory diagram showing a method for determining the correspondence between abstract syntax and transfer syntax in the protocol control unit 3. In order to determine only one transfer syntax base for each abstract syntax (ASI, AS2,..., ASk), when establishing a connection for the communication system lock with which you want to communicate, the connection-initiating gutter 1t system List of transfer syntax bases supported by one system ((TS 1-1, -, TS
l-n 1), (TS 2-1, -...,
T S 2- n 2),...-1 (TSk-1
, ..., TSI<-nk)) to the responding communication system. The responding communication system determines whether each transfer syntax group included in the received list can be used, and if it can be used, it marks O, and if it cannot, it marks l (provider abort) or 2 (user abort). ) mark. Next, select one to actually use from among the available transfer syntax bases marked with 0. TSI-3, TS2-1, ......, T S k
-2), return the result to the initiating communication system. When the negotiation of the transfer syntax base is completed in this way and the transfer syntax name is agreed upon on a one-to-one basis for each abstract syntax, the result is the presentation context identifier (1, 3,...
..., 2-1) and is used when encoding and decoding presentation user data.

Problems to be Solved by the Invention However, in the conventional data communication method between heterogeneous systems, the transfer syntax name agreed upon between the communicating communication systems must correspond to the abstract syntax on an l-to-l basis. For example, the receiving communication system may not be able to correctly decode the transfer syntax, so when the presentation user wishes to communicate data using a different type of transfer syntax name, the presentation context change service must be used, or If this service is not supported, the connection must be broken and then re-established specifying the desired transfer syntax name; therefore, especially in the latter case, the presentation user may It is not possible to respond quickly to processes such as switching applications.

The present invention allows for multiple transfer syntax names to be agreed upon between the communication systems of the sender and the receiver, and unifies the format of all transfer syntaxes to be suitable for decoding the used transfer syntax. To provide a data communication method between heterogeneous systems that enables accurate transmission and reception even when transfer syntax names are dynamically switched, and that can quickly respond to presentation user requests.

Means for Solving the Problems In a network system that realizes data communication between communication systems using the O8I protocol, each communication system uses an OSI protocol processing program that is modularized for each layer, and a conversion before abstract syntax and transfer syntax. It has a plurality of types of conversion functions to perform, and a means for exchanging information regarding the conversion functions between the communication systems, and when negotiating a presentation context, the communication systems on the sending side and the receiving side exchange a transfer syntax name and its corresponding information. By mutually exchanging information regarding the conversion function, the transmitting communication system
Dynamically select and use an arbitrary transfer syntax name from multiple transfer syntax names agreed upon between sender and receiver for one abstract syntax,
The first field of the created transfer syntax contains information about the conversion function that the receiving communication system should use for decoding, and the transfer syntax name is dynamically switched to provide a data communication method between different types of communication systems. .

Operation The present invention uses the method described above to perform the following operations when establishing a connection.
A presentation context change service is supported by allowing multiple transfer syntax names to be agreed upon for one abstract syntax and by allowing dynamic selection of any transfer syntax name included in the set of agreed transfer syntax names. This makes it possible to change the type of transfer syntax used without breaking the connection, even between communication systems that are not compatible.

Embodiment FIG. 1 shows a conceptual diagram of the configuration of a presentation layer processing module to which a data communication method between heterogeneous communication systems in an embodiment of the present invention is applied, and is the same as the conventional example shown in FIG. The parts are numbered the same. 1st
In the figure, 4 indicates the correspondence between the abstract syntax and the transfer syntax name agreed upon between the communication systems on the sending side and the receiving side, and the storage address of the processing routine (hereinafter referred to as a parser) that performs the conversion before these syntaxes. This is the context management unit that manages the .

FIG. 2 is an explanatory diagram showing a method of managing transfer syntax names in the context management unit 4 of FIG. 1.

When establishing a connection between systems, each abstract syntax (ASI, AS2,..., AS) of the initiating communication system is
In order to know which transfer syntax names are also supported by the responding communication system among the transfer syntax names supported for k), the connection initiating communication system creates a list of transfer syntax names supported by its own system (( TSI-1
, ---, TSI-nl), (TS2-1.----
-, TS2-n2), ......, (TSk-1, -
--, TSk-nk)) and the address where the parser for each transfer syntax name month is stored is sent to the responding communication system. The responding communication system determines whether each transfer syntax name included in the received list can be used, marks it as 0 if it is usable, and stores the address of the parser of the initiating communication system for each transfer syntax name. Also, if it is not used, mark 1 (provider abort) h) 2 (user abort). Transfer syntax names marked with 0 are considered to have been agreed upon between both communication systems, and the address where the agreed transfer syntax name and the parser that uses those transfer syntaxes in the responding communication system are stored. and is returned to the initiating communication system. As a result, both communication systems mutually know the agreed upon transfer syntax name and the address of the parser of the other communication system corresponding to the transfer syntax name, and this information is held in the context management unit 4. In addition, in order to obtain the information to be held by the context management unit 4 as described above, the flowcharts of the processing carried out by the protocol control unit of the communication system of the initiating side and the response example are shown in FIGS. 3(a) and 3(a), respectively. It is shown in Figure 3 ([)).

In the above configuration example, conversion from abstract syntax to transfer syntax is performed as follows. The protocol control unit 3 in FIG. 1 passes abstract syntax data to the encoding unit 5, and dynamically selects and notifies the context management unit 4 of a transfer syntax name.

From the information held therein, the context management section 4 passes the encoder storage address corresponding to the selected transfer syntax name and the address of the parser to be used by the receiving communication system to the encoding section 5. The encoding unit 5 formats the abstract syntax data into a transfer syntax using the information 1- below.

However, since the correspondence between the abstract syntax and the transfer syntax is not uniquely determined, encoding and decoding are performed as shown in FIG. 4 so that the transfer syntax can be correctly decoded in the receiving communication system. Now, n abstract syntax (ASI
, AS2, . . . , ASn). Each abstract syntax is processed by the encoder corresponding to the selected transfer syntax name in Figure 4 (a).
) is converted to a transfer syntax with the basic format. In FIG. 4(a), 10 is the first field of the transfer syntax, which stores the address of a parser necessary for the receiving communication system to decode this transfer syntax. 11 indicates encoded data content;
EOC of 12 indicates the end of data content. When encoded in this format, the receiving communication system uses the parser stored at the address written in the first field of the received transfer syntax at the time of decoding to use the subsequent data until the EOC is detected. All you have to do is apply it, and the used transfer syntax can be easily decoded. Since actual protocol data consists of n abstract syntaxes, the transfer syntax can be created by concatenating the basic formats as shown in Figure 4(b). In this case, the parser that decodes the transfer syntax is The parser starts from the one written in the field, and switches to the parser written in the next field each time an EOC is detected. Figure 4 (b
), TSk (k=1, . . . , n) indicates the transfer syntax name of the abstract syntax ASk. Also, the fourth
As shown in Figure (C), (b) may be modified to collect the first fields of each transfer syntax in one place.

As shown in (L), according to this embodiment, the addresses of the parsers for the transfer syntax names used between systems are mutually notified when establishing a connection, so the transfer syntax name corresponding to each abstract syntax can be uniquely assigned. By including the parser address of the transfer syntax in the transfer syntax, it is possible to accurately decode it in the communication system on the receiving side, even if the transfer syntax is not determined in advance.

In this embodiment, the address of the parser to be used in each communication system is used to identify the transfer syntax, but the object identifier of the transfer syntax name exchanged during connection negotiation may also be used.

Further, in this embodiment, the context management unit 4 is provided to hold information regarding the correspondence between the abstract syntax and the transfer syntax, but this information may be held within the protocol control unit 3.

As described in detail, according to the present invention, negotiation of the correspondence between an abstract syntax and a transfer syntax only needs to be performed once per connection, and when creating a transfer syntax, it is necessary to negotiate the correspondence between an abstract syntax and a transfer syntax only once. Since any transfer syntax name can be dynamically selected from the syntax names, it is possible to switch transfer syntax names while maintaining the connection even in communication systems that do not support context change services, making it possible to switch between transfer syntax names while maintaining the connection, making it easier for presentation users to use various applications. can be quickly responded to, and its practical effects are significant.

[Brief explanation of the drawing]

FIG. 1 is a conceptual diagram of a configuration of a presentation layer processing module according to an embodiment of the present invention, FIG. 2 is an explanatory diagram of a presentation context management method according to the embodiment, and FIG. 3 is a diagram illustrating a presentation context management method according to the embodiment. FIG. 4 is an explanatory diagram of the encoding/decoding method of the same embodiment, FIG. 5 is an explanatory diagram of a network system to which the present invention and the conventional data communication method are applied, and FIG. 6 is a conventional presentation diagram. FIG. 7, which is a conceptual diagram of the structure of a layer processing module, is an explanatory diagram of a conventional presentation context management method. l...Processing module that implements presentation layer services and protocols, 2...
...User interface section, 3...Protocol control section, 4...Context management section, 5
... Encoding section, 6... Decoding section, 7... Session interface section, 10...
...First field of transfer syntax, 11...
Data content of transfer syntax, 12... Content end identifier, 20.20 '... Application process, 21, 21''... Communication system, 22
...Transmission path, 23...Application layer, 24.
... Presentation layer, 25 ... Session layer, 26 ... Transport layer, 27.
...Network layer, 28...Data link layer, 29...Physical layer. Name of agent: Patent attorney Toshio Nakao (1 person) Figure 2 Figure 3 + Q) TH side communication system (b) Charcoal? ≦Bond detection 1 wound system entered Figure 4

Claims (1)

[Claims] In a network system that realizes data communication between communication systems using the OSI protocol, each communication system has an OSI protocol processing program that is modularized for each layer, and multiple types of conversion functions that convert between abstract syntax and transfer syntax. , a means for exchanging information regarding the conversion function between the communication systems, and during presentation context negotiation, the communication systems on the transmitting side and the receiving side mutually exchange information regarding the transfer syntax name and the corresponding conversion function. The transmitting communication system is 1.
An arbitrary transfer syntax name is dynamically selected and used from multiple transfer syntax names agreed upon between the sender and the receiver for the same abstract syntax, and the first field of the created transfer syntax is used for decoding by the receiving communication system. Contains information about the power conversion function,
A data communication method between heterogeneous communication systems that dynamically switches transfer syntax names.