JP2024065336A - Terminal device and first computer program for terminal device - Google Patents

Abstract

To provide a technique for obtaining approvals twice from a user.SOLUTION: A terminal device executes a use start process for starting the use of a specific service provided by a specific server on the Internet, according to a first computer program. The specific service is a service provided to a user who uses a communication device different from the terminal device. The use start process includes: a first display process to display, on a display unit, a first screen for requesting an approval for an access to the specific server using the first computer program; and a second display process to display, on the display unit, a second screen for requesting an approval for an access to the specific server using a second computer program stored in the communication device before the use start process is completed.SELECTED DRAWING: Figure 3

Description

This specification relates to a terminal device that communicates with a server that provides a service.

Patent document 1 discloses a server that provides services related to a printer. A user contracts for the service using a terminal device, such as a PC, that is different from the printer. In the service contract, the terminal device executes a first communication with the server for purposes such as creating an account, and the printer executes a second communication with the server for purposes such as registering a serial number.

JP 2018-92558 A

The first communication is executed by a first computer program stored in the terminal device, and the second communication is executed by a second computer program stored in the printer. Here, it is assumed that before each computer program is used, consent to the use of each computer program is sought from the user. This is because the user may feel uneasy if each computer program is used without the user's consent. On the other hand, if one of the two consents is not obtained, the user cannot receive the service. This specification provides a technique for obtaining two consents from the user.

The terminal device disclosed in this specification includes a memory that stores a first computer program, a display unit, and a processing execution unit that executes a usage start process for starting the use of a specific service provided by a specific server on the Internet in accordance with the first computer program, the specific service being a service provided to a user who uses a communication device different from the terminal device, and the usage start process includes a first display process that causes the display unit to display a first screen requesting consent to access to the specific server using the first computer program, and a second screen that causes the display unit to display consent to access to the specific server using a second computer program stored in the communication device until the usage start process is completed. and a second display process in which the start-of-use process is completed when a first instruction to approve access to the specific server using the first computer program is input to the terminal device according to the first screen and a second instruction to approve access to the specific server using the second computer program is input to the terminal device according to the second screen. The device is equipped with the process execution unit, a first transmission unit that transmits a first notification to the specific server indicating that the first instruction has been input to the terminal device when the first instruction is input to the terminal device, and a second transmission unit that transmits a second notification to the specific server indicating that the second instruction has been input to the terminal device when the second instruction is input to the terminal device.

According to the above configuration, during the start-of-use process executed by the first computer program, it is possible to obtain not only consent to access a specific server using the first computer program, but also consent to access a specific server using a second computer program stored in a communication device different from the terminal device. In other words, during the start-of-use process executed by the first computer program, it is possible to obtain two consents from the user corresponding to two types of computer programs at once.

A computer program for implementing the above-mentioned terminal device, and a computer-readable storage medium for storing the computer program, are also novel and useful.

FIG. 1 is a block diagram of a communication system. FIG. 2 is a schematic diagram of each table. FIG. 3 is a sequence diagram showing a process for obtaining a registration token from a server. FIG. 4 is a sequence diagram showing a process for registering a plurality of printers in a server. FIG. 5 is a sequence diagram showing a process for requesting permission for access to a server using firmware.

(Configuration of communication system 2; FIG. 1)
The communication system 2 includes a terminal device 10, a printer 100, a printer 200, and a server 300. The terminal device 10 is, for example, a smartphone, a tablet PC, a laptop PC, or a desktop PC. The printer 100 is a peripheral device having a printing function, for example, a peripheral device of the terminal device 10. In a modified example, the printer 100 may be a multi-function device capable of executing a scanning function, a FAX function, and the like in addition to a printing function. The terminal device 10 and the printer 100 are connected to a LAN 4. The LAN 4 is wired or wireless. The LAN 4 is connected to the Internet 6. The server 300 is connected to the Internet 6. A device connected to the LAN 4, for example, the terminal device 10, is configured to communicate with the server 300 via the LAN 4 and the Internet 6. The number of printers connected to the LAN 4 is not limited to two, and may be, for example, one, or three or more.

Printers 100 and 200 are installed at a predetermined location used by a specific organization. The specific organization is, for example, a company, and the predetermined location is, for example, an office. Printers 100 and 200 are used by multiple users who belong to the specific organization. The multiple users include an administrator and individual users managed by the administrator.

(Configuration of terminal device 10; FIG. 1)
The terminal device 10 includes an operation unit 12, a display unit 14, a LAN interface 16, and a control unit 30. The units 12, 14, 16, and 30 are connected to a bus line. In the following description, the interface will be referred to as "I/F."

The operation unit 12 has a number of keys. A user can input various instructions to the terminal device 10 by operating the operation unit 12. The display unit 14 is a display that displays various information. The display unit 14 may function as a so-called touch screen (i.e., the operation unit 12). The LAN I/F 16 is an I/F for performing communication via the LAN 4, and is connected to the LAN 4.

The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the programs 40, 42, and 44 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, and the like. The operating system (OS) program 40 controls the basic operations of the terminal device 10. The token acquisition application 42 is an application program for acquiring a registration token from the server 300. The token acquisition application 42 includes a program ID "pr1" that identifies the token acquisition application 42. The registration token is used to register a printer (e.g., 100) to the server 300. The registration application 44 is an application program for registering multiple printers to the server 300.

The token acquisition application 42 and the registration application 44 are provided by the vendor of the printers 100 and 200. In the following, the vendor of the printers 100 and 200 will be referred to as the "printer vendor." The token acquisition application 42 and the registration application 44 are installed in the terminal device 10, for example, from a server on the Internet. In a modified example, the token acquisition application 42 and the registration application 44 may be provided by a business entity other than the printer vendor.

(Configuration of Printers 100 and 200; FIG. 1)
The printer 100 stores firmware 140 that controls the operation of the printer 100. The firmware 140 includes a program ID “pr2” that identifies the firmware 140.

The printer 100 also stores a serial number SN1 that identifies the printer 100. The serial number SN1 is assigned by the printer vendor when the printer 100 is manufactured.

Printer 200 is similar to printer 100, except that printer 200 stores a serial number SN2 that identifies printer 200. Printer 200 stores the same firmware 140 as printer 100.

(Configuration of server 300; Figs. 1 and 2)
The server 300 provides an intermediation service that mediates the transmission of print data from the terminal device 10 to a printer (e.g., 100). The server 300 issues a program ID that identifies the program to be used in response to a request from a business that has created a program to be used for utilizing the intermediation service, such as a printer vendor. The program to be used is, for example, a token acquisition application 42 and firmware 140. For example, the printer vendor writes the program ID "pr1" issued by the server 300 in the token acquisition application 42.

Server 300 stores tables 350, 352, 354, and 356 that manage information for providing intermediation services.

The ID table 350 manages the program IDs issued by the server 300. The ID table 350 stores a plurality of program IDs. As shown in FIG. 2, the ID table 350 stores the creator name and the authority information in association with the program ID. The creator name is the name of the business entity that created the utilization program identified by the program ID. The authority information indicates a list of one or more functions that are permitted to the utilization program identified by the program ID, out of the plurality of functions possessed by the server 300.

The organization table 352 manages organizations that use the intermediary service. The organization table 352 stores an organization ID, a user ID, and a password in association with each other. The organization table 352 stores multiple organization IDs. As shown in FIG. 2, multiple user IDs and multiple passwords are stored in association with one organization ID.

The organization ID identifies an organization. The user ID identifies a user who belongs to an organization. For example, the user ID "admin" and the user ID "user1" are stored in association with the organization ID "org1". The user ID "admin" identifies an administrator who belongs to the organization identified by the organization ID "org1", and the user ID "user1" identifies an individual user who belongs to the organization identified by the organization ID "org1". In the following, the organization identified by the organization ID "org1" is referred to as the organization "org1", and the administrator identified by the user ID "admin" is referred to as the administrator "admin".

The consent table 354 stores the organization ID and the consent information in association with each other. The consent information indicates that consent to access the server 300 using the program being used has been obtained from an administrator belonging to the organization identified by the organization ID. For example, when consent to access the server 300 using the token acquisition application 42 is obtained from the administrator "admin", the server 300 stores the consent information CI1 in the consent table 354 in association with the organization ID "org1". The consent information CI1 is, for example, a flag value corresponding to the program ID "pr1" that identifies the token acquisition application 42. In a modified example, the consent information CI1 may be the program ID "pr1" itself. Also, for example, when consent to access the server 300 using the firmware 140 is obtained from the administrator "admin", the server 300 stores the consent information CI2 in the consent table 354 in association with the organization ID "org1".

The registration table 356 registers printers used by the organization for which the intermediation service is provided. The registration table 356 stores an organization ID, a serial number, and an access token in association with each other. The access token is information for authenticating communication between the printer registered in the server 300 and the server 300.

As shown in FIG. 2, multiple serial numbers and multiple access tokens are stored in association with one organization ID. Storing a serial number in registration table 356 means that the printer identified by that serial number has been registered in server 300.

(Obtaining a registration token; Figure 3)
A process for acquiring a registration token from the server 300 will be described with reference to FIG. 3. In the following, for ease of understanding, the operation executed by the CPU 32 of the terminal device 10 in accordance with the token acquisition application 42 will be described with the token acquisition application 42 as the subject, rather than with the CPU 32 as the subject. In addition, since all of the following communications are executed via the LAN I/F 16 and the LAN 4, the following description of "via the LAN I/F 16" and "via the LAN 4" will be omitted. In addition, since the communication between the terminal device 10 and the server 300 is executed via the Internet 6, the following description of "via the Internet 6" will be omitted. In addition, in the following, the token acquisition application 42 may be described as "application 42".

In the initial state of FIG. 3, no consent to access the server 300 has been obtained from the administrator "admin" belonging to the organization "org1". Therefore, the consent table 354 of the server 300 does not store consent information CI1 and CI2 in association with the organization ID "org1".

The terminal device 10 launches the app 42 in response to a predetermined operation from the user. At T12, the app 42 displays a login screen on the display unit 14. The login screen includes input fields for inputting a user ID and a password.

At T14, the administrator "admin" enters the user ID "admin" and the password "xxxx" into the login screen displayed at T12. As a result, at T16, the app 42 establishes a login session with the server 300.

At T20, in response to a predetermined operation from the user, the app 42 transmits a registration token request to the server 300, requesting transmission of a registration token. The registration token request includes the program ID "pr1" that identifies the app 42.

When the server 300 receives a registration token request from the app 42 in T20, the server 300 determines whether or not consent to access to the server 300 using the app 42 has been obtained from the administrator "admin" in T22. Specifically, the server 300 acquires the organization ID "org1" stored in association with the currently logged-in user ID "admin" from the organization table 352. The server 300 determines whether or not the consent information CI1 is stored in association with the acquired organization ID "org1" in the consent table 354. In this case, the server 300 determines in T22 that the consent information CI1 is not stored in association with the acquired organization ID "org1" in the consent table 354, and proceeds to processing from T24 onwards. If the server 300 determines that the consent information CI1 is stored in association with the acquired organization ID "org1" in the consent table 354, instead of T24, the server 300 transmits a specific notification to the app 42. The specific notification is a signal notifying that consent has been obtained from the administrator "admin". This causes the application 42 to skip T26 and proceed to T40.

At T24, the server 300 sends an application consent request to the application 42, requesting consent for access to the server 300 using the application 42. The application consent request includes information stored in the ID table 350 in association with the program ID "pr1" included in the registration token request of T20, i.e., the creator name "AAA.Ltd" and the authority information AI1.

When the app 42 receives an app consent request from the server 300 in T24, the app 42 displays a consent request screen SC1 on the display unit 14 in T26. The consent request screen SC1 includes a consent button BT1 that requests the administrator "admin" to consent to access to the server 300 using the app 42. The consent request screen SC1 displays the name of the app 42 and the creator name "AAA.Ltd" included in the app consent request. Although not shown, the consent request screen SC1 also displays a list of functions indicated by the authority information AI1 included in the app consent request, i.e., functions permitted for the app 42. The consent request screen SC1 includes a cancel button, and if the cancel button is selected, T28 and subsequent steps are skipped and the processing in FIG. 3 ends.

In this case, the administrator "admin" looks at the information in the consent request screen SC1, i.e., the creator name "AAA.Ltd" and the list indicated by the authority information AI1, and consents to access to the server 300 using the application 42. At T28, the administrator "admin" selects the consent button BT1 in the consent request screen SC1.

When the app 42 acquires a signal indicating that the consent button BT1 has been selected from the operation unit 12 at T28, the app 42 transmits an app consent notification to the server 300 at T30. The app consent notification is a signal for notifying the server 300 that the consent button BT1 has been selected.

When the server 300 receives an application consent notification from the application 42 at T30, at T32, the server 300 stores the consent information CI1 in the consent table 354 in association with the organization ID "org1".

In addition, at T40 following T30, the app 42 transmits a firmware confirmation signal to the server 300. The firmware confirmation signal is a signal for confirming whether or not permission has been obtained from the administrator "admin" to access the server 300 using the firmware 140. The firmware confirmation signal includes a program ID "pr2" that identifies the firmware 140. The program ID "pr2" is pre-stored in the app 42.

When the server 300 receives a firmware confirmation signal from the application 42 in T40, the server 300 determines in T42 whether consent has been obtained from the administrator "admin" to access the server 300 using the firmware 140. Specifically, the server 300 determines whether consent information CI2 is stored in the consent table 354 in association with the organization ID "org1". In this case, the server 300 determines in T42 that consent information CI2 is not stored in the consent table 354 in association with the organization ID "org1", and proceeds to processing from T44 onwards. If the server 300 determines that consent information CI2 is stored in the consent table 354 in association with the organization ID "org1", it skips T44 and proceeds to T60.

At T44, the server 300 transmits to the application 42 a firmware approval request requesting approval for access to the server 300 using the firmware 140. The firmware approval request includes information stored in the ID table 350 in association with the program ID "pr2" included in the firmware confirmation signal of T40, i.e., the creator name "AAA.Ltd" and the authority information AI2.

When the application 42 receives a firmware consent request from the server 300 in T44, it displays a consent request screen SC2 on the display unit 14 in T46. The consent request screen SC2 includes a consent button BT2 that requests the administrator "admin" to consent to access to the server 300 using the firmware 140. The consent request screen SC2 displays the name of the firmware 140 and the creator name "AAA.Ltd" included in the firmware consent request. Although not shown, the consent request screen SC2 also displays a list of one or more functions indicated by the authority information AI2 included in the firmware consent request. Note that the consent request screen SC2 includes a cancel button, and if the cancel button is selected, T48 and subsequent steps are skipped and the processing in FIG. 3 ends.

In this case, the administrator "admin" looks at the information in the consent request screen SC2, i.e., the creator name "AAA.Ltd" and the list indicated by the authority information AI2, and consents to access to the server 300 using the firmware 140. At T48, the administrator "admin" selects the consent button BT2 in the consent request screen SC2.

When the app 42 acquires a signal indicating that the accept button BT2 has been selected from the operation unit 12 at T48, the app 42 transmits a firmware acceptance notification to the server 300 at T50. The firmware acceptance notification is a signal for notifying the server 300 that the accept button BT2 has been selected.

When the server 300 receives a firmware consent notification from the app 42 at T50, the server 300 stores consent information CI2 in the consent table 354 in association with the organization ID "org1" at T52. As a result, information indicating that consent has been obtained for both the app 42 and the firmware 140 is stored in the server 300.

In the next step T60, the server 300 generates a registration token RT1. In T62, the server 300 associates the registration token RT1 with the organization ID "org1" and stores the registration token RT1 in the server 300. In T64, the server 300 transmits the registration token RT1 to the application 42. Since the printer is registered using the registration token RT1, the administrator "admin" does not need to input a user ID and password to the printer. Note that the timing of the execution of the processes from T60 to T64 is not limited to the timing shown in FIG. 3, and may be executed between T30 and T40, for example. Generally speaking, the generation, storage, and transmission of the registration token RT1 may be executed after the application acceptance notification of T30 is received.

When permission for access using app 42 and permission for access using firmware 140 are both obtained, the process in Figure 3 is completed.

(Printer registration; Figure 4)
Fig. 4 describes the process for registering multiple printers in the server 300. Fig. 4 is a continuation of T64 in Fig. 3. In the following, for ease of understanding, the operations executed by the CPU 32 of the terminal device 10 in accordance with the registered application 44 will be described mainly in terms of the registered application 44, rather than mainly in terms of the CPU 32. In addition, in the following, the registered application 44 may be described as "application 44".

The terminal device 10 starts the app 44 in response to a predetermined operation from the user. In a modified example, the app 42 may start the app 44 in response to reception of the registration token RT1 at T64 in FIG. 3 as a trigger.

The application 44 searches for printers 100 and 200 connected to the LAN 4. The application 44 transmits the registration token RT1 to one or more of the searched printers. In this case, the application 44 transmits the registration token RT1 to the printer 100 at T102, and transmits the registration token RT1 to the printer 200 at T104. For example, the processes of T102 and T104 may be executed at the same timing. Also, for example, the processes of T102 and T104 may be executed sequentially within a predetermined time. The predetermined time is, for example, 5 seconds. Both the printers 100 and 200 execute the same process using the registration token RT1. The process executed by the printer 100 is described below.

In T110, the printer 100 transmits a registration request to the server 300, requesting the server 300 to register the printer 100. The registration request includes the registration token RT1 received in T102, the serial number SN1 that identifies the printer 100, and the program ID "pr2" that identifies the firmware 140.

When the server 300 receives a registration request from the printer 100 in T110, it determines whether a registration token matching the registration token RT1 included in the registration request is stored in the server 300. In this case, the registration token RT1 included in the registration request matches the registration token RT1 stored in T62 of FIG. 3. This allows the server 300 to authenticate that the printer 100 that sent the registration request is managed by the administrator "admin" who executed the process in FIG. 3. Then, in T112, the server 300 identifies the organization ID "org1" that is stored in association with the registration token RT1.

The next step T114 is the same as T42 in FIG. 3, except that the program ID "pr2" included in the registration request is used. In this case, in T52 in FIG. 3, consent to access to the server 300 using the firmware 140 is obtained from the administrator "admin", and consent information CI2 has already been stored in the consent table 354. In this case, in T114, the server 300 determines that consent information CI2 is stored in the consent table 354 in association with the organization ID "org1", and proceeds to processing from T116 onwards. Note that if it is determined that consent information CI2 is not stored in the consent table 354 in association with the organization ID "org1", processing from T116 onwards is not executed. In this case, the server 300 sends a notification to the printer 100 indicating that registration of the printer 100 has failed.

In T116, the server 300 generates an access token AT1. The access token AT1 is information for authenticating communication between the printer 100 and the server 300. In T118, the server 300 stores the serial number SN1 in the registration request and the generated access token AT1 in the registration table 356 in association with the organization ID "org1" identified in T112. This causes the printer 100 to be registered in the server 300.

At T120, the server 300 sends a success notification to the printer 100 indicating that the registration of the printer 100 was successful. The success notification includes the access token AT1.

In addition, after the application 44 transmits the registration token RT1 to the printers 100 and 200 at T102 and T104, it repeatedly transmits a registration confirmation signal to each of the printers 100 and 200. The registration confirmation signal is a polling signal for confirming the successful registration of the printer.

At T130, the app 44 sends a registration confirmation signal to the printer 100 after the printer 100 receives a success notification from the server 300. At T132, the app 44 receives a success response from the printer 100, indicating that the registration of the printer 100 was successful, as a response to the registration confirmation signal. This allows the app 44 to know that the registration of the printer 100 was successful.

In addition, at T140 after T120, the server 300 uses the access token AT1 included in the success notification to establish a constant connection with the server 300. Once the constant connection is established, the server 300 can transmit a signal to the printer 100 beyond the firewall of the LAN4 without receiving a request from the printer 100. The constant connection is, for example, a connection according to the Extensible Messaging and Presence Protocol (XMPP) or a connection according to the Hypertext Transfer Protocol Secure (HTTPS). Establishing the constant connection allows the user to use the intermediary service.

For example, in order to use the intermediation service, a user operates the terminal device 10 to log in to the server 300. The terminal device 10 transmits print data to the server 300 in response to instructions from the user. The server 300 transmits the print data received from the terminal device 10 to the printer 100 using a constant connection without receiving a request from the terminal device 10. When the printer 100 receives the print data from the server 300, it prints an image according to the print data.

For printer 200, the same processing as T110 to T140 is executed, and the serial number SN2 of printer 200 and the access token AT2 used by printer 200 are stored in registration table 356. This allows the user to use the intermediation service with printer 200 as well.

(Another method for firmware authentication; Figure 5)
With reference to Fig. 5, another method of requesting permission for access to the server 300 using the firmware 140 will be described. The process of Fig. 5 is executed separately from the process of Fig. 3, in place of the processes of T40 to T52 in Fig. 3. The printers 100 and 200 have a server function that operates as a server in addition to a printing function. In the server function, the printers 100 and 200 provide a setting screen to a terminal device. For example, a user can operate the setting screen provided by the printer 100 to change the settings of the printer 100, for example, the network settings.

In response to an instruction from a user, the terminal device 10 sends an HTTP command to the printer 100 in accordance with a browser program installed in the terminal device 10. Here, HTTP stands for Hyper Text Transfer Protocol. Note that the process executed by the terminal device 10 in FIG. 5 is executed in accordance with the browser program.

At T204, the terminal device 10 receives setting screen information from the printer 100 as a response to the HTTP command of T202.

At T206, the terminal device 10 displays a setting screen corresponding to the setting screen information on the display unit 14. The setting screen includes buttons for changing various settings of the printer 100. In this embodiment, the setting screen includes a predetermined button for accepting access to the server 300 using the firmware 140.

In T208, the user selects a specific button on the setting screen. In response to the selection of the specific button, in T210, the terminal device 10 transmits a communication execution request to the printer 100.

When the printer 100 receives a communication execution request from the terminal device 10 at T210, the printer 100 transmits the program ID "pr2" to the server 300 at T212. At T214, the printer 100 receives a login request from the server 300. At T216, the printer 100 transmits login screen information to the terminal device 10 in accordance with the login request received from the server 300. The login screen information is information corresponding to the login screen.

When the terminal device 10 receives the login screen information from the printer 100 at T216, it displays the login screen on the display unit 14 at T218.

At T220, the administrator "admin" enters the user ID "admin" and password "xxxx" into the login screen displayed at T218. As a result, at T222, the terminal device 10 transmits the information entered into the login screen to the server 300. As a result, at T224, a login session is established between the terminal device 10 and the server 300.

When the server 300 establishes a login session with the terminal device 10 in T224, the process proceeds to T226. T226 is the same as T42 in FIG. 3. In this case, consent information CI2 is not stored in the consent table 354 in association with the acquired organization ID "org1". Therefore, in T226, the server 300 determines that consent to accessing the server 300 using the firmware 140 has not been obtained from the administrator "admin", and the process proceeds to T228. T228 is the same as T44 in FIG. 3.

When the terminal device 10 receives a firmware approval request from the server 300 at T228, it displays an approval request screen SC2 on the display unit 14 at T232. T234 and T236 are the same as T48 and T50 in FIG. 3.

When the server 300 receives a firmware consent request from the terminal device 10 at T236, it stores consent information CI2 in the consent table 354 in association with the organization ID "org1" at T240. Note that in this case, the process of FIG. 5 is executed before the process of FIG. 3 is executed. Therefore, consent information CI1 is not currently stored in the consent table 354.

In T242, the server 300 sends a completion notification to the printer 100 indicating that processing of T240 has been completed.

When the printer 100 receives a completion notification from the server 300 in T242, the printer 100 transmits notification screen information to the terminal device 10 in T244. The notification screen information is information corresponding to a notification screen for notifying the user that the processing in T240 has been completed.

When the terminal device 10 receives the notification screen information from the printer 100 at T244, it displays the notification screen on the display unit 14 at T246. This allows the administrator "admin" to know that the processing corresponding to the selection of the consent button BT2 has been completed by the server 300.

(Effects of this embodiment)
3 executed by the token acquisition application 42, it is possible to obtain not only consent to access the server 300 using the token acquisition application 42 (T26 in FIG. 3), but also consent to access the server 300 using the firmware 140 stored in a printer 100 different from the terminal device 10 (T48). That is, in the process of FIG. 3 executed by the token acquisition application 42, it is possible to obtain two consents from the user at once, corresponding to two types of computer programs, that is, the token acquisition application 42 and the firmware 140.

For example, a comparative example is assumed in which the processes from T40 to T52 in FIG. 3 are not executed. In this comparative example, for example, the administrator "admin" consents to access to the server 300 using the firmware 140 by the process in FIG. 5. However, if the administrator forgets to execute the process in FIG. 5, even if the process in FIG. 4 is executed following the process in FIG. 3, it is determined in T114 in FIG. 4 that consent to the firmware 140 has not been obtained. As a result, registration of the printer 100 to the server 300 fails.

In contrast, according to the configuration of this embodiment, in T48 of FIG. 3, it is possible to obtain consent not only for the token acquisition application 42 but also for the firmware 140. This makes it possible to prevent failure of registration of the printer 100 with the server 300 due to failure to obtain consent for the firmware 140. The user does not need to obtain two types of consent at separate times. This improves user convenience.

The terminal device 10 also uses the registration app 44 to send the registration token RT1 to the printer 100 (T102 in FIG. 4). This improves user convenience compared to a configuration in which the registration token RT1 is manually input into the printer 100. Note that in a modified example, the configuration of the comparative example described above may be adopted. Furthermore, the registration app 44 has a function of sending the registration token RT1 to multiple printers with a single instruction from the user, for example, an instruction to start the registration app 44 (T102 and T104). This further improves user convenience.

A comparative example is also envisaged in which the determination of T42 in FIG. 3 is not executed. In this comparative example, even if consent of the firmware 140 has been obtained, the consent request screen SC2 is displayed on the terminal device 10 in the process of FIG. 3. In this embodiment, the determination of T42 in FIG. 3 can be used to prevent the consent request screen SC2 from being displayed unnecessarily. Note that in a modified example, the configuration of the comparative example in which the determination of T42 is not executed may be adopted.

(Correspondence)
The terminal device 10, the token acquisition application 42, and the registration application 44 are examples of a "terminal device", a "first computer program", and a "third computer program", respectively. The memory 34 and the display unit 14 are examples of a "memory" and a "display unit", respectively. The control unit 30 that transmits the registration token RT1 to the server 300 via the LAN I/F 16 is an example of an "output unit". The server 300 and the intermediation service are examples of a "specific server" and a "specific service", respectively. The printer 100 and the firmware 140 are examples of a "communication device" and a "second computer program", respectively. The process of FIG. 3 is an example of a "use start process". T26, T46, T64, and T42 in FIG. 3 are examples of a "first display process", a "second display process", a "reception process", and a "determination process", respectively. The consent request screen SC1, the consent request screen SC2, the consent button BT1, and the consent button BT2 are examples of a "first screen", a "second screen", a "first button", and a "second button", respectively. The selection of the acceptance button BT1 and the selection of the acceptance button BT2 are examples of a “first instruction” and a “second instruction”, respectively. The application acceptance notification of T30 and the firmware acceptance notification of T50 are examples of a “first notification” and a “second notification”, respectively. The registration token RT1 is an example of “authentication information”.

T26 and T48 in FIG. 3 are examples of processing realized by a "processing execution unit." T30 and T50 are examples of processing realized by a "first transmission unit" and a "second transmission unit," respectively.

Although specific examples of the present invention have been described above in detail, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples given above. Modifications of the above examples are listed below.

(Variation 1) The "first instruction" is not limited to selecting the acceptance button BT1 in the acceptance request screen SC1, but may be, for example, selecting a specific button on a keyboard. The "second instruction" is also not limited to selecting the acceptance button BT2 in the acceptance request screen SC2, but may be, for example, selecting a specific button on a keyboard.

(Variation 2) The processes of T64 in FIG. 3 and T102 and T104 in FIG. 4 do not need to be executed. In this variation, the "reception process" and "output section" can be omitted.

(Variation 3) The registration token RT1 may be displayed, for example, on the display unit 14. Also, an information code obtained by encoding the registration token RT1, for example, a barcode or a two-dimensional code, may be displayed on the display unit 14. In this variation, the control unit 30 that displays the above information on the display unit 14 is an example of an "output unit."

(Variation 4) The instruction to send the registration token RT1 to multiple printers does not have to be a single instruction. For example, the instruction to execute T104 in FIG. 4 may be issued at a different time from the instruction to execute T102.

(Variation 5) The "specific service" may be, for example, a service that collects and manages the status of the printer 100, or a service that collects the usage amount of consumables of the printer 100 and automatically dispatches the consumables.

(Variation 6) The "communication device" is not limited to a printer, but may be, for example, a desktop PC or a laptop PC.

(Variation 7) In the above embodiment, the CPU 32 executes the programs 40, 42, and 44 to realize the processes in FIG. 3 to FIG. 5. Alternatively, any of the processes may be realized by hardware such as a logic circuit.

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

In the scope of the claims at the time of filing of this patent application, even if each claim is dependent on only some of the claims, it is not limited to the fact that each claim can be dependent on only those some of the claims. Each claim can also be dependent on other claims that are not dependent on it at the time of filing to the extent that there is no technical contradiction. In other words, the technology of each claim can be combined in various ways as follows:
(Item 1)
A terminal device,
a memory storing a first computer program;
A display unit;
a process execution unit that executes a usage start process for starting to use a specific service provided by a specific server on the Internet in accordance with the first computer program,
the specific service is a service provided to a user who uses a communication device different from the terminal device,
The start-of-use process includes:
a first display process for displaying a first screen on the display unit, the first screen requesting consent for access to the specific server using the first computer program;
a second display process for displaying, on the display unit, a second screen requesting consent for access to the specific server using a second computer program stored in the communication device until the use start process is completed;
Including,
the process execution unit, which completes the usage start process when a first instruction to approve the access to the specific server using the first computer program is input to the terminal device according to the first screen, and a second instruction to approve the access to the specific server using the second computer program is input to the terminal device according to the second screen;
a first transmission unit that, when the first instruction is input to the terminal device, transmits a first notification indicating that the first instruction has been input to the terminal device to the specific server;
a second transmission unit that, when the second instruction is input to the terminal device, transmits a second notification indicating that the second instruction has been input to the terminal device to the specific server;
A terminal device comprising:
(Item 2)
The start-of-use process further includes:
a receiving process of receiving authentication information from the specific server when the first instruction is input;
The terminal device further comprises:
an output unit that outputs the authentication information to an outside when the authentication information is received from the specific server;
the authentication information is information for the specific server to authenticate the communication device,
2. The terminal device according to claim 1, wherein the authentication information output by the terminal device is input to the communication device.
(Item 3)
the second computer program has a function of transmitting the authentication information input to the communication device to the specific server;
3. The terminal device according to claim 2, wherein the specific server registers information for identifying the communication device in the specific server when authentication using the authentication information received from the communication device is successful.
(Item 4)
the memory further stores a third computer program different from the first computer program;
4. The terminal device according to claim 2, wherein the output unit outputs the authentication information to the outside by transmitting the authentication information to the communication device in accordance with the third computer program.
(Item 5)
5. The terminal device according to claim 4, wherein the output unit transmits the authentication information to a plurality of the communication devices.
(Item 6)
The start-of-use process further includes:
a determination process for determining whether or not permission for access to the specific server using the second computer program has been obtained before the start-of-use process is completed;
when it is determined in the determination process that permission to access the specific server using the second computer program has not been obtained, the second display process is executed;
6. The terminal device according to any one of claims 1 to 5, wherein, in the judgment process, if it is determined that consent to access the specific server using the second computer program has been obtained, the second display process is not executed.
(Item 7)
the first instruction is to select a first button in the first screen;
7. The terminal device according to any one of items 1 to 6, wherein the second instruction is to select a second button in the second screen.
(Item 8)
the communication device has a printing function;
the specific service is a service that mediates transmission of print data from the terminal device to the communication device,
8. The terminal device according to any one of items 1 to 7, wherein the second computer program has a function of receiving the print data from the specific server after the first notification and the second notification are sent to the specific server.
(Item 9)
A first computer program for a terminal device, comprising:
The terminal device
A display unit;
A computer,
Equipped with
The first computer program causes the computer to include the following units:
A process execution unit that executes a usage start process for starting to use a specific service provided by a specific server on the Internet,
the specific service is a service provided to a user who uses a communication device different from the terminal device,
The start-of-use process includes:
a first display process for displaying a first screen on the display unit, the first screen requesting consent for access to the specific server using the first computer program;
a second display process for displaying, on the display unit, a second screen requesting consent to access to the specific server using a second computer program stored in the communication device until the use start process is completed;
Including,
the process execution unit, which completes the usage start process when a first instruction for authorizing access to the specific server using the first computer program is input to the terminal device according to the first screen, and a second instruction for authorizing access to the specific server using the second computer program is input to the terminal device according to the second screen;
a first transmission unit that, when the first instruction is input to the terminal device, transmits a first notification indicating that the first instruction has been input to the terminal device to the specific server;
a second transmission unit that, when the second instruction is input to the terminal device, transmits a second notification indicating that the second instruction has been input to the terminal device to the specific server;
A first computer program that functions as:

2: Communication system 4: LAN
6: Internet 10: Terminal device 12: Operation unit 14: Display unit 16: LAN I/F
30: Control unit 32: CPU
34: Memory 40: Token acquisition application 44: Bulk registration application 100, 200: Printer 140: Firmware 300: Server 350: ID table 352: Organization table 354: Consent table 356: Registration table AI1, AI2: Authority information AT1, AT2: Access tokens BT1, BT2: Consent buttons CI1, CI2: Consent information RT1: Registration tokens SC1, SC2: Consent request screens SN1, SN2: Serial number

Claims (9)

A terminal device,
a memory storing a first computer program;
A display unit;
a process execution unit that executes a usage start process for starting to use a specific service provided by a specific server on the Internet in accordance with the first computer program,
the specific service is a service provided to a user who uses a communication device different from the terminal device,
The start-of-use process includes:
a first display process for displaying a first screen on the display unit, the first screen requesting consent for access to the specific server using the first computer program;
a second display process for displaying, on the display unit, a second screen requesting consent to access to the specific server using a second computer program stored in the communication device until the use start process is completed;
Including,
the process execution unit, which completes the usage start process when a first instruction for authorizing access to the specific server using the first computer program is input to the terminal device according to the first screen, and a second instruction for authorizing access to the specific server using the second computer program is input to the terminal device according to the second screen;
a first transmission unit that, when the first instruction is input to the terminal device, transmits a first notification indicating that the first instruction has been input to the terminal device to the specific server;
a second transmission unit that, when the second instruction is input to the terminal device, transmits a second notification indicating that the second instruction has been input to the terminal device to the specific server;
A terminal device comprising: The start-of-use process further includes:
a receiving process of receiving authentication information from the specific server when the first instruction is input;
The terminal device further comprises:
an output unit that outputs the authentication information to an outside when the authentication information is received from the specific server;
the authentication information is information for the specific server to authenticate the communication device,
The terminal device according to claim 1 , wherein the authentication information output by the terminal device is input to the communication device. the second computer program has a function of transmitting the authentication information input to the communication device to the specific server;
The terminal device according to claim 2 , wherein the specific server registers information for identifying the communication device in the specific server when authentication using the authentication information received from the communication device is successful. the memory further stores a third computer program different from the first computer program;
The terminal device according to claim 2 , wherein the output unit outputs the authentication information to the outside by transmitting the authentication information to the communication device in accordance with the third computer program. The terminal device according to claim 4, wherein the output unit transmits the authentication information to a plurality of the communication devices. The start-of-use process further includes:
a determination process for determining whether or not permission for access to the specific server using the second computer program has been obtained before the start-of-use process is completed;
when it is determined in the determination process that permission for accessing the specific server using the second computer program has not been obtained, the second display process is executed;
The terminal device according to claim 1 , wherein the second display process is not executed when it is determined in the judgment process that permission for access to the specific server using the second computer program has been obtained. the first instruction is to select a first button in the first screen;
The terminal device according to claim 1 , wherein the second instruction is to select a second button in the second screen. the communication device has a printing function;
the specific service is a service that mediates transmission of print data from the terminal device to the communication device,
6. The terminal device according to claim 1, wherein the second computer program has a function of receiving the print data from the specific server after the first notification and the second notification are sent to the specific server. A first computer program for a terminal device, comprising:
The terminal device
A display unit;
A computer,
Equipped with
The first computer program causes the computer to include the following units:
A process execution unit that executes a usage start process for starting to use a specific service provided by a specific server on the Internet,
the specific service is a service provided to a user who uses a communication device different from the terminal device,
The start-of-use process includes:
a first display process for displaying a first screen on the display unit, the first screen requesting consent for access to the specific server using the first computer program;
a second display process for displaying, on the display unit, a second screen requesting consent to access to the specific server using a second computer program stored in the communication device until the use start process is completed;
Including,
the process execution unit, which completes the usage start process when a first instruction for authorizing access to the specific server using the first computer program is input to the terminal device according to the first screen, and a second instruction for authorizing access to the specific server using the second computer program is input to the terminal device according to the second screen;
a first transmission unit that, when the first instruction is input to the terminal device, transmits a first notification indicating that the first instruction has been input to the terminal device to the specific server;
a second transmission unit that, when the second instruction is input to the terminal device, transmits a second notification indicating that the second instruction has been input to the terminal device to the specific server;
A first computer program that functions as:

Images