KR20110049059A - Flexible adapter system for data transfer among various protocols - Google Patents

Abstract

PURPOSE: A flexible adapter system for transferring data among various protocols is provided to support variable communication environments by defining a processing method of a transceiving packet through an XML. CONSTITUTION: A packet definition part(100) defines the data processing method about an input and output data of a packet which is transmitted to various protocols. An XML mapper(200) acquires specific parts of data in the XML form packet data. The XML mapper defines a method for designating data acquisition route in XPATH and a method for processing data with a specific structure. A flexible adapter(300) is processed according to the protocol which transmits various packets by the definition part.

Description

Flexible adapter system for data transfer between various protocols. {FLEXIBLE ADAPTER SYSTEM FOR DATA TRANSFER AMONG VARIOUS PROTOCOLS}

The present invention relates to a packet transmission flexible adapter system configured to perform data processing for transmission and reception packets through XML and applicable to various communication environments.

Recently, with the rapid development of technology in the field of information and communication, the use of the Internet is becoming common, and according to the trend of the generalization of the Internet, numerous Internet websites have been widely opened, and accordingly, each Internet website is managed. The importance of web operating systems is also increasing.

This trend is not only in the age of popularization of the Internet, but also various services and business fields through the web based on the advancement of the IT infrastructure are realized in various forms in all fields from the private, corporate and government level.

In the past, the stable performance of software was the top priority in the Web 1.0 era, but the importance of the user interface has been the main concern since the arrival of the Web 2.0 era, which promotes participation and sharing, emphasizes user convenience. .

Accordingly, there is a need for an integrated control technology for packets transmitted through various protocols such as network data, that is, HTTP, TCP, UDP, and FILE, which are increasingly diversified.

In order to meet these demands, an adapter system capable of processing packet data on a network corresponding to various transmission protocols has been developed.

However, the conventional adapter system has not only increased complexity due to frequent control modifications and appearances of a number of dedicated controls that occur due to an increasingly diverse communication environment and format, but also a lot of resources for maintenance activities and new sites due to management difficulties. There was an issue that brings waste.

In order to solve the above problems, the present invention is configured to define the processing method of the transmission and reception packet through XML to support various communication environments, thereby transmitting data between various protocols applicable to various communication environments without changing the version or controlling the control. To provide a flexible adapter system for.

According to the present invention, in the adapter system for controlling a packet on a network, it is possible to define a data collection and processing method for a packet transmitted and received through various protocols and a packet generation method to upload to a server using XML. A packet defining unit, a data receiving unit receiving a packet according to an execution plan defined by the packet defining unit, a transmitting unit transmitting a data packet to a server side, and the packet defining unit defines a packet processing in a specialized binary form and a packet in an XML form. It is divided into XML mappers that define the processing, and this packet processing method is used to create an execution plan to send and receive packets according to the contents of the defined XML document, and to use the various protocols to receive the packets while actually executing the packet transmission and execution plan. For adapters, including flexible adapters It is achieved by a flexible adapter system for data transfer between various protocols applicable to various communication environments without requiring a separate version change or modification to the system.

Here, the packet definition unit includes a variable definition unit configured with an element for declaring variables, a receive unit configured with an element describing a part of analyzing a received packet, and a transmission of the processed data. An element described for the purpose may include a configured sender.

Preferably, the packet definer may include a variable definer, a receiver, and an element configured in the transmitter in a tree structure.

In addition, the packet may include a head including segments corresponding to an element configured in the variable definition unit, and a body including one or more data sets.

The flexible adapter may include a packet management unit for receiving data from an external XML or various packets and requesting data processing, a packet processing unit for processing data received from the packet management unit according to a rule defined by the packet definition unit, and a packet definition. A packet processing definition unit for transmitting the rule defined by the unit to the packet management unit or the packet processing unit, and the packet variable definition unit for registering the variable defined in the packet definition unit and transmitting the registered variable rule to the packet processing unit. have.

In addition, the flexible adapter includes a command storage unit for storing instructions frequently processed by the packet processing unit, and a temporary packet storage for temporarily storing a previous packet that is being executed when a packet that is easy to process while a data processing process is received. In addition, it may be arranged to improve performance of performing data processing.

Therefore, the present invention is configured to define the processing method of the transmission and reception packet through XML to support a variety of communication environments, there is an advantage that can be applied to various communication environments without changing the version or control.

Hereinafter, a flexible adapter system for data transmission between various protocols according to the present invention will be described in detail with reference to the accompanying drawings.

1 is an overall configuration diagram of a flexible adapter system for data transmission between various protocols according to the present invention.

Referring to FIG. 1, the flexible adapter system according to the present invention includes a packet defining unit 100 which defines a processing method for data input and output in a packet 20 received in various protocols 10 and the packet definition. An XML mapper 200 defining a method of specifying a data acquisition path in the XPATH form and processing the data set having a specific structure in order to obtain specific data from the packet data in XML format received inside the subpart, and the packet definition It is configured to include a flexible adapter 300 for processing a variety of packets 20 to suit the protocol 10 to be transmitted according to the execution plan defined in the section.

For reference, to explain the Xpath and the flexible adapter for better understanding of the present invention, Xpath is a string designating a specific structure in a structure defining a processing method for the data, for example, '/ gform / components / It is expressed in the form of 'model / @ text'.

The flexible adapter is not only configured to receive various data (Gauce Packet, User Packet, Soap, RSS, CSV, etc.) through various protocols (HTTP, TCP, UDP, FILE), but also to configure a data set. It is a component that reconstructs data after transmission as needed.

The flexible adapter 300 reconstructs the data by the packet defining unit 100 or the XML mapper 200.

Here, the XML mapper 200 is composed of the same elements as the packet definition unit 100, and the difference from the packet definition unit 100 is that the difference between the 'xmlpath', which is an attribute for the Xpath, is described. have.

The 'xmlpath' is described in a 'treat' item among elements of the packet defining unit 100 to be described later.

The packet defining unit 100 defines a processing method for data input and output from the packet 20 through the flexible adapter 300, and elements formed through the tree structure are formed.

FIG. 2 is a diagram illustrating a tree structure of a packet defining unit. Referring to FIG. 2, the packet defining unit 100 includes a definer 110 that declares variables set in the packet defining unit 100. And a receiving unit 120 for describing a portion for analyzing and processing the received packet, and a sender 130 for transmitting the processed data.

Here, the packet defining unit 100 has a 'packet' 101 as a root element, and the variable type sets the type of the packet 20. As a value, binary and extensibility are generated. Language (XML), text (text) can be set.

The definer declares variables set in the 'packet' 101 which is the root element of the packet definer 100, and includes a 'define' 110 as a distinguishing element.

The lower element of 'define' is 'value' 115, and the 'value' 115 is to set the name and variable type of various variables, according to the variable attribute of the upper element 'packet' 101 The operating characteristics are different.

If the parent element 'packet' 101 is 'variable', it is used as a variable in the block.However, if 'httphead' is the parent element, the communication method should be used as the HTTP protocol. The content is included and sent.

An attribute including the information of the 'value' 115 is 'name' 'type' 'value'.

The 'name' should not be duplicated by specifying the name of the variable. When the 'name' is described in the 'httphead', it is a name for the HTTP head 150.

The 'type' describes a variable type, and a variable of the type shown in [Table 1] is used, and it is not necessary to describe it in 'httphead', in this case, it is set to a string type unconditionally.

Variable type Justice string   Variable with Molecular String int8   8-bit (1 byte) integer int16   16 bit (2 byte) integer int32   32-bit (4 byte) type integer int64   64-bit (8 byte) integer uint8   8-bit (1-byte) positive integer uint16   16-bit (2-byte) positive integer uint32   32-bit (4 byte) positive integer uint64   64-bit (8 byte) positive integer double   A variable with a decimal point bool   Boolean variable of true (1) / false (0) unknown Data type variable of type void *
Data variables such as images

The 'value' 115 is a value to be assigned to a variable, which is the value of the http head when describing in 'httphead', and does not need to be described in 'variable'.

'httphead' is a valid element only when HTTP protocol is used. It is a distinguishing element for describing the contents included in the head in the Http Request.

The receiving unit 120 includes 'receive' as a distinguishing element for describing the received packet 20 as a part for analyzing and processing the received packet 20, and 'default-start' as a lower attribute.

The 'default-start' interprets the packet 20 from the block set here if there is no configuration at reception.

'block' 105 is a root element representing a block of the packet defining unit 100. The type of the packet 20 is set to binary, xml, or text.

'data' 122 cuts and receives the received packet data according to a set situation, and has sub-properties 'id', 'type', 'size', 'convtype', 'netnumber', and 'treat'.

'id' represents the type of identification of the data and must be described as an ID string uniquely within the 'block'.

'type' is the data type stored, see Table 1 above.

'size' is valid only when the type is set to string or unknown, and the string or binary data is read as much as the set size.

'convtype' converts the read data type. Refer to [Table 1] as the data type.

When 'type' is an integer type, 'netnumber' is corrected because the value is inverted and transmitted.

'treat' does not describe an item and treats it as normal by default. When set to 'static', it is recommended to receive data from the received packet 20, such as '<data> value to be input </ data>'. Rather, it accepts the text of <data> as the value of that data.

In addition, when the 'treat' is set to 'eod' and the text of the data is set to ',' as follows, the data of the packet 20 is cut out using ',' as a separator.

For example, when 'treat', a sub attribute of 'data' is set to 'eod', '<data id = "samp01" type = "string" threat = "eod">, </ data>' and Can be represented as:

In addition, when the 'treat' is set to 'eof', it indicates until the reception of all packets 20 is completed.

If the type of the packet 20 is set to xml, 'treat' is set to 'xmlpath' to describe the xml path of the data.

In this case, the packet defining unit 100 acts as an xml mapper.

'repeat' simply accepts data repeatedly if the received data comes in the same format repeatedly. The sub-attributes are 'id', 'condition' and 'array'.

'id' is the only ID string in the block and can usually be omitted.

'condition' can enter a specific conditional statement and accepts data while continuing to iterate through all the elements in the 'repeat' statement as long as the result is true.

'array' is an option for storing the data in an array form when the data is received by mistake, and may include a value of 'true' or 'false'.

'if' 124 executes the elements in the 'if' statement only if the corresponding conditional statement in the statement is true, and has a subcondition as 'condition'.

'condition' is the place where the conditional statement is entered. It executes the child element only when the result is true.

'elif' 125a is supposed to execute the conditional statement of 'elif' only if the condition described in the previous syntax is false, and must be described before the 'if' statement or 'elif'.

A lower attribute of 'elif' 125a is 'condition', and 'condition' is a place where a conditional statement is input, and performs a lower element only when the result is true.

'else' 125b executes the elements in the syntax of 'else' when both conditional statements of 'if' and 'elif' are false.

'next' 123 performs a function of calling another block at any place in the block, and has 'goto' as a sub attribute, and 'goto' indicates an ID string of a block to be called.

'return' 128 returns to the block that called itself from any place in the block, and may transmit an error code, a message, and the like.

Subattributes are 'code' and 'mag'.

'code' represents the error code to be passed in the 'return' syntax, and 'msg' represents the error message to be passed in the 'return'.

'operator' 127 calls the interface function of the flexible adapter 300, and if there is a result value, the value corresponding to the ID is stored.

The sub-properties are 'name' and 'id', where 'name' represents the name of the function to call and 'id' represents the unique ID string in the block.

'dataset' 126 calls the interface function described in 'dataset', and if there is a result value, the value corresponding to the ID is stored.

The sub-properties are 'name' and 'id', where 'name' represents the name of the function to call and 'id' represents the unique ID string in the block.

'param' describes a parameter of a corresponding function when calling a function from the 'operator' and 'dataset', and the parameter order of the function is the same as the description order of the elements of the 'param'.

The sub-attributes include 'type' and 'value', where 'type' indicates the data type of the parameter, and refers to [Table 1] above as the data type to be stored.

 The sender 130 is a part described for the transmission of the processed data. There is 'send' as a division element and 'default-start' as a lower attribute.

'default-start' represents the ID string of the start block.

'write' 131 is available only in a block in which the upper element is 'send' and transmits the loaded data.

3 is a block diagram of a packet according to an embodiment of a flexible adapter system for data transmission between various protocols according to the present invention.

Referring to FIG. 3, the packet 20 includes a head 150 including segments corresponding to elements configured in the packet defining unit 100, and a body 160 including one or more data sets.

3 (a) is a diagram showing a configuration of a packet implemented to repeatedly access data of a specific section according to an embodiment of the present invention, in which the head 150 includes an error detection segment 151, The name size recognition segment 152, the packet name segment 153, and the string segment 154 are included, and the body 160 includes the data repeating segment 161 and the data segment 162.

The program described below is an example of an XML program of a packet definition unit for a packet implemented to repeatedly access data of a specific section shown in FIG. 3 (a) by a given condition.

<packet type = "binary">
<define />
<receive>

<block id = "head">
<data id = "ident" size = "2" type = "string"/>
<if condition = ": ident! = 'HZ'">
<return code = "-1" msg = "ident error"/>
</ if>
<data id = "namesz" type = "int4" netnumber = "true"/>
<data id = "name" type = "string" size = ": namesz"/>
<data id = "flag" type = "string" size = "1"/>
<next goto = "body"/>
<return code = "$ result_code" msg = "$ result_msg"/>
</ block>

<block id = "body">
<repeat condition = "$ EOF" id = "loop01">
<data id = "size" type = "string" size = "2" convert = "int4"/>
<data id = "data" type = "string" size = ": size"/>
</ repeat>
<return code = "0" msg = "ok"/>
</ block>

</ receive>
<send />
</ packet>

The error detection segment 151 is a segment that detects an error of a packet and receives the HZ described in the above example in the form of a string with a size of 2, and then checks whether the corresponding value is normal by the if statement below. Returns.

The name size recognition segment 152 is a segment that determines the size of the packet name to be read. The size of the packet name is read and the network byte type is inverted. If 'netnumber' described in the above example is used in 'send' Convert to ground network bytes.

The packet name segment 153 reads data as much as the size received from the name size recognition segment 152 in the form of a packet name string.

The string segment 154 reads the value of the stored segment in the size of string 1.

In the data repeating segment 161, a repeating phrase is set to repeatedly read each corresponding data portion from the data sets Data1, Data2, Data3, and Data4 included in the body 160. Convert the data to read the data.

 The data segment 162 is a segment in which data is stored, and reads the next corresponding data by the size value obtained from the data repeating segment 161.

3 (b) is a diagram showing a configuration of a packet 20 implemented to be interoperable with a data set according to another embodiment of the present invention, wherein the head 150 is a variable type segment 155 and a name size recognition segment. 152, a packet name segment 153, and the body 160 includes a data repeating segment 161 and a data segment 162.

The program described below is an example of an XML program of a packet definition unit for a packet implemented to be interoperable with a data set in FIG.

<packet type = "binary">
<define>
<value name = "typename" type = "string"/>
</ define>
<receive>
<block id = "head">
<data id = "type" type = "int1"/>
<if condition = ": type == 1" then = "$ typename = 'string'"/>
<else then = "typename = 'int4'"/>
<data id = "size" type = "int4" netnumber = "true"/>
<data id = "name" type = "string" size = ": size"/>
<dataset name = "addhead" parameter = ": name, $ typename, 0,0"/>
<next goto = "body"/>
<return code = "$ result_code" msg = "$ result_msg"/>
</ block>

<block id = "body">
<repeat condition = "$ EOF" id = "loop01">
<data id = "size" type = "string" size = "2" convert = "int4"/>
<data id = "data" type = "string" size = ": size"/>
<dataset id = "rowidx" name = "addrow"/>
<dataset name = "putrowdata" parameter = ": rowidx, 0,: data"/>
</ repeat>
<return code = "0" msg = "ok"/>
</ block>

</ receive>
<send />
</ packet>

The variable type segment 155 converts the read variable type into a string and puts it into a variable defined in a define unit.

The packet name segment 153 is a name of an interface used in the data sets Data1, Data2, Data3, and Data4 and fills data necessary for parameters to form the head 150 of the data set.

In the data repeating segment 161, a repeating phrase is set to repeatedly read each corresponding data portion from the data sets Data1, Data2, Data3, and Data4 included in the body 160. Convert the data to read the data.

 The data segment 162 is a segment in which data is stored, and reads the next corresponding data by the size value obtained from the repeating segment.

Here, the data segment 162 may receive a result value after executing the corresponding interface when an ID is specified in the data set, and return an index of an added column when the name of the data set is 'addrow' and then describe the 'dataset' described below. 'Parameter' of 'puts data using the index

4 is a block diagram illustrating a conceptual structure of a flexible adapter of a flexible adapter system for data transmission between various protocols according to the present invention, and FIG. 5 is a diagram of a flexible adapter system for data transmission between various protocols according to the present invention. It is a structural diagram showing the packet processing of the flexible adapter.

Referring to FIG. 4, the flexible adapter 300 receives an external XML or various packets 20 from a plug-in that exchanges data through a protocol, and processes a received packet 20 to reconstruct data. The processor 310 and the packet manager 320 are included.

In addition, the flexible adapter 300 includes a packet processing definition unit 360 and a packet 20 variable definition unit that define a rule for processing the packet 20, and temporarily stores the instruction or the packet 20. Storage spaces such as the command storage unit 330 and the temporary packet storage unit 340 are also configured.

The packet manager 320 receives XML data or a packet 20 from various plug-ins composed of various protocols, and transmits the XML data to the packet processor 310 to request data processing.

Here, the data processing proceeds according to the rules defined by the packet definition unit 100 described above, and these rules are transmitted by the packet processing definition unit 360 to the packet management unit 320 or the packet processing unit 310. do.

In addition, the processing of the variable in the data processing is performed through the rule received from the packet 20 variable definition unit, and the packet 20 variable definition unit registers the variable rules defined in the packet processing unit 310. It is.

The flexible adapter 300 is provided with a temporary storage space for fast and smooth data processing, one of the command storage unit 330 stores instructions that are frequently processed to improve the performance of data processing.

In addition, the temporary packet storage unit 340 temporarily stores the previous packet being executed to improve processing performance when a packet that is easily processed comes in during the data processing process.

Referring to FIG. 5, the flexible adapter 300 configured as described above processes the data through the following data structure in the packet processor 310.

First, the packet 20 is transmitted to the packet definition data module 420 from various protocols.

Next, the data is prepared to be processed by determining a conditional statement according to the syntax defined in the packet definition data module 420. The conditional statement determination is performed through the conditional statement determination module 425.

Here, the factor to be used for the conditional statement from the parameters recorded in the data is filled in the queue and transmitted to the conditional statement determination module 425 as the conditional statement defined in the packet definition data module 420, and then 'repeat', 'if' among the conditional statements. In the case of 'else' and 'elif' syntaxes, the conditional statement is determined and the result is transmitted to the packet definition data module 420 in the form of true / false.

Next, the data is organized according to the conditional statement defined in the packet definition data module 420, and then the conditional statements such as 'next', 'elif', 'else', 'dataset', and 'operator' described in the data are Only the deleted data data structure is arranged and transmitted to the packet data data module 430.

Next, the data organized into a data data structure is rearranged by the dynamic array module in the packet data data module 430.

The terms used in the above description and claims are not to be construed in a dictionary sense, and the inventors can properly define the concept of terms in order to explain their invention in the best way. Therefore, it should be interpreted as meaning and concept corresponding to the technical idea of the present invention.

Accordingly, the shapes and configurations shown in the drawings as well as the embodiments described herein do not represent all of the technical ideas of the present invention, and various equivalents may be substituted for them at the time of filing of the present invention. It should be understood that variations may exist.

1 is an overall configuration diagram of a flexible adapter system for data transmission between various protocols according to the present invention;

2 is a diagram illustrating a tree structure of a packet definition unit of a flexible adapter system for data transmission between various protocols according to the present invention;

3 is a block diagram of a packet according to an embodiment of a flexible adapter system for data transmission between various protocols according to the present invention;

4 is a block diagram illustrating a conceptual structure of a flexible adapter of a flexible adapter system for data transmission between various protocols according to the present invention;

5 is a structural diagram illustrating a packet processing procedure of a flexible adapter of a flexible adapter system for data transmission between various protocols according to the present invention.

* Description of the symbols for the main parts of the drawings *

10: protocol 20: packet

100: packet defining unit 200: XML mapper

300: flexible adapter

Claims (6)

An adapter system for controlling packets on a network, A packet defining unit defining a processing method for data input / output in packets received from various protocols through XML; and,  An XML mapper defining a method of specifying a data acquisition path in the XPATH form and processing into a data set having a specific structure in order to obtain only a specific data portion of the packet data in XML form among the above data; Flexible adapter for processing a variety of packets according to the packet definition according to the packet definition unit (Flexible Adapter), including data transfer between various protocols applicable to various communication environments without a separate version change or modification to the adapter system Flexible adapter system. The method of claim 1, The packet defining unit may include a variable defining unit configured to declare elements to be set in the packet defining unit, and a receiving unit configured to describe a portion for analyzing and processing a received packet. And a sender configured to describe an element for transmitting the processed data. 12. The flexible adapter system for transmitting data between various protocols. The method of claim 2, The packet defining unit is a flexible adapter system for data transmission between the various protocols, characterized in that the variable defining unit, the receiving unit, and the elements configured in the transmission unit is formed in a tree structure. The method according to any one of claims 1 to 3, The packet includes a head including segments corresponding to an element configured in the packet definition unit, and a body including one or more data sets. Adapter system. The method of claim 1, The flexible adapter may include: a packet manager configured to receive external XML or various packets and request data processing; and a packet processor configured to process data received from the packet manager according to a rule defined by the packet definer. A packet processing definition unit for transmitting the rule defined by the unit to the packet management unit or the packet processing unit; and the packet variable definition unit for registering the variable defined in the packet definition unit and transmitting the registered variable rule to the packet processing unit. Flexible adapter system for data transmission between the various protocols comprising a. The method of claim 5, The flexible adapter may include an instruction storage unit that stores instructions frequently processed by the packet processor; and a temporary packet storage unit that temporarily stores a previous packet that is being executed when a packet that is easily processed is received while performing a data processing process. Flexible adapter system for data transmission between the various protocols, characterized in that is further provided to improve the performance of data processing.

Images