KR19990057306A - Validation method of segment repetition in electronic document exchange system - Google Patents

Abstract

1. Technical field to which the invention described in the claims belongs

A validation method for the use of segment repetition in an electronic document exchange system.

2. Technical Challenges to be Solved by the Invention

We want to be able to check whether the transmitted and received electronic document conforms to the standard electronic document structure agreed by the sender.

3. The point of the solution of the invention

The electronic document structure information is mapped to the electronic document data structure and the correlation information of the segments and loops is mapped to the loop data structure, and if the number of times of use of the segments exceeds the number of times of segment repetition, If the current looping count of the loop exceeds the upper limit of loop repetition usage, it is determined whether the segment is a segment included in the loop. If the segment is an embedded segment, If it is not exceeded, it is checked whether the total cumulative use count value of the segment exceeds the repeated use limit value, and if it is exceeded, the error according to the use of the segment upper limit excess is handled.

4. Important Uses of the Invention

Used in electronic document exchange system.

Description

Validation method of segment repetition in electronic document exchange system

The present invention relates to a method for verifying the validity of repeated use of segments which are components of electronic standard types of electronic documents in an electronic data interchange (EDI).

Here, the validity verification refers to a process in which a document conversion unit (Translator) generates a standard electronic document (Interchange) in an electronic document exchange system and a transmission conversion process in which a standard electronic document is input and application data If the segments that are considered to correspond to one sentence in the electronic document in the generated incoming conversion process are not used in excess of the maximum allowed number of times of repeated use specified on the electronic document, or if the segment is used in the loop (s) Quot; maximum allowed number of loops times segment maximum allowed number of loops ", which includes the segment.

Therefore, it is an object of the present invention to make it possible to check whether an electronic document to be transmitted and received conforms to a standard electronic document structure agreed upon by the sender and the receiver, when the electronic document is transmitted and received using the electronic document exchange system, Or to enable application data generated by an application program to be correctly converted into a standard electronic document, and to provide a validation method for repeated use of an electronic document segment.

1 is a schematic block diagram of an electronic document exchange system to which the present invention is applied;

2 is a loop structure diagram of an electronic document.

3A and 3B are structural diagrams of segment tables of electronic documents;

FIG. 4 is a diagram showing a data structure of a segment table of an electronic document; FIG.

5 shows a loop data structure for loop information management;

6 shows a frequency data structure for segment repeat use information management;

7 illustrates an electronic document data structure including electronic document structure information;

FIG. 8 is a flowchart of setting correlation information of segments and loops of an electronic document according to the present invention to an electronic document, a loop, and a frequency data structure; FIG.

Figures 9a and 9b are flow diagrams for validating the use of segment repetition according to the present invention.

DESCRIPTION OF THE REFERENCE NUMERALS

101: Subscriber unit 102: Document conversion unit

103: EDI messaging device 104, 107: Subscriber processing part

105: Message relay processing unit 106: Message storage unit

According to another aspect of the present invention, there is provided a method for verifying validity of repeated use of segments in an electronic document exchange system, the method comprising the steps of: comparing electronic document structure information with an electronic document data structure; correlating segments and loops included in each electronic document A first step of mapping information to a loop data structure, respectively, and initializing a frequency data structure indicating a frequency of use of segments in the electronic document; A second step of checking whether the number of times the unit used in the data structure of the segment to be used exceeds the number of times of segment repetition of the electronic document data structure; A third step of performing an error process according to the use of the segment repetition exceeding if it is exceeded in the second step; A fourth step of checking if the segment is included in the loop if it is not exceeded in the second step; A fifth step of initializing the number of loop repetition times if the segment is not included in the loop in the fourth step; A sixth step of checking whether the current looping count of the loop exceeds a loop repeat use upper limit value in the case of a segment included in the loop in the fourth step; A seventh step of processing a use error according to the use of loop repetition if it is exceeded in the sixth step; An eighth step of checking whether the total cumulative use count value of the segments exceeds the repeat use limit value in the sixth step; And a ninth step of processing an error due to use of the upper limit of the segment if it is exceeded in the eighth step, and ending the normal use if the error has not been exceeded.

First, an electronic document exchange system (EDI) will be described in order to facilitate understanding of the present invention.

Electronic document exchange system (EDI) refers to a new document delivery system that converts commercial transaction documents and administrative documents into structured electronic documents that can be processed by computers in accordance with the standards agreed by the trading partners and exchange them through computer networks.

In this electronic document exchange system, the UN / EDIFACT document standard and the ITU-T X.435 communication standard agreed internationally on the contents and structure (document standard) and communication method (communication standard) of electronic documents.

In the electronic document exchange system, the electronic document conversion unit converts the fact data file generated by the application program into an interchange file composed of the international (UN / EDIFACT) standard electronic document structure through the mapping and conversion process, and transmits the interchange file Upon receipt of the file, it performs the function of converting it into a private data file through the reverse operation.

Generally, the electronic document conversion unit performs document conversion in compliance with all the syntax rules defined by the international (UN / EDIFACT) standard, and consists of a transmission conversion unit, a reception conversion unit, a mapping unit, and a standard data management unit.

Like current infrastructure such as roads, ports and railways, ICT has a huge impact on all industries and is an important measure of corporate and national competitiveness. Among them, the electronic document exchange system, which provides a new business method of paperless transaction, is emerging as an essential means of securing the competitiveness of companies worldwide. Conventional fax and e-mail expresses unofficially informal informal data between sender and receiver in a human-readable form and electronically transmits it. However, since it is not a standardized form, in order for the recipient to use the received data, You have to rework or re-enter the computer. This is because it assumes a man-to-man communication type. In other words, it is imperative that people fill out the form.

However, in an electronic document exchange system in which a computer-to-computer communication type is assumed, data generated by a computer application program, unlike the fax and e-mail, (Encoding) into a standard electronic document format and transmits it to the receiving system. The standard electronic document is again interpreted by the document conversion unit of the receiving computer in accordance with the international standard electronic document syntax rules and is processed in a form that can be processed by the application program, To be processed by a computer without human intervention.

In this way, the electronic document exchange system connecting the information systems of each company generates documents according to the document standards and communication standards of the electronic document exchange system without being restricted by computer hardware, software, geographical location, time zone, Anyone with an interpretable software can send paperless electronic documents anywhere, anytime, anywhere in the world. In other words, the scope of the electronic document exchange system is very wide, enabling not only vertical information flow, but also cross-industry, horizontal information flow among industries, and international information flow among countries. Therefore, conventional data processing methods such as telephone, mail, fax, etc., are repeatedly inputting data, so that the processing time is delayed, the accuracy of data due to re-input is decreased, the time and manpower are consumed, It is inefficient and complicated to process. However, by using electronic document exchange system, cost reduction such as inventory cost, transportation cost and data error reduction, improvement of work efficiency, improvement of customer service, improvement of relations with customers, .

In order to realize such an electronic document exchange system, there is a need for a standard for electronic documents exchanged between senders and receivers. Since the format of the documents used by each company is different, in order to maintain the compatibility of the documents, all standards concerning the contents and structure of the electronic documents to be exchanged are required.

The standards that apply to electronic document exchange systems are largely document standards and communication standards. The document standard was enacted and published by the United Nations Economic Commission for Europe (UN / ECE), and the communication standard has been promulgated around ITU (formerly CCITT) and ISO. The United Nations has now published UN / EDIFACT as an international document standard (1987), and ITU-T has published the X.435 Recommendation as an international telecommunication standard.

UN / EDIFACT (UN / EDIF for Adiministration Commercial Transportation) is the United Nations convention for the electronic exchange of administrative, commercial and transport data. It consists of internationally agreed standards, directories, and message design guidelines for the electronic exchange of structured data. These rules are recommended within the framework of the United Nations and are approved and published by the United Nations Economic Commission for Europe (UN / ECE) as United Nations Trade Data Interchange Directory (UNTDID) Improvement.

The UN Economic Commission for Europe (UN / ECE) is one of the five regional committees established by the UN Economic and Social Commission. Despite its name, the European Economic Area includes Europe as well as North America.

The content defined by UN / EDIFACT is defined in terms of Syntax Rules (ISO 9735), Message Design Guidelines, Syntax Implementation Guidelines, Data Element Directory (EDED) (EDC), Segment Directory (EDSD), Code List, Standard Message Directory (EDMD), Uniform Rules of Transaction Data Exchange Procedures by Remote Transmission (UNCID ), And related commentary materials.

The character sets that can be used in UN / EDIFACT are classified into two sets of lengths: There are A and B character sets used in UN / EDIFACT. A message using character set A is called A level, and a message using character set B is called B level message. However, when using character set B, there must be an agreement between the two.

Character set A

Alphabetic characters (upper case) A to Z

Numbers 0 through 9

Korean syllable

Other characters., - () / =

Reserved character '+ :?

Unacceptable characters for telex transmission! "% &*; <>

Character set B

Alphabetic characters (upper case) A to Z

Alphabetic characters (lowercase letters) a to z

Numbers 0 through 9

Korean syllable

Other characters., - () / =

'+:?

! "% &*; <>

Reserved characters IS4 IS3 IS1 (non-printing characters)

UN / EDIFACT standard To be able to display electronic documents in a flexible format that does not transmit unnecessary parts, it must be able to indicate the beginning and end of a data element or segment. In UN / EDIFACT, separators are used for this purpose, and different characters are used depending on the character set. The name of the delimiter and the characters used are as follows.

- Segment terminator (': upper comma): Indicates the end of the segment. The tag after this indicates the segment name immediately following it.

- Segment tag and data element separator (+): Used when separating the segment tag and the data above it and separating the independent data elements in the segment.

- Configuration data element separator (:): Used to separate constituent data elements from each other in a composite data element.

- Release code (?): When character set A is used, it is used in front of the character to be used as general data when used as a delimiter.

In UN / EDIFACT, a Data Element acts like a word in a language, and can be roughly divided into a Simple Data Element and a Composite Data Element.

A simple data element is a data element that does not need a supplementary or qualifier because its data element is sufficiently meaningful.

For example, "3207" Country Code an3 id "means the identifier for the national face or other geographic name specified in ISO 3066.

However, since its meaning is not completely defined by its own data element, an element requiring a quilifier for further explanation is called a quilified data element.

For example, "6063 quantity n..15 n" means a numerical value of quantity.

In the above example, it is not possible to know what the numerical value of the quantity is. For example, if the numerical value of the quantity is '10', the meaning of the quantity will be confirmed if it is described as '114' (number of passengers) or '115' (number of the crews) Thus, a data element that specifies the attributes of a qualifying data element is limited.

A coincidence data element is a data element consisting of a single set of data elements that are conceptually related. At this time, it is referred to as a data element constituting a single data element in a composite data element. In UN / EDIFACT, a composite data element must begin with an uppercase 'S' or 'C'.

The following example is a composite data element consisting of three configuration data elements. When using this composite data element, it is mandatory to use the declared '6060 quantity' but not the selectively declared '6063 quantity qualifier' or '6411 measurement unit qualifier'.

Example) C186 Quantity Details

Content: 6063 Quantity Qualifier C an..3id

6060 quantity Mn.15n

6411 Measuring unit qualifier C an..3id

The composite data element from S001 to S010, starting with S, among the complex data elements is called a service data element. These are data elements that represent the content related to the transmission.

The data representation of the data elements described in ISO 7372 / UNTDED of UN / EDIFACT is as follows.

a alphabetic character

n number

an Alpha / Numerical Mixed

a33 alphabetic characters (fixed length)

n33 numbers (fixed length)

mixed an33 alphanumeric characters (fixed length)

a..33 alphabetic characters (variable length)

n.3 Up to three digits (variable length)

an..3 Up to 3 alphanumeric characters (variable length)

M Required element attributes

C optional element property

In UN / EDIFACT, a segment is a meaningful set of data elements (simple, compound data elements) that are related to one another. Each segment must be separated by a unique three-character tag, and its structure must be defined in advance.

One segment consists of a segment type identifier, a tag, a data element separator, a simple or composite data element, and a segment terminator.

For example, in "CLU + BEF: IN", "CUX" is the "call" segment and tag, "+" is the delimiter, "BEF" is the value of the data element "currency code" The data element separator in the data element. &Quot; IN " represents a currency code qualifier indicating that the currency is applied to an amount on an invoice message, and " " represents a segment terminator.

Segments can be roughly divided into data segments and service segments.

A data segment is a segment that contains the data that the user actually wants to transmit and has a segment tag that does not necessarily begin with the letter "UN".

Below is an example.

CLX call segment

Description: Describe the currency used in the document to describe the exchange rate related content

C180 Reference currency M

6345 Currency code M a3 id

6343 Currency Qualifier C an..3 id

C182 Target currency C

6345 Currency code M a3 id

6343 Currency Qualifier C an..3 id

5042 Rate C n..12 n

6341 Foreign exchange market code C an3 id

C034 Parallax C

2005 Date / Time Qualifier C an..3 id

2001 Date code C n6 n

2002 Time C n4 n

2461 Time zone code C an3 an

A service segment is a segment with a segment tag beginning with "UN", which is a mandatory segment that must be used for UN / EDIFACT message construction (UNA, UNS segments may not be used in some cases). A service segment that is used for control of a data segment is used to distinguish the start and end of an interface and a message, or to distinguish the start and end of an optional function group.

The service segments used in UN / EDIFACT are:

The UNB interchange header is an interchange start segment, the UNZ interchange trailer is an interchange end segment, the UNG functional group header is a start segment of a functional group, the UNE functional group trailer is an end segment of a functional group, the UNH message header is a start segment of a message, The trailer indicates the ending segment of the message, the UNS sector control indicates the heading, detail, summary segment segment of the message, and the UNA service string notification indicates the segment separator used in the interchange.

Below is an example of this.

UNB interchange header

Function: Indicates the start of the interchange and includes the control data required for transmission or necessary for document conversion.

S001 Syntax identifier M

0001 Syntactic identifier M a4

0002 Syntax revision number M n1

S002 Interchange sender M

0004 Sender identification M an..35

Identification code qualifier C an..4

0008 Return address C an..14

S003 Interchange recipient M

...

S004 Creation date and time M

...

S005 Recipient reference, password C

...

0026 Application Reference C an..14

The processing priority codes C a1

0031 Receipt notification request C n1

0032] The communication agreement identifier C an..35

The test indicator C n1

The UN / EDIFACT standard electronic document can be divided into three major parts as follows. Each data segment is located in a specific place in the series of segments that make up the message, and can appear in the next three parts of the message.

Heading Section: Segments appearing in this section are related to the entire message.

Detail Section: Segments appearing in this section relate only to the detailed information that the user wishes to convey to the other party and take precedence over any similar guidance defined in the heading section.

Summary Section: In the Summary section, only aggregate or control information segments such as the total amount, number of lines, etc. on the message (eg, invoice, order form, etc.)

In UN / EDIFACT, a message loop can appear where the same segment type overlaps two or more segments in the message, such as headline and detail segments, and some segments can be repeated a certain number of times at a particular position in the message. The status, that is, whether it is mandatory or optional, and the maximum number of iterations of the segment type is displayed in the message structure.

Certain groups of functionally related segments within a message may be repeated and may be omitted when not required. These segment groups are referred to as " loops. &Quot; The maximum number of iterations of a particular location is displayed in the message structure.

Software for exchanging electronic documents requires a message store and a relay system installed in a transmission host having a function of transmitting messages to be transmitted between a subscriber system installed at a subscriber (EDI subscriber) and a subscriber, and storing the messages temporarily. The electronic document exchange system can be used on any hardware platform such as a personal computer (PC), a workstation, a minicomputer, and a mainframe in addition to a communication modem. With the emergence of low cost, high performance personal computers and software for many electronic document exchange systems, Based electronic document exchange system can be realized at low cost, contributing to the spread of the electronic document exchange system.

An example of an electronic document exchange system according to the X.435 and F.435 standards and international document standards based on the X.400 Recommendation of the International Telegraph and Telephone Advisory Committee (CCITT) is as follows.

First, the electronic document exchange system can have various hardware and software configurations according to the applied application or the environment of the user who uses it. Basically, the software consists of a subscriber system, a subscriber processor, a repeater, and a message storage, Depending on the software environment, each subsystem may be installed in various combinations, and the hardware platforms in which the subsystems are installed may vary.

Fig. 1 shows a schematic block diagram of an electronic document exchange system to which the present invention is applied.

The subscriber device 101 is connected to the messaging device 103 having a plurality of message relays and a subscriber processor 104, a message store 106, and a message relay via a public switched telephone network (PSTN) to send messages to other subscribers, And retrieves and processes the message sent by the subscriber. In other words, the subscriber device 101 provides all functions for the user to generate and transmit an electronic document message, and the subscriber device 101 is provided with a document editor, a document conversion section, a communication for transmitting and receiving an electronic document message between the relay host and the subscriber device A message storage unit inquiry unit according to the message storage unit access protocol P7, and a document management unit for objectifying and managing the transmission / reception document and the management information.

The document conversion unit 102 in the subscriber unit 101 is a functional unit that maintains mutual compatibility of messages by performing mutual conversion between a private document and a standard electronic document on all messages transmitted and received, Interchange file (IC) composed of international standard electronic document structure is generated through mapping and conversion of data file (DF: Data File), or vice versa, and a private data file do. In general, the document conversion unit 102 performs conversion according to the general syntax rule (IS09735) of the international standard (UN / EDIFACT), and is roughly divided into a transmission converter, a reception converter, a mapper, and a standard data manager.

The subscriber processing unit 104 of the messaging apparatus 103 as a relay host performs a function of encoding or decoding a message transmitted between the subscriber apparatus 101 and the message storage unit 106. That is, the message created and transmitted by the subscriber unit 101 is encoded according to the encoding rule (ASN.1) and transmitted to the message storage unit 106, or the message transmitted from the message storage unit 106 is decoded, (101).

The message storage unit 106 is a functional unit serving as an intermediary between the subscriber processing unit 104 and the relay host. The message storage unit 106 receives a message transmitted from the subscriber and receives the message from the message relay processing unit 105. In addition, the user can search the messages stored in the message storage unit 106 by using the subscriber device 101 to retrieve the number of messages satisfying a specific condition, to take the entirety of a specific message, , And so on. The P7 protocol (message store search rule) is applied when a message is transmitted between the subscriber processing unit 104 and the message storage unit 106. When the message is transmitted between the message storage unit 106 and the message relay processing unit 105, The protocol (submission and delivery protocol) applies.

The message relay processing unit 105 has a function of transmitting a message submitted from the message storage unit 106 via the subscriber's apparatus 101 to another relay system or delivering the message to the message storage unit 106 connected to its own relay system . That is, a message is stored in the message storage unit 106 using the P3 protocol, a message is received from the message storage unit 106, and a message is transmitted to another message relay using the P1 protocol (message transfer protocol). In addition, a plurality of message relays may be connected to relay messages, a message may be delivered using the accumulation-storage method, a confirmation service may be provided to notify the message delivery requestor whether the message delivery is successful or failed, It provides a variety of services such as delivery selection function such as support according to rank, resource delivery, content conversion to various media, error submission and delivery of messages.

2 shows an example of a loop structure of an electronic document for explaining a loop structure.

In FIG. 2, the segment group 1 has a structure including an arbitrary segment AAA and segment groups 2 and 3, and may be omitted because the loop status is optional (C). However, if used, it can be repeated up to 10 times.

Segment group 2 consists of an arbitrary segment BBB and a segment CCC. Each time segment group 1 is repeated, segment group 2 can not be omitted because the loop state is mandatory (M) and must be used repeatedly at least twice. When segment group 2 is repeated, any segment BBB must be used, any segment CCC may be omitted, and used up to two times at each iteration if used.

The segment group 3 is composed of an arbitrary segment DDD and an arbitrary segment EEE, and each time the segment group 1 is repeated, the segment group 3 can be omitted because the loop state is optional (C). However, if used, any segment DDD MUST be used, the segment EEE may be omitted, and if used, any segment EEE may be repeated up to a maximum of nine times.

A segment is a unit of a sentence in an electronic document. It consists of a plurality of elements starting with a segment tag (Tag), ending with a period "", and performing a word role. The segment tag is an element consisting of three upper case letters, which serves as a prefix representing the sentence, and has an initial (Initial) that can infer the contents of the information included in the sentence.

One electronic document consists of a set of a plurality of segments and realizes iterative representation of a specific sentence through repeated use of segments.

Figures 3a and 3b are a set of segments that are semantically related to each other in an electronic document and are represented in a loop form and allow the included segments to be treated logically as a lump.

The structure in which the loop structure of the electronic document shown in Figs. 3A and 3B is converted into a data structure recognizable by the document conversion unit is shown in Fig.

In Figs. 3A and 3B, the correlation and the loop relationship of the segments are expressed using graphic lines. In Fig. 4, the relationship is represented by data values.

The identifiers (ID) of the segment groups shown in FIGS. 3A and 3B are assigned an identifier (ID) value starting from 'A' and increasing in ASCII code value as shown in FIG. A segment group having a loop ID with a large loop ID value of a loop identifier (ID) appears before a segment group having a loop ID whose ASCII code value is relatively smaller. 3A and 3B, the segment group 5 includes the segment groups 6 and 7, the segment group 5 becomes the parent loop of the segment groups 6 and 7, and the segment groups 6 and 7 are the child of the segment group 5 ) Loop.

Segments that are not included in the segment groups in FIGS. 3A and 3B do not have loops, so that in the data structure of FIG. 4, the reverse loop ID is expressed as "$" and the loop ID thereof is represented as "0". The loop condition and the loop iteration are also expressed as " 0 ".

3A and 3B are segments included in the loop, segments in the segment group 1 of FIGS. 3A and 3B are segments included in the loop. Therefore, in the data structure of FIG. 4, The condition is " C " which is selectively indicated, and the number of loop repetitions is 99. This means that segment group 1 may be omitted (because the loop condition is optional) and may be looped up to 99 times.

Since the segment group 6 in FIGS. 3A and 3B is included in the segment group 5, the segments included in the segment group 6 are represented by two loop IDs "E" and their own loop IDs "F" in the data structure of FIG. 4 , The loop condition is "C", and the number of loop repetitions is 9. This means that segment group 6 can be omitted (because the loop condition is optional) and can be looped up to a maximum of nine if used, when segment group 5, which is a reverse loop, is looped once.

The data structures necessary to verify the validity of repeated use of a segment using the electronic document data structure as shown in FIG. 4 are shown in FIGS. 5, 6, and 7.

In the present invention, a "C" -like language is used to represent algorithms and data structures for convenience.

5 is a loop information structure including the order of the loops included in the electronic document and correlation information.

The components shown in Fig. 5 are as follows.

Loop identifier (loop_id): An identifier (ID) that identifies a loop used in an electronic document. An identifier (ID) value is assigned in ascending order of the ASCII code value starting from 'A'.

A loop identifier (parent_loop_id): It has a loop ID that contains itself.

Loop start position (loop_start_position): It has the index value of the segment where the loop starts on the electronic document.

Loop iteration count (loop_repeat_count): It has looping accumulation value of loop.

Loop iteration upper limit (loop_repeat_upper_limit): It has the maximum allowable iteration number of loops defined on the electronic document.

In the present invention, it is assumed that up to 60 loops can be included in one electronic document.

FIG. 6 is a data structure having information on the number of times of use of a segment. The components are as follows.

Unit usage frequency (accurency): It means the number of unit usage of segment. This value is initialized to 1 each time it is looped.

Total cumulative use count (total_accurency): The cumulative cumulative use count of segments.

7 is a data structure having electronic document structure information, and is composed of the following components.

Segment identifier (segment_id): It has tags of the segments constituting the electronic document.

Segment condition (segment_condition): Indicates the use attribute of the segment, that is, whether it is mandatory use (M) or selective use (C) segment.

Segment repetition number (segment_repeat_number): It has the maximum number of repetitions allowed in the segment specified in the electronic document. This number of iterations means the number of iterations that can be tolerated without looping.

Loop_id (parent_loop_id): means the loop ID containing the loop containing the segment.

Loop identifier (loop_id): means the loop ID containing the segment.

Loop condition (loop_condition): Indicates the usage attribute of the loop containing the segment, that is, required use (M) or selective use (C) loop.

Number of loop iterations (loop_repeat_number): It has the maximum number of iterations of the loop that contains the specified segment in the electronic document.

FIG. 8 shows a flowchart for setting correlation information of segments and loops of an electronic document according to the present invention to an electronic document, a loop, and a frequency data structure.

The first task for validation of segment repetition of an electronic document is to set the electronic document as shown in FIG. 4 in the electronic document data structure of FIG. 7 on a record basis (801). At this time, each record of the electronic document is referenced through the electronic document data structure separated by the index variable 'n'. Here, index 'n' represents the position number of the segments in the electronic document. That is, if the value of 'n' is '1', it means the first segment in the electronic document, and if it is '2', it means the second segment.

Also, when representing a data structure corresponding to an index 'n', 'm', etc., it is expressed as 'data structure [n]', which means 'n' th data structure.

Next, in order to set the inclusion and correlation information of segments and loops included in the electronic document in the loop data structure of FIG. 5, the index 'n' is incremented by '1' until all the segments in the electronic document are executed (802).

If the number of loop repetitions of the segment of the electronic document data structure [n] is '0' (803). If it is '0', the corresponding segment is not a loop start segment and should be skipped. If the loop iteration count is not '0', the index 'm' value for setting the loop data structure of FIG. 5 is obtained (804).

The value of 'm' in the step 804 is a residual value obtained by dividing the decimal ASCII code value of the loop identifier (ID) of the corresponding segment of the electronic document data structure [n] by '64'. Therefore, the first loop information having the loop identifier 'A' in order is the loop information having the loop identifier 'B' in the first loop data structure since the value of the index 'm' is '1' Is '2', it is set to the second loop data structure.

The loop identifier (ID) of the electronic document data structure [n], the loop identifier (ID), the position number in the electronic document of the segment in which the loop is started, and the loop count value of the loop, (ID), the loop start position, and the loop repetition upper limit value, and sets the loop repetition count in the loop data structure to '0' (805 to 808).

In order to initialize the frequency of use of the segments in the electronic document, the frequency data structure of FIG. 6 is initialized to '0' (809).

By performing the above steps from (801) to (809), necessary data structure (FIGS. 5, 6 and 7) for ensuring validity of repeated use of segments in the electronic document is secured.

FIGS. 9A and 9B are flow charts for validation of segment repetition use according to the present invention. All segments in an electronic document must be validated for segment repetition use each time they are used or referenced before being processed as data in an electronic document. That is, it must be checked whether or not the use of the segment does not deviate from the allowable use frequency range stipulated by the electronic document as shown in FIG. 4 before use.

In the present invention, it is assumed that the position index in the electronic document of the current segment to be validated before use is 'p', the position index in the electronic document of the immediately preceding segment is 'q' Start the algorithm.

First, the unit usage count and the cumulative use count of the current segment of the frequency data structure [p] are incremented by 1 (901). Here, the unit usage count is always equal to the total cumulative use count when the segment is not included in the loop. However, if the segment is included in the loop, the unit usage count is initialized to 1 every time looping (i.e., loop repetition) occurs. On the other hand, the total cumulative use count is increased by 1 every time the segment is used, but is never initialized, so it has a total use count for the segment.

First, it is checked 902 whether the unit usage count value of the frequency data structure [p] corresponding to the currently used segment exceeds the segment repeat count value of the electronic document data structure [p]. If the unit usage count value exceeds the allowed number of segment repetition count of the electronic document data structure [p] Since it is used in excess of the number of segment repetitions, processing according to the segment overuse error is performed (903) and the verification is terminated.

On the other hand, if it is not exceeded, it is checked whether the currently used segment is a segment included in the loop (904). This is done by examining whether the loop identifier value of the electronic document data structure [p] is not zero and the number of loop iterations is zero.

If the segment is a segment included in the loop, then it is checked 905 whether the current number of looping times of the loop to which the segment belongs exceeds the loop-structured loop use upper limit value in the electronic document. This allocates the remainder value obtained by dividing the decimal ASCII code value of the loop identifier (ID) of the corresponding segment of the electronic document data structure [p] by 64 to the index " m ", and sets the loop start position value of the loop data structure [ 'l', and then checking whether the value of the loop iteration number of the loop data structure [m] is larger than the value of the loop iteration number of the electronic document data structure [l].

If the result of the inquiry in step 905 is exceeded, processing according to the use error exceeding the loop repetition use upper limit value is performed (step 906). Otherwise, step 912 is performed.

If the segment is not a segment included in the loop 904, if the index 'p' value is greater than the index 'q' and the current segment corresponding to index p is the loop start segment 907, If the number of loop repetitions of the data structure [p] is greater than 0, the loop repetition count value of the loop data structure [m] is initialized to 1 (908). The first looping starts in step 908.

The value of the index 'p' is smaller than the value of the index 'q' (this means that the currently used segment is located at a position that appears first in the electronic document structure than the segment used immediately before, If the segment corresponding to p 'is a loop start segment (909), that is, if the number of loop iterations of the electronic document data structure [p] is greater than 0, the loop iteration count value of the loop data structure [m] is incremented by 1, The unit usage count value of the structure [p] is initialized to 1, the index 'p' value is replaced with the index 'q' value (910), and step 911 is performed. The number of times of loop repetition of the loop data structure is incremented by 1 and the number of times of use of the frequency data structure corresponding to the segment is always initialized to 1 through step 910. [

It is checked whether the segment to be used is not related to the loop, that is, the loop identifier value of the segment is 0 (step 911), and if the segment is not related to the loop, the verification process is terminated.

Steps 912 to 916 are steps for checking whether the total cumulative use count value of the segment to be used exceeds the structurally acceptable repetition limit value of the electronic document.

First, it is checked whether there is a reverse loop including a loop including a segment to be used (912). This can be confirmed by checking whether the loop loop identifier value of the loop data structure [m] is '$'.

If there is no back loop, the total cumulative use count value of the segment to use for the frequency data structure [p] is greater than the loop repeat upper limit value of the loop data structure [m] and the segment repeat count value of the electronic document data structure [p] (913). If the difference is larger than the multiplied value, error processing according to the use of the upper limit of the segment size is performed (914).

If it is not large, the validity of the use of segment repetition has been verified and the execution is terminated.

On the other hand, if there is a negative loop in step 912, it is checked whether the total used frequency accumulated value of the segment to be currently used exceeds the loop repeat upper limit value of each of the sub loops including the segment and the repeated use allowable upper limit value of the segment. To do this, first, the value of the segment repetition number of the electronic document data structure [p] is multiplied by the loop repetition upper limit value of the loop data structure [m], and this value is stored in the temporary variable 'A' (915). If there is another loop (i.e., a negative loop) including a loop corresponding to the index 'm' (916), the remainder value obtained by dividing the decimal ASCII code value of the loop loop identifier of the loop data structure [m] 'm' (917), multiplying the loop repetition upper limit value of the loop data structure [m] by the value stored in the temporary variable 'A' obtained above again, and storing the result in the temporary variable 'A' (918). The above process is repeated until there is no negative loop (ie, until the loop-loop identifier ['] of the loop data structure [m] is' $') to end up with the segment The maximum allowable number of repetition times can be obtained.

(919) whether the total cumulative use count value of the segment to be currently used exceeds the loop repeat upper limit value of each of the sub-loops including the segment and the repeat use upper limit value of the segment (value stored in the temporary variable 'A' .

If the number of times of repetition exceeds the allowable number, error processing according to use of the upper limit of the segment is performed (920) and the processing is terminated.

According to the present invention as described above, when an electronic document is transmitted and received using the electronic document exchange system, it is possible to check whether the electronic document to be transmitted and received conforms to a standard electronic document structure agreed upon by the sender and the receiver, The validity of repeated use of segments can be verified based on a standard electronic document structure. It also has the effect of ensuring that the electronic document is correctly mapped to the application, or that the application data generated by the application is correctly converted to a standard electronic document.

Claims (8)

A validation method for use of segment repetition in an electronic document exchange system, A first step of mapping the electronic document structure information to the electronic document data structure, mapping the correlation information of the segments and loops included in each electronic document to the loop data structure, and initializing the frequency data structure indicating the frequency of use of the segments in the electronic document, step; A second step of checking whether the number of times the unit used in the data structure of the segment to be used exceeds the number of times of segment repetition of the electronic document data structure; A third step of performing an error process according to the use of the segment repetition exceeding if it is exceeded in the second step; A fourth step of checking if the segment is included in the loop if it is not exceeded in the second step; A fifth step of initializing the number of loop repetition times if the segment is not included in the loop in the fourth step; A sixth step of checking whether the current looping count of the loop exceeds a loop repeat use upper limit value in the case of a segment included in the loop in the fourth step; A seventh step of processing a use error according to the use of loop repetition if it is exceeded in the sixth step; An eighth step of checking whether the total cumulative use count value of the segments exceeds the repeat use limit value in the sixth step; And If it is exceeded in the eighth step, an error due to use exceeding the upper limit of the segment is handled, and if it is not exceeded, A validation method for the use of the segment repeatedly. The method according to claim 1, In the first step, Setting electronic document structure information in an electronic document data structure; Incrementing the index value until it is performed for all segments comprising the electronic document, and examining whether the current segment is a loop start segment; And if it is not a loop start segment, incrementing the index value. If the loop start segment is not a loop start segment, a loop index value for setting a loop data structure is calculated and a loop identifier value, an inverse loop identifier value, Setting a loop identifier value, a loop loop identifier value, and a loop repeat upper limit value of a loop data structure corresponding to the calculated index value, respectively; And Setting a loop start position value as an index value of the segment, initializing a loop repetition count value, and initializing a unit usage count and a cumulative use count value of the frequency data structure A validation method for the use of the segment repeatedly. The method according to claim 1, In the fifth step, Initializing a loop iteration count value of the loop data structure if the index value of the current segment is greater than the index value of the immediately preceding segment and the current segment is a loop start segment; And If the index value of the current segment is smaller than the index value of the immediately preceding segment and the current segment is a loop start segment, the loop iteration count value of the loop data structure is increased, the unit usage count value of the frequency data structure is initialized, With the index value of the immediately preceding segment A validation method for the use of the segment repeatedly. The method according to claim 1, In the eighth step, Checking whether a parent loop including a loop including a segment to be used exists; If the parent loop does not exist, checking whether the total cumulative use count value of the segment to be used in the frequency data structure is greater than the loop repeat upper limit multiplied by the number of segment repetitions; Processing the error according to the use of the upper limit of the segment if the total cumulative use frequency value is larger; Ending normal use if the total cumulative use frequency value is not greater; If the parent loop exists, checking whether the cumulative value of the total usable frequency of the current segment to be used exceeds the loop repetition upper limit value of each parent loops including the segment times the repetition allowable upper limit value of the segment; And If it is exceeded, the error according to the use of exceeding the upper limit of the segment is handled, and if not exceeding, ending with normal use A validation method for the use of the segment repeatedly. 5. The method according to any one of claims 1 to 4, Wherein the step of checking whether the current segment is a loop start segment is performed by checking whether a loop iteration count of a segment of the electronic document data structure is '0'. 6. The method of claim 5, Wherein the loop index value is obtained by finding a remainder value obtained by dividing a loop identifier code value of a corresponding segment of the electronic document data structure by '64'. 6. The method of claim 5, Wherein the step of checking whether a segment included in the loop is performed by checking whether the loop identifier value of the electronic document data structure is not '0' and the number of loop repetition times is '0'. Way. 6. The method of claim 5, Wherein the step of checking whether there is a parent loop including a loop including the segment to be used is performed by checking whether the parent loop identifier value of the loop data structure is '$'.