KR20030053296A - Standard messagin system with base on XML - Google Patents

Abstract

PURPOSE: An XML(eXtensible Markup Language) based standard messaging system is provided to improve the compatibility and the extendability between systems by making the messaging system using a non-standard message exchange a message with the messaging system using a standard message. CONSTITUTION: A text/form generator(110) has the form information of a document and the information for generating the header information. An expression type processor(120) defines the generated document as an expression type selected by a user. A message processor(130) converts the message received by the messaging system into a format used by the corresponding system, and forms the message in order to fit to the corresponding form. A dictionary(150) is referred to convert the received message into the format used by the corresponding system. A database management part(140) stores the generated and inputted message. A message exchanging part(170) transmits/receives the written message.

Description

Standard messagin system with base on XML

The present invention relates to a messaging system, and more particularly to an XML-based standardized messaging system that facilitates compatibility with all schemes by using standardized messages in electronic document exchange.

Historically, the messaging system used a system that applied a system-specific message format and processing procedure.

1 is a block diagram showing the configuration of a conventional message handling system.

Particularly, in the present invention, a messaging system used by the military will be described as an example, and referring to FIG. 1 configured accordingly, a conventional message handling system (hereinafter referred to as MHS) can be written according to a form. Professional processing client 10 for transmitting and receiving, X.500 (20) for distributed directory service for storing and managing data in the professional processing client 10, and X.400 (30) for transmitting and receiving messages. And a work flow (hereinafter referred to as WF) server 40 which receives a message received from a client, performs file processing or database update processing, and delivers the message to the X.400 30 so as to be transmitted and received by mail. , File unit 60 for file processing, specialized DB 70 for managing electronic document information, etc., form DB 80 for managing form information and managing interlocking syntax, and accompanying data It is configured to include a secondary application server 90 for management and services, and MHS management processor (MMP) 50 for the management of the MHS.

At this time, the definition of the preamble and the form is as follows.

The form refers to the format of a given document. It defines the properties of interlocking syntax, interlocking method, table information, cell information, cell group, etc., and the preamble includes a header for receiving and sending in the message written according to the above form. Refers to the document that is actually sent.

In the MHS configured as described above will be described for each configuration as follows.

First, the professional processing client 10 is a form processing client 12 having a message format form information as a part which is configured identically to each client, and displaying a form according to a user selection, and provided by the form processing client 12. A specialized processing client 11 that adds header information for inputting and transmitting actual data into a document form, an encoder / decoder 13 for encoding and decoding for encrypting or compressing a created document, and for communicating with a server. And a first cl / server (C / S) communication unit 14 and an LDAP (lightweight directory access protocol) 15 which is a directory related protocol for retrieving information from other clients distributed for the document creation and management. It is configured by.

The LDAP 15 is interworked with the X.500 20. The X.500 20 includes a directory specification agent (DSA) 21 and an LDAP server 22 for performing a user request. The LDAP 15 is connected to the LDAP server 22 to use information retrieval and directory services.

In addition, the WF server 40 may include a message notification unit 41 for notifying a message upon receiving the message, a second C / S communication unit 42 for communicating with a client, an encoder / decoder 43, and a WF server ( 4), the specialized module 45 for the professional processing, the form module 46 for the document form processing, the Tuxedo client 47 for interworking with the auxiliary application server 90, and the first file. A processing unit 48, a first structured query language (SQL) 49, a WF gateway 49a for transmitting and receiving messages to and from the X.400 30, and a second file processing unit 49b. And the second SQL 49c.

The secondary application server 90 to which the Tuxedo client 47 connects and interoperates includes a Tuxedo server 91 in charge of a TP-monitoring process and a secondary application DB 92.

On the other hand, MMP (50) for overall management is configured for each part management, such as form management (51), professional processing management (52), X.400 management (53), X.500 management (54), In addition, the server includes a graphical user interface (GUI) 55 for providing a user interface so that an administrator can manage the system more easily.

The MHS configured as described above writes the full text using the information retrieval of X.500 through the LDAP 15 in the professional processing client unit 10, encodes it in the encoder / decoder 13, and matches the private MTF in accordance with the rules defined in the MHS. When the message is written in (message text format) and transmitted to the server, the WF server 40 processes this.

The WF server 40 receives and processes the private MTF, and transmits the generated form through the WF gateway 49a connected to the X.400 so that it can be distributed by mail, and stored as a file in a database. Will be in charge of.

As shown in FIG. 1, the file and database may be divided into a file 60, a full-text DB 70, a form DB 80, and an accompanying application DB 92. The file 50 includes a form, an enclosed file, Attached files and the like are managed, the professional DB 70 manages the professional information, user information, environmental information and file link information.

In addition, the form DB 80 manages form information and interlocking syntax information, and finally, the unit application DB 92 manages information, operations, personnel, logistics data, and the like.

As described above, the conventional MHS constitutes a private MTF according to a rule defined separately in the system to send and receive messages, and in particular, military operations such as command, control, and communication intelligence (C3I) in conjunction with the unit application DB 92. It can be used in response support systems and the like.

The linkage with the companion application DB 92 is divided into input linkage for reading data from the companion application DB 92 and output linkage for updating the companion application DB 92 using data of aquaculture specialist.

However, when using a conventional messaging system, private MTFs created by a given key field and content type cannot be interpreted in other types of systems, and at present, there is no interworking with a standardized messaging system through the Internet. there is a problem.

Therefore, in order to interoperate with the conventional messaging system, a messaging system having the same keyfield and content format must be separately constructed so that documents can be interpreted and processed.

In order to solve the above problems, the present invention is to convert the received private MTF document to XML by defining the XML format corresponding to the private MTF in a dictionary format for document linkage of other systems based on standardized XML Its purpose is to provide an XML-based standardized messaging system that can be interpreted, processed, and created by using XML to create and transmit a corresponding private MTF format document so that it can be linked with other system documents. .

1 is a block diagram showing the configuration of a conventional message handling system.

Figure 2 is a block diagram showing the configuration of an XML-based standardized messaging system of the present invention.

XML-based standardized messaging system according to the present invention,

A full text / form generation unit having form information of a specific document to be created by a user using a messaging system and information for generating header information for transmitting and receiving the created document;

A representation processor for defining a document of a format generated by the full text / form generation unit to be suitable for a presentation format selected by a user;

A message processor configured to convert a message received by the messaging system into a format used by the system, and to configure the message according to a corresponding form;

A dictionary for referencing to convert a message received by the message processor into a format used by the corresponding system;

A database manager which stores the generated message input message;

A message exchange unit for transmitting and receiving the created message;

Characterized in that it comprises a system manager for management of the messaging system.

Preferably, the dictionary,

It defines common word definition and object between private document form and standard document form, and when changing and adding, it is characterized in that mutual system matches the corresponding contents and defines and stores commands corresponding to each document form.

Preferably, the message processor,

A message conversion unit for converting the received message into a language format used by the corresponding messaging system;

It is configured to include a message generating unit for configuring the converted message to match the form.

Preferably, the database manager,

It is characterized by converting data of standard document format into certain data format and storing.

Preferably, the message exchange unit is to provide a variety of protocols and transmission media according to the situation in order to exchange the messages for mutual reliability of performing the message exchange.

The XML-based standardized messaging system according to the present invention configured as described above will be described with reference to the accompanying drawings.

2 is a block diagram showing the configuration of an XML-based standardized messaging system of the present invention.

In particular, Figure 2 will be described by taking the C4I TMS (technical message system) used in the military according to an embodiment of the present invention as an example.

Referring to FIG. 2, a text / form generation unit 110 for generating a form and a full text, a presentation method processor 120 for defining a presentation method in a message generated according to a browser using a document, and a reception; Each information object is defined with a message processor 130 for processing a message, a system manager 160 for managing a message system, and a data in common to enable conversion between a private MTF format document and an XML document. XML-MTF dictionary 150 for storing and storing, a database manager 140 for storing and managing the generated message or input message, and a message exchange unit 170 for sending and receiving messages between servers. .

In particular, the full text / form generation unit 110 may include a CPAS message 111 for generating a form and full text of a command post automation system (CPAS) message, and an XML-MTF for generating a private MTF and an XML message. The message 112 includes a message, and the message processor 130 includes a message generator 131 and a message converter 132.

When the user wants to transmit a message in the TMS configured as described above, when the user selects a desired document form, the full text / form generation unit 110 retrieves form information according to the user's selection to provide a document form on the user screen. do.

When the user inputs data in accordance with the document form, a message is transmitted by adding headers according to the sending and receiving. In this case, only the content of the missing data is transmitted and only the data applied to the form is displayed. do.

The message is transmitted from the message exchange unit 170.

In addition, the message received by the message exchange unit 170 is converted to match the language format used by the TMS in the message processor, when the language version or the language of the server that sent the message is different, that is, converted If the received message is an XML format message, when the current TMS uses the private MTF format, the message conversion unit 132 converts the XML format message into a private MTF format message. Reference is made to the XML-MTF dictionary 150 in which the stored information is stored.

The converted message is reconfigured to fit the corresponding form, which is performed by the message generator 131, and defined by the expression processor 120 to match the browser used by the current user so that the user can view the message.

As described above, the XML-based standardized messaging system according to the present invention maintains, changes, and adds object definitions and common data to each other for compatibility between the non-standardized private MTF format and the standardized XML format used in the messaging system. By converting messages sent and received by referring to the available dictionaries, messaging systems using non-standard messages and messaging systems using standard messages can exchange messages with each other. There is an effect of facilitating expandability.

Claims (5)

A full text / form generation unit having form information of a specific document to be created by a user using a messaging system and information for generating header information for transmitting and receiving the created document; A representation processor for defining a document of a format generated by the full text / form generation unit to be suitable for a presentation format selected by a user; A message processor configured to convert a message received by the messaging system into a format used by the system, and to configure the message according to a corresponding form; A dictionary for referencing to convert a message received by the message processor into a format used by the corresponding system; A database manager which stores the generated message input message; A message exchange unit for transmitting and receiving the created message; XML-based standardized messaging system, characterized in that it comprises a system manager for management of the messaging system. The method of claim 1, wherein the dictionary is XML that defines the definition and object of common word between private document format and standard document format, and makes it possible to match the contents between systems when changing and adding, and to define and store the command corresponding to each document format. Based standardized messaging system. The method of claim 1, wherein the message processor, A message conversion unit for converting the received message into a language format used by the corresponding messaging system by referring to the dictionary; And a message generator configured to configure the converted message in accordance with a corresponding form. The method of claim 1, wherein the database management unit, Standardized messaging system based on XML, characterized by converting the data of the standard document format to a certain data format. The XML-based standardized messaging system of claim 1, wherein the message exchange unit exchanges messages by providing various protocols and transmission media according to a situation for mutual reliability of performing a message exchange.