Communication system, server, and computer program

Abstract

To reduce dissatisfaction that a user may feel when he / she is asked to enter information into an input screen for user registration.SOLUTION: A communication system displays an input screen containing multiple input fields on a terminal device. When a registration instruction is entered with information on multiple items already entered into the multiple input fields, the communication system determines whether or not the information on the multiple items satisfies registration conditions. If the registration conditions are satisfied, the communication system performs user registration. While the user is still inputting information before the registration instruction is entered, the communication system determines a suggestive value suggesting the likelihood of successful user registration based on the information already entered into the input fields, and displays suggestive information based on the suggestive value on the input screen currently displayed on the display unit.SELECTED DRAWING: Figure 6

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 the case where a desired result is not obtained after inputting information, for example, where the user's registration is rejected, which can result in the user becoming dissatisfied when the desired result is not obtained.

[0005] This specification discloses a technique that can reduce the dissatisfaction that a user may feel when asked to input information into an input screen for user registration. [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 terminal device used by a user, the terminal device having a display unit that displays a screen and an operation unit that receives user operations; and a server that is communicably connected to the terminal device and has a storage unit that stores registered user information, the user information including information of a plurality of items, the system including: an input screen display process that displays, on the display unit of the terminal device, an input screen including a plurality of input fields for inputting the information of the plurality of items; and a condition determination process that, when a registration instruction is input with the information of the plurality of items already entered in the plurality of input fields, determines whether the information of the plurality of items already entered satisfies a registration condition, the registration condition including a condition determined based on a comparison between the information of the plurality of items already entered and the information of the plurality of items included in the registered user information; and, when the registration condition is satisfied, a condition determination process that determines whether the information of the plurality of items already entered satisfies a registration condition. a registration process for registering a user by storing user information including information on items in the storage unit, and not registering the user if the registration conditions are not met; an input information acquisition process for acquiring information on one or more items that have been entered in the multiple input fields, in an input-in-progress state before the registration instruction is input, in which the input screen is displayed on the display unit so that information can be entered into the multiple input fields; a suggestion value determination process for determining a suggestion value that suggests the possibility of user registration being permitted based on the information on the one or more items acquired in the input information acquisition process, in the input-in-progress state, wherein the suggestion value is determined based on a comparison between the information on the one or more items and information on the multiple items included in the registered user information; and a suggestion information display process for displaying suggestion information based on the suggestion value on the input screen being displayed on the display unit, in the input-in-progress state.

[0008] When a registration instruction is input after inputting information for multiple items on an input screen, if user registration is not performed because the registration conditions are not met, the user may feel dissatisfied due to the fact that the input was wasted. According to the above configuration, in the input state, a suggestion value that suggests the possibility that user registration will be permitted is determined based on the information already input on the input screen, and suggestion information based on the suggestion value is displayed on the input screen. As a result, the user can recognize to some extent the possibility that user registration will be permitted while inputting information. Therefore, the user can also abandon user registration in the middle of inputting information. Furthermore, even if user registration is not performed when a registration instruction is input after inputting information, the user is unlikely to feel dissatisfied because he or she can foresee that user registration will not be performed. In this way, it is possible to reduce the dissatisfaction that the user may feel when the user is asked to input information on an input screen for user registration.

[0009] The technology disclosed in this specification can be realized in various forms, such as a communication system including a device, an external device, and a server, a communication method using a device, an external device, and a server, a computer program for realizing these servers, systems, and methods, a recording medium on which the computer program is recorded, and the like. [Brief explanation of the drawings]

[0010] [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] Sequence of user registration process for service 1. [Figure 4] Sequence of user registration process for service 1. [Figure 5] FIG. 10 is a diagram showing an example of an input screen W1. [Figure 6] 10 is a flowchart of a suggestion image update process. [Figure 7] 10A and 10B are diagrams showing examples of a registration completion screen and a registration failure notification screen. [Figure 8]10 is a flowchart of a registration failure notification generation process. DETAILED DESCRIPTION OF THE INVENTION

[0011] 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, a terminal device 200, and a server 300 for providing a service (hereinafter simply referred to as a service) that uses the multifunction peripheral 100, as will be described later.

[0012] 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, 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.

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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. The multifunction device 100 also controls the reading mechanism 160 to generate scan data. The multifunction device 100 also executes the computer program PGp to communicate with the server 300 and perform processes related to the service (for example, a process for transmitting history information to the server 300).

[0017] The setting database DBp stores various setting information related to the multifunction peripheral 100. The setting information includes, for example, setting information related to printing, setting information related to scanning, and setting information related to the services provided by the server 300.

[0018] 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.

[0019] 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.

[0020] The multifunction peripheral 100 is connected to, for example, a user's local area network LN and is used by the user.

[0021] The terminal device 200 is a computer used by a user of the multifunction peripheral 100, such as a personal computer, and is connected to the local area network LN. In a modified example, the terminal device 200 may be a smartphone or a tablet computer. The terminal device 200 includes a CPU 210 as a controller for the terminal device 200, a volatile storage device 220 such as RAM, and a non-volatile storage device 230 such as a hard disk drive or flash memory.

[0022] The terminal device 200 also includes a display unit 240, an operation unit 250 that receives operations by the user, and a wired or wireless communication IF 280 for connecting to the Internet IT. The display unit 240 is, for example, a liquid crystal display, and the operation unit 250 is, for example, a mouse, keyboard, or touch panel.

[0023] The CPU 210 is a computing device that performs data processing. The volatile storage device 220 provides a buffer area for temporarily storing various intermediate data generated when the CPU 210 performs processing. The non-volatile storage device 230 stores a browser program BP.

[0024] The CPU 210 functions as a web browser by executing the browser program BP. The terminal device 200 (CPU 210) functioning as a web browser executes a user registration process, which will be described later, in cooperation with the server 300. The terminal device 200 is connected to, for example, a local area network LN, and is connected to the Internet IT via the local area network LN.

[0025] The server 300 is, for example, a computer, such as a cloud server, operated by a service provider (for example, a provider that manufactures and sells the multifunction peripheral 100). The server 300 includes a CPU 310 as a controller for 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.

[0026] 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.

[0027] 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 executes a user registration process (described later) in cooperation with the terminal device 200. The management database DBs stores various data (described later) required for processing related to the service.

[0028] The server 300 is connected to the Internet IT, which allows the server 300 to communicate with both the multifunction peripheral 100 and the terminal device 200 via the Internet IT.

[0029] 1, only the multifunction device 100 is shown, but the server 300 communicates with a large number of devices (multifunction devices and standalone printers) to provide services that use the devices (for example, 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 target of the service.

[0030] 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.

[0031] 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.

[0032] 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 more than once for one type of service (for example, service 1). For example, suppose that a user has registered for service 1 in association with the multifunction device 100. In this case, the user cannot register for service 1 in association with the same multifunction device 100. The user can register for a service different from service 1 (for example, service 2) in association with the same multifunction device 100.

[0033] A2. Management databases The following describes the management database DBs stored in the nonvolatile storage device 330 of the server 300. 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 weight table WT.

[0034] The user table UT is a table in which registered user information for 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 about the user identified by the user ID, in association with each user ID. As shown in FIG. 2(A), the user information includes multiple items, specifically, the user ID, email address, address, user name, year of birth, and gender. For the name, the family name and first name are registered as separate items. The user information further includes information necessary for using the service, such as payment information (e.g., credit card number) (not shown). In this way, the user information may include personal information. In the example of FIG. 2, the above-mentioned user information is stored in association with the user IDs "UID_A" and "UID_B" of the users.

[0035] 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, service 2, and service 3 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 services 1 to 3 out of services 1 to 4.

[0036] The device table DT is a table that stores information about devices (e.g., the multifunction peripheral 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 no user ID is associated with the service if the user has not registered. The serial number is associated with the user ID and is information used to identify the device that the user uses to use the service, and is therefore also a type of user information.

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

[0038] The weight table is a table in which weights used in the user registration process are recorded for each initial registration item of user information registered in the user registration process described below. The initial registration items include, for example, part of the user information registered in the user table UT. In this embodiment, the initial registration items are email address, address, user name (first and last name), year of birth, and gender. For the user name, weights are set for both the first and last name. The weight table WT will be further explained in the user registration process described below.

[0039] 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.

[0040] A3.User registration process The user registration process for the above-mentioned services 1 to 4 will be described. For each of services 1 to 4, user registration is performed in association with a device (for example, the multifunction peripheral 100). This user registration process is executed separately for each of services 1 to 4. The following description will be given taking the user registration process for service 1 as an example.

[0041] 3 and 4 show the sequence of the user registration process for service 1. In S2, terminal device 200 receives an instruction to display input screen W1 from the user. Specifically, the user starts browser program BP on terminal device 200 and performs a predetermined operation on terminal device 200, which functions as a web browser. The predetermined operation includes, for example, inputting a uniform resource locator (URL) of server 300 to access a web page provided by server 300 and inputting an input instruction for input screen W1 via the web page.

[0042] When the terminal device 200 receives an instruction to display the input screen W1, the terminal device 200 (CPU 210) functioning as a web browser transmits an input screen request to the server 300. Communication between the terminal device 200 and the server 300 is performed in accordance with a known protocol, for example, HTTP (Hypertext Transfer Protocol). For this purpose, the input screen request is, for example, an HTTP request including a URL indicating the location of the input screen W1 for service 1.

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

[0044] Fig. 5 is a diagram showing an example of the input screen W1. The input screen W1 in Fig. 5 includes a message MS1 prompting user registration, a possibility suggestion image RS, a plurality of input elements TB1 to TB6, RBa, RBb, and a registration button BTr.

[0045] The possibility suggestion image RS, the details of which will be described later, is an image showing suggestion information suggesting the possibility that user registration will be permitted (hereinafter referred to as registration possibility).

[0046] The multiple input elements include input fields TB1 to TB5 and radio buttons RBa and RBb for inputting the initial registration items to be registered in the user registration process. As described above, in this embodiment, the initial registration items include a serial number, an email address, an address, the user's name (first and last name), a year of birth, and a gender. Thus, the initial registration items include information including the user's personal information and information about the device (e.g., the multifunction peripheral 100) that the user will use for service 1. The initial registration items may include other items, such as payment information (credit card number), a telephone number, a display name, an occupation, and a job title. The initial registration items may also include items other than the serial number related to the device to be used, such as the date and year of purchase of the device and the store where the device was purchased. The multiple items may also include required and optional items. In this embodiment, the multiple initial registration items included in the input screen W1 are required.

[0047] The registration button BTr is a button for the user to input a registration instruction. The processes of S10 to S20 are repeatedly executed from when the input screen W1 is displayed on the display unit 140 (S8) until when the user presses the registration button BTr to input a registration instruction into the terminal device 200 (S22). The state in which the input screen W1 is displayed and before the registration instruction is input is a state in which the user can input information into each input element of the input screen W1 (hereinafter also referred to as an input state).

[0048] In S10, the user updates information (hereinafter also referred to as input information) already entered for one of the multiple input elements on the input screen W1. This causes the multifunction peripheral 100 to acquire updated input information for the one input element. For example, the user selects an input field TB1, which is an input element that has not been filled in, and enters an email address in the input field TB1. When the user then performs an operation on another input element (for example, selecting an input field TB2), the terminal device 200 determines that the update of the input information for the input field TB1 has been completed, and acquires the email address entered in the input field TB1 at that time as updated input information. Furthermore, for example, the user selects the input field TB1, in which an email address has already been entered, and deletes the email address entered in the input field TB1. When the user then performs an operation on another input element, the terminal device 200 acquires information indicating that the input field TB1 has no input, as updated input information. More specifically, the terminal device 200 acquires information indicating that the input field TB1 is “empty” or in its initial state, as updated input information. Also, for example, if a user selects an input field TB1 in which an email address has already been entered and changes the email address entered in the input field TB1 to another email address, when the user subsequently performs an operation on another input element, the terminal device 200 acquires the other email address entered in the input field TB1 as updated input information.

[0049] Upon acquiring the updated input information, the terminal device 200 transmits the updated input information to the server 300 in S12. In this manner, every time the input information for each input element is updated, the updated input information is transmitted to the server 300.

[0050] When the server 300 receives the updated input information, it executes a suggestion image update process for updating the possibility suggestion image RS in S15. Fig. 6 is a flowchart of the suggestion image update process.

[0051] In S110, the server 300 updates the data indicating the input information group for the input screen W1 stored in the server 300 based on the updated input information for one item received in S12. For example, the input information group indicates input information for each input element on the input screen W1. The initial value of the input information group indicates that nothing has been entered for each input element on the input screen W1. The input information group is updated every time updated input information for one item is received from the server 300. As a result, the server 300 can grasp the input information (serial number and user information) for each input element on the input screen W1 in real time.

[0052] In S115, the server 300 searches the device table DT for a record that includes the serial number that has been entered on the input screen W1. For example, if the serial number that has been entered on the input screen W1 is "DID_1," the search extracts record Rd, which is indicated by the dashed line in Fig. 2. If a serial number that is being registered for the first time or if no serial number has been entered on the input screen W1, no record is extracted by the search.

[0053] In S120, the server 300 uses the search results to determine whether there is a user registration associated with the serial number entered on the input screen W1. Specifically, if a record is extracted in S115, the server 300 determines whether there is a user ID associated with the service to be registered in the user registration process (hereinafter also referred to as the target service; in this embodiment, service 1) in the record. If there is a user ID associated with the target service in the extracted record, the server 300 determines that there is a user registration associated with the serial number entered on the input screen W1 (S120: YES). If there is no user ID associated with the target service in the extracted record, the server 300 determines that there is no user registration associated with the input serial number (S120: NO). Furthermore, if no record is extracted in S115, the server 300 also determines that there is no user registration associated with the input serial number (S120: NO).

[0054] If there is a user registration associated with the entered serial number (S120: YES), the server 300 determines the registration possibility suggestion value EV to be the maximum value in S125. Here, the registration possibility suggestion value EV is a value determined based on the current input information for each input element on the input screen W1 (in other words, the updated input information acquired in S12), and is a value indicating the possibility that user registration will be permitted (hereinafter also referred to as registration possibility). In this embodiment, the registration possibility suggestion value EV indicates a larger value when the registration possibility is lower. In this embodiment, the registration possibility suggestion value EV indicates a value between 0 and 100, and the initial value is 0. For this reason, in this step, the registration possibility suggestion value EV is determined to be the maximum value of 100. In other words, in this step, the registration possibility suggestion value EV is determined to be the value indicating the lowest registration possibility. After the registration possibility suggestion value EV is determined, the process proceeds to S155.

[0055] If there is no user registration associated with the serial number entered on the input screen W1 (S120: NO), the server 300 compares the information entered on the input screen W1 with the registered user information stored in the user table UT, item by item, in S130, and searches for records containing user information that matches in one or more items. For example, if the surname of the user entered on the input screen W1 is "Yamada," the search extracts record Ru, indicated by the dashed line in the user table UT in FIG. 2. This search can extract multiple records contained in the user table UT.

[0056] In S135, the server 300 uses the search result to determine whether a record of a user registered with the target service (e.g., service 1) has been extracted. Specifically, the server 300 determines whether each of the user IDs included in the one or more records extracted in S130 is associated with the target service by referring to the device table DT. If the one or more records extracted in S130 include a record containing a user ID associated with the target service, it is determined that a record of a user registered with the target service has been extracted (S135: YES). If the one or more records extracted in S130 do not include a record containing a user ID associated with the target service, it is determined that a record of a user registered with the target service has not been extracted (S135: NO). Also, if no record is extracted in S130, it is determined that a record of a user registered with the target service has not been extracted (S135: NO).

[0057] If a record of a user who is already registered with the target service has not been extracted (S135: NO), the server 300 determines the registration possibility suggestion value EV to be the minimum value in S140. As described above, the registration possibility suggestion value EV indicates a value between 0 and 100, and the initial value is 0. For this reason, in this step, the registration possibility suggestion value EV is determined to be 0, which is the minimum value. In other words, in this step, the registration possibility suggestion value EV is determined to be a value that indicates the highest possibility of registration. After the registration possibility suggestion value EV is determined, the process proceeds to S155.

[0058] If records of users registered with the target service are extracted (S135: YES), the server 300 calculates the sum of weights of matching items WA for each extracted record of the registered user in S145. Specifically, for a target record among the extracted records of the registered user, the server 300 identifies one or more input elements (hereinafter also referred to as matching items) whose input information on the input screen W1 matches the information recorded in the record. The server 300 obtains the weights of the one or more matching items from the weight table WT (FIG. 2) and calculates the sum of the weights of the one or more matching items as the sum of weights WA of the target record. For example, if "address" and "surname" are matching items, the sum of the weights of "address" (10) and "surname" (10) (10 + 10 = 20) is calculated as the sum of weights WA. In this way, by adding the weights for each matching item, the sum of weights WA that is a candidate for the registration possibility suggestion value EV is calculated.

[0059] In S150, the server 300 determines the maximum value of the weight sums WA of the extracted registered user records as the registration possibility suggestion value EV.

[0060] As can be seen from the above explanation, the registration possibility suggestion value EV is determined based on a comparison between the multiple pieces of input information already entered on the input screen W1 and the user information already registered in the management database DBs.

[0061] Here, a supplementary explanation will be given regarding the weights recorded in the weight table WT shown in FIG. 2. In the weight table WT, the weight of an email address is set to "0." That is, the weight sum WA, and therefore the registration possibility suggestion value EV, does not change depending on whether the email address entered on the input screen W1 matches the email address included in the registered user information. Assume that the registration possibility suggestion value EV changes and the possibility suggestion image RS changes depending on whether the email address entered on the input screen W1 matches the email address included in the registered user information. In this case, for example, a fraudster can enter various email addresses into the input field TB1 and observe the changes in the possibility suggestion image RS to determine whether the email address entered into the input field TB1 is registered. This allows the fraudster to fraudulently obtain the email addresses of users of the target service. Email addresses can be easily used, for example, as the destination of spam emails, and therefore, if they are leaked, the disadvantages are great. For this reason, in this embodiment, the weight of an email address is set to "0."

[0062] In addition, in the weight table WT, the weights of year of birth and gender are lower than those of address and name. This is because year of birth and gender are items that have little relation to the registration conditions described below.

[0063] In S155, the server 300 generates a possibility suggestion image RS based on the determined registration possibility suggestion value EV. Once the possibility suggestion image RS is generated, the server 300 ends the suggestion image update process.

[0064] As shown in FIG. 5, the possibility suggestion image RS includes a bar-shaped display area DA and a bar-shaped portion BR (hatched portion) located within the display area DA. The length of the bar-shaped portion BR in the longitudinal direction (horizontal direction in FIG. 5) corresponds to the registration possibility suggestion value EV. Therefore, in this embodiment, the longer the horizontal length of the bar-shaped portion BR, the lower the registration possibility, and the shorter the horizontal length of the bar-shaped portion BR, the higher the registration possibility. For example, the longitudinal length of the bar-shaped portion BR is determined in three rough stages, for example, from 3 to 5 stages. In this embodiment, the length is determined in three stages: (1 / 3) the length of the display area DA when the registration possibility suggestion value EV is 0 or greater but less than 35; (2 / 3) the length of the display area DA when the registration possibility suggestion value EV is 35 or greater but less than 70; and (2 / 3) the length of the display area DA when the registration possibility suggestion value EV is 70 or greater.

[0065] 3, the server 300 transmits data of the possibility suggestion image RS generated in the suggestion image update process (S15) to the terminal device 200. Upon receiving the data of the possibility suggestion image RS, the terminal device 200 uses the data to update the input screen W1 displayed on the display unit 240 in S20. Specifically, the server 300 updates the possibility suggestion image RS included in the input screen W1 to the possibility suggestion image RS indicated by the data received in S18.

[0066] The above-described processes of S10 to S20 are repeated every time information is input to one input element on the input screen W1, whereby the possibility suggestion image RS is updated in real time as needed while the user is inputting information on the input screen W1.

[0067] When the user has completed inputting information into the input screen W1, in S22, the user inputs a registration instruction by pressing the registration button BTr on the input screen W1. That is, in S22, the registration instruction is input in a state in which information for a plurality of items to be input into the input elements TB1 to TB6, RBa, and RBb of the input screen W1 has already been input into these input elements. When the terminal device 200 acquires an input instruction from the user, the terminal device 200 acquires all of the input information that has been input into the input elements TB1 to TB6, RBa, and RBb of the input screen W1 at that time, and transmits all of the input information to the server 300.

[0068] When the server 300 receives the input information from the terminal device 200, in S28, it determines whether or not the registration conditions are met based on the input information, that is, the information of the multiple items that have been input by the user on the input screen W1.

[0069] In this embodiment, if the following conditions 1 to 3 are met, it is determined that the registration conditions are met, and if at least some of the conditions 1 to 3 are not met, it is determined that the registration conditions are not met. Condition 1: The entered serial number does not match the serial number of the registered device used in the target service. Condition 2: The entered email address does not match the email address of a registered user of the target service. Condition 3: The entered address and name (first and last name) set does not match the address and name set of a registered user of the target service.

[0070] As can be seen from conditions 1 to 3, in this embodiment, the registration conditions include that at least some of the information in the multiple items already entered on the input screen W1 does not match at least some of the information in the multiple items included in the registered user information.

[0071] Condition 1 is determined to be satisfied if a record including a serial number included in the input information on the input screen W1 is not recorded in the device table DT, or if a record including the serial number is recorded in the device table DT but the ID of the user of the target service is not recorded in that record. Condition 2 is determined to be satisfied if the email address included in the input information on the input screen W1 is not recorded in the user table UT as the email address of a registered user of the target service. Condition 3 is determined to be satisfied if the set of the address and name included in the input information on the input screen W1 is not recorded in the user table UT as the address and name of a registered user of the target service. As can be seen from the above explanation, the registration conditions in this embodiment can be said to be determined based on a comparison of information on multiple items entered on the input screen W1 with information on multiple items registered in the management database DBs (user table UT and device table DT).

[0072] If it is determined in S28 that the registration conditions are met, the processes of S32 to S35 in FIG. 4 are executed.

[0073] In S32, the server 300 executes user registration for the target service using the multiple items of information received from the terminal device 200. Specifically, the server 300 generates a user ID. The server 300 associates the received user information, such as email address, address, and name, with the generated user ID and records them in the user table UT. As a result, one new row of record is recorded in the user table UT of FIG. 2.

[0074] Furthermore, the server 300 newly registers a user associated with a device (e.g., the multifunction peripheral 100) for the target service (e.g., service 1). Specifically, the server 300 identifies the model name of the multifunction peripheral 100 by searching for the serial number received in S28 in a table (not shown) that associates serial numbers with model information such as model names. The server 300 records a user ID indicating the user of service 1 in the device table DT, in association with the serial number and model name of the multifunction peripheral 100. The user ID to be recorded is the user ID newly recorded in the user table UT. As a result, one row of record is newly recorded in the device table DT of FIG. 2.

[0075] In S34, the server 300 transmits data of the registration completion screen W2 to the terminal device 200. Upon receiving the data of the registration completion screen W2, the terminal device 200 displays the registration completion screen W2 on the display unit 140 using the data in S35.

[0076] 7A and 7B are diagrams showing examples of a registration completion screen and a registration failure notification screen. The registration completion screen W2 in Fig. 7A includes a message MS2 indicating that user registration for the target service has been completed, and an OK button BTo. When the OK button BTo is pressed, the terminal device 200 terminates the display of the registration completion screen W2, and the user registration process is terminated.

[0077] Once the above user registration process is complete, the user can use service 1 using multifunction device 100. For example, if service 1 is the above-mentioned print management service, 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.

[0078] If it is determined in S28 that the registration conditions are not met, the processes of S40 to S48 in Fig. 4 are executed. In S40, the server 300 executes a registration failure notification generation process. The registration failure notification generation process is a process for generating a registration failure notification screen for notifying that registration of the target service is not possible.

[0079] FIG. 8 is a flowchart of the registration failure notification generation process. In S210, the server 300 identifies the user ID of the registered user (hereinafter also referred to as the causative user) who caused the registration condition not to be satisfied. In other words, when the registration condition is not satisfied because specific user information (e.g., a serial number or an email address) is registered in the management database DBs (the user table UT is the device table DT), the user ID included in the specific user information (i.e., the user information of the causative user) is identified. For example, when the registration condition is not satisfied because the above-mentioned condition 1 is not satisfied, the user ID associated with the target service in the record of the device table DT that includes the same serial number as the input serial number is identified as the user ID of the causative user. For example, when the input serial number is "DID_1" and the target service is "service 1," "UID_A" associated with service 1 in the record Rd indicated by the dashed line in FIG. 2 is identified as the user ID of the causative user. Furthermore, if the registration conditions are not met because the above-mentioned condition 2 is not met, the user ID included in the record in the user table UT that contains the same email address as the input email address is identified as the user ID of the cause user. For example, if the input email address is "MA_A," "UID_A" included in the record Ru shown by the dashed line in Figure 2 is identified as the user ID of the cause user. Similarly, if the registration conditions are not met because the above-mentioned condition 3 is not met, the user ID included in the record in the user table UT that contains the same address and name as the input user's address and name is identified as the user ID of the cause user.

[0080] In S220, the server 300 identifies, from among services other than the target service, services for which the cause user is registered. For example, the server 300 identifies a record in the device table DT that includes the user ID of the cause user. The server 300 identifies a service that is associated with the user ID of the cause user and is other than the target service in the service registration information included in the identified record. For example, if the user ID of the cause user is "UID_A" and the target service is "service 1," the server 300 identifies record Rd in the device table DT, as indicated by the dashed line in FIG. 2. In the service registration information of this record Rd, "UID_A" is associated with service 1 and service 3. For this reason, in this example, service 3 is identified as the service for which the cause user is registered. If there are no other services for which the cause user is registered, it is determined that there are no other services for which the cause user is registered.

[0081] The services identified in this step are services that are different from the target service and that the user currently performing the user registration process cannot register using the user information that has already been entered.

[0082] In S230, the server 300 registers services that the cause user has not registered, among those that can be used with the device having the input serial number. For example, the server 300 identifies the model name of the multifunction device 100 by searching for the input serial number 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 with the multifunction device 100 by searching for a record containing the identified model name in the corresponding service table ST (FIG. 2). The server 300 references the service registration information of a record in the device table DT that includes the user ID of the cause user, and identifies services that cannot be associated with a user ID, among those that can be used with the multifunction device 100. For example, if the model name of the multifunction device 100 is "MA_1," the server 300 references the record Rm indicated by the dashed line in FIG. 2, and identifies services 1 to 3 as the services that can be used with the multifunction device 100. Then, when the user ID of the cause user is "UID_A", the record Rd indicated by the dashed line in FIG. 2 in the device table DT is referenced, and the services to which no user ID is associated are identified as services 2 and 4. For this reason, in this example, service 2 is identified as the service for which the cause user is not registered. If there are no services for which the cause user is not registered, it is identified that there are no services for which the cause user is not registered.

[0083] The services identified in this step are, among the services available using the multifunction peripheral 100, services that the user currently performing the user registration process can register using the user information that has already been input.

[0084] In S240, the server 300 determines whether the name notification condition is met. The name notification condition is a condition for determining whether the name of the cause user should be notified to the user currently performing the user registration process. If the name notification condition is met, the name of the cause user is notified. In this embodiment, the name notification condition is determined to be met if the address and surname entered on the input screen W1 match the address and surname of the cause user. Since the address and surname of the cause user are registered in the user table UT, the name notification condition is determined by referring to the user table UT.

[0085] If the name notification condition is met (S240: YES), the server 300 generates a registration failure notification screen W3 including the name of the causing user in S250. Once the registration failure notification screen W3 is generated, the registration failure notification generation process ends. The registration failure notification screen W3 in Fig. 7(B) includes a message MS3 indicating that user registration for the target service is not possible, a message MS4 indicating the reason why user registration is not possible, registered service information IF1, unregistered service information IF2, name information IF3 indicating the name of the causing user, and an OK button BTo.

[0086] If user registration is not possible because the above-mentioned condition 1 is not met, message MS4 indicates that the user's device (e.g., multifunction peripheral 100) is already registered as a device to be used with service 1. If user registration is not possible because the above-mentioned condition 2 is not met, message MS4 indicates that the email address entered by the user is already registered as the email address of another user who is registered with service 1. If user registration is not possible because the above-mentioned condition 3 is not met, message MS4 indicates that the set of address and name entered by the user is already registered as the address and name of another user who is registered with service 1.

[0087] Registered service information IF1 indicates services that have been registered by the cause user. If the cause user has not registered any other services, the display of registered service information IF1 is omitted. Unregistered service information IF2 indicates services that have not been registered by the cause user. If the cause user has not registered any services, the display of unregistered service information IF2 is omitted.

[0088] If the name notification condition is not met (S240: YES), the server 300 generates a registration failure notification screen W4 in S260 that does not include the name of the causing user. Once the registration failure notification screen W4 is generated, the registration failure notification generation process ends. The registration failure notification screen W4 in FIG. 7(C) includes a message MS3 indicating that user registration for the target service is not possible, a message MS4 indicating the reason why user registration is not possible, registered service information IF1, unregistered service information IF2, and an OK button BTo. Unlike the registration failure notification screen W3, the registration failure notification screen W4 does not include name information IF3.

[0089] In S46 of FIG. 4 after the registration failure notification generation process, the server 300 transmits data for the registration failure notification screen (W3 or W4) to the terminal device 200. Upon receiving the data for the registration failure notification screen, the terminal device 200 uses the data to display the registration failure notification screen on the display unit 240 in S48. By viewing the registration failure notification screen W3 or W4, the user can recognize that registration for the target service is not possible and the reason for the registration failure. Furthermore, by viewing the registration failure notification screen W3 or W4, the user can recognize other services that cannot be registered and services that can be registered, among the services available using the multifunction peripheral 100. Furthermore, by viewing the registration failure notification screen W4, the user can recognize the name of the user who performed the user registration that prevented the user from registering.

[0090] According to the present embodiment described above, the system 1000 displays the input screen W1 (FIG. 5) on the display unit 240 of the terminal device 200 (S2 to S8 in FIG. 3). When a registration instruction is input after input information for multiple items has already been input into multiple input elements TB1 to TB6, RBa, and RBb (S22 in FIG. 3), the system 1000 determines whether the input information satisfies the registration conditions (S28 in FIG. 3). When the registration conditions are satisfied, the system 1000 performs user registration by storing user information including the input information in the management database DBs (user table UT and device table DT in FIG. 2) (S32 in FIG. 4). When the registration conditions are not satisfied, the system 1000 does not perform user registration (S40 to S48 in FIG. 4). When the input screen W1 is displayed and the input information is in an input state before the registration instruction is input, the system 1000 acquires the input information that has already been input into the multiple input elements (S12 in FIG. 3). The system 1000 determines a registration possibility suggestion value EV based on input information acquired in the input state (S15 in FIG. 3, S110 to S150 in FIG. 6). In the input state, the system 1000 displays a possibility suggestion image RS on the input screen W1 being displayed on the display unit 240 as suggestion information based on the registration possibility suggestion value EV (S18 and S20 in FIGS. 5 and 3).

[0091] If a user inputs multiple fields of information on the input screen W1 and then inputs a registration instruction, the user may feel dissatisfied if user registration is not performed because the registration conditions are not met. For example, if there are many fields to be input, the user is likely to feel dissatisfied that the input was wasted. Furthermore, if the fields to be input include personal information, the user is likely to feel dissatisfied if the personal information is not registered despite being submitted. In this embodiment, during the input state, a registration possibility suggestion value EV is determined based on the information already input on the input screen W1, suggesting the possibility that user registration will be permitted. A possibility suggestion image RS, which is suggestive information based on the registration possibility suggestion value EV, is displayed on the input screen W1 (FIG. 2). As a result, the user can recognize to some extent the possibility that user registration will be permitted while inputting information on the input screen W1. Therefore, the user can abandon user registration midway through inputting information. Furthermore, even if user registration is not performed when inputting a registration instruction after inputting information, the user can predict that user registration will not be performed, and is therefore less likely to feel dissatisfied. In this way, the user's potential dissatisfaction can be reduced when the user is required to input information on the input screen for user registration.

[0092] Furthermore, according to this embodiment, in the input state, each time input is completed for one of the multiple input elements TB1 to TB6, RBa, and RBb, the system 1000 acquires the input information (S12 in FIG. 3), updates the registration possibility suggestion value EV using the acquired input information (S15 in FIG. 3), and updates the possibility suggestion image RS displayed on the input screen W1 based on the updated registration possibility suggestion value EV (S18, S20 in FIG. 3). As a result, each time input for one input element is completed, the possibility suggestion image RS displayed on the input screen W1 is updated. As a result, the user can check to some extent in real time the possibility of user registration being permitted each time information is input for an input element.

[0093] As can be seen from the weight table WT in FIG. 2, the explanation of the suggestion image update process in FIG. 6, and the explanation of the registration conditions (conditions 1 to 3), the registration possibility suggestion value EV does not accurately indicate the probability of satisfying the registration conditions. For example, if the address and name (surname and given name) entered on the input screen W1 match the address and name of a registered user of the target service, the registration condition is not satisfied, but the registration possibility suggestion value EV does not reach its maximum value. Furthermore, in cases where a user entering information on the input screen W1 is unable to register as a user because a registered user already exists, this is often due to the user having already registered as a user but forgetting that fact, or a family member living with the user having already registered as a user. In such cases, if the user can predict the possibility of failing user registration by observing the gradual increase in the registration possibility suggestion value EV displayed on the possibility suggestion image RS while entering information on the input screen W1, the user's frustration can be alleviated even if the user is unable to register as a user after entering a lot of information. Furthermore, it is believed that the user's frustration will be reduced if the user aborts registration based on the suggestion.

[0094] Furthermore, according to this embodiment, the input information that has been entered is compared item by item with information on multiple items included in the registered user information, and a specific value (weight in this embodiment) is added for each matching item to determine the registration possibility suggestion value EV (S145 in FIG. 6). In this embodiment, as shown in conditions 1 to 3, if some items of the information input to the input screen W1 match some items of the registered user information, the registration condition is not met. For this reason, in this embodiment, the registration possibility suggestion value EV is determined by adding a specific value for each matching item, so that an appropriate registration possibility suggestion value EV can be determined.

[0095] Furthermore, in this embodiment, the registration possibility suggestion value EV is determined using weights set for each of the multiple items to be entered (weight table WT in FIG. 2). The multiple items to be entered include items that are loosely related to the registration conditions and items that are closely related. Also, depending on the item, it may be preferable not to affect the registration possibility suggestion value EV. For this reason, by setting a weight for each of the multiple items, an appropriate registration possibility suggestion value EV can be determined using the weight.

[0096] According to this embodiment, the multiple items of user information include a serial number identifying a device used by the user. In this embodiment, if the serial number entered into the input screen W1 matches the registered serial identification information (YES in S120 of FIG. 6), the registration possibility suggestion value EV is set to the maximum value, i.e., a value indicating the lowest registration possibility (S125 of FIG. 6). As a result, when a user attempts to register an already registered device as a device to be used for a service by entering the registered serial number into the input field TB6, the possibility suggestion image RS displayed on the input screen W1 at that time indicates the lowest registration possibility. This prevents a user from attempting to register an already registered device as a device to be used for a service. For example, in this embodiment, if a user attempts to register an already registered device as a device to be used for a service, the registration is not permitted regardless of the information entered in the other user information. In this case, since entering user information including personal information into the input screen W1 is futile, it is preferable to strongly suggest to the user that registration is not permitted. In this embodiment, a possibility suggestion image RS strongly suggesting that registration is not permitted can be displayed in such a case.

[0097] Furthermore, according to this embodiment, in the user registration process for service 1, if user registration for service 1 is not performed, other services among the multiple services 1 to 4 that are associated with the user information of the causative user who caused the registration conditions to not be satisfied, i.e., services in which the causative user has already been registered, are displayed on the display unit 240 (S220 in FIG. 8, FIGS. 7(B) and (C)). As a result, if user registration for service 1 is not possible, the user can also be notified of other services for which user registration is not possible.

[0098] Furthermore, according to this embodiment, in the registration process for service 1, if user registration for service 1 is not performed, among the multiple services 1 to 4, services that are not associated with the user information of the causative user who caused the registration conditions to not be satisfied, i.e., services for which the causative user is not registered, are displayed on the display unit 240 (S230 in FIG. 8, FIGS. 7(B) and (C)). As a result, if user registration for service 1 is not possible, the user can be notified of services for which user registration is possible.

[0099] In this way, in this embodiment, in the user registration process for service 1, the user can conveniently know whether or not he or she can also register for other services 2 to 4.

[0100] Furthermore, according to this embodiment, if the address and surname of the given name entered on the input screen W1 match the address and surname of the given name included in the registered specific user information, and if user registration is not performed because the specific user information is already registered, the name included in the specific user information is displayed on the display unit 240 (YES in S240 of FIG. 8, S250, FIG. 7(B)). That is, if the address and surname of the cause user match the address and surname entered on the input screen W1, the name of the cause user is notified to the user performing the user registration process. If the address and surname of the cause user match the address and surname entered on the input screen W1, the cause user is considered to be a family member living with the user performing the user registration process. Furthermore, it is considered that the user performing the user registration process is unable to register because the family member living with the user has registered first. In this case, it is considered appropriate to inform the user performing the user registration process that the family member living with the user has registered first. This allows the user to know that he or she does not need to register as a user and can use the service together with family members living with him or her.

[0101] Furthermore, according to this embodiment, the weight of the email address is set to "0" in the weight table WT (FIG. 2). That is, in this embodiment, the registration possibility suggestion value EV is determined regardless of whether the email address entered on the input screen W1 matches the email address included in the registered user information. As a result, the possibility suggestion image RS does not change regardless of what email address is entered in the input field TB1 on the input screen W1. As a result, it is possible to prevent the unauthorized leakage of registered email addresses.

[0102] As can be seen from the above explanation, the serial number in this embodiment is an example of device identification information, the user information of the causative user is an example of specific user information, the multifunction device 100 in this embodiment is an example of a device, the management database DBs is an example of a storage unit, and the email address is an example of a specific item.

[0103] B. Variations (1) In the user registration process of the above embodiment, a registration condition is that the serial number, email address, address and surname combination, etc., entered on the input screen W1 do not match the information contained in the registered user information. Alternatively, consider a case where, for example, a user first registers user information including a device serial number, unrelated to the service, and then separately registers for use of the target service using a registered user account. In this case, the registration condition for registering for use of the target service is that the user information, such as the serial number, entered on the input screen matches the information contained in the registered user information. In this case, information on multiple items entered on the input screen may be compared with information on multiple items contained in the registered user information, and a registration possibility suggestion value may be determined that indicates a higher likelihood of registration as the number of matching items increases.

[0104] (2) In the user registration process of the above embodiment, the registration possibility suggestion value EV indicates a larger value when the registration possibility suggestion value is lower. For this reason, in S145 of the above embodiment, a weight sum WA that is a candidate for the registration possibility suggestion value EV is calculated by adding a weight for each matching item. Alternatively, for example, the registration possibility suggestion value EV may be determined to indicate a larger value when the registration possibility suggestion value is higher. In this case, in S145 of the above embodiment, a candidate for the registration possibility suggestion value EV may be calculated by subtracting a weight from an initial value (e.g., 100) for each matching item.

[0105] (3) In the above embodiment, the weight of the email address is set to "0," so that the email address is not taken into consideration when calculating the registration possibility suggestion value EV. Alternatively, when calculating the registration possibility suggestion value EV, processing related to the email address may simply not be performed, such as determining whether the input email address matches.

[0106] Furthermore, the items not taken into consideration when calculating the registration possibility suggestion value EV are not limited to email addresses. Other items among the multiple items input on the input screen W1, such as addresses, may not be taken into consideration when calculating the registration possibility suggestion value EV. Furthermore, if the multiple items input on the input screen W1 include a mobile phone number, the mobile phone number may not be taken into consideration when calculating the registration possibility suggestion value EV. In general, personal information that is likely to be different for each user, such as email addresses and mobile phone numbers, may not be taken into consideration when calculating the registration possibility suggestion value EV.

[0107] In another example, if both the address and the address are matched or if the weight sum WA is 25 or greater, the weight sum WA for the email address may be adjusted to indicate a low likelihood of registration, such as when the inputter is presumed not to be a fraudulent individual. The value 35 indicates a one-level increase in the likelihood of registration when the possibility suggestion image RS in the above-described embodiment is displayed in a three-level display. Alternatively, the weight for the email address match may be added only when a weight is added due to a match of input elements other than the email address. In this case, if the weight sum WA for the match of input elements other than the email address is 0, the weight for the email address is not added. However, if there are other matched items, the weight of the email address is added to the weight sum WA along with the other matched items. This makes it impossible to determine whether the previous input element is a matched item, making it more difficult to obtain email addresses fraudulently. For security reasons, the weight sum WA may not be calculated immediately after each input element is completed, but may be calculated at a later time to prevent fraudulent individuals from identifying matched items.

[0108] (4) In the above embodiment, the possibility suggestion image RS indicates the registration possibility suggestion value EV by the longitudinal length of the rod-shaped portion BR. The possibility suggestion image RS may take various forms. For example, the possibility suggestion image RS may be an image of a numerical value indicating the registration possibility suggestion value EV, a text image expressing the level of the registration possibility suggestion value EV in words, or an image indicating the registration possibility suggestion value EV by the number of marks such as stars or circles. Furthermore, the possibility suggestion image RS may indicate the registration possibility suggestion value EV by color. For example, the possibility suggestion image RS may be an image indicating red when the possibility of not being able to register is high, yellow when the possibility is medium, and blue when the possibility is low.

[0109] (5) The registration conditions (conditions 1 to 3) in the above embodiment are merely examples and are not limited to these. For example, if multiple users are allowed to be registered in association with one device for one service, condition 1 of the above registration conditions may be omitted. In this case, the serial number of the device does not need to be taken into consideration when calculating the registration possibility suggestion value EV. Alternatively, instead of conditions 2 and 3, the registration condition may include that at least one of the items of information, excluding the device serial number, among the multiple items of information entered on the input screen W1 is different from (does not completely match) the registered user information.

[0110] (6) In the above embodiment, each time input is completed for one input element on the input screen W1, steps S12 to S20 in Fig. 3 are repeated. Alternatively, for example, in the input state, steps S12 to S20 in Fig. 3 may be repeated at predetermined time intervals (for example, every 10 seconds) to update the possibility suggestion image RS.

[0111] (7) In the above embodiment, the registration possibility suggestion value EV is determined using weights set for each of the multiple items entered on the input screen W1. However, the present invention is not limited to this, and the registration possibility suggestion value EV may be determined based on the number of items among the multiple items in which the information entered on the input screen W1 matches the registered information, without using weights.

[0112] (8) In the registration failure notification screen of the above embodiment, when the name notification condition is met, the registration failure notification screen W3 of FIG. 7(B) includes a display IF3 of the name of the causative user who caused the registration condition not to be met. Alternatively, the registration failure notification screen W3 may include a display of only the first name of the causative user, excluding the surname. Alternatively, the display of the name of the causative user may be omitted, and when the registration failure notification screen is displayed, the registration failure notification screen W4 of FIG. 7(C) may always be displayed.

[0113] (9) In the above embodiment, the registration failure notification screens W3 and W4 include registered service information IF1 and unregistered service information IF2 (FIGS. 7B and 7C). Alternatively, the registration failure notification screens W3 and W4 may not include either or both of the registered service information IF1 and the unregistered service information IF2.

[0114] (10) In the above embodiment, server 300 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.

[0115] (11) In the above embodiment, the user registration process is performed by one server 300. Alternatively, the initial registration process and the subsequent registration process may be performed by two or more servers that can communicate with each other, with each server sharing the roles. For example, the user registration process may be performed by a first server that communicates with the terminal device 200 and provides various screens W1 to W4 to the terminal device 200, in cooperation with a second server that manages registration information such as the user table UT and the device table DT.

[0116] (12) In the above embodiments, some of the configurations realized by hardware may be replaced by software, and conversely, some or all of the configurations realized by software may be replaced by hardware.

[0117] 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]

[0118] 1000...system, 100...multifunction peripheral, 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, 200...terminal device, 210...CPU, 220...volatile storage device, 230...nonvolatile storage device, 240...display unit, 250...operation unit, 280...communication IF, 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, PGp, PGs...computer program, RS...possibility suggestion image, ST...compatible service table, UT...user table, W1...input screen, W2...registration completion screen, W3, W4...registration impossible notification screen, WT...weight table

Claims

1. 1. A communication system comprising: a terminal device used by a user, the terminal device having a display unit that displays a screen and an operation unit that receives user operations; a server communicably connected to the terminal device, the server including a storage unit for storing registered user information, the user information including a plurality of items of information; Equipped with an input screen display process for displaying an input screen including a plurality of input elements for inputting information of the plurality of items on the display unit of the terminal device; a condition determination process for determining whether a registration condition is satisfied based on the input information of the plurality of items when a registration instruction is input with the information of the plurality of items already input into the plurality of input elements, the condition determination process including a condition determined based on a comparison between the input information of the plurality of items and the information of the plurality of items included in registered user information; a registration process in which, when the registration conditions are satisfied, the user information including the input information of the plurality of items is stored in the storage unit to perform user registration, and when the registration conditions are not satisfied, the user registration is not performed; an input information acquisition process for acquiring information of one or more items that have been input into the plurality of input elements while the input screen is displayed on the display unit so that information can be input into the plurality of input elements and while the input screen is in an input state before the registration instruction is input; a suggestion value determination process that determines a suggestion value that suggests the possibility of user registration being permitted based on information about the one or more items acquired in the input information acquisition process in the input state, the suggestion value being determined based on a comparison between the information about the one or more items and information about the plurality of items included in the registered user information; a suggestion information display process for displaying suggestion information based on the suggestion value on the input screen being displayed on the display unit in the input state; A communication system that performs

2. 2. The communication system of claim 1, In the inputting state, each time an input is completed for one of the plurality of input elements, the input information acquisition process acquires information of the one or more items, The suggestion value determination process updates the suggestion value using the acquired information of the one or more items, The suggestion information display process updates the suggestion information displayed on the input screen based on the updated suggestion value.

3. 2. The communication system of claim 1, The suggestion value determination process includes: A communication system that compares the information of the one or more items that have been entered with the information of the multiple items included in the registered user information for each item, and determines the suggested value by adding or subtracting a specific value for each matching item.

4. 4. The communication system according to claim 3, The suggestion value determination process determines the suggestion value using weights set for each of the plurality of items.

5. 4. The communication system according to claim 3, the user registration is performed for a service provided using the device, the plurality of items include device identification information that identifies the device; The suggestion value determination process determines the suggestion value indicating the lowest possibility of registration when the input device identification information matches the device identification information associated with registered user information.

6. 4. The communication system according to claim 3, the user registration is performed for each of a plurality of services provided using the device; the registered user information is registered in association with a service that is a target of the user registration among the plurality of services; the registration conditions for each of the plurality of services include a condition that at least a portion of the information of the plurality of items that has been input does not match at least a portion of the information of the plurality of items that has been registered and is included in the user information; The communication system further comprises: A communication system in which, in the registration process for a specific service, if the user registration for the specific service is not performed because at least a portion of the information of the multiple items that has been entered matches at least a portion of the multiple items included in the registered specific user information associated with the specific service, a first service display process is executed to display other services from the multiple services that are associated with the specific user information on the display unit.

7. 4. The communication system according to claim 3, the user registration is performed for each of a plurality of services provided using the device; the registered user information is registered in association with a service that is a target of the user registration among the plurality of services; the registration conditions for each of the plurality of services include a condition that at least a portion of the information of the plurality of items that has been input does not match at least a portion of the information of the plurality of items that has been registered and is included in the user information; The communication system further comprises: A communication system in which, in the registration process for a specific service, if the user registration for the specific service is not performed because at least a portion of the information of the multiple items that has been entered matches at least a portion of the multiple items included in the registered specific user information associated with the specific service, a second service display process is executed to display services among the multiple services that are not associated with the specific user information on the display unit.

8. 4. The communication system according to claim 3, The plurality of items include a user's address and a user's name; The communication system further comprises: A communication system that executes a name display process to display the name included in the specific user information on the display unit when the input address and the surname of the given name match the address and the surname of the given name included in registered specific user information, and when the user registration is not performed because the specific user information has already been registered.

9. 4. The communication system according to claim 3, The suggestion value determination process includes: A communication system that determines the suggestion value regardless of whether or not information on a specific item that has been input matches information on the specific item that is included in the registered user information.

10. 1. A communication system comprising: A server connected to a terminal device used by a user, the server having a display unit that displays a screen and an operation unit that receives user operations, the server being communicably connected to the terminal device, a storage unit for storing registered user information, the user information including a plurality of items of information; A control unit; Equipped with The control unit an input screen display process for displaying an input screen including a plurality of input elements for inputting information of the plurality of items on the display unit of the terminal device; a condition determination process for determining whether a registration condition is satisfied based on the input information of the plurality of items when a registration instruction is acquired in which the information of the plurality of items has already been input into the plurality of input elements, the condition determination process including a condition determined based on a comparison between the input information of the plurality of items and the information of the plurality of items included in registered user information; a registration process in which, when the registration conditions are satisfied, the user information including the input information of the plurality of items is stored in the storage unit to perform user registration, and when the registration conditions are not satisfied, the user registration is not performed; an input information acquisition process for acquiring information of one or more items that have been input into the plurality of input elements while the input screen is displayed on the display unit so that information can be input into the plurality of input elements and while the input screen is in an input state before the registration instruction is input; a suggestion value determination process that determines a suggestion value that suggests the possibility of user registration being permitted based on information about the one or more items acquired in the input information acquisition process in the input state, the suggestion value being determined based on a comparison between the information about the one or more items and information about the plurality of items included in the registered user information; a suggestion information display process for displaying suggestion information based on the suggestion value on the input screen being displayed on the display unit in the input state; The server that runs

11. A computer program for a server, comprising: The server A terminal device used by a user, the terminal device having a display unit that displays a screen and an operation unit that receives user operations, the terminal device being communicably connected to the terminal device; a storage unit for storing registered user information, the user information including information on a plurality of items; The computer program comprises: an input screen display function for displaying an input screen including a plurality of input elements for inputting information of the plurality of items on the display unit of the terminal device; a condition determination function that, when acquiring a registration instruction in which information on the plurality of items has already been entered into the plurality of input elements, determines whether a registration condition is satisfied based on the information on the plurality of items that has already been entered, and the registration condition includes a condition determined based on a comparison between the information on the plurality of items that has already been entered and the information on the plurality of items included in registered user information; a registration function that, when the registration conditions are satisfied, performs user registration by storing user information including the input information of the plurality of items in the storage unit, and does not perform user registration when the registration conditions are not satisfied; an input information acquisition function that acquires information of one or more items that have been input into the plurality of input elements while the input screen is displayed on the display unit so that information can be input into the plurality of input elements and in an input state before the registration instruction is input; a suggestion value determination function that determines a suggestion value that indicates the possibility of user registration being permitted based on information on the one or more items acquired by the input information acquisition function in the input state, the suggestion value being determined based on a comparison between the information on the one or more items and information on the plurality of items included in the registered user information; a suggestion information display function that displays suggestion information based on the suggestion value on the input screen being displayed on the display unit in the input state; A computer program that enables a computer to realize the above.

Images