JPH0622354A - Processing system for transfer syntax in compliance with osi - Google Patents

Abstract

PURPOSE:To convert a transfer syntax so as to make the processing of application efficient when the transfer syntax is received with respect to the processing system of the transfer syntax in compliance with OSI comprising combination of information elements consisting of a tag representing a type of the information elements, length of the information and information element content data. CONSTITUTION:This system is provided with a transfer syntax conversion section 2 converting a reception transfer syntax 1 into data suitable for processing the application. The transfer syntax conversion section uses message configuration data 3 defined in response to the application to convert each information of the received transfer syntax. Then an information element identification data set 4a comprising identification data of each information element in the order defined by the conversion and an information element content data set 4b stored in an address commanded by the identification data are generated and given to the application.

Description

Detailed Description of the Invention

[0001]

The present invention relates to OSI (Open Systems I).
nterconnection) Concerning the processing method of the conforming transfer syntax.

In recent years, in the field of information and communication, development and utilization of devices and systems compatible with the OSI standard have been promoted. This OSI is standardized by hierarchizing the communication protocol between computers into seven layers, and the presentation layer (sixth layer) therein is a general-purpose information exchanged by an upper application (application layer: seventh layer). The encoding process is performed, and the encoded result is called a transfer syntax. The application layer handles the meaning of the information to be exchanged without being aware of encoding, and what expresses the meaning is called abstract syntax. In this way, the presentation layer makes it possible to realize general and systematic information representation rules by making the transfer syntax and abstract syntax rules independent regarding the information exchanged to realize the application.

[0003]

2. Description of the Related Art The presentation layer of OSI converts an abstract syntax defined by an application layer into a transfer syntax, or converts a transfer syntax into an abstract syntax. At this time, in order to enable general-purpose conversion, a general rule for correspondence between the abstract syntax and the transfer syntax is provided, and the abstract syntax notation rule 1 common to both layers
(Referred to as ANS.1) and its encoding rules are defined.

The general structure of the transfer syntax specified by OSI is shown in FIG. One transfer syntax is composed of one or more information elements, and in the example of FIG. 7, is composed of three information elements 1 to 3. The information elements can have a hierarchical structure, and in the case of FIG. 7, the information element 2 is an example.

Each information element includes a tag (Tag) indicating the type of information element (type of data to be transferred, etc.) and a length (Leng) indicating the data length of the next value (Value).
th) and a value (Data) which is a value (data) of an actual information element.

The tag value and the value value (coding) of the information element forming the transfer syntax are determined for each application, and there are applications whose contents change in the following points.

The arrangement order of each information element is arbitrary. Figure 7
In the example, information elements 1, 2 and 3 are arranged in this order, but
It doesn't matter if they are arranged side by side. Information elements include mandatory (called mandatory) information elements and information elements that can be arbitrarily selected according to optional conditions and are not necessarily included in the transfer syntax. Although the information elements 1 to 3 are included in the example of FIG. 7, the information elements 1 and 3 are included.
In some cases, it only contains.

The value data length does not take a fixed value. In the example of FIG. 7, Value-1 is 3 if it exists.
What was a byte is 5 bytes in other cases. A conventional method for receiving and processing such a transfer syntax will be described with reference to FIG.

A. Shows an example of transfer syntax. In this example, the information element (displayed by IE: InformationElement) is IE1.
To IE4, IE1 is a mandatory information element (3 bytes), and IE2 to IE4 are optional information elements (4 bytes, 3 bytes, and 5 bytes, respectively). Conventionally, when this transfer syntax is received, it is stored in the memory and processed as it is.

Referring to FIG. Is a basic flow in the application, IE1 is read first, and the read I
The process corresponding to E1 is executed. After that, the same processing is sequentially performed for each IE.

FIG. 9 shows the B. 2 is a processing flow of reading an information element (IE) in FIG. That is, the address of the first tag (first IE of the memory storing the IE)
(The address where the tag is stored) is obtained (S in FIG. 9)
1) Next, the tag value (data type) required in the application, that is, the tag value to be searched is stored (at step S2). Then, the tag is read from the previously obtained address (at step S3) and it is determined whether the tag value matches the tag value stored at step S4. If a match is obtained, the output data of one IE (one of IE1 to IE4) is read and set (at step S5).

If the tag values do not match, it is determined whether the tag is the final tag (at step S6). If it is not the final tag, the address of the next tag is calculated (at step S7), and the process returns to step S3 to repeat the same processing. In the processing of FIG. 9, when the tag value of IE1 is first stored as the tag value to be searched, the above S1 to S
When the corresponding output data is obtained by each process of 5 and the tag value of IE3 is stored as the tag value to be searched next, the processes of S1 to S6 and the processes after returning to S3 are performed. Be seen. Hereinafter, similar processing is performed for each tag value to be searched. Also, even if IE3 and IE4 are not included in the received transfer syntax because of options, it cannot be determined that they are not included unless all the IEs are read by repeating the above processing.

[0013]

The transfer syntax as described above is transferred by the presentation layer between computers, and the application directly analyzes the transfer syntax while proceeding with the processing requested by the other party. There is a problem that efficiency is poor because of such conditions. Further, the processing shown in FIG. 9 described above, that is, constantly searching for tags in the transfer syntax when reading an information element imposes a heavy load on the processing capacity of the system. In particular, in the actual transfer syntax, there are many cases where there are 20 information elements (IEs) and 10 or more of them are optional IEs. In such cases, the processing capacity of the system is greatly affected.

According to the present invention, when the transfer syntax is received, the presence or absence of the information element can be efficiently identified, and the data can be retrieved to prevent the deterioration of the processing capability.
It is intended to provide a processing method of a compliant transfer syntax.

[0015]

FIG. 1 is a block diagram showing the principle of the present invention. 1 in FIG. 1 is a reception transfer syntax received from the outside,
2 is a transfer syntax conversion unit that converts the received transfer syntax format message into an internal data format that is easy for the application to process, and 3 defines the types of information elements required according to the application, the arrangement order, etc. Reference numeral 4 is a conversion data storage unit which is composed of message data. The conversion data storage unit 4 stores the information element identification data set 4a and the information element content data 4b.

According to the present invention, when a transfer syntax is passed to an application, it is converted into a format determined by using the data defined by the application, and a data set representing the presence / absence of the content data of each information element and the data storage position. It is to be converted into data of information element contents.

[0017]

In the message structure data 3, all data necessary for creating the information element identification data set 4a and the information element content data 4b in the conversion data storage unit 4 are set for each message.

In FIG. 1, the transfer syntax is communicated from another device such as a computer to obtain the received transfer syntax 1.
In the transfer syntax conversion unit 2, the information element (tag) specified in the list of the message configuration data 3 is the reception transfer syntax 1
Is searched for each information element (composed of a tag, a length, and a value) using a tag, and if there is, a flag is set at the position of the identification data of the information element of the information element identification data set 4a (“1”). ), The content data (value) of the information element is stored at the head of the information element content data 4b. Further, after the flag of the information element of the information element identification data set 4a, the address storing the information element content data is written and the data length (length) is written.
The information of this data length is not always necessary because the address is stored.

If the specified information element does not exist as an option, the position of the identification data of the information element in the information element identification data set 4a is not flagged ("0"). No address or data length related to this flag is set.

By carrying out such a conversion operation sequentially according to the list of tags set in the message structure data 3 corresponding to the message, the information element contents data 4b of the conversion data storage unit 4 contains the actually received information. If the element exists, a flag is set, the information element content is sequentially stored in the information element content data 4b at a position subsequent to the previous information element content data, and the optional information element that is not received does not exist due to the flag. Is displayed and nothing is stored in the information element content data 4b.

The data thus created in the conversion data storage unit 4 can be efficiently processed by the application. When the information element is of a hierarchical type, a plurality of bits are assigned as a flag, the flag bit at the head indicates the presence or absence of the information element, and the next bit indicates the presence or absence of a hierarchy. Also, when there are three or more layers, a bit indicating the presence or absence of the information element of each layer is provided accordingly.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 2 is a hardware configuration diagram for implementing the present invention, FIG. 3 is a processing flow of transfer syntax conversion of the embodiment, FIG. 4 is an application processing flow, FIG. 5 is an example of expanding structural information elements, FIG. 6 is a configuration example of a system to which the present invention is applied.

In FIG. 2, 20 is a network and 21
Is a communication processing unit, 22 is a central processing unit (CPU), 23
Is memory. The communication processing device 21 is the network 20.
It has a function of communicating with an external device (another computer or the like) via the Internet, for example, OSI layers 1 to 6 and layer 7
Is a function that provides a common service to a plurality of application services, including a part of
It corresponds to functions such as P (Transaction Capability Application Part). The central processing unit 22 is the communication processing unit 2
1, connected to the memory 23, the memory 2 by the program
Each process is performed on the data of 3. 24 in memory 23
Is a first in-system communication work area (hereinafter referred to as the first area), in which the message received by the communication processing device 21 is stored, and the data is the OSI standard X. 208 /
X. 209 has a transfer syntax (each information element is composed of a tag, a length, and a value). Reference numeral 25 is message configuration data (corresponding to 3 in FIG. 1), which has the following data for various message correspondences.

Blank format of information element identification data set (26a) List of tags of information element included in each message Option / mandatory / default information of information element included in each message Expansion of structured (hierarchical) information element The information 26 is the data converted according to the present invention. A second message is stored in the form of the information element identification data set 26a and the information element content data 26b (internal data type).
Is an in-system communication work area (hereinafter, referred to as a second area), and this area is provided to the application.

The CPU 22 of FIG. 2 executes the processing flow of transfer syntax conversion shown in FIG. First, the address of the head tag (head address of the first area 24 in FIG. 2) is obtained (S1 in FIG. 3), and the tag value to be searched is stored from the message configuration data (25 in FIG. 2) (FIG. 3). Of S
2). This message configuration data is defined in advance according to a format suitable for application processing, and is defined for each operation of the application protocol.

Next, the tag (the address of the first tag) of the transfer syntax of the first area (24 in FIG. 2) is read (S3 in FIG. 3), and the read tag value is the tag value to be searched (S in the above S).
It is determined whether or not it matches the tag value stored in 2) (S
4). If no match is found, it is determined whether the tag is the last tag, and if it is not the last tag, the address of the next tag is calculated (at step S6) and the process returns to step S3. "No IE" (flag "0") is set to the data set (26a in FIG. 2) (step S7) and step S
Move to 10.

If the tag values match, the second area (see FIG. 2)
26) information element identification data set (26a in FIG. 2)
Set "with IE" to (set the flag to "1"),
The related data, that is, the value of the transfer syntax of the first area (24 in FIG. 2) is set as the information element identification data set (FIG. 2).
26a) storage address (represented by a relative address based on the start address, the next address is obtained by adding the data length) and the data length are set (S8 in FIG. 3), and the information element content data ( The first area 24 is located at the corresponding address in 26b) of FIG.
The value of the relevant tag is stored (S9 in FIG. 3).

Then, it is judged whether the conversion is completed (S1
0) If not completed, the address of the next head tag of the first area (24 in FIG. 2) is obtained (at step S11), the tag value to be searched next is stored (at step S12), and the process returns to step S3. Then, the same processing is performed for the next tag.

In the second area 26, the data whose transfer syntax has been converted by the above processing corresponds to each tag and the information element identification data set 26a consisting of the data of the flag, address and data length for each tag. Information element content data 26b including information element content data (value) is obtained.

The converted data of the second area 26 is processed by the processing flow of the application shown in FIG. In this process, first, the parameter I is set to 0 (S1 in FIG. 4), and then I + 1 is executed (S
2). Next, the I-th flag of the information element identification data set (26a) is read (at step S3), and it is determined whether this flag indicates that there is an information element (at least IE) (at step S4). When there is IE, the tag of the information element (IE) is decoded (at step S5), and the corresponding information element content data is obtained from the information element content data 26b using the address and data length of the information element identification data set 26a. The data is taken out and the processing corresponding to the tag is executed (at step S6). When the processing is completed, it is judged whether or not the current I is the last information element number (at step S7).
1 is executed and the same processing is performed. If the flag is not IE in step S4, step S7
Move to.

As described above, by using the data obtained by converting the transfer syntax in the application, when there is no data such as an optional tag, it can be immediately detected by discriminating the flag, so that the processing is performed efficiently. be able to.

Next, the contents of conversion for delivery to the application when the information element has a structural type will be described with reference to the structural information element conversion example shown in FIG. A of FIG. Is an information element identification data set, B. Is information element content data.

In the case of FIG. 5, the received transfer syntax has the same structural type as the transfer syntax shown in FIG. 8 of the above conventional example (information element content 2 and information element contents 21 and 22 below it). For the transfer syntax, information element 1 (tag 1, length 1 (L
1) and value 1), A. As shown in
The storage address a1 of the information element content data is set at the beginning of the information element identification data set, and the value of the information element is B.
It is stored as shown in. As the information element content 2 after that, the tag 2, the length 2 (L2), and the value 2 are the tag 21 as the information element content 21 of the two lower layers.
Length 21 (L21), value 21 and tag 22 as tag 22, length 22 (L22), value 22
Is received.

Regarding such a structured type information element,
The number of flags corresponding to the layer is provided. In the case of two layers as in this example, two flags f1 and f2 are provided, and the presence or absence of the information element corresponding to the tag is displayed by the first flag f1. The presence or absence of the lower hierarchy is displayed by f2. In this example, since there are information elements and lower layers as the identification data set for the tag 2, the two flags are "1, 1" and the storage address of the information element content data is a.
2, L2 is set as the length. For the tag 21, the two flags are "1,0" (there is no subordinate information element of this tag 21), the address is a21 (same as a2 above), the length is L21, and the same flag is applied to the tag 22. The address and length data are also A. Is set as follows. At this time, the information element content data of this information element content 2 is B. It is stored as shown in. That is, since the value of the information element content 2 is composed of the value of each lower information element, B. Information element content 2 as shown in
The information element content 21 and the information element content 22 are sequentially stored by the length of each data.

By storing in this way, the application can read the entire information element content 2 as one information element, but if necessary, only the information element content 21 (or 22) can be retrieved individually. it can.

According to the present invention, the processing method of the OSI compliant transfer syntax is the intelligent network capability (Capabili) which is currently being recommended by CCITT.
ty) Set 1 application protocol (IN
The present invention can be applied to an AP (Intelligent Network Application Protocol), and FIG. 6 is a configuration example of a system to which the present invention is applied.

In the intelligent network system shown in FIG. 6, a service switching point (SSP) 60 is composed of an exchange (including a computer) for switching subscribers.
61), 61 is a service control point (referred to as SCP) which is composed of a computer that receives a processing request from the SSP 60 and performs control and instructions, and 62 is a transmission line (SS7X.25, which transmits and receives signals between them). FDD
I, Ethernet, etc.).

With such an IN, the system uses SSP6.
When the status of the subscriber or the trunk line and various information (dial signal, subscriber information, etc.) are detected at 0, the request information including the signal corresponding to each status is transmitted to the SCP 62 via the transmission line 62. The SCP 62 processes the signal and returns a signal for exchange control and the like to the SSP 60 as response information. Such request information and response information are transmitted and received by the layer 6 transfer syntax for processing by the layer 7 application. By implementing the present invention in such a system, the processing efficiency of the system is improved.

[0039]

According to the present invention, the existence of each information element and the position of the content of the information element can be fixedly determined by the application, and the processing capacity for information retrieval is greatly improved. In addition, by separating the information element identification data set and the information element content data, as compared with the method of simply accommodating the information element content fixedly, the number of information elements that are not included in a specific transfer syntax is reduced. Since the memory is not used, the efficiency of memory use can be improved. Furthermore, by defining the sequence of the information element content data of the information element identification data set for each operation, it is possible to minimize the occupied memory amount unnecessarily for a certain transfer syntax.

Although the memory is dynamically allocated at the time of executing the protocol processing, a large memory capacity affects the processing capacity including the dynamic allocation, whereas according to the present invention, the memory is as described above. Improvements in throughput can be achieved over reductions in capacity.

[Brief description of drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is a hardware configuration diagram in which the present invention is implemented.

FIG. 3 is a processing flow of transfer syntax conversion according to the embodiment.

FIG. 4 is a processing flow of an application.

FIG. 5 is an expansion example of a structural information element.

FIG. 6 is a configuration example of a system to which the present invention is applied.

FIG. 7 is a diagram showing a general structure of a transfer syntax defined by OSI.

FIG. 8 is an explanatory diagram of conventional reception processing of a transfer syntax.

FIG. 9 is a processing flow of reading an information element (IE).

[Explanation of symbols]

 1 reception transfer syntax 2 transfer syntax conversion unit 3 message configuration data 4 conversion data storage unit 4a information element identification data set 4b information element content data

Claims (4)

[Claims] 1. In a processing method of an OSI-compliant transfer syntax in which an information element constituted by a tag indicating the type of an information element, a length of information, and information element content data is combined, a reception transfer syntax is adapted to processing of an application. A transfer syntax conversion unit for converting to data is provided, and the transfer syntax conversion unit performs conversion for each information element of the reception transfer syntax using the message configuration data defined according to the application, and is defined by the conversion. An OSI-compliant transfer syntax processing method characterized in that an information element identification data set composed of identification data of each information element in order and information element content data stored at a position indicated by the identification data are created. 2. The information element identification data set according to claim 1, wherein in the order of the defined information elements, a flag indicating the presence or absence of the defined information elements in a reception transfer syntax corresponding to each information element is provided. A processing method of an OSI-compliant transfer syntax, characterized in that, when there is an information element, the information element content data is stored and the data including the address. 3. The information element identification data set and the information element content data according to claim 2, which are passed to an application, and the application identifies a flag of each information element in the information element identification data set. Then, the processing method of the OSI-compliant transfer syntax is characterized in that information content data is extracted and processed for an information element having a flag of "Yes". 4. In claim 3, when the defined information element is a structural type having a hierarchical structure, identification data is set corresponding to each information element having a hierarchical relationship as the information element identification data set, Each identification data includes, in addition to a flag indicating the presence or absence of an information element, a flag indicating the presence or absence of hierarchical data, and the information element content data is individually stored, and the processing of the OSI-compliant transfer syntax is performed. method.