Communication system, server, and computer program

Abstract

To reduce an inconvenience that could occur in user registration associated with a device.SOLUTION: A server receives device identification information and a request for registration of a second user from a second terminal device after registration of a first user and, when the request for registration of second user is received, transmits a rejection notification indicating rejection of registration of second user to the second terminal device. When specific authentication information is received from a specific device in an administrator log-in state after transmission of the rejection notification, the server acquires first user information associated with device identification information associated with the specific authentication information in a storage unit and notifies the acquired first user information to a specific notification destination. Otherwise, when specific authentication information is received from a specific device in an administrator log-in state after transmitting the rejection notification, the server updates registration information that associates registration information with second user information and device identification information and thereby performs registration of the second user.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present specification relates to a communication system, a server, and a computer program. [Background technology]

[0002] Patent Document 1 discloses an information processing system that provides a member registration form. In this system, an input form including multiple input fields is displayed on a terminal device, and the user is prompted to input information into the input fields. If input into the input form is interrupted and member registration is not completed, the interruption of input is registered on the server. For users who interrupted member registration in the previously presented input form, an input form modified to reduce the amount of information to be entered is presented. This is said to make it easier for users to complete member registration. [Prior art documents] [Non-patent literature]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-84291 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above technology does not take into consideration user registration associated with a device. For example, in user registration associated with a device, if a user has already registered a device, other users may not be able to register the device. In user registration associated with a device, there is room for improvement in dealing with such cases.

[0005] This specification discloses a technique that can reduce inconveniences that may occur when registering a user associated with a device. [Means for solving the problem]

[0006] The techniques disclosed in this specification can be implemented in the following application examples.

[0007] [Application Example 1] A communication system includes a first terminal device used by a first user, a second terminal device used by a second user, a specific device, and a server having a storage unit and communicably connected to the first terminal device, the second terminal device, and the specific device, wherein the server includes a first receiving unit that receives from the first terminal device first user information that is information of the first user, device identification information that identifies the specific device, and a registration request for the first user, a registration unit that, when the registration request for the first user is received, registers the first user by storing registration information that associates the first user information with the device identification information in the storage unit, an authentication information storage processing unit that, when registering the first user, stores specific authentication information in the storage unit in association with the device identification information, an authentication information transmission processing unit that, when registering the first user, transmits the specific authentication information to the specific device, and a processing unit that performs the registration of the first user. a second receiving unit that receives the device identification information and a registration request for the second user from the second terminal device after the first receiving unit receives the device identification information and the second user's registration request; a response sending unit that, when the registration request for the second user is received, sends to the second terminal device a rejection notification indicating that the registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device in an administrator login state after sending the rejection notification, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; an acquiring unit that, when the specific authentication information is received, acquires the first user information associated with the device identification information that is associated with the specific authentication information in the storage unit; and a notification unit that, when the specific authentication information is received, notifies a specific notification destination of the first user information acquired by the acquiring unit.

[0008] According to the above configuration, when registering a first user, the server stores specific authentication information in a storage unit in association with device identification information and transmits the specific authentication information to the specific device. After registering the first user, the server receives a registration request for a second user from a second terminal device. When the server receives the specific authentication information from the specific device, the server notifies a specific notification destination of the first user information associated with the device identification information associated with the specific authentication information. As a result, even if a second user cannot be registered for a specific device because the first user has already been registered for the specific device, the first user information is notified to the specific notification destination, allowing the specific notification destination to take some action based on the first user information. Furthermore, since notification of the first user information is provided only when the specific authentication information is received from a specific device to which an administrator is logged in, unauthorized leakage of the first user information can be prevented. This reduces potential inconveniences that may occur when registering a user associated with a specific device.

[0009] [Application Example 2] A communication system includes a first terminal device used by a first user, a second terminal device used by a second user, a specific device, and a server having a storage unit and communicably connected to the first terminal device, the second terminal device, and the specific device, wherein the server includes a first receiving unit that receives from the first terminal device first user information that is information of the first user, device identification information that identifies the specific device, and a registration request for the first user, a first registration unit that, when the registration request for the first user is received, executes registration of the first user by storing registration information that associates the first user information with the device identification information in the storage unit, an authentication information storage processing unit that, when registering the first user, associates specific authentication information with the device identification information and stores it in the storage unit, an authentication information transmission processing unit that, when registering the first user, transmits the specific authentication information to the specific device, and, after registering the first user, receives second user information that is information of a second user from the second terminal device. a second receiving unit that receives user information, the device identification information, and a registration request for the second user; a response sending unit that, when the registration request for the second user is received, sends to the second terminal device a rejection notice indicating that registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device in an administrator login state after sending the rejection notice, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; a registration specifying unit that, when the specific authentication information is received, specifies the registration information in the storage unit including the device identification information that is associated with the specific authentication information; and a second registration unit that, when the specific authentication information is received, executes registration of the second user by updating the specified registration information in the storage unit to registration information that associates the second user information with the device identification information.

[0010] According to the above configuration, when registering a first user, the server stores specific authentication information in the storage unit in association with device identification information and transmits the specific authentication information to the specific device. Then, after registering the first user, if a registration request for a second user is received from a second terminal device, the server registers the second user on the condition that the specific authentication information is received from the specific device in an administrator logged-in state. As a result, it is possible to prevent the inconvenience of being unable to register a second user when the first user has already been registered for the specific device. Therefore, it is possible to reduce the inconvenience that may occur when registering a user associated with a specific device.

[0011] The technology disclosed in this specification can be realized in various forms, such as a server communicatively connected to a first terminal device, a second terminal device, and a specific device, a method using a server communicatively connected to a first terminal device, a second terminal device, and a specific device, a computer program for realizing these communication systems, servers, and methods, a recording medium on which the computer program is recorded, and the like. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing the configuration of a system 1000. [Figure 2] FIG. 10 is an explanatory diagram of a management database DBs. [Figure 3] FIG. 10 is a sequence diagram of an initial registration process. [Figure 4] FIG. 10 is a diagram showing an example of a screen displayed during initial registration processing. [Figure 5] FIG. 10 is a first sequence diagram of the next registration process. [Figure 6] FIG. 10 is a second sequence diagram of the next registration process. [Figure 7] FIG. 10 is a third sequence diagram of the next registration process. [Figure 8] FIG. 10 is a diagram illustrating some of the records in the device table DT and the token table TT. [Figure 9] FIG. 10 is a diagram showing an example of a screen displayed in the next registration process. [Figure 10] FIG. 10 is a diagram showing an example of an update registration screen W6. [Figure 11] FIG. 10 is a sequence diagram of the next registration process according to the second embodiment. [Figure 12] FIG. 10 is a diagram showing an example of a deregistration confirmation screen W7. DETAILED DESCRIPTION OF THE INVENTION

[0013] A. First Example A1. System 1000 Configuration 1 is a block diagram showing the configuration of a system 1000. The system 1000 includes a multifunction peripheral 100, terminal devices 200A and 200B, and a server 300 for providing a specific service (hereinafter simply referred to as a service) using the multifunction peripheral 100, as will be described later.

[0014] Multifunction device 100 is a device that consumes ink as a printing material to perform printing. Multifunction device 100 includes a CPU 110 as a controller for multifunction device 100, a volatile storage device 120 such as a DRAM, and a nonvolatile storage device 130 such as a hard disk or flash memory. Multifunction device 100 also includes a display unit 140 such as a liquid crystal display for displaying images, an operation unit 150 such as buttons or a touch panel for acquiring user operations, a reading mechanism 160, a printing mechanism 170, and a communication interface (IF) 180.

[0015] The communication IF 180 is an interface for connecting to the Internet IT, for example, a wired interface conforming to Ethernet (registered trademark) or a wireless interface conforming to the Wi-Fi standard.

[0016] The CPU 110 is a computing device (processor) that processes data. The volatile storage device 120 provides a buffer area for temporarily storing various intermediate data generated when the CPU 110 performs processing. The non-volatile storage device 130 stores a computer program PGp for controlling the multifunction peripheral 100 and a setting database DBp.

[0017] In this embodiment, the computer program PGp is ​​provided by being stored in advance in the nonvolatile storage device 130 when the multifunction peripheral 100 is manufactured. Alternatively, the computer program PGp may be provided in a form in which it is downloaded from a server connected via the Internet IT, or in a form in which it is recorded on a recording medium such as a DVD-ROM or USB memory.

[0018] The CPU 110 executes the computer program PGp to perform various processes for controlling the multifunction device 100. For example, the multifunction device 100 (CPU 110) controls the printing mechanism 170 to print an image. Furthermore, the multifunction device 100 executes the computer program PGp to communicate with the server 300 and perform processes related to services (for example, service registration processes described below).

[0019] The setting database DBp stores various setting information and the like related to the multifunction device 100. The setting database DBp stores administrator information MI. The multifunction device 100 has a function for registering an administrator. The administrator information MI is information for logging in to the multifunction device 100 as an administrator (for example, an administrator ID and password). The administrator can log in to the multifunction device 100 by inputting the administrator information MI into the multifunction device 100. Once logged in as an administrator, the administrator can perform operations on the multifunction device 100 that require administrator privileges (for example, operations to change important settings). The administrator can be set by the owner of the multifunction device 100. This administrator registration is managed independently by the multifunction device 100, regardless of the server 300. For this reason, the administrator information MI is information that is not stored in the server 300, but is information that is stored only in the multifunction device 100.

[0020] The reading mechanism 160, under the control of the CPU 110, optically reads an original using a one-dimensional image sensor, thereby generating scan data representing an image of the original.

[0021] The printing mechanism 170 executes printing under the control of the CPU 110. The printing mechanism 170 of this embodiment is an inkjet printing mechanism that prints an image on a recording medium using multiple types of ink, for example, four types of ink: cyan (C), magenta (M), yellow (Y), and black (K). Alternatively, the printing mechanism 170 may be an electrophotographic printing mechanism that prints an image on a recording medium using toner contained in a toner cartridge as a coloring material.

[0022] The multifunction peripheral 100 is used by being connected to, for example, a user's local network. In the state shown in FIG.

[0023] The terminal devices 200A and 200B are computers owned by users of the service. Each of the terminal devices 200A and 200B is a computer equipped with a CPU, memory, and display unit (e.g., a liquid crystal display), not shown, and is, for example, a personal computer. In a modified example, the terminal devices 200A and 200B may be a smartphone or a tablet computer. The terminal devices 200A and 200B are equipped with a predetermined communication interface (not shown), for example, a wireless communication interface conforming to the Wi-Fi standard or a mobile communication standard (e.g., the LTE standard). A browser program BP is installed in the terminal devices 200A and 200B. The terminal devices 200A and 200B function as a web browser by executing the browser program BP. The terminal devices 200A and 200B functioning as a web browser communicate with the server 300 and execute processing related to the service (described later) (e.g., service registration processing, described later).

[0024] The terminal device 200A is a terminal device used by a user A, and is connected to a local area network LNa (for example, a local area network configured in the home of the user A).

[0025] The terminal device 200B is a terminal device used by a user B, and is connected to a local area network LNb (for example, a local area network configured in the home of the user B).

[0026] The server 300 is, for example, a computer operated by a service provider, such as a cloud server. The server 300 includes a CPU 310 as a controller of the server 300, a volatile storage device 320 such as a DRAM, a non-volatile storage device 330 such as a hard disk or flash memory, and a wired or wireless communication IF 380 for connecting to the Internet IT. The server 300 is connected to the Internet IT. This allows the server 300 to communicate with the multifunction peripheral 100 and the terminal devices 200A and 200B via the Internet IT.

[0027] The CPU 310 is a computing device (processor) that processes data. The volatile storage device 320 provides a buffer area for temporarily storing various intermediate data generated when the CPU 310 performs processing. The non-volatile storage device 330 stores computer programs PGs and a management database DBs.

[0028] The computer programs PGs are provided, for example, in the form of being uploaded by a business operator that operates the server 300. The server 300 (CPU 310) provides services by executing the computer programs PGs. The server 300 also cooperates with the multifunction peripheral 100 and the terminal devices 200A and 200B to execute processes related to the services (for example, the initial registration process and the next registration process) described below.

[0029] The management database DBs stores various data (described later) required for processing related to the service.

[0030] 1 shows only the multifunction device 100, the server 300 communicates with a large number of printers (multifunction devices and standalone printers) to provide services using the multifunction device 100. Below, we will explain the processes related to the multifunction device 100, but these processes can also be executed between the multifunction device 100 and other printers that are the subject of the service.

[0031] The server 300 provides a variety of services, including, for example, various services that use the multifunction peripheral 100, such as a print management service, a remote printing service, a storage service, and a content service.

[0032] The print management service is a service that manages, for example, the remaining amount of ink in the multifunction peripheral 100 and printing and malfunction history information, arranges for ink according to the remaining amount of ink, and performs maintenance on the multifunction peripheral 100 according to the malfunction history of the multifunction peripheral 100, etc. The remote printing service is a service that causes the multifunction peripheral 100 to print by generating a print job using, for example, an image file that a user has stored in the server 300 or an image file transmitted from the user's mobile terminal (not shown). The storage service is a service that stores image files such as scan data and print data generated using the multifunction peripheral 100 in the server 300. The content service is a service that downloads content data representing content images to the multifunction peripheral 100 and allows the multifunction peripheral 100 to use them. The content images may include, for example, character fonts, characters from animations or cartoons, and templates including pictures and designs for greeting cards (e.g., New Year's cards or Christmas cards) and calendars.

[0033] In the following description, it is assumed that the server 300 provides four types of services 1 to 4. In this embodiment, in order to use these services, the user must register for each service to be used. When registering for each service, the user and a device (for example, the multifunction device 100) are registered in association with each other. In this embodiment, a device cannot be registered twice for the same type of service (for example, service 1). For example, assume that user A has registered for services 1 and 2 in association with the multifunction device 100. In this case, user B cannot register for service 1 or service 2 in association with the same multifunction device 100. User B can register for service 3 or service 4 in association with the same multifunction device 100.

[0034] A2. Management databases The management database DBs stored in the nonvolatile storage device 330 of the server 300 will now be described. Fig. 2 is an explanatory diagram of the management database DBs. The management database DBs in Fig. 2 includes a user table UT, a corresponding service table ST, a device table DT, and a token table TT.

[0035] The user table UT is a table in which information about users of a service is stored. In this embodiment, the user table UT stores user IDs that identify multiple users of the service. The user table UT also stores various information (user information) about the user identified by each user ID, in association with the user ID. The user information may include personal information necessary for using the service, such as the user's name, address, email address, and payment information (e.g., credit card number) (not shown). In the example of FIG. 2, user information "US_A" is recorded in association with user A's user ID "UID_A."

[0036] The compatible service table ST is a table in which, for each device model, services that can be used with a device of that model (hereinafter also referred to as compatible services) are recorded. For example, in the example of Fig. 2, service 1 and service 2 are recorded in association with the model name "MA_1". This means that the compatible services for a device having the model name "MA_1" are service 1 and service 2 out of services 1 to 4.

[0037] The device table DT is a table that stores information about devices (e.g., multifunction peripherals 100) managed by the server 300. In this embodiment, the device table DT stores serial numbers as identification information for multiple devices managed by the server 300. The device table DT also stores, in association with each serial number, a model name and user registration information. The user registration information indicates whether a user has registered for a service that can be used using the device, and, if the user has registered, further indicates the registered user. Specifically, the user registration information stores, for each service that can be used using the device, the user ID of the registered user in association with the service if the user has registered, and, if the user has not registered, no user ID is associated with the service.

[0038] 2 records, in association with the serial number "DID_1" of the multifunction device 100, the model name "MA_1" of the multifunction device 100 and the user registration information for each of services 1 and 2 that can be used using the multifunction device 100. For service 1, the user ID "UID_A" of user A is recorded, indicating that user A is registered as a user who uses service 1 using the multifunction device 100. For service 2, no user ID is recorded, indicating that no user is registered to use service 2 using the multifunction device 100.

[0039] The token table TT is a table that stores token information related to takeover tokens for each device. For example, in the token table TT of Fig. 2, token information is stored in association with the serial number and model name of the device. The token information includes the takeover token, a used flag, the issue date and time, and the expiration date.

[0040] The takeover token is authentication information used in the registration process described below, and is authentication information associated with a device (for example, the multifunction peripheral 100). The takeover token is, for example, a string of characters that is randomly generated and consists of a predetermined number of characters.

[0041] The used flag is a flag that indicates whether the associated takeover token has been used. If the used flag is OFF, the takeover token is unused and is valid as long as it is before the expiration date. If the used flag is ON, the takeover token has been used and is invalid regardless of the expiration date.

[0042] The issue date and time is the date and time when the takeover token was issued, in other words, the date and time when the takeover token was generated and recorded in the token table TT. The expiration date and time is set to a date and time a predetermined period (for example, several minutes to several days) after the expiration date is set.

[0043] The management database DBs stores various information for providing the services 1 to 4. For example, for the printing service, the management database DBs stores a table for managing the remaining amount of ink in the devices (printers and multifunction peripherals) used for the printing service, but illustrations and explanations of this table are omitted because it has little relevance to the present application.

[0044] A3. User registration process for the service Next, the user registration process for the above-mentioned services 1 to 4 will be described. Each of services 1 to 4 is associated with a device (for example, the multifunction peripheral 100) and user registration is performed. The user registration process for one device includes an initial registration process and a subsequent registration process. The initial registration process is a process that is executed when a user is to register for a specific service (for example, service 1) when a user has not been registered for that specific service. The subsequent registration process is a process that is executed when a user other than the user already registered for that specific service is to register for that specific service when a user has already been registered for that specific service (for example, service 1).

[0045] A3-1. Initial registration process Fig. 3 is a sequence diagram of the initial registration process. The example of Fig. 3 shows the initial registration process that is executed when user A performs user registration for service 1 in association with multifunction peripheral 100. This initial registration process is executed when user A's terminal device 200A and multifunction peripheral 100 are connected to the local area network LNa used by user A, and when the terminal device 200A and multifunction peripheral 100 are powered on.

[0046] In S4, terminal device 200A transmits a registration screen request to server 300, requesting data for a registration screen. Communication between terminal devices 200A and 200B and server 300 is performed in accordance with a known protocol, such as HTTP (Hypertext Transfer Protocol). For example, user A starts a browser program BP on terminal device 200A and performs a predetermined operation on terminal device 200A, which functions as a web browser. The predetermined operation includes, for example, entering a uniform resource locator (URL) of server 300 to access a web page provided by server 300, and entering an instruction for user registration for service 1 via the web page. Upon receiving the operation, terminal device 200A transmits a registration screen request to server 300.

[0047] When the server 300 (CPU 310) receives the registration screen request, it transmits data of the registration screen W1 for service 1 to the terminal device 200A in S6. When the terminal device 200A receives the data of the registration screen W1, it displays the registration screen W1 on its own display unit using the data in S8.

[0048] 4A and 4B are diagrams showing examples of screens displayed during the initial registration process. The registration screen W1 in Fig. 4A includes a message MS1 prompting the user to enter the serial number of the device for user registration for service 1, an input field TBa for entering the serial number, and an OK button BTa.

[0049] In S10, the terminal device 200A acquires the serial number from the user A via the registration screen W1. Specifically, when the user A enters the serial number of the multifunction peripheral 100 in the input field TBa and then presses the OK button BTa, the terminal device 200A acquires the serial number entered in the input field TBa.

[0050] In S12, the terminal device 200A transmits a registration request to the server 300. The registration request includes the serial number obtained in S10.

[0051] When the server 300 receives the registration request, in S14 it determines the registration status of service 1, which is the target of user registration. That is, the server 300 determines whether or not a user has been registered for service 1 in association with the multifunction peripheral 100. Specifically, the server 300 searches the device table DT for the serial number included in the registration request. If the serial number is recorded in the device table DT, the server 300 determines whether or not a user ID for service 1 is associated with the serial number. If a user ID for service 1 is associated with the serial number, the server 300 determines that a user has been registered for service 1 in association with the multifunction peripheral 100. If the serial number is not recorded in the device table DT, the server 300 determines that a user has not been registered for service 1 in association with the multifunction peripheral 100. Similarly, if a user ID for service 1 is not associated with the serial number, the server 300 determines that a user has not been registered for service 1 in association with the multifunction peripheral 100 (unregistered).

[0052] Here, in the initial registration process, a record including the serial number of the multifunction device 100 is not recorded in the device table DT, so in S14 the server 300 determines that a user associated with the multifunction device 100 has not been registered for service 1. In this case, in S16 the server 300 transmits data for a new registration screen W2 to the terminal device 200A. Upon receiving the data for the new registration screen W2, the terminal device 200A displays the new registration screen W2 on its own display unit using the data in S18.

[0053] The new registration screen W2 in Figure 4(B) notifies the user that no user registration has been made for service 1 and includes a message MS2 prompting new registration, input elements for entering various user information required for registration (input fields TB1 to TB5 and radio buttons RBa, RBb), and a registration button BTb.

[0054] In S20, the terminal device 200A acquires user information from the user A via the new registration screen W2. Specifically, when the user A inputs the user information into the input elements (input fields TB1 to TB5 and radio buttons RBa and RBb) of the new registration screen W2 and then presses the register button BTb, the terminal device 200A acquires the user information input into each input element. In the example of FIG. 4(B), the acquired user information includes an email address, a name, a year of birth, a gender, and an address. In S22, the terminal device 200A transmits the user information acquired from the user A to the server 300.

[0055] Upon receiving the user information, the server 300 registers the acquired user information (user A's information) in S23. Specifically, the server 300 generates a user ID for user A. The server 300 records the received user information in the user table UT in association with the generated user ID. As a result, as shown by the dashed line in FIG. 2, a record R1 including user A's ID "UID_A" and user A's information "US_A" is recorded in the user table UT.

[0056] In S24, the server 300 performs new user registration for the service. That is, user A is newly registered as a user associated with the multifunction peripheral 100 for service 1. Specifically, the server 300 identifies the model name of the multifunction peripheral 100 by searching for the serial number received in S12 in a table (not shown) that associates serial numbers with model information such as model names. The server 300 identifies services that can be used using a device having the identified model name by referring to the corresponding service table ST (FIG. 2). The server 300 records user registration information registering user A as a user of service 1 in the device table DT, in association with the serial number and model name of the multifunction peripheral 100. As a result, as shown by the dashed line in FIG. 2, a record R2 including user registration information that associates the serial number "DID_1" of the multifunction peripheral 100, the model name "MA_1" of the multifunction peripheral 100, and service 1 with user A's ID "UID_A" is recorded in the device table DT. In record R2, no user ID is registered for service 2, and it can be seen that no user is registered to associate service 2 with the multifunction peripheral 100 (FIG. 2).

[0057] In S25, the server 300 executes a takeover token issuing process. Specifically, the server 300 generates a takeover token. The server 300 stores the takeover token in the token table TT in association with the serial number and model name of the multifunction device 100. As a result, as shown by the dashed line in FIG. 2, a record R3 including the serial number "DID_1" of the multifunction device 100, the model name "MA_1" of the multifunction device 100, and the takeover token "TK_1" is recorded in the token table TT. At this point, as shown in FIG. 2, in record R3, the used flag is set to "OFF," the issue date and time is set to the current date and time, and no expiration date is set.

[0058] In S26, the server 300 transmits the generated takeover token to the multifunction peripheral 100. In this embodiment, the multifunction peripheral 100 establishes a constant connection with the server 300 while the multifunction peripheral 100 is powered on. The constant connection is established according to, for example, XMPP (eXtensible Messaging and Presence Protocol). Communication between the multifunction peripheral 100 and the server 300 is performed using the constant connection.

[0059] When the multifunction device 100 receives the takeover token, it stores the takeover token in the setting database DBp in S27.

[0060] In S29, the server 300 transmits data of a registration completion screen to the terminal device 200A. Upon receiving the data of the registration completion screen, the terminal device 200A displays the registration completion screen on its own display unit using the data in S30. Although not shown in the figure, the registration completion screen includes a message indicating that the user registration associated with the multifunction peripheral 100 for service 1 has been completed.

[0061] Once the initial registration process is complete, user A can use service 1 using multifunction device 100. For example, if service 1 is the print management service described above, multifunction device 100 receives periodic transmission setting information from server 300 and stores the setting information in setting database DBp. Thereafter, multifunction device 100 periodically uploads information such as remaining ink level, printing history, and malfunction history to server 300 in accordance with the periodic transmission setting information. Server 300 performs processes such as arranging for ink and charging fees in accordance with the information uploaded from multifunction device 100.

[0062] A3-2. Next registration process 5 to 7 are sequence diagrams of the next registration process. The next registration process is a process that is executed when a user other than the user already registered for a specific service (for example, service 1) performs user registration for the specific service. In the example of FIG. 5, the process is executed when user B performs user registration for service 1 in a state where user A has been registered for service 1 in association with multifunction peripheral 100 through the initial registration process of FIG. 3. This example assumes that user A has already registered and then transferred the multifunction peripheral 100 to user B. Therefore, at the start of the next registration process of FIG. 5, the multifunction peripheral 100 is connected to the local area network LNb used by user B, as indicated by the dashed line in FIG. 1. The next registration process is executed in a state where user B's terminal device 200B and multifunction peripheral 100 are connected to the local area network LNb and the terminal device 200B and multifunction peripheral 100 are powered on.

[0063] In addition to the above-mentioned examples, a case where the next registration process is executed may also be assumed where user A and user B are family members living together. For example, it is assumed that after user A has registered, user B registers himself / herself without knowing that user A has registered himself / herself. In this case, user A and user B use the same local area network LNa, and therefore, unlike the example of FIG. 1, the next registration process is executed with the multifunction peripheral 100 and terminal device 200B connected to the local area network LNa.

[0064] In S54, terminal device 200B transmits a registration screen request requesting data for a registration screen to server 300, similar to S4 in Fig. 3. Upon receiving the registration screen request, server 300 transmits data for registration screen W1 for service 1 to terminal device 200B in S56, similar to S6 in Fig. 3. Upon receiving the data for registration screen W1, terminal device 200B displays registration screen W1 (Fig. 4(A)) on its own display unit using the data, similar to S8 in Fig. 4, in S58.

[0065] In S60, terminal device 200B acquires the serial number from user B via registration screen W1, similar to S10 in Fig. 3. In S62, terminal device 200B transmits a registration request to server 300, similar to S12 in Fig. 3. The registration request includes the serial number acquired in S60.

[0066] When the server 300 receives the registration request, in S64, it determines the registration status of the service 1 for which the user is to be registered, similar to S14 in FIG.

[0067] FIG. 8 is a diagram illustrating some of the records in the device table DT and the token table TT. At the start of the next registration process, the record shown in FIG. 8(A) is recorded in the device table DT. This is the record recorded in the initial registration process of FIG. 3. The server 300 searches the device table DT for the serial number included in the registration request, and obtains the record shown in FIG. 8(A). As shown in the dashed-line box F1, this record is associated with user A's ID "UID_A" as the user ID for service 1. For this reason, in S64, unlike S14 in FIG. 3, the server 300 determines that the user associated with the multifunction peripheral 100 for service 1 has already been registered.

[0068] In this case, in S66, the server 300 transmits data of a registration rejection notification screen W3 indicating that registration of user B is rejected to the terminal device 200B. Upon receiving the data of the registration rejection notification screen W3, in S68, the terminal device 200B uses the data to display the registration rejection notification screen W3 on its own display unit.

[0069] 9A and 9B are diagrams showing examples of screens displayed during the next registration process. The registration rejection notification screen W3 in FIG. 9A notifies the user that user B's registration has been rejected because a user has already been registered for service 1, and includes a message MS3 asking whether or not to display information about the registered user, a YES button BTy, and a NO button BTn. By viewing the registration rejection notification screen W3, user B recognizes that another user has already registered a user associated with multifunction peripheral 100 for service 1, and therefore cannot register. User B may press the NO button BTn if, for example, he or she decides to give up on user registration for service 1, but it is generally believed that user B will press the YES button BTy. When the NO button BTn is pressed, terminal device 200B terminates the display of the registration rejection notification screen W3 and terminates the next registration process.

[0070] By pressing the YES button BTy, user B can input a registration information request requesting information about registered users. In S72 of Fig. 5, the terminal device 200B acquires the registration information request input by user B. Upon acquiring the registration information request, in S74, the terminal device 200B transmits a token expiration setting request to the server 300.

[0071]

[0073] When the server 300 receives the token expiration setting request, it sets the expiration date of the takeover token in S76. Figure 8(C) shows a record in the token table TT at the start of the next registration process, which includes the serial number "DID_1" of the multifunction peripheral 100. As shown in the dashed box F3 in Figure 8(C), at this point in time, the record in the token table TT which includes the serial number "DID_1" does not include an expiration date. The server 300 sets the expiration date of the takeover token by recording the expiration date in the record. As described above, the expiration date is set to a date and time a predetermined period (for example, several minutes to several days) after the current date and time (when the expiration date is set). Figure 8(D) shows a record in the token table TT after the expiration date has been set. As shown in the dashed box F5, the record in the token table TT which includes the serial number "DID_1" includes the expiration date "LT_1" of the takeover token. As can be seen from this explanation, in this embodiment, the takeover token is set with an expiration date calculated from S76 after user B's registration request (S62).

[0072] 6, the server 300 transmits a login screen display instruction to the multifunction device 100. Upon receiving the login screen display instruction, the multifunction device 100 displays a login screen W5 on the display unit 140 in S80. The login screen W5 is a screen for an administrator of the multifunction device 100 to log in to the multifunction device 100. The data for the login screen W5 is stored in advance in the nonvolatile storage device 130 of the multifunction device 100. As described above, the multifunction device 100 has a function for registering an administrator. The administrator can log in to the multifunction device 100 by inputting administrator information (for example, an administrator ID and password) into the multifunction device 100. Here, it is assumed that user B has already been registered as the administrator of the multifunction device 100 and knows the administrator information (administrator ID and password).

[0073] The login screen W5 in Figure 9(B) includes a message MS5 prompting the user to log in as an administrator, input fields IB1 and IB2 for entering administrator information (administrator ID and password in the example of Figure 9(B)), and a login button BTr.

[0074] In S81, the multifunction device 100 acquires administrator information from user B via the login screen W5. Specifically, when user B enters administrator information for logging in as an administrator in input fields IB1 and IB2 and presses the login button BTr, the multifunction device 100 acquires the administrator ID and password entered in each input field as the administrator information.

[0075] In S82, the multifunction peripheral 100 executes login processing using the acquired administrator information. Specifically, the multifunction peripheral 100 determines whether the acquired administrator information matches the administrator information MI (FIG. 1) already stored in the setting database DBp. If the acquired administrator information matches the administrator information MI already stored in the setting database DBp, the multifunction peripheral 100 determines that the authentication for login has been successful and transitions the multifunction peripheral 100 to a logged-in state (a state in which operations requiring administrator authority are accepted). If the acquired administrator information does not match the stored administrator information MI, the multifunction peripheral 100 determines that the authentication has failed and does not transition the multifunction peripheral 100 to a logged-in state. If the authentication has failed, the multifunction peripheral 100 displays a message on the display unit 140 that the authentication has failed, and the next registration processing is interrupted (not shown). Here, it is assumed that the authentication has been successful and the multifunction peripheral 100 transitions to a logged-in state.

[0076] When the multifunction peripheral 100 transitions to the logged-in state, in S86 it transmits the takeover token stored in the setting database DBp to the server 300. As can be seen from the above explanation, the multifunction peripheral 100 transmits the takeover token to the server 300 when it is in the logged-in state, but is controlled not to transmit the takeover token when it is not in the logged-in state. The takeover token is transmitted in association with login information indicating whether the multifunction peripheral 100 is in the logged-in state.

[0077] When the server 300 receives the takeover token and the login information, in S87, it checks the login status based on the login information. If the login information indicates that the multifunction device 100 is not in a logged-in state, the server 300, for example, sends an error notification to the multifunction device 100, and the next registration process is interrupted (not shown). Here, it is assumed that the login information indicates that the multifunction device 100 is in a logged-in state. If the login information indicates that the multifunction device 100 is in a logged-in state, the server 300 proceeds to S88.

[0078] In S88, the server 300 checks the validity of the takeover token. Specifically, the server 300 searches the token table TT for a record that includes the serial number "DID_1" of the multifunction device 100. This searches for the record shown in FIG. 8D. The server 300 determines whether the takeover token "TK_1" included in the record in FIG. 8D matches the takeover token received in S86. If the takeover token "TK_1" included in the record in FIG. 8D matches the takeover token received in S86, the server 300 determines whether the used flag included in the record in FIG. 8D is "OFF." If the used flag included in the record in FIG. 8D is "OFF," the server 300 further determines whether the current date and time is within the expiration date "LT_1" included in the record in FIG. 8D. If the current date and time is within the expiration date "LT_1" included in the record of FIG. 8(D), the server 300 determines that the takeover token received from the multifunction device 100 is valid.

[0079] If the takeover token "TK_1" contained in the record in Figure 8(D) does not match the received takeover token, if the used flag contained in the record in Figure 8(D) is "ON", and if the current date and time has passed the expiration date "LT_1" contained in the record in Figure 8(D), the server 300 determines that the takeover token received from the multifunction device 100 is invalid.

[0080] If it is determined that the takeover token received from the multifunction device 100 is invalid, steps S90 and S92 in Fig. 6 are executed. In S90, the server 300 transmits data for an invalidation notification screen to the terminal device 200B. Upon receiving the data for the invalidation notification screen, the terminal device 200B uses the data to display the invalidation notification screen on its own display unit in S92. Although not shown in the figure, the invalidation notification screen includes a message indicating that user registration and notification of registered user information are not possible because the takeover token is invalid. In this case, the initial registration process is interrupted.

[0081] If it is determined that the takeover token received from the multifunction device 100 is valid, steps S93 to S106 in FIG. 7 are executed. In S93, the server 300 changes the takeover token to a used state. At this point, as shown in the dashed box F4 in FIG. 8(D), the used flag of the record in the token table TT that includes the serial number "DID_1" of the multifunction device 100 is "OFF." The server 300 changes this used flag from "OFF" to "ON," as shown in the dashed box F6 in FIG. 8(E). This makes the takeover token invalid even if it has not yet expired.

[0082] In S94, the server 300 acquires registered user information. Specifically, the server 300 references the user registration information of the record (FIG. 8(A)) containing the serial number "DID_1" in the device table DT, and acquires the ID "UID_A" of the registered user of service 1. The server 300 searches the user table UT (FIG. 2) for a record containing the user ID "UID_A," and acquires necessary information from the user information "US_A" contained in that record. In this embodiment, the name of user A contained in the user information "US_A" is acquired.

[0083] In S95, the server 300 transmits data for the update registration screen W6 to the terminal device 200B. As will be described later, the update registration screen W6 includes registered user information, in this embodiment, the name of user A. Upon receiving the data for the update registration screen W6, the terminal device 200B displays the update registration screen W6 on its own display unit using the data in S96.

[0084] 10 is a diagram showing an example of the update registration screen W6. The update registration screen W6 includes a message MS6 notifying the above-mentioned registered user information (in the example of FIG. 10, the name of user A). This allows user B to know the information of registered user A. This allows user B to take action such as contacting registered user A and obtaining consent to change the registered user to himself / herself.

[0085] The update registration screen W6 further includes a message MS7 notifying the user that they can change and register the user, input elements (input fields TB1 to TB5 and radio buttons RBa and RBb) for entering user information similar to that of the new registration screen W2 in Figure 4(B), a register button BTb, and a cancel button BTc.

[0086] User B presses the Cancel button BTc if, for example, he / she wishes to maintain the current user registration as is. When the Cancel button BTc is pressed, terminal device 200B terminates display of the update registration screen W6, and the next registration process is interrupted (not shown). Here, it is assumed that User B enters user information into the input elements (input fields TB1 to TB5 and radio buttons RBa, RBb) of the update registration screen W6, and then presses the Register button BTb.

[0087] When the registration button BTb is pressed, the terminal device 200B acquires the user information input into each input element in S98. In S100, the terminal device 200B transmits the acquired user information to the server 300.

[0088] Upon receiving the user information, the server 300 registers the acquired user information (information about user B) in S101. Specifically, the server 300 generates a user ID for user B. The server 300 records the received user information in the user table UT in association with the generated user ID.

[0089] In S102, the server 300 identifies the record to be updated. That is, the server 300 identifies the record (FIG. 8A) in the device table DT that includes the serial number associated with the takeover token (in this embodiment, the serial number "DID_1" of the multifunction device 100).

[0090] In S103, the server 300 updates the registration of service 1. That is, the user registered in association with the multifunction peripheral 100 for service 1 is changed from user A to user B. Specifically, the server 300 updates the user registration information included in the identified record of FIG. 8A. In the record of FIG. 8A, as shown in the dashed-line box F1, the ID of user A, "UID_A," is recorded as the ID of the user for service 1. As shown in the dashed-line box F2 in FIG. 8B, the server 300 changes the ID of the user for service 1 in the record from user A's ID, "UID_A," to user B's ID, "UID_B." As a result, the serial number "DID_1" of the multifunction peripheral 100 and user B's ID, "UID_B," are associated with each other for service 1, and user B is registered as a user of service 1. User A's registration as a user of service 1 is canceled.

[0091] In S104, the server 300 transmits data for an update completion notification screen to the terminal device 200B. When the terminal device 200B receives the data for the update completion notification screen, in S106, the terminal device 200B uses the data to display the update completion notification screen on its own display unit. Although not shown in the figure, the update completion notification screen includes a message indicating that the user registered in association with the multifunction device 100 for service 1 has been updated. When the above next registration process is completed, user B can use service 1 using the multifunction device 100.

[0092] According to the present embodiment described above, in the initial registration process of FIG. 3, the server 300 receives from the terminal device 200A the user information of user A, the serial number of the multifunction peripheral 100, and a registration request for user A (S12 and S22 of FIG. 3). When the server 300 receives the registration request for user A, the server 300 registers user A by storing registration information (the user table UT and the device table DT of FIG. 2) that associates the user information and serial number of user A in the management database DBs (S24 of FIG. 3). When registering user A, the server 300 stores a takeover token in the management database DBs in association with the serial number of the multifunction peripheral 100 (S25 of FIGS. 2 and 3). When registering user A, the server 300 transmits the takeover token to the multifunction peripheral 100 (S26 of FIG. 3).

[0093] In the next registration process (FIGS. 5-7) after the initial registration process, the server 300 receives the serial number of the multifunction peripheral 100 and a registration request for user B from the terminal device 200B (S62 in FIG. 5). When the server 300 receives the registration request for user B, it transmits a registration rejection notification screen W3 to the terminal device 200B, indicating that registration of user B is rejected (S66 in FIG. 5). After transmitting the registration rejection notification screen W3, the server 300 receives a takeover token from the logged-in multifunction peripheral 100 (S86 in FIG. 6). When the server 300 receives the takeover token, it acquires information about user A (e.g., user A's name) associated with the serial number associated with the takeover token in the management database DBs (device table DT and token table TT) (S94 in FIG. 7). When the takeover token is received, the server 300 notifies the terminal device 200B of the acquired information about user A (e.g., user A's name) (S95 in FIG. 7). As a result, even if user B cannot be registered because user A has already been registered in association with the multifunction peripheral 100 and therefore overlaps with user A, the information about the registered user A is notified to user B. As a result, user B can take some action based on the information about user A. For example, as described above, user B can contact the registered user A and obtain consent to change the registered user to himself / herself. It is also possible that a family member living with user B has already registered. In this case, the family member's name is displayed on the update registration screen W6, so user B can recognize that the registered user is a family member. In this case, user B can maintain the family registration as is and use service 1 together with the family member.

[0094] Furthermore, since notification of user A's information is performed on the condition that a takeover token is received from the multifunction device 100 in which the administrator is logged in, it is possible to prevent the information of user A from being improperly leaked. If there is a registration request from user B and it is confirmed that user B can log in to the multifunction device 100 as an administrator, it is confirmed that user B is the legitimate administrator of the multifunction device 100. For this reason, it is considered that there is no problem in notifying user B of the information of user A that is registered in association with the multifunction device 100.

[0095] Furthermore, if user B, who is a legitimate administrator, is unable to register for service 1 because another user has already registered and is unable to obtain information about registered user A, user B will not know what to do. In such a case, user B may give up on using service 1. According to this embodiment, it is possible to prevent user B from giving up on using service 1, thereby promoting the use of service 1. In such a case, user B may inquire of the provider providing service 1 about how to use service 1 or information about registered user A. According to this embodiment, it is possible to prevent such inquiries from occurring, thereby reducing the burden on the provider providing service 1. As described above, according to this embodiment, it is possible to reduce various inconveniences that may occur when registering a user associated with the multifunction peripheral 100.

[0096] Furthermore, according to this embodiment, the takeover token is set with a validity period (S76 in FIG. 5) that starts after the registration request for user B is received (S62 in FIG. 5). If the takeover token is received from the multifunction device 100 within the validity period (S88 in FIG. 6), the server 300 notifies the terminal device 200B of the information about user A (S95 in FIG. 7). If the takeover token is received from the multifunction device 100 within the validity period that starts after the registration request for user B is received, there is an extremely high possibility that user B is the legitimate administrator of the multifunction device 100. This further prevents the information about user A from being leaked improperly.

[0097] Furthermore, according to this embodiment, the server 300 receives, together with the takeover token, login information indicating whether or not the administrator is logged in to the multifunction device 100 (S86 in FIG. 6). When the server 300 receives, together with the takeover token, login information indicating that the administrator is logged in to the multifunction device 100 (S87 in FIG. 6), the server 300 notifies the terminal device 200B of the information about user A (S95 in FIG. 7). As a result, the information about user A is notified to the terminal device 200B only when it is confirmed that the administrator is logged in to the multifunction device 100, which further prevents the information about user A from being leaked improperly.

[0098] Furthermore, according to this embodiment, in the next registration process (FIGS. 5-7) after the initial registration process, the server 300 receives from the terminal device 200B the user information of user B, the serial number of the multifunction peripheral 100, and a registration request for user B (S62 in FIG. 5, S100 in FIG. 7). When the server 300 receives the registration request for user B, it transmits a registration rejection notification screen W3 to the terminal device 200B, indicating that registration of user B is rejected (S66 in FIG. 5). After transmitting the registration rejection notification screen W3, the server 300 receives a takeover token from the logged-in multifunction peripheral 100 (S86 in FIG. 6). When the server 300 receives the takeover token, it acquires information about user A (e.g., the name of user A) associated with the serial number associated with the takeover token in the management database DBs (device table DT and token table TT) (S94 in FIG. 7). When the server 300 receives the takeover token, it identifies registration information (the record in FIG. 8A in the device table DT) including the serial number of the multifunction peripheral 100 associated with the takeover token in the management database DBs (S102 in FIG. 7). When the server 300 receives specific authentication information, it updates the registration information (the record in FIG. 8A) in the management database DBs to registration information (the record in FIG. 8B) associating user B with the multifunction peripheral 100, thereby registering user B (S103 in FIG. 7). In this way, when the server 300 receives a registration request for user B from the terminal device 200B after registering user A, it registers user B on the condition that it receives a takeover token from the multifunction peripheral 100 to which the administrator is logged in. As a result, it is possible to prevent the inconvenience of user B not being able to be registered when user A is already registered for the multifunction peripheral 100. Therefore, it is possible to reduce the inconvenience that may occur in registering a user associated with the multifunction peripheral 100.

[0099] For example, in this embodiment, only one user can be registered in association with the multifunction peripheral 100 for one service, and duplicate registrations are not permitted. In this case, if user B inherits the multifunction peripheral 100 from user A, even though user B is the legitimate owner of the multifunction peripheral 100, user B cannot be registered unless user A's registration can be canceled. If user A's registration is not permitted to be canceled, user B will not be able to use service 1, which would be a major disadvantage for user B. If there is a registration request from user B and it is confirmed that user B can log in to the multifunction peripheral 100 as an administrator, it is confirmed that user B is the legitimate administrator of the multifunction peripheral 100. For this reason, it is considered that there is no problem with user B canceling the registration of user A associated with the multifunction peripheral 100 if user B wishes.

[0100] Furthermore, according to this embodiment, the takeover token is set with a validity period (S76 in FIG. 5) that starts after the registration request for user B is received (S62 in FIG. 5). If the takeover token is received from the multifunction device 100 within the validity period (S88 in FIG. 6), the server 300 executes the registration of user B (S103 in FIG. 7). If the takeover token is received from the multifunction device 100 within the validity period that starts after the registration request for user B is received, it is highly likely that user B is the legitimate administrator of the multifunction device 100. For this reason, it is possible to approve the registration of user B only if user B is the legitimate administrator. Therefore, for example, it is possible to prevent user A's registration from being fraudulently updated with the registration of another user.

[0101] Furthermore, according to this embodiment, the server 300 receives, together with the takeover token, login information indicating whether or not the administrator is logged in to the multifunction device 100 (S86 in FIG. 6). When the server 300 receives, together with the takeover token, login information indicating that the administrator is logged in to the multifunction device 100 (S87 in FIG. 6), the server 300 executes registration of user B (S103 in FIG. 7). As a result, registration of user B is performed only when it is confirmed that the administrator is logged in to the multifunction device 100, which further prevents the registration of user A from being fraudulently updated with the registration of another user.

[0102] As can be seen from the above explanation, user A in this embodiment is an example of a first user, and user B is an example of a second user. The multifunction device 100 in this embodiment is an example of a specific device, and the serial number is an example of device identification information. The management database DBs in this embodiment is an example of a storage unit, and the takeover token is an example of specific authentication information.

[0103] B. Second Example Fig. 11 is a sequence diagram of the next registration process in the second embodiment. In the second embodiment, the process executed when the takeover token is determined to be valid differs from that in the first embodiment. In the first embodiment, if the takeover token is determined to be valid in S88 of Fig. 6, the process in Fig. 7 is executed, but in the second embodiment, if the takeover token is determined to be valid, the process in Fig. 11 is executed. The other processes in the second embodiment are the same as those in the first embodiment.

[0104] In S93B of Fig. 11, the server 300 changes the takeover token to a used state, similar to S93 of Fig. 7. In S94B, the server 300 acquires registered user information, similar to S94 of Fig. 7.

[0105] In S95B, the server 300 transmits the acquired registered user information to the multifunction device 100. In this way, the registered user information may be transmitted to the terminal device 200B as in the first embodiment, or may be transmitted to the multifunction device 100. In the second embodiment, the registered user information is, for example, text data indicating the name of the registered user A.

[0106] Upon receiving the registered user information, the multifunction device 100 prints the registered user information in S96B. For example, the CPU 110 of the multifunction device 100 generates print image data showing an image including the registered user information, and causes the printing mechanism 170 to print the image using the print image data. User B can recognize the name of registered User A by looking at the registered user information printed on paper. In a modified example, the registered user information may be displayed on the display unit 140 of the multifunction device 100.

[0107] In S98B, the server 300 transmits data for the deregistration confirmation screen W7 to the multifunction device 100. Upon receiving the data for the deregistration confirmation screen W7, the multifunction device 100 displays the deregistration confirmation screen W7 on the display unit 140 using the data in S99B.

[0108] FIG. 12 is a diagram showing an example of a deregistration confirmation screen W7. The deregistration confirmation screen W7 includes a message MS8 notifying the user that registered user information (e.g., the name of user A) has been printed. The deregistration confirmation screen W7 also includes a message MS9 asking whether to deregister the registered user, a message MS10 notifying the user that a new user can be registered if the registered user's registration is deregistered, a cancel button BTd, and a maintain button BTk. The cancel button BTd is a button for inputting an instruction to deregister the registered user. The maintain button BTk is a button for inputting an instruction to maintain the registration of the registered user.

[0109] If user B wishes to maintain the current user registration as is, he / she presses the maintain button BTk. When the maintain button BTk is pressed, the terminal device 200B terminates the display of the deregistration confirmation screen W7, and the next registration process is interrupted (not shown). If user B wishes to maintain the current user registration as is, he / she presses the cancel button BTd.

[0110] When the cancel button BTd is pressed, the terminal device 200B acquires a deregistration instruction in S100B. Upon acquiring the deregistration instruction, the terminal device 200B transmits a deregistration request to the server 300 in S101B, requesting cancellation of the current user registration.

[0111] When the server 300 receives the deregistration request, in S102B, the server 300 identifies the record to be deregistered. That is, the server 300 identifies the record (FIG. 8A) in the device table DT that includes the serial number associated with the takeover token (in this embodiment, the serial number "DID_1" of the multifunction peripheral 100).

[0112] In S103B, the server 300 cancels the current user registration for service 1. Specifically, the registration of user A, who is registered in association with the multifunction peripheral 100 for service 1, is canceled. For example, the server 300 deletes the entire identified record of FIG. 8A. In a modified example, the server 300 may cancel the registration of user A by leaving the record of FIG. 8A and associating an invalid flag indicating that the record is invalid.

[0113] In S104B, the server 300 transmits data of a cancellation completion notification screen to the terminal device 200B. Upon receiving the data of the cancellation completion notification screen, the terminal device 200B displays the cancellation completion notification screen on its own display unit using the data in S106B. Although not shown in the figure, the cancellation completion notification screen includes a message indicating that the registration of User A, who was associated with the multifunction peripheral 100 for Service 1, has been cancelled.

[0114] When the above-described next-time registration process is completed, user B again operates terminal device 200B to perform a predetermined operation for user registration for service 1, causing terminal device 200B to send a registration screen request to server 300. In this case, the initial registration process of FIG. 3 is executed to register user B. As a result, user B is registered as a user associated with multifunction peripheral 100 for service 1. When the initial registration process is completed, user B can use service 1 using multifunction peripheral 100.

[0115] In the present embodiment described above, the destination of notification of registered user information (for example, the name of user A) is multifunction device 100. In this case, the registered user information can be notified to user B, who is the administrator of multifunction device 100. In addition, since the registered user information is printed by printing mechanism 170 of multifunction device 100, user B can learn about the registered users by looking at the printed paper.

[0116] Furthermore, according to this embodiment, the server 300 notifies the multifunction peripheral 100 of the information about registered user A, and then receives from the multifunction peripheral 100 a deregistration request transmitted in response to an instruction from user B. When the server 300 receives the deregistration request, it changes the registration information (specifically, the device table DT) stored in the management database DBs so as to deregister user A. When a registration request is received from user B and it is confirmed that user B can log in to the multifunction peripheral 100 as an administrator, it is confirmed that user B is a legitimate administrator of the multifunction peripheral 100. For this reason, when a deregistration request is received from user B, it is considered that there is no problem in deregistering the registration for service 1 used using the multifunction peripheral 100. Furthermore, since user B can deregister user A, user B can register for service 1 himself. This prevents the inconvenience of user B not being able to register because user A is already registered.

[0117] C. Variations (1) In the next registration process of the above embodiment, the server 300 transmits data of the update registration screen W6 including the registered user information to the terminal device 200B in S95 of Fig. 7. Alternatively, the server 300 may transmit data of a registered user information notification screen including only the registered user information to the terminal device 200B. In this case, for example, in S96 of Fig. 7, the terminal device 200B may display the registered user information notification screen including the name and contact email address of user A, and the next registration process may be terminated. In this case, S98 to S106 of Fig. 7 are not executed.

[0118] In this case, user B can learn about registered user A, and can, for example, contact registered user A and request that user A be deregistered from service 1. After user A's registration is deregistered through user A's procedure, user B can send a registration request to server 300 using terminal device 200B, whereby the initial registration process of FIG. 3 is executed and user B is registered for service 1.

[0119] (2) In the next registration process of the above embodiment, the server 300 transmits data of the update registration screen W6 including the registered user information to the terminal device 200B in S95 of FIG. 7. Alternatively, the server 300 may transmit data of the update registration screen W6 that does not include the registered user information to the terminal device 200B. Even in this case, S96 to S106 of FIG. 7 are executed, and user B is registered for service 1. Therefore, in this case, user B cannot obtain information about registered user A, but can use service 1 using the multifunction peripheral 100. Furthermore, leakage of user A's information can be more reliably prevented.

[0120] (3) In the next registration process of the above embodiment, an expiration date for the takeover token is set in S76 of FIG. 5 , but the expiration date does not have to be set. In this case, the server 300 may receive date and time information indicating the date and time when user B logged in to the multifunction device 100 from the multifunction device 100 along with the takeover token. When the server 300 receives date and time information indicating that user B logged in to the multifunction device 100 within a predetermined period from the time when the server 300 received the registration request for user B from the terminal device 200B, the server 300 may transmit the registered user information to the multifunction device 100 or the terminal device 200B. Alternatively, when the server 300 receives the registration request for user B from the terminal device 200B, the server 300 may transmit a one-time code (e.g., a number of about 5 to 10 digits) to the terminal device 200B. In this case, for example, user B may enter the one-time code into the multifunction device 100 after logging in, and the server 300 may receive the one-time code from the multifunction device 100 along with the takeover token. If the server 300 receives a one-time code and a takeover token within a predetermined period from the time when it receives a registration request for user B from the terminal device 200B, it may send the registered user information to the multifunction peripheral 100 or the terminal device 200B.

[0121] (4) In the next registration process of the above embodiment, when login information indicating that an administrator has logged in to the multifunction peripheral 100 is received together with the takeover token (S87 in FIG. 6), the server 300 transmits registered user information to the terminal device 200B (S95 in FIG. 7). For example, if the multifunction peripheral 100 is strictly controlled so that it transmits a takeover token to the outside only when the administrator is logged in and does not transmit a takeover token to the outside when the administrator is not logged in, the multifunction peripheral 100 does not need to transmit login information to the server 300. In this case, the server 300 may transmit registered user information to the terminal device 200B even when it receives a takeover token but does not receive login information.

[0122] (5) The initial registration process and the next registration process in the above embodiment are merely examples and may be modified as appropriate. For example, the initial registration process and the next registration process may be executed collectively for multiple services. Furthermore, terminal devices 200A and 200B execute the initial registration process and the next registration process by launching a browser program BP and communicating with server 300 using a web browser. Alternatively, terminal devices 200A and 200B may execute the initial registration process and the next registration process by launching an application program provided by a service provider and communicating with server 300 using functions realized by the application program.

[0123] (6) In the above embodiment, server 300 is server 300 that provides services 1 to 4. Alternatively, a server other than server 300 may provide services 1 to 4, and server 300 may be a server that only manages user registration for the services.

[0124] (7) In the above embodiment, the initial registration process and the next registration process are realized by one server 300. Alternatively, the initial registration process and the next registration process may be realized by two or more servers that can communicate with each other, with each server sharing the roles. For example, the initial registration process and the next registration process may be realized by a first server that communicates with the multifunction peripheral 100 and a second server that communicates with the terminal devices 200A and 200B working together.

[0125] (8) In the above embodiments, part of the configuration realized by hardware may be replaced by software, and conversely, part or all of the configuration realized by software may be replaced by hardware.

[0126] The present invention has been described above based on examples and modifications, but the above-described embodiments of the invention are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit and scope of the claims, and equivalents thereof are also included in the present invention. [Explanation of symbols]

[0127] 1000...system, 100...multifunction device, 110...CPU, 120...volatile storage device, 130...nonvolatile storage device, 140...display unit, 150...operation unit, 160...reading mechanism, 170...printing mechanism, 180...communication IF, 200A, 200B...terminal device, 300...server, 310...CPU, 320...volatile storage device, 330...nonvolatile storage device, 380...communication IF, BP...browser program, DBp...setting database, DBs...management database, DT...device table, IT...Internet, LNa, LNb...local area network, PGp, PGs...computer program, ST...supported service table, TT...token table, UT...user table, W1...registration screen, W2...new registration screen, W3...registration rejection notification screen, W3...registration rejection notification screen, W3...rejection notification screen, W5...login screen, W6...update registration screen, W7...deregistration confirmation screen

Claims

1. 1. A communication system comprising: a first terminal device used by a first user; a second terminal device used by a second user; A specific device, a server having a storage unit and communicably connected to the first terminal device, the second terminal device, and the specific device; Equipped with The server a first receiving unit that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a registration unit that, when a registration request for the first user is received, registers the first user by storing registration information that associates the first user information with the device identification information in the storage unit; an authentication information storage processing unit that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing unit that transmits the specific authentication information to the specific device when registering the first user; a second receiving unit that receives the device identification information and a registration request for the second user from the second terminal device after the registration of the first user; a response transmitting unit configured to, when a registration request for the second user is received, transmit a rejection notice to the second terminal device indicating that registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device that is in a logged-in state after the rejection notification is transmitted, the login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; an acquisition unit that acquires, when the specific authentication information is received, the first user information associated with the device identification information associated with the specific authentication information in the storage unit; a notification unit that notifies a specific notification destination of the first user information acquired by the acquisition unit when the specific authentication information is received; A communication system comprising:

2. 10. The communication system of claim 1, further comprising: The specific authentication information has a validity period calculated from the date on which the registration request of the second user is received, The notification unit notifies a specific notification destination of the first user information acquired by the acquisition unit when the specific authentication information is received from the specific device within the validity period.

3. 3. The communication system according to claim 2, the specific notification destination is the specific device, the specific device includes at least one of a display unit and a printing unit, A communication system in which the notification unit sends a notification including the first user information to the specific device, and causes the display unit to display the first user information, or causes the printing unit to print the first user information.

4. 3. The communication system according to claim 2, the specific notification destination is the specific device, The server further an instruction receiving unit that receives, from the specific device, a cancellation request to cancel the registration of the first user, the cancellation request being transmitted in response to an instruction from the second user after notifying the specific device of the first user information; a deregistration processing unit that, when receiving the deregistration request, changes the registration information stored in the storage unit so as to deregister the first user; A communication system comprising:

5. 5. A communication system according to claim 3 or 4, the authentication information receiving unit receives, together with the specific authentication information, login information indicating whether an administrator has logged in to the specific device; The notification unit notifies the specific notification destination of the first user information when login information indicating that the administrator is logged in to the specific device is received together with the specific authentication information.

6. 1. A communication system comprising: a first terminal device used by a first user; a second terminal device used by a second user; A specific device, a server having a storage unit and communicably connected to the first terminal device, the second terminal device, and the specific device; Equipped with The server a first receiving unit that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a first registration unit that, when a registration request for the first user is received, executes registration of the first user by storing, in the storage unit, registration information that associates the first user information with the device identification information; an authentication information storage processing unit that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing unit that transmits the specific authentication information to the specific device when registering the first user; a second receiving unit that receives, after the registration of the first user, second user information that is information of the second user, the device identification information, and a registration request for the second user from the second terminal device; a response transmitting unit configured to, when a registration request for the second user is received, transmit a rejection notice to the second terminal device indicating that registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device that is in an administrator login state after the rejection notification is transmitted, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; a registration specifying unit that specifies, when the specific authentication information is received, the registration information including the device identification information associated with the specific authentication information in the storage unit; a second registration unit that, when the specific authentication information is received, updates the specified registration information in the storage unit to registration information that associates the second user information with the device identification information, thereby registering the second user; A communication system comprising:

7. 7. The communication system according to claim 6, further comprising: The specific authentication information is set with a validity period from when the registration request of the second user is received, The second registration unit registers the second user when the specific authentication information is received from the specific device within the validity period.

8. 7. The communication system according to claim 6, the authentication information receiving unit receives, together with the specific authentication information, login information indicating whether an administrator has logged in to the specific device; A communication system in which the second registration unit registers the second user when login information indicating that the administrator is logged in to the specific device is received together with the specific authentication information.

9. A server having a storage unit and communicably connected to a first terminal device used by a first user, a second terminal device used by a second user, and a specific device, a first receiving unit that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a registration unit that, when a registration request for the first user is received, registers the first user by storing registration information that associates the first user information with the device identification information in the storage unit; an authentication information storage processing unit that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing unit that transmits the specific authentication information to the specific device when registering the first user; a second receiving unit that receives the device identification information and a registration request for the second user from the second terminal device after the registration of the first user; a response transmitting unit configured to, when a registration request for the second user is received, transmit a rejection notice to the second terminal device indicating that registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device that is in an administrator login state after the rejection notification is transmitted, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; an acquisition unit that acquires, when the specific authentication information is received, the first user information associated with the device identification information associated with the specific authentication information in the storage unit; a notification unit that notifies a specific notification destination of the first user information acquired by the acquisition unit when the specific authentication information is received; A server comprising:

10. A server having a storage unit and communicably connected to a first terminal device used by a first user, a second terminal device used by a second user, and a specific device, a first receiving unit that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a first registration unit that, when a registration request for the first user is received, executes registration of the first user by storing, in the storage unit, registration information that associates the first user information with the device identification information; an authentication information storage processing unit that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing unit that transmits the specific authentication information to the specific device when registering the first user; a second receiving unit that receives, after the registration of the first user, second user information that is information of the second user, the device identification information, and a registration request for the second user from the second terminal device; a response transmitting unit configured to, when a registration request for the second user is received, transmit a rejection notice to the second terminal device indicating that registration of the second user is rejected; an authentication information receiving unit that receives the specific authentication information from the specific device that is in an administrator login state after the rejection notification is transmitted, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; a registration specifying unit that specifies, when the specific authentication information is received, the registration information including the device identification information associated with the specific authentication information in the storage unit; a second registration unit that, when the specific authentication information is received, updates the specified registration information in the storage unit to registration information that associates the second user information with the device identification information, thereby registering the second user; A server comprising:

11. A computer program for a server having a storage unit, the computer program being communicatively connected to a first terminal device used by a first user, a second terminal device used by a second user, and a specific device, the computer program comprising: a first receiving function that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a registration function that, when a registration request for the first user is received, registers the first user by storing registration information that associates the first user information with the device identification information in the storage unit; an authentication information storage processing function that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing function that transmits the specific authentication information to the specific device when registering the first user; a second receiving function for receiving the device identification information and a registration request for the second user from the second terminal device after the registration of the first user; a response transmission function of transmitting, when the registration request of the second user is received, a rejection notice indicating that the registration of the second user is rejected to the second terminal device; an authentication information receiving function that receives the specific authentication information from the specific device in an administrator login state after transmitting the rejection notification, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; and an acquisition function that acquires, when the specific authentication information is received, the first user information associated with the device identification information associated with the specific authentication information in the storage unit; a notification function that notifies a specific notification destination of the first user information acquired by the acquisition function when the specific authentication information is received; A computer program that enables a computer to realize the above.

12. A computer program for a server having a storage unit, the computer program being communicatively connected to a first terminal device used by a first user, a second terminal device used by a second user, and a specific device, the computer program comprising: a first receiving function that receives, from the first terminal device, first user information that is information about the first user, device identification information that identifies the specific device, and a registration request for the first user; a first registration function that, when a registration request for the first user is received, executes registration of the first user by storing, in the storage unit, registration information that associates the first user information with the device identification information; an authentication information storage processing function that stores specific authentication information in the storage unit in association with the device identification information when registering the first user; an authentication information transmission processing function that transmits the specific authentication information to the specific device when registering the first user; a second receiving function that receives, after the registration of the first user, second user information that is information of the second user, the device identification information, and a registration request of the second user from the second terminal device; a response transmission function of transmitting, when the registration request of the second user is received, a rejection notice indicating that the registration of the second user is rejected to the second terminal device; an authentication information receiving function that receives the specific authentication information from the specific device in an administrator login state after transmitting the rejection notification, the administrator login state being a state in which an administrator is logged in to the specific device using administrator information that is not stored in the storage unit of the server; and a registration specifying function that, when the specific authentication information is received, specifies the registration information including the device identification information associated with the specific authentication information in the storage unit; a second registration function that, when the specific authentication information is received, updates the specified registration information in the storage unit to registration information that associates the second user information with the device identification information, thereby registering the second user; A computer program that enables a computer to realize the above.

Images