Service providing program, server, service system, and service providing method

Abstract

To make it possible to efficiently perform exchange of a device being a contract object in a service directed to devices.SOLUTION: A server provides a service directed to devices. The server acquires use information of a contract device contracting with the service, from the contract device. The use information represents use situations of the contract device. The server generates service utilization information representing utilization situations of the service on the basis of the acquired use information. The server acquires an exchange request. The exchange request requests to change the contract device from a first device currently contracting with the service to a second device different from the first device. In response to acquisition of the exchange request, the server changes the contract device from the first device to the second device.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a technology for providing services for devices such as printers.

Background Art

[0002] Patent Document 1 discloses a server that provides various services for devices. This server provides a consumable maintenance fixed - amount service. The consumable maintenance fixed - amount service provides consumables (such as toner and paper) used in the devices registered in the service at a fixed amount during the maintenance period.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There may be a need to replace the device subject to the service contract with another new device. In this case, it is desired that the replacement of the device subject to the contract be performed efficiently. One aspect of the present disclosure aims to efficiently perform the replacement of the device subject to the contract in a service for devices.

Means for Solving the Problems

[0005] The service - providing program in one aspect of the present disclosure is a program (computer program) executable by a computer provided in a server. The service - providing program is a program for providing a service for devices.

[0006] The service - providing program causes the computer to execute a first acquisition process, a generation process, a second acquisition process, and a change process. The first acquisition process acquires usage information of a contracted device from the contracted device. The contracted device is a device that has contracted for the service. The usage information indicates the usage status of the contracted device.

[0007] The generation process generates service usage information indicating the usage status of the service based on the usage information acquired by the first acquisition process. The second acquisition process acquires an exchange request. The exchange request requests to change the contracted device from a first device, which is a device currently contracted for the service, to a second device, which is a device different from the first device.

[0008] The change process changes the contracted device from the first device to the second device in response to the exchange request being acquired by the second acquisition process. In a server in which such a service provision program is executed, while the contracted device is the first device, the usage information of the first device is acquired, and when the contracted device is changed to the second device, the acquired usage information is changed to the second device. On the other hand, the service usage information is not generated individually for each device, but is generated in units of the contracted service. That is, the generation process does not generate separate service usage information for each device every time the device for which the service is contracted is changed, but switches the usage information to be referred to from the contracted device before the change to the contracted device after the change. Therefore, before the change, the service usage information is updated as the usage information of the contracted device before the change is acquired, and after the change is that the service usage information generated until immediately before is further updated according to the usage information of the contracted device after the change. Therefore, an increase in resources (i.e., an increase in information to be generated and managed) associated with a change in the device for which the contract is made is suppressed, and it becomes possible to efficiently change the device for which the contract is made.

[0009] In another aspect of the present disclosure, a server configured to execute the above service provision program may be provided. In yet another aspect of the present disclosure, a service system may be provided that includes a server on which the above-described service providing program is executed, a first device, a second device, and an information processing device. In this case, the information processing device may execute reception processing for receiving an instruction operation for instructing to change a contract device from the first device to the second device, and transmission processing for transmitting an exchange request to the server in response to the instruction operation being received by the reception processing.

[0010] In yet another aspect of the present disclosure, a service providing method used in a server on which the above-described service providing program is executed may be provided.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0012] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. [1. Embodiment] (1-1) Overview of the Device Service System The device service system 1 of the present embodiment shown in FIG. 1 includes a service server 10, a first device 41, a second device 42, and an information processing apparatus 60. The device service system 1 provides a device management service. More specifically, in the device service system 1, the service server 10 provides the device management service for devices that have contracted for the device management service (hereinafter referred to as "contracted devices"). The contract (registration) of the device management service is performed individually for each device.

[0013] Devices that can contract for the device management service are, for example, devices having a printing function such as a printer or a multifunction device in the present embodiment. The printing function is a function of acquiring data of an image to be printed and printing the image indicated by the data on a sheet-like recording medium. Both the first device 41 and the second device 42 have a printing function. Therefore, both the first device 41 and the second device 42 can contract for the device management service.

[0014] In the present embodiment, as an example, it is assumed that the first device 41 has already contracted for the device management service and the second device 42 has not contracted for the device management service. The device management service currently contracted (registered) for the first device 41 is hereinafter referred to as the first contract. Note that there may be one or more other devices other than the first and second devices 41 and 42, and second contracts, third contracts, etc. may be individually concluded for those one or more other devices. In the present embodiment, it is assumed that the device that is the subject of the first contract is exchanged from the current first device 41 to the second device 42.

[0015] The service server 10 can communicate with each of the first device 41, the second device 42, and the information processing apparatus 60. In the present embodiment, the first device 41, the second device 42, and the information processing apparatus 60 are connected to the communication network 100. The communication network 100 is connected to a WAN (Wide Area Network) 150. The service server 10 is connected to the WAN 150.

[0016] Therefore, in the present embodiment, the service server 10 can communicate with each of the first device 41, the second device 42, and the information processing apparatus 60 via the WAN 150 and the communication network 100.

[0017] Note that the service server 10 may be connected to the communication network 100. The information processing apparatus 60 may be connected to the WAN 150 and may be connected to the communication network 100 via the WAN 150. The information processing apparatus 60 may be able to communicate with the service server 10 without going through the WAN 150. In a situation where the first device 41 has a contract with the device management service, the second device 42 may not be connected to the communication network 100.

[0018] The communication network 100 may include a wired network or may include a wireless network. The WAN 150 may be any network. The WAN 150 of the present embodiment is, for example, the Internet configured to perform communication according to the TCP / IP protocol.

[0019] (1-2) Outline of the device management service The specific content of the device management service provided by the service server 10, and the procedures and processing flow when contracting for the device management service will be outlined.

[0020] The device management service of this embodiment is, for example, a service targeting particularly consumables in a contracted device and includes a so-called subscription service (flat-rate service).

[0021] That is, in this embodiment, when a service is contracted, a service-exclusive cartridge is provided as a cartridge containing a colorant (toner or ink) used for printing. The contracted user installs the exclusive cartridge in the contracted device and uses the contracted device. The exclusive cartridge can be used only during the contract period and becomes unusable when the service is cancelled.

[0022] The consideration for the service for the contracted user is set on a monthly basis. That is, for each contract, printing can be done at a fixed rate up to a specified number of sheets (for example, M sheets per month). If the number of printed sheets exceeds the specified number within a month, an additional charge is levied. For example, a fixed amount is additionally charged for each N sheets exceeding the specified number. If the actual number of printed sheets in a month is less than the specified number, the surplus can be carried over to the next month.

[0023] The service server 10 periodically collects and stores various data from the contracted devices. That is, when a contract is concluded for a certain device, the service server 10 instructs the contracted device to periodically notify the notification target information. The instruction includes the type of the notification target information to be notified and the notification interval. Examples of the notification target information include the number of printed sheets, the remaining amount of consumables, the firmware version, and various status information. The instructed contracted device periodically transmits the specified notification target information to the service server 10 at the specified notification interval.

[0024] In addition, the service server 10 can issue an action instruction to the contracted device. Examples of the action instruction include an instruction to change various setting values used in the contracted device and an instruction to execute printing. When the contracted device receives an action instruction from the service server 10, it executes the process according to the instruction.

[0025] The remaining amount of the consumable (here, the remaining amount of the toner in the dedicated cartridge) is periodically monitored by the service server 10 as described above. When the remaining amount falls below a certain level, a new dedicated cartridge is automatically ordered and shipped to the contractor.

[0026] The procedure for contracting a desired device with the device management service is generally as follows. First, the user accesses a web page provided by a server program 21 (to be described later) in the service server 10 by using a terminal program 62b (to be described later) in the information processing apparatus 60 (that is, by using a web browser in this example). Specifically, for example, the user accesses a login page. Then, starting from the login page, the user creates (registers) an account in the service server 10. By registering the account, the user becomes eligible to contract with the device management service.

[0027] The user who has registered an account registers the device for which the user desires to receive the service in the service server 10. At this point, the device is registered in the service server 10 as a contractable device but has not yet been contracted. The registration of the device is also performed by accessing the web page of the service server 10 by using the terminal program 62b of the information processing apparatus 60.

[0028] The user who has registered the device performs a contract procedure for the registered device. Specifically, the user accesses a contract web page in the service server 10 and enters the necessary information. Examples of the necessary information include a contract plan (e.g., monthly fee), the address of the delivery destination of the consumables, and information necessary for payment (e.g., credit card information).

[0029] Note that, in order to contract for the device management service, the device to be contracted must meet the contractable conditions. The contractable conditions may be defined in any way. The contractable conditions may be defined based on, for example, the specifications of the device. The contractable conditions may vary for each contract plan. When a device that does not meet the contractable conditions attempts to be contracted, the service server 10 issues an error notification as described later.

[0030] When the contract procedure is completed, a contract for the registered device as the contract target is formally concluded. The contractor can access and check various information related to the contract, such as the contract content and the usage status of the contracted device, on the Web page for contractors in the service server 10. The Web page for contractors includes the service main screen 71 described later. The contractor can check, for example, starting from the service main screen 71, their own account, the registered printers of the account, the service contract status for each registered printer, and the usage status for each contracted device. Examples of the checkable usage status include the number of printed sheets and the remaining amount of consumables. Also, starting from the service main screen 71, it is possible to add registered devices, change contracted devices, change contract plans, cancel contracts, etc.

[0031] Note that the service server 10 has payment information indicating whether the payment of the necessary consideration is properly made for each contract. (1-3) Configuration of the Service Server As shown in FIG. 1, the service server 10 includes a control unit 11, a storage unit 12, and a communication I / F 13. "I / F" is an abbreviation for interface.

[0032] The control unit 11 has, for example, a CPU. The storage unit 12 has semiconductor memories such as ROM, RAM, NVRAM, and flash memory. That is, the service server 10 of the present embodiment includes a microcomputer including a CPU and a semiconductor memory.

[0033] The control unit 11 realizes various functions by executing the programs stored in the storage unit 12. In the present embodiment, the storage unit 12 corresponds to a non-transitory computer-readable storage medium storing the programs. Note that the various functions realized by the control unit 11 are not limited to being realized by the execution of programs, and a part or all of them may be realized using one or a plurality of hardware.

[0034] The communication I / F 13 is an interface for communicating with other devices. The communication I / F 13 may support, for example, a wired LAN, a wireless LAN, and other various communication methods. In the present embodiment, the communication I / F 13 is connected to the WAN 150.

[0035] The storage unit 12 stores a server program 21 and a database 22. The database 22 is managed by the server program 21. The server program 21 has a function of providing a device management service. That is, various functions related to the device management service are basically realized by the server program 21. In the following description, the entity that executes the program (for example, the control unit 11 in the service server 10) may be described simply by the program name or software name. For example, the description "the server program 21 is" may, in detail, mean "the control unit 11 that executes the server program 21 is".

[0036] (1-4) Configuration of the First and Second Devices The first and second devices 41 and 42 will be specifically described with reference to FIG. 2A. In the present embodiment, the first and second devices 41 and 42 have functional blocks with common functions, although they are different in detail. FIG. 2A shows an excerpt of the functional blocks with common functions.

[0037] As shown in FIG. 2A, each of the first and second devices 41 and 42 includes a control unit 51, a storage unit 52, an input I / F 53, a display I / F 54, a communication I / F 55, and a printing unit 56.

[0038] The control unit 51 has, for example, a CPU. The storage unit 52 has semiconductor memories such as a ROM, a RAM, a NVRAM, and a flash memory. That is, each of the first and second devices 41 and 42 of the present embodiment includes a microcomputer including a CPU and a semiconductor memory. Various software and data are stored in the storage unit 52. The control unit 51 realizes various functions by executing various programs stored in the storage unit 52. Note that the various functions realized by the control unit 51 are not limited to being realized by program execution (i.e., software processing), and a part or all of them may be realized using one or a plurality of hardware.

[0039] The input I / F 53 has an input device for receiving various input operations by a user. The input device included in the input I / F 53 may include, for example, an operation switch (not shown) and a touch panel (not shown). The display I / F 54 has a display device capable of displaying an image, such as a liquid crystal display or an organic EL display. The communication I / F 55 is an I / F for connecting the first and second devices 41 and 42 to the communication network 100. The printing unit 56 realizes the above-described printing function. In the present embodiment, each of the first and second devices 41 and 42 can communicate with the service server 10 using, for example, the communication protocol of XMPP (Extensible Messaging and Presence Protocol).

[0040]

[0041] (1-5) Configuration of Information Processing Apparatus The information processing apparatus 60 is various information processing apparatuses such as a smartphone, a tablet terminal, a mobile personal computer, and a desktop personal computer.

[0042] As shown in FIG. 2B, the information processing apparatus 60 includes a control unit 61, a storage unit 62, an input I / F 63, a display I / F 64, and a communication I / F 65. The control unit 61 has, for example, a CPU. The storage unit 62 has semiconductor memories such as a ROM, a RAM, a NVRAM, and a flash memory. That is, the information processing apparatus 60 of the present embodiment includes a microcomputer including a CPU and a semiconductor memory.

[0043] The control unit 61 realizes various functions by executing a program stored in the storage unit 62. In the present embodiment, the storage unit 62 corresponds to a non-transitory computer-readable storage medium storing a program. Note that the various functions realized by the control unit 61 are not limited to being realized by program execution, and a part or all of them may be realized using one or a plurality of hardware.

[0044] The input I / F 63 has an input device for receiving various input operations by the user. The input device included in the input I / F 63 includes, for example, a touch panel. The display I / F 64 has a display device capable of displaying an image, such as a liquid crystal display or an organic EL display. The communication I / F 65 is an I / F for connecting the information processing apparatus 60 to the communication network 100.

[0045] The storage unit 62 stores an OS 62a and a terminal program 62b. The OS 62a and the terminal program 62b are installed in the computer system. The terminal program 62b is used to enjoy the device management service. The contractor of the first contract can access the service server 10 to obtain various types of information related to the first contract. One of the tools for obtaining various types of information is the terminal program 62b. The terminal program 62b has a function of obtaining various information related to the first contract by communicating with the service server 10 (specifically, communicating with the server program 21) and displaying it on the display I / F 64. In addition, the terminal program 62b has a function of transmitting various information, requests, etc. input by a user such as an administrator to the server program 21 via the input I / F 63.

[0046] In this embodiment, the terminal program 62b has, for example, the function of a web browser. On the other hand, the server program 21 of the service server 10 has, for example, the function of a web server. Therefore, the terminal program 62b of this embodiment communicates with the server program 21 of the service server 10 using, for example, the communication protocol of HTTP or HTTPS.

[0047] (1-6) Data tables managed in the database Next, the data table group created in the database 22 of the service server 10 for each contract in the device management service will be described with reference to FIG. 3. FIG. 3 illustrates the data table group related to the first contract. When the first contract is concluded, a data table group as shown in FIG. 3 is constructed in the database 22. as shown.

[0048] As shown in FIG. 3, the data table group includes an account table 30, a contract management table 31, a contract information table 32, a total print count related table 33, a device information table 34, and a device print count table 35.

[0049] As illustrated in FIG. 3, the account table 30 includes basic information about the contractor, such as the user ID and the account type. The user ID identifies the contractor. The account type is set to any one of a plurality of types. In the present embodiment, for example, any one of "customer", "administrator", and "system" is set as the account type. Generally, when a user who receives a service registers an account, the account type is set to "customer". Note that the account type corresponds to an example of the contractor information in the present disclosure.

[0050] The device information table 34 is created individually for each registered device, that is, every time a device is registered. The device information table 34 is associated with the account table 30. As illustrated in FIG. 3, the device information table 34 includes, in addition to the user ID, a device information record regarding the registered device. As illustrated in FIG. 3, the device information record includes, for example, a device ID, a device valid / invalid setting, and various other information regarding the registered device. The device ID identifies the device. The device valid / invalid setting indicates whether the device has a contract for the service. When the device has a contract for the service, the device valid / invalid setting is set to "valid". Note that the device information table 34 shown in FIG. 3 includes a device information record of the first device 41 that is the current contract device of the first contract, that is, the first device information record 34a. In this device information table 34, the user ID corresponds to an example of the first user information and the second user information in the present disclosure, and the device ID corresponds to an example of the first identification information in the present disclosure.

[0051] The contract management table 31 includes information regarding the status of the services contracted by the users who have registered accounts. The contract management table 31 is associated with the device information table 34 of the devices that are under contract for the service.

[0052] As illustrated in FIG. 3, the contract information table 32 includes various types of information indicating the specific content of the services under contract. The contract information table 32 is linked to the contract management table 31. The device print count table 35 is created individually for each registered device. The device print count table 35 is linked to the device information table of the corresponding registered device. As illustrated in FIG. 3, the device print count table 35 includes, in addition to the user ID, device print count records related to the registered device. The device print count records include, for example, a device ID, the print count for the current month, etc., as illustrated in FIG. 3. The print count for the current month is the number of prints executed in the current month (the current contract unit month) on the corresponding registered device. The device print count table 35 is linked to the device information table 34 and the total print count related table 33. Note that the device print count table 35 shown in FIG. 3 includes the device print count record of the first device 41, which is the current contract device of the first contract, i.e., the first device print count record 35a. The device information table 34 and the device print count table 35 correspond to an example of usage information in the present disclosure.

[0053] The total print count related table 33 is not generated individually for each registered device, but one common table is generated for each contract. As illustrated in FIG. 3, the total print count related table 33 includes the print count for the current month, the excess count for the current month, etc. The print count for the current month is the total number of prints executed on the contract devices of the contract during the current month. The excess count for the current month is the excess count when the print count for the current month exceeds the contract count. The total print count related table 33 is linked to the contract information table. The total print count related table 33 is further linked to the device print count table 35 (specifically, the device print count record of the current contract device) corresponding to the contract device. Note that the total print count related table 33 corresponds to an example of service usage information in the present disclosure.

[0054] (1-7) Overview of Contract Target Device Replacement For example, a need may arise to replace the current contract device with another device, such as when the contract device malfunctions or when one wants to use another device that has a function not available in the contract device. In this case, in the present embodiment, after registering another device, a process of switching the contract device from the current device to another device is performed.

[0055] At this time, instead of separately creating new Tables 30 to 35 shown in FIG. 3 for another device, some tables are continuously referenced. Specifically, as illustrated in FIG. 4, for example, when the contract device is exchanged from the first device 41 to the second device 42, what is newly generated is the second device information record 34b in the device information table 34 and the second device print count record 35b in the device print count table 35. That is, in the device information table 34, a new second device information record 34b is generated separately from the existing first device information record 34a. In the device print count table 35, a new second device print count record 35b is generated separately from the existing first device print count record 35a. After the exchange of the contract device, in the device information table 34, the second device information record 34b is referenced instead of the first device information record 34a, and in the device print count table 35, the second device print count record 35b is referenced instead of the first device print count record 35a. The second device information record 34b indicates the information of the second device 42, which is the new contract device of the first contract. The types of information included in the second device information record 34b are basically the same as those of the first device information record 34a. The second device print count record 35b includes the monthly print count, which is the number of prints executed in the current month (the current contract unit month) on the second device. The types of information included in the second device print count record 35b are basically the same as those of the first device print count record 35a. For several other tables including the total print count related table 33, instead of being separately generated for the second device 42, the tables that have already been generated and referenced before the exchange are continuously referenced.

[0056] 4, the first device information record 34a in the device information table 34 is released from the link with the contract management table 31, and is linked with a new second device information record 34b. Also, the first device print count record 35a in the device print count table 35 is released from the link with the total print count association table, and is linked with a new second device print count record 35b. However, for the month in which the replacement was made, the total print count association table 33 is updated with reference to both the first device print count record 35a and the second device print count record 35b so that the billing for that month is performed correctly. The first device information record 34a and the first device print count record 35a may be left without being deleted, although they will no longer be referenced.

[0057] The device ID of the second device 42 included in the second device information record 34b corresponds to an example of second identification information in the present disclosure. The first device print count record 35a corresponds to an example of first usage information in the present disclosure, and the second device print count record 35b corresponds to an example of second usage information in the present disclosure.

[0058] The server program 21 calculates the number of printed sheets for each contract month (i.e., the total number of printed sheets related table When updating the record 35a (updating the record 35b), if the contracted device is replaced from the first device 41 to the second device 42 in the middle of the contract month, the first device print count record 35a of the first device 41 before the replacement (hereinafter also referred to as the "old device") is referenced for the number of pages printed before the replacement, and the second device print count record 35b of the second device 42 after the replacement (hereinafter also referred to as the "new device") is referenced for the number of pages printed after the replacement.

[0059] (1-8) Processing related to the provision of services The process executed by the service server 10 to provide the device management service, that is, the process executed according to the server program 21, will be described with reference to FIGS. 5 to 7. FIG.

[0060] (1-8-1) Regular Notification Response Processing The control unit 11 of the service server 10 periodically executes the regular notification response processing shown in FIG. 5 at the aforementioned notification interval. The regular notification response processing is included in the server program 21.

[0061] When starting the regular notification response processing, the control unit 11 acquires notification target information from the contracted device in S110. In S120, based on the notification target information acquired in S110, the control unit 11 updates the device information table 34 (specifically, the device information record 34a of the current contracted device) and the device print count table 35 (specifically, the device print count record 35a of the current contracted device).

[0062] In S130, the control unit 11 updates the total print count related table 33 by reflecting the update result of S120 in the total print count related table 33. For example, when the monthly print count in the device print count table 35 is updated from 30 to 40 (i.e., increased by 10) by the process of S120, 10 is added to the current monthly print count in the total print count related table 33. By repeatedly executing such regular notification response processing periodically, the device information table 34, the device print count table 35, and the total print count related table 33 are updated.

[0063] Also, when the contracted device is changed from the first device 41 to the second device 42, as described above, in the device information table 34, the second device information record 34b is generated while leaving the first device information record 34a, and in the device print count table 35, the second device print count record 35b is generated while leaving the first device print count record 35a. Then, the update of the total print count related table 33 after the change is performed with reference to the second device print count record 35b.

[0064] As a result, the monthly printed sheet count in the monthly print sheet count related table 33 for the billing month (corresponding to an example of a certain period in the present disclosure) in which the contract device was replaced is calculated as follows. That is, for the monthly printed sheet count from the start of the billing month to the time of replacement, it is calculated (updated) by referring to the monthly printed sheet count in the first device printed sheet count record 35a. On the other hand, after the replacement, for the monthly printed sheet count from the time of replacement to the end of the billing month, it is calculated (updated by addition) with reference to the monthly printed sheet count in the second device printed sheet count record 35b with respect to the monthly printed sheet count at the time of replacement.

[0065] (1-8-2) Processing related to contract device replacement Next, the processing executed by the device service system 1 at the time of replacing the contract device will be described with reference to FIGS. 6 and 7. Here, it will be described assuming that the contract device of the first contract is replaced from the current first device (old device) 41 to the second device (new device) 42.

[0066] In order to replace the contract device with a new device, the user first starts the terminal program 62b (for example, a Web browser in the present embodiment) in the information processing device 60 to log in to the service server 10, access the service server 10, and display a login screen on the display I / F 64 of the information processing device 60. Then, a login operation including inputting necessary items is performed.

[0067] Thereby, the terminal program 62b transmits a login request to the server program 21 together with the information input in the login operation (S11). The server program 21 that has received the login request from the terminal program 62b accepts the login request (S30). Thereby, the user's login is accepted.

[0068] The server program 21 that has received the user's login transmits the screen information of the service main screen 71 (see FIG. 8) corresponding to the logged-in user to the terminal program 62b (S31). The terminal program 62b that has received this screen information displays the service main screen 71 on the display I / F 64 based on the screen information (S12).

[0069] When the service main screen 71 is displayed, the user performs a device addition request operation to register a new device. Specifically, the user taps or clicks the addition button 71a displayed on the service main screen 71.

[0070] When the terminal program 62b receives the device addition request operation, it executes a device registration request process (S13). Specifically, first, a device registration screen (not shown) for receiving the registration of a new device is displayed. Then, the user's new device registration operation starting from that device registration screen is received. The new device registration operation includes operations on the new device. When a new device is selected by the new device registration operation and a registration instruction is given by the user, the terminal program 62b requests the server program 21 to register the new device.

[0071] The server program 21 that has received this request executes a new device registration process for registering the new device in the device management service (S32). This process includes generating a new second device information record 34b and a second device print count record 35b corresponding to the new device. At this point, the new device has not yet been registered as a contract device of the first contract, and the contract device of the first contract is still the old device. When the new device is registered, as shown in FIG. 4, the second device information record 34b of the new device is associated with the account table 30.

[0072] When the server program 21 registers a new device, it transmits the screen information of the service main screen 71 corresponding to the logged-in user to the terminal program 62b (S33). The terminal program 62b that has received this screen information displays the service main screen 71 on the display I / F 64 based on the screen information (S14). Although not shown in FIG. 8, on the service main screen 71 displayed here, in addition to the old device that is the current contracted device, the new device is also displayed as a list of registered devices.

[0073] When the service main screen 71 is displayed in S14, the user performs an exchange request operation to replace the contracted device. Specifically, for example, the user taps or clicks the exchange button 71b displayed on the service main screen 71. When the terminal program 62b receives the exchange request operation, it executes a device exchange request process (S15). Specifically, it displays an exchange reception screen (not shown) for selecting the device to be exchanged. Then, starting from the exchange reception screen, it receives the old device selection operation and the new device selection operation by the user. As a result, the terminal program 62b recognizes the new device and the old device. The terminal program 62b further receives the exchange decision operation by the user. The terminal program 62b that has received the exchange decision operation sends an exchange request to the server program 21. That is, it requests the server program 21 to change the contracted device from the current old device to the new device. That is, it requests the server program 21 to change the contracted device from the current old device to the new device.

[0074] The server program 21 that has received the exchange request from the terminal program 62b executes an exchange request reception process (S34). For example, it grasps the new device and the old device. Then, it verifies the validity of the exchange (S35).

[0075] Specifically, for example, it checks whether the account type of the logged-in user is "customer" by referring to the account table 30 of the logged-in user. If the account type is "customer", it tentatively determines that the validity is valid, and if it is other than "customer", it determines that the validity is invalid.

[0076] For example, to determine whether the old device and the new device are the same, refer to the device IDs in the respective device information records 34a and 34b. If the device IDs match each other, it is determined that the old device and the new device are the same. In this case, it is determined that there is no validity. If the device IDs do not match each other, it is determined that the old device and the new device are not the same. In this case, it is determined that there is validity. In this way, the validity of several verification items is verified.

[0077] Based on the verification result, the server program 21 that has performed the validity verification determines whether the replacement is valid (S36). If all the verification results in S35 are valid, the server program 21 determines that it is valid. On the other hand, if there is a verification item determined to be invalid, it is determined that it is not valid.

[0078] If it is determined that the replacement is not valid (S36: NO), the server program 21 sends an error notification to the terminal program 62b (S37). The terminal program 62b that has received this error notification notifies that the replacement has been rejected via the display I / F 64. If it is determined that the replacement is valid (S36: YES), the server program 21 acquires the table information (S38). That is, it acquires the data table groups of the old device and the new device (see FIG. 4) stored in the database 22. Then, the acquired data table groups are verified (S39). The purpose of this verification is the same as the verification in S35, which is to confirm whether the replacement can be allowed.

[0079] In S39, for example, it is determined whether both the old device and the new device are associated with the same logged-in user. This determination is made, for example, by checking whether both the first device information record 34a of the old device and the second device information record 34b of the new device are associated with the same account table 30. That is, it is checked whether both the first device information record 34a and the second device information record 34b belong to the same logged-in user. When each device information record 34a, 34b is associated with the same account table 30 (that is, when the user IDs of each device information record 34a, 34b are the same), it is determined that the verification is OK. On the other hand, when each device information record 34a, 34b is not associated with the same account table 30 (that is, when the user IDs of each device information record 34a, 34b are different), it is determined that the verification is NG.

[0080] Also, for example, in S39, it is determined whether the service fee has been properly paid by the logged-in user. This determination may be made, for example, based on the above-mentioned payment information managed by the service server 10. For example, if the payment has not been properly made, such as there is an arrearage, the verification is set to NG. On the other hand, if the payment has been properly made, it is determined that the verification is OK.

[0081] Also, for example, in S39, it is determined whether the old device and the new device are each valid. Specifically, the setting of " Device valid / invalid" in the device information records 34a, 34b of each device is checked. Then, when it is set to "valid", it is determined that the verification is OK, and when it is set to "invalid", it is determined that the verification is NG.

[0082] Also, for example, in S39, it is determined whether the new and old devices are associated with the contract. Specifically, the contract status (valid or invalid) set for each registered device in the contract management table 31 is checked. If it is set to valid, it is determined that it is associated with the contract, and if it is set to invalid, it is determined that it is not associated with the contract. And when the old device is set to valid, it is determined that the old device is currently associated with the contract, and the verification is considered OK. On the other hand, when the old device is set to invalid, it is determined that the verification fails. For the new device, conversely, when the contract status is set to invalid, the verification is considered OK, and when the contract status is set to valid, the verification is considered NG.

[0083] Also, for example, in S39, it is determined whether the new device meets the aforementioned contractable conditions. That is, it is determined whether the new device can continue to meet the contract conditions under which the old device is currently contracted (in other words, the compatibility of the contract). If the new device meets the contractable conditions, the verification is considered OK, and if it does not meet the contractable conditions, the verification is considered NG.

[0084] In this way, after verifying the necessary items, the server program 21 determines whether the verification was successful (S40). Specifically, if all the verifications performed in S39 are verified OK, it is determined that the verification is successful. On the other hand, if there is an item with verification NG in S39, it is determined that the verification fails.

[0085] When it is determined that the verification fails (S40: NO), the server program 21 sends an error notification to the terminal program 62b (S41). The terminal program 62b that receives this error notification notifies, via the display I / F64, that the verification has failed (that is, the replacement has been rejected). When it is determined that the verification is successful (S40: YES), the server program 21 invalidates the old device (S42 in FIG. 7). Specifically, the server program 21 sets the device valid / invalid setting to "invalid" in the first device information record 34a in the device information table 34.

[0086] The server program 21 that invalidates the old device further sets the service mode to off and cancels the notification registration for the old device (S43). These are performed directly on the old device. That is, for a device that satisfies the contractable conditions, a service mode indicating whether or not it is receiving a service is set, and this is set to off. Also, since the above-mentioned periodic notification is no longer necessary for the old device, this is cancelled so that no periodic notification is sent from the old device.

[0087] Then, the server program 21 checks the service subscription status of the new device (S44). That is, it checks whether the device that is about to contract now has already subscribed (contracted) to another service different from the device management service. Then, based on the check result, it determines whether the device that is about to contract now has already subscribed to another service that is in a competing relationship with the device management service. The competing relationship includes a relationship in which at least part of the functions of the mutual services overlap. For example, if there is another service specialized only in the automatic ordering of consumables, which is one function of the device management service, that other service is in a competing relationship with the device management service.

[0088] If the new service has already subscribed to another service in a competing relationship (S45: YES), the server program 21 sends an error notification to the terminal program 62b (S46). The terminal program 62b that receives this error notification notifies that the replacement has been rejected via the display I / F64. If the new device has not subscribed to another service in a competing relationship (S45: NO), the server program 21 activates the new device (S47). Specifically, the server program 21 sets the device valid / invalid setting to "valid" in the second device information record 34b in the device information table 34.

[0089] The server program 21 that activates the new device replaces the contract of the old device with that of the new device (S48). That is, the contract device is changed here. Specifically, as described with reference to FIG. 4, the second device information record 34b is associated as a device information record belonging to the device information table 34, and the second device print count record 35b is associated as a device print count record belonging to the device print count table 35. Then, the association between the tables is changed as shown in <After replacement> in FIG. 4. As a result, when updating the total print count related table 33, the record referred to in the device print count table 35 switches from the first device print count record 35a to the second device print count record 35b.

[0090] The server program 21 that has changed the contract device acquires initial information (current information such as the print count) from the new device (S49) and reflects it in the second device print count record 35b of the new device.

[0091] Furthermore, the server program 21 sets the service mode to on and sets notification registration for the new device (S50). As a result, notification target information is periodically transmitted from the new device.

[0092] In this embodiment, the server program 21 corresponds to an example of the service providing program in the present disclosure. The process of S110 corresponds to an example of the first acquisition process in the present disclosure. The process of S120 corresponds to an example of the storage process in the present disclosure. The process of S130 corresponds to an example of the generation process in the present disclosure. The process of S34 corresponds to an example of the second acquisition process in the present disclosure. The processes of S35, S36, S38 to S40, S44, and S45 correspond to examples of the determination process in the present disclosure. The process of S48 corresponds to an example of the change process in the present disclosure.

[0093] [2. Other Embodiments] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0094] (1) The verification items for the validity of the exchange in S35 are not limited to the items exemplified in the above embodiment. In addition to the exemplified items, or instead of at least a part of the exemplified items, other verification items may be provided.

[0095] (2) The verification items for the data table group in S39 are not limited to the items exemplified in the above embodiment. In addition to the exemplified items, or instead of at least a part of the exemplified items, other verification items may be provided.

[0096] (3) The functions of the server program 21 in the service server 10 may be physically configured by a plurality of different servers. The functions of the server program 21 may be shared by a plurality of servers. Also, the service server 10 may be provided as a so-called virtual server.

[0097] (4) The plurality of functions of one component in the above embodiment may be realized by a plurality of components, or one function of one component may be realized by a plurality of components. Also, the plurality of functions of a plurality of components may be realized by one component, or one function realized by a plurality of components may be realized by one component. Also, a part of the configuration of the above embodiment may be omitted. Also, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of other above embodiments. That is, it may be realized by one component, or one function realized by a plurality of components may be realized by one component. Also, a part of the configuration of the above embodiment may be omitted. Also, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of other above embodiments.

Explanation of Reference Numerals

[0098] 1…Device service system, 10…Service server, 11, 61…Control unit, 12, 62…Memory unit, 21…Server program, 22…Database, 30…Account table, 31…Contract management table, 32…Contract information table, 33…Total print count related table, 34…Device information table, 35…Device print count table, 41…First device, 42…Second device, 60…Information processing device, 62b…Terminal program, 71…Service main screen, 71a…Add button, 71b…Replace button.

Claims

1. A service providing program executable by a computer included in a server for providing a service for a device, the computer is caused to, perform a first acquisition process of repeatedly acquiring usage information indicating the usage status of a contract device, which is the device that has contracted for the service, from the contract device, perform a generation process of generating service usage information indicating the usage status of the service based on the usage information acquired by the first acquisition process, perform a second acquisition process of acquiring an exchange request, where the exchange request requests to change the contract device from a first device, which is the device that has contracted for the current service, to a second device, which is a device different from the first device, perform a change process of changing the contract device from the first device to the second device in response to the exchange request being acquired by the second acquisition process, and execute, the change process includes switching the usage information that is the reference destination when generating the service usage information in the generation process from first usage information, which is the usage information of the first device, to second usage information, which is the usage information of the second device, the generation process generates the service usage information based on the first usage information acquired by the first acquisition process before the execution of the change process, and generates the service usage information based on the service usage information generated until the execution of the change process and the second usage information acquired by the first acquisition process after the execution of the change process after the execution of the change process, service providing program.

2. The service providing program according to claim 1, the server includes a storage unit in which the usage information and the service usage information are stored, the service providing program further causes the computer to, A storage process for storing the usage information obtained by the first acquisition process in the storage unit, the storage process for updating the usage information stored in the storage unit based on the obtained usage information in response to the acquisition of the usage information, to execute, The generation process generates the service usage information with reference to the usage information stored in the storage unit. Service providing program.

3. The service providing program according to claim 2, Before the exchange request is obtained by the second acquisition process, the storage process stores the first usage information in the storage unit, and after the exchange request is obtained by the second acquisition process, the storage process stores the second usage information in the storage unit. Service providing program.

4. The service providing program according to claim 3, In response to the contract device being changed from the first device to the second device by the change process, the storage process stores the second usage information separately while leaving the first usage information in the storage unit. Service providing program.

5. The service providing program according to claim 4, Regarding the service usage information in a certain period including the timing when the contract device is changed from the first device to the second device by the change process, In the period from the start of the certain period to the timing, the service usage information is generated based on the usage status of the first device based on the first usage information stored in the storage unit, In the period from the timing to the end of the certain period, the service usage information is generated based on the service usage information generated up to the timing and the usage status of the second device based on the second usage information stored in the storage unit after the timing. Service provision program.

6. The service provision program according to any one of Claims 1 to 5, further causing the computer to execute a determination process of determining whether a changeable condition under which the change process can be executed is satisfied in response to the acquisition of the exchange request by the second acquisition process, and the change process is executed in response to the determination by the determination process that the changeable condition is satisfied. Service provision program.

7. The service provision program according to Claim 6, wherein the server has contractor information indicating the type of the contractor who has contracted the contract device for the service, and the changeable condition includes that the type indicated by the contractor information is any one of one or more specific types among a plurality of types. Service provision program.

8. The service provision program according to Claim 6 or Claim 7, wherein the server has unique first identification information indicating the first device and unique second identification information indicating the second device, and the changeable condition includes that the second identification information is different from the first identification information. Service provision program.

9. The service provision program according to any one of Claims 6 to 8, wherein the server has first user information indicating the user of the first device and second user information indicating the user of the second device, and The changeable conditions include that the first user information and the second user information each indicate the same user. Service provision program.

10. A service provision program according to any one of Claims 6 to 9, wherein the server has payment information indicating whether payment for the service contracted by the contract device is being properly made, and the changeable conditions include that the payment information indicates that the payment for the consideration is being properly made. Service provision program.

11. A service provision program according to any one of Claims 6 to 10, for the service contracted by the first device, a device satisfying predetermined contractable conditions can contract, and the changeable conditions include that the second device satisfies the contractable conditions. Service provision program.

12. A service provision program according to any one of Claims 6 to 11, wherein the changeable conditions include that the second device is not contracted with another service in a competitive relationship with the service contracted by the first device, and the competitive relationship includes a relationship in which at least part of the functions of the service and the functions of the other service overlap. Service provision program.

13. A control unit capable of providing a service for a device, a communication unit capable of communicating with a contract device that is the device contracted with the service, and comprising: wherein the control unit A first acquisition process that repeatedly acquires usage information indicating the usage status of the contract device from the contract device, A generation process that generates service usage information indicating the usage status of the service based on the usage information acquired by the first acquisition process, A second acquisition process for acquiring an exchange request, where the exchange request requests to change the contract device from a first device, which is the device currently contracted for the service, to a second device, which is a device different from the first device, A change process that changes the contract device from the first device to the second device in response to the exchange request being acquired by the second acquisition process, Execute, The change process includes switching the usage information that is the reference destination when generating the service usage information in the generation process from first usage information, which is the usage information of the first device, to second usage information, which is the usage information of the second device, Before the execution of the change process, the generation process generates the service usage information based on the first usage information acquired by the first acquisition process. After the change process is executed, the service usage information is generated based on the service usage information generated until the execution of the change process and the second usage information acquired by the first acquisition process after the execution of the change process, Server.

14. Comprising a server, a first device, a second device, and an information processing device, The server is, A control unit capable of providing a service for a contract device that is a contracted device, A communication unit capable of communicating with the contract device, Comprising, The control unit is, A first acquisition process that repeatedly acquires usage information indicating the usage status of the contract device from the contract device, A generation process for generating service usage information indicating the usage status of the service based on the usage information obtained by the first acquisition process; A second acquisition process for acquiring an exchange request from the information processing device, where the exchange request requests to change the contract device from the first device, which is the device currently contracted for the service, to a second device, which is a device different from the first device; A change process for changing the contract device from the first device to the second device in response to the exchange request being acquired by the second acquisition process; Execute, The change process includes switching the usage information that is the reference destination when generating the service usage information in the generation process from first usage information that is the usage information of the first device to second usage information that is the usage information of the second device; Before the execution of the change process, the generation process generates the service usage information based on the first usage information acquired by the first acquisition process. After the change process is executed, the service usage information is generated based on the service usage information generated until the execution of the change process and the second usage information acquired by the first acquisition process after the execution of the change process; The information processing device, A reception process for receiving an instruction operation for instructing to change the contract device from the first device to the second device; A transmission process for transmitting the exchange request to the server in response to the instruction operation being received by the reception process; A service system that executes.

15. A service providing method for providing a service for a contract device, which is executed by a server configured to be communicable with the contract device, which is a contracted device, via a communication network, A first acquisition step of repeatedly acquiring, from the contract device via the communication, usage information indicating the usage status of the contract device; A generation step of generating service usage information indicating the usage status of the service based on the usage information acquired in the first acquisition step; A second acquisition step of acquiring an exchange request, wherein the exchange request requests to change the contract device from a first device, which is the device currently contracted with the service, to a second device, which is a device different from the first device; A change step of changing the contract device from the first device to the second device in response to the exchange request being acquired in the second acquisition step; comprising; In the change step, the server switches the reference usage information for generating the service usage information in the generation step from first usage information, which is the usage information of the first device, to second usage information, which is the usage information of the second device; In the generation step, before the change step, the server generates the service usage information based on the first usage information acquired in the first acquisition step, and after the change step, the server generates the service usage information based on the service usage information generated before the change step and the second usage information acquired in the first acquisition step after the change step; Service providing method.

Images