JP6601255B2 - Meeting material distribution system and program thereof - Google Patents

Description

  The present invention relates to a conference material distribution system and a program thereof.

  2. Description of the Related Art Conventionally, a conference material distribution system has been developed that distributes digital data (hereinafter referred to as “original data”) of materials used in a conference or the like to prospective participants (for example, Patent Document 1).

  Normally, the manuscript data is managed by a management device or the like serving as the main body of the conference material distribution system, and may be updated (revision, addition of new manuscript data, etc.) as necessary.

  When the original data is distributed (including notification of the storage location), the prospective participant can print it at an appropriate timing and read it in advance.

JP 2014-109811 A

  However, depending on the prospective participant, the document data may be printed at home or on a business trip separated from the network (for example, in-house LAN) to which the document data is distributed. At this time, even if the manuscript data managed by the management device or the like is updated, it is difficult for the prospective participant to easily confirm whether or not the manuscript data is updated. For this reason, the prospective participant may participate in the conference with anxiety that the manuscript data printed at home or on a business trip may not be the latest version.

  The present invention has been made in view of the above circumstances. That is, it is an object of the present invention to provide a conference material distribution system or the like that can easily check whether or not document data is updated even when the document data is printed in an environment separated from the network to which the document data is distributed. To do.

  (1) A conference in which a portable information terminal used by a prospective participant of a conference and a management device that manages manuscript data of conference materials used in the conference are communicably connected via a predetermined network. In the document distribution system, the information terminal receives a meeting opening notice including meeting information capable of specifying the meeting and the manuscript data, and manages the meeting holding notice for managing the meeting information and the manuscript data in association with each other. A print management unit for instructing printing based on the document data managed by the meeting holding notification management unit and storing a print history of the document data in a state where the connection is released from the network; It is confirmed whether or not the document data corresponding to the printed document data printed based on the instruction of the print management unit has been updated in the management device. Therefore, a confirmation request unit that transmits the print history to the management apparatus in a state of being connected to the network, and the management apparatus receives the meeting opening notification and includes the meeting included in the meeting opening notification Information and the document data are registered in association with each other, and the document data management unit that updates the document data in response to the request, the print history transmitted from the confirmation request unit, and the document data management unit registered An update confirmation unit that analyzes the conference information and the document data and confirms whether document data corresponding to the printed document data has been updated by the document data management unit, and a confirmation result by the update confirmation unit And a result notifying unit for notifying the information terminal of the conference material distribution system.

  (2) To update the document data by the document data management unit, add document data that is newer than the previously registered document data, and add another document data related to the previously registered document data. The meeting material distribution system according to (1), wherein at least one of the above is included.

  (3) The print history includes version information about the printed document data, and the update confirmation unit performs the version information included in the print history and the document data management unit. The meeting according to (2) above, wherein the version information preliminarily added to the registered or updated document data is compared to confirm whether or not document data newer than previously registered document data is added. Document distribution system.

  (4) When the print management unit displays the confirmation result notified from the result notification unit and receives an instruction to execute printing based on the document data updated by the document data management unit, Instructing the management apparatus to perform printing based on the updated document data, and the management apparatus includes a print control unit that causes the image forming apparatus connected to the network to execute printing based on an instruction from the print management unit. (1) The conference material distribution system according to any one of (3).

  (5) When the print management unit displays the confirmation result notified from the result notification unit and receives an instruction to execute printing based on the document data updated by the document data management unit, A print execution unit that instructs the management device to perform printing based on the updated document data, and the management device is incorporated in the image forming apparatus connected to the network and executes printing based on the instruction of the print management unit A conference material distribution system according to any one of (1) to (3), comprising:

  (6) The print management unit determines whether or not the printed document data is the document data of the conference material after the instructed printing is normally completed. The conference material distribution system according to any one of the above (1) to (5), which stores a print history of data.

  (7) The meeting according to (6), wherein the print management unit determines that the document data instructed to be printed in a state in which the meeting opening notification is opened by a specific application is the document data of the meeting material. Document distribution system.

  (8) The conference according to (6), wherein the print management unit determines that the document data stored and managed in a predetermined folder by the conference holding notification management unit is the document data of the conference material. Document distribution system.

  (9) The print management unit according to any one of (1) to (8), wherein the print history of original data before update of original data printed with the information terminal connected to the network is deleted. The conference material distribution system described.

  (10) The conference information includes a conference start time or a conference end time, and the print management unit acquires a current time, and the current time has passed the conference start time or the conference end time. The conference material distribution system according to any one of (1) to (9), wherein the print history is deleted.

  (11) The conference material distribution system according to (3), wherein the print management unit refers to the version information of the document data used in the same conference and deletes a print history other than the latest print history.

  (12) The print management unit stores a print history for each document data, and the confirmation request unit displays a plurality of print histories stored by the print management unit, and selects at least one print history. The meeting material distribution system according to any one of (1) to (11), wherein only the received print history that has been received and selected is transmitted to the management device.

  (13) The print history includes reception date / time information indicating a date / time when a meeting holding notification including the printed document data is received, and the update confirmation unit is included in the print history. The received date and time information is compared with the date and time information of the meeting holding notification that contained the document data registered or updated by the document data management unit, and the document data that is newer than the previously registered document data The conference material distribution system according to (2), wherein whether or not is added is confirmed.

  (14) The conference material distribution system according to (4) or (5), wherein the result notification unit notifies the information terminal of a print result when printing based on an instruction from the print management unit is executed.

  (15) The notification of the confirmation result includes a notification that the original data is not updated by the original data management unit and thus printing is not necessary, and any of the above (1) to (14) The conference material distribution system described.

  (16) The conference material distribution system according to any one of (1) to (15), wherein the notification of the confirmation result includes a notification that the conference information or the document data is not registered.

  (17) The print management unit deletes the printed document data, and stores the meeting information associated with the document data and information previously attached to the document data as the print history. The conference material distribution system according to any one of (1) to (12) above.

  (18) A conference in which a portable information terminal used by a prospective participant of a conference and a management device that manages manuscript data of conference materials used in the conference are communicably connected via a predetermined network. In the document distribution system, the information terminal receives a meeting opening notice including meeting information capable of specifying the meeting and the manuscript data, and manages the meeting holding notice for managing the meeting information and the manuscript data in association with each other. A print management unit for instructing printing based on the document data managed by the meeting holding notification management unit and storing a print history of the document data in a state where the connection is released from the network; Check whether or not document data corresponding to printed document data printed based on an instruction from the print management unit has been updated in the management device And a confirmation request unit that transmits the print history to the management device in a state of being connected to the network, and the management device receives the conference opening notification and is included in the conference opening notification. The document information is registered in association with the conference information and the document data, and the document data management unit updates the document data in response to the request, the print history transmitted from the confirmation request unit, and the document data management unit. The meeting information and the document data are analyzed, and an update confirmation unit that confirms whether or not the document data corresponding to the printed document data has been updated by the document data management unit, and updated by the update confirmation unit A conference material distribution system comprising: a print control unit that causes the image forming apparatus connected to the network to execute printing based on the document data for which the document has been confirmed. Temu.

  (19) The meeting material distribution system according to (18), further including a result notification unit that notifies the information terminal of the confirmation result by the update confirmation unit and the printing result after the printing is completed.

  (20) A program for causing a computer to function as the conference material distribution system according to any one of (1) to (19).

  According to the present invention, when the document data is printed in an environment separated from the network to which the document data is distributed, the print history is stored in the information terminal. Therefore, even if the document data managed by the management apparatus is updated later, the update can be easily confirmed using the print history. If necessary, the prospective participant can print the latest updated version of the manuscript data and participate in the conference.

It is a schematic block diagram of a meeting material delivery system. It is a block diagram which shows the hardware structural example of a management apparatus. It is a block diagram which shows the hardware structural example of participant PC. It is a block diagram which shows the function structural example of a management apparatus. It is a block diagram which shows the function structural example of participant PC. It is a flowchart of the reception process of a meeting holding notification. It is a figure for demonstrating the operation | movement of a meeting holding notification. It is a figure which shows the example of a display of a meeting holding notification. It is a figure which shows the schematic data structure of management data. It is a flowchart of the registration process of a meeting holding notification. It is a figure which shows the schematic data structure of registration data. It is a flowchart of a printing process. It is a figure for demonstrating the operation | movement of a printing process. It is a flowchart of a printing history management process. It is a figure which shows the schematic data structure of printing log | history data. It is a flowchart of an update confirmation request process. 6 is a diagram illustrating a display example of a print history. FIG. It is a figure for demonstrating operation | movement of a confirmation request | requirement. It is a figure for demonstrating operation | movement of a confirmation result notification. FIG. 6 is a diagram for explaining a printing operation based on the latest version of document data. It is a flowchart of an update confirmation process. It is a figure for demonstrating the operation | movement of update confirmation. It is a flowchart of a history deletion process. It is a figure for demonstrating the modification of a meeting material delivery system.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted. In addition, the dimensional ratios in the drawings are exaggerated for convenience of explanation, and may be different from the actual ratios.

[Meeting Material Distribution System 10]
FIG. 1 is a schematic configuration diagram of a conference material distribution system 10.

(1-1) Overall Configuration As shown in FIG. 1, the conference material distribution system 10 includes an organizer PC (Personal Computer) 100, a management device 200, an image forming device 300, and a participant PC 400.

  In the present embodiment, each device (100, 200, 300, 400) is connected to be communicable with each other via a predetermined computer network (hereinafter simply referred to as “network A”) built in a company or the like. The For the network A, a LAN (Local Area Network) or the like is used regardless of wired or wireless.

  Further, the printing apparatus 500 is placed in an environment (for example, a home or a business trip destination) separated from the network A, and is connected to a participant PC 400 brought in from a company or the like so as to be communicable.

(1-2) Organizer PC100
The organizer PC 100 is an information processing apparatus used by the organizer of a conference held in a company or the like. The organizer PC 100 may be a desktop PC or a portable information terminal.

  The organizer PC 100 is used to create digital data (that is, “original data”) of material used in the conference (hereinafter, sometimes simply referred to as “meeting material”). The created manuscript data is distributed from the organizer PC 100 to the management device 200 and the participant PC 400 via the network A. The document data includes digital data in various formats (for example, word files, PDF files, etc.) that can be browsed and printed.

(1-3) Management device 200
The management device 200 is a server device that manages document data. Therefore, the management device 200 can be realized by a general computer device.

  The management apparatus 200 registers (accumulates) the document data distributed from the organizer PC 100 and stores it until the meeting using the document data starts or ends. In addition, the management apparatus 200 accepts update of document data (revision, addition of new document data, etc.) as necessary. Then, in response to a request from the participant PC 400 (“confirmation request” to be described later), the management apparatus 200 confirms whether or not the document data has been updated, and notifies the participant PC 400 of the confirmation result.

(1-4) Image forming apparatus 300
The image forming apparatus 300 is a printer having at least a printing function, a multifunction machine, or the like. Although only one image forming apparatus 300 is shown in FIG. 1, a plurality of image forming apparatuses 300 may be connected to the network A.

  The image forming apparatus 300 executes printing based on the document data in response to a request from the participant PC 400. As a result, the printed material corresponding to the conference material is output from the image forming apparatus 300.

(1-5) Participant PC 400
Participant PC 400 is a portable information terminal used by those who plan to participate in the conference. Therefore, the participant PC 400 is a mobile computer represented by a notebook computer, a tablet terminal, a smartphone, or the like. Although only one participant PC 400 is shown in FIG. 1, a plurality of participant PCs 400 may be connected to the network A.

  Participant PC 400 is not limited to use in a state where it is connected to network A, but can also be used in an environment disconnected from network A. For example, when a busy participant is unable to print the manuscript data distributed from the organizer PC 100 within the company (connected to the network A), the participant PC 400 is taken home to the home and the environment is separated from the network A. The document data can be printed. In addition, the participant PC 400 can make a request for confirmation as to whether or not the manuscript data managed by the management apparatus 200 has been updated.

(1-6) Printing apparatus 500
The printing apparatus 500 is a printer, a multifunction machine, or the like that has at least a printing function. The printing apparatus 500 performs printing in response to a request from the participant PC 400 that a prospective participant of the conference has taken home.

  Next, the hardware configuration of the management apparatus 200 and the participant PC 400, which are main apparatuses of the conference material distribution system 10, will be described.

(2-1) Management device 200 (hardware configuration)
FIG. 2 is a block diagram illustrating a hardware configuration example of the management apparatus 200.

  As shown in FIG. 2, the management device 200 has a control unit 210 and a communication unit 220, which are connected to each other via a signal line (bus or the like) 230 for exchanging signals.

  The control unit 210 controls the entire management apparatus 200. For example, the control unit 210 includes a CPU 211, a memory 212, and a storage 213.

  The CPU 211 is a control circuit composed of a multi-core processor or the like that executes control of each unit and various arithmetic processes according to a program. Each function of the management device 200 is executed by the CPU 211 executing a corresponding program. Demonstrated.

  The memory 212 is a high-speed accessible main storage device that temporarily stores programs and data as a work area. As the memory 212, for example, a DRAM (Dynamic Random Access Memory), an SDRAM (Synchronous Dynamic Access Memory), an SRAM (Static Random Access Memory), or the like is employed.

  The storage 213 is a large-capacity auxiliary storage device that stores various programs including an operating system and various data. For the storage 213, for example, a hard disk, a solid state drive, a flash memory, a ROM, or the like is employed.

  The communication unit 220 is an interface for communicating with the organizer PC 100, the image forming apparatus 300, and the participant PC 400 via the network A.

(2-2) Participant PC 400 (hardware configuration)
FIG. 3 is a block diagram illustrating a hardware configuration example of the participant PC 400.

  As shown in FIG. 3, the participant PC 400 includes a control unit 410, a display unit 420, an input unit 430, and a communication unit 440, which have signal lines (such as a bus) 450 for exchanging signals. Are connected to each other.

  The control unit 410 controls the entire participant PC 400. For example, the control unit 410 includes a CPU 411, a memory 412, and a storage 413. Since the CPU 411, the memory 412, and the storage 413 can be realized by the same configuration as that of the management apparatus 200, description thereof will be omitted.

  The display unit 420 displays various data such as information necessary for operating the participant PC 400 and setting information. As the display unit 420, for example, a liquid crystal display, an organic EL (Electro-Luminescence), or the like is employed.

  The input unit 430 inputs various data according to an instruction from a conference participant. For the input unit 430, for example, a pointing device such as a keyboard or a touch pad is employed.

  The communication unit 440 is an interface for communicating with the organizer PC 100, the management apparatus 200, and the image forming apparatus 300 via the network A.

  Next, functional configurations of the management apparatus 200 and the participant PC 400, which are main apparatuses of the conference material distribution system 10, will be described.

(3-1) Management device 200 (functional configuration)
FIG. 4 is a block diagram illustrating a functional configuration example of the management apparatus 200.

  As shown in FIG. 4, the control unit 210 of the management apparatus 200 includes a document data management unit 610, an update confirmation unit 620, a result notification unit 630, and a print control unit 640.

  The manuscript data management unit 610 receives a meeting holding notification from the organizer PC 100. The meeting holding notification includes meeting information that can identify a meeting scheduled to be held, and digital data (that is, “original data”) of meeting materials used in the meeting. The manuscript data management unit 610 registers the meeting information and manuscript data included in the received meeting holding notice in association with each other, and updates the manuscript data in response to a request from the organizer (host PC 100 or the like). The registered and updated conference information and document data are stored in the storage 213.

  To update the document data, at least one of adding a newer version of the document data than the previously registered document data and adding another document data related to the previously registered document data. included.

  In response to a request (confirmation request) from the participant PC 400, the update confirmation unit 620 receives document data corresponding to document data that has been printed in an environment disconnected from the network A by the document data management unit 610 in the management apparatus 200. Check if it has been updated.

  The result notification unit 630 notifies the confirmation result by the update confirmation unit 620 to the participant PC 400.

  The print control unit 640 causes the image forming apparatus 300 connected to the network A to execute printing based on an instruction from the participant PC 400.

  The document data management unit 610, the update confirmation unit 620, the result notification unit 630, and the print control unit 640 are each realized by the CPU 211 reading the program installed in the storage 213 into the memory 212 and executing it. The However, the present invention is not limited to this, and hardware such as ASIC may be used.

(3-2) Participant PC 400 (functional configuration)
FIG. 5 is a block diagram illustrating a functional configuration example of the participant PC 400.

  The control unit 410 of the participant PC 400 includes a conference opening notification management unit 710, a print management unit 720, and a confirmation request unit 730, as shown in FIG.

  The meeting holding notification management unit 710 receives a meeting holding notice from the organizer PC 100 and manages the meeting information and the manuscript data included in the meeting holding notice in association with each other. The managed conference information and document data are stored in the storage 413.

  The print management unit 720 instructs printing based on the document data managed by the meeting holding notification management unit 710 in a state where the participant PC 400 is disconnected from the network A, and stores the print history of the document data. To do.

  The confirmation request unit 730 is connected to the network A in order to confirm whether or not the document data corresponding to the printed document data printed based on the instruction of the print management unit 720 has been updated in the management apparatus 200. The print history is transmitted to the management apparatus 200.

  Note that the conference holding notification management unit 710, the print management unit 720, and the confirmation request unit 730 are realized by the CPU 411 reading out the program installed in the storage 413 to the memory 412 and executing it. However, the present invention is not limited to this, and hardware such as ASIC may be used.

[Operation of Meeting Material Distribution System 10]
Next, a characteristic operation of the conference material distribution system 10 according to the present embodiment will be described.

(1) Conference Holding Notification Acceptance Processing FIG. 6 is a flowchart of conference holding notification reception processing. FIG. 7 is a diagram for explaining the operation of the conference opening notification. FIG. 8 is a diagram illustrating a display example of a conference opening notification. FIG. 9 is a diagram showing a schematic data structure of management data. Hereinafter, with reference to FIG. 6 to FIG. 9, the procedure of the conference holding notification reception process executed in the participant PC 400 will be described. It should be noted that in the following process for accepting a conference opening notification, the control unit 410 functions as a conference opening notification management unit 710.

  For example, when the participant PC 400 is turned on while being connected to the network A, the control unit 410 starts a conference opening notification reception process.

(Step S101)
When the process for accepting the conference opening notification is started, the control unit 410 determines whether there is a conference opening notification from the organizer PC 100.

  Here, the conference opening notice is transmitted from the organizer PC 100 to the management apparatus 200 and the participant PC 400 via the network A as shown in FIG. For example, the conference opening notification is performed by e-mail.

  As shown in FIG. 8, the conference name notification e-mail includes a conference name (eg, xx conference) in the title column. In the address field, the transmission destination of the conference opening notification, that is, the mail addresses assigned to the management apparatus 200 and the participants A, B, and C are described. The e-mail includes information indicating the meeting location (for example, XX meeting room) and information indicating the date and time of the meeting (for example, December 25, 13: 00-15: 00). . In addition, the original data of the conference material is attached to the e-mail.

  If at least the meeting name is described in the title column of the e-mail received via communication unit 440, control unit 410 determines that the meeting is held (step S101: YES), and the process proceeds to step S102. Proceed. On the other hand, the control unit 410 determines that there is no meeting opening notice when it has not received the e-mail with the meeting name written in the title column (step S101: NO), and performs the process for accepting the meeting opening notice. finish.

(Step S102)
When the process proceeds to step S102, control unit 410 stores the conference information and document data included in the conference opening notification.

  Specifically, as shown in FIG. 9, the control unit 410 associates reception date / time information, conference information (meeting name, venue, date / time, participant information), and document data, and stores them as management data. It is stored in a predetermined folder 413.

  Here, the reception date and time information is the current time acquired by the control unit 410 when an e-mail for meeting holding notification is received. The current time may be acquired from a clock (real time clock) built in the CPU 411 or may be acquired from an external server via the Internet. In addition, the transmission time described in the header of the e-mail for notifying the meeting may be used.

  Also, the conference name, the venue, the date and time, and the participant information are information described in the conference notification email. As shown in FIG. 9, the date and time of the event is composed of a meeting start time and an end time. The participant information may be an e-mail address described in the destination column of the e-mail for notifying the meeting opening, or may be the name of a prospective participant.

  The document data is preliminarily assigned with a meeting material name (file name), version information (A version, B version, etc.), and the control unit 410 stores the accompanying information together with the document data. As shown in FIG. 9, link information indicating a storage location of document data may be stored instead of document data.

  When the process of step S102 ends, the control unit 410 ends the process for accepting the conference opening notification.

  By repeating the above-described process for accepting the meeting opening notice periodically, the participant PC 400 receives the meeting opening notice transmitted from the organizer PC 100, and associates the meeting information and the manuscript data for each meeting opening notice. Can be stored and managed.

(2) Conference Holding Notification Registration Processing FIG. 10 is a flowchart of the conference holding notification registration processing. FIG. 11 is a diagram showing a schematic data structure of registration data. Hereinafter, the procedure of the registration process of the conference opening notification executed in the management apparatus 200 will be described with reference to FIGS. Note that the control unit 210 functions as the manuscript data management unit 610 in the following process for registering the meeting notification.

  For example, when the management apparatus 200 is turned on, the control unit 210 starts a conference holding notification registration process.

(Step S201)
When the process for registering the meeting opening notice is started, the control unit 210 determines whether or not there is a meeting opening notice from the organizer PC 100.

  Here, as shown in FIG. 7, the conference opening notification is the same conference opening notification transmitted from the organizer PC 100 to the participant PC 400 via the network A.

  When at least the meeting name is described in the title column of the e-mail received via the communication unit 220, the control unit 210 determines that the meeting is held (step S201: YES), and the process proceeds to step S202. Proceed. On the other hand, if the control unit 210 has not received an e-mail in which the title of the conference is described in the title column, the control unit 210 determines that there is no conference opening notification (step S201: NO), and performs a conference opening notification registration process. finish.

(Step S202)
When the process proceeds to step S202, the control unit 210 registers the conference information and document data included in the conference opening notification.

  Specifically, as shown in FIG. 11, control unit 210 associates reception date / time information, conference information (meeting name, venue, date / time, participant information), and document data in association with each other and stores them as registration data. To do.

  Here, the reception date and time information is the current time acquired by the control unit 210 when an e-mail for notifying the meeting is received. The current time may be obtained from a clock (real time clock) built in the CPU 211 or may be obtained from an external server via the Internet. In addition, the transmission time described in the header of the e-mail for notifying the meeting may be used.

  Also, the conference name, the venue, the date and time, and the participant information are information described in the conference notification email. As shown in FIG. 11, the date and time of the event is composed of a start time and an end time of the conference. The participant information may be an e-mail address described in the destination column of the e-mail for notifying the meeting opening, or may be the name of a prospective participant.

  The document data is preliminarily assigned with a meeting material name (file name), version information (A version, B version, etc.), and the control unit 210 stores the accompanying information together with the document data. However, as shown in FIG. 11, link information indicating the storage location of the document data may be stored instead of the document data.

  When there is registration data having the same conference name among a plurality of registration data, the control unit 210 collectively manages each conference (conference name) as shown in FIG.

  When the process of step S202 ends, the control unit 210 ends the process for registering the conference opening notification.

  The management apparatus 200 receives the meeting opening notification transmitted from the organizer PC 100 by periodically and repeatedly executing the above-described meeting opening notification registration process, and receives the meeting information and the manuscript for each meeting opening notification and for each meeting. Data can be registered and managed in association with each other.

  In addition, when the manuscript data registered in the management apparatus 200 is to be updated, the host PC 100 simply transmits a meeting opening notice to the management apparatus 200 to revise the manuscript data registered in advance or to create a new manuscript. Data can be added.

(3) Printing Process FIG. 12 is a flowchart of the printing process. FIG. 13 is a diagram for explaining the operation of the printing process. Hereinafter, with reference to FIGS. 12 to 13, the procedure of the printing process executed in the participant PC 400 will be described. In the following printing process, the control unit 410 functions as the print management unit 720.

  For example, when the controller 410 receives an instruction to open an e-mail stored in the participant PC 400 with a specific application in a state in which the connection is released from the network A (for example, at home or on a business trip), printing is performed. Start processing.

(Step S301)
When the printing process is started, the control unit 410 displays the content of the e-mail on the display unit 420. In the example shown in FIG. 8, an e-mail for notifying the meeting is displayed by a mailer, a browser, or the like.

  At this time, control unit 410 accepts selection of document data to be printed via input unit 430. For example, the original data to be printed can be selected by an operation (such as clicking) for specifying the original data attached to the e-mail.

  However, the document data selection method is not limited to this, and the document data may be directly selected from the document data stored and managed in the predetermined folder as the management data in step 102.

(Step S302)
The control unit 410 receives selection of an image forming apparatus that executes printing via the input unit 430. In the example shown in FIG. 13, since only the printing apparatus 500 is connected to the participant PC 400, the printing apparatus 500 is selected in step S302.

(Step S303)
The control unit 410 outputs a print instruction to the image forming apparatus. For example, in the example illustrated in FIG. 13, the control unit 410 instructs the printing apparatus 500 selected in step S302 to print based on the document data selected in step S301. More specifically, the control unit 410 converts document data to be printed into print data in a format that can be printed by the printing apparatus 500, and transmits the print data to the printing apparatus 500 together with a print command.

(Step S304)
The printing apparatus 500 executes printing based on a printing instruction from the participant PC 400. At this time, as shown in FIG. 13, the printing apparatus 500 outputs a printed matter (for example, conference material) based on the document data selected in step S301. When the printing is normally completed, the printing apparatus 500 transmits a printing completion notification to the participant PC 400.

  The control unit 410 of the participant PC 400 determines whether the printing instructed in step S303 is completed. Specifically, when receiving a print completion notification transmitted from printing apparatus 500 (step S304: YES), control unit 410 determines that printing is complete, and advances the process to step S305. On the other hand, when the notification of printing completion has not been received (step S304: NO), the control unit 410 waits until receiving the notification of printing completion.

(Step S305)
Control unit 410 determines whether or not the document data instructed to be printed in step S303 is the document data of the conference material. Specifically, control unit 410 determines that the document data of the conference material is the document data instructed to be printed in a state where the conference material notification is opened by a specific application. For example, if an e-mail including meeting information is opened by a mailer, a browser, or the like in step S301, and the document data is instructed to be printed in step S303, it is determined that the document data is meeting document data. If control unit 410 determines that the document data is the document data of the conference material (step 305: YES), the process proceeds to step S306.

  On the other hand, when the conference information is not included in the e-mail opened in step S301, control unit 410 determines that the document data instructed for printing in step S303 is not the document data of the conference material. If the control unit 410 determines that the document data is not the document data of the conference material (step S305: NO), the print process is terminated without storing (creating or updating) the print history.

  The control unit 410 selects the manuscript data selected from the manuscript data stored and managed as a management data in a predetermined folder of the storage 413 and then instructed to print in step S303 as manuscript data of the conference material. You may judge that there is.

(Step S306)
The control unit 410 executes a print history management process in order to store (create or update) the print history of the document data instructed to be printed in step S303. Details of the print history management process will be described later.

  When the process of step S306 ends, the control unit 410 ends the printing process.

  By executing the above print processing, the print history can be managed when the document data of the conference material is printed in an environment separated from the network A such as a company.

(4) Print history management process (S306)
FIG. 14 is a flowchart of the print history management process. FIG. 15 is a diagram illustrating a schematic data structure of print history data. Hereinafter, the procedure of the print history management process executed in the participant PC 400 will be described with reference to FIGS. In the following print history management process, the control unit 410 functions as the print management unit 720.

  The control unit 410 starts the print history management process when the process proceeds to step S306 of the print process.

(Step S361)
When the print history management process is started, the control unit 410 acquires information regarding the document data printed immediately before in step S303. Specifically, control unit 410 acquires conference information and attached information (conference material name, version information) managed in association with the printed document data.

(Step S362)
The control unit 410 determines whether the print history of the document data of the same conference as the document data printed immediately before in step S303 (document data having the same conference name) already exists in the print history data. If the print history data already exists (step S362: YES), the control unit 410 advances the process to step S363. If the print history data does not exist (step S362: NO), the control unit 410 performs the process. Proceed to S365. In the print history data, reception date / time information, file name (conference material name), version information, conference name, and print date / time are stored in association with each other as shown in FIG.

(Step S363)
The control unit 410 determines whether or not the document data printed immediately before in step S303 is the latest version. Specifically, the control unit 410 includes version information attached to the document data acquired immediately before in step S361, version information included in the print history of each document data stored in the print history data, and Are compared.

  If the document data printed immediately before in step S303 is the latest version (step S363: YES), control unit 410 advances the process to step S364. On the other hand, if the document data printed immediately before in step S303 is not the latest version (step S363: NO), the control unit 410 does not need to save it as a print history, and thus ends the print history management process. .

(Step S364)
The control unit 410 deletes data other than the latest print history. Specifically, the control unit 410 prints document data having version information older than or the same as the document data printed immediately before in the print history of the document data of the same conference as the document data printed immediately before in step S303. The print history is deleted from the print history data shown in FIG.

(Step S365)
The control unit 410 adds the latest print history. Specifically, control unit 410 adds the meeting information and the attached information acquired in step S361 to the print history data shown in FIG. 15 as the print history of the document data printed immediately before in step S303. At the same time, the control unit 410 may delete the printed document data printed immediately before in step S303.

  When the process of step S365 ends, the control unit 410 returns the process to the printing process of FIG.

  By executing the above print history management process, the print history can be stored (created and updated) every time the document data of the conference material is printed in an environment separated from the network A such as a company. In addition, since the print history other than the latest print history (print history of the latest version of manuscript data) is deleted by referring to the version information of the manuscript data used in the same meeting, the data amount of the print history is minimized. To the limit.

(5) Update Confirmation Request Process FIG. 16 is a flowchart of the update confirmation request process. FIG. 17 is a diagram illustrating a display example of a print history. FIG. 18 is a diagram for explaining the operation of the confirmation request. FIG. 19 is a diagram for explaining the operation of the confirmation result notification. Hereinafter, with reference to FIG. 16 to FIG. 19, a procedure of update confirmation request processing executed in the participant PC 400 will be described. In the following update confirmation request process, the control unit 410 functions as the confirmation request unit 730.

  For example, when the control unit 410 receives an instruction to display the print history through the input unit 430 while connected to the network A, the control unit 410 starts the update confirmation request process.

(Step S401)
When the update confirmation request process is started, the control unit 410 displays a plurality of print histories (print histories included in the print history data) stored by the print history management process on the display unit 420. For example, as shown in FIG. 17, the control unit 410 displays a print history for each original data, a check box 510 for selecting each print history, and a confirmation request transmission button 520 on the display unit 420.

  At this time, the control unit 410 receives selection of target document data (print history) to be requested for confirmation from the management apparatus 200 via the input unit 430. The confirmation request here is a request for confirming whether or not document data corresponding to printed document data printed in an environment disconnected from the network A has been updated in the management apparatus 200. A prospective participant of the conference who operates the participant PC 400 can select at least one document data (print history) for which a confirmation request is desired, for example, by checking a check box 510 shown in FIG.

  However, the display method of the print history is not limited to this, and the print history of the document data used in the same meeting may be displayed collectively.

(Step S402)
The control unit 410 issues a confirmation request to the management apparatus 200. For example, when the control unit 410 receives an operation for touching the confirmation request transmission button 520 illustrated in FIG. 17 via the input unit 430, the control unit 410 manages the print history of the document data selected in step S401 via the network A. It transmits to the apparatus 200 (FIG. 18). Note that the print history transmitted to the management apparatus 200 in step S402 is only the print history of the document data selected in step S401. Further, as described above, the print history includes reception date / time information, file name (conference material name), version information, conference name, print date / time, and the like (FIG. 15).

(Step S403)
Upon receiving the confirmation request in step S402, the management apparatus 200 executes an update confirmation process described later (FIG. 18), and confirms whether or not the document data subject to the confirmation request has been updated. The management apparatus 200 notifies the confirmation result to the participant PC 400 via the network A (FIG. 19).

  At this time, the control unit 410 of the participant PC 400 determines whether there is a confirmation result notification from the management apparatus 200. When the confirmation result is notified from the management apparatus 200 (step S403: YES), the control unit 410 advances the process to step S404. On the other hand, when the confirmation result is not notified from the management apparatus 200 (step S403: NO), the control unit 410 waits until the confirmation result is notified.

(Step S404)
The control unit 410 displays the confirmation result notified from the management apparatus 200 on the display unit 420 (FIG. 19).

(Step S405)
The control unit 410 determines whether there is a print instruction based on the document data updated in the management apparatus 200. For example, when control unit 410 receives an instruction to execute printing based on the updated document data via input unit 430 (step S405: YES), the process proceeds to step S406. On the other hand, when the print instruction is not accepted or when the instruction not to print is accepted (step S405: NO), the control unit 410 ends the update confirmation request process.

(Step S406)
The control unit 410 instructs the management apparatus 200 via the network A to print based on the updated document data (FIG. 20). At this time, the control unit 210 of the management apparatus 200 functions as the print control unit 640 and causes the image forming apparatus 300 connected to the network A to execute printing based on an instruction from the participant PC 400. More specifically, the control unit 210 of the management apparatus 200 converts the updated document data into print data in a format that can be printed by the image forming apparatus 300, and transmits the print data together with the print command to the image forming apparatus 300 (FIG. 20). ).

  The image forming apparatus 300 performs printing based on a print instruction from the management apparatus 200. At this time, as shown in FIG. 20, the image forming apparatus 300 outputs a printed matter based on the updated document data. When the printing is normally completed, the image forming apparatus 300 transmits a print completion notification to the management apparatus 200. At this time, the control unit 210 of the management apparatus 200 functions as the result notification unit 630 and notifies the participant PC 400 of the print result (print completion or the like).

(Step S407)
The control unit 410 of the participant PC 400 determines whether the printing instructed in step S406 has been completed. Specifically, when control unit 410 receives a print result notification transmitted from management apparatus 200 (step S407: YES), control unit 410 advances the process to step S408. On the other hand, when the notification of the printing result is not received (step S407: NO), the control unit 410 waits until the notification of the printing result is received.

(Step S408)
The control unit 410 deletes the print history of the original data before updating the original data printed in step S406. For example, as in the example shown in FIG. 20, when material 1 (B version) and material 2 (A version (older than B version)) are printed by the image forming apparatus 300, the material 1 before the update The print history for (A version) is deleted from the print history data.

  Note that the process of step S306 may be executed instead of the process of step S408. In this case, the print history of the original data before update is deleted, and the print history of the original data printed in step S406 is added.

  When the process of step S408 ends, the control unit 410 ends the update confirmation request process.

  By executing the above update confirmation request processing, the management apparatus 200 determines whether or not the document data is updated even when the document data of the conference material is printed in an environment separated from the network A such as a company. You can request confirmation. In addition, if necessary, the prospective participant can participate in the conference by printing the updated latest manuscript data.

(6) Update Confirmation Process FIG. 21 is a flowchart of the update confirmation process. FIG. 22 is a diagram for explaining the update confirmation operation. Hereinafter, with reference to FIGS. 21 to 22, a procedure of update confirmation processing executed in the management apparatus 200 will be described. In the following update confirmation process, the control unit 210 functions as the update confirmation unit 620.

  For example, the control unit 210 starts the update confirmation process when the management apparatus 200 is powered on.

(Step S501)
When the update confirmation process is started, the control unit 210 determines whether or not there is a confirmation request (confirmation request in step S402) from the participant PC 400. For example, when the control unit 210 receives a print history transmitted from the participant PC 400 via the network A (step S501: YES), the control unit 210 determines that this is a confirmation request and advances the process to step S502. On the other hand, when the print history is not received (step S501: NO), the control unit 210 waits until the print history is sent from the participant PC 400.

(Step S502)
The control unit 210 confirms whether there is newer document data than the document data requested to be confirmed. For this purpose, the control unit 210 analyzes and determines the print history received in step S501 and the conference information and document data managed by the management apparatus 200. More specifically, the control unit 210 compares the version information included in the print history received in step S501 with the version information added in advance to the document data registered or updated in the management apparatus 200. Judgment.

  For example, as shown in FIG. 22, the print history of the meeting name “XX meeting”, the meeting material name “document 1”, the version information “A version”, the meeting name “YY meeting”, and the meeting material name is It is assumed that the management apparatus 200 receives “Document 3” and a print history whose version information is “B version”.

  At this time, the control unit 210 extracts conference information having the same conference name as “XX conference” from the registration data (FIGS. 11 and 22). Next, the control unit 210 specifies document data having the same conference material name (file name) as “Material 1” from the document data associated with the extracted conference information. Then, the control unit 210 uses the version information (“A version”, “B version”) previously attached to the document data specified here and the version information (“A version”) included in the print history. Compare. At this time, if the version information of the document data identified from the registered data is newer than the version information included in the print history, the control unit 210 has newer document data ( It is determined that there is the latest version of the original data.

  Further, the control unit 210 extracts conference information having the same conference name as “YY conference” from the registered data (FIGS. 11 and 22). Next, the control unit 210 specifies document data having the same conference material name (file name) as “Material 3” from the document data associated with the extracted conference information. Then, the control unit 210 uses the version information (“A version”, “B version”) previously attached to the document data specified here and the version information (“B version”) included in the print history. Compare. At this time, if the version information of the document data identified from the registered data is older or the same as the version information included in the print history, the control unit 210 determines that the document data requested to be confirmed. It is determined that there is no new document data (latest document data).

(Step S503)
Next, the control unit 210 confirms whether there is another document data related to the document data requested to be confirmed. Specifically, the control unit 210 analyzes and determines the print history received in step S501 and the conference information and document data managed by the management apparatus 200.

  For example, as shown in FIG. 22, the print history of the meeting name “XX meeting”, the meeting material name “document 1”, the version information “A version”, the meeting name “YY meeting”, and the meeting material name is It is assumed that the management apparatus 200 receives “Document 3” and a print history whose version information is “B version”.

  At this time, the control unit 210 extracts conference information having the same conference name as “XX conference” from the registration data (FIGS. 11 and 22). Next, the control unit 210 searches for document data having a conference material name (file name) different from “Material 1” from the document data associated with the extracted conference information. At this time, if document data having a meeting material name (file name) different from “document 1” (“document 2 (A version)”) exists, control unit 210 determines that another document related to the document data requested for confirmation. Is determined to be present.

  Further, the control unit 210 extracts conference information having the same conference name as “YY conference” from the registered data (FIGS. 11 and 22). Next, the control unit 210 searches for document data having a conference material name (file name) different from “Material 3” from the document data associated with the extracted conference information. At this time, if there is no document data having a meeting material name (file name) different from “document 3”, control unit 210 determines that there is no other document data related to the document data requested to be confirmed.

(Step S504)
The control unit 210 functions as the result notification unit 630 and notifies the participant PC 400 of the confirmation results of steps S502 and S503 via the network A (notification of step S403, FIG. 19). Therefore, the control unit 210 determines whether or not document data that is newer than the document data requested for confirmation in step S501 exists in the management apparatus 200, and whether there is other document data related to the document data requested for confirmation in step S501. Notify the participant PC 400 whether or not.

  When the process of step S504 ends, the control unit 210 ends the update confirmation process.

  By executing the above update confirmation process, it is possible to confirm whether or not the manuscript data managed by the management apparatus 200 has been updated in response to a request from the participant PC 400 and to notify the confirmation result.

(7) History Deletion Processing FIG. 23 is a flowchart of history deletion processing. Hereinafter, with reference to FIG. 23, a procedure of history deletion processing executed in the participant PC 400 will be described. In the following history deletion process, the control unit 410 functions as the print management unit 720.

  For example, when power is turned on to the participant PC 400, the control unit 410 starts the history deletion process.

(Step S601)
When the history deletion process is started, the control unit 410 acquires the current time. For example, the control unit 410 may acquire the current time from a clock (real-time clock) built in the CPU 211 or may acquire the current time from an external server via the Internet.

(Step S602)
The control unit 410 acquires the meeting start time or meeting end time of each print history from the print history data. As shown in FIG. 11, the conference information of the print history data includes a conference start time and a conference end time as the conference date and time.

(Step S603)
The control unit 410 determines whether or not there is a print history whose current time has passed the conference start time or conference end time in the print history data. For example, the control unit 410 may determine whether or not the current time acquired in step S601 has passed the conference start time or conference end time acquired in step S602.

  If there is a print history whose current time has passed the conference start time or conference end time (step S603: YES), control unit 410 advances the process to step S604. On the other hand, when there is no print history whose current time has passed the conference start time or conference end time (step S603: NO), the control unit 410 ends the history deletion process.

(Step S604)
The control unit 410 deletes the print history whose current time has passed the conference start time or conference end time.

  When the process of step S604 ends, the control unit 410 ends the history deletion process.

  By periodically executing the history deletion process described above, the print history that is no longer needed after the conference is started or ended can be immediately deleted, and the memory storing the print history can be used effectively.

  Each processing unit in each flowchart described above is divided according to the main processing contents in order to facilitate understanding of the conference material distribution system 10. The invention of the present application is not limited by the method of classification of the processing steps and the names thereof. The processing performed in the conference material distribution system 10 can be divided into more processing steps. One processing step may execute more processes.

<Modification>
Moreover, said embodiment intends to illustrate the summary of this invention, and does not limit this invention. Many alternatives, modifications, and variations will be apparent to those skilled in the art.

  For example, in the above-described embodiment, in step S502, the control unit 210 compares the version information included in the print history with the version information added in advance to the document data registered or updated in the management apparatus 200. is doing. Then, the control unit 210 performs management processing 200 (registered data in FIG. 11) with newer document data than the previously registered document data (that is, the document data requested to be confirmed by the participant PC 400). It has been confirmed whether it was added to.

  However, the present invention need not be limited to this confirmation method. For example, in step S <b> 502, the control unit 210 compares the reception date / time information included in the print history with the reception date / time information of the meeting opening notification that includes the document data registered or updated in the management apparatus 200. You may confirm by doing. According to this confirmation method, even if the version information is not confirmed, the confirmation can be made based on whether or not the reception dates and times of the meeting holding notifications in the management apparatus 200 and the participant PC 400 match. Therefore, even when version information is not attached to the document data, it can be confirmed easily and at high speed that document data having a different version has been added to the management apparatus 200.

  In the above embodiment, the management apparatus 200 notifies the confirmation result to the participant PC 400 in step S403. The notification of the confirmation result indicates that the document data has been updated or the document data includes A notification that it has not been updated and does not need to be printed is included. However, the present invention is not limited to this, and the notification of the confirmation result may include a notification that the conference information or document data requested for confirmation is not registered in the management apparatus 200.

  In the above embodiment, the control unit 210 of the management apparatus 200 confirms whether or not there is document data that is newer than the document data requested to be confirmed by the participant PC 400, and notifies the participant PC 400 of the confirmation result. ing. After the notification, the management apparatus 200 receives a print instruction from the participant PC 400 and causes the image forming apparatus 300 to execute printing based on the updated document data.

  However, the present invention is not limited to this. After confirming that there is document data that is newer than the document data requested to be confirmed by the participant PC 400, the management apparatus 200 does not notify the participant PC 400 of the confirmation result, and performs printing based on the document data that has been confirmed to be updated. The image forming apparatus 300 may be executed. In this case, the control unit 210 of the management apparatus 200 functions as the result notification unit 630 and notifies the participant PC 400 of the confirmation result and the print result after the printing is completed. With such control, it is possible to output conference materials based on the updated document data without repeatedly communicating between the management apparatus 200 and the participant PC 400.

  In the above embodiment, the print history is displayed so as to be selectable for each document data (FIG. 17). However, the present invention is not limited to this, and the control unit 410 may display the print history so as to be selectable for each conference (meeting name). In this case, the control unit 410 transmits to the management apparatus 200 the print history for all document data used in the selected conference.

  Further, in the above embodiment, the conference opening notification is performed by electronic mail. However, the present invention is not limited to this, and the conference opening notification may be performed by transmission of data (for example, HTML data) that can be viewed with a WEB browser.

  FIG. 24 is a diagram for explaining a modified example of the conference material distribution system 10. As in the modification shown in FIG. 24, the management apparatus 200 may be incorporated in the image forming apparatus 300. In this case, the image forming apparatus 300 in which the management apparatus 200 is incorporated includes a print execution unit that directly receives a print instruction from the participant PC 400 and executes printing based on the print instruction. In addition, the image forming apparatus 300 may have all the functions of the management apparatus 200 described in the above-described embodiments and modifications.

  In addition, the configuration of the conference material distribution system 10 described above is the main configuration in describing the features of the above embodiment, and is not limited to the above configuration. Further, the configuration of the general conference material distribution system 10 is not excluded.

  Each functional configuration shown in FIGS. 4 and 5 is classified according to main processing contents in order to facilitate understanding of each functional configuration. The present invention is not limited by the way of classification and names of the constituent elements. Each functional configuration can be classified into more components according to the processing content. Moreover, it can also classify | categorize so that one component may perform more processes.

  The processing of each functional configuration shown in FIGS. 4 and 5 can also be realized by a dedicated hardware circuit. In this case, it may be executed by one hardware or a plurality of hardware.

  The program for operating the conference material distribution system 10 may be provided by a computer-readable recording medium such as a USB memory, a flexible disk, or a CD-ROM, or provided online via a network such as the Internet. Also good. In this case, the program recorded on the computer-readable recording medium is usually transferred to and stored in a memory or storage. Further, this program may be provided as, for example, a single application software, or may be incorporated in the software of each device as one function of the conference material distribution system 10.

10 meeting material distribution system,
100 Organizer PC,
200 management device,
210 control unit (management device),
220 communication unit (management device),
300 image forming apparatus,
400 Participant PC,
410 control unit (participant PC),
420 display unit,
430 input section,
440 Communication Department (participant PC),
500 printing device,
610 Document data management unit,
620 Update confirmation unit,
630 result notification unit,
640 print controller,
710 Meeting Holding Notification Management Department,
720 Print Management Department,
730 confirmation request part,
A network.

Claims (20)

A conference material distribution system in which a portable information terminal used by a prospective participant of a conference and a management device that manages manuscript data of the conference material used in the conference are communicably connected via a predetermined network Because
The information terminal
A meeting opening notification management unit that receives meeting information including meeting information that can identify the meeting and the document data, and manages the meeting information and the document data in association with each other;
A print management unit for instructing printing based on the document data managed by the meeting holding notification management unit and storing a print history of the document data in a state in which the connection is released from the network;
In order to confirm whether or not the document data corresponding to the printed document data printed based on the instruction of the print management unit has been updated in the management device, the print history is stored in the state connected to the network. A confirmation request part to be transmitted to the management device;
With
The management device
A document data management unit for receiving the conference notification and registering the conference information and the document data included in the conference notification in association with each other, and updating the document data in response to a request;
Analyzing the print history transmitted from the confirmation request unit, the meeting information and the document data registered by the document data management unit, document data corresponding to the printed document data is the document data. An update confirmation unit for confirming whether or not it has been updated by the management unit;
A result notification unit for notifying the information terminal of the confirmation result by the update confirmation unit;
Meeting material distribution system with   The document data management unit updates the document data by adding document data that is newer than previously registered document data and / or adding another document data related to the previously registered document data. The conference material distribution system according to claim 1, wherein The print history includes version information about the printed document data,
The update confirmation unit compares the version information included in the print history with the version information preliminarily attached to the document data registered or updated by the document data management unit, and registers it first. 3. The conference material distribution system according to claim 2, wherein whether or not new original data is added is confirmed. When the print management unit displays the confirmation result notified from the result notification unit and receives an instruction to execute printing based on the document data updated by the document data management unit, the print management unit Instruct printing based on the updated document data,
The conference material distribution system according to claim 1, wherein the management apparatus includes a print control unit that causes an image forming apparatus connected to the network to execute printing based on an instruction from the print management unit. . When the print management unit displays the confirmation result notified from the result notification unit and receives an instruction to execute printing based on the document data updated by the document data management unit, the print management unit Instruct printing based on the updated document data,
The said management apparatus is incorporated in the image forming apparatus connected to the said network, and is provided with the printing execution part which performs the printing based on the instruction | indication of the said printing management part. Meeting material distribution system.   After the instructed printing has been normally completed, the print management unit determines whether the printed document data is the document data of the conference material. If the document data is the conference material, the print management unit prints the printed document data. The meeting material distribution system according to any one of claims 1 to 5, which stores a history.   The conference material distribution system according to claim 6, wherein the print management unit determines that the document data instructed to be printed in a state in which the conference opening notification is opened by a specific application is the document data of the conference material.   7. The conference material distribution system according to claim 6, wherein the print management unit determines that the document data stored and managed in a predetermined folder by the conference holding notification management unit is the document data of the conference material.   The conference material according to claim 1, wherein the print management unit deletes a print history of original data before update of original data printed with the information terminal connected to the network. Distribution system. The conference information includes a conference start time or a conference end time,
The conference according to any one of claims 1 to 9, wherein the print management unit acquires a current time and deletes a print history in which the current time has passed the conference start time or the conference end time. Document distribution system.   The conference material distribution system according to claim 3, wherein the print management unit deletes a print history other than the latest print history by referring to the version information of the document data used in the same conference. The print management unit stores a print history for each document data,
The confirmation request unit displays a plurality of print histories stored by the print management unit, accepts selection of at least one print history, and transmits only the selected print history to the management device. The meeting material delivery system as described in any one of 1-11. The printing history includes reception date / time information indicating a date / time when a meeting holding notification including the printed document data was received,
The update confirmation unit compares the reception date and time information included in the print history with the reception date and time information of the meeting holding notification that includes the document data registered or updated by the document data management unit. 3. The conference material distribution system according to claim 2, wherein confirmation is made as to whether or not new manuscript data is added to the manuscript data previously registered.   6. The conference material distribution system according to claim 4, wherein the result notification unit notifies the information terminal of a print result when printing based on an instruction from the print management unit is executed.   The meeting material according to any one of claims 1 to 14, wherein the confirmation result notification includes a notification that the manuscript data is not updated by the manuscript data management unit and thus printing is not necessary. Distribution system.   The conference material distribution system according to claim 1, wherein the notification of the confirmation result includes a notification that the conference information or the document data is not registered.   The print management unit deletes the printed document data, and stores the conference information associated with the document data and information previously attached to the document data as the print history. The meeting material distribution system according to any one of 1 to 12. A conference material distribution system in which a portable information terminal used by a prospective participant of a conference and a management device that manages manuscript data of the conference material used in the conference are communicably connected via a predetermined network Because
The information terminal
A meeting opening notification management unit that receives meeting information including meeting information that can identify the meeting and the document data, and manages the meeting information and the document data in association with each other;
A print management unit for instructing printing based on the document data managed by the meeting holding notification management unit and storing a print history of the document data in a state in which the connection is released from the network;
In order to confirm whether or not the document data corresponding to the printed document data printed based on the instruction of the print management unit has been updated in the management device, the print history is stored in the state connected to the network. A confirmation request part to be transmitted to the management device;
With
The management device
A document data management unit for receiving the conference notification and registering the conference information and the document data included in the conference notification in association with each other, and updating the document data in response to a request;
Analyzing the print history transmitted from the confirmation request unit, the meeting information and the document data registered by the document data management unit, document data corresponding to the printed document data is the document data. An update confirmation unit for confirming whether or not it has been updated by the management unit;
A print control unit that causes an image forming apparatus connected to the network to execute printing based on document data whose update is confirmed by the update confirmation unit;
Meeting material distribution system with   The conference material distribution system according to claim 18, further comprising a result notification unit that notifies the information terminal of the confirmation result by the update confirmation unit and the printing result after the printing is completed.   The program for functioning a computer as a meeting material delivery system as described in any one of Claims 1-19.