JP2016103272A - Information processing device, control method of the same, program, and communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism for easily checking whether the transmission and reception of data is performed as scheduled without requiring an administrator to manually set a notification schedule.SOLUTION: A communication table is provided as a history of the past communication end time; a communication schedule is determined on the basis of the content of the communication table; and if the transmission and reception of data is not performed by a communication limit time of the determined communication schedule, an administrator is notified of the fact.SELECTED DRAWING: Figure 5

Description

  The present invention relates to an information processing apparatus, a control method thereof, a program, and a communication system.

  2. Description of the Related Art EDI (Electronic Data Interchange), which performs electronic commerce by data communication using an Internet line or the like, has been widely introduced in ordering operations in companies. By using this method, business data such as purchase orders and invoices is not exchanged by telephone, fax, or mail, but via a network that connects the company's computer with the business partner. You can communicate in a form.

  In such an EDI data communication business, for example, the ordering person may be the receiving side that accepts communication, and the ordering party may be the originating side that sends the order. The sender (sender) performs communication at an arbitrary timing, and the order receiving side (sender) receives the order data prepared by the orderer (sender) within a specified time.

  In such an operation, if the order receiving side (sender) does not come to receive the order data, the order itself will not be established. There is a request to confirm whether data has been received.

  As a method of confirming data transmission / reception, the execution of data transmission / reception of the EDI file transfer system as disclosed in Patent Document 1 is monitored, and data transmission / reception is performed within a time set in a preset monitoring schedule. If it has not been executed, a method of delay notification to the administrator can be used. By using such a method, it is possible to confirm whether data transmission / reception has been executed as scheduled.

JP 2013-109411 A

  However, in the method of Patent Document 1, it is necessary for an administrator to manually set a monitoring schedule (notification schedule), and it can be said that the setting is complicated when the number of connections and the number of files to be transmitted and received are large.

  The present invention has been made in view of the above problems, and provides a mechanism that can easily check whether data transmission / reception has been executed as scheduled without an administrator manually setting a notification schedule. The purpose is that.

In response to such a problem, the information processing apparatus according to the present invention corresponds to the communication condition, the acquisition unit that acquires the communication time performed by the communication unit that transmits and receives data and the communication time that is performed by the communication unit Next, a storage means for storing as a communication history, a setting means for setting a communication schedule including a communication deadline time for each communication condition based on the communication history stored in the storage means, and a setting set by the setting means A notification means for notifying the user that data transmission / reception is not performed when data transmission / reception corresponding to the communication means is not performed by the communication deadline time of the communication schedule;
It is characterized by having.

  As described above, when data transmission / reception is not performed by the communication deadline time of the communication schedule set from the past communication time history, the administrator can perform data transmission / reception without any problem by notifying that effect. It can be easily confirmed whether or not it has been broken.

It is a figure which shows an example of the system configuration | structure of an EDI system. 2 is a diagram illustrating an example of a hardware configuration of a backbone system 100 and an operation management server 102. FIG. It is a flowchart explaining the flow which registers a log | history after communication processing in embodiment of this invention. It is a figure which shows the list of the communication history memorize | stored after a communication process. It is a flowchart explaining the flow which registers the communication schedule in the 1st Embodiment of this invention. (A) A setting table for setting communication history extraction conditions. (B) It is a figure which shows an example of the extracted communication history. It is a figure which shows the list of the set communication schedule. It is an example of the screen which sets extraction conditions. It is a flowchart explaining the flow which judges whether communication delay has generate | occur | produced and notifies a user that it is delaying. It is an example of the mail which notifies a user that communication delay has occurred. It is a figure which shows an example of the screen which performs default setting of an automatic notification, and the table which manages these. It is a flowchart explaining the flow which registers the communication schedule in the 2nd Embodiment of this invention. It is a setting table which sets the extraction conditions of the communication history in 2nd Embodiment. It is a flowchart for demonstrating the flow at the time of transmitting an automatic notification proposal mail. It is an example of the mail which proposes an automatic notification to a user. It is a flowchart for demonstrating the flow of a process when the link on mail is selected by the user.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a system configuration of an EDI communication system in the present embodiment.

  As shown in FIG. 1, the present invention is configured such that an EDI system 101 of its own company and an EDI system of a business partner can communicate with each other via a network 103 such as a public line, a dedicated line, or an Internet line. Through this network 103, EDI data, which is electronic information related to electronic commerce between companies, can be exchanged. Specifically, commercial transaction data such as an order form and an invoice is transmitted and received.

  The company's EDI system 101 includes a backbone system 100 for managing in-house ordering operations and an operation management server 102 for performing EDI communication, such as a network 107 such as a LAN (Local Area Network) or a WAN (Wide Area Network). Are connected to each other through data communication. Such a mechanism is the same in the EDI system 105 of the business partner.

  Since the data format used for such EDI communication is a format unique to each company, there is a situation in which the data format differs for each business partner, so a standard (hereinafter also referred to as an industry standard) is provided within the industry. In general, data is exchanged in a data format conforming to this standard.

  On the other hand, in the backbone system 100, the ordering and receiving operations are managed with data in a format different from the data format for performing EDI communication. Therefore, the operation management server 102 functions as a translator, and when the data is transmitted to the business partner using EDI communication, the operation management server 102 converts the data in the format managed by the backbone system 100 into the data of the EDI communication. Convert to format. Further, even when data is received by EDI communication, the operation management server 102 functions as a translator, and the operation management server 102 converts the data format of the EDI communication into data in a format managed by the backbone system 100. That is, the operation management server 102 mediates exchange of data between the company's backbone system 100 and the EDI system 105 of the business partner by transmitting and receiving using a communicable protocol.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of various information processing apparatuses (the basic system 100 and the operation management server 102).

  The CPU 201 comprehensively controls each device and controller connected to the system bus 204.

  Further, the ROM 202 or the external memory 211 (storage means) has a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as OS), which is a control program of the CPU 201, and functions executed by the backbone system 100 and the operation management server 102. Various programs described below necessary for realizing the above are stored. The RAM 203 functions as a main memory, work area, and the like for the CPU 201.

  The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from an input device 209 such as a keyboard or a pointing device such as a mouse (not shown).

  A video controller (VC) 206 controls display on a display device such as the display 210. The type of the display device is assumed to be a CRT or a liquid crystal display, but is not limited thereto.

  The memory controller (MC) 207 is an adapter to a hard disk (HD), flexible disk (FD) or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a card-type memory connected via the.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via a network, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the display 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example.

  Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the display 210.

  Various programs and the like used by the backbone system 100 of the present invention to execute various processes described later are recorded in the external memory 211 and are executed by the CPU 201 by being loaded into the RAM 203 as necessary. .

  Furthermore, definition files and various information tables used by the program according to the present invention are also stored in the external memory 211.

  In this embodiment, the operation management server 102 of the EDI system 101 functions as an ordering side system for placing orders, and the operation management server 102 of the business partner EDI system 105 serves as an ordering side terminal for receiving orders. This will be described using a functioning example. In such an example, the order receiving side performs communication at an arbitrary timing, and the order receiving side (the supplier EDI system 105) receives the order data prepared by the ordering side (the EDI system 101) within a specified time. Is made. In other words, the EDI system 101 that is the ordering side is a recipient who receives an incoming call, and the supplier EDI system 105 that is the order receiving side is a sender.

  In such an operation mode, the EDI system 101 side receives an incoming call from the supplier EDI system 105 by the incoming call deadline time estimated from the past performance, and easily confirms whether the ordering data is correctly received by the supplier EDI system 105 The possible mechanisms are described in detail below.

(First embodiment)
First, the flow of registering a communication history that is performed whenever file data communication is completed will be described with reference to FIGS. 3 and 4.

  FIG. 3 is a flowchart illustrating a flow of registering a history after communication processing. The processing shown in the flowchart of FIG. 3 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101. The process in FIG. 3 is performed every time the core system 100 receives communication data from the operation management server 102, and stores the communication partner, file type, and communication end time. FIG. 4 is a diagram showing a communication table that is a list of communication histories registered according to the flow of FIG.

  In step S <b> 301, the CPU 201 of the backbone system 100 determines whether communication data whose format has been converted by the operation management server 102 has been received. When the communication is completed, the process proceeds to S302. In S302, the CPU 201 of the backbone system 100 stores the connection destination No. of the connection partner that is the communication condition of the communication performed this time in the communication table as shown in FIG. And a file number indicating the communication type. Further, it is determined whether or not there is a record (identical) that matches all the communication dates and times.

  In the communication table of FIG. 401, a file No. indicating a communication type. 402, a communication date and time 403, a communication end time 404, and a notification presence / absence 405 indicating whether or not the communication at that time is delayed are stored.

  In S302, the connection destination No. 401, file no. 402. If there is a record with the same communication date and time 403, the process advances to step S303, and the CPU 201 of the backbone system 100 overwrites and saves the communication end time 404 in the communication table with the current communication end time. As a result, when communication is performed a plurality of times under the same conditions per day, the last communication time is stored in the communication table.

  In S302, the connection destination No. 401, file no. 402. If there is no record having the same communication date and time 403, the process proceeds to S304, and it is determined whether there is a delay notification history in the schedule table shown in FIG. Although details of FIG. 7 will be described later, the delay notification 705 of FIG. 7 notifies the user that data transmission / reception is delayed because file data is not transmitted / received by the communication deadline time of the communication schedule. In this case, the “1” flag is set. That is, by confirming the schedule table, it is possible to confirm whether the current notification is made at a time later than the communication deadline time (whether the communication is delayed).

  If it is determined in S304 that there is a history of delay notification, the CPU 201 of the backbone system 100 stores the connection destination No. in the communication table of FIG. 401, file no. 402, the communication date and time 403 is registered, and a flag is set in the presence / absence of notification 405.

  On the other hand, if it is determined in S304 that there is no delay notification history, the CPU 201 of the backbone system 100 stores the connection destination No. in the communication table of FIG. 401, file no. 402, the communication date 403 is registered.

  Through the processing as described above, a history is registered in the communication table every time communication ends.

  Next, communication schedule registration processing will be described with reference to FIGS.

  FIG. 5 is a flowchart for explaining a flow for registering a communication schedule. The processing shown in the flowchart of FIG. 5 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101. This process is a process that is performed at the daily change timing (when the communication process for one day is completed).

  The processing in FIG. 5 is repeatedly performed for the registration conditions set in the setting table (extraction condition storage means) in FIG. In the setting table of FIG. 601, file no. 602, outgoing / incoming 603, transmission / reception 604, automatic notification function 605 indicating whether or not to automatically notify delay, number of days 606 used when setting schedule, communication pattern 607, threshold 608, buffer time 609 are set Has been.

  In step S501, the CPU 201 of the backbone system 100 refers to the setting table and determines whether the target file automatic notification function 605 is ON. If it is OFF, the schedule registration is not performed and the process proceeds to determination of the next registration condition.

  If the automatic notification function 605 of the target file is ON in S501, the process proceeds to S502, and the CPU 201 of the backbone system 100 sets the usage days 606, the communication pattern 607, the automatic notification threshold 608, and the buffer time 609 from the setting table. get.

  In S <b> 503, the CPU 201 of the backbone system 100 determines the registration conditions and connection destination No. of the setting table from the communication table shown in FIG. 4. , File No. Are matched, and the number of records set in the usage days 606 are extracted. Specifically, when “Monthly” is set in the communication pattern 606 and the number of days of use is set as 3 days, records for the last four months are extracted, and “Weekly” is extracted in the communication pattern 607. If “Next” is set and the number of days used is set to 4 days, the records for the last 4 weeks are extracted, “Daily” is set in the communication pattern 607, and the number of days used is 4 days. If it is set, records for the last four days are extracted. If the usage days 606 are not set, it may be specified from all records stored in the communication table shown in FIG. 4 or may be specified for a predetermined date. Good.

  In step S504, the CPU 201 of the core system 100 determines the ratio of available records (number of records that can be used / number of days to use 606, that is, the number of records that can be used for setting the communication deadline time, as defined in the extraction condition. It is determined whether the ratio to the threshold value is equal to or greater than a threshold value (a predetermined value or greater). Here, the record that can be used is a record that has been communicated by the communication deadline, and excludes records that have not been communicated in the first place and are not extracted, or records that have been delayed due to communication and have a delay flag. The

  If it is determined in S504 that the percentage of records that can be used is less than the threshold, that is, if there are few records that can be used for schedule registration, the reliability of the scheduled communication deadline cannot be ensured. The process proceeds to determination of the next registration condition without performing registration.

  If the ratio of no delay in S504 is equal to or greater than the threshold, it can be said that the reliability of the scheduled communication deadline time is high, and the process proceeds to S505. In S505, the CPU 201 of the backbone system 100 calculates an average time from the communication end time of the extracted record with no delay in the communication table.

  In S506, the CPU 201 of the backbone system 100 calculates the schedule setting time by adding the buffer time 609 of the setting table to the average time calculated in S505.

  In S507, the CPU 201 of the backbone system 100 registers the schedule in the schedule table shown in FIG. 7 as the communication deadline time calculated in S506. The schedule table of FIG. 7 includes a communication date 701, a communication deadline time 702, a connection destination No. 703, file no. 704 and a delay notification 705 are provided so that they can be registered. Specifically, when “monthly” is set in the communication pattern 607, the date after January when the next communication is performed is registered as the communication date 701, and the schedule setting calculated in S506 is performed. The time is registered as the communication deadline time 702. If there is no date corresponding to the month after January, if there is no day after January, a schedule is set on the day before or after the day. If “weekly” is set in the communication pattern 607, the date one week after the next communication is registered as the communication date 701, and the schedule setting time calculated in S506 is the communication time. The deadline time 702 is registered. If “daily” is set in the communication pattern 607, the date of the next day when communication is performed next is registered as the communication date 701, and the schedule set time calculated in S506 is the communication time. The deadline time 702 is registered.

  Next, the process performed in FIG. 5 will be specifically described using an example. The following is an example of processing performed at the daily change timing on June 23, 2014. The connection destination No. in FIG. 1 for file no. In the case of the registration condition of 1, since the usage days 606 are registered as 4 and the communication pattern 607 is registered as “weekly”, records for the latest 4 weeks are extracted from the communication table shown in FIG. 4 (S503). . An example of the extracted record is shown in FIG.

  Since it can be confirmed from the absence of flag in the notification presence / absence 615 that there is no delayed notification in the extracted records, it is determined that these four records are usable records. Since “number of available records (4) / number of days used (4) = 100%” is 75% or more stored in the threshold 608, it can be said that the schedule can be registered (S504).

  Then, the average time of 15:15 minutes is calculated from the communication end times 614 of the four available records (S505). By adding 60 minutes registered as the buffer time 609 to this average time, the connection destination No. 1 for file no. The schedule setting time of 1 is 16:15 (S506).

And the connection destination No. 1 for file no. Since “1” is “weekly” processing, the next communication is “June 30, 2014”. 1 for file no. 1, June 30, 2014 is registered as the communication date 701, and 16:15 is registered as the communication deadline time 702.
In this flowchart, the average time of the communication end times of all records without delay in the communication table is used as the schedule setting time. Among these records without delay, a record with little variation is specified and specified. You may schedule using the average time of a record. By excluding data that varies in this way, the accuracy of the set time can be increased. Specifically, the time range that identifies records with little variation is, for example, μ ± σ (μ: average, σ: standard deviation) using the average time and standard deviation of the extracted data, and records that fall within this range The set time may be determined using the average time.

  In the example of FIG. 6B, since μ = 15: 15 and σ = 0: 15, the time range is 15:00 to 15:30, which is the average time of all four extracted records. : 15 is the set time.

  In the example of FIG. 6C, μ = 15: 22 and σ = 0: 25, so the time range is 14:57 to 15.47, and the communication end time of 2014/6/16 is out of the acquisition range. It becomes. Therefore, the set time is 15:10, which is the average time of three records other than the record.

  In the example of FIG. 6D, the notification presence / absence 615 column of 2014/6/16 is “1”, a delay occurs in communication of this record, and a delay notification described later is performed. Show. In this case, since μ = 15: 08 and σ = 0: 06 from the other three, the acquisition range is 15.02 to 15.14, 2014/6/2 and 2014/6/23. 15:12 from this record is the set time.

  FIG. 8 shows an example of a screen 800 used when the user sets a setting table as shown in FIG. The user can register the registration condition in the setting table using such a screen 800, and the user can specify the target connection destination and the file and perform it appropriately.

  The screen 800 includes a check field 801 for automatic notification of a target connection destination / file, a communication pattern selection field 802, a usage days input field 803, a buffer time input field 804, and a threshold value input field. 805 is provided, and the user can make settings by inputting into each column and pressing an OK button 806. The communication pattern selection field 802 is provided so that one of “monthly”, “weekly”, and “daily” can be selected as a communication pattern. In the present embodiment, the above three types of communication patterns have been described as examples. However, other communication patterns may be employed.

  Note that the number of days used, buffer time, and threshold do not need to be set for each connection destination / file. If not set, the number of days used, buffer time, and threshold set in advance as default automatic notification conditions are used. Can be used. An example of a screen 1100 used for such default automatic notification condition setting is shown in FIG. The user can set a default automatic notification condition using such a screen 800 in advance, and such data includes the number of use days 1112, the threshold 1110, and the buffer time 1111 as shown in FIG. Are managed as a default setting table. That is, if the number of days used, the buffer time, and the threshold are not set in the setting table, the number of days used, the buffer time, and the threshold are acquired from the default setting table in S502, and this value is determined in S504 and the average time is calculated in S505. Can be used for processing.

  Next, with reference to FIGS. 9 and 10, a delay notification to the user that is performed when it is determined that the delay has occurred will be described.

  FIG. 9 is a flowchart for explaining the flow of determining whether a communication delay has occurred and notifying the user of the delay. The processing shown in the flowchart of FIG. 9 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101. This process is a process that is always performed (every minute).

  In step S901, the CPU 201 of the backbone system 100 determines whether the current date and time match the communication date 701 and the communication deadline time 702 in the schedule table of FIG. If it does not match the communication date 701 and the communication deadline time 702, the process is terminated. If they match, the process moves to S902. If there are a plurality of schedules in which the communication date 701 and the communication deadline time 702 coincide in S901, the processes in S902 to S904 are repeated.

  In S902, the CPU 201 of the backbone system 100 determines the connection destination No. of the record matched in S901. And file No. Is used as a key to search the communication table shown in FIG. And file No. It is determined whether or not communication with the same is performed today. In the communication table, the connection destination No. And file No. If it is determined that there is communication with equal, the communication has already been performed and there is no need to make a delay notification, so the processing ends.

  On the other hand, if there is no target file in S902 and communication is not performed today, it can be said that communication has not been performed by the communication deadline time, so that the process proceeds to S903 to perform delay notification.

  The delay notification to the user performed in S903 is performed by displaying on the desktop screen as an email notification or event log.

  FIG. 10 shows an example of the mail text 1000 used when notifying the user of such a notification delay. The core system 100 becomes the sender 1001, and an email in which notification information 1003 such as a communication destination, file type, scheduled notification time, etc. is transmitted to the user, so that the user can communicate by the communication deadline time. You will be notified that it was not done.

  In S904, the CPU 201 of the backbone system 100 registers a flag indicating that a notification has been made in the delay notification 705 field of the schedule table of the corresponding record, and ends the process. By registering in this way, it is determined that there is a history of delay in S304 of the flowchart shown in FIG. 3 when communication is performed after the communication deadline time has passed, and the communication is delayed to the notification table. It can be memorized that it was done.

  As described above, a communication table is created as a history of past communication end times, a communication schedule is set based on the contents of the communication table and the setting table, and data transmission / reception is performed by the communication deadline time of this communication schedule. If not, the manager can easily confirm whether or not the data has been transmitted and received by notifying the fact.

  In addition, although the case where each process in this embodiment is performed in the main system 100 was demonstrated to the example, it is not restricted to this, You may perform by the operation management server 102, or may be performed separately.

  Furthermore, in the present embodiment, the contractor (sender) executes communication at an arbitrary timing, and the orderer (sender) receives the order data prepared by the orderer (sender) within a specified time. That is, the timing of incoming calls has been described as an example. Similarly, the timing of outgoing calls is also indicated when data is not sent before the communication deadline of the communication schedule set from the history of past communication times. A similar effect can be obtained by providing the notification.

(Second Embodiment)
In the first embodiment, an example has been described in which the processing ends when the automatic notification function is not set. However, in the present embodiment, when the automatic notification function is not set, automatic notification is performed. An example to be proposed to the user will be described.

  The present embodiment will be described with a focus on differences from the first embodiment, and the description of the same parts as the first embodiment such as a flow of registering a history after communication processing will be omitted.

A communication schedule registration process and a process for proposing an automatic notification to a user will be described with reference to FIGS.
FIG. 12 is a flowchart illustrating a flow for registering a communication schedule. The processing shown in the flowchart of FIG. 12 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101. This process is a process that is performed at the daily change timing (when the communication process for one day is completed).

  The processing in FIG. 12 is repeated for the registration conditions set in the setting table (extraction condition storage means) in FIG. In the setting table of FIG. 601, file no. 602, outgoing / incoming 603, transmission / reception 604, automatic notification function 605 indicating whether notification of delay is automatically performed, use days 606 used when setting a schedule, communication pattern 607, threshold 608, buffer time 609, automatic A notification unnecessary setting 1301 is set.

  The processes in S501 through S507 in FIG. 12 are the same as those in FIG. In step S1201, the CPU 201 of the backbone system 100 refers to the setting table and determines whether or not the automatic notification unnecessary setting of the target file is set to be unnecessary.

  If it is set to be unnecessary in S1201, it is already determined that the movement notification is not required in response to the notification proposal from the user, which will be described later, and thus the process is terminated without performing the automatic notification proposal again.

  On the other hand, if it is not set as unnecessary in S1201, the process proceeds to S1202 and an automatic notification proposal process is performed. Details of S1202 will be described with reference to the flowchart of FIG.

  FIG. 14 is a flowchart for explaining a flow when an automatic notification proposal mail is transmitted as the automatic notification proposal processing. The processing shown in the flowchart of FIG. 14 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101.

  In S1401, the CPU 201 of the backbone system 100 reads the current target record and the connection destination No. from the communication table that is a list of communication histories. And file No. Among the records that match, the records with date 403 up to three months before the processing date are extracted.

  In S1402, the CPU 201 of the backbone system 100 determines whether the communication pattern is “monthly” based on the extracted record. Specifically, if the date of the last three records among the extracted records is a specific date, it is determined as “monthly” and the process proceeds to S1405. Otherwise, “monthly” If not, the process proceeds to S1403.

  Next, in S1403, the CPU 201 of the backbone system 100 determines whether it is “daily”. Specifically, if the year, month, day interval of the last 10 consecutive records among the extracted records is “1”, it is determined as “daily” and the process proceeds to S1405. Is not “daily”, the process proceeds to S1405.

  In step S1405, the CPU 201 of the backbone system 100 determines whether the communication pattern is “weekly” based on the extracted record. Specifically, among the extracted records, a record whose date falls on Sunday is extracted, and when the date interval is “7”, it is determined that it is “weekly” on Sunday. . Similarly, the determination is also made on Monday to Saturday, and if any one of Sunday to Saturday is determined to be “weekly”, the communication pattern is determined to be “weekly” and the process proceeds to S1405. If it is determined that it is not “weekly”, the process is terminated because the communication is not performed regularly.

  In S1405, the CPU 201 of the backbone system 100 transmits a mail as shown in FIG. 15B that proposes to notify the user of the communication pattern specified in S1402, S1403, and S1404 and to set automatic notification.

  Next, the process performed in FIG. 13 will be specifically described using an example. The following is an example of processing performed at the daily change timing on June 23, 2014. In FIG. 1 for file no. In the case of the registration condition 1, the automatic notification function 605 is OFF and the automatic notification unnecessary setting 1301 is not set. In step S1401, the communication table shown in FIG. 1 for file no. Extract one record. An example of the extracted record is shown in FIG. In this case, since 2014/6/2, 2014/6/9, 2014/6/16, and 2014/6/23 are Mondays and the interval is “7”, it is determined to be “weekly” on Monday. The communication pattern is “weekly”. FIG. 15B shows an example of the mail text 1500 transmitted at this time. Whether the main system 100 becomes the sender 1501 and notifies the user of which communication pattern the connection destination name and file No. are determined 1502 and whether to set automatic notification with the communication pattern You can set whether or not. Specifically, a “Yes” link 1503 for setting automatic notification with a communication pattern, a setting link 1504 for setting with a communication pattern different from the determined communication pattern, and setting that delay notification is unnecessary “ A “delay notification unnecessary” link 1505 is provided in the mail. By selecting a link on the mail, the user can easily update the setting table and set the automatic notification function to ON.

  FIG. 16 is a flowchart for explaining the flow of processing when a link in the mail text 1500 is selected by the user. The process shown in the flowchart of FIG. 16 is realized by reading and executing a control program stored in the CPU 201 of the backbone system 100 of the EDI system 101.

  In step S <b> 1601, the CPU 201 of the backbone system 100 determines whether a link has been selected and notified by the user in the mail text 1500. If notified, the process proceeds to S1602, and it is determined which of the notification contents is.

  If the user selects the “Yes” link 1503 on the mail, the process advances to step S1603 to update the setting table in FIG. 13A using the automatically determined conditions. Specifically, the automatic notification function 605 is turned on, and the communication pattern 607 is registered under automatically determined conditions. Note that regarding the use days 606, the threshold 608, and the buffer time 609, default values may be set from a default setting table as shown in FIG.

  If the setting link 1504 on the mail is selected by the user, the process advances to step S1604 to update the setting table in FIG. 13A using the communication pattern specified by the user. Specifically, the automatic notification function 605 is turned on, and the communication pattern 607 is registered with the communication pattern designated by the user. Note that regarding the use days 606, the threshold 608, and the buffer time 609, default values may be set from a default setting table as shown in FIG.

  If the “delay notification unnecessary” link 1505 on the mail is selected by the user, the process advances to step S1605 to update the setting table shown in FIG. Specifically, the column of the automatic notification unnecessary setting 1301 in FIG. 13A is set to “1”, and it is updated that automatic notification is unnecessary. By making automatic notification unnecessary in this way, it is possible to prevent the automatic notification proposal mail from being sent again.

  13B is an example of a setting table updated when the user selects the “Yes” link 1503 on the mail text shown in FIG. 1 for file no. The automatic registration function 605 for the registration condition 1 is “ON”, the communication pattern is “weekly”, the number of use days 606, the threshold 608, and the buffer time 609 are acquired from the default setting table shown in FIG. Default value is set. As a result, the subsequent connection destination No. 1 for file no. In the case of 1 automatic notification setting, the setting is performed under the condition.

  In the present embodiment, an example in which the setting can be made from the link of the e-mail has been described. However, the setting table may be changed by replying with a content that can specify any one in the e-mail text.

  The present invention can be implemented as a system, apparatus, method, program, storage medium, or the like, and can be applied to a system including a plurality of devices. You may apply to the apparatus which consists of one apparatus.

  Note that the present invention includes a software program that implements the functions of the above-described embodiments directly or remotely from a system or apparatus. The present invention also includes a case where the information processing apparatus of the system or apparatus is achieved by reading and executing the supplied program code.

  Therefore, the program code itself installed in the information processing apparatus in order to realize the functional processing of the present invention with the information processing apparatus also realizes the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. In addition, there are magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R), and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded from the homepage by downloading it to a recording medium such as a hard disk.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, the present invention also includes a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention with an information processing apparatus.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let The downloaded key information can be used to execute the encrypted program and install it in the information processing apparatus.

  Further, the functions of the above-described embodiment are realized by the information processing apparatus executing the read program. In addition, based on the instructions of the program, the OS or the like operating on the information processing apparatus performs part or all of the actual processing, and the functions of the above-described embodiments can be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the information processing apparatus or a function expansion unit connected to the information processing apparatus. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  Note that the above-described embodiments are merely examples of implementation in carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

100 Core System 101 EDI System 102 Operation Management Server 103 Network 105 Customer EDI System 107 Network

Claims (9)

An acquisition means for acquiring a communication time performed by a communication means for transmitting and receiving data;
Storage means for storing the communication time performed by the communication means as a communication history in association with communication conditions;
Based on the communication history stored in the storage means, setting means for setting a communication schedule including a communication deadline time for each communication condition;
Notification notifying the user that data transmission / reception is not performed when data corresponding to the communication condition is not transmitted / received by the communication unit by the communication deadline time of the communication schedule set by the setting unit Means,
An information processing apparatus comprising:   The said setting means extracts the some communication time corresponding to a communication condition from the said memory | storage means, The communication deadline time is set based on the said some extracted communication time. Information processing device. The storage means also stores a delay as the communication history when communication is performed after the communication deadline time set by the setting means,
The said setting means sets communication deadline time using the communication time except for what was memorize | stored in the said memory | storage means among the several communication times extracted from the said memory | storage means. 2. The information processing apparatus according to 2.   The setting means sets the communication deadline time when the ratio of the number of records that can be used for setting the communication deadline time to the number determined by the extraction condition is equal to or greater than a predetermined value. The information processing apparatus according to claim 3. For each communication condition, it further has an extraction condition storage means for storing an extraction condition for extracting a communication time from the storage means,
The setting unit specifies a plurality of communication times to be extracted from the storage unit based on the extraction condition stored in the extraction condition storage unit, and sets a communication deadline time based on the plurality of communication times. The information processing apparatus according to claim 2, wherein the information processing apparatus is an information processing apparatus.   The information processing apparatus according to claim 1, wherein the communication unit is an EDI communication unit. Information processing comprising: an acquisition unit that acquires a communication time performed by a communication unit that transmits and receives data; and a storage unit that stores the communication time performed by the communication unit as a communication history in association with a communication condition An apparatus control method comprising:
Based on the communication history stored in the storage means, a setting step for setting a communication schedule including a communication deadline time for each communication condition;
Notification notifying the user that data transmission / reception is not performed when data corresponding to the communication condition is not transmitted / received by the communication means by the communication deadline time of the communication schedule set in the setting step Process,
A control method characterized by comprising: Information including: an acquisition unit that acquires a communication time performed by a communication unit that transmits and receives data; and a storage unit that stores the communication time performed by the communication unit as a communication history in association with a communication condition. A program that can be installed in a processing device,
The information processing apparatus;
Setting means for setting a communication schedule including a communication time limit for each communication condition based on the communication history stored in the storage means;
Notification notifying the user that data transmission / reception is not performed when data corresponding to the communication condition is not transmitted / received by the communication unit by the communication deadline time of the communication schedule set by the setting unit means,
A program characterized by functioning as A communication means for transmitting and receiving data;
Storage means for storing the communication time performed by the communication means as a communication history in association with communication conditions;
Based on the communication history stored in the storage means, setting means for setting a communication schedule including a communication deadline time for each communication condition;
Notification notifying the user that data transmission / reception is not performed when data corresponding to the communication condition is not transmitted / received by the communication unit by the communication deadline time of the communication schedule set by the setting unit Means,
A communication system comprising:

Images