Server, computer program for server, and method executed by server

Abstract

To provide a technique capable of appropriately presenting notification information about a service provided by a server.SOLUTION: The server includes a first acquisition unit configured to acquire print history information indicating a print history in the printer, the print history information including a plurality of pieces of print log information corresponding to a plurality of times of printing, each of the plurality of pieces of print log information including user information for identifying a user who causes the printer to execute printing and device information indicating a device used by the user to cause the printer to execute printing, a first determination unit configured to determine a specific user who uses the plurality of pieces of print log information most frequently, and a first display control unit configured to cause the specific device to display first notification information related to a service provided by the server.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present specification relates to a technology relating to a server capable of providing a service. [Background technology]

[0002] Patent Document 1 discloses a technique for calculating a fee corresponding to a fee plan using log information of image processing executed by an image processing device, and presenting notification information relating to the fee to a user.

[0003] Furthermore, Patent Document 2 discloses a service for delivering consumables for a printing device. The printing device in Patent Document 2 determines whether or not a service contract has been made when the remaining amount of consumables used for printing falls below a predetermined threshold. If it is determined that a service contract has been made, a request for delivery of the consumables is made, and if it is determined that a service contract has not been made, a screen prompting the user to make a contract for the service is displayed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-035779 [Patent Document 2] Japanese Patent Publication No. 2020-111023 Summary of the Invention [Problem to be solved by the invention]

[0005] The technology of Patent Document 2 simply displays a screen prompting a user to sign up for a service contract if it is determined that the service contract has not been signed up for. When a screen prompting a user to sign up for a service contract is displayed in an environment where multiple users use a printing device, such a screen may be displayed to a user who has no authority over the maintenance and management of the printing device. This is insufficient to make a user who has authority over the maintenance and management of the printing device, including the service contract, aware of the service contract. This specification provides a technology that can appropriately present notification information about services provided by a server. [Means for solving the problem]

[0006] The server disclosed in this specification may include: a first acquisition unit that acquires print history information indicating the print history of a printer used by multiple users, the print history information including multiple pieces of print log information corresponding to multiple prints performed by the printer, the first acquisition unit including user information that identifies the user who caused the printer to perform the print corresponding to the print log information, and device information that indicates the device used by the user to cause the printer to perform the print; a first determination unit that uses the multiple pieces of print log information included in the print history information to determine a specific user among the multiple users who has caused the printer to perform the print the most times; a second determination unit that uses the multiple pieces of print log information included in the print history information to determine a specific device that has been used the most times by the specific user; and a first display control unit that displays first notification information regarding services provided by the server on the specific device.

[0007] According to the above configuration, the server uses multiple pieces of print log information to determine the specific user who has most frequently printed on the printer, and determines the specific device that has most frequently been used by the specific user. The server then displays first notification information about the service provided by the server on the specific device. Therefore, the server can appropriately present the notification information.

[0008] Another server disclosed in this specification may include a first acquisition unit that acquires print history information indicating the print history of a printer used by multiple users, the print history information including multiple pieces of print log information corresponding to multiple prints performed by the printer, and each of the multiple pieces of print log information including user information identifying the user who caused the printer to perform the print corresponding to the print log information; a first determination unit that uses the multiple pieces of print log information included in the print history information to determine a specific user among the multiple users who has caused the printer to perform printing the most times; and a first display control unit that, if the specific user is an administrator of the printer, displays first notification information regarding services provided by the server on a specific device used by the specific user, and does not display the first notification information on the specific device if the specific user is not the administrator.

[0009] According to the above configuration, the server uses multiple pieces of print log information to determine the specific user who has most frequently printed on the printer. If the specific user is an administrator, the server then displays first notification information about the services provided by the server on a specific device used by the specific user. If the specific user is not an administrator, the server does not display the first notification information on the specific device. Therefore, the server can appropriately present the notification information.

[0010] A computer program for the server, a computer-readable recording medium for storing the computer program, and a method executed by the server are also novel and useful. Also novel and useful is a system including the server, a printer, and a specific device. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a configuration diagram of a communication system. [Figure 2]FIG. 2 is a diagram illustrating the hardware configuration of each device. [Figure 3] FIG. [Figure 4] FIG. 2 is a sequence diagram of the first embodiment. [Figure 5] This is a sequence diagram for case A. [Figure 6] FIG. 10 is a sequence diagram of cases B and C. [Figure 7] FIG. 10 is a sequence diagram of case D. [Figure 8] FIG. 10 is a sequence diagram of a second embodiment. [Figure 9] FIG. 11 is a sequence diagram of a third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (Configuration of communication system 2; Figure 1) 1, the communication system 2 includes a printer 10, a plurality of PCs 100X and 100Y, a plurality of mobile devices 200X and 200Y, a service server 300, and a log server 400. The PC 100X and the mobile device 200X are devices used by a user XXX. The PC 100Y and the mobile device 200Y are devices used by a user YYY. The communication system 2 may further include devices such as PCs and mobile devices used by other users (e.g., user ZZZ).

[0013] Each of the devices 100X, 100Y, 200X, 200Y, and 400 is configured to be able to communicate with the printer 10 via a local area network (LAN). The LAN may be a wired LAN or a wireless LAN. The printer 10 is also configured to be able to communicate with the service server 300 via the Internet 6. In particular, a server-push type permanent connection is established between the printer 10 and the service server 300. The permanent connection is, for example, an Extensible Messaging and Presence Protocol (XMPP) connection.

[0014] (Configuration of printer 10; Figure 2) Next, the configuration of each device constituting the communication system 2 will be described with reference to FIG. 2. The printer 10 is a peripheral device capable of executing a printing function, such as a PC 100X or a mobile device 200X. In a modified example, the printer 10 may be a multi-function device capable of executing a scanning function, a facsimile function, etc. in addition to the printing function. The printer 10 includes an operation unit 12, a display unit 14, a communication interface 16, a print execution unit 18, and a control unit 30. Each unit 12 to 30 is connected to a bus line. Hereinafter, the interface will be referred to as "I / F."

[0015] The operation unit 12 is a user interface that allows a user to input various information to the printer 10. The operation unit 12 includes, for example, a touch panel for displaying software keys (operation objects), hardware keys, or both. The hardware keys include, for example, buttons, switches, etc. The user can input various information to the printer 10 via the operation unit 12. The display unit 14 is a display or panel for displaying various information. The panel may or may not be a touch panel. The panel is, for example, a liquid crystal panel or an organic EL panel. The communication I / F 16 is connected to a LAN and the Internet 6. The print execution unit 18 includes an inkjet, electrophotographic, or thermal print engine.

[0016] The control unit 30 includes a CPU 32 and a memory 34. The memory 34 includes a main storage device and an auxiliary storage device. As an example, the main storage device includes a RAM and a cache memory. As an example, the auxiliary storage device may be a ROM, a flash memory, a solid state drive (SSD), a hard disk drive (HDD), or a combination thereof. A program 36 is stored in the auxiliary storage device of the memory 34. The CPU 32 performs various processes in accordance with the program 36 loaded from the auxiliary storage device to the main storage device.

[0017] (PC100X, 100Y configuration) Each of the PCs 100X and 100Y is a desktop PC, a laptop PC, or the like. The configuration of the PC 100X is similar to that of the PC 100Y, so the configuration of the PC 100X will be described below. The PC 100X includes an operation unit 112, a display unit 114, a communication I / F 116, and a control unit 130. Each of the units 112 to 130 is connected to a bus line.

[0018] The operation unit 112 is a user interface that enables a user to input various pieces of information to the PC 100X. The operation unit 112 includes, for example, a touch panel for displaying software keys (operation objects), hardware keys, or both. The hardware keys include, for example, buttons, switches, etc. The user can input various pieces of information to the PC 100X via the operation unit 112. The display unit 114 is a display or panel for displaying various pieces of information. The panel may or may not be a touch panel. The panel is, for example, a liquid crystal panel or an organic EL panel. The communication I / F 116 is connected to a LAN.

[0019] The control unit 130 includes a CPU 132 and a memory 134. The memory 134 includes a main storage device and an auxiliary storage device. For example, the main storage device includes a RAM and a cache memory. For example, the auxiliary storage device may be a ROM, a flash memory, an SSD, an HDD, or a combination thereof.

[0020] An OS program 136 and an application program 138 are stored in the auxiliary storage device of the memory 134. Hereinafter, the OS program and the application program will be referred to as "OS" and "app," respectively. The OS 136 controls the basic operations of the PC 100X. As an example, the app 138 causes a printer (e.g., 10) to execute a printing function. The CPU 132 performs various processes in accordance with programs loaded from the auxiliary storage device to the main storage device. Hereinafter, various processes performed by the CPU 132 in accordance with the programs may be described as being performed primarily by the OS 136 or the app 138.

[0021] (Mobile 200X, 200Y configuration) Each of the mobiles 200X and 200Y is a portable terminal device such as a mobile phone, a smartphone, a PDA, or a tablet PC. The configuration of the mobile 200X is similar to that of the mobile 200Y, so the configuration of the mobile 200X will be described below. The mobile 200X includes an operation unit 212, a display unit 214, a communication I / F 216, and a control unit 230. Each of the units 212 to 230 is connected to a bus line.

[0022] The operation unit 212 is a user interface that enables the user to input various pieces of information to the mobile 200X. The operation unit 212 includes, for example, a touch panel for displaying software keys (operation objects), hardware keys, or both. The hardware keys include, for example, buttons, switches, etc. The user can input various pieces of information to the mobile 200X via the operation unit 212. The display unit 214 is a display or panel for displaying various pieces of information. The panel may or may not be a touch panel. The panel is, for example, a liquid crystal panel or an organic EL panel. The communication I / F 216 is connected to a LAN.

[0023] The control unit 230 includes a CPU 232 and a memory 234. The memory 234 includes a main storage device and an auxiliary storage device. As an example, the main storage device includes a RAM and a cache memory. As an example, the auxiliary storage device may be a ROM, a flash memory, an SSD, an HDD, or a combination thereof.

[0024] An OS 236 and an application 238 are stored in the auxiliary storage device of the memory 234. The OS 236 controls the basic operations of the mobile 200X. As an example, the application 238 causes a printer (e.g., 10) to execute a printing function. The CPU 232 performs various processes in accordance with a program loaded from the auxiliary storage device to the main storage device. In the following, various processes performed by the CPU 232 in accordance with a program may be described as being performed primarily by the OS 236 or the application 238.

[0025] (Configuration of service server 300) The service server 300 is installed on the Internet 6 by the vendor of the printer 10 (hereinafter simply referred to as the "vendor"). The service server 300 may be a physical server, a virtual server on the cloud, a virtual machine, or the like. The service server 300 may be a single server or a collection of multiple servers. The service server 300 may be a cloud server on the Internet 6 or a server on an intranet. In a modified example, the service server 300 may be installed on the Internet 6 by a business operator other than the vendor. In another modified example, the vendor may not prepare the hardware for the service server 300 itself, but may use an environment provided by an external cloud computing service. In this case, the vendor may prepare a program (i.e., software) for the service server 300 and implement the program in the above-described environment to realize the service server 300. In this embodiment, as an example, a configuration in which the service server 300 is a physical server will be described.

[0026] The service server 300 is a server that provides printer-related services (e.g., subscription services). Subscription services include, for example, flat-rate printing services that allow printing on a specified number of print media for a fixed fee, and automatic shipping services for consumables (e.g., ink cartridges, toner cartridges, etc.). The service server 300 includes a communication I / F 316 and a control unit 330. The units 316 and 330 are connected to a bus line. The communication I / F 316 is connected to the Internet 6.

[0027] The control unit 330 includes a CPU 332 and a memory 334. The memory 334 includes a main storage device and an auxiliary storage device. As an example, the main storage device includes a RAM and a cache memory. As an example, the auxiliary storage device may be a ROM, a flash memory, an SSD, an HDD, or a combination thereof. A program 336 is stored in the auxiliary storage device of the memory 334. The CPU 332 performs various processes in accordance with the program 336 loaded from the auxiliary storage device to the main storage device. The auxiliary storage device of the memory 334 also stores a count table 338. Details of the count table 338 will be described later with reference to FIG. 3.

[0028] (Log Server 400 Configuration) The log server 400 is installed on a LAN (i.e., on an intranet) by the administrator of the printer 10. The log server 400 may also be installed on a LAN or on the Internet 6 by the vendor of the printer 10. The log server 400 may be a physical server, a virtual server on a cloud, a virtual machine, or the like. The log server 400 may be a single server or a collection of multiple servers. The log server 400 may be a server on an intranet or a cloud server on the Internet 6. In a modified example, the log server 400 may be installed on the Internet 6 by a business entity other than the administrator and vendor of the printer 10. In another modified example, the administrator or vendor may not prepare the hardware for the log server 400 themselves, but may use an environment provided by an external cloud computing service. In this case, the administrator or vendor may prepare a program (i.e., software) for the log server 400 and implement the log server 400 by installing it in the above-described environment. In this embodiment, as an example, a configuration in which the log server 400 is a physical server will be described.

[0029] The log server 400 stores information related to the printer 10 (for example, print log information showing the printing history of the printer 10, access log information showing the access history to the printer 10, etc.). The log server 400 includes a communication I / F 416 and a control unit 430. The units 416 and 430 are connected to a bus line. The communication I / F 416 is connected to a LAN.

[0030] The control unit 430 includes a CPU 432 and a memory 434. The memory 434 includes a main storage device and an auxiliary storage device. As an example, the main storage device includes RAM and cache memory. As an example, the auxiliary storage device may be a ROM, flash memory, SSD, HDD, or a combination thereof. A program 436 is stored in the auxiliary storage device of the memory 434. The CPU 432 performs various processes in accordance with the program 436 loaded from the auxiliary storage device to the main storage device. The auxiliary storage device of the memory 434 also stores a print log table 438 and an access log table 440. Details of each of the tables 438 and 440 will be described later with reference to FIG. 3.

[0031] (Contents of the frequency table; Figure 3) Next, with reference to FIG. 3, the tables 338, 438, and 440 will be described. The count table 338 is a table that stores, for each user, the total number of times the user has caused the printer 10 to print and the number of times the user has used the device to print on the printer 10. Here, "device" is classified into printer, mobile, and PC. "Printer" means that the printer 10 has been directly operated to cause the printer 10 to print (i.e., to perform a copy). "Mobile" means that a mobile (e.g., 200X) has sent a print instruction to the printer 10, causing the printer 10 to print. "PC" means that a PC (e.g., 100X) has sent a print instruction to the printer 10, causing the printer 10 to print. When the service server 300 receives multiple print logs from the log server 400, it updates the count table 338 based on the multiple print logs. A specific method for generating the count table 338 will be described later.

[0032] (Contents of print log table 438) The print log table 438 is a table that stores multiple print logs corresponding to multiple printing operations performed by the printer 10. Each print log stores a print date and time, a user ID, a device type, an IP address, and parameters in association with each other. The print date and time indicates the date and time when printing was performed by the printer 10. The user ID is information that identifies the user who caused the printer 10 to print. The device type indicates the device used by the user who caused the printer 10 to print. The IP address indicates the IP address of the device used by the user who caused the printer 10 to print (i.e., the IP address of the device that sent the print instruction). Note that if the device type is "printer (copy)," the printer 10 directly accepts copy operations from the user (i.e., does not receive print instructions via communication), so the IP address is not stored. The parameters include the printing conditions (e.g., number of copies, paper size, number of colors, etc.) when the printer 10 was caused to print. The log server 400 receives a print log from the printer 10 each time printing is executed in the printer 10 and stores it in a print log table 438 .

[0033] (Contents of access log table 440) The access log table 440 is a table that stores multiple access logs corresponding to multiple accesses to the printer 10. Each access log stored in the access log table 440 stores a user ID, a target menu, content, and a result in association with each other. The user ID is information that identifies the user who accessed the printer 10. The target menu indicates the menu selected when the access was performed (e.g., an administrator menu, a print setting menu, etc.). The content indicates the content of the processing performed in response to the access (e.g., a password change, a paper size change, etc.). The result indicates whether the processing was successful or unsuccessful. The log server 400 receives an access log from the printer 10 each time an access is performed to the printer 10 and stores it in the access log table 440.

[0034] (Processing performed between each device; Figure 4) Next, the processing executed between each device will be described with reference to Figure 4. Note that, in the following, for ease of understanding, the processing executed by the CPU (e.g., 32, etc.) of each device (e.g., printer 10, etc.) will be described as the processing subject, rather than each CPU being described as the processing subject. Also, communication between each device is executed via a communication I / F (e.g., 16, etc.). Therefore, in the following description, when describing communication, the phrase "via a communication I / F" will be omitted.

[0035] In T10, the mobile 200X accepts a print operation from the user XXX of the mobile 200X. The print operation includes, for example, designation of the printer 10 to which the print instruction is to be sent, designation of image data representing the image to be printed, designation of printing conditions (i.e., parameters), etc. In this case, the mobile 200X sends the print instruction to the printer 10 in T12. The print instruction includes a user ID that identifies the user XXX, information indicating that it is mobile printing (particularly the IP address IPMX of the mobile 200X), print data representing the image to be printed, and parameters. The user ID is pre-stored in the mobile 200X.

[0036] When the printer 10 receives a print instruction from the mobile 200X at T12, it causes the print execution unit 18 to print an image represented by the print data included in the print instruction in accordance with the parameters included in the print instruction at T14. Then, the printer 10 sends a print log to the log server 400 at T20. The print log includes the print date and time, the user ID, information indicating that it is a mobile print (particularly the IP address IPMX of the mobile 200X), and parameters.

[0037] When the log server 400 receives the print log from the printer 10 in T20, it stores the received print log in the print log table 438 in T22 (that is, it updates the print log table 438).

[0038] Thereafter, in T30, the printer 10 accepts a copy operation from the user XXX. The copy operation includes placing the document to be copied on the printer 10, inputting a user ID, specifying copy conditions (i.e., parameters), and the like. In this case, in T32, the printer 10 causes a scan execution unit (not shown) to scan the document to be copied, and causes the print execution unit 18 to print the scanned image represented by the scan data. Then, in T40, the printer 10 transmits a print log to the log server 400. The print log includes the print date and time, the user ID, information indicating that it is a copy, and parameters.

[0039] Thereafter, at a predetermined timing (for example, once a month), at T50, the service server 300 transmits a print log request to the log server 400. The print log request is a signal requesting the log server 400 to transmit multiple print logs included in the print log table 438.

[0040] When the log server 400 receives a print log request from the service server 300 at T50, it transmits the multiple print logs contained in the print log table 438 and the multiple access logs contained in the access log table 440 to the service server 300 at T52.

[0041] When service server 300 receives multiple print logs and multiple access logs in T52, it executes the following processes of T54 to T64. First, in T54, service server 300 updates count table 338 based on the multiple print logs it has received. Specifically, service server 300 identifies one print log that has not yet been processed from the multiple print logs, and identifies the user ID and device type included in that print log. For example, if print log table 438 is the example shown in FIG. 3, service server 300 first identifies user ID of user XXX and device type "printer" from the print log in the second row. Then, service server 300 increments by 1 the total number of times and the number of times the printer has been used in the row corresponding to the identified user ID. Furthermore, for example, service server 300 identifies user ID of user XXX and device type "mobile" from the print log in the third row of print log table 438. In the row corresponding to the identified user ID, the service server 300 increments both the total number of times and the number of times the mobile device has been used by 1. The service server 300 sequentially performs the same process as above for each print log that has not yet been processed, thereby updating the number of times table 338.

[0042] Next, in T60, the service server 300 determines the user who has caused the printer 10 to print the most (hereinafter referred to as the "most frequent user"). Specifically, the service server 300 identifies the user with the largest total number of times in the count table 338 as the most frequent user. For example, if the count table 338 is the example shown in FIG. 3, user XXX is determined to be the most frequent user.

[0043] Next, in T62, the service server 300 determines the device that has been used the most times by the identified most frequently used user (hereinafter referred to as the "most frequently used device"). Specifically, the service server 300 identifies the device that has the most frequently used count corresponding to the most frequently used user as the most frequently used device in the generated count table 338. For example, when the count table 338 is the example illustrated in FIG. 3, the mobile 200X is determined as the most frequently used device.

[0044] Next, in T64, the service server 300 uses the multiple access logs it has received to determine user XXX as the administrator of the printer 10. Specifically, the service server 300 identifies, from the multiple access logs, an access log corresponding to access permitted only to the administrator. For example, if the access log table 440 is the example shown in FIG. 3, the service server 300 identifies an access log containing "Administrator Menu" as an access log corresponding to access permitted only to the administrator. The service server 300 then determines user XXX, whose user ID is included in that access log, as the administrator of the printer 10. In this way, the service server 300 can determine the most popular users and most popular devices, and also determine user XXX as the administrator of the printer 10.

[0045] (Specific case A; Figure 5) Next, specific cases A to D according to the most common user and the most common device will be described with reference to Figures 5 to 7. First, case A will be described with reference to Figure 5. Figure 5 is a continuation of Figure 4. In case A, the most common user is user XXX, who is the administrator, and the most common device is mobile 200X.

[0046] In T100, the service server 300 transmits offer information to the printer 10 using the server-push constant connection established between the service server 300 and the printer 10. Because the most popular device is the mobile device 200X (i.e., the most popular device is not the printer 10), the offer information includes first screen information representing an offer screen SC10 for the administrator. If the most popular device is the printer 10, the offer information includes second screen information different from the first screen information (see T300 in FIG. 6). The offer information further includes information (i.e., IP address IPMX) indicating the most popular device (i.e., the mobile device 200X) and timing information. The timing information indicates the timing at which the offer screen SC10 should be displayed on the mobile device 200X, which is the most popular device. In this case, the timing information indicates the timing at which a print operation was performed on the mobile device 200X.

[0047] In T100, the printer 10 receives offer information from the service server 300. In this case, in T102, the printer 10 transmits the offer information, including the first screen information and timing information, to the mobile 200X, addressed to the IP address IPMX included in the offer information. In this way, the service server 300 can transmit the offer information to the mobile 200X via the printer 10 by using a server-push-type constant connection with the printer 10.

[0048] When the mobile 200X receives the offer information from the printer 10 in T102, the mobile 200X stores the offer information in the memory 234 of the mobile 200X in T104.

[0049] Thereafter, when the mobile 200X accepts a print operation from the user XXX in T110, it sends a print instruction to the printer 10 in T112. The processes of T110 and T112 are similar to the processes of T10 and T12 in FIG. 4, except that the print data and parameters may differ.

[0050] When the printer 10 receives a print instruction from the mobile 200X in T112, it causes the print execution unit 18 to print an image represented by the print data included in the print instruction in accordance with the parameters included in the print instruction in T114. When the printer 10 executes printing, it sends a print log to the log server 400 (not shown). As a result, the print log table 438 is updated in the log server 400. In the following description of the first embodiment, the description of sending a print log to the log server 400 when the printer 10 executes printing will also be omitted.

[0051] Furthermore, when the mobile 200X accepts a print operation in T110, since offer information including timing information indicating the print operation has already been stored in the memory 234, in T120 the mobile 200X uses the first screen information to display an offer screen SC10 having a pop-up display format on the display unit 214 of the mobile 200X. The offer screen SC10 includes a message indicating that there are cost benefits to using the subscription service, various information related to the subscription service, and buttons for providing details of the subscription service (i.e., a print button and a send email button). The "various information related to the subscription service" includes information indicating the number of pages printed by each user on the printer 10 and information indicating the respective costs of subscribing to the subscription service and not subscribing to it.

[0052] Here, if the offer information includes timing information indicating a print operation, the following advantages are obtained. For example, consider a comparative example in which the offer screen SC10 is displayed immediately when the offer information is received. In this comparative example, if the user is not operating the mobile 200X at the timing when the mobile 200X receives the offer information, there is a possibility that the offer screen SC10 will not be confirmed by the user XXX. On the other hand, according to the configuration of this embodiment, the offer screen SC10 is displayed at the timing when the user XXX performs a print operation, so the offer screen SC10 is more likely to be confirmed by the user XXX.

[0053] (Case A-1) Case A-1 will be described, in which the print button on the offer screen SC10 is selected. At T130, the mobile 200X accepts the selection of the print button included in the offer screen SC10 from the user XXX. In this case, at T132, the mobile 200X transmits a file request to the service server 300. The file request is a signal requesting the service server 300 to transmit a file (in this embodiment, a PDF file) representing a pamphlet describing the details of the subscription service.

[0054] When the service server 300 receives the file request from the mobile 200X in T132, the service server 300 transmits a PDF file representing the pamphlet to the mobile 200X in T134.

[0055] When the mobile 200X receives the PDF file from the service server 300 in T134, it sends a print instruction to the printer 10 in T136. This print instruction is similar to the print instruction of T12 in FIG. 4, except that it includes the PDF file as data to be printed and that the parameters may be different.

[0056] When the printer 10 receives a print instruction from the mobile 200X at T136, at T138, the printer 10 causes the print execution unit 18 to print the image (i.e., pamphlet) represented by the PDF file included in the print instruction in accordance with the parameters included in the print instruction. In this way, the user XXX, who is the administrator, can obtain a pamphlet for the subscription service by selecting the print button included in the offer screen SC10.

[0057] (Case A-2) Next, a case A-2 in which the email send button on the offer screen SC10 is selected will be described. In T140, the mobile 200X accepts selection of the email send button included in the offer screen SC10 from the user XXX. In this case, the mobile 200X displays an email address input screen (not shown) and accepts input of an email address from the user XXX in T142. Then, in T144, the mobile 200X transmits an email transmission request including the input email address to the service server 300. The email transmission request is a signal requesting the service server 300 to transmit an email to which is attached a file (in this embodiment, a PDF file) representing a pamphlet describing details of the subscription service.

[0058] When the service server 300 receives the email transmission request from the mobile 200X in T144, the service server 300 sends, in T146, an email with an attached PDF file representing the pamphlet, to the email address included in the email transmission request already received in T144. In this case, the email is sent to the mobile 200X.

[0059] At T146, the mobile 200X receives an email with a PDF file attached from the service server 300. In this way, the user XXX, who is the administrator, can obtain a brochure for the subscription service by selecting the email send button included in the offer screen SC10.

[0060] (Case B; Figure 6) Next, case B will be described with reference to FIG. 6. In case B, the most frequent user is user XXX who is the administrator, and the most frequent device is PC 100X. The processing of T200 in FIG. 6 is a continuation of the processing of FIG. 4. The processing of T200 is the same as the processing of the offer information of T100 in FIG. 5, except that the information indicating the most frequent device included in the offer information is different. Furthermore, the processing of T202 to T220 is the same as the processing of T102 to T110 in FIG. 5, except that the subject of the processing is PC 100X instead of mobile 200X. In case B, as in case A, user XXX who is the administrator can obtain a brochure of the subscription service in response to user XXX selecting the print button or email send button included in offer screen SC10 (not shown).

[0061] (Case C; Figure 6) Next, case C will be described with reference to FIG. 6. In case C, the most frequent user is user XXX, who is the administrator, and the most frequent device is printer 10. The processing of T300 in FIG. 6 is a continuation of the processing of FIG. 4. In T300, the service server 300 transmits offer information to the printer 10 using a server-push-type constant connection established between the service server 300 and the printer 10. Since the most frequent device is the printer 10, the offer information includes second screen information representing an offer screen SC20 for the administrator. The offer information further includes a user ID that identifies the most frequent user XXX, information indicating the most frequent device (i.e., the printer 10), and timing information. In particular, the offer information in this case includes the user ID. When the printer 10 accepts a copy operation, the user ID is used to determine whether the user who performed the copy operation is the most frequent user.

[0062] In T300, the printer 10 receives offer information from the service server 300. In this case, since the printer 10 is the most popular device, the printer 10 determines that the offer information should be stored in the memory 34. Then, in T302, the printer 10 associates the second screen information, the user ID, and the timing information included in the offer information with each other and stores them in the memory 34. The timing information indicates the timing at which a copy operation was performed by the user identified by the associated and stored user ID in the printer 10.

[0063] Thereafter, when the printer 10 receives a copy operation including input of the user ID from the user XXX in T304, the printer 10 causes the print execution unit 18 to execute copying (i.e., printing) in T306. The processes of T304 and T306 are similar to the processes of T30 and T32 in FIG. 4, except that the print data and parameters may differ.

[0064] Furthermore, when the printer 10 accepts a copy operation from the user XXX in T304, the user ID identifying the user XXX and timing information indicating the copy operation have already been stored in association with each other in the memory 34. Therefore, in T310, the printer 10 uses the second screen information to display an offer screen SC20 on the display unit 14. The offer screen SC20 includes a message indicating that the subscription service is available and a QR code obtained by encoding the URL indicating the location of the first screen information. QR code is a registered trademark of Denso Wave Inc.

[0065] The reason why the offer screen SC20 is displayed on the printer 10 instead of the offer screen SC10 is as follows. That is, the display unit 14 of the printer 10 is usually smaller than the display unit 114 of the PC 100X, the display unit 214 of the mobile device 200X, etc. That is, it is difficult to display the offer screen SC10, which describes detailed information, on the display unit 14 of the printer 10. For this reason, the offer screen SC20, which has a small amount of description, is displayed on the printer 10. In this way, in this embodiment, an appropriate offer screen is displayed according to the device on which the offer screen is to be displayed.

[0066] Thereafter, at T320, the user XXX uses the mobile device 200X to photograph the QR code included in the offer screen SC20 displayed on the printer 10. The mobile device 200X decodes the photographed QR code to obtain a URL. Then, at T322, the mobile device 200X transmits an offer screen request including the URL to the service server 300. Note that in a modified example, the service server 300 may transmit offer information including both the first screen information and the second screen information to the printer 10 at T300. The QR code included in the offer screen SC20 may be a QR code obtained by encoding a URL indicating the position of the first screen information. In this case, the mobile device 200X may transmit the offer screen request to the printer 10 at T322.

[0067] When the service server 300 receives the offer screen request from the mobile 200X at T322, the service server 300 transmits, at T324, the first screen information stored in the location indicated by the URL included in the offer screen request to the mobile 200X.

[0068] When the mobile 200X receives the first screen information from the service server 300 at T324, at T326, the mobile 200X displays the offer screen SC10 (see FIG. 5) on the display unit 214 of the mobile 200X. In this way, the user XXX can display a more detailed offer screen SC10 by photographing the QR code included in the offer screen SC20. In case C, as in case A, the user XXX selects the print button or the email send button included in the offer screen SC10, and in response, the user XXX, who is the administrator, can obtain a pamphlet of the subscription service (not shown).

[0069] (Case D; Figure 7) Next, case D will be described with reference to FIG. 7. FIG. 7 is a continuation of FIG. 4. In case D, the most frequent user is user YYY, who is a non-administrator, and the most frequent device is mobile 200Y. In T400, service server 300 transmits offer information to printer 10 using the constant connection established between service server 300 and printer 10. The offer information includes third screen information representing an offer screen SC30 for non-administrators. The offer information further includes information (i.e., IP address IPMY) indicating the most frequent device (i.e., mobile 200Y) and timing information. The timing information is information indicating the timing at which the offer screen SC30 should be displayed on mobile 200Y, which is the most frequent device. The timing information in this case indicates the timing at which a print operation was performed on mobile 200Y.

[0070] In T400, the printer 10 receives the offer information from the service server 300. In this case, in T402, the printer 10 transmits the offer information including the third screen information and timing information to the mobile 200Y, addressed to the IP address IPMY included in the offer information.

[0071] When the mobile 200Y receives the offer information from the printer 10 in T402, the mobile 200Y stores the offer information in the memory 234 of the mobile 200Y in T404.

[0072] Thereafter, when the mobile 200Y accepts a print operation from the user YYY in T410, it sends a print instruction to the printer 10 in T412. The processing of T410 and T412 is the same as the processing of T10 and T12 in Fig. 4, except that the subject of the processing is the mobile 200Y instead of the mobile 200X, and the print data and parameters may be different.

[0073] When the printer 10 receives the print instruction from the mobile 200Y in T412, in T414 the printer 10 causes the print execution unit 18 to print the image represented by the print data included in the print instruction in accordance with the parameters included in the print instruction.

[0074] Furthermore, when the mobile 200Y accepts the print operation in T410, since the offer information including timing information indicating the print operation has already been stored in the memory 234, in T420, the mobile 200Y uses the third screen information to display an offer screen SC30 having a pop-up display format on the display unit 214 of the mobile 200Y. The offer screen SC30 includes a message indicating that there are benefits to using the subscription service (in this case, a message indicating that consumables will be automatically delivered), a message urging the user to provide details of the subscription service to the administrator, and buttons for providing the details of the subscription service (i.e., a print button and a send email button). In Case D, selecting the print button included in the offer screen SC30 prints a pamphlet (see T130 to T138 in FIG. 5), and user YYY can provide the pamphlet to user XXX, the administrator (not shown). Furthermore, when the send email button included in the offer screen SC30 is selected, the email address of the administrator is entered by user YYY, and an email with a pamphlet attached is sent to the administrator's device (e.g., mobile 200X) (see T140 to T146 in FIG. 5). In this way, even when the offer screen SC30 is presented to user YYY, who is a non-administrator, user XXX can obtain the pamphlet of the subscription service.

[0075] (Effects of the first embodiment) According to the above configuration, the service server 300 uses multiple print logs to determine the user who has most frequently caused the printer 10 to execute printing (i.e., the most frequent user) (T60 in FIG. 4), and then determines the device that has been used most frequently by that user (i.e., the most frequent device) (T62 in FIG. 4). The service server 300 then displays the offer screen SC10 on the most frequently used device (T120 in FIG. 5, etc.). Therefore, the service server 300 can present the offer screen SC10, etc. to frequently used users via the frequently used device.

[0076] Furthermore, with the above configuration, the service server 300 uses multiple print logs to determine the user who has had the printer 10 print the most times (i.e., the most frequent user) (T60 in FIG. 4). If the most frequent user is an administrator, the service server 300 displays the offer screen SC10 on the device used by the most frequent user (T120 in FIG. 5), and if the most frequent user is not an administrator, the service server 300 displays the offer screen SC30, which is different from the offer screen SC10, on the device used by the most frequent user (T420 in FIG. 7). In this way, the service server 300 can present an appropriate offer screen depending on whether the most frequent user is an administrator or a non-administrator.

[0077] (Correspondence) The service server 300 and the printer 10 are examples of a "server" and a "printer," respectively. A PC (e.g., 100X) and a mobile device (e.g., 200X) are examples of a "terminal device." The print log table 438 and the access log table 440 are examples of "print history information" and "access history information," respectively. The user ID included in each print log is an example of "user information identifying the user who caused the printer to execute printing corresponding to the print log information." The device type and IP address included in each print log are an example of "device information." The user ID included in each access log is an example of "user information identifying the user who executed access corresponding to the access log information." The target menu included in each access log is an example of "type information." In case A, the user XXX, the mobile device 200X, and the offer screen SC10 are examples of a "specific user," a "specific device," and a "first notification information," respectively. In case B, the user XXX, the PC 100X, and the offer screen SC10 are examples of a "specific user," a "specific device," and a "first notification information," respectively. In case C, user XXX, printer 10, and offer screen SC20 are examples of a "specific user," "specific device," and "first notification information," respectively. In case D, user YYY, mobile 200Y, and offer screen SC30 are examples of a "specific user," "specific device," and "second notification information," respectively. The various information related to the subscription service included in offer screen SC10 is an example of "first (and third) information." The QR code included in offer screen SC20 is an example of "second information." A URL indicating the location of the offer information is an example of "location information." A brochure about the subscription service is an example of "detailed information." The print button and email send button included in offer screens SC10, SC30, etc. are examples of "objects for providing detailed information to an administrator."

[0078] The process of T52, the process of T60, the process of T62, and the process of T64 in Fig. 4 are examples of processes executed by the "first (and second) acquisition unit," the "first determination unit," the "second determination unit," and the "third determination unit," respectively. The process of T100 in Fig. 5 is an example of processes executed by the "first display control unit." The process of T400 in Fig. 7 is an example of processes executed by the "second display control unit."

[0079] (Second Example) Next, a second embodiment will be described. The second embodiment differs from the first embodiment in the method by which the service server 300 determines an administrator. As shown in FIG. 2, the log server 400 of the second embodiment stores an account table 442 instead of the access log table 440.

[0080] (Contents of Account Table 442; Figure 3) The account table 442 will be described with reference to Fig. 3. The account table 442 stores multiple pieces of account information for multiple users who use the printer 10. Each piece of account information is stored in association with a user ID and attribute information. The attribute information indicates the user's attribute (for example, administrator, general user, etc.).

[0081] (Processing performed between each device; Figure 8) Next, the processing executed between the devices of the second embodiment will be described with reference to Fig. 8. In Fig. 8, the same processes as those in Fig. 4 are denoted by the same reference numerals. Below, only the differences from the processing in Fig. 4 will be described, and a description of the same processes as those in Fig. 4 will be omitted.

[0082] When the log server 400 receives a print log request from the service server 300 at T50, it sends the multiple print logs contained in the print log table 438 and the multiple pieces of account information contained in the account table 442 to the service server 300 at T552.

[0083] In T564, the service server 300 uses the received multiple pieces of account information to determine user XXX as the administrator of the printer 10. Specifically, the service server 300 identifies, from the multiple pieces of account information, account information that includes the attribute information "administrator." For example, if the account table 442 is the example shown in FIG. 3, the service server 300 determines user XXX, who has a user ID included in the account information that includes the attribute information "administrator," as the administrator of the printer 10. In this way, the service server 300 can determine user XXX as the administrator of the printer 10. The user ID and attribute information included in each piece of account information are examples of "user information that identifies a user" and "attribute information," respectively. The processing of T552 and the processing of T564 in FIG. 8 are examples of processing executed by the "first (and third) acquisition unit" and the "fourth determination unit," respectively.

[0084] (Third embodiment; Figure 9) Next, a third embodiment will be described with reference to FIG. 9. The third embodiment differs from the first embodiment in that the administrator of the printer 10 is not determined by the service server 300. In FIG. 9, the same processes as those in FIG. 4 are denoted by the same reference numerals. Below, only the differences from the processes in FIG. 4 will be described, and a description of the processes that are the same as those in FIG. 4 will be omitted. In the third embodiment, first, the same processes as T10 to T42 in FIG. 4 are executed.

[0085] When the log server 400 receives a print log request from the service server 300 in T50, it transmits the multiple print logs included in the print log table 438 to the service server 300 in T652. In this case, the service server 300 executes the same processes as T54 to T62 in Fig. 4 to determine the most frequent user and the most frequent number of times. In the third embodiment, the service server 300 does not determine the administrator of the printer 10.

[0086] (Case E; Figure 9) Below, we will explain Case E, in which the most frequent user is user XXX, who is an administrator, and the most frequent device is mobile 200X. The processing of T700 is similar to the offer information of T100 in FIG. 5, except that the offer information includes fourth screen information representing offer screen SC40 including a button for allowing the user to select whether they are the administrator of printer 10. The processing of T702 is similar to the processing of T102 in FIG. 5, except that the fourth screen information is used. Furthermore, the processing of T704 to T714 is similar to the processing of T104 to T114 in FIG. 5, except that the print data and parameters used may differ.

[0087] Furthermore, when the mobile 200X accepts the print operation in T710, because offer information including timing information indicating the print operation has already been stored in the memory 234, in T720 the mobile 200X uses the fourth screen information to display an offer screen SC40 having a pop-up display format on the display unit 214 of the mobile 200X. The offer screen SC40 includes a message indicating that the subscription service is available, a message urging the user to provide details of the subscription service to the administrator, a button for selecting that the user is the administrator (i.e., an "I am the administrator" button), and buttons for providing details of the subscription service (i.e., a print button and an email send button).

[0088] In this case, since the most frequent user XXX is the administrator of the printer 10, the mobile 200X accepts the selection of the "I am the administrator" button from the user XXX in T730. In this case, the same processes as T322 to T326 in FIG. 6 are executed, and the offer screen SC10 (see FIG. 5) is displayed. The user XXX, who is the administrator, can select the print button or the email send button on the offer screen SC10 to obtain a brochure for the subscription service.

[0089] Furthermore, even if the most frequent user is a non-administrator, the most frequent user can provide the administrator user XXX with a pamphlet of the subscription service by selecting the print button or email send button in the offer screen SC40. That is, regardless of whether the offer screen SC40 is presented to an administrator or a non-administrator, the administrator user XXX can obtain the pamphlet of the subscription service. The offer screen SC40 is an example of an "inquiry screen." The print button and email send button in the offer screen SC40 are examples of "objects for providing detailed information to the administrator." The processing of T722 in FIG. 9 is an example of processing executed by the "third display control unit."

[0090] Although specific examples of the technology disclosed in this specification have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above examples are listed below.

[0091] (Variant 1) In each of the above embodiments, the service server 300 and the log server 400 are configured separately, but in a variant, the service server 300 and the log server 400 may be configured as an integrated unit.

[0092] (Variation 2) The service server 300 can omit the process of T62 in Fig. 4. In this case, the service server 300 can randomly determine one of the devices used by the most users (i.e., one of a PC, a mobile device, and a printer). In this variation, the "second determination unit" can be omitted.

[0093] (Variation 3) The mobile 200X may display an offer screen SC20 in place of the offer screen SC10 at T120 in FIG. 5. In this variation, when the "specific device is a terminal device," the "first notification information" may include "second information without including first information." Furthermore, the printer 10 may display an offer screen SC10 in place of the offer screen SC20 at T310 in FIG. 6. In this variation, when the "specific device is a printer," the "first notification information" may include "first information."

[0094] (Variation 4) A server-push connection may be established between the mobile 200X and the service server 300. In this case, the service server 300 may use the server-push connection to transmit offer information directly to the mobile 200X at T100 in Fig. 5 .

[0095] (Variation 5) The offer screen SC20 does not have to include a QR code. For example, the offer screen SC20 may include only a message indicating that a subscription service is available.

[0096] (Variation 6) The timing at which the offer screen SC10 and the like are displayed is not limited to the form of the above embodiment. For example, the mobile 200X may immediately display the offer screen SC10 when offer information is received from the printer 10. In another variation, the mobile 200X may display the offer screen SC10 when the app 238 is launched after offer information is received from the printer 10.

[0097] (Variation 7) The service server 300 may transmit offer information including the first screen information to the printer 10 at T400 in FIG. 7. In this case, the mobile 200Y may display the offer screen SC10 at T420 in FIG. 7. That is, the same offer screen may be displayed regardless of whether the most frequent user is an administrator or a non-administrator. In this variation, the "second display control unit" can be omitted.

[0098] (Variation 8) The offer screen SC30 may not include a message prompting the user to provide details of the subscription service to the administrator and buttons for providing the details of the subscription service (i.e., a print button and an email send button). In another variation, the offer screen SC30 may include a message prompting the user to provide details of the subscription service to the administrator, but may not include a button for providing details of the subscription service. In another variation, the offer screen SC30 may include a button for providing details of the subscription service, but may not include a message prompting the user to provide details of the subscription service to the administrator.

[0099] (Variation 9) The offer screen SC10 may not include various information about the subscription service and buttons for providing details of the subscription service (i.e., a print button and a send email button). In another variation, the offer screen SC10 may include various information about the subscription service but not include buttons for providing details of the subscription service. In another variation, the offer screen SC10 may include buttons for providing details of the subscription service but not include various information about the subscription service.

[0100] (Variant 10) If the most frequent user is a non-administrator user (e.g., YYY) and the most frequent device is printer 10, printer 10 may display an offer screen including a QR code obtained by encoding a URL indicating the location of third screen information representing offer screen SC30.

[0101] (Variant 11) In the above embodiment, the processing of each step in Figures 4 to 9 is realized by software (e.g., program 36, etc.), but at least one of these processes may also be realized by hardware such as a logic circuit.

[0102] The technical elements described in this specification or drawings may exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technologies illustrated in this specification or drawings may achieve multiple objectives simultaneously, and achieving one of those objectives alone is technically useful.

[0103] In the scope of the claims at the time of filing, even if each claim depends on only some of the claims, it is not limited to the fact that each claim can depend on only those some of the claims. To the extent that there is no technical contradiction, each claim can also depend on other claims that were not dependent at the time of filing. In other words, the technology of each claim can be combined in various ways as follows: (Item 1) a server, a first acquisition unit that acquires print history information indicating a print history of a printer used by multiple users, the print history information including multiple print log information corresponding to multiple prints executed by the printer, each of the multiple print log information including user information that identifies a user who caused the printer to execute the print corresponding to the print log information, and device information that indicates a device used by the user to cause the printer to execute the print; a first determination unit that determines, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by using the plurality of pieces of print log information included in the print history information; a second determination unit that determines a specific device that has been used most frequently by the specific user by using the plurality of pieces of print log information included in the print history information; a first display control unit that causes the specific device to display first notification information related to a service provided by the server; A server comprising: (Item 2) When the specific device is a terminal device used by the specific user, the first notification information includes first information regarding the service; When the specific device is the printer, the first notification information does not include the first information but includes second information different from the first information. The server described in item 1. (Item 3) the server establishes a server-push connection with the printer; the first display control unit, when the specific device is the terminal device, uses the server push connection to transmit the first notification information including the first information to the printer; 3. The server according to item 2, wherein the first notification information is transmitted from the printer to the specific device, which is the terminal device, and displayed on the specific device. (Item 4) 4. The server according to item 2 or 3, wherein the second information includes code information obtained by encoding location information representing a location where the first information is stored. (Item 5) The server described in any one of items 1 to 4, wherein the first display control unit displays the first notification information on the specific device when, after the specific user and the specific device have been determined, the specific user inputs an instruction to the specific device to cause the printer to perform printing. (Item 6) The first display control unit If the specific user is an administrator of the printer, displaying the first notification information regarding the service on the specific device; If the specific user is not the administrator, the first notification information is not displayed on the specific device. 6. The server according to any one of items 1 to 5. (Item 7) a server, a first acquisition unit that acquires print history information indicating the print history of a printer used by multiple users, the print history information including multiple pieces of print log information corresponding to multiple prints executed by the printer, and each of the multiple pieces of print log information including user information that identifies the user who caused the printer to execute the print corresponding to the print log information; a first determination unit that determines, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by using the plurality of pieces of print log information included in the print history information; a first display control unit that, when the specific user is an administrator of the printer, causes first notification information regarding the service to be displayed on a specific device used by the specific user, and does not cause the first notification information to be displayed on the specific device when the specific user is not the administrator; A server comprising: (Item 8) The server further The server described in item 6 or 7, further comprising a second display control unit that causes the specific device to display second notification information regarding the service, the second notification information being different from the first notification information, when the specific user is not the administrator of the printer. (Item 9) The server described in item 8, wherein the second notification information includes a message prompting the user to provide detailed information about the service details to the administrator, and an object for providing the detailed information to the administrator. (Item 10) A server described in any one of items 6 to 9, wherein the first notification information includes third information about the service and an object for providing the administrator with detailed information about the details of the service. (Item 11) The server described in any one of items 6 to 10, wherein the first display control unit displays the first notification information on the specific device when, after the specific user is determined, the specific user is the administrator and the specific user inputs an instruction to cause the printer to perform printing into the specific device. (Item 12) The server further a second acquisition unit that acquires access history information indicating a history of accesses to the printer, the access history information including a plurality of access log information corresponding to a plurality of accesses to the printer, each of the plurality of access log information including user information that identifies a user who performed an access corresponding to the access log information, and type information that indicates the type of the access; a third determination unit that determines, as the administrator, a user who has performed a specific access permitted only to the administrator, by using the plurality of pieces of access log information included in the access history information; 12. The server according to any one of items 6 to 11, comprising: (Item 13) The server further a third acquisition unit that acquires a plurality of pieces of account information of the plurality of users, the third acquisition unit acquiring a plurality of pieces of account information each including user information that identifies a user and attribute information that indicates an attribute of the user; a fourth determination unit that determines, as the administrator, a user that exhibits attributes of the administrator using the plurality of pieces of account information; 12. The server according to any one of items 6 to 11, comprising: (Item 14) The server further a third display control unit that causes an inquiry screen to be displayed on the specific device, the inquiry screen being a screen for inquiring of the specific user as to whether the specific user is the administrator; The server according to any one of items 6 to 11, wherein the first display control unit determines whether the specific user is the administrator depending on whether the specific user is input as the administrator on the inquiry screen. (Item 15) The server described in item 14, wherein the inquiry screen includes a message prompting the user to provide detailed information about the service details to the administrator, and an object for providing the detailed information to the administrator. [Explanation of symbols]

[0104] 2: Communication system, 6: Internet, 10: Printer, 12, 112, 212: Operation unit, 14, 114, 214: Display unit, 16, 116, 216, 316, 416: Communication I / F, 18: Print execution unit, 30, 130, 230, 330, 430: Control unit, 32, 132, 232, 332, 432: CPU, 34, 134, 234, 334, 434: Memory, 36, 336, 436: Program, 100X, 100Y: PC, 136, 236: OS program, 138, 238: Application program, 338: Number of times table, 438: Print log table, 440: Access log table, 442: Account table

Claims

1. a server, a first acquisition unit that acquires print history information indicating a print history of a printer used by multiple users, the print history information including multiple print log information corresponding to multiple prints executed by the printer, each of the multiple print log information including user information that identifies a user who caused the printer to execute the print corresponding to the print log information, and device information that indicates a device used by the user to cause the printer to execute the print; a first determination unit that determines, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by using the plurality of pieces of print log information included in the print history information; a second determination unit that determines a specific device that has been used most frequently by the specific user by using the plurality of pieces of print log information included in the print history information; a first display control unit that causes the specific device to display first notification information related to a service provided by the server; A server comprising:

2. When the specific device is a terminal device used by the specific user, the first notification information includes first information regarding the service; When the specific device is the printer, the first notification information does not include the first information but includes second information different from the first information. The server of claim 1 .

3. the server establishes a server-push connection with the printer; the first display control unit, when the specific device is the terminal device, uses the server push connection to transmit the first notification information including the first information to the printer; 3. The server according to claim 2, wherein the first notification information is transmitted from the printer to the specific device that is the terminal device and displayed on the specific device.

4. 3. The server according to claim 2, wherein the second information includes code information obtained by encoding location information representing a location where the first information is stored.

5. The server according to claim 1, wherein the first display control unit displays the first notification information on the specific device when, after the specific user and the specific device have been determined, the specific user inputs an instruction to the specific device to cause the printer to perform printing.

6. The first display control unit If the specific user is an administrator of the printer, displaying the first notification information regarding the service on the specific device; If the specific user is not the administrator, the first notification information is not displayed on the specific device. The server of claim 1 .

7. a server, a first acquisition unit that acquires print history information indicating a print history of a printer used by multiple users, the print history information including multiple pieces of print log information corresponding to multiple prints executed by the printer, and each of the multiple pieces of print log information including user information that identifies a user who caused the printer to execute the print corresponding to the print log information; a first determination unit that determines, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by using the plurality of pieces of print log information included in the print history information; a first display control unit that, when the specific user is an administrator of the printer, causes a specific device used by the specific user to display first notification information related to a service provided by the server, and does not cause the specific device to display the first notification information when the specific user is not the administrator; A server comprising:

8. The server further The server according to claim 6 or 7, further comprising a second display control unit that causes the specific device to display second notification information regarding the service, the second notification information being different from the first notification information, when the specific user is not the administrator of the printer.

9. The server according to claim 8 , wherein the second notification information includes a message prompting the user to provide detailed information about the service to the administrator, and an object for providing the detailed information to the administrator.

10. The server according to claim 6 or 7, wherein the first notification information includes third information about the service and an object for providing detailed information about the service to the administrator.

11. The server according to claim 6 or 7, wherein the first display control unit, after the specific user is determined, displays the first notification information on the specific device when the specific user is the administrator and the specific user inputs an instruction to cause the printer to perform printing into the specific device.

12. The server further a second acquisition unit that acquires access history information indicating a history of accesses to the printer, the access history information including a plurality of access log information corresponding to a plurality of accesses to the printer, each of the plurality of access log information including user information that identifies a user who performed an access corresponding to the access log information, and type information that indicates the type of the access; a third determination unit that determines, as the administrator, a user who has performed a specific access permitted only to the administrator, by utilizing the plurality of pieces of access log information included in the access history information; 8. The server according to claim 6 or 7, comprising:

13. The server further a third acquisition unit that acquires a plurality of pieces of account information of the plurality of users, the third acquisition unit acquiring a plurality of pieces of account information each including user information that identifies a user and attribute information that indicates an attribute of the user; a fourth determination unit that determines, as the administrator, a user who exhibits attributes of the administrator by using the plurality of pieces of account information; 8. The server according to claim 6 or 7, comprising:

14. The server further a third display control unit that causes an inquiry screen to be displayed on the specific device, the inquiry screen being a screen for inquiring of the specific user as to whether the specific user is the administrator; The server according to claim 6 or 7, wherein the first display control unit determines whether the specific user is the administrator depending on whether or not an input indicating that the specific user is the administrator is entered on the inquiry screen.

15. The server according to claim 14 , wherein the inquiry screen includes a message prompting the user to provide detailed information about the service to the administrator, and an object for providing the detailed information to the administrator.

16. A computer program for a server, comprising: The server computer is composed of the following parts: a first acquisition unit that acquires print history information indicating a print history of a printer used by multiple users, the print history information including multiple pieces of print log information corresponding to multiple prints executed by the printer, and each of the multiple pieces of print log information including user information that identifies a user who caused the printer to execute the print corresponding to the print log information; a first determination unit that determines, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by using the plurality of pieces of print log information included in the print history information; a first display control unit that, when the specific user is an administrator of the printer, causes a specific device used by the specific user to display first notification information related to a service provided by the server, and does not cause the specific device to display the first notification information when the specific user is not the administrator; A computer program that functions as a

17. 1. A method performed by a server, comprising: a first acquisition step of acquiring print history information indicating the print history of a printer used by a plurality of users, the print history information including a plurality of print log information corresponding to a plurality of prints executed by the printer, each of the plurality of print log information including user information identifying a user who caused the printer to execute the print corresponding to the print log information; a first determination step of determining, from among the plurality of users, a specific user who has caused the printer to execute printing the most times by utilizing the plurality of pieces of print log information included in the print history information; a first display control step of displaying first notification information related to a service provided by the server on a specific device used by the specific user when the specific user is an administrator of the printer, and not displaying the first notification information on the specific device when the specific user is not the administrator; A method comprising:

Images