JP2002304341A - Transfer device, and system and method for data replacement - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an EDI system capable of easily coping with the change of the system. SOLUTION: An operation system at a sender 150 prepares an internal file to be transmitted to a receiver as a trading partner and stores the file in a processing waiting area 104. A comprehensive information exchange system 103 acquires a transmitting and receiving registry stored in the file server based on the file name of the file for sending, and converts the file into an intermediate file based on the registry, and stores the file in an intermediate area. The file name of the intermediate file is prepared based on the file name of the file for sending and the information on the receiver. An exchanged registry in connection with the name of the intermediate file and corresponding to the system 140 of the receiver is read from a file server 106 and, based on the registry, the file is converted from the intermediate file to the file for sending before sending.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a data exchange system via a network, and more particularly to a transfer device and an exchange system in an EDI system.

[0002]

2. Description of the Related Art In recent years, electronic transactions using a computer network have been activated. An example of this electronic commerce is Electronic Data Interchang.
e: EDI) is widespread. If you use this EDI,
Data such as ordering can be transmitted to and received from business partners. Web-EDI is known as an advanced type of EDI. This Web-EDI uses a Web server and a Web browser to transmit and receive order data and the like created in HTML format to and from a business partner via the Internet.

[0003] In these systems, EDI is used for data exchange between specific companies, while Web-EDI is used for data exchange with unspecified partners, and so-called systems are separated.

When data is exchanged, it is necessary to determine a data format and the like in advance to ensure mutual compatibility. In conventional EDI, this arrangement was made in three stages. First, as a domestic rule, the procedure of exchange, the structure of exchange, the style, the character code to be used, etc. were defined. Next, as a rule for each trading industry, the type, content and meaning of the data to be exchanged were defined as standard messages. Other operational and transactional matters were defined among the participating companies.

[0005]

In the conventional EDI, in actual operation, in addition to the above-mentioned standard specifications, contents unique to a company were added, and in many cases, the standard specifications were not observed. Furthermore, there have been many cases where a system for exchanging incidental information generated during a commercial transaction is constructed using a system different from EDI. Therefore, it was necessary to adapt its own system to the original specifications adopted by the business partners. In particular, when the number of new business partners increases or the content of the business is partially changed, the system and its operation are forced to change, resulting in an increase in development costs and operation costs. Furthermore, in order to develop an individual system for each business partner, a considerable development period is required, and there is a problem that it is not possible to timely respond to the participation of a new business partner or a change in the business method.

[0006] On the other hand, in Web-EDI, by providing a program to be used by a client on the server side, a business partner serving as a client can participate in Web-EDI as long as an environment capable of connecting to the Internet is prepared. There are advantages.
However, when there are a plurality of servers and a plurality of Web-EDIs, the screen style, input method and operation method are different for each of them. In turn, there was a danger of causing trouble in commercial transactions.

[0007] Further, in a company adopting Web-EDI, when the transaction contents and the transaction environment are changed, like the conventional EDI,
It is necessary to change the system and the operation on the server side, and there is an adverse effect that development costs and operation costs increase.

[0008] Furthermore, EDI using the Internet as a communication line has a security problem because the Internet is also used by ordinary users. For example, there is damage caused by eavesdropping, falsification, and spoofing of exchange information. There is a danger of doing.

[0009] The above-mentioned data exchange system employs the legal attainment principle with respect to the establishment of commercial transactions. Therefore, the time when the transaction message arrives at the partner is interpreted as the time at which the transaction was completed. Therefore, determination of the transaction time of a message has a very important meaning, and it is necessary to sufficiently secure communication reliability. In conventional EDI, reliability was secured by the replacement procedure. In contrast, Web-EDI uses the Internet, so communication reliability is low,
There was a problem that confirmation of the establishment of a commercial transaction could not be sufficiently guaranteed. In particular, in business transactions with unspecified business partners that adopt open EDI, it is not possible to predetermine a content collation method or a method of exchanging confirmation results due to its openness. In such systems, there is a tendency to adopt a method of sending the same data again and checking it visually.
Sending the same content multiple times is not a solution because some experts point out that it is a double transaction between companies.

[0010] Therefore, an object of the present invention is to provide a data exchange system that can easily cope with a customer's own specifications.

A further object of the present invention is to provide a data exchange system that can use a user interface on the client side in a unified manner even when dealing with a plurality of different partners.

Further, according to the present invention, in a data exchange system using the Internet as a communication line,
An object of the present invention is to provide a data exchange system that can prevent data tampering and the like.

It is another object of the present invention to provide a data exchange system capable of confirming the establishment of a commercial transaction.

[0014]

According to the present invention, in order to solve the above-mentioned problem, a first file generated in a first information system is transferred to a second information system connected to a specific network. In the transfer device, a first storage device that stores the first file, a conversion rule for performing a conversion process from the first file to a second file, and transmission regarding a destination of the second file A second storage device for storing destination information, and reading the conversion rule from the second storage device based on a file name of the first file, applying the conversion rule, and reading the conversion rule from the first file. A first conversion unit for converting to the second file; and a second file for the second file converted by the conversion unit, based on a file name of the first file and the destination information. File name creating means for creating a file name of the second file, a third storage device for storing the second file with the file name created by the creating means, and a file name of the second file associated with the file name. And a fourth storage device for storing a file exchange rule corresponding to the second information system, and reading the file exchange rule from the fourth storage device based on the second file name, A second conversion unit that converts the second file into a third file by applying an exchange rule; and the third conversion unit based on the file exchange rule.
Transmitting means for transmitting the third file in order to exchange the third file with the second information system.

The specific network is an EDI network or the Internet, but may be another network.

Further, the conversion rule and the exchange rule are as follows:
It is preferable that at least one is described on an XML basis. Of course, another description language may be used as long as the rules can be easily changed.

Further, the present invention further comprises rule management means for creating or modifying the conversion rule and the exchange rule. For example, as the rule management means, an editor program that provides a user interface that can easily change the rule is preferable.

[0018] The present invention is directed to solving the above problems.
In a transfer device for transferring a first file generated in a first information system to a second information system connected to a specific network, a file name of the first file and transmission of the first file Creating means for creating message guide information including destination information regarding a destination, and first storage for storing a first folder storing the message guide information and the first file created by the creating means. An apparatus, a second storage device associated with the message guide information, and storing a file exchange rule corresponding to the second information system, and a second storage device based on the message guide information. Converting means for reading a file exchange rule and applying the exchange rule to convert the first file into a second file; Wherein in order to replace the said second information system the second file based on Le swapping rules second
And transmitting means for transmitting the file.

Since it is generally the user who creates the message guide information, it is desirable to provide a user-friendly environment. For example, at least one piece of standard message guide information is prepared in advance for each application, and this is set as default message guide information. If there are missing or insufficient parts in the default contents, the user may correct only the insufficient parts or add missing contents. A message guide information creation program for achieving these is prepared in a transfer device, a file server, or the like, and the user operates the user's terminal, activates it via a network, and makes necessary corrections. Good. Here, the message guide information may be a single file or data included in any one of the files.

The message guide information requests processing to be executed in the second information system after the second file transmitted by the transmission means is received by the second information system. May be further provided. For example, as processing to be executed in the second information system, there will be processing for returning delivery confirmation information when the second file has been correctly delivered, and processing for detecting falsification of the second file. Of course, other processing may be requested.

In the falsification detection processing, a hash calculation of the received file, a calculation result of the hash calculation, and a hash calculation result included in the message guide information and calculated in advance by the transfer device are compared. Matching process. Of course, a method other than the hash calculation may be used as long as tampering can be detected.
Further, in order to solve the above-mentioned problem, the invention of the present application transmits information comprising a disclosure unit and a non-disclosure unit to the first via a relay system.
In the data exchange method for exchanging the information from the system to the second system, the first system reads the disclosure unit, and performs the process based on data on an exchange route of the information described in the disclosure unit. Identifying a final destination of information exchange, and, if the exchange destination is the second system, acquiring a first encryption method corresponding to the second system from an encryption table; Encrypting the non-disclosure unit using the first encryption method, and identifying a relay destination of the information based on data on an exchange route of the information described in the disclosure unit Acquiring the second encryption method corresponding to the relay system from an encryption table when the relay destination is the relay system; Encrypting the disclosure unit using: transmitting the encrypted non-disclosure unit and the encrypted disclosure unit to the relay system; and Receiving the information and the encrypted disclosure unit from the relay system; decrypting the received disclosure unit; and transmitting the information to the next destination (the next relay destination or the final destination) based on the decrypted disclosure unit. And a step of obtaining a third encryption method corresponding to the second system from the encryption table when the specified destination is the second system. Encrypting the decrypted disclosure section again with the third encryption method, the disclosure section encrypted with the third encryption method, and encrypting the decrypted disclosure section with the first encryption method. Non- Wherein the radical 113 second
Transmitting the information to the system, receiving the disclosure unit and the non-disclosure unit encrypted by the third encryption method, and decrypting the disclosure unit. Identifying the transmission source based on the decrypted disclosing unit, and, when the identified transmission source is the first system, a decoding method corresponding to the first system. , And a step of decoding the non-disclosure unit with the decoding method. The disclosure unit may be transmitted as message guide information.

The first system performs a first hash operation on the encrypted non-disclosed portion, and stores an operation result obtained by the first hash operation in the disclosed portion. And further comprising:
The relay system executes a second hash operation on the received non-disclosure unit, an operation result of the first hash operation stored in the decrypted disclosure unit, and the second hash operation.
And a step of transmitting a tampering detection to the first system if they do not match.

Further, the second system executes a second hash operation on the received non-disclosure unit, an operation result of the first hash operation stored in the decrypted open unit, And a step of transmitting a tampering detection to the first system if they do not match.

Further, the first system displays a list of processes to be executed in the second system, and executes the second system selected by a user in response to the display. Storing, for the process to be performed, data specifying the process in the disclosing unit, wherein the second system specifies the process from the decrypted disclosing unit, and executes the process. And the step of performing.

The processing to be executed in the second system includes, for example, respective processing of a hash operation for the non-disclosed part and a detection report of improvement,
Although there is a delivery confirmation process for the non-disclosure unit, other processes may be used.

Further, the present invention has been made in order to solve the above problems.
The information including the disclosure unit and the non-disclosure unit is exchanged from the first information processing device that is the transmission source to the second information processing device that is the final exchange destination via the relay device that is the relay destination. In the data exchange system, the first information processing apparatus may include: a reading unit that reads the disclosure unit; and a final destination of the information based on the content of the disclosure unit that is read by the reading unit. First specifying means for specifying, first obtaining means for obtaining a first encryption method corresponding to the exchange destination, and first obtaining means for encrypting the non-disclosure part by the first encryption method. Encryption means, second identification means for identifying a relay destination of the information based on the contents of the disclosure unit, and second acquisition means for acquiring a second encryption method corresponding to the relay destination A second encryption method for encrypting the disclosure unit with the second encryption method. The first transmitting means for transmitting the encrypted non-disclosure part and the encrypted disclosure part to the relay system that is the relay destination; First receiving means for receiving the information and the encrypted disclosure part from the relay device; decryption means for decrypting the received disclosure part; and a next destination (next destination) for the information based on the decrypted disclosure part. Third specifying means for specifying a relay destination or an exchange destination), third obtaining means for obtaining a third encryption method corresponding to the next destination, and third specified encryption method. Thus, the third encrypting means for re-encrypting the decrypted disclosure unit, the disclosure unit encrypted by the third encryption method, and the non-disclosure unit confirmed to match in the collation are described above. A second transmitting means for transmitting to a destination, and the second information processing device, A second receiving unit that receives the disclosure unit encrypted by the third encryption method and the non-disclosure unit encrypted by the first encryption method; and decrypts the disclosure unit. A second decoding unit, a fourth specifying unit that specifies the transmission source based on the decoded disclosure unit, a fourth obtaining unit that obtains a decoding method corresponding to the specified transmission source, And a third decoding unit for decoding the non-disclosure unit using the decoding method.

It is to be noted that the first information processing device is configured to execute first hashing operation on the encrypted non-disclosed portion, and to calculate an operation result obtained by the first hashing operation. A first storage unit that stores the non-disclosure unit, wherein the first storage unit stores the first storage unit in the disclosure unit;
A verification unit that verifies the operation result of the first hash operation stored in the decrypted disclosure unit with the operation result of the second hash operation; if they do not match, the first information processing apparatus is tampered with; And a third transmitting unit for transmitting the detection of the second detection.

[0028] The first information processing apparatus may further include a display unit for displaying a list of processes to be executed in the second information processing device, and a process selected by a user corresponding to the display. And second storage means for storing request data for requesting the processing in the disclosing unit, wherein the second information processing apparatus specifies the request data from the decrypted disclosing unit. May be further provided, and execution means for executing the processing.

[0029]

DESCRIPTION OF THE PREFERRED EMBODIMENTS [First Embodiment] In this embodiment, an integrated information exchange system is provided between its own system and a business partner system to absorb differences between the two systems. Since the difference of the system is different for each business partner, conversion rules and exchange rules are prepared for each business partner. Also,
In order to respond to the addition of a new business partner or a change in the system of an existing business partner, it is relatively easy to cope only by modifying the conversion rule or the exchange rule.

FIG. 1 shows the system configuration of this embodiment. A plurality of user terminals 101 are connected to a business system 100 via an in-house LAN 102 on an intranet 150 of a company.
Is connected to The user terminal 101 executes transfer software such as Web browser software, mail software, and FTP, and transmits and receives files to and from the business system 100 and the integrated information exchange system 103 via the software. Also,
In the intranet 150, the file servers 104 to
106 are present. These file servers are used for storing files by the user terminal 101, the business system 100, and the integrated information exchange system 103. Instead of providing a file server, a hard disk built in the integrated information exchange system 103 or the like may be used. The integrated information exchange system 103 is connected to a business partner system via an arbitrary communication network 110. In the present embodiment, of the parties to the transaction, the side transmitting the data may be referred to as the sender, and the partner of the transaction, that is, the side receiving the data, may be referred to as the destination (130 or 140). The relay destination 120 may be arbitrarily provided between the transmission source and the destination 130.

FIG. 2 shows a business system 100, a user terminal 101, an integrated information exchange system 103, and a relay destination 120.
And the computer configuration of the destinations 130 and 140.

The CPU 200 executes various programs stored in a hard disk drive (HDD) 206. The RAM 201 is a random access memory and is used for executing a program. ROM 202
Is a read-only memory and the computer BIOS
Etc. are stored. The display 203 is a display device. The communication IF 205 is a communication device such as a network card or a modem for connecting to a LAN or the Internet. The input device 207 is configured by a keyboard or the like.

Now, an example will be described in which EDI processing is executed using the transmission / reception registry and the exchange destination registry based on the above-described configuration. That is, the transmission / reception registry and the exchange destination registry are a set of information on data conversion rules and data exchange rules required for continuous transactions. More specifically, the transmission / reception registry is a business system 10
0 and control information necessary for file editing between the integrated information exchange system. For example, if the user is continuously trading, the file created by the business system 100 is often transmitted to the trading partner. In such a case, the file created by the business system 100 must be changed to a format that can be processed by the integrated information exchange system 103. Therefore, when the format is changed, data serving as a reference for the change process is stored in the transmission / reception registry. On the other hand, the exchange destination registry stores control information required when editing a file for each exchange destination (relay destination, destination, etc.). For example, if a file is created with reference to the transmission / reception registry, then a file conversion process according to the specifications of the business partner is required. Therefore, data serving as a basis for file conversion processing for each trading partner is stored in the exchange destination registry.

These two types of registries have an element name,
It contains the value corresponding to the element name, and is described based on XML. Since it is based on XML, the description order of the elements is not important, and the elements can be freely selected and combined. In other words, since it is rich in expandability, it is possible to easily deal with the addition of a business partner and the change of the business partner system. For example,
When the exchange contents and the number of destinations increase, or when switching to the conventional EDI or Web-EDI according to the destination system, it can be handled simply by adding or changing the registry information. Furthermore, future expansion of usage can be handled by adding elements. In this way, the system of the connection part for data exchange can flexibly process based on the destination registry exchange destination registry.

FIG. 3 shows the configuration of the transmission / reception registry. The transmission / reception registry includes element names 301 to 306 and values corresponding thereto. The transmission / reception section 301 indicates whether the registry is used for transmission or the registry used for reception. The internal file name 302 is the name of a file to be processed in the processing waiting area. The exchange destination code 303 is a company code indicating the exchange destination of the internal file, and is used for collating with the company code of the business partner registered in the exchange destination registry. The exchange section 304 indicates that the destination of the message included in the processing target file is VAN, mixed, or single. The division section 305 indicates whether division by destination is necessary before transmission or division of the transmission source after reception is required. The creation category 305 indicates whether, when a message having the same destination exists in the internal file, the message is added to the internal file or an individual file is created and written to the intermediate area.

FIG. 4 shows the structure of the replacement destination registry. The exchange destination registry includes element names 401 to 404 and values corresponding thereto. In the company code 401, the company code of the exchange destination is stored as a value. The name of the person in charge of the exchange destination company is stored as a value in the person in charge of the exchange destination. The exchange e-mail 403 contains the e-mail
-mail address is stored as a value. Description part 404
Stores element names 411 to 418. In the internal file name 411, the name of the processing target file stored in the intermediate area is stored as a value. Send / receive file name 4
12, a file name for external exchange is stored as a value. Outside (such as a VAN company) determines the process at the time of relaying based on this file name. The exchange method 413 includes VAN
Whether the data is transmitted via the Internet or directly to the other party is stored as a value. In the exchange procedure 414, a protocol name to be used is stored as a value. In the exchange method 415, a conversion method for a file to be exchanged or a message to be exchanged is stored as a value. The edit category 416 stores whether a plurality of files having the same exchange destination are combined into one file as a value. In the transmission / reception directory 417, a name of a directory for registering a processing result is stored as a value. In the integrated destination 418, a company code of the exchange destination when the exchange file is collectively transmitted to another exchange destination (such as a VAN) is stored as a value.

In this embodiment, when only a file is transferred, the process is performed by referring to the transmission / reception registry and the exchange destination registry based on the file name.

FIG. 5 shows an outline of the processing in the intranet. The internal file created by the business system 100 or the user terminal 101 is first stored in the processing waiting area 104 of the file server. The integrated information exchange system 103 reads the internal file at an arbitrary timing and creates an intermediate file based on the transmission / reception registry. The created intermediate file is stored in the intermediate area 105 of the file server. Integrated information exchange system
103 reads out the intermediate file at an arbitrary timing, creates a transmission file based on the exchange destination directory, and stores it in the sending waiting area 107 of the file server. Finally, the integrated information exchange system 103 reads the transmission file from the transmission waiting area at an arbitrary timing and transmits the file to the destination.

FIG. 6 shows a flowchart for processing an internal file stored in the processing waiting area. It is assumed that the sending / receiving registry and the exchange destination registry are created in advance by the EDI administrator.

The integrated information exchange system 103 reads an internal file at an arbitrary timing (S10). This timing may be regular or may be timing based on a user's instruction. FIG. 7 shows the stored contents of the processing waiting area 104. In the processing waiting area 104 on the file server, a file named gyoumu10 and a folder named fldr20 are stored.
The internal file gyoumu10 is created by the business processing system, and one file contains at least one message. Destination information is added to the beginning of each message. Each message is delimited by a separator, and as illustrated in FIG. 7, messages with different destinations may be mixed.

The fldr 20 is a folder format internal file. The fldr 20 includes message guide information, main information to be transmitted to the supplier, and a plurality of related information.
The internal file in the folder format is created by the user terminal 101. Message guide information is information that has the same content as the sending and receiving registry,
Describes the content of the process to be executed at the business partner. Details will be described later. The message guide information can be distinguished from other files by giving a unique file name. For example, a naming rule for the file name (or the first n characters of the file name) may be determined in advance.

The integrated information exchange system 103 determines whether the read file is in the file format or the folder format based on whether or not the read file contains the message guide information (S15).

Next, the integrated information exchange system 103
The transmission / reception registry is read from the file server 106 (S30). Specifically, the integrated information exchange system extracts a file name (referred to as an internal file name N) when the content extracted from the processing waiting area is not in a folder format,
A search is made for a transmission / reception registry whose value of the element “internal file name” of the transmission / reception registry matches the internal file name N.
FIG. 8 shows an example of data in the transmission / reception registry. According to this example, the name of the file to be processed "gyoumu
A transmission / reception registry having "value 11" having "1" as an element is selected.

Next, "value 1" of the selected transmission / reception registry
Reference is made to the values of "exchange division" and "division division" described in "1". According to the example of FIG. 8, they are “mixed” and “divided”, and in this case, the integrated information exchange system 103
Determines that a plurality of messages are included in the internal file to be processed, and executes processing for dividing the message into message units (S40). In the example of FIG. 8, the internal file gyoumu10
Is divided into four messages.

Next, with respect to the message obtained in S40, destination information added to the head of the message is extracted (S50). For example, the destination of the message 1 shown in FIG. 7 is “F1”. Next, the exchange destination registry corresponding to the destination extracted in S50 is searched (S60). FIG. 9 shows a specific example of the replacement destination registry. For example, a search is made for a match between the "company code" of the exchange destination registry and the destination. In the example of FIG. 9, “value 21”, which is the destination “F1” of the message 1 in the internal file gyoumu10, is the replacement registry to be obtained.

Next, an intermediate file name is created based on the value of the "company code" in the exchange destination registry and the value of the "internal file name" in the detail part. For example, "company code + internal file name". Further, an intermediate file is written with the created file name (S70). In addition, when the value of the “creation category” of the transmission / reception registry read in S30 is “append”, a file with the same name already exists in the intermediate area, and if it does not exist, the file is newly created. . In the example of FIG. 8, the message 4 is added after the message 1 of the internal file gyoumu10, and is written in the intermediate area 105 as the intermediate file name “F1 + gyoumu10”. Message 3 is added after message 2 of the internal file gyoumu10, and the intermediate file name “G1 + gy” is added to the intermediate area 105.
oumu10 ".

The processing from S50 to S70 is performed for all messages (S80), and the processing from S10 to S80 is performed for all files (S90).

Next, the integrated information exchange system creates a transmission / reception file for the intermediate file stored in the intermediate area 105 at a specified time or periodically, and stores the file in the transmission waiting area 107 of the file server. FIG.
9 shows a flowchart for processing a file in the intermediate area 105.

First, the integrated information exchange system 103
Intermediate file (or intermediate folder,
Is read from the intermediate area 105 (S210).

Next, a replacement registry is searched based on the file name of the read intermediate file (S220). The file name of the intermediate file is “company code + internal file name” as described above. So, from this file name +
Is used as a separator to obtain the company code and the internal file name, and the value of the element "company code" of the exchange destination registry matches the value of the element "internal file name" of the item description Search the replacement registry.

Next, as for the replacement destination registry extracted by the search in S210, the value of the “edit category” of the detailed part is “
(S225). If the result of the determination is that the file has been designated as a batch, the intermediate files with the same destination are edited into one (S230). It is determined whether there is a file (S235), and if so, an intermediate file to be subjected to the grouping process is read from the intermediate area 105 (S240), and the process is continued until all the grouping processes are completed.

An example of a specific grouping process will be described below. The summarization process differs depending on the value of the element, and performs the following processes, respectively.

(1) In the case where the value of “Exchange method” in the specification part of the exchange destination registry is “direct” and the value of “Edit category” is “Summary”, the element name “Transmit / receive directory” of the same specification part The value and the value of the element name “send / receive file name” are obtained and stored. Intermediate file "G
If "1 + gyoumu10", "value 2" of the replacement registry in FIG.
2 ”, the value“ d002 ”of the element name“ transmission / reception directory ”and the value“ snd20 ”of the element name“ transmission / reception file name ”are stored. If there is an unprocessed intermediate file corresponding to the intermediate area that has a value that matches the stored value with reference to other detailed parts of the same exchange registry, this is also read and collected. All the contents of the read-into-be-compiled intermediate file are additionally recorded, collected and stored, and the process proceeds to the next step.

(2) When the value of “exchange method” in the specification part of the exchange destination registry is “VAN” and the value of “edit category” is “summary”: the element name “send / receive directory” of the same specification part And the value of the element name “send / receive file name” are obtained and stored. Based on the value of the element name "company code" (referred to as company code K) of the replacement registry, another replacement registry is searched. If the company code K is registered as a value of "integrated destination" in another destination registry (referred to as a destination registry R), it can be understood that the destination is a batch transmission in which destinations are mixed via VAN. The coordination processing performed by the integrated information exchange system in this case will be described with reference to FIG. Since “F1” is included in the value of the element name “integrated destination” of the exchange destination registry “value 23”, it is understood that the destination is a batch transmission in which the destinations are mixed via the VAN. Also, the value of the element name “company code” is “VAN1” and the value of the element name “send / receive file name” is “van10”. Next, referring to the exchange destination registry "value 21" in which the value of the element name "company code" is "F1", the detail part 1 in which the value of the element name "transmission / reception file name" is the same "van10" is found. From the value "gyoumu10" of the element name "internal file name" of this detailed part 1, the intermediate file "F1 + gyoumu1
It is understood that it is necessary to collect "0" for VAN transmission. If the intermediate file "F1 + gyoumu10" is not yet processed, it is read and set as a target for collection. Element name "send / receive file name"
, And if there is a file having the same “send / receive file name” value “van10”, the corresponding intermediate file is read and collected. Same send / receive file name "van1
This process is repeated until there are no more intermediate files to be collected at "0." If another value is registered as the value of the element name "integrated destination" in the detail part of the replacement registry R,
Similar processing is repeated for this. When this process is completed, all the contents of the read-into-be-compiled intermediate file are additionally recorded, collected and stored, and the process proceeds to the next step.

Next, for the information of the intermediate file (or the file created by the consolidation process) stored in the previous step, whether the conversion method is specified in the value of the detail part “conversion method” of the exchange destination registry Is determined (S245).
If the conversion method is specified, the conversion processing is performed by the specified conversion processing method. (S250). In the example of FIG. 9, the value of the “send / receive file name” of the exchange destination registry is “van10” and “send2”.
If the value is "0", the message is converted into a standard message in CII syntax. For the message corresponding to "mail100", the content of the main information "tmp20" is converted into XML.

Finally, the transmission / reception file subjected to the above processing is written in the transmission waiting area 107 (S260). Specifically, first, the file name of the write-out file is created as the file name “company code + transmit / receive file name” from the value of “company code” and the value of “transmit / receive file name”. Subsequently, a directory to which the file is to be written is extracted from the value of the "sending directory" of the exchange destination registry, and the file is written with the created file name. When writing, it is checked whether the same file name already exists, and if it exists, it is added to the already existing file.
If it does not exist, create a new file. FIG.
In the example, a file named "VAN1 + van10" is stored in the "V001" directory. In the directory of “002”, a file named “G2 + send20” is stored. In addition, the directory of "m010" is "F1 + mail100"
The folder named is stored. The transmission / reception files in the transmission waiting area are edited at regular intervals or at regular intervals with reference to the exchange destination registry and transmitted to the outside for data exchange.

According to the present invention, when the number of new destinations increases, it is only necessary to register information on the new destination in the exchange destination registry. Further, when the transaction system is partially changed, it is only necessary to make necessary corrections to the specification part of the sending / receiving registry and / or the exchange destination registry. In addition, you may replace with a new registry.

Also, conventional EDI, Web-EDI or mail ED
Switching the system to I can be done simply by adding or changing the registry information. These two
Since each type of registry is described with XML-based element names and values, it is possible to select and combine elements in any order.

Further, in the future expansion of usage, it is possible to easily cope with the addition of elements. As described above, the system of the connection part for data exchange can perform processing flexibly based on the transmission / reception registry and the exchange destination registry. Since there is no need to make system or operational changes, it is possible to respond in a timely manner and at a low cost.

[Second Embodiment] In this embodiment, a case will be described in which data to be sent to a destination is transmitted in a folder format. In the folder format, a file describing contents to be transmitted to a destination and message guide information are stored in one folder, and this folder is transmitted to the destination. Note that the message guide information is created by the user or the integrated information exchange system 103.

FIG. 11 shows the structure of the message guide information. FIG. 12 shows a specific data example of the message guide information. The message guide information also consists of element names and corresponding values, as in the previous registry.
It can be described on an XML basis. Subject 10
01 stores the title of the transmission content as a value. The main information file name 1002 stores, as a value, a file name of main information describing the details of the transaction. Send type 1003
Stores the type of information to be traded as a value. The message level 1004 stores a message handling level as a value. The destination 1005 stores the company code of the business partner as a value. This value is checked against the company code of the business partner registered in the exchange registry. The destination name 1006 stores the formal name of the customer as a value. The partner person name 1007 stores the name of the person in charge of the business partner as a value. The contact person e-mail 1008 stores the e-mail address of the contact person as a value. Sender 1
009 stores the company code of the sending company as a value. The creator 1010 stores the creator and issuer of the message as values. The creator e-mail 1011 stores the e-mail address of the creator or issuer of the message as a value. The creation date 1012 stores the creation date and issue date of the file as a value. The collation data 1013 stores data required for falsification detection as a value. This value is
The result of the hash operation is stored. The action request 1014 stores the content of the request as a value when requesting the business partner to execute an arbitrary process. The action result 1015 stores the execution result requested by the business partner based on the action request as a value. The related information file name 1016 stores, as a value, the file name of the related information sent along with the main information.

Now, in the processing waiting area 104 shown in FIG. 7, a folder fldr20 is stored as a file to be processed. Referring again to the flowchart of FIG. 6, it is determined whether the message read information read from the waiting area includes the message guide information (S15). For example, if there is no message guide information, the file format is determined, and if it has message guide information, the file format is determined. That is, this determination is a process of determining whether the processing target is a file format or a folder format. Therefore, any other process may be used as long as it can determine which one is.

Next, the integrated information exchange system 103
Read the message guide information included in the folder,
The value of the element name that will be required in the subsequent steps is obtained (S20). In the examples of FIGS. 7 and 12, “value 3” is obtained from the message guide information of msggd20 included in the folder fldr20.
The value “F1” of the element “destination” of “1” and the value “tmp20” of the element “main information file name” are extracted. Although the above-described processing from S60 is executed based on the transmission / reception directory, in the present embodiment, the processing is executed using the value extracted from the message guide information. For example, in S60, the replacement destination registry is searched based on the destination extracted in S20. folder
Based on the destination "F1" of fldr20, "value 21" is extracted as the desired replacement registry. In S70, the folder fldr20 is written as the folder name "F1 + tmp20" in the intermediate area in the same state as that in the area waiting for processing. The following processing is performed in the same manner as in the case of the file format.

In preparing the message information, a model intended for common use is prepared in advance, and a creation assistance program that can be created in an interactive manner according to the purpose of use of the user is prepared in the user terminal. It may be executed at 101. Alternatively, the user terminal 101
b. Launch the browser to access the integrated information exchange system 103 and access the integrated information exchange system 103 via the CGI.
May be created by executing the creation assisting program. In the latter case, message information is created by displaying a plurality of candidates for each element and marking the radio box.

[Third Embodiment] In this embodiment, as another method of using the message guide information, for example, an example in which the message guide information is used for setting a transfer route of a message or for requesting an action at a destination is disclosed. By the way, in EDI, it is essential to set the relay route of the VAN and express the final destination and the like. If message guide information is employed as this expression, the contents of transmission can be protected from eavesdropping and tampering at the relay destination.

FIG. 13 shows an outline of this embodiment. In the present embodiment, information necessary for relay processing at a relay destination is stored in a message information section, and encryption is performed by an encryption method determined with the first relay destination. On the other hand, texts and accompanying materials such as order data stored in a file different from the message guide information are encrypted by an encryption method agreed with the business partner who is the final destination of these materials. At the relay destination, only the disclosure unit (public unit) is decrypted to extract the message guide information, and the next relay destination and the encryption method agreed with the next relay destination are specified and encrypted. Finally, everything is decrypted at the final destination. As described above, in the present embodiment, information necessary for relaying is set as a disclosure unit, and information related to a transaction is divided into a non-disclosure unit (non-public unit) and separately encrypted. No more eavesdropping or tampering.

Next, a processing flowchart of this embodiment shown in FIG. 14 will be described. The sender's integrated information exchange system 103 reads the message guide information created in the user terminal 101 (S1401). The final destination is specified from the read message guide information (S1402), and the encryption method negotiated with the final destination is specified from the encryption table stored in the file server 106 (S1403). The non-disclosure part is encrypted using the specified encryption method. A hash operation is performed on the encrypted non-disclosure part (S1405), and the operation result is stored as the value of the collation data 1013 of the message guide information.
(S1406). Next, the first relay destination is specified with reference to the message guide information (S1407). Referring to the encryption table again, the encryption method determined with the specified relay destination is specified. The disclosure unit is encrypted using the specified encryption method (S1409). The disclosure unit and the non-disclosure unit are included in a folder or enclosed in a mail, and transmitted to the first relay destination (S1410).

The first relay destination 120 receives this (S
1411), the disclosure unit is decrypted (S1412), and the message guide information is extracted. A hash operation is performed on the non-disclosure part (S14
13), it is determined whether the value of the data matching unit included in the message guide information matches the calculation result (S1414). if,
If they do not match, it indicates that the non-disclosure part has been tampered with or damaged, and so it is reported that tampering has been detected (S1415). If they match, the falsification has not been performed, and the next relay destination is specified from the message guide information so as to be transferred to the next relay destination (S1416). The encryption method corresponding to the specified next relay destination is specified from the encryption table (S1417), and the disclosure unit is encrypted again by the specified encryption method (S1418). The disclosure unit and the non-disclosure unit are included in a folder or enclosed in an e-mail, and transmitted to the next relay destination (final destination if relay is completed) (S1419).

The destination 130 receives this (S142).
0), the disclosure unit is decrypted (S1421), and the message guide information is extracted. Specify the sender from the message guide information (S
1422), the encryption method corresponding to the specified transmission source is specified (S1423), the non-disclosure part is decrypted by the specified encryption method (S1424), and the process ends (S1425).

The processing performed by the sender integrated information exchange system may be performed by the user terminal. In that case, the following processing is performed.

1) Encrypt the text and accompanying materials using the encryption method and encryption key agreed with the final destination. If necessary, a hash operation is performed on the text or accompanying materials, and the result of the hash operation is added as the value of the element name “verification data” of the message guide information, and used for data tampering confirmation and the like.

2) The text and accompanying materials are encrypted and the message guide information is encrypted with the encryption method and encryption key agreed with the first relay destination and sent to the first relay destination. 3) At the relay destination, decryption processing is performed using a key based on encryption agreed with the issuer.
Since the message guide information is disclosed, the value is referred to and the relay destination serving as the next route is known. If necessary, a hash operation is performed on the contents of the delivery, and the hash value is compared with the value of the element name “verification data” of the message guide information to confirm whether the data is valid data. Encrypted text and accompanying materials and message guide information are encrypted with the encryption method and encryption key agreed with the relay destination on the next route, and sent to the relay destination on the next route. . Thereafter, this is repeated for each relay destination.

4) At the final destination, the content transmitted from the relay to the final destination is decrypted using a decryption key based on the encryption method of the relay. If necessary, a hash operation is performed on the content of the delivery, and the hash value is compared with the value of the element name “verification data” of the message guide information to check whether the data is valid data. Next, the text and accompanying materials are decrypted using a decryption key based on an encryption scheme agreed with the issuer.

As described above, the route setting and the encryption are performed by using the message guide information, that is, by using both the disclosure unit and the non-disclosure unit, the reliability of the transaction data and the Internet connection can be obtained at the application level. , Falsification, spoofing, etc. can be dealt with. It should be noted that the information disclosure / non-disclosure mechanism according to this method can be applied to a specific department in a company, and can be applied to, for example, confidential information exchange such as personnel information.

[Fourth Embodiment] In this embodiment, a destination is made to execute a predetermined process using message guide information.

For example, in a commercial transaction, there may be a case where the transaction is concluded by the delivery of a predetermined electronic document. In such a case, it is considered that the sending principle of sending the electronic document is regarded as the time of delivery, and that the time when the trading partner actually receives the electronic document, that is, the time when the electronic document reaches the other party is considered the time of delivery. There is attainment.
If the transmission principle is adopted, if the transmission time is recorded in the transmission source system, it can be considered that the transaction has been completed at that transmission time, and if the transmission time is attached to the other party together with the electronic document, the other party will also transact Can be confirmed. On the other hand, in the case of the arrival principle, the receiving system records the reception time, regards the transaction as having been completed at that reception time, and informs the sender of the fact that the sender confirms the transaction completion time it can. Thus, in the case of the attainment principle, some means for confirming receipt of the transmitted document, that is, confirming that the transaction document has been delivered to the other party, is required.

Therefore, in the present embodiment, it is possible to request an action to be performed at the destination, such as the above-mentioned confirmation of the delivery. Specifically, the request is mounted on the message guide information, Send it to the destination. The destination performs the requested process (action) based on the request described in the content of the guide information. This execution may be performed automatically as described above, or the fact that an action request has been made is displayed on the display of the person in charge,
It may be executed by a manual operation by a person who looks at the information. Thereby, for example, there is an advantage that the above-described confirmation can be easily performed even in Web-EDI.

FIG. 15 shows the concept of an action request using message guide information. FIG. 16 shows a flowchart of the processing. At present, it is generally interpreted that the establishment of a commercial transaction by EDI is established by the arrival of data at the destination. In the conventional EDI, there is a tendency to omit reception confirmation under mutual agreement, provided that a highly reliable exchange procedure is adopted. However, since Web-EDI uses the Internet, the reliability of transfer is low, and it cannot be guaranteed that commercial transactions have been established. In the present embodiment, for example, the mechanism of delivery confirmation in Web-EDI is realized by the following method.

In the example of FIG. 15, the message guide information is
It contains the contents requested for the delivery confirmation processing to the destination.

At the sending company b, the user terminal 1
01 activates a program for setting an action request in the message guide information (S1601). When the program is started, whether the content confirmation request or the delivery confirmation request is displayed on the display device of the user terminal, and the setting can be made interactively (S1602, S1603). Here, the content confirmation is a process of detecting falsification of the electronic document and returning the result to the sender. For detection,
Matching could be used using the hash operation described above. FIG.
In the example of (1), it is necessary to perform both content confirmation and delivery confirmation (YE
S) is set. When the setting by the user ends, the setting program ends (S1604).

Thereafter, transmission processing is performed according to the flow of FIG. For example, a hash operation is performed on the main information file EDI01 (EDI data) (S1405), and the result (hash value) is stored as a value of “collation data” of the message guide information (S1406). The main information file EDI01 (EDI data) and the message guide information are transmitted to the destination "company a" system in the system of the source "company b" (S14).
Ten).

The system of the destination “company a” obtains the value of “action request” from the received message guide information.
(S1611), based on the value, it is determined whether or not the content confirmation processing is requested (S1612). If required, that is, if YES, perform a hash operation on the EDI data
(S1613), compares the operation result with the value of the "verification data" (hash value at the sender) of the message guide information (S1614), and stores the verification result as the value of the element name "action result" of the message guide information (S1615). If the sending company, such as the company b, registers and discloses the hash calculation program and the verification program on the Web and allows the company a to download the program, the program can be processed without creating a program at the destination. . It is determined whether the message guide information requires delivery confirmation (S1616), and the delivery confirmation is YES.
If so, only the message guide information is transmitted to the source company b (S1617).

In the system of the sending company b, based on the returned message guide information, it is compared with the sending history, and the matching result is managed as history information, and the matching result is checked with the person in charge if necessary. Send the results. Note that the system may be configured so that if the result of the collation does not match, the message is resent. Further, the history information may be displayed on a user terminal or the like so that the user can confirm the delivery.

By using the message guide information in this way, it is possible to mutually specify an operation request, an execution process, and the like at a destination of a message, and the types of messages exchanged without creating a program at the destination. And processing corresponding to the contents can be performed at the destination. In addition, since the message guide information at the time of sending is returned with the delivery result further added, the collation at the sender is facilitated.

According to the present invention, for example, the number of new destinations is increased, the exchange style with the destination is changed, the exchange method such as regular exchange or exchange every time is changed, or the existing exchange method is changed.
Even if the EDI procedure or the exchange means of the Internet is changed, it is possible to cope with these changes only by modifying the values of the elements of the exchange destination registry and the transmission / reception registry or the message guide information in the system. Therefore, system development becomes unnecessary, and it is possible to respond to these changes in a timely and easy manner.

Further, by using the functions of the present invention described above, the interface inside the company is unified, and the conventional EDI and Web-EDI can be used together, or the conventional EDI and Web-EDI can be switched. There is an advantage that it can be easily performed.

Also, a request for adding a new function can be dealt with by adding an element. As a result, the overall business processing cost can be reduced, and the development and test costs can be reduced.

Further, by setting the disclosure part and the non-disclosure part of the message content, it becomes possible to take measures against eavesdropping, falsification, spoofing, etc. on the Internet. For example, the reliability of commercial transaction data could be ensured and leakage could be prevented.

Further, by using the present invention, it is possible to set a route and exchange confidential technical information and the like with a specific department between companies.

Also, in Web-EDI, since the processing at the destination can be specified, the reliability of the establishment of the commercial transaction such as delivery confirmation can be ensured, and the secure electronic commerce with an unspecified number of people can be performed.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating an example of a system configuration according to an embodiment.

FIG. 2 is a block diagram showing a schematic configuration of an integrated information exchange system and the like in the embodiment.

FIG. 3 is a diagram showing contents of a transmission / reception registry in the embodiment.

FIG. 4 is a diagram showing contents of a replacement destination registry in the embodiment.

FIG. 5 is a diagram conceptually illustrating a processing flow in the present embodiment.

FIG. 6 is a processing flowchart of an internal file according to the embodiment.

FIG. 7 is a diagram illustrating an example of a file to be processed in a processing waiting area according to the embodiment;

FIG. 8 is a diagram illustrating an example of storing data in a transmission / reception registry according to the embodiment.

FIG. 9 is a diagram illustrating an example of storing data in a replacement registry according to the embodiment;

FIG. 10 is a flowchart of processing of an intermediate file according to the embodiment.

FIG. 11 is a diagram showing contents of message guide information in the present embodiment.

FIG. 12 is a diagram illustrating an example of storing data in message guide information according to the present embodiment.

FIG. 13 is a diagram conceptually illustrating a flow of an encryption process in the present embodiment.

FIG. 14 is a flowchart for data exchange in the present embodiment.

FIG. 15 is a diagram conceptually illustrating a flow of an action request process in the embodiment.

FIG. 16 is a flowchart of an action request process according to the embodiment.

[Explanation of symbols]

100 ... business system 101 ... user terminal 102 ... LAN 103 ... integrated information exchange system 104 ... file server processing waiting area 105 ... file server intermediate area 106 ... file server sending and receiving registry and exchange destination registry 110 ... EDI network or Internet 120 … Relay destination server 130… Destination system 140… Other destination system 150… Sender's overall system

Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat II (Reference) G06F 17/60 318 G06F 17/60 318Z G09C 1/00 640 G09C 1/00 640D F-term (Reference) 5B082 GA02 HA05 5B085 AA08 AE29 BA07 BG07 CA04 5J104 AA01 AA08 LA05 NA12 PA07 PA10

Claims (19)

[Claims] 1. A transfer device for transferring a first file generated in a first information system to a second information system connected to a specific network, wherein a first file storing the first file is provided. A second storage device for storing a conversion rule for performing a conversion process from the first file to the second file, and destination information regarding a destination of the second file; First conversion means for reading the conversion rule from the second storage device based on the file name of the first file and applying the conversion rule to convert the first file into the second file; File name creation means for creating a file name of a second file based on the file name of the first file and the destination information for the second file converted by the conversion means A third storage device that stores the second file with a file name created by the creating unit, and that is associated with the file name of the second file and corresponds to the second information system. A fourth storage device storing a file exchange rule to be read, and reading the file exchange rule from the fourth storage device based on the second file name, and applying the exchange rule to read out the second file from the second file. Second conversion means for converting to a third file, transmission means for transmitting the third file to exchange the third file with the second information system based on the file exchange rules, A transfer device comprising: 2. The transfer device according to claim 1, wherein the specific network is an EDI network or the Internet. 3. The transfer apparatus according to claim 1, wherein at least one of the conversion rule and the exchange rule is described on an XML basis. 4. The transfer apparatus according to claim 1, further comprising rule management means for creating or modifying said conversion rules and said exchange rules. 5. A transfer device for transferring a first file generated in a first information system to a second information system connected to a specific network, wherein a file name of the first file and the Creating means for creating message guide information including destination information on a destination of one file; and a first folder storing the message guide information and the first file created by the creating means. A first storage device that stores a file exchange rule associated with the message guide information and corresponding to the second information system; and a second storage device based on the message guide information. Converting the file from the first file to the second file by reading the file exchange rule from the storage device and applying the exchange rule Stage and the transfer device characterized by comprising a transmitting means for transmitting the second file in order to replace the second file and the second information system based on the file swapping rules. 6. The message guide information requests a process to be executed in the second information system after the second file transmitted by the transmission means is received by the second information system. The transfer device according to claim 5, further comprising request information to perform the transfer. 7. The process to be executed in the second information system includes a process of returning delivery confirmation information when the second file is delivered correctly. Item 7. The transfer device according to Item 6. 8. The processing to be executed in the second information system includes a falsification detection processing for the second file or the encrypted second file. The transfer device according to claim 6. 9. The falsification detection process includes checking a hash operation of the received file, a result of the hash operation, and a hash operation result calculated by the transfer device and stored in the message guide information. 9. The transfer device according to claim 8, wherein the transfer device includes: 10. An exchange system for exchanging a first file generated in a first information system for a second information system connected to an EDI network or the Internet, wherein the first information system and the exchange system are exchanged. A first storage device for storing a first file conversion rule between the first storage device and a second storage device for storing a second file conversion rule between the conversion system and the second information system; Reading a first file conversion rule from the first storage device based on a file name of a file, and converting the first file into a second file based on the first file conversion rule Conversion means, and the second file conversion rule is read from the second storage device, and the second file conversion rule is read based on the second file conversion rule.
And a transmitting unit that transmits the third file to the second information system via the EDI network or the Internet. Characteristic exchange system. 11. A data exchange method for exchanging information consisting of a disclosing unit and a non-disclosing unit from a first system to a second system via a relay system, wherein the first system comprises: Reading the information, a step of identifying a final destination of the information based on data on the information exchange path described in the disclosure part, and a case where the destination is the second system. Obtaining a first encryption method corresponding to the second system from an encryption table; encrypting the non-disclosure unit using the first encryption method; A step of specifying a relay destination of the information based on data on an exchange route of the information described in a unit, and, if the relay destination is the relay system, corresponding to the relay system. Obtaining a second encryption method from an encryption table, encrypting the disclosure unit using the second encryption method, and encrypting the encrypted non-disclosure unit with the encrypted non-disclosure unit. Transmitting a disclosure unit to the relay system; receiving the encrypted non-disclosure unit and the encrypted disclosure unit from the relay system; and decrypting the received disclosure unit A step of specifying a next destination (the next relay destination or a final destination) of the information based on the decrypted disclosure unit; and if the specified destination is the second system, ,
Acquiring a third encryption method corresponding to the second system from an encryption table; encrypting the decrypted disclosure unit again using the third encryption method; A disclosure unit encrypted by the encryption method of
Transmitting a non-disclosure part encrypted by the first encryption method to the second system, wherein the second system transmits the non-disclosure part encrypted by the third encryption method. Receiving the unit and the non-disclosure unit; decoding the disclosure unit; identifying the transmission source based on the decrypted disclosure unit; When the system is a system, the method comprises: obtaining a decoding method corresponding to the first system from a decoding table; and decoding the non-disclosure unit using the decoding method. Data exchange method. 12. The first system performs a first hash operation on an encrypted non-disclosure unit, and stores an operation result obtained by the first hash operation in the disclosure unit. The relay system further comprises: performing a second hash calculation on the received non-disclosure unit; calculating the first hash calculation stored in the decrypted disclosure unit; 12. The method according to claim 11, further comprising: comparing an operation result of the hash operation of (a) with (a), and transmitting a notification that tampering has been detected to the first system if they do not match. Data exchange method. 13. The system according to claim 12, wherein the second system performs a second hash operation on the received non-disclosure unit, an operation result of the first hash operation stored in the decrypted open unit, and the second hash operation. 12. The method according to claim 11, further comprising: comparing an operation result of the hash operation of (a) with (a), and transmitting a notification that tampering has been detected to the first system if they do not match. Data exchange method. 14. The first system displays a list of processes to be executed in the second system, and specifies a process selected by a user in response to the display. Storing the data in the disclosure unit; and the second system further comprising: identifying the process from the decrypted disclosure unit; and executing the process. The data exchange method according to claim 11, wherein 15. The processing to be executed in the second system includes a hash operation and a falsification detection report for the non-disclosed part. Data exchange method described in. 16. The data exchange method according to claim 14, wherein the processing to be executed in the second system includes a delivery confirmation processing for the non-disclosure part. 17. A method according to claim 17, further comprising the step of transmitting information comprising a disclosing unit and a non-disclosing unit from a first information processing apparatus as a transmission source via a relay apparatus as a relay destination to a second information processing as a final exchange destination. In the data exchange system for exchanging the information, the first information processing apparatus includes: a reading unit that reads the disclosure unit; and a final unit of the information based on the content of the disclosure unit that is read by the reading unit. First specifying means for specifying a temporary replacement destination, and first obtaining means for obtaining a first encryption method corresponding to the replacement destination
Acquisition means, first encryption means for encrypting the non-disclosure part with the first encryption method, and second identification for identifying a relay destination of the information based on the contents of the disclosure part Means for acquiring a second encryption method corresponding to the relay destination;
Acquisition means, and second encryption means for encrypting the disclosure section with the second encryption method, wherein the encrypted non-disclosure section and the encrypted disclosure section are relay destinations. First transmitting means for transmitting to the relay system; the relay device; first receiving means for receiving an encrypted non-disclosure unit and an encrypted disclosure unit from the relay device; and a received disclosure unit Decoding means for decoding the information, third specifying means for specifying the next transmission destination (next relay destination or exchange destination) of the information based on the decrypted disclosure section, and third specifying means corresponding to the next transmission destination. Third to get the encryption method
Acquiring means, a third encrypting means for encrypting the decrypted portion again with the specified third encrypting method, and a revealing portion encrypted with the third encrypting method When,
A second transmission unit that transmits a non-disclosure unit that is confirmed to match in the collation to the destination, the second information processing apparatus includes a disclosure unit encrypted by the third encryption method; A second receiving unit that receives the non-disclosure unit encrypted by the first encryption method, a second decryption unit that decrypts the disclosure unit, and the decryption unit based on the decryption unit. The fourth to identify the sender
, A fourth obtaining unit that obtains a decoding method corresponding to the specified transmission source, and a third decoding unit that decodes the non-disclosure unit using the decoding method. A data exchange system. 18. The first information processing apparatus, comprising: first operation means for performing a first hash operation on an encrypted non-disclosed portion; and an operation result obtained by the first hash operation. The relay device further includes a first storage unit that stores the received non-disclosure unit, a second storage unit that performs a second hash operation on the received non-disclosure unit, and a decryption unit that stores the decrypted disclosure unit. Checking means for checking the calculation result of the first hash calculation and the calculation result of the second hash calculation; and transmitting a tampering detection to the first information processing device if they do not match. 18. The data exchange system according to claim 17, further comprising: a transmitting unit. 19. The first information processing apparatus, comprising: display means for displaying a list of processes to be executed in the second information processing device; and a process selected by a user corresponding to the display. And second storage means for storing request data for requesting the processing in the disclosing unit, wherein the second information processing apparatus specifies the request data from the decrypted disclosing unit. 19. The data exchange system according to claim 18, further comprising: an identification unit according to claim 5, and an execution unit that executes the processing.