Computer programs for servers, computer programs for terminal devices, methods for displaying screens on terminal devices, and communication systems

Abstract

We provide technology that improves user convenience regarding notification information. [Solution] In the first login state, the server receives a first generation request from the first terminal device, generates specific notification information corresponding to the notification identification information, and stores the specific account information, notification identification information, device identification information, and specific notification information in memory in association with each other. When the server receives a first request signal from the first terminal device, it sends the specific notification information associated with the specific account information to the first terminal device. The first terminal device displays the specific notification information. In the second login state, when the server receives a second request signal from the second terminal device, it sends the specific notification information associated with the specific account information to the second terminal device. The second terminal device displays the specific notification information.

Description

Technical Field

[0001] This specification discloses a technique for causing a terminal device to display notification information.

Background Art

[0002] Patent Document 1 discloses a communication system including a plurality of MFPs, a terminal device, a notification server, a service providing server, and a service management server. The terminal device transmits a pull notification information request to the notification server and receives pull notification information from the notification server. The terminal device stores the pull notification information received from the notification server in the memory of the terminal device. When the terminal device receives an operation on a button for displaying a notification list screen, the terminal device displays a notification list screen including a list of notification information stored in the memory of the terminal device.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] This specification provides a technique for improving the convenience of users regarding notification information.

Means for Solving the Problems

[0005] This specification discloses a computer program for a server. The computer program may cause the server's computer to function as a first generation request receiving unit that receives a first generation request from a first terminal device, in a first login state where the first terminal device is logged into the server using specific account information, the generation request includes notification identification information that identifies specific notification information and device identification information that identifies a specific communication device. The specific notification information may be information for notifying a user of the specific communication device of the existence of a service related to the specific communication device. The computer program may cause the computer to function as a first generation unit that generates the specific notification information corresponding to the notification identification information when the first generation request is received from the first terminal device. The computer program may cause the server's computer to function as a first storage control unit that stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory in association with each other after the specific notification information has been generated. The computer program may cause the server's computer to function as a first request signal receiving unit that receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information after the specific notification information has been generated. The computer program may cause the server's computer to function as a first notification information transmitting unit that transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device. The first terminal device may display the specific notification information when it receives the specific notification information from the server.The computer program may cause the server's computer to function as a second request signal receiving unit that receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information, after the specific account information, the notification identification information, the device identification information, and the specific notification information have been stored in memory in association with each other, and in a second login state in which a second terminal device different from the first terminal device is logged into the server using the specific account information. The computer program may cause the server's computer to function as a second notification information transmitting unit that transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device. The second terminal device may display the specific notification information when it receives the specific notification information from the server.

[0006] According to the above configuration, the server sends specific notification information to a first terminal device and a second terminal device that use specific account information. The first terminal device and the second terminal device then display the specific notification information. Therefore, user convenience regarding notification information is improved.

[0007] This specification also discloses a computer program for a terminal device. The computer program may cause the computer of the terminal device to function as a generation request transmission unit that sends a generation request to the server, which includes notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, when the terminal device is logged into the server using specific account information. The specific notification information may be information for notifying a user of the specific communication device of the existence of a service related to the specific communication device. When the server receives the generation request from the terminal device, it may generate the specific notification information corresponding to the notification identification information and store the specific account information, the notification identification information, the device identification information, and the specific notification information in memory in association with each other. The computer program may cause the computer to function as a request signal transmission unit that sends a request signal to the server after the generation request has been sent to the server, requesting the transmission of notification information associated with the specific account information. The computer program may cause the computer to function as a notification information transmission unit that receives the specific notification information associated with the specific account information at the server from the server after the request signal has been sent to the server. The computer program may also cause the computer to function as a display control unit that displays the specific notification information on the display unit of the terminal device when the specific notification information is received from the server.

[0008] According to the above configuration, the terminal device receives specific notification information associated with specific account information on the server and displays that specific notification information. Therefore, user convenience regarding notification information is improved.

[0009] Furthermore, this specification discloses a communication system. The communication system may include a generation request receiving unit that receives a generation request from a first terminal device in a first login state in which the first terminal device is logged into a server using specific account information, the generation request includes notification identification information that identifies specific notification information and device identification information that identifies a specific communication device. The specific notification information may be information for notifying a user of the specific communication device of the existence of a service related to the specific communication device. The communication system may include a generation unit that generates the specific notification information corresponding to the notification identification information when the generation request is received from the first terminal device. After the specific notification information has been generated, the communication system may include a first storage control unit that stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory in association with each other. After the specific notification information has been generated, the communication system may include a first request signal receiving unit that receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information. The communication system may include a first notification information transmission unit that transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device. The communication system may also include a first display control unit that displays the specific notification information on the display unit of the first terminal device when the specific notification information is received from the server. The communication system may also include a second request signal receiving unit that receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information in a second login state where the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and a second terminal device different from the first terminal device is logged into the server using the specific account information.The communication system may include a second notification information transmission unit that transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device. The communication system may also include a second display control unit that causes the specific notification information to be displayed on the display unit of the second terminal device when the specific notification information is received from the server.

[0010] According to the above configuration, specific notification information is sent to a first terminal device and a second terminal device that use specific account information. The first terminal device and the second terminal device then display the specific notification information. Therefore, user convenience regarding notification information is improved.

[0011] A computer-readable recording medium for storing a computer program for the above-mentioned server, a server implemented by the above-mentioned computer program, and a method for controlling the server are novel and useful. A method for displaying a screen on a terminal device is also novel and useful. Furthermore, a computer-readable recording medium for storing a computer program for the above-mentioned terminal device, a terminal device implemented by the above-mentioned computer program, and a method for controlling the terminal device are also novel and useful. A communication system comprising a server, a first terminal device, and a second terminal device is also novel and useful. Here, the above-mentioned recording medium may be a single medium or multiple mediums. [Brief explanation of the drawing]

[0012] [Figure 1] A diagram showing the configuration of a communication system. [Figure 2] This diagram shows the contents of the management table and the user table. [Figure 3] This diagram shows the contents of the first local table and the second local table. [Figure 4] This is a flowchart illustrating the merge process performed by the notification server. [Figure 5]It is a sequence diagram of Case A. [Figure 6] It is a figure showing the continuation of FIG. 5. [Figure 7] It is a figure showing the screen displayed on the mobile terminal in Case A. [Figure 8] It is a figure showing the screen displayed on the PC in Case A. [Figure 9] It is a figure showing the transition of the user table in Case A. [Figure 10] It is a figure showing the transition of the first local table in Case A. [Figure 11] It is a figure showing the transition of the second local table in Case A. [Figure 12] It is a sequence diagram of Case B. [Figure 13] It is a figure showing the continuation of FIG. 12. [Figure 14] It is a figure showing the transition of the user table in Case B. [Figure 15] It is a figure showing the transition of the first local table in Case B. [Figure 16] It is a figure showing the continuation of FIG. 15.

Mode for Carrying Out the Invention

[0013] (Example) (Configuration of Communication System 2; FIG. 1) As shown in FIG. 1, the communication system 2 includes a plurality of printers 10, 20, 30, a mobile terminal 100, a Personal Computer (PC) 200, a notification server 300, and a content server 400.

[0014] Printers 10, 20, 30, mobile terminal 100, and PC 200 are connected to LAN 4. Printers 10, 20, 30, mobile terminal 100, and PC 200 can communicate with each other via LAN 4. Notification server 300 and content server 400 are connected to Internet 6. Therefore, printers 10, 20, 30, mobile terminal 100, PC 200, notification server 300, and content server 400 can communicate with each other via Internet 6.

[0015] (Configuration of Printers 10, 20, 30) Printers 10, 20, 30 are peripheral devices capable of executing a printing function. Printers 10, 20, 30 are peripheral devices such as PC 200. Printers 10, 20, 30 include a printing mechanism capable of executing a printing function. The printing mechanism includes an inkjet, electrophotographic, or thermal printing engine. The inkjet printing engine includes a print head that discharges ink droplets. The electrophotographic printing engine includes a photoreceptor and an exposure device that emits light to expose the photoreceptor. The thermal printing engine includes a print head that generates heat by a heater.

[0016] Printer 10 has a serial number "SN1" and a model name "MN1". The serial number is an identification number assigned at the time of manufacturing the printer. The model name is a name indicating the model of the printer. Printer 20 has a serial number "SN2" and a model name "MN2". Printer 30 has a serial number "SN3" and a model name "MN3".

[0017] (Configuration of Mobile Terminal 100) Mobile terminal 100 is a portable terminal such as a mobile phone, PDA, or tablet PC. As an example, the mobile phone is a smartphone. Mobile terminal 100 includes an operation unit 112, a display unit 114, a communication interface 120, and a control unit 130. Hereinafter, an interface will be referred to as "I / F".

[0018] <000The operation unit 112 is a user interface that allows the user to input various information to the mobile terminal 100. The operation unit 112 includes, for example, a touch panel for displaying software keys, hardware keys, or both. Software keys are operation objects. Hardware keys include, for example, buttons or switches. The display unit 114 is a display or panel for displaying various information. The panel may or may not be a touch panel. The panel may also be, for example, a liquid crystal panel or an organic EL panel. The communication interface 120 is connected to the LAN 4.

[0019] The control unit 130 comprises a CPU 132 and a memory 134. The memory 134 comprises a main memory and an auxiliary memory. For example, the main memory includes RAM and cache memory. For example, the auxiliary memory may be ROM, flash memory, Solid State Drive (SSD), Hard Disk Drive (HDD), or a combination thereof. The auxiliary memory of the memory 134 stores an Operating System (OS) program 140, a first print application 142, and a first local table 144. "Application" is an abbreviation for application program. Hereafter, the OS program will be simply referred to as "OS". The OS 140 controls the basic operation of the mobile terminal 100. The first print application 142 is a program that causes the printer to execute the printing function. The first print application 142 is a mobile application. The CPU 132 performs various processes according to the program loaded from the auxiliary memory to the main memory.

[0020] (PC200 configuration) PC200 is a stationary terminal device such as a desktop PC. In a modified example, PC200 may be a portable terminal device such as a tablet or laptop PC. PC200 comprises an operation unit 212, a display unit 214, a communication interface 220, and a control unit 230.

[0021] The operation unit 212 is a user interface that allows the user to input various information to the PC 200. The display unit 214 is a display or panel for displaying various information. The details of the operation unit 212 and the display unit 214 are the same as those of the mobile terminal 100. The communication interface 220 is connected to LAN 4.

[0022] The control unit 230 includes a CPU 232 and a memory 234. The details of the memory 234 are the same as those of the memory 134 of the mobile terminal 100. The auxiliary storage device of the memory 234 stores the OS 240 and the second printing application 242. The OS 240 controls the basic operation of the PC 200. The second printing application 242 is a program that causes the printer to execute printing functions. The second printing application 242 is a PC application. The CPU 232 performs various processes according to the program loaded from the auxiliary storage device to the main memory. In the following, the various processes that the CPU 232 performs according to the program may be described as being performed proactively by the OS 240 or the second printing application 242.

[0023] (Configuration of notification server 300) The notification server 300 is a server installed on the Internet 6 by a vendor different from the vendors of printers 10, 20, and 30. Hereafter, this vendor will be simply referred to as "the vendor." The notification server 300 may be a single server or a collection of multiple servers.

[0024] The notification server 300 manages notification information corresponding to services related to the printer. These services include automatic shipping services, subscription services, and remote printing services. Hereafter, subscription services will be referred to as "subscription services." The automatic shipping service is a service that automatically ships a new cartridge when the amount of ink in the cartridge installed in the printer falls below a predetermined amount. The subscription service is a service that allows printing up to a contracted number of pages within a predetermined period for a basic fee. Subscription services include automatic shipping services. The remote printing service is a service that allows printing to be performed remotely on the printer via the Internet 6.

[0025] The notification server 300 comprises a communication interface 320 and a control unit 330. The communication interface 320 is connected to the Internet 6. The control unit 330 comprises a CPU 332 and a memory 334. The details of the memory 334 are the same as those of the memory 134 of the mobile terminal 100. The auxiliary storage device of the memory 334 stores a program 340, a management table 342, and a user table 344. The CPU 332 performs various processes according to the program loaded from the auxiliary storage device to the main memory.

[0026] In this embodiment, the users of the mobile terminal 100 and the PC 200 are the same. In a modified example, the users of the mobile terminal 100 and the PC 200 may be different.

[0027] (Content Server 400 Configuration) The content server 400 is installed on the Internet 6 by the vendor. The content server 400 may be a single server or a collection of multiple servers. The content server 400 stores image data representing images of information and transmits said image data to external devices according to instructions from those external devices.

[0028] (Contents of management table 342 and user table 344; Figure 2) Referring to Figure 2, the contents of the management table 342 and user table 344 of the notification server 300 will be explained.

[0029] Management table 342 is a table for managing information for all users. Management table 342 stores the notification ID, model name, start information, content information, and notification information in association with each other. Notification information is information for notifying printer users of the existence of services related to the printer. Notification information includes information indicating the title, information indicating the message, etc. The notification ID is information for identifying the notification information. The start information is information indicating the date on which the transmission of the notification information will start. The content information is information indicating the URL to be accessed when a selection operation for the notification information is accepted. Hereafter, the notification ID, model name, start information, content information, and notification information may be collectively referred to as "notification-related information." Notification-related information is information that is not associated with account information. Notification-related information is information registered by the administrator of notification server 300. In the modified example, notification-related information may be information registered in management table 342 depending on whether it is received from a server other than notification server 300.

[0030] User table 344 is a table for managing information for each user. User table 344 stores account information, management ID, notification ID, serial number, start information, content information, notification information, selection information, merge information, and update information in association with each other. The management ID is information used to identify information within the user table. The management ID is information generated by the notification server 300. The selection information indicates either "ON," which indicates that a selection operation for the notification information has been accepted, or "OFF," which indicates that a selection operation for the notification information has not been accepted. The merge information indicates either "ON," which indicates that the merge process (see Figure 4) described later has been executed, or "OFF," which indicates that the merge process has not been executed. The update information indicates the date and time when the information containing the information was stored, or the date and time when it was updated. Hereafter, the management ID, notification ID, serial number, start information, content information, notification information, selection information, and merge information may be collectively referred to as "user notification information."

[0031] (Contents of the first local table 144 and the second local table 244; Figure 3) Referring to Figure 3, the contents of the first local table 144 of the mobile terminal 100 and the contents of the second local table 244 of the PC 200 will be explained.

[0032] The first local table 144 of the mobile terminal 100 is a table that manages user notification information for users of the mobile terminal 100. The first local table 144 stores the management ID, notification ID, serial number, start information, content information, notification information, selection information, and merge information in association with each other.

[0033] The second local table 244 of the PC200 is a table that manages user notification information for users of the PC200. In the second local table 244, the management ID, notification ID, serial number, start information, content information, notification information, selection information, and merge information are stored in association with each other.

[0034] (Merge process; Figure 4) Referring to Figure 4, the merge process performed by the CPU 332 of the notification server 300 will be described. When the CPU 332 receives a merge request from an external device, it performs the process shown in Figure 4. A merge request is a signal to request an update to the user table 344 using the information contained in the merge request. The merge request includes the notification ID, serial number, and selection information. Note that the CPU 332 has already received account information from the external device before receiving the merge request from that external device. Hereafter, the received account information will be referred to as "target account information".

[0035] In S10, the CPU 332 generates target merge information using the received merge request and the management table 342. The CPU 332 identifies one notification ID as the target notification ID from among the one or more notification IDs included in the merge request. Hereinafter, the serial number and selection information associated with the target notification ID in the merge request may be referred to as "target serial number" and "target selection information," respectively. The CPU 332 identifies the start information, content information, and notification information associated with the target notification ID in the management table 342. Next, the CPU 332 generates target merge information that includes the target notification ID, target serial number, target selection information, identified start information, identified content information, and identified notification information. In this way, when the notification server 300 generates target merge information, it extracts the notification information from the management table 342 in memory 334. With this configuration, the time required to generate the target merge can be shortened compared to a configuration in which notification information is newly generated.

[0036] In S12, CPU 332 determines whether the combination of the target notification ID and the target serial number is already stored in user table 344 in association with the target account information. If the combination is already stored in user table 344 (YES in S12), CPU 332 proceeds to S20. On the other hand, if the combination is not already stored in user table 344 (NO in S12), CPU 332 proceeds to S14.

[0037] In S14, CPU 332 stores the target merge information and the merge information "ON" in the user table 344, associating them with the target account information. CPU 332 also stores the current date and time as update information in the user table 344, associating it with the target merge information.

[0038] In S16, CPU332 generates a management ID and stores the generated management ID in user table344, associating it with the target merge information.

[0039] In S20, the CPU 332 determines whether the selection information associated with the target notification ID and target serial number in the management table 342 is "ON". If the selection information is not "ON" (NO in S20), the CPU 332 proceeds to S22. On the other hand, if the selection information is "ON" (YES in S20), the CPU 332 proceeds to S30. If the CPU 332 determines YES in S20, it updates the update information associated with the target notification ID in the user table 344 to the current date and time.

[0040] In S22, CPU332 overwrites the target merge information in user table344. CPU332 also updates the update information using the current date and time.

[0041] In S30, CPU332 determines whether the check process using all notification IDs included in the merge request has been completed. If the check process using all notification IDs has been completed (YES in S30), CPU332 terminates the process shown in Figure 4. On the other hand, if the check process using at least one notification ID has not been completed (NO in S30), CPU332 returns to S10.

[0042] (Specific cases) Referring to Figures 5 to 16, a specific case realized by the communication system 2 of this embodiment will be described.

[0043] (Case A; Figures 5-11) Case A will be explained with reference to Figures 5 to 11. In the initial state of Case A, printers 10 and 20 are registered in the first printing application 142 of the mobile terminal 100. Therefore, serial number "SN1" and model name "MN1", and serial number "SN2" and model name "MN2" are stored in the memory 134 of the mobile terminal 100. In addition, printers 10 and 30 are registered in the second printing application 242 of the PC 200. Therefore, serial number "SN1" and model name "MN1", and serial number "SN3" and model name "MN3" are stored in the memory 234 of the PC 200. Furthermore, the contents of the management table 342 in the initial state of Case A are the same as the contents of the management table 342 in Figure 2. That is, the management table 342 stores notification-related information NR1, NR2, NR3, and NR4. The start information ST1 and ST2 indicate "December 10, 2024" and "December 20, 2024," respectively. The first local table 144, the second local table 244, and the user table 344 are empty. Furthermore, the date for Case A is December 11, 2024. Mobile terminal 100 was logged into notification server 300 using account information AC1 during the previous operation of the first print application 142. PC 200 was also logged into notification server 300 using account information AC1 during the previous operation of the second print application 242. In the following, for ease of understanding, the processing performed by each device's CPU will be described as being primarily performed by each device, rather than primarily by each CPU. Communication between devices is performed via a communication interface. Therefore, in the following explanation, the phrase "via the communication interface" will be omitted when describing communication.

[0044] The user of the mobile terminal 100 performs a first application launch operation on the mobile terminal 100 at T110, which is an operation to launch the first print application 142. As a result, the mobile terminal 100 launches the first print application 142 and determines that it had logged in to the notification server 300 using account information AC1 during the previous operation of the first print application 142. In this case, at T112, the mobile terminal 100 sends account information AC1 to the notification server 300 and receives a login success notification from the notification server 300. As a result, the state of the mobile terminal 100 becomes one in which it is logged in to the notification server 300 using account information AC1. At T114, the mobile terminal 100 displays the first home screen SC2 on the display unit 114. As shown in Figure 7, the first home screen SC2 includes a device object 600, a "Print" button 602, a "List" button 606, and a login icon 608. The device object 600 displays information about the device selected as the destination for sending instruction information, such as print commands, from among the one or more devices registered in the first print application 142. In this case, the serial number "SN1" and model name "MN1" are displayed in the device object 600. If no devices are registered in the first print application 142, the string "Not Selected" is displayed in the device object 600. The "List" button 606 is a button that displays the list screen on the mobile terminal 100. The login icon 608 is an icon for performing login using account information. The login icon 608 is also an icon for performing logout.

[0045] At T116 in Figure 5, the mobile terminal 100 sends a notification-related information request to the notification server 300. The notification-related information request is a signal to request the notification server 300 to send notification-related information.

[0046] When the notification server 300 receives a notification-related information request from the mobile terminal 100 at T116, it identifies the notification-related information to be sent to the mobile terminal 100. In the management table 342, the notification server 300 identifies notification-related information NR1, NR2, and NR3, which include start information ST1 indicating a start date earlier than today's date. The notification server 300 determines that the identified notification-related information NR1, NR2, and NR3 have not yet been sent to the logged-in mobile terminal 100. In this case, the mobile terminal 100 identifies notification-related information NR1, NR2, and NR3 as the notification-related information to be sent to the mobile terminal 100. At T118, the notification server 300 sends notification-related information NR1, NR2, and NR3 to the mobile terminal 100. The notification server 300 also stores in memory 334 that it has sent notification-related information NR1, NR2, and NR3 to the logged-in mobile terminal 100.

[0047] When the mobile terminal 100 receives notification-related information NR1, NR2, and NR3 from the notification server 300 at T118, it identifies the notification-related information to be displayed on the notification screen. Specifically, the mobile terminal 100 identifies notification-related information NR1 and NR2, which contain the model name "MN1" or model name "MN2" stored in memory 134, as the notification-related information to be displayed. Next, at T120, the mobile terminal 100 updates the first local table 144 using the identified notification-related information NR1 and NR2. Specifically, the mobile terminal 100 identifies the serial number "SN1" corresponding to the model name "MN1" contained in notification-related information NR1. Next, as shown in Figure 10, the mobile terminal 100 stores the information other than the model name "MN1" from the information contained in notification-related information NR1 in the first local table 144. The mobile terminal 100 further stores the serial number "SN1", selection information "OFF", and merge information "OFF" in the first local table 144. As a result, the notification ID "ID1", serial number "SN1", start information ST1, content information CT1, notification information NT1, selection information "OFF", and merge information "OFF" are associated and stored in the first local table 144. The mobile terminal 100 performs the same process for notification-related information NR2. As a result, the notification ID "ID2", serial number "SN2", start information ST1, content information CT2, notification information NT2, selection information "OFF", and merge information "OFF" are associated and stored in the first local table 144.

[0048] At T122 in Figure 5, the mobile terminal 100 displays the first notification screen SC4 on the first home screen SC2 using notification information NT1 within notification-related information NR1. As shown in Figure 7, the first notification screen SC4 is displayed on the first home screen SC2 in a pop-up format. The first notification screen SC4 includes a message corresponding to notification information NT1. This message is related to a subscription service. If a predetermined time elapses without the mobile terminal 100 accepting a selection operation for the first notification screen SC4, at T124 in Figure 5, the mobile terminal 100 displays the second notification screen SC6 on the first home screen SC2. For example, the predetermined time is "7 seconds". As shown in Figure 7, the second notification screen SC6 is displayed on the first home screen SC2 in a pop-up format. The second notification screen SC6 includes a message corresponding to notification information NT2. This message is related to a remote printing service. If a predetermined time elapses without the mobile terminal 100 accepting a selection operation for the second notification screen SC6, the display of the second notification screen SC6 is terminated at T126 in Figure 5.

[0049] Next, the mobile terminal 100 identifies the information to be included in the merge request to be sent to the notification server 300. Specifically, the mobile terminal 100 identifies the notification ID, serial number, and selection information associated with the merge information "OFF" in the first local table 144. Then, in T130, the mobile terminal 100 sends a merge request to the notification server 300 that includes "ID1-SN1-OFF" and "ID2-SN2-OFF". Also, in T132, the mobile terminal 100 clears the information in the first local table 144.

[0050] When the notification server 300 receives a merge request from the mobile terminal 100 at T130, it executes a merge process (see Figure 4) at T134 to update the user table 344. First, the notification server 300 identifies notification ID "ID1" as the target notification ID from among the notification IDs "ID1" and "ID2" included in the merge request. The notification server 300 executes a generation process to generate target merge information that includes notification ID "ID1", serial number "SN1", start information ST1, content information CT1, notification information NT1, and selection information "OFF" (S10). Next, the notification server 300 determines that the combination of notification ID "ID1" and serial number "SN1" is not already stored in the user table 344 in association with account information AC1 (NO in S12). In this case, the notification server 300 stores the target merge information in the user table 344 in association with account information AC1 (S14). Furthermore, the notification server 300 stores update information indicating the current date and time in the user table 344, associating it with the target merge information (S14). Next, the notification server 300 stores the management ID "MG1" in the user table 344, associating it with the target merge information (S16). This generates the user notification information UN1.

[0051] The notification server 300 determines that the check process using notification ID "ID2" is not complete (NO in S30). The notification server 300 uses notification ID "ID2" to perform the same processing as when using notification ID "ID1" (NO in S10 and S12, S14 and S16). As a result, user notification information UN2 is stored in user table 344, as shown in Figure 9. Next, the notification server 300 determines that the check process using all notification IDs included in the merge request is complete (YES in S30), and in T136 in Figure 5, sends a completion notification to the mobile terminal 100 indicating that the merge process is complete.

[0052] When the mobile terminal 100 receives a completion notification from the notification server 300 at T136, it sends a user notification information request to the notification server 300 at T140. The user notification information request is a signal requesting the notification server 300 to send user notification information associated with the account information used for login. If the mobile terminal 100 is logged in, it periodically sends user notification information requests to the notification server 300.

[0053] When the notification server 300 receives a user notification information request from the mobile terminal 100 at T140, it identifies user notification information UN1 and UN2 associated with account information AC1. The notification server 300 adjusts the data position of the user notification information in the order of the date and time indicated by the associated update information. At T142, the notification server 300 sends user notification information UN1 and UN2 to the mobile terminal 100.

[0054] When the mobile terminal 100 receives user notification information UN1 and UN2 from the notification server 300 at T142, it updates the first local table 144 at T144 using this information. As shown in Figure 10, the mobile terminal 100 stores the user notification information UN1 and UN2 in the first local table 144, and also stores the merge information "ON" in the first local table 144 in association with the user notification information UN1 and UN2.

[0055] At T150 in Figure 5, the user performs an operation on the "List" button 606 on the first home screen SC2. As a result, at T152, the mobile terminal 100 uses the first local table 144 to display the first list screen SC8 on the display unit 114. As shown in Figure 7, the first list screen SC8 includes a first notification area 610, a second notification area 620, and a "Home" button 630. The first notification area 610 is the area corresponding to the user notification information UN1. The first notification area 610 includes an unoperated object 612 and a message area 614. The unoperated object 612 is an object that indicates that a selection operation for the notification information has not yet been performed. In this embodiment, the unoperated object is a white circle. "A selection operation for the notification information has not yet been performed" may indicate that the user has not read the notification information. The message area 614 displays the information indicated by the notification information NT1. The second notification area 620 is the area corresponding to the user notification information UN2. The second notification area 620 includes an unoperated object 622 and a message area 624. The message area 624 displays the information indicated by the notification information NT2. In this way, the user of the mobile terminal 100 can check the notification information for printers 10 and 20 by performing an operation on the "List" button 606.

[0056] Next, we consider a scenario where the user uses PC200. At T160, the user performs a second application launch operation on PC200, which is an operation to launch the second print application 242. As a result, PC200 launches the second print application 242 and determines that the user was logged into the notification server 300 using account information AC1 during the previous operation of the second print application 242. In this case, at T162, PC200 sends account information AC1 to the notification server 300 and receives a login success notification from the notification server 300. As a result, PC200's state becomes logged in. At T164, PC200 displays the second home screen SC12 on the display unit 214. As shown in Figure 8, the second home screen SC12 includes a "Print" button 700, a "List" button 704, a device object 706, and a login icon 708. The device object 706 displays information about the device selected as the destination for sending instruction information, such as print commands, from among the one or more devices registered in the second print application 242. In this case, the serial number "SN1" and model name "MN1" are displayed in the device object 706. If no devices are registered in the second print application 242, the string "Not Selected" is displayed in the device object 706. The "List" button 704 is a button that displays the list screen on the PC 200. The login icon 708 is an icon for performing login using account information. The login icon 708 is also an icon for performing logout. In T166 of Figure 5, the PC 200 sends a notification-related information request to the notification server 300.

[0057] When the notification server 300 receives a notification-related information request from PC200 at T166, it identifies notification-related information NR1, NR2, and NR3 as notification-related information to be sent to PC200. At T168, the notification server 300 sends notification-related information NR1, NR2, and NR3 to PC200. The notification server 300 stores in memory 334 that it has sent notification-related information NR1, NR2, and NR3 to PC200, which is logged in.

[0058] When PC200 receives notification-related information NR1, NR2, and NR3 from the notification server 300 at T168, it identifies the notification-related information to be displayed on the notification screen. Specifically, PC200 identifies notification-related information NR1 and NR3, which contain the model name "MN1" or model name "MN3" and are stored in memory 234, as the notification-related information to be displayed.

[0059] At T170 in Figure 6, PC200 updates the second local table 244 using the identified notification-related information NR1 and NR3. The process for updating the second local table 244 at T170 is the same as the process for updating the first local table 144 at T120. As a result, as shown in Figure 11, notification ID "ID1", serial number "SN1", start information ST1, content information CT1, notification information NT1, selection information "OFF", and merge information "OFF" are associated and stored in the second local table 244. In addition, notification ID "ID3", serial number "SN3", start information ST1, content information CT3, notification information NT3, selection information "OFF", and merge information "OFF" are associated and stored in the second local table 244.

[0060] In Figure 6, at T172, PC200 uses notification information NT1 within notification-related information NR1 to display the third notification screen SC14 on the second home screen SC12. As shown in Figure 8, the third notification screen SC14 is displayed on the second home screen SC12 in a pop-up format. The third notification screen SC14 includes a message corresponding to notification information NT1.

[0061] In Figure 6, at T174, the user performs a selection operation for the third notification screen SC14. As a result, PC200 accesses the content server 400 using the URL indicated by the content information CT1 in the notification-related information NR1. PC200 receives first service screen data representing the first service screen SC16 from the content server 400 and displays the first service screen SC16 on the display unit 214 in T176. As shown in Figure 8, the first service screen SC16 includes a message 710 guiding users to the subscription service and a "Subscribe" button 712. When the user clicks the "Subscribe" button 712, a subscription process is executed to subscribe to the subscription service. The subscription process is performed between the printer 10, PC200, and the server providing the subscription service.

[0062] PC200 updates the second local table 244 at T180 in Figure 6. As shown in Figure 11, PC200 changes the selection information associated with notification ID "ID1" corresponding to the third notification screen SC14 in the second local table 244 to "ON".

[0063] Subsequently, at T190, the second home screen SC12 is displayed on the display unit 214 of the PC200. Then, at T192, the PC200 uses the notification information NT3 in the notification-related information NR3 to display the fourth notification screen SC18 on the second home screen SC12. As shown in Figure 8, the fourth notification screen SC18 is displayed on the second home screen SC12 in a pop-up format. The fourth notification screen SC18 includes a message corresponding to the notification information NT3. This message is a message regarding the remote printing service. If a predetermined time elapses without accepting a selection operation for the fourth notification screen SC18, the PC200 terminates the display of the fourth notification screen SC18 at T194 in Figure 6.

[0064] Next, PC200 identifies the information to include in the merge request to send to notification server 300. PC200 identifies the notification ID, serial number, and selection information associated with the merge information "OFF" in the second local table 244. PC200 then sends a merge request containing "ID1-SN1-ON" and "ID3-SN3-OFF" to notification server 300 at T200. PC200 also clears the information in the second local table 244 at T202.

[0065] When the notification server 300 receives a merge request from PC200 at T200, it executes a merge process (see Figure 4) at T204 to update the user table 344. The notification server 300 identifies notification ID "ID1" as the target notification ID among the notification IDs "ID1" and "ID3" included in the merge request, and generates target merge information that includes notification ID "ID1" (S10). The notification server 300 determines that the combination of notification ID "ID1" and serial number "SN1" is already stored in the user table 344 in association with account information AC1 (YES in S12). The notification server 300 determines that the selection information associated with notification ID "ID1" and serial number "SN1" in the user table 344 is "OFF" (NO in S20). In this case, the notification server 300 overwrites the target merge information in the user table 344 and updates the update information (S22). This changes the selection information associated with notification ID "ID1" and serial number "SN1" to "ON".

[0066] Next, the notification server 300 determines that the check process using notification ID "ID3" is not complete (NO in S30) and generates target merge information including notification ID "ID3" (S10). The notification server 300 determines that the combination of notification ID "ID3" and serial number "SN1" is not already stored in user table 344 in association with account information AC1 (NO in S12). In this case, the notification server 300 stores the target merge information including notification ID "ID3" in user table 344 in association with account information AC1 (S14). The notification server 300 also stores update information indicating the current date and time in user table 344 in association with the target merge information (S14). Next, the notification server 300 stores management ID "MG3" in user table 344 in association with the target merge information (S16). As a result, as shown in Figure 9, user notification information UN1 is updated and user notification information UN3 is stored in user table 344. Next, the notification server 300 determines that the check process using all notification IDs is complete (YES in S30), and sends a completion notification to the PC 200 at T206 in Figure 6.

[0067] When PC200 receives a completion notification from the notification server 300 at T206, it sends a user notification information request to the notification server 300 at T210. Furthermore, if PC200 is logged in, it periodically sends user notification information requests to the notification server 300.

[0068] When the notification server 300 receives a user notification information request from PC200 at T210, it sends user notification information UN1, UN3, and UN2 associated with account information AC1 to PC200 at T212.

[0069] When PC200 receives user notification information UN1, UN3, and UN2 from the notification server 300 at T212, it updates the second local table 244 at T214 using this information. First, PC200 identifies user notification information UN1 and UN3 from the received user notification information UN1, UN3, and UN2 that contain the serial number "SN1" or "SN3" stored in memory 234. Next, as shown in Figure 11, PC200 stores user notification information UN1 and UN3 in the second local table 244, and also stores merge information "ON" associated with user notification information UN1 and UN3 in the second local table 244.

[0070] In Figure 6, at T220, the user performs an operation on the "List" button 704 on the second home screen SC12. As a result, at T222, the PC200 uses the second local table 244 to display the second list screen SC20 on the display unit 214. As shown in Figure 8, the second list screen SC20 includes a third notification area 720, a fourth notification area 730, and a "Home" button 740. The third notification area 720 is the area corresponding to the user notification information UN1. The third notification area 720 includes an operated object 722 and a message area 724. The operated object 722 is an object that indicates that a selection operation on the notification information has been performed. In this embodiment, the operated object is a black circle. "A selection operation on the notification information has been performed" may indicate that the user has read the notification information. The message area 724 displays the information indicated by the notification information NT1. The fourth notification area 730 is the area corresponding to the user notification information UN3. The fourth notification area 730 includes an unoperated object 732 and a message area 734. The message area 734 displays the information indicated by the notification information NT3. In this way, the user of the mobile terminal 100 can check the notification information for printers 10 and 30 by performing an operation on the "List" button 704.

[0071] As shown in the first list screen SC8 in Figure 7, if a selection operation has not been performed on the notification information, the notification information is displayed in a display mode associated with the unoperated object. Also, as shown in the second list screen SC20 in Figure 8, if a selection operation has been performed on the notification information, the notification information is displayed in a display mode associated with the operated object. In this way, when a selection operation is performed on the notification information, the unoperated object corresponding to that notification information is changed to an operated object. Therefore, the user can know whether or not a selection operation has been performed on the notification information by looking at the display mode of the notification information. In the modified version, if a selection operation has not been performed on the notification information, the notification area may be displayed in a display mode that includes only the message area, and if a selection operation has been performed, the notification area may be displayed in a display mode that includes both the message area and the operated object. In this modified version, when a selection operation has not been performed, the area where the operated object would be displayed if a selection operation had been performed is displayed is either the screen background or the message area. In another modification, if a selection operation has been performed on the notification information, the notification area may be displayed in a way that includes only the message area, and if a selection operation has not been performed, the notification area may be displayed in a way that includes both the message area and the unoperated object. In this modification, when a selection operation has been performed, the area where the unoperated object would be displayed if a selection operation had not been performed is displayed either the screen background or the message area. Furthermore, in yet another modification, the display manner of the message area may differ depending on whether a selection operation has been performed on the notification information or not. In other words, the notification information should be displayed in a way that distinguishes between when a selection operation on the notification information has been performed and when it has not.

[0072] Subsequently, we assume a scenario in which the mobile terminal 100 sends a user notification information request to the notification server 300, and then the user performs an operation on the "List" button 606 (see Figure 7) on the first home screen SC2. At T230, the mobile terminal 100 sends a user notification information request to the notification server 300. Then, at T232, the mobile terminal 100 receives user notification information UN1, UN3, and UN2 from the notification server 300, and at T234, updates the first local table 144 using this information. First, the mobile terminal 100 identifies user notification information UN1 and UN2 from the received user notification information UN1, UN3, and UN2 that contain the serial number "SN1" or "SN2" stored in memory 134. Next, the mobile terminal 100 updates the user notification information UN1 and UN2 in the first local table 144 using the identified user notification information UN1 and UN2. As a result, as shown in Figure 10, the selection information associated with notification ID "ID1" in the first local table 144 changes to "ON".

[0073] In Figure 6, at T240, the user performs an operation on the "List" button 606 on the first home screen SC2. As a result, at T242, the mobile terminal 100 uses the first local table 144 to display the third list screen SC10 on the display unit 114. As shown in Figure 7, the third list screen SC10 includes a fifth notification area 640, a sixth notification area 650, and a "Home" button 630. The fifth notification area 640 is the area corresponding to user notification information UN1. The fifth notification area 640 includes an operated object 642 and a message area 614. The fifth notification area 640 differs from the first notification area 610 in the first list screen SC8 in that it includes an operated object 642. The sixth notification area 650 is the area corresponding to user notification information UN2. The sixth notification area 650 is the same as the second notification area 620 in the first list screen SC8. Thus, in the third list screen SC10, the fifth notification area 640 corresponding to the notification information NT1 selected using PC200 contains the operated object 642. Therefore, the user can know that a selection operation has been performed on the notification information NT1. Consequently, user convenience can be improved.

[0074] As described above, the notification server 300 receives a merge request from an external device when the external device is logged into the notification server 300 using specific account information. The notification server 300 then updates the user table 344 using the specific account information and the merge request. With this configuration, even if the external devices communicating are different, the notification server 300 updates the selection information associated with the account information used for login if the account information is the same. Therefore, the notification server 300 can synchronize the selection information for multiple external devices that use the same account information.

[0075] (Case B; Figures 12-16) Refer to Figures 12-16 to explain Case B. Case B is the state after Case A. The date for Case B is December 21, 2024.

[0076] T310 to T316 are the same as T110 to T116 in Figure 5. When the notification server 300 receives a notification-related information request from the mobile terminal 100 at T316, it identifies the notification-related information to be sent to the mobile terminal 100. In the management table 342, the notification server 300 identifies notification-related information NR1, NR2, NR3, and NR4, which include start information ST1 and ST2 indicating a start date earlier than today's date. The notification server 300 determines that notification-related information NR1, NR2, and NR3 have already been sent to the logged-in mobile terminal 100, but notification-related information NR4 has not already been sent to the logged-in mobile terminal 100. In this case, the notification server 300 identifies notification-related information NR4 as the notification-related information to be sent to the mobile terminal 100. At T318, the notification server 300 sends notification-related information NR4 to the mobile terminal 100. The notification server 300 stores in memory 334 that it has sent notification-related information NR4 to the mobile terminal 100, which is logged in.

[0077] When the mobile terminal 100 receives notification-related information NR4 from the notification server 300 at T318, it identifies the notification-related information NR4 as the notification-related information to be displayed. Next, at T320, the mobile terminal 100 updates the first local table 144 using the identified notification-related information NR4. As a result, as shown in Figure 15, the notification ID "ID4", serial number "SN1", start information ST2, content information CT4, notification information NT4, selection information "OFF", and merge information "OFF" are associated and stored in the first local table 144.

[0078] At T322 in Figure 12, the mobile terminal 100 displays a fifth notification screen on the first home screen SC2 using notification information NT4 within notification-related information NR4. The fifth notification screen is displayed on the first home screen SC2 in a pop-up format. The fifth notification screen includes a message indicated by notification information NT4. This message is related to an automated delivery service. At T324, if a predetermined time has elapsed without the mobile terminal 100 accepting a selection operation for the fifth notification screen, the display of the fifth notification screen is terminated.

[0079] The mobile terminal 100 identifies the notification ID "ID4", serial number "SN1", and selection information "OFF" associated with the merge information "OFF" in the first local table 144. Then, in T330, the mobile terminal 100 sends a merge request containing "ID4-SN1-OFF" to the notification server 300. Also, in T332, the mobile terminal 100 clears the information in the first local table 144.

[0080] When the notification server 300 receives a merge request from the mobile terminal 100 at T330, it executes a merge process (see Figure 4) at T334 to update the user table 344. The notification server 300 identifies the notification ID "NT4" included in the merge request as the target notification ID and generates target merge information including the notification ID "NT4" (S10). The notification server 300 determines that the combination of notification ID "NT4" and serial number "SN1" is not already stored in the user table 344 in association with account information AC1 (NO in S12). In this case, the notification server 300 stores the target merge information in the user table 344 (S14). The notification server 300 also stores update information indicating the current date and time in association with the target merge information in the user table 344 (S14). Next, the notification server 300 stores the management ID "MG4" in association with the target merge information in the user table 344 (S16). As a result, as shown in Figure 14, the user notification information UN4 is stored in the user table 344. Next, the notification server 300 determines that the check process using all notification IDs is complete (YES in S30), and sends a completion notification to the mobile terminal 100 at T336 in Figure 12.

[0081] When the mobile terminal 100 receives a completion notification from the notification server 300 at T336, it sends a user notification information request to the notification server 300 at T340. At T342, the mobile terminal 100 receives user notification information UN4, UN1, UN3, and UN2 from the notification server 300. From the received user notification information UN4, UN1, UN3, and UN2, the mobile terminal 100 identifies user notification information UN4, UN1, and UN2 that contain the serial number "SN1" or "SN2" stored in memory 134. At T344, the mobile terminal 100 updates the first local table 144 using the identified user notification information UN4, UN1, and UN2. As shown in Figure 15, the mobile terminal 100 stores user notification information UN4, UN1, and UN2 in the first local table 144, and also stores merge information "ON" in the first local table 144 in association with the user notification information UN4, UN1, and UN2.

[0082] The user performs a logout operation at T350 in Figure 12. As a result, the mobile terminal 100 deletes the information in the first local table 144 at T352. The mobile terminal 100 sends a logout request to the notification server 300 at T354. As a result, the state of the mobile terminal 100 changes from logged in to logged out. The mobile terminal 100 sends a notification-related information request to the notification server 300 at T356.

[0083] When the notification server 300 receives a notification-related information request from the mobile terminal 100 at T356, it identifies the notification-related information to be sent to the mobile terminal 100, which is currently logged out. In the management table 342, the notification server 300 identifies notification-related information NR1, NR2, NR3, and NR4, which include start information ST1 and ST2 indicating a start date earlier than today's date. At T358, the notification server 300 sends the notification-related information NR1, NR2, NR3, and NR4 to the mobile terminal 100. In this way, when the state of the mobile terminal 100 changes from logged in to logged out, the notification server 300 also sends the notification-related information that has already been sent to the mobile terminal 100 while it was logged in. With this configuration, the notification server 300 can appropriately switch the notification-related information to be sent to the mobile terminal 100 depending on the state of the mobile terminal 100.

[0084] When the mobile terminal 100 receives notification-related information NR1, NR2, NR3, and NR4 from the notification server 300 at T358, it identifies the notification-related information to be displayed on the notification screen. The mobile terminal 100 identifies the notification-related information NR1, NR2, and NR4, which include the model name "MN1" or "MN2" stored in memory 134, as the notification-related information to be displayed. Next, the mobile terminal 100 updates the first local table 144 using the identified notification-related information NR1, NR2, and NR4. As a result, as shown in Figure 16, information including notification ID "ID1", information including notification ID "ID2", and information including notification ID "ID4" are stored in the first local table 144.

[0085] T362, T364, and T366 in Figure 12 are the same as T122, T124, and T322 in Figure 5, respectively. At T368 in Figure 13, the user performs a selection operation on the mobile terminal 100 for the fifth notification screen. As a result, the mobile terminal 100 accesses the content server 400 using the URL indicated by the content information CT4 in the notification-related information NR4. When the mobile terminal 100 receives second service screen data representing the second service screen from the content server 400, it displays the second service screen on the display unit 114 at T370. The second service screen is a screen related to the automated shipping service.

[0086] The mobile terminal 100 updates the first local table 144 in T372. As shown in Figure 16, the mobile terminal 100 changes the selection information associated with notification ID "ID4" corresponding to the fifth notification screen in the first local table 144 to "ON".

[0087] Next, we assume that the first home screen SC2 is displayed on the display unit 114 of the mobile terminal 100. The user performs an account information input operation at T374. The account information input operation includes an operation on the login icon 608 and an operation to input account information AC1. At T376, the mobile terminal 100 sends the account information AC1 to the notification server 300 and receives a login success notification from the notification server 300. As a result, the state of the mobile terminal 100 changes from the logout state to the logged-in state.

[0088] Next, the mobile terminal 100 identifies the information to be included in the merge request to be sent to the notification server 300. In the first local table 144, the mobile terminal 100 identifies the notification ID, serial number, and selection information associated with the merge information "OFF". Then, in T380, the mobile terminal 100 sends a merge request to the notification server 300 that includes "ID1-SN1-OFF", "ID2-SN2-OFF", and "ID4-SN1-ON". Also, in T382, the mobile terminal 100 clears the information in the first local table 144.

[0089] When the notification server 300 receives a merge request from the mobile terminal 100 at T380, it executes a merge process (see Figure 4) at T384 to update the user table 344. The notification server 300 identifies notification ID "ID1" as the target notification ID from among the notification IDs "ID1", "ID2", and "ID4" included in the merge request. The notification server 300 generates target merge information including notification ID "ID1" (S10). The notification server 300 determines that the combination of notification ID "ID1" and serial number "SN1" is already stored in the user table 344 in association with account information AC1 (YES in S12). The notification server 300 determines that the selection information associated with notification ID "ID1" and serial number "SN1" in the user table 344 is "ON" (YES in S20). In this case, the notification server 300 updates the update information associated with notification ID "ID1".

[0090] Next, the notification server 300 determines that the check process using notification IDs "ID2" and "ID4" is not complete (NO in S30), and identifies notification ID "ID2" as the target notification ID. The notification server 300 generates target merge information including notification ID "ID2" (S10). The notification server 300 determines that the combination of notification ID "ID2" and serial number "SN2" is already stored in user table 344 in association with account information AC1 (YES in S12). The notification server 300 also determines that the selection information associated with notification ID "ID2" and serial number "SN2" in user table 344 is "OFF" (NO in S20). In this case, the notification server 300 overwrites the target merge information in user table 344 and updates the update information (S22).

[0091] Next, the notification server 300 determines that the check process using notification ID "ID4" is not complete (NO in S30) and generates target merge information including notification ID "ID4" (S10). The notification server 300 determines that the combination of notification ID "ID4" and serial number "SN1" is already stored in user table 344 in association with account information AC1 (YES in S12). The notification server 300 also determines that the selection information associated with notification ID "ID4" and serial number "SN1" in user table 344 is "OFF" (NO in S20). In this case, the notification server 300 overwrites the target merge information in user table 344 and updates the update information (S22). As a result, the selection information associated with notification ID "ID4" in user table 344 changes to "ON". Next, the notification server 300 determines that the check process using all notification IDs is complete (YES in S30) and sends a completion notification to PC200 in T386.

[0092] As described above, the notification server 300 receives a merge request from the mobile terminal 100 when the mobile terminal 100's state changes from logout to logged in (T380). The notification server 300 then generates notification information NT4 corresponding to the notification ID "ID4" received by the mobile terminal 100 while it was logged out (T384). Next, the notification server 300 associates the account information AC1, the notification ID "ID1", the serial number "SN1", and the notification information NT4 and stores them in the user table 344 (T384). With this configuration, the notification server 300 can also store information corresponding to the notification ID received by the mobile terminal 100 while it was logged out.

[0093] T390 and T392 are the same as T340 and T342 in Figure 12, respectively. The mobile terminal 100 identifies user notification information UN4, UN1, UN3, and UN2 from the received user notification information UN4, UN1, UN3, and UN2 that contain the serial number "SN1" or "SN2" stored in memory 134. At T394, the mobile terminal 100 updates the first local table 144 using the identified user notification information UN4, UN1, and UN2. As shown in Figure 16, the mobile terminal 100 stores user notification information UN4, UN1, and UN2 in the first local table 144, and also stores merge information "ON" associated with user notification information UN4, UN1, and UN2 in the first local table 144.

[0094] In T400 of Figure 13, the user performs an operation on the "List" button 606 on the first home screen SC2. As a result, in T402, the mobile terminal 100 uses the first local table 144 to display the fourth list screen SC40 on the display unit 114. The fourth list screen SC40 includes a seventh notification area 660, an eighth notification area 670, a ninth notification area 680, and a "Home" button 630. The seventh notification area 660 is the area corresponding to user notification information UN4. The seventh notification area 660 includes an operated object 662 and a message area 664. The message area 664 displays information indicated by notification information NT4. The eighth notification area 670 is the area corresponding to user notification information UN1. The eighth notification area 670 is similar to the fifth notification area 640 (see Figure 7) in the third list screen SC10. The ninth notification area 680 is the area corresponding to user notification information UN2. The ninth notification area 680 is the same as the sixth notification area 650 (see Figure 7) in the third list screen SC10.

[0095] At T410, the user performs a selection operation on the ninth notification area 680 on the fourth list screen SC40. As a result, the mobile terminal 100 accesses the content server 400 using the URL indicated by the content information CT2 in the notification-related information NR2. When the mobile terminal 100 receives third service screen data representing the third service screen from the content server 400, at T402, it displays the third service screen on the display unit 114. The third service screen is a screen related to the remote printing service. Next, the mobile terminal 100 changes the selection information associated with notification ID "ID2" in the first local table 144 to "ON", and at T414, it sends an update request including "ID2-SN2-ON" to the notification server 300.

[0096] When the notification server 300 receives an update request from the mobile terminal 100 at T414, at T416, it changes the selection information associated with the notification ID "ID2" and serial number "SN2" in the user table 344 to "ON". In this way, the selection information in the user table 344 is changed to "ON" in response to a selection operation performed on the notification screen or the notification area in the list screen.

[0097] (Effects of Case A and Case B) According to the above configuration, the notification server 300 sends notification information NT1 to the mobile terminal 100 and PC 200 that use account information AC1 (T142 in Figure 5, T212 in Figure 6). The mobile terminal 100 and PC 200 display the notification information NT1 (T152 in Figure 5, T222 in Figure 6). Therefore, user convenience regarding notification information NT1 is improved.

[0098] Furthermore, a merge request includes selection information related to a selection operation on the notification information. Therefore, the notification server 300 can store the selection information included in the merge request in the user table 344. Thus, it can manage whether or not a selection operation on the notification information has been performed.

[0099] (Correspondence) Notification server 300 is an example of a "server". Program 340 is an example of a "computer program for a server". Mobile terminal 100 is an example of a "first terminal device". Account information AC1 is an example of "specific account information". Notification information NT1 is an example of "specific notification information". Notification ID "ID1" is an example of "notification identification information". Printer 10 is an example of a "specific communication device". Serial number "SN1" is an example of "device identification information". The merge requests T130 in Figure 5 and T380 in Figure 13 are examples of "first generation requests". Subscription service is an example of a "service". Memory 334 of notification server 300 is an example of "memory". The user notification information request T140 in Figure 5 is an example of a "first request signal". PC 200 is an example of a "second terminal device". The user notification information request T210 in Figure 6 is an example of a "second request signal". The user notification information UN1 at T142 in Figure 5 is an example of "first information". The user notification information UN1 at T212 in Figure 6 is an example of "second information". The selection information "OFF" is an example of "first value". The selection information "ON" is an example of "second value". The merge request at T200 in Figure 6 is an example of "second generation request". The notification-related information request at T356 in Figure 12 is an example of "third request signal". The notification-related information request at T116 in Figure 5 is an example of "fourth request signal". The operation on the "List" button is an example of "predetermined operation". The notification-related information request at T356 in Figure 12 is an example of "fifth request signal".

[0100] T130 in Figure 5 and T380 in Figure 13 are examples of processes executed by the "first generation request receiving unit". T134 in Figure 5 and T384 in Figure 13 are examples of processes executed by the "first generation unit" and the "first memory control unit". T140 in Figure 5 and T390 in Figure 13 are examples of processes executed by the "first request signal receiving unit". T142 in Figure 5 and T392 in Figure 13 are examples of processes executed by the "first notification information transmission unit". T210 in Figure 6 is an example of a process executed by the "second request signal receiving unit". T212 in Figure 6 is an example of a process executed by the "second notification information transmission unit".

[0101] Mobile terminal 100 is an example of a "terminal device." The first printing application 142 is an example of a "computer program for a terminal device."

[0102] T130 in Figure 5 and T380 in Figure 13 are examples of processes performed by the "first generation request transmission unit". T140 in Figure 5 and T390 in Figure 13 are examples of processes performed by the "first request signal transmission unit". T142 in Figure 5 and T392 in Figure 13 are examples of processes performed by the "first notification information receiving unit". T152 in Figure 5 and T402 in Figure 13 are examples of processes performed by the "first display control unit".

[0103] T222 in Figure 6 is an example of a process executed by the "second display control unit".

[0104] Although specific examples of the present invention have been described in detail above, these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples illustrated above. Modifications of the above embodiments are listed below.

[0105] (First Modification) In the above embodiment, each server 300 and 400 was described as a separate server, but servers 300 and 400 may be configured as a single server.

[0106] (Second Modification) In the above embodiment, each server 300 and 400 is a physical server, but each server 300 and 400 is not limited to a physical server, but may be a virtual server or virtual machine on the cloud. That is, the vendor may not prepare the hardware for 300 and 400 itself, but may use an environment provided by an external cloud computing service. In this case, the vendor may realize each server 300 and 400 by preparing the programs (i.e., software) for 300 and 400 and installing them in the above environment. In another modification, each server 300 and 400 may be installed on the Internet 6 by a different operator than the vendor.

[0107] (Third variation) The "first terminal device" is not limited to the mobile terminal 100, but may be a PC 200 or the like. Also, the "second terminal device" is not limited to the PC 200, but may be a mobile terminal 100 or the like.

[0108] (Fourth modified example) "Device identification information" is not limited to a serial number, but may also be an IP address, MAC address, etc.

[0109] (Fifth variation) "Service" is not limited to subscription services, but may also include automated shipping services, remote printing services, etc.

[0110] (Sixth variation) "Specific communication device" is not limited to printers, but may also be a multifunction printer, copier, sewing machine, etc.

[0111] (Seventh modified example) The "memory" is not limited to the memory 334 of the notification server 300, but may be the memory of a device other than the notification server 300.

[0112] (Eighth Modification) In S10 of Figure 4, the notification server 300 may generate the target merge information without using the management table 342. For example, the information included in the target merge information may be registered by the administrator of the notification server 300.

[0113] (9th variation) The merge request does not need to include selection information.

[0114] (Tenth Modification) In the above embodiment, the merge request includes the selection information "OFF" or the selection information "ON". In the modification, the merge request may include information related to the selection operation if the selection operation has not been performed, and may not include information related to the selection operation if the selection operation has been performed. In another modification, the merge request may not include information related to the selection operation if the selection operation has not been performed, and may include information related to the selection operation if the selection operation has been performed.

[0115] (11th Modification) The mobile terminal 100 may be configured not to send a merge request even when the state of the mobile terminal 100 changes from a logout state to a logged-in state. In this modification, T376, T380, T384, and T386 in Figure 13 can be omitted. The mobile terminal 100 may further be configured not to send a notification-related information request when the state of the mobile terminal 100 is a logout state. In this modification, the "third request signal receiving unit" and the "third notification information transmitting unit" can be omitted.

[0116] (12th Modification) The mobile terminal 100 may be configured not to send a notification-related information request when the mobile terminal 100 is logged out. In this modification, the "fifth request signal receiving unit" and the "fifth notification information transmitting unit" can be omitted.

[0117] (13th Modification) In each of the above embodiments, the processes shown in Figures 4, 5, 12, and 13 are implemented by software (for example, programs 140, 142, 240, 242, and 340), but at least one of these processes may be implemented by hardware such as a logic circuit.

[0118] Furthermore, the technical elements described herein or in the drawings demonstrate technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies illustrated herein or in the drawings achieve multiple objectives simultaneously, and achieving even one of these objectives constitutes technical usefulness in itself.

[0119] Even if, in the claims of this patent application, each claim depends on only some of the claims, it is not limited to the claim being dependent only on those specific claims. To the extent that it is not technically contradictory, each claim may be dependent on other claims that were not dependent at the time of application. That is, the technologies of each claim can be combined in various ways as follows: (Item 1) A computer program for a server, The computer of the aforementioned server, A first generation request receiving unit receives a first generation request from a first terminal device in a first login state in which the first terminal device is logged into the server using specific account information, the first generation request receiving unit receiving the first generation request request which includes notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, A first generation unit generates the specific notification information corresponding to the notification identification information when the first generation request is received, A first storage control unit stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory after the specific notification information has been generated, in association with each other. A first request signal receiving unit receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information after the specific notification information has been generated, A first notification information transmission unit transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device, wherein the first terminal device displays the specific notification information when it receives the specific notification information from the server, After the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and in a second login state in which a second terminal device different from the first terminal device is logged into the server using the specific account information, a second request signal receiving unit receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information, A second notification information transmission unit transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device, wherein the second terminal device displays the specific notification information when it receives the specific notification information from the server, the second notification information transmission unit A computer program that functions as such. (Item 2) The computer program described in item 1, wherein the first generation unit, when the first generation request is received, extracts from the memory the specific notification information that is stored in the memory in association with the notification identification information and not stored in the memory in association with account information. (Item 3) The first generation request indicates either that the selection operation for the specific notification information has not been performed, or that the selection operation for the specific notification information has been performed. When the first notification information transmission unit receives the first request signal from the first terminal device, it transmits to the first terminal device the first information, including the specific notification information associated with the specific account information. When the second notification information transmission unit receives the second request signal from the second terminal device, it transmits to the second terminal device the second information, including the specific notification information associated with the specific account information. If the first generation request indicates that a selection operation for the specific notification information has not been performed, the first information indicates that a selection operation for the specific notification information has not been performed. The computer program described in item 1 or 2, wherein the first generation request indicates that a selection operation for the specific notification information has been performed, and the first information and the second information indicate that a selection operation for the specific notification information has been performed. (Item 4) The first generation request includes the notification identification information, the device identification information, and the selection information. The selection information indicates either a first value indicating that a selection operation for the specific notification information has not yet been performed, or a second value indicating that a selection operation for the specific notification information has already been performed. The first memory control unit, after the specific notification information is generated, stores the specific account information, the notification identification information, the device identification information, the specific notification information, and the selection information in the memory in association with each other. The first information includes the specific notification information and the selection information associated with the specific account information, The second information is the computer program described in item 3, which includes the specific notification information and the selection information associated with the specific account information. (Item 5) The aforementioned computer program further uses the computer, After the specific account information, the notification identification information, the device identification information, the specific notification information, and the selection information which is the first value have been associated and stored in the memory, and in the second login state, a second generation request receiving unit receives a second generation request from the second terminal device which includes the notification identification information, the device identification information, and the selection information which is the second value, When the second generation request is received, a second storage control unit changes the selection information associated with the specific account information from the first value to the second value and stores it in the memory, A computer program described in item 4 that functions as such. (Item 6) The aforementioned computer program further uses the computer, A third request signal receiving unit receives a third request signal from the first terminal device requesting the transmission of notification information not associated with account information, when the first terminal device is logged out and has not logged into the server using account information. When the third request signal is received from the first terminal device, the third notification information transmission unit functions as a unit that transmits the specific notification information not associated with account information and the notification identification information to the first terminal device from within the memory. The first generation request receiving unit is a computer program according to any one of items 1 to 5, which receives the first generation request from the first terminal device after changing from the logout state to the first login state. (Item 7) The aforementioned computer program further uses the computer, In the first login state, a fourth request signal receiving unit receives a fourth request signal from the first terminal device requesting the transmission of notification information not associated with account information, A fourth notification information transmission unit, which, when the fourth request signal is received from the first terminal device, transmits the specific notification information, which is not associated with account information in the memory, to the first terminal device, In the first login state, if the fourth request signal is received again from the first terminal device, the specific notification information is not transmitted. The first terminal device, After the first request signal is transmitted to the first terminal device, if the specific notification information is received from the server and a predetermined operation is accepted, the specific notification information is displayed. When the fourth request signal is transmitted to the first terminal device and the specific notification information is received from the server, the specific notification information is displayed without accepting the predetermined operation. The fourth notification information transmission unit, A fifth request signal receiving unit receives a fifth request signal from the first terminal device requesting the transmission of notification information not associated with account information after the state has changed from the first login state to the logout state. A fifth notification information transmission unit transmits to the first terminal device the specific notification information that is not associated with account information in the memory when the fifth request signal is received from the first terminal device, wherein the first terminal device, after the fifth request signal has been transmitted to the first terminal device, receives the specific notification information from the server and displays the specific notification information without accepting the predetermined operation, the fifth notification information transmission unit A computer program described in any one of items 1 through 6 that functions as such. (Item 8) A computer program for a terminal device, The computer of the aforementioned terminal device A first generation request transmission unit transmits to the server a first generation request including notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, The aforementioned server, When the terminal device receives the first generation request, it generates the specific notification information corresponding to the notification identification information, The specific account information, the notification identification information, the device identification information, and the specific notification information are associated and stored in memory. The first generation request transmission unit, A first request signal transmission unit transmits a first request signal to the server after the first generation request has been transmitted to the server, requesting the transmission of notification information associated with the specific account information. After the first request signal is transmitted to the server, a first notification information transmission unit receives the specific notification information associated with the specific account information at the server from the server, A first display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the terminal device, A computer program that functions as such. (Item 9) A method for displaying a screen on a terminal device, A generation request receiving step in which a first terminal device receives a generation request from the first terminal device in a first login state in which the first terminal device is logged into the server using specific account information, the generation request receiving step wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, and the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device. When the aforementioned generation request is received, a generation step is performed to generate the specific notification information corresponding to the notification identification information, A first storage control step involves associating the specific account information, the notification identification information, the device identification information, and the specific notification information with each other and storing them in memory after the specific notification information has been generated. A first request signal reception step, after the specific notification information has been generated, receiving a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information, A first notification information transmission step, in which, when the first request signal is received from the first terminal device, the specific notification information associated with the specific account information is transmitted to the first terminal device; A first display control step, in which the specific notification information is displayed on the display unit of the first terminal device when the specific notification information is received from the server, A second request signal reception step is performed, after the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and a second terminal device different from the first terminal device is logged into the server using the specific account information in a second login state, and the second request signal is received from the second terminal device requesting the transmission of notification information associated with the specific account information. A second notification information transmission step, in which, when the second request signal is received from the second terminal device, the specific notification information associated with the specific account information is transmitted to the second terminal device; A second display control step, in which the specific notification information is displayed on the display unit of the second terminal device when the specific notification information is received from the server, A method that includes [a certain feature]. (Item 10) It is a communication system, A generation request receiving unit receives a generation request from a first terminal device in a first login state in which the first terminal device is logged into a server using specific account information, the generation request receiving unit receiving the generation request request including notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, When the aforementioned generation request is received, a generation unit generates the specific notification information corresponding to the notification identification information, A first storage control unit stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory after the specific notification information has been generated, in association with each other. A first request signal receiving unit receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information after the specific notification information has been generated, A first notification information transmission unit transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device, A first display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the first terminal device, After the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and in a second login state in which a second terminal device different from the first terminal device is logged into the server using the specific account information, a second request signal receiving unit receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information, A second notification information transmission unit transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device. A second display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the second terminal device, A communication system equipped with these features. [Explanation of Symbols]

[0120] 2: Communication system, 4: LAN, 6: Internet, 10: Printer, 20: Printer, 30: Printer, 100: Mobile terminal, 112: Operation unit, 114: Display unit, 120: Communication I / F, 130: Control unit, 132: CPU, 134: Memory, 140: OS program, 142: First print application, 144: First local table, 200: PC, 212: Operation unit, 214: Display unit, 220: Communication I / F, 230: Control unit, 232: CPU, 234: Memory, 240: OS program, 242: Second print application, 244: Second local table, 300: Notification server, 320: Communication I / F, 330: Control unit, 332: CPU, 334: Memory, 340: Program, 342: Management table, 344: User table, 400: Content server

Claims

1. A computer program for a server, The computer of the aforementioned server, A first generation request receiving unit receives a first generation request from a first terminal device in a first login state in which the first terminal device is logged into the server using specific account information, the first generation request receiving unit receiving the first generation request receiving unit which includes notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, A first generation unit generates the specific notification information corresponding to the notification identification information when the first generation request is received, A first storage control unit stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory after the specific notification information has been generated, in association with each other. A first request signal receiving unit receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information after the specific notification information has been generated, A first notification information transmission unit transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device, wherein the first terminal device displays the specific notification information when it receives the specific notification information from the server, After the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and in a second login state in which a second terminal device different from the first terminal device is logged into the server using the specific account information, a second request signal receiving unit receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information, A second notification information transmission unit transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device, wherein the second terminal device displays the specific notification information when it receives the specific notification information from the server, the second notification information transmission unit A computer program that functions as such.

2. The computer program according to claim 1, wherein the first generation unit, when it receives the first generation request, extracts from the memory the specific notification information that is stored in the memory in association with the notification identification information and is not stored in the memory in association with account information.

3. The first generation request indicates either that the selection operation for the specific notification information has not been performed, or that the selection operation for the specific notification information has been performed. When the first notification information transmission unit receives the first request signal from the first terminal device, it transmits to the first terminal device the first information, including the specific notification information associated with the specific account information. When the second notification information transmission unit receives the second request signal from the second terminal device, it transmits to the second terminal device the second information, including the specific notification information associated with the specific account information. If the first generation request indicates that a selection operation for the specific notification information has not been performed, the first information indicates that a selection operation for the specific notification information has not been performed. The computer program according to claim 1, wherein, when the first generation request indicates that a selection operation for the specific notification information has been performed, the first information and the second information indicate that a selection operation for the specific notification information has been performed.

4. The first generation request includes the notification identification information, the device identification information, and the selection information. The selection information indicates either a first value indicating that a selection operation for the specific notification information has not yet been performed, or a second value indicating that a selection operation for the specific notification information has already been performed. The first memory control unit, after the specific notification information is generated, stores the specific account information, the notification identification information, the device identification information, the specific notification information, and the selection information in the memory in association with each other. The first information includes the specific notification information and the selection information associated with the specific account information, The computer program according to claim 3, wherein the second information includes the specific notification information and the selection information associated with the specific account information.

5. The aforementioned computer program further uses the computer, After the specific account information, the notification identification information, the device identification information, the specific notification information, and the selection information which is the first value have been associated and stored in the memory, and in the second login state, a second generation request receiving unit receives a second generation request from the second terminal device which includes the notification identification information, the device identification information, and the selection information which is the second value, When the second generation request is received, a second storage control unit changes the selection information associated with the specific account information from the first value to the second value and stores it in the memory, A computer program according to claim 4, which functions as such.

6. The aforementioned computer program further uses the computer, A third request signal receiving unit receives a third request signal from the first terminal device requesting the transmission of notification information not associated with account information, when the first terminal device is logged out and has not logged into the server using account information. When the third request signal is received from the first terminal device, the third notification information transmission unit functions as a unit that transmits the specific notification information not associated with account information and the notification identification information to the first terminal device within the memory. The computer program according to claim 1, wherein the first generation request receiving unit receives the first generation request from the first terminal device after changing from the logout state to the first login state.

7. The aforementioned computer program further uses the computer, In the first login state, a fourth request signal receiving unit receives a fourth request signal from the first terminal device requesting the transmission of notification information not associated with account information, A fourth notification information transmission unit, which, when the fourth request signal is received from the first terminal device, transmits the specific notification information, which is not associated with account information in the memory, to the first terminal device, In the first login state, if the fourth request signal is received again from the first terminal device, the specific notification information is not transmitted. The first terminal device is After the first request signal is transmitted to the first terminal device, if the specific notification information is received from the server and a predetermined operation is accepted, the specific notification information is displayed. When the fourth request signal is transmitted to the first terminal device and the specific notification information is received from the server, the specific notification information is displayed without accepting the predetermined operation. The fourth notification information transmission unit, A fifth request signal receiving unit receives a fifth request signal from the first terminal device requesting the transmission of notification information not associated with account information after the state has changed from the first login state to the logout state. A fifth notification information transmission unit transmits to the first terminal device the specific notification information that is not associated with account information in the memory when the fifth request signal is received from the first terminal device, wherein the first terminal device, after the fifth request signal has been transmitted to the first terminal device, receives the specific notification information from the server and displays the specific notification information without accepting the predetermined operation, the fifth notification information transmission unit A computer program according to claim 1, which functions as such.

8. A computer program for a terminal device, The computer of the aforementioned terminal device A first generation request transmission unit transmits to the server a first generation request including notification identification information that identifies specific notification information and device identification information that identifies a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, The aforementioned server, When the terminal device receives the first generation request, it generates the specific notification information corresponding to the notification identification information, The specific account information, the notification identification information, the device identification information, and the specific notification information are associated and stored in memory. The first generation request transmission unit, A first request signal transmission unit transmits a first request signal to the server after the first generation request has been transmitted to the server, requesting the transmission of notification information associated with the specific account information. After the first request signal is transmitted to the server, a first notification information transmission unit receives the specific notification information associated with the specific account information at the server from the server, A first display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the terminal device, A computer program that functions as such.

9. A method for displaying a screen on a terminal device, A generation request receiving step in which a first terminal device receives a generation request from the first terminal device in a first login state in which the first terminal device is logged into the server using specific account information, the generation request receiving step wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device, and the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device. When the aforementioned generation request is received, a generation step is performed to generate the specific notification information corresponding to the notification identification information, A first storage control step involves associating the specific account information, the notification identification information, the device identification information, and the specific notification information with each other and storing them in memory after the specific notification information has been generated. A first request signal reception step, after the specific notification information has been generated, receiving a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information, A first notification information transmission step, in which, when the first request signal is received from the first terminal device, the specific notification information associated with the specific account information is transmitted to the first terminal device; A first display control step in which, when the specific notification information is received from the server, the specific notification information is displayed on the display unit of the first terminal device, A second request signal reception step is performed, after the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and a second terminal device different from the first terminal device is logged into the server using the specific account information in a second login state, and the second request signal is received from the second terminal device requesting the transmission of notification information associated with the specific account information. A second notification information transmission step, in which, when the second request signal is received from the second terminal device, the specific notification information associated with the specific account information is transmitted to the second terminal device; A second display control step, in which the specific notification information is displayed on the display unit of the second terminal device when the specific notification information is received from the server, A method that includes [a certain feature].

10. It is a communication system, A generation request receiving unit receives a generation request from a first terminal device in a first login state in which the first terminal device is logged into a server using specific account information, the generation request receiving unit receiving the generation request request from the first terminal device, the generation request receiving unit receiving the generation request request request that includes notification identification information for identifying specific notification information and device identification information for identifying a specific communication device, wherein the specific notification information is information for notifying the user of the specific communication device of the existence of a service related to the specific communication device. When the aforementioned generation request is received, a generation unit generates the specific notification information corresponding to the notification identification information, A first storage control unit stores the specific account information, the notification identification information, the device identification information, and the specific notification information in memory after the specific notification information has been generated, in association with each other. A first request signal receiving unit receives a first request signal from the first terminal device requesting the transmission of notification information associated with the specific account information after the specific notification information has been generated, A first notification information transmission unit transmits the specific notification information associated with the specific account information to the first terminal device when the first request signal is received from the first terminal device, A first display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the first terminal device, After the specific account information, the notification identification information, the device identification information, and the specific notification information have been associated and stored in the memory, and in a second login state in which a second terminal device different from the first terminal device is logged into the server using the specific account information, a second request signal receiving unit receives a second request signal from the second terminal device requesting the transmission of notification information associated with the specific account information, A second notification information transmission unit transmits the specific notification information associated with the specific account information to the second terminal device when the second request signal is received from the second terminal device. A second display control unit that, when the specific notification information is received from the server, causes the specific notification information to be displayed on the display unit of the second terminal device, A communication system equipped with these features.

Images