Information Processing Apparatus and Information Processing Method

Abstract

To provide an information processing device capable of improving user convenience when distributing an event to both a compound machine and a user terminal.SOLUTION: An information processing device includes: an event notification reception unit configured to receive an event notification that is the same as that of a user terminal; an already-read information reception unit configured to receive already-read information indicating that the user terminal has confirmed the event notification; and an event processing unit configured to perform processing regarding the event notification differentiated according to whether the already-read information reception unit has received the already-read information.SELECTED DRAWING: Figure 9

Description

Technical Field

[0001] The present invention relates to an information processing apparatus and an information processing method, and more particularly, to an information processing apparatus, an information processing program, and an information processing method for distributing an event to both a multifunction device and a user terminal, for example.

Background Art

[0002] Patent Document 1 discloses a notification cooperation device that performs the same notification to the same user among different systems, and when the notification is read in one of the two systems, the information is linked to the other system.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Although the notification cooperation device disclosed in Patent Document 1 can manage the unread and read states of the same notification for the same user among different systems, depending on the type of notification, even if the notification content has been read in one system, there may be a case where the user has to check the notification content in the other system and perform some processing. Therefore, further improvement in user convenience is desired.

[0005] Therefore, the main object of the present invention is to provide a novel information processing apparatus and an information processing method.

[0006] Another object of the present invention is to provide an information processing apparatus and an information processing method that can improve user convenience when distributing an event to both a multifunction device and a user terminal.

Means for Solving the Problems

[0007] In order to solve the above problems, the present invention adopts the following configuration. Note that the reference numerals and supplementary explanations in parentheses indicate the correspondence with the embodiments described to assist in understanding the present invention, and do not limit the present invention in any way.

[0008] The first Example is an event notification receiving unit that receives the same event notification as the user terminal, A display unit that displays received event notifications, a read information receiving unit that receives read information indicating that the user terminal has confirmed the event notification, and an event processing unit that executes different processes regarding the event notification based on whether the read information receiving unit has received the read information. For events for which the event processing unit has received read information at the read information receiving unit, depending on whether the event notification requires re-notification even after being read on the user terminal, controls whether to redisplay the event notification for which read information has been received on the display unit It is an information processing apparatus.

[0009] The first Example In the, the information processing apparatus (20: reference numeral exemplifying the corresponding part in the embodiment. The same applies hereinafter) receives the same event notification distribution as the user terminal (40) as a personal device. When the information processing apparatus receives the event notification distribution, the event notification receiving unit (212, S25, S27) receives the event notification. The read information receiving unit (212, S29, S31) receives the read information indicating that the user terminal has confirmed the event notification. The event processing unit (212, S37 - S43) executes different processes regarding the event notification based on whether the read information receiving unit has received the read information. Not intended to be limiting For example, for event notifications for which the event processing unit has received read information at the read information receiving unit, depending on whether the event notification requires re-notification even after being read on the user terminal, controls whether to redisplay the event notification for which read information has been received on the display unit.

[0010] Example The first According to the, since different processes are executed regarding the event notification based on whether the read information has been received, the convenience of the user can be improved when distributing the event to both the user terminal (personal device).

[0012] The second example is an information processing apparatus that depends on the first example ​The event notification includes a first event notification and a second event notification of a different type from the first event notification. When the event notification received by the event notification receiving unit is the first event notification, if the read information receiving unit receives the read information, the event processing unit does not display the first event notification on the display unit. Yes.

[0013] The third example is an information processing apparatus that depends on the second example, When the event notification received by the event notification receiving unit is the second event notification, the event processing unit displays the second event notification on the display unit even if the read information receiving unit has received the read information. Yes. The fourth example includes an event notification receiving unit that receives the same event notifications as the user terminal, a display unit that displays the received event notifications, a read information receiving unit that receives read information indicating that the user terminal has confirmed the event notification, and an event processing unit that executes different processes for the event notification based on whether the read information receiving unit has received the read information. The event notification includes a second event notification of a type different from the first event notification and the first event notification, When the event notification received by the event notification receiving unit is the second event notification, the event processing unit displays the second event notification on the display unit even if the read information receiving unit has received the read information. Is an information processing apparatus

[0014] The fifth Example is an information processing method in an information processing apparatus, including an event notification receiving step of receiving the same event notification as that of the user terminal, A display step of displaying the received event notification, a read information receiving step of receiving read information indicating that the user terminal has confirmed the event notification, and an event processing step of performing different processes regarding the event notification based on whether the read information is received in the read information receiving step. In the event processing step, for event notifications for which read information has been received in the read information receiving step, depending on whether the event notification requires re-notification even after being read on the user terminal, controls whether to redisplay the event notification for which read information has been received in the display step It is an information processing method.

Advantages of the Invention

[0015] According to this invention, different processes (or display processes) regarding the event notification are executed based on whether it has been read or not on the user terminal (personal device). Therefore, even when event notifications are distributed to both the information processing apparatus and the user terminal, the convenience for the user can be improved.

[0016] The above object, other objects, features, and advantages of this invention will become more apparent from the following detailed description of the embodiments with reference to the drawings.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Best Mode for Carrying Out the Invention

[0018] Referring to FIG. 1, an information processing system 10 according to an embodiment (first embodiment) of the present invention includes a multifunction device 20, a server 30, and a user terminal 40. The multifunction device 20, the server 30, and the user terminal 40 can communicate signals, data, or information with each other via a network 50 such as the Internet.

[0019] The multifunction device 20 in this embodiment is an example of an information processing apparatus and has a plurality of functions such as a copying function, a printing function, a scanning function, and a facsimile function. The server 30 distributes, for example, events generated by the multifunction device 20 to the multifunction device 20 and the user terminal 40 in response to a distribution request from the multifunction device 20. The user terminal 40 is a personal device of the user who owns it and may be, for example, a smartphone, a tablet computer, or a personal computer. The network 50 is, as described above, for example, the Internet, but is not limited thereto and may be a VPN (Virtual Private Network) or a dedicated line.

[0020] In FIG. 1, only one user terminal 40 is connected to the network 50, but the number of user terminals 40 corresponding to the number of users related to the information processing system 10 may be connected to the network 50.

[0021] As shown in FIG. 2, the multifunction device 20 in the first embodiment includes an image reading unit 202, an image forming unit 204, and a paper feeding unit 206. The multifunction device 20 also includes a communication unit 208 and an input / output interface (I / O) unit 210. Further, the multifunction device 20 includes a main control unit 212, an auxiliary storage unit 214, and an external storage medium connection unit 216. The multifunction device 20 also includes a display unit 218 and an operation unit 220. These are connected to a common bus 222.

[0022] As is well known, the image reading unit 202 is an image reading means that reads an image of a document and outputs two-dimensional image data corresponding to the image of the document. For this purpose, the image reading unit 202 includes a document placement table, a light source, a plurality of mirrors, an imaging lens, a line sensor, etc., although not shown in the drawings.

[0023] The image forming unit 204 is an image forming means that forms an image on a recording sheet by an electrophotographic method. For this purpose, the image forming unit 204 includes a photosensitive drum, a charging device, an exposure device, a developing device, a transfer device, a fixing device, etc., although not shown in the drawings. As the image data used for the image forming process by this image forming unit 204, for example, there is image data output from the image reading unit 202. Also, image data based on various files imported from the user terminal 40 and external storage media described later may also be used for the image forming process by the image forming unit 204. Note that the image forming unit 204 can perform not only black-and-white image forming processes but also color image forming processes.

[0024] The paper feeding unit 206 includes a paper feeding cassette (not shown) and is a paper feeding means that feeds the recording paper accommodated in this paper feeding cassette one by one into the image forming unit 204.

[0025] The communication unit 208 is a communication means that can perform two-way communication processing via the network 50. Also, the communication unit 208 can execute communication by a wireless method such as the Wi-Fi (registered trademark) method. This communication processing by the wireless method is performed, for example, with the user terminal 40 near the multifunction machine 20.

[0026] The input / output interface unit 210 is connected to various sensors, motors, etc., and strictly speaking, is connected to their drive circuits. Examples of various sensors include a sensor for detecting the presence or absence of paper in the paper feed cassette, a toner sensor in the developing device, and a paper detection sensor appropriately provided in the paper conveyance path from the paper feed cassette to the paper discharge unit. Examples of motors include a paper conveyance motor appropriately provided in the paper conveyance path and a motor for driving the aforementioned photosensitive drum. Output signals from the respective sensors are sent to the main control unit 212 via this input / output interface unit 210, and control signals are sent from the main control unit 212 to the respective motors.

[0027] The main control unit 212 is a control means that controls the overall operation of the multifunction device 20. For this reason, the main control unit 212 includes a computer equipped with a CPU. The main control unit 212 also includes a main storage unit 212a as main storage means directly accessible by the CPU. This main storage unit 212a includes, for example, a RAM and a ROM.

[0028] The auxiliary storage unit 214 is auxiliary storage means including, for example, a hard disk and a flash memory. Various types of image data such as image data output from the image reading unit 202 and various types of data other than image data are appropriately stored in this auxiliary storage unit 214 according to the control by the CPU.

[0029] The external storage medium connection unit 216 has a connection port to which an external storage medium such as a USB memory can be connected, and performs data transmission and reception of various files and the like with the external storage medium. Therefore, for example, it is possible to import data such as various files recorded on the external storage medium to the multifunction device 20 side, or to send data such as various files from the multifunction device 20 side to the external storage medium for storage.

[0030] The display unit 218 has a display 218a as a display means. This display 218a cooperates with the touch panel 220a of the operation unit 220 to constitute a display with a touch panel (touch screen). This display 218a is, for example, a liquid crystal display (LCD), but is not limited thereto, and may be an organic EL display or the like. Further, the display unit 218 may include an appropriate light-emitting element such as a light-emitting diode in addition to the display 218a.

[0031] The operation unit 220 has a touch panel 220a as an operation reception means. This touch panel 220a cooperates with the display 218a as described above to constitute a display with a touch panel. For this reason, the touch panel 220a is provided so as to overlap the display surface of the display 218a. Further, the operation unit 220 may include an appropriate hardware switch such as a push button switch in addition to the touch panel 220a.

[0032] As shown in FIG. 3, the server 30 in the first embodiment includes a main control unit 302, a communication unit 304, and an auxiliary storage unit 306. These are connected to a common bus 308.

[0033] The main control unit 302 is a control means in the server 30 that controls the overall operation of the server 30. For this reason, the main control unit 302 includes a computer including a CPU. Further, the main control unit 302 includes a main storage unit 302a as a main storage means in the server 30. This main storage unit 302a includes, for example, a RAM and a ROM.

[0034] The communication unit 304 is a communication means in the server 30 that can perform two-way communication processing via the network 50.

[0035] The auxiliary storage unit 306 is an auxiliary storage means in the server 30 that includes, for example, a hard disk and a flash memory.

[0036] The user terminal 40 in the first embodiment is a smartphone, a tablet computer, a personal computer, etc. as described above. For example, when it is a smartphone, as shown in FIG. 4, it includes a main control unit 402, an auxiliary storage unit 404, and a communication unit 406. The smartphone as the user terminal 40 includes a display unit 408 and an operation unit 410. These are connected to a common bus 412 with each other.

[0037] The main control unit 402 is a control means in the user terminal 40 that controls the overall operation of the user terminal 40. Therefore, the main control unit 402 includes a computer having a CPU. The main control unit 402 also includes a main storage unit 402a as the main storage means in the user terminal 40. This main storage unit 402a includes, for example, RAM and ROM.

[0038] The communication unit 406 of the user terminal 40 is a communication means in the user terminal 40 that performs two-way communication processing via the network 50. This communication unit 406 can perform communication processing by a wireless method such as the Wi-Fi method, but can also perform communication processing by a wired method. Further, the communication unit 406 can perform wireless communication processing with the multifunction device 20 (communication unit 208).

[0039] The display unit 408 has a display 408a as a display means in the user terminal 40. This display 408a cooperates with the touch panel 410a of the operation unit 410 to form a touch panel-equipped display. This display 408a is, for example, a liquid crystal display, but is not limited thereto, and may be an organic EL display or the like.

[0040] The operation unit 410 has a touch panel 410a as an operation reception means in the user terminal 40. This touch panel 410a cooperates with the display 408a as described above to form a touch panel-equipped display. Therefore, the touch panel 410a is provided so as to overlap the display surface of the display 408a.

[0041] In the information processing system 10 of the first embodiment, upon receiving an event distribution request from the multifunction device 20, the server 30 transmits the event information to both the multifunction device 20 and the user terminal 40. Then, the server 30 processes the event notification depending on whether or not there is read information from the user terminal 40. In other words, the server 30 executes processing (or display processing) related to the event notification based on whether or not the information has been read on the user terminal 40.

[0042] There are two types of such events, as described below.

[0043] An event of type 1 is simply a notification, and does not require canceling the notification cause on the multifunction device 20. In other words, an event notification of type 1 is an event that only needs to be confirmed once on either the multifunction device 20 or the user terminal 40, and does not require a cancel operation on the multifunction device 20.

[0044] Events of type 1 include, for example, internal business notices, notices from the management department, notices from the management department about document format revisions, announcements of new products and services from multifunction device retailers, etc. Event notices of type 1 like this should basically be distributed to the user terminals of all users, and do not need to be continuously displayed on the multifunction device 20 after being confirmed (read) on the user terminal 40.

[0045] A type 2 event is an event notification that occurs in the multifunction device 20, and the cause of the notification must be canceled or confirmed in the multifunction device 20. Therefore, even if the event notification in question is confirmed (read) in the user terminal 40, this type 2 event is an event that needs to be displayed in the multifunction device 20 until the cause of the notification is canceled or confirmed in the multifunction device 20.

[0046] Events of type 2 include, for example, receiving print data, receiving facsimile data, running out of paper / toner, a firmware update notification, and printing print data.

[0047] Such type 2 event notifications may be distributed only to the user terminals of specific users or should be distributed to the user terminals of all users. For example, a print data reception notification should be distributed to the specific user who sent the print data to the multifunction device 20, a firmware update notice should be distributed to the user terminals of all users belonging to a specific group, and a fax data reception or paper / toner out notice should be distributed to the user terminals of all users.

[0048] Among type 2 events, for example, fax data reception, firmware update notices, etc. are displayed on the multifunction device 20 until they are confirmed once or the notification factor is canceled. Notices such as paper / toner out need to be displayed on the multifunction device 20 until the notification factor is canceled on the multifunction device 20 even if they have been confirmed (marked as read) on the user terminal 40.

[0049] Among type 2 events, printing of print data, etc. is an event that requires cancellation of the notification factor on the multifunction device 20 and is an event where it is desired to have a specific user (the target user) cancel the notification factor.

[0050] A program for processing events as described above is set in the multifunction device 20.

[0051] FIG. 5 shows a memory map 60 of the main memory unit 212a of the multifunction device 20. As shown in this memory map 60, the main memory unit 212a has a program storage area 62 and a data storage area 64.

[0052] In the program storage area 62, a control program 620 for controlling the operation of the aforementioned computer is stored. This control program 620 includes a display control program 622, an operation detection program 624, an image reading program 626, an image forming program 628, a communication control program 630, an event processing program 632, etc.

[0053] The display control program 622 is a program for generating display screen data necessary to display various screens on the display 218a (Fig. 2) of the display unit 218. The operation detection program 624 is a program for detecting the operation state of the user on the operation unit 220 including the touch panel 220a. The image reading program 626 is a program for controlling the image reading unit 202. The image forming program 628 is a program for controlling the image forming unit 204. The communication control program 630 is a program for controlling the communication unit 208.

[0054] And the event processing program 632 is a program for causing the main control unit (computer) 212 to detect events as described above, send a distribution request for an event to the server 30, receive an event notification sent from the server 30, and receive read information from the user terminal 40 sent from the server 30.

[0055] For example, in response to a paper out signal from the paper sensor input from the I / O unit 210, an event of paper out in the paper feeding unit can be detected. Similarly, in response to a toner out signal input from the toner sensor provided in the image forming unit 204, an event of toner out can be detected.

[0056] For example, the computer can identify the data (including the data identifier) received from the communication unit 208 and detect events such as receiving an internal notice, receiving facsimile data, receiving print data, etc. Further, the computer can identify the data (including the data identifier) received from the communication unit 208 and also detect events such as having a firmware update, having a revision of the document format, etc.

[0057] For example, an event of printing facsimile data can be detected according to the operation commanded by the computer to the image forming unit 204. Similarly, an event of printing hold print data can be detected according to the operation commanded by the computer to the image forming unit 204.

[0058] In the data storage area 64 shown in FIG. 5, a storage area 640 for various data is provided. The various data include display image generation data, operation data, image data, transmission / reception data, event data, distribution destination lists, etc., and respective storage areas 642, 644, 646, 648, 650, 652, etc. are formed.

[0059] The display image generation data stored in the display image generation data storage area 642 is data such as polygon data and texture data used for generating the above-described display screen data. The operation data stored in the operation data storage area 644 is data representing the operation state of the user on the operation unit 220 including the touch panel 220a. For example, it is time-series data representing the touch position (coordinates) of the user on the touch panel 220a. The image data stored in the image data storage area 646 is image data such as the image data output from the image reading unit 202 and the image data used for the image forming process by the image forming unit 204. The image data stored in the image data storage area 646 may further include the facsimile data and print data listed above. The transmission / reception data stored in the transmission / reception data storage area 648 is data transmitted and received between the server 30, the user terminal 40, etc.

[0060] The event data stored in the event data storage area 650 is, for example, the event data detected by the previous event processing program 632.

[0061] The destination list stored in the destination list storage area 652 is a list indicating to which user terminals (and MFPs) the event data should be distributed when the MFP 20 distributes event data in response to an event distribution request from the server 30. This destination list stores, for each type of the above-described events, to which user terminals (and MFPs) the events should be distributed.

[0062] FIG. 6 shows a memory map 70 of the main storage unit 302a of the server 30. As shown in this memory map 70, the main storage unit 302a has a program storage area 72 and a data storage area 74.

[0063] The program storage area 72 stores a control program 720 for controlling the operation of the computer of the main control unit 302. This control program 720 includes a communication control program 722, an event processing program 724, and the like.

[0064] The communication control program 722 is a program for controlling the communication unit 304. The event processing program 724 is a program for causing the main control unit (computer) 302 to execute store event processing described later. However, the event processing here includes, in response to an event distribution request from the previous MFP 20, distributing (transmitting) an event notification to the corresponding or all user terminals 40 of users and the corresponding MFP 20, re-distributing (re-transmitting) the event notification as necessary, receiving read information of the event notification from the user terminal 40, and transmitting the read information to the corresponding MFP 20.

[0065] On one hand, various data storage areas 740 are formed in the data storage area 74. The transmission / reception data stored in these various data storage areas 740 includes a transmission / reception data storage area 742 that stores transmission / reception data such as event data received from the multifunction device 20, a destination list storage area 744, and the like. The destination list is a list indicating to which user terminals or multifunction devices the event notification should be distributed when the server 30 receives an event distribution request from the multifunction device 20. This destination list stores which user terminals or multifunction devices to distribute the event to for each type of the aforementioned event.

[0066] FIG. 7 shows a memory map 80 of the main memory section 402a of the user terminal 40. The main memory section 402a has a program storage area 82 and a data storage area 84. In the program storage area 82 among these, a control program 820 for controlling the operation of the computer of the main control section 402 is stored. This control program 820 includes a display control program 822, an operation detection program 824, a communication control program 826, an event processing program 828, and the like.

[0067] The display control program 822 is a program for generating display screen data necessary for displaying various screens on the display 408a of the display section 408. The operation detection program 824 is a program for detecting the operation state by the user on the operation section 410 including the touch panel 410a. The communication control program 826 is a program for controlling the communication section 406. The event processing program 828 is a program for causing the main control section (computer) 402 to process the event notification data as described above.

[0068] In the data storage area 84, various data storage units 840 are formed. In the display image generation data storage area 842, display image generation data such as polygon data and texture data used for generating display screen data based on the display control program 822 is stored. The operation data stored in the operation data storage area 844 is data representing the operation state of the user on the operation unit 410 including the touch panel 410a, for example, time-series data representing the touch position of the user on the touch panel 410a. And the transmission / reception data is stored in the transmission / reception data storage area 846. The transmission / reception data includes event data distributed from the server 30, read information to be returned to the server 30 when the user has read the event data on the user terminal 40, and the like.

[0069] FIG. 8 is a flowchart showing the operation according to the event processing program 724 of the main control unit 302 (computer) of the server 30 in this embodiment. The operation flow of FIG. 8 is assumed to be repeatedly executed at a predetermined time, for example, every frame period.

[0070] In the first step S1, the main control unit 302 determines whether it has received an event distribution request from the multifunction machine 20. In this step S1, the main control unit 302 can determine whether the received data is a distribution request from the multifunction machine 20 by decoding the received data received from the communication unit 304 (FIG. 3) according to the event processing program 724 (FIG. 6). The event distribution request from the multifunction machine 20 includes not only the event notification data desired to be distributed but also data (type data) indicating which of the above-described type 1 or type 2 the event notification data corresponds to. Therefore, the event notification data from the multifunction machine 20 is stored in the transmission / reception data storage area 742 (FIG. 6) together with the type data.

[0071] When it is determined as "YES" in step S1, the main control unit 302 transmits an event to the user terminal 40 of the destination indicated by the distribution destination list according to the type, using the event notification data stored in the transmission / reception data storage area 742 in step S3. At the same time, in step S5, the main control unit 302 transmits an event to the multifunction device 20 of the destination indicated by the distribution destination list according to the type, using the event notification data stored in the transmission / reception data storage area 742.

[0072] When it is determined as "NO" in step S1, the main control unit 302 determines in the next step S7 whether there is an event distribution request from the outside. Here, "the outside" means other computers (not shown) connected via the network 50 (FIG. 1). For example, an event such as an advertising request from the sales company of the multifunction device 20 corresponds to the event distribution request from the outside here.

[0073] When it is determined as "YES" in step S7, the main control unit 302 stores the event data of such an external distribution request in the transmission / reception data storage area 742. Note that an event (for example, an advertisement) from such an external event distribution request corresponds to type 1, so the type data indicating type 1 is also stored in the transmission / reception data storage area 742 together.

[0074] Then, in steps S9 and S11, according to the external distribution request, event data is transmitted to the user terminal and the multifunction device of the destination indicated by the distribution destination list.

[0075] When it is determined as "NO" in step S7, the main control unit 302 determines in step S13 whether it has received read information from the user terminal 40 that distributed event data in step S3 or S9. Also in this step S13, the main control unit 302 can determine whether the received data is read information from the user terminal 40 by referring to the received data according to the event processing program 724 (FIG. 6) received from the communication unit 304 (FIG. 3).

[0076] When it is determined as “YES” in step S13, the main control unit 302 transmits the read information to the multifunction machine 20 that received the event distribution request in step S1 in the subsequent step S15.

[0077] FIG. 9 is a flowchart showing the operation according to the event processing program 632 of the main control unit 212 (computer) of the multifunction machine 20 in this embodiment. It is assumed that the operation flow of FIG. 9 is repeatedly executed every predetermined time, for example, every frame period.

[0078] In the first step S21, the main control unit 212 determines whether an event has been detected. When it is determined as “YES” in this step S21, the main control unit 212 transmits the event distribution request together with the event notification data from the communication unit 208 (FIG. 2) to the server 30 according to the event processing program 632 (FIG. 5) in the subsequent step S23.

[0079] This event distribution request includes not only the event notification data for which distribution is desired but also data (type data) indicating which of the above-described type 1 or type 2 the event notification data corresponds to. And the event notification data included in the event distribution request transmitted to the server 30 in step S23 is stored in the transmission / reception data storage area 742 (FIG. 6) together with the type data.

[0080] When it is determined as “NO” in step S21, the main control unit 212 determines in step S25 whether an event notification for the multifunction machine 20 has been received. The main control unit 212 can determine whether the received data is event notification data from the server 30 by referring to the received data from the communication unit 208 (FIG. 2) according to the event processing program 632 (FIG. 5).

[0081] When it is determined as "YES" in this step S25, the main control unit 212 stores, in step S27, the received event notification data (including type data) in the transmission / reception data storage area 648. The main control unit 212 that executes steps S25 and S27 functions as an event notification reception unit.

[0082] After storing the event notification data received in step S27, or after determining "NO" in step S25, the main control unit 212 determines, in step S29, whether it has received the read information of the target event (the event that the MFP 20 has requested the server 30 to distribute) at the user terminal from the server 30. Here too, the main control unit 212 can determine whether the received data is the read information from the server 30 by referring to the received data according to the event processing program 632 (FIG. 5) received from the communication unit 208 (FIG. 2).

[0083] When it is determined as "YES" in step S29, in step S31, the read information of the target event is stored in the transmission / reception data storage area 648. The main control unit 212 that executes steps S29 and S31 functions as a read information reception unit.

[0084] When it is determined as "NO" in step S29, or after executing step S31, the main control unit 212 determines, in step S33, whether a user has logged in to the MFP 20. Specifically, as is well known, a login screen (for example, a GUI (Graphical User Interface)) is displayed on the display 218a, and if the user inputs a user ID or the like there and goes through an authentication process, the user logs in. However, when it is determined as "NO" in this step S33, that is, when the user has not logged in, the operation ends.

[0085] When it is determined "YES" in step S33, the main control unit 212 determines in step S35 whether the logged-in user has an event distribution request to be notified. Here, the main control unit 212 can make the determination by referring to the event data and the distribution destination list respectively stored in the event data storage area 650 and the distribution destination list storage area 652 of the data storage area 64 according to the event processing program 632 (FIG. 5). The main control unit 212 that executes this step S35 functions as an event notification receiving unit.

[0086] When it is determined "NO" in step S35, the operation ends.

[0087] When it is determined "YES" in step S35, the main control unit 212 determines in step S37 whether the target event is an event that requires re-notification even if it has been read on the user terminal 40. Here, the main control unit 212 can make the determination by referring to the event data (including type data) and the distribution destination list respectively stored in the event data storage area 650 and the distribution destination list storage area 652 of the data storage area 64.

[0088] When it is determined "YES" in step S37, the main control unit 212 displays in step S39 the event notification data (including type data) stored in the transmission / reception data storage area 742 (FIG. 6) in step S23 on the display unit 218 (display 218a thereof) according to the display control program 622 (FIG. 6). That is, step S39 is a step of re-displaying the notification content of the target event even if the reception of the read information from the user terminal 40 is definite because the target event is an event of a type that must be re-notified (displayed) on the multifunction machine 20 even if the user has confirmed it (even if it has been read) on the user terminal 40.

[0089] When the main control unit 212 determines "NO" in step S37, in the next step S41, it determines whether the user who logged in in step S33 has confirmed (read) the target event on the multifunction device 20. Here, the main control unit 212 can determine, for example, whether a confirmation means such as an OK button, which is displayed together when the target event is displayed on the display 218a, has been operated by the user.

[0090] When it is determined "YES" in this step S41, since there is no need for re-notification ( "NO" in step S37), the operation is terminated as it is.

[0091] On the other hand, when it is determined "NO" in step S41, the main control unit 212 displays the corresponding target event on the display 218a of the display unit 218 in step S43 according to the display control program 622.

[0092] In this way, different determinations are made in steps S37 and S41 depending on whether the read information from the user terminal 40 has been received, and step S39 is executed or not according to the result. That is, the main control unit 212 that executes this step S37 - S37 functions as an event processing unit that executes different processes regarding event notifications based on whether the read information has been received.

[0093] FIG. 10 is a flowchart showing the operation according to the event processing program 828 of the main control unit 402 (computer) of the user terminal 40 in this embodiment. It is assumed that the operation flow of this FIG. 10 is repeatedly executed at a predetermined time, for example, every frame period.

[0094] In the initial step S51, the main control unit 402 determines whether it has received an event notification from the server 30. In this step S51, the main control unit 402 can determine whether the received data received from the communication unit 406 (FIG. 4) is an event notification distributed from the server 30. The received event data is displayed on the display 408a of the display unit 408 by the display control program 822 (FIG. 7).

[0095] When it is determined as "NO" in step S51, the operation ends. On the other hand, when it is determined as "YES" in step S51, the main control unit 402 determines whether it has confirmed (read) the event notification in step S53. Here, the main control unit 402 can determine, for example, whether a confirmation means, such as an OK button, which is also displayed when the event is displayed on the display 408a, has been operated by the user.

[0096] When it is determined as "YES" in step S53, the main control unit 402 transmits the read information to the server 30. For example, in response to the operation of the above-described confirmation means, the main control unit 402 controls the communication control program 822 (FIG. 7) to transmit the read information to the server 30 and ends the operation.

[0097] When it is determined as "NO" in step S53, that is, when the event notification has not been read, the operation ends.

[0098] Next, with reference to FIGS. 11 - 14, specific examples of different types of event notifications will be described.

[0099] FIG. 11 shows a case where an event notification of type 1 is transmitted from the server 30 to both the multifunction device 20 and the user terminal 40. FIG. 11(A) shows an example of the display screen 224 of the display 218a of the multifunction device 20, and FIG. 11(B) shows an example of the display screen 414 of the display 408a of the user terminal 40. The event notification shown in FIG. 11 belongs to type 1 described above, which is "Internal business notice".

[0100] In this example, the event notification of the internal business notice is input from an external computer or server (not shown) to the server 30 through the communication unit 304. This event notification data, together with the type data, is stored in the transmission / reception data storage area 742 (FIG. 6) of the main memory unit 302 of the server 30. Then, the main control unit (computer) 302 of the server 30 refers to the type data and recognizes that the event notification at this time belongs to type 1. Therefore, the main control unit 302 determines "YES" in step S7 of FIG. 8, and in steps S9 and S11, according to the distribution destination list for the type 1 event notification stored in the distribution destination list storage area 744, it transmits the event notification data (including the type data) to the user terminals 40 of all users and all the multifunction devices 20.

[0101] Therefore, the main control unit (computer) 212 of the multifunction device 20 stores the received event notification data, together with the type data, in the event data storage area 650 according to the event processing program 632 (FIG. 5).

[0102] Also in the user terminal 40, the main control unit (computer) 402 stores the received event notification data, together with the type data, in the transmission / reception data storage area 846 that also functions as an event data storage area according to the event processing program 828 (FIG. 7).

[0103] Then, the main control unit (computer) 402 displays a pop-up 416 on the display screen 414 of the display 408a according to the display control program 822, and displays an event notification 418 and a detail button 420 in the pop-up 416. This detail button 420 is a software button for operating when the user wants to check (read) the details of the event notification, and is operated by the touch panel 410a.

[0104] When this detail button 420 is operated by the user, the main control unit 402 determines that the event notification 418 has been confirmed by the user (FIG. 10: step S53), and transmits the read information to the server 30.

[0105] This read information is transmitted from the server 30 to the multifunction device 20 (FIG. 8: step S13).

[0106] In response to this, the main control unit 212 of the multifunction device 20 determines "YES" in step S29 shown in FIG. 9, and stores this read information in the event data storage area 650 (FIG. 5).

[0107] Based on the type data included in the previously stored event data, the main control unit 212 of the multifunction device 20 determines that the current event notification belongs to type 1, and if it is confirmed (read) on the user terminal 40, it determines that there is no need to confirm it on the multifunction device 20 ("NO" in step S37, "YES" in step S41), so the event notification is not displayed on the multifunction device 20.

[0108] However, if there is no read information on the user terminal 40, "NO" is determined in step S41, and the main control unit 212 displays a pop-up 226 on the display screen 224 of the display 218a in accordance with the display control program 622, and displays an event notification 228 based on the event notification data stored in the event data storage area 650 and an OK button 230 within the pop-up 226. This OK button 230 is a software button to be operated when the event notification has been confirmed (read), and is operated by the touch panel 220a.

[0109] In this way, in the case of an event belonging to type 1, which is an event that does not require the cancellation of the notification cause on the multifunction device 20, if it is confirmed (read) on the user terminal 40, it will not be displayed again on the multifunction device 20. However, if there is no read information from the user terminal 40, an event belonging to type 1 will be displayed on the multifunction device 20.

[0110] In the embodiment of FIG. 11, the event notification delivered to the multifunction device 20 and the event notification delivered to the user terminal 40 are the same, but they do not necessarily have to be the same; as long as the event notifications have a similar purpose, they can be said to be the same event notification in this case as well.

[0111] FIG. 12 shows a case where an event belonging to type 2 is distributed from the server 30 to both the multifunction device 20 and the user terminal 40. FIG. 12(A) shows an example of the display screen 224 of the display 218a of the multifunction device 20, and FIG. 12(B) shows an example of the display screen 414 of the display 408a of the user terminal 40. The event notification shown in FIG. 12 is the "fax reception" belonging to type 2 described above.

[0112] For this "fax reception" event notification, although only one person actually needs to be notified, since the server 30 cannot know in advance to whom the fax data is addressed, it notifies all registered users. And not only is the user terminal 40 (personal device) used to confirm the notification content, but someone also has to operate the multifunction device 20 to cancel the notification factor.

[0113] The fax data is input into the multifunction device 20 from an external computer or a fax device (not shown) through the communication unit 208 (FIG. 2). When the reception of the fax data is completed, the main control unit (computer) 212 determines "YES" in step S21 for determining whether an event has been detected. Then, in step S23, an event distribution request for distributing the detected event is transmitted to the server 30. At this time, data of the event notification of the fax data reception and type data of the event notification data (in this case, type 2) are transmitted to the server 30.

[0114] On the one hand, this event notification data, together with the type data, is stored in the transmission / reception data storage area 742 (Fig. 6) of the main memory unit 302 of the server 30. Then, the main control unit (computer) 302 of the server 30 refers to the type data and recognizes that the event notification at this time belongs to type 2. Therefore, the main control unit 302 determines "YES" in step S1 of Fig. 8, and in steps S3 and S5, according to the destination list for the event notification of type 2 stored in the destination list storage area 744, it transmits the event notification data (including the type data) to the user terminals 40 of all users and all multifunction devices 20.

[0115] Therefore, the main control unit (computer) 212 of the multifunction device 20 stores the received event notification data, together with the type data, in the event data storage area 650 according to the event processing program 632 (Fig. 5).

[0116] Also in the user terminal 40, the main control unit (computer) 402 stores the received event notification data, together with the type data, in the transmission / reception data storage area 846 that also functions as an event data storage area according to the event processing program 828 (Fig. 7).

[0117] Then, the main control unit (computer) 402 displays a pop-up 416 on the display screen 414 of the display 408a according to the display control program 822, and displays an event notification 418 with the content 'There is received data. Sender: 123-456-7890', a detail button 420, and a close button 422 inside the pop-up 416. This detail button 420 is a software button for operating when checking (marking as read) the details of the event notification, and is operated on the touch panel 410a. This close button 422 is a software button for operating when closing the event notification 418 after checking (marking as read) the details of the event notification, and is operated on the touch panel 410a.

[0118] When the detail button 420 or the close button 422 is operated by the user, the main control unit 402 determines that the event notification 418 has been confirmed by the user (FIG. 10: step S53), and transmits the read information to the server 30.

[0119] This read information is transmitted from the server 30 to the multifunction device 20 (FIG. 8: step S13).

[0120] In response to this, the main control unit 212 of the multifunction device 20 determines "YES" in step S29 shown in FIG. 9, and stores this read information in the event data storage area 650 (FIG. 5).

[0121] Based on the type data included in the previously stored event data, the main control unit 212 of the multifunction device 20 determines that the current event notification belongs to type 2 and that even if it is confirmed (read) on the user terminal 40, it needs to be confirmed on the multifunction device 20 ( "YES" in step S37). Therefore, in step S39, the main control unit 212 displays a pop-up 226 including the event notification 228 on the display screen 224 of the display 218a according to the display control program 622 (FIG. 6) for the event notification data (including type data) stored in the transmission / reception data storage area 742 (FIG. 6) in step S23, and also displays the yes button 232 and the no button 234. The yes button 232 and the no button 234 are software buttons for responding to the content of the event notification 228 at this time, "There is received data. Do you want to check it?", and are operated on the touch panel 220a.

[0122] Thus, in the case of an event belonging to type 2, not only is the user terminal 40 as a personal device made to check the notification content, but the user must also operate the multifunction device 20 to cancel the event notification factor. Therefore, regardless of the presence or absence of read information on the user terminal 40, the event content is displayed in step S39.

[0123] In the embodiment of FIG. 12, the event notifications distributed to the multifunction machine 20 and those distributed to the user terminal 40 are not the same, but since they are event notifications with a similar gist, they can be referred to as the same event notification.

[0124] FIG. 13 shows a case where an event belonging to type 2 is distributed from the server 30 to both the multifunction machine 20 and the user terminal 40. FIG. 13(A) shows an example of the display screen 224 of the display 218a of the multifunction machine 20, and FIG. 13(B) shows an example of the display screen 414 of the display 408a of the user terminal 40. The event notification shown in FIG. 13 is the "paper removal notification after printing of print data" belonging to type 2 described above.

[0125] The target of the notification of this "paper removal notification after printing of print data" event may be only a specific target user who has sent the print data. Not only should the user terminal 40 (personal device) be used to check the notification content, but the target user must also cancel the notification by operating the multifunction machine 20.

[0126] When the printing of the print data is completed, the main control unit (computer) 212 determines "YES" in step S21 which determines whether an event has been detected. Then, in step S23, an event distribution request for distributing the detected event is sent to the server 30. At this time, data of an event of "paper removal notification after printing of print data" and type data of the event notification data (in this case, type 2) are sent to the server 30. However, the event notification data at this time includes user information that can identify the user who has sent the print data.

[0127] On one hand, this event notification data, together with the type data, is stored in the transmission / reception data storage area 742 (Fig. 6) of the main memory unit 302 of the server 30. Then, the main control unit (computer) 302 of the server 30 refers to the type data and recognizes that the event notification at this time belongs to type 2. Therefore, the main control unit 302 determines "YES" in step S1 of Fig. 8, and in steps S3 and S5, according to the destination list for the event notifications of type 2 stored in the destination list storage area 744, it transmits the event notification data (including the type data) to the user terminal 40 and the multifunction device 20 of the user indicated by the user information included in the event notification data.

[0128] Therefore, the main control unit (computer) 212 of the multifunction device 20 stores the received event notification data, together with the type data, in the event data storage area 650 according to the event processing program 632 (Fig. 5).

[0129] Also in the user terminal 40 of the user indicated by the above user information, the main control unit (computer) 402 stores the received event notification data, together with the type data, in the transmission / reception data storage area 846 that also functions as an event data storage area according to the event processing program 828 (Fig. 7).

[0130] Then, the main control unit (computer) 402 displays a pop-up 416 on the display screen 414 of the display 408a according to the display control program 822, and displays an event notification 418 with the content "Printed data has been printed. Please remove the paper." and an OK button 424 inside the pop-up 416. This OK button 424 is a software button for operating when the content of the event notification is confirmed (read), and is operated by the touch panel 410a.

[0131] When this OK button 424 is operated by the user, the main control unit 402 determines that the event notification 418 has been confirmed by the user (Fig. 10: step S53), and transmits the read information to the server 30.

[0132] This read information is transmitted from the server 30 to the multifunction device 20 (FIG. 8: step S13).

[0133] In response to this, the main control unit 212 of the multifunction device 20 determines "YES" in step S29 shown in FIG. 9, and stores this read information in the event data storage area 650 (FIG. 5).

[0134] Based on the type data included in the event data stored previously, the main control unit 212 of the multifunction device 20 determines that this event notification belongs to type 2, and even if it is confirmed (read) on the user terminal 40, it is necessary to confirm it on the multifunction device 20 ( "YES" in step S37). Therefore, in step S39, the main control unit 212 displays a popup 226 including an event notification 228 on the display screen 224 of the display 218a in accordance with the display control program 622 (FIG. 6), along with an OK button 236, for the event notification data (including type data) stored in the transmission / reception data storage area 742 (FIG. 6) in step S23. The OK button 236 is a software button for operating when the paper is removed after confirming the content of the event notification 228 at this time, "Printed print data. Please remove the paper.", and is operated on the touch panel 220a.

[0135] Also in this case, not only let the user terminal 40 as a personal device confirm the notification content, but also the multifunction device 20 must be operated to cancel the event notification factor. Therefore, regardless of the presence or absence of read information on the user terminal 40, the event content is displayed in step S39.

[0136] Note that in the embodiment of FIG. 13, the event notification distributed to the multifunction device 20 and the event notification distributed to the user terminal 40 are the same, but they do not necessarily have to be the same. As long as they are event notifications with a similar meaning, they can also be regarded as the same event notification in this case.

[0137] Fig. 14 shows a case where an event belonging to type 2 is distributed from the server 30 to both the multifunction device 20 and the user terminal 40, Fig. 14(A) shows an example of the display screen 224 of the display 218a of the multifunction device 20, and Fig. 14(B) shows an example of the display screen 414 of the display 408a of the user terminal 40. The event notification shown in Fig. 14 is a "toner out notification" belonging to type 2.

[0138] The target of notification of this "toner out notification" event is everyone, including general users, but the cause of the notification is canceled by the administrator of the multifunction device 20. Therefore, while it is sufficient for general users to check on either the user terminal (personal device) 40 or the multifunction device 20, the administrator needs to not only notify the user terminal 40 but also cancel the cause of the notification by operating the multifunction device 20.

[0139] When a toner out signal is input to main control unit (computer) 212 from a toner sensor (not shown) through I / O unit 210, "YES" is determined in step S21, which determines whether an event has been detected. Then, in step S23, an event distribution request for distribution of the detected event is sent to server 30. At this time, data on the event, a toner out notification, and type data of the event notification data (type 2 in this case) are sent to server 30.

[0140] Meanwhile, this event notification data is stored together with the type data in the transmission / reception data storage area 742 (FIG. 6) of the main memory unit 302 of the server 30. Then, the main control unit (computer) 302 of the server 30 refers to the type data and recognizes that the event notification at this time belongs to type 2. Therefore, the main control unit 302 judges "YES" in step S1 of FIG. 8, and in steps S3 and S5, transmits the event notification data (including the type data) to the user terminals 40 and multifunction peripherals 20 of all users according to the distribution destination list for event notifications of type 2 stored in the distribution destination list storage area 744.

[0141] Therefore, the main control unit (computer) 212 of the multifunction device 20 stores the received event notification data together with the type data in the event data storage area 650 according to the event processing program 632 (Fig. 5).

[0142] Also in the user terminal 40 of the user indicated by the above user information, the main control unit (computer) 402 stores the received event notification data together with the type data in the transmission / reception data storage area 846 that also functions as an event data storage area according to the event processing program 828 (Fig. 7).

[0143] Then, according to the display control program 822, the main control unit (computer) 402 displays a pop-up 416 on the display screen 414 of the display 408a, and displays an event notification 418 with the content "K color toner is out" and a detail button 420 inside the pop-up 416. This detail button 420 is a software button for operating when the details of the event notification are confirmed (read), and is operated by the touch panel 410a.

[0144] When this detail button 420 is operated by the user, the main control unit 402 determines that the event notification 418 has been confirmed by the user (Fig. 10: step S53), and transmits the read information to the server 30.

[0145] This read information is transmitted from the server 30 to the multifunction device 20 (Fig. 8: step S13).

[0146] Accordingly, the main control unit 212 of the multifunction device 20 determines "YES" in step S29 shown in Fig. 9, and stores this read information in the event data storage area 650 (Fig. 5).

[0147] Based on the type data included in the previously stored event data, the main control unit 212 of the multifunction machine 20 determines that the current event notification belongs to type 2 and needs to be confirmed by the multifunction machine 20 even if it has been confirmed (read) on the user terminal 40 ( "YES" in step S37). Therefore, in step S39, the main control unit 212 displays a pop-up 226 including an event notification 228 on the display screen 224 of the display 218a and also displays an OK button 236 in accordance with the display control program 622 (FIG. 6) for the event notification data (including type data) stored in the transmission / reception data storage area 742 (FIG. 6) in step S23. The OK button 236 has software button data for operating when the toner cartridge is replaced after confirming the content of the event notification 228 at this time, "Please replace the toner cartridge. (□□□□)", and is operated on the touch panel 220a.

[0148] In this case as well, not only should the user terminal 40 as a personal device be made to check the notification content, but the multifunction machine 20 also needs to be operated to cancel the event notification factor. Therefore, regardless of the presence or absence of read information on the user terminal 40, the event content is displayed in step S39.

[0149] In the embodiment of FIG. 14, although the event notifications distributed to the multifunction machine 20 and the event notifications distributed to the user terminal 40 are not the same, they are event notifications with the same general meaning, so they can be referred to as the same event notification.

[0150] In the above-described embodiment, a server 30 is provided to distribute event notifications. However, the functions of this server 30 can be incorporated into the multifunction machine 20 to omit the server 30. In this case, the flowchart of FIG. 8 can be incorporated into the event processing program 632 (FIG. 5) of the multifunction machine 20, and the operation of the main control unit (computer) 302 of the server 30 can be taken over by the main control unit (computer) 212 of the multifunction machine 20.

Explanation of Reference Numerals

[0151] 10 … Information processing system 20 … Multifunction device 30 … Server 40 … User terminal 50 … Network 212, 302, 402 … Main control unit 212a, 302a, 402a … Main memory 208, 304, 406 … Communication unit 218a, 408a … Display

Claims

1. An event notification receiving unit that receives the same event notifications as the user terminal, A display unit that displays the received event notifications, A read information receiving unit that receives read information indicating that the user terminal has confirmed the event notification, and An event processing unit that executes different processes for the event notification based on whether the read information receiving unit has received the read information, The event processing unit controls whether to redisplay the event notification for which the read information has been received on the display unit according to whether the event notification for which the read information has been received by the read information receiving unit is an event notification that requires re-notification even after being read on the user terminal. An information processing apparatus.

2. The event notification includes a first event notification and a second event notification of a type different from the first event notification, When the event notification received by the event notification receiving unit is the first event notification, the event processing unit does not display the first event notification on the display unit when the read information receiving unit receives the read information. The information processing apparatus according to Claim 1.

3. When the event notification received by the event notification receiving unit is the second event notification, the event processing unit displays the second event notification on the display unit even if the read information receiving unit has received the read information. The information processing apparatus according to Claim 2.

4. An event notification receiving unit that receives the same event notifications as the user terminal, A display unit that displays the received event notifications, A read information receiving unit that receives read information indicating that the user terminal has confirmed the event notification, and An event processing unit that executes different processes for the event notification based on whether the read information receiving unit has received the read information, The event notification includes a first event notification and a second event notification of a type different from the first event notification, When the event notification received by the event notification receiving unit is the second event notification, the event processing unit displays the second event notification on the display unit even if the read information receiving unit has received the read information. An information processing apparatus.

5. An information processing method in an information processing apparatus, comprising: An event notification receiving step of receiving the same event notifications as the user terminal, A display step of displaying the received event notifications, A read information receiving step of receiving read information indicating that the user terminal has confirmed the event notification, and An event processing step of performing different processes regarding the event notification based on whether the read information is received in the read information receiving step, In the event processing step, for the event notification for which the read information is received in the read information receiving step, depending on whether it is an event notification that requires re-notification even after being read on the user terminal, controls whether to re-display the event notification for which the read information is received in the display step. An information processing method.

Images