JP7134772B2 - ELECTRONIC DEVICE, ELECTRONIC DEVICE CONTROL METHOD, INFORMATION PROCESSING SYSTEM AND PROGRAM - Google Patents

Description

The present invention relates to a technology for transmitting information on an electronic device to a service management server that can communicate with a service providing server that provides services.

2. Description of the Related Art Log information such as user usage information and history information obtained in a multifunction peripheral (MFP), and status information indicating the state of the MFP (for example, remaining ink information) are beginning to be utilized in various services. For example, it has been proposed to provide a new service according to the state of the MFP by transmitting status information to a server with the consent of the user and analyzing the status information on the server side. Further, a service has been proposed in which a server side refers to log information and gives a privilege to a user who uses the system frequently.

Japanese Patent Laid-Open No. 2002-200001 describes a technique of centrally managing the status of all services by providing a relay device that manages the status of service licenses and the registration status of services. Then, it is described that data is sent from the MFP to the relay device, and the data is collected by the relay device.

JP 2016-45679 A

However, in Patent Literature 1, data collection is performed without distinguishing between the data used in the service of the service providing apparatus and simple log data. Therefore, data collection is performed even when the service is not available.

An object of the present invention is to enable appropriate data to be transmitted from an electronic device in accordance with the status of service usage registration.

An electronic device according to an aspect of the present invention is an electronic device capable of communicating with a management server capable of transmitting information to a plurality of service providing servers, wherein the electronic device instructs permission to transmit information to the management server. display means for displaying a screen for acceptance; storage means for storing permission status information received via the screen and indicating whether or not a user has permitted transmission of information from the electronic device to the management server; first transmission means for periodically or irregularly transmitting the first information of the electronic device to the management server on condition that the permission status information stored in the means indicates the permission setting; and the permission status information. indicates a permission setting and receives a notification from the management server indicating that information transmission is possible, second information different from the first information of the electronic device is sent to the management server and second transmitting means for transmitting periodically or irregularly.

According to the present invention, appropriate data is transmitted from the electronic device according to the status of service usage registration.

The block diagram of an information processing system. Block diagram of MFP. Block diagram of this service management server. 4 is a block diagram of a service providing server; FIG. FIG. 2 is an overall relationship diagram among the MFP, the service management server, and each service providing server; 4 is a sequence diagram for registering an MFP with a service management server; FIG. FIG. 4 is a sequence diagram of transmission of status information; FIG. 10 is a sequence diagram for deleting the registration of the MFP from the service management server;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. It should be noted that the following embodiments do not limit the present invention, and not all combinations of features described in the embodiments are essential for the solution of the present invention. In addition, the same configuration will be described by attaching the same reference numerals.

<<Embodiment 1>>
<System configuration>
FIG. 1 is a configuration diagram showing the overall configuration of an information processing system. The information processing system includes MFP 100 , service management server 200 , service providing server group 400 , and communication network 300 . The service providing server group 400 is a general term for service providing servers that provide each service. In the example of FIG. 1, the service providing server group 400 has a service A providing server 420 that provides service A, a service B providing server 430 that provides service B, and a service C providing server 440 that provides service C.

<Overview of the system>
An outline of the processing performed by this system will be explained. First, an example of the services provided by this system will be described. An example of the service is a service that gives points to the user according to log information such as usage information and history information of the user in MFP 100 . More specifically, the log information is information that stores events occurring in the MFP 100, such as error occurrence status, number of prints, number of prints, and the like.

Examples of other services include services corresponding to status information indicating the state of MFP 100 . For example, an automatic delivery service for MFP 100 consumables such as ink and toner can be cited. The automatic delivery service automatically orders and delivers consumables when the remaining amount of consumables falls below a certain level. In this case, the status information is identification information for identifying the consumable and information indicating the remaining amount of the corresponding consumable.

Examples of other services include content printing services. In the content printing service, MFP 100 prints content such as a user's photo or content such as a coloring template provided by a service providing server. In this case, the status information is information indicating the state of MFP 100 and the print result.

These log information and status information can be said to be information indicating the state of the device of MFP 100 . Alternatively, it can be said that the information relates to the state in which the user uses MFP 100 . These are collectively called device provision information. Device provision information is hereinafter simply referred to as device information. The services described above are only examples and are not intended to be limiting. Any service may be used as long as the service providing server uses the device information of the MFP 100 . Also, the device information is not limited to the above example.

1, MFP 100, service management server 200, and service providing server group 400 are connected via communication network 300. FIG. However, in this embodiment, the MFP 100 transmits and receives information to and from the service management server 200 . Each service providing server of the service providing server group 400 transmits and receives information to and from the service management server 200 . That is, the MFP 100 does not directly transmit and receive information to and from each service providing server of the service providing server group 400 . Moreover, the network 300 is specifically the Internet. For example, MFP 100 is connected to a wireless LAN via an external access point, and is further connected to the Internet by a router function of the external access point (that is, when the external access point is a wireless LAN router). Therefore, MFP 100 and service management server 200 are connected via the Internet.

In this embodiment, by providing the service management server 200, for example, the information of the MFP 100 necessary for various services can be collected by the service management server 200. FIG. Since the service management server 200 exchanges information with the service providing server that provides various services, the MFP 100 does not need to directly exchange information with the service providing server.

In order to provide the above services, it is first necessary to obtain permission from the user. This is because device information such as log information and status information of MFP 100 is provided to the outside. Furthermore, in addition to permitting provision of device information to the outside, service usage registration is separately performed between the user and the service providing server through, for example, a web page. These series of processes are generally required for each service.

In this embodiment, the steps required to use the service are divided into two steps. The first stage is a process of obtaining permission from the user to transmit the device information to the outside. In other words, as a permission common to all services, a permission for transmitting device information to the outside is obtained. At this time, a permission common to all services is obtained from the user. The second stage is the process of performing registration specific to each service.

In this embodiment, the information transmitted from the MFP 100 to the service management server 200 is divided into two stages and transmitted. The first stage is a step in which MFP 100 transmits log information on the condition that permission for transmission of device information to the outside is obtained from the user. In this embodiment, the user obtains a common permission for all services. Log information is sent on the condition that this common permission setting is made. After that, registration processing of the device (MFP 100) with the service management server 200 is performed. The second stage is a step in which MFP 100 transmits status information to service management server 200 according to the content of the notification received from service management server 200 . The notification from service management server 200 is received as a response to device (MFP 100) registration processing, a response to an inquiry as to whether status information can be transmitted, or a response to transmission of status information.

As described above, the device information transmitted from MFP 100 to service management server 200 includes log information and status information. Among these, the log information is information that is used regardless of the service usage registration of the service providing server. On the other hand, the status information is information that is used when the user is registered to use the service of the service providing server. In this embodiment, the MFP 100 manages information indicating a common license status (hereinafter referred to as "license status information") regarding provision of device information to the outside. Then, if the permission status information is a value indicating the permission setting, the log information is first transmitted from MFP 100 to service management server 200 . On the other hand, the status information is transmitted from MFP 100 to service management server 200 when the content of the notification from service management server 200 indicates that transmission of the status information is “permitted”. For example, when the service management server 200 can confirm the service usage registration between the user who uses the MFP 100 and the service providing server, the service management server 200 notifies the MFP 100 of information indicating that transmission is “permitted”. MFP 100 starts transmitting status information in response to this notification. Such processing can prevent MFP 100 from transmitting unnecessary information.

Transmission of information from the service management server 200 to each service providing server included in the service providing server group 400 is performed when the use condition of each service is satisfied. The usage conditions include, for example, that service usage registration processing is performed between the user and each service providing server. When the service usage conditions are satisfied, each service providing server receives information (part of the device information) necessary for providing the service from the service management server 200 and provides the service. Each communication is controlled through HTTP, XMPP, or the like. As for the protocol, other protocols may be used.

<Block diagram>
FIG. 2 is a block diagram showing a schematic configuration example of the MFP 100 according to this embodiment. MFP 100 is a type of information processing apparatus. Also, MFP 100 is a type of electronic device. The MFP 100 of this embodiment has information processing functions such as generation, storage, and transmission of device information including log information and status information. It also has an image forming function of forming an image on a recording medium by means of a recording control unit 113 and a recording unit 114, which will be described later.

MFP 100 includes CPU 101 , ROM 102 , RAM 103 , image memory 104 , data conversion section 105 , reading control section 106 , reading section 107 , operation display section 108 , LCD 109 , communication control section 110 and resolution conversion section 111 . Further, it includes an encoding/decoding unit 112 , a recording control unit 113 , a recording unit 114 , a USB function control unit 115 , a USB host control unit 116 and a bus 117 .

A CPU 101 is a system control unit and controls the entire MFP 100 . The ROM 102 is a non-volatile memory that stores fixed data such as a control program executed by the CPU 101, a data table, and an embedded operating system (OS). In this embodiment, each control program stored in the ROM 102 performs software execution control such as scheduling, task switching, and interrupt processing under the control of the built-in OS stored in the ROM 102 . The ROM 102 stores information indicating permission status indicating whether or not to provide the device information to the outside. The RAM 103 is composed of an SRAM (Static Random Access Memory) or the like that requires a backup power supply, and power supply to the RAM 103 is guaranteed by a primary battery (not shown) for data backup. The RAM 103 stores program control variables and the like. The image memory 104 is composed of a DRAM (Dynamic Random Access Memory) or the like, and can accumulate image data. A partial area of the image memory 104 is reserved as a work area for executing software processing. The data conversion unit 105 can convert image data such as page description language (PDL) analysis and CG (computer graphics) expansion of character data.

A reading unit 107 optically reads a document using a CIS image sensor and converts it into an electrical image signal. The reading control unit 106 performs various image processing such as binarization processing and halftone processing on the image signal, and outputs high-definition image data. The method of optically reading the document can be either a sheet reading control method that reads the document with a fixed CIS image sensor or a book reading control method that reads the document fixed on the platen with a moving CIS image sensor. It's okay.

The operation display unit 108 is composed of minimum necessary keys such as a numeric input key, a mode setting key, an enter key, and a cancel key, an LED (light emitting diode), a 7-segment display, and the like. The various keys described above are realized by so-called soft keys displayed on the LCD 109, and can receive operations from the user. When the user does not operate the LCD 109 for a certain period of time, the backlight of the LCD 109 is turned off in order to reduce power consumption.

Communication control unit 110 controls communication between MFP 100 and communication network 300 , connects to an Internet service provider, and communicates various data with service management server 200 . Further, communication control unit 110 can determine whether MFP 100 is connected to the Internet or only to a LAN. Note that the connection between the communication control unit 110 and the communication network 300 is based on a known method such as HTTP or XMPP. A resolution conversion unit 111 performs resolution conversion processing such as mutual conversion between millimeter-based image data and inch-based image data. Note that the resolution conversion unit 111 can also execute enlargement/reduction processing of image data. The encoding/decoding unit 112 performs encoding/decoding processing and enlargement/reduction processing on image data (uncompressed, MH, MR, MMR, JBIG, JPEG, etc.) handled by the MFP 100 . The recording control unit 113 converts the image data to be printed into high-definition image data by performing various image processing such as smoothing processing, recording density correction processing, and color correction, and outputs the data to the recording unit 114 . The recording control unit 113 also plays a role of periodically acquiring the state information data of the recording unit 114 . A recording unit 114 is configured by a laser beam printer, an inkjet printer, or the like, and prints the image data generated by the recording control unit 113 on a recording medium such as paper.

The USB function control unit 115 performs protocol control according to the USB communication standard. The USB host control unit 116 is a control unit for performing communication according to the protocol defined by the USB communication standard. This USB communication standard is a standard for two-way high-speed data communication, and according to this USB communication standard, a plurality of hubs or functions (slaves) can be connected to one host (master). It is defined. That is, the USB host control unit 116 provides host functions in USB communication. Components other than the reading unit 107 and the LCD 109 are interconnected via a bus 117 .

FIG. 3 is a block diagram showing a schematic configuration example of the service management server 200 in this embodiment. The service management server 200 is an information processing device, and includes a CPU 201 , a ROM 202 , a RAM 203 , an internal storage device 204 , an external storage device 205 , an operation section 207 , a display section 208 and a communication section 209 .

The CPU 201 controls the overall operation of the service management server 200 according to programs read from the ROM 202 , the RAM 203 , the internal storage device 204 , or the external storage medium 206 to the external storage device 205 . The ROM 202 stores control programs for the CPU 201 and the like. The RAM 203 temporarily stores programs and various data, and allows the service management server 200 to operate at high speed. The internal storage device 204 stores an operating system, various application programs, various data, and the like. Device information (log information and status information) sent from the MFP 100 is stored in the internal storage device 204 . Device information will be described later. In addition, application software for transmitting and receiving various control commands and data is installed in the internal storage device 204 . The operation unit 207 is an input device such as a keyboard and a mouse, and receives instruction inputs from the operator of the service management server 200 . A display unit 208 provides various displays to the operator. Communication unit 209 is connected to communication network 300 , connects to an Internet service provider, and communicates various data between MFP 100 and each service providing server included in service providing server group 400 . It is assumed that the connection to the communication network 300 is made by a known method such as HTTP or XMPP.

FIG. 4 is a block diagram showing a schematic configuration example of each service providing server included in the service providing server group 400 in this embodiment. Specifically, it is a diagram showing a configuration example of a service A providing server 420, a service B providing server 430, and a service C providing server 440. FIG. Each service providing server includes a CPU 401 , a ROM 402 , a RAM 403 , an internal storage device 404 , an external storage device 405 , an operation section 407 , a display section 408 and a communication section 409 .

Configurations other than the internal storage device 404 and the communication unit 409 are the same as the configuration of the service management server 200 in FIG. 3, so description thereof will be omitted. The internal storage device 404 stores an operating system, various application programs, various data, and the like. Further, in the internal storage device 404, application software and the like for transmitting and receiving various control commands and data to and from the service management server 200 are installed. The communication unit 409 is connected to the communication network 300 and performs connection to the Internet service provider and communication of various data with the service management server 200 .

<Description of system functions>
FIG. 5 is a diagram showing the relationship of the entire system including the service providing servers of the MFP 100, service management server 200, and service providing server group 400 in this embodiment. MFP 100 and service management server 200 also include functional block diagrams.

The MFP 100 includes a permission setting management section 130 , a processing section 140 , a notification section 150 and a management server registration management section 160 . The processing section 140 includes a management server registration processing section 141 and a device information transmission section 142 . The device information transmitter 142 includes a log information transmitter 143 and a status information transmitter 144 . The CPU 101 of the MFP 100 functions as each part shown in FIG. 5 by reading out the program stored in the ROM 102 to the RAM 103 and executing it.

The permission setting management unit 130 can manage permission status information indicating whether the user has given permission to transmit device information. The permission setting management unit 130 has a non-volatile memory that stores permission status information. The permission setting management unit 130 manages the permission status information using three values: "0: not set", "1: permission set", and "2: permission canceled". Device information includes, for example, log information and status information of MFP 100, as described above. The permission status information is permission status information common to the services provided by each service providing server of the service providing server group 400 . The license setting management section 130 can manage the license status information even when the communication in the communication network 300 is not valid, that is, even in the offline state.

The processing unit 140 performs processing for transmitting device information to the service management server 200 when the common permission status information managed by the permission setting management unit 130 indicates permission setting. The device information transmission unit 142 has a function of transmitting device information to the service management server 200 . In this embodiment, the device information transmission section 142 includes a log information transmission section 143 and a status information transmission section 144 in order to transmit information in two stages. The log information transmission unit 143 is a first information transmission unit that transmits first information (log information) that is transmitted when the common permission status information managed by the permission setting management unit 130 indicates permission setting. The log information transmission unit 143 sends the log information to the service management server 200 at an arbitrary timing, periodically or Send irregularly. The status information transmission unit 144 transmits the second information (status information) that is transmitted when the service management server 200 notifies that a common permission setting is made and status information can be transmitted. It is a second information transmission unit.

The management server registration processing unit 141 registers the MFP 100 with the service management server 200 when the permission status information managed by the permission setting management unit 130 indicates permission setting, that is, when the user performs common permission setting. process. The management server registration processing unit 141 transmits a registration request to the service management server 200 and receives notification of the response.

Management server registration management unit 160 manages the registration state of MFP 100 in service management server 200 . The management server registration management unit 160 changes the registration state according to the contents of the notification received by the management server registration processing unit 141 . The management server registration manager 160 has a non-volatile memory that stores the registration state. The management server registration management unit 160 sets the registration status to one of "0: unregistered", "1: registered (cannot be sent)", "2: registered (can be sent)", and "3: deletion not completed". It is managed with 4 values. The management server registration management unit 160 also stores authentication information acquired from the service management server 200 when receiving a registration completion notification from the service management server 200 in the non-volatile memory. In addition, in this embodiment, an example in which the registration state is managed by four values is shown, but the present invention is not limited to this. For example, the management server registration management unit 160 may separately manage the registration status and transmission availability. Also, if it has been registered, it may be considered that transmission is possible. These can be appropriately designed according to the characteristics of the service.

The registration completion notification received from the service management server 200 in response to the registration request includes whether or not the status information can be transmitted. When the received notification indicates that the status information can be transmitted, the management server registration management unit 160 manages the registration status as "2: registered (transmittable)". When the received notification indicates that the transmission of the status information is "not allowed", the management server registration management unit 160 manages the registration status as "1: registered (not sent)".

The status information transmission unit 144 confirms that the registration status of the management server registration management unit 160 is "2: registered (transmittable)" and that the license status information of the license setting management unit 130 is "1: license setting". The status information is transmitted to the service management server 200 on condition that the status information is indicated. After the condition is satisfied, the status information transmission unit 144 periodically or irregularly transmits the status information to the service management server 200 at any timing.

Although the log information and the status information are collected in the service management server 200 in this embodiment, the log information and the status information may be collected in another server. In addition, collection of log information and collection of status information may be performed by separate data collection servers.

The notification unit 150 notifies the user of the permission setting. For example, the notification unit 150 displays on the operation display unit 108 a notification prompting permission setting. If the common permission status information managed by the permission setting management unit 130 is a value indicating the permission setting, the notification unit 150 does not send the notification again. For example, when using the first service, if the user inputs permission status information to change the value indicating the permission setting, when using the second service different from the first service, It is not necessary to input the permission setting again. Therefore, when the permission status information managed by the permission setting management unit 130 indicates permission setting, the notification unit 150 does not issue a notification prompting permission setting.

Thus, the MFP 100 has a device transmission function of transmitting device information to the service management server 200 . The device transmission function is enabled/disabled according to the license status information managed by the license setting manager 130 and the registration status managed by the management server registration manager 160 . Enabling the device transmission feature is done in two stages. First, when the transmission function is activated under the condition that the common permission information indicates the permission setting, the transmission function of the first information (log information) is activated. After that, when it is notified that the transmission of the second information (status information) is "possible" and the registration state is updated, the transmission function of the second information (status information) is activated. The device information including the first information and the second information is device information including all information required by each service.

The common license status information is managed by the license setting management unit 130 inside the MFP 100, and the user can input the license settings without communicating with the service management server 200 or the like. That is, in this embodiment, common permission status information can be set offline. The common permission status information can be changed by the user's input through the operation display unit 108 of the MFP 100, for example. Alternatively, settings can be changed through a PC application or smartphone application that can communicate with MFP 100 .

Next, the service management server 200 will be explained. The service management server 200 includes a registered device management section 220 , a device information collection section 230 , a service cooperation management section 240 and an information transfer section 250 . Device information collector 230 includes log information collector 231 and status information collector 232 . The CPU 201 of the service management server 200 reads programs stored in the ROM 202 into the RAM 203 and executes them, thereby functioning as the units shown in FIG. The service management server 200 is configured to be able to transmit at least part of the information included in the device information to each service providing server that provides services.

Registered device management unit 220 manages MFP 100 registered in service management server 200 . For example, the registered device manager 220 assigns predetermined identification information to the MFP 100 that has undergone registration processing with the management server registration processor 141 of the MFP 100 and manages the MFP 100 . Further, when notifying MFP 100 of completion of registration, registered device management unit 220 determines whether service use registration has been made with the service providing server. For example, the list managed by the service cooperation management unit 240 is checked, and if the MFP 100 is included in the list, it is detected that the use of the service has been registered. If the service is registered for use, registered device management unit 220 notifies MFP 100 that has requested the registration that the registration is completed and that the status information can be transmitted, as a response to MFP 100 . . If the service is not registered for use, registered device management unit 220 notifies MFP 100 that has requested the registration that the registration has been completed and that the transmission of the status information is "not accepted." . Similarly, when receiving an inquiry as to whether or not status information can be transmitted from MFP 100, registered device management unit 220 determines whether or not status information can be transmitted to MFP 100 in accordance with whether or not the user has been registered for use of the service. to notify. Further, when registered device management section 220 detects that the use of the service has been canceled and that there is no service in use, registered device management section 220 responds to MFP 100 that has transmitted the status information by indicating that the transmission of the status information is "not permitted". to MFP 100.

Device information collection unit 230 collects device information transmitted from MFP 100 managed by registered device management unit 220 . That is, the log information collecting unit 231 collects log information, and the status information collecting unit 232 collects status information. Device information is stored in internal storage device 204 , external storage device 205 , or external storage medium 206 .

The service cooperation management unit 240 cooperates with each service providing server of the service providing server group 400 and the service management server 200 . In the present embodiment, license and registration processing regarding use of the service are performed between the user and the service providing server. This usage permission is a permission different from the common permission setting described above. In other words, it corresponds to a license to use individual services. The service cooperation management unit 240 receives the device identification information of the device (MFP 100) for which use permission and registration processing have been performed from each service providing server, and updates the device list that uses each service.

The information transfer unit 250 transmits device information required for each service to each service providing server of the service providing server group 400 . In the present embodiment, the device information collected by the device information collecting unit 230 is information that covers information necessary for each service provided by each service providing server of the service providing server group 400 . On the other hand, the service providing server does not necessarily use all device information. Therefore, the information transfer unit 250 transfers the information necessary for the target service among the device information to the service providing server.

Next, services provided by each service providing server of the service providing server group 400 will be specifically described. In this embodiment, service providing servers are classified into three types according to the type of service provision.

The service A providing server 420 is a first service providing server that provides a first service. The first service is a service-free service that does not require user registration to receive the service. An example of the first service is a failure/maintenance support service.

Of the device information collected from MFP 100, service management server 200 transfers only the information required for failure and maintenance support service to service A providing server 420 that provides the first service. The device information transferred here includes information necessary for failure and maintenance support, such as consumption information of expendable parts of the MFP 100, ink remaining amount information, and device error information.

The service A providing server 420 provides a user or a serviceman with a report for identifying the cause of failure from the consumption information and error information. In addition, the service A providing server 420 provides the user with countermeasure proposals by, for example, predicting the time of failure and the timing at which maintenance is required.

The service B providing server 430 is a second service providing server that provides a second service. The second service is an external registration type service that requires service registration through another route (for example, on a web page displayed on a PC or smart phone) instead of processing through the MFP 100 . In this type of service, the service management server 200 is notified that the device (MFP 100) has been registered with the service as a result of performing the service license and registration processing 431 together with the device identification information of the device (MFP 100). The service management server 200 manages the device identification information notified from the service B providing server 430 as a service B registered device list. An example of the second service is a point service that gives points according to the user's usage. In this case, in order to receive the point service, the user registers user information and device identification information for identifying MFP 100 used by the user in service B providing server 430 via a website or a registration application. At this time, the user also consents to the usage license of the service B presented by the service B providing server 430 . When the registration is completed, service B providing server 430 that provides the point service transmits to service management server 200 a notice of completion of registration and device identification information for identifying the device (MFP 100). The registered devices notified in this manner are included in the service B registered device list and managed by the service management server 200 . On the other hand, as described above, the user makes permission settings for transmitting device information to the service management server 200 . If the common permission status information managed by the permission setting management unit 130 has been changed to a value indicating permission, it is not necessary to input the setting again.

Of the device information collected from MFP 100 , service management server 200 transfers only the information required for the point service to service B providing server 430 that provides service B. FIG. The device information transferred here includes job information executed by the user, tank information attached, and the like. The service B providing server 430 gives points to the user according to the job information executed by the user and the tank information attached. The user can use the given points for benefits such as discounts on the purchase of ink and media.

The first service (service A) and the second service (service B) described above are services of the type in which the service management server 200 transmits information necessary for the service to each service providing server in a Push type. be. That is, it is a type of service in which information is periodically or irregularly transmitted from the service management server 200 to the service providing server. On the other hand, a third service (service C) described below is a pull-type service that transmits information necessary for the service. That is, it is a type of service in which information is transmitted from the service management server 200 in response to a request from the service providing server.

Service C providing server 440 is a third service providing server that provides a third service. The third service, like the second service, is an external registration type service that requires service registration through a different route than processing through the MFP 100 . However, unlike the second service, in the third service, the service management server 200 is not notified that the service license and registration processing 441 has been performed. The service C providing server 440 requests information from the service management server 200 as necessary, and the service management server 200 transfers necessary information in response to the information request. In this type of service, the service management server 200 cannot manage the service C registration list. Therefore, the service management server 200 transfers information in response to a request from the service C providing server 440. FIG. An example of the third service (service C) is an automatic ink transport service in cooperation with other systems (other servers). In this case, the user registers user information and device identification information for identifying the MFP 100 used by the user on the system that provides the automatic ink transport system. At this time, the user also agrees on the usage license presented by the service C providing server 440 . When registration is completed, the device (MFP 100 ) for which registration is completed is managed by service C providing server 440 . On the other hand, as described above, the user makes permission settings for transmitting device information to the service management server 200 . If the common permission status information managed by the permission setting management unit 130 has been changed to a value indicating permission, it is not necessary to input the setting again.

Service management server 200, which collects device information transmitted from MFP 100, receives a list of target devices and a request for device information from service C providing server 440. FIG. In response to the received request, the service management server 200 transfers to the service C providing server 440 only the information required for the automatic ink transfer service among the collected device information. The device information transferred here is information necessary for the automatic ink transfer service, such as remaining ink amount information.

In the external registration type service, in order to receive the service, both the common license status information managed by the MFP 100 indicating the license setting and the service use license and registration on each service are required. Must be running. If either one is released, the service cannot be received.

<Sequence diagram>
6 and 7 are sequence diagrams when using service B, which is an externally registered Push type service. FIG. 6 is a sequence diagram related to registration processing between MFP 100 and service management server 200 . FIG. 7 is a sequence diagram related to the process of registering for use of service B after the registration process of FIG.

A series of processes shown in the sequences of FIGS. 6 and 7 are executed by each CPU of MFP 100, service management server 200, and service B providing server 430 expanding program codes stored in ROM into RAM and executing them. will be Alternatively, some or all of the functions of the steps in FIG. 6 may be realized by hardware such as an ASIC or an electronic circuit. Note that the symbol "S" in the description of each process means a step in the flowchart.

In S601, the MFP 100 receives an operation start instruction from the user. At this point, the MFP 100 is in the initial state, and is in "licensed state: unset" and "registered state: unregistered". Note that the notation "permission status: not set" means that the permission status is not yet set. The same applies to the registration status. The same applies hereinafter in this specification.

In S602, the MFP 100 displays a permission screen on the operation display unit 108 for permission operation. In S603, the MFP 100 accepts consent input by the user through the consent screen. In step S<b>604 , the MFP 100 changes the status to “permission status: permit setting” and displays a completion screen on the operation display unit 108 . This allows the user to recognize that common permission settings have been completed.

When the status is changed to "permission status: permission setting", the management server registration processing unit 141 of the MFP 100 transmits a registration request to the service management server 200 in S605. The service management server 200 starts registration processing in response to the registration request. In S<b>606 , service management server 200 transmits the registration result to MFP 100 . The example of S606 shows an example in which the registration process has failed for some reason. If the registration fails, the MFP 100 remains in "registration status: unregistered".

The MFP 100 transmits the log information to the service management server 200 in parallel with the registration process of S605 or before or after the registration process of S605. In the present embodiment, log information is transmitted from the MFP 100 to the service management server 200 on condition that the status is changed to "permission status: permission setting". The example of FIG. 6 shows an example of transmitting log information after the registration process. In S<b>607 , the MFP 100 transmits log information to the service management server 200 . In S<b>608 , the MFP 100 receives a response to the log information transmission from the service management server 200 .

In the example of FIG. 6, at the time of S608, the MFP 100 is in a state of "licensed state: licensed setting" and "registered state: unregistered". Therefore, the MFP 100 retries the registration with the service management server 200 in S609. Note that MFP 100 performs retry until the registration is completed. Also, if the status is changed to "license status: license canceled" before registration is completed, MFP 100 stops the registration process. In the example of FIG. 6, it is assumed that the registration process has succeeded in the process of S609. In S<b>610 , service management server 200 transmits a registration completion notice to MFP 100 . MFP 100 changes the registration status of management server registration management unit 160 by referring to the information included in the notification of registration completion. That is, the status is changed to "Registered status: Registered (transmission not permitted)" or "Registration status: Registered (transmittable)".

At this point, the MFP 100 is in "license status: permission set" and "registration status: registered (transmission denied or transmission permitted)". That is, since it is "permission status: permission setting", the log information is continuously transmitted to the service management server 200 in S611, and the response is received in S612.

Here, if the status is “registration status: registered (transmittable)”, the MFP 100 transmits status information usable by each service providing server of the service providing server group 400 to the service management server 200 in S<b>613 . At S614, the response is received. As described above, service management server 200 notifies MFP 100 of "transmittable" when MFP 100 is a device registered for service use with the service providing server. In the example of S613 in FIG. 6, it is assumed that the service management server 200 notifies that the user is "sendable" in response to the user registering for use of another service D. FIG.

Here, the device information transmitted from MFP 100 to service management server 200 includes log information obtained by collecting logs and status information used by a higher-level service providing server. If all the device information is transmitted in the case of “licensed state: licensed setting”, unnecessary information will be transmitted from MFP 100 to service management server 200 . Therefore, in the present embodiment, when the service becomes available with a higher service providing server, the service management server 200 notifies the MFP 100 that the status information can be transmitted. In response to this notification, MFP 100 updates the status to "registered (transmittable)". The MFP 100 transmits the status information to the service management server 200 under the conditions of "permission status: permission setting" and "registration status: registered (transmittable)". Such a configuration can prevent unnecessary information from being transmitted from MFP 100 to service management server 200 .

Further, as described above, the user registers for use of the service through a website or a registration application without going through MFP 100 . Therefore, the MFP 100 cannot determine that the service has been registered between the service providing server and the user. Therefore, the MFP 100 of the present embodiment transmits status information according to whether or not the service management server 200 can confirm the status of service registration between the user of the MFP 100 and the service providing server. As a result, even MFP 100 that cannot confirm the registration status of the service provided by the service providing server can be prevented from transmitting unnecessary information.

Also, the user may cancel the service provided by the service providing server. In this case, the service management server 200 is notified by the service providing server that the service has been unregistered. In response to this, service management server 200 transmits to MFP 100 a notification indicating that transmission of the status information is “not permitted”. In this way, even when the service provided by the service providing server is cancelled, it is possible to prevent unnecessary information from being sent from MFP 100 .

FIG. 7 is a sequence diagram after the process of registering for use of service B. FIG. In the initial state of FIG. 7, the MFP 100 is assumed to be in "license state: permission setting" and "registration state: registered (transmission not permitted)".

In S701, the user performs an operation to start using service B through the terminal. In S702, the user transmits a request to start using service B to service B providing server 430 through the terminal. For example, the user accesses a web page for registering for use of service B using a general terminal having a browser function. The service B providing server 430 that has received the request from the user transmits a service A linking request to the service management server 200 in S703. In S<b>704 , the service management server 200 transmits a service A linking response to the service B providing server 430 . In S705, the service B providing server 430 transmits a service B usage response to the terminal. In S706, the terminal displays a service B utilization start completion screen, and the user recognizes the completion of the procedure.

On the other hand, MFP 100 is in "registration status: registered (transmission not permitted)". In this case, the MFP 100 inquires of the service management server 200 whether or not the status information can be transmitted at an arbitrary timing. This is because the MFP 100 does not know the service registration status. Therefore, in the example of FIG. 7, in S707, the MFP 100 inquires of the service management server 200 whether or not status information can be transmitted. For example, the inquiry is made at arbitrary timing, such as the timing when the MFP 100 is powered on, the timing when a predetermined time has passed, or the timing based on the user's operation. In S<b>708 , service management server 200 transmits a response to the inquiry to MFP 100 . In the example of FIG. 7, the service management server 200 manages that service B has been registered in S704. Therefore, in S<b>708 , the service management server 200 transmits a response indicating “transmittable” to the MFP 100 . Upon receiving this response, MFP 100 changes to "registration status: registered (transmittable)".

As described above, regardless of the registration status, MFP 100 transmits log information if "permission status: permit setting". S709 and S710 are log information transmission and response processing. The MFP 100 transmits the status information to the service management server 200 in S711 in response to "registration status: registered (transmittable)". The MFP 100 receives the response from the service management server 200 in S712. It should be noted that the service management server 200 can include information indicating whether or not the status information can be transmitted in the status information transmission response as shown in S712. MFP 100 can change the registration state in response to this response.

In S<b>713 , the service management server 200 extracts the status information necessary for the service B of the service B providing server 430 and transfers it to the service B providing server 430 . If log information is required for service B, the log information may also be transferred. The service management server 200 receives a response from the service B providing server 430 in S714.

FIG. 8 is a sequence diagram when the user changes the permission status to cancel the common permission settings. In S<b>801 , the MFP 100 accepts the start of the permission canceling operation from the user. In S<b>802 , the MFP 100 displays a consent screen on the operation display unit 108 . In S803, the MFP 100 accepts an input to cancel permission from the user. As a result, the MFP 100 becomes "permission status: canceled setting" and "registration status: deletion incomplete". In S<b>804 , the MFP 100 displays a completion screen on the operation display unit 108 . The user recognizes release completion.

As described above, the transmission of log information and status information is performed on the condition that it is at least "permitted state: permitted setting". Therefore, since the status is "permission status: release setting", the MFP 100 does not transmit log information or status information. In order to prevent inconsistency with the service management server 200, a process of deleting the registration status with the service management server 200 is performed later.

In S<b>805 , the MFP 100 transmits a registration deletion request to the service management server 200 . In the example of FIG. 8, the registration cannot be deleted at the stage of S805 for some reason, and a deletion failure response is sent from the service management server 200 to the MFP 100 at S806. MFP 100 retries until deletion succeeds. In S<b>807 , the MFP 100 transmits another registration deletion request to the service management server 200 . When the deletion is successful, the service management server 200 transmits a notification of successful deletion to the MFP 100 in S808. Upon receiving the notification of successful deletion, the MFP 100 becomes "permission status: canceled setting" and "registration status: unregistered". After that, when the user inputs the common permission setting again, the process returns to the process shown in FIG. 6, and the registration process is performed again. Also, if the status changes again to "permitted status: permitted setting" during the deletion retry, the MFP 100 performs the registration process again after successful registration deletion.

The deletion process shown in FIG. 8 is a sequence diagram for canceling the common permission setting. In such a case, deletion is retried until the deletion is completed by the service management server 200, as shown in S807. This is to prevent inconsistency with the service management server 200 . However, when resetting to the initial state (or a predetermined state), such as initialization processing of the entire MFP 100, the entire device enters reset processing, so retry processing in response to a failure in deregistration is not performed. .

Thus, in this embodiment, the MFP 100 starts log transmission when the user inputs an instruction to set the common permission status information to the permission setting. Also, when the notification from the service management server 200 includes that the transmission of status information is "possible", the MFP 100 starts transmitting the status information used in the service. Further, when the license status information is changed to a value indicating the cancellation setting, the MFP 100 stops log transmission and status transmission, and starts deletion to the registered device management section 220 of the service management server 200 . Then retry the deletion until the deletion is completed.

As described above, in the present embodiment, the MFP 100 does not manage the license for transmitting device information for each service, but manages it as common license status information. Therefore, the user only needs to enter the common permission setting once as a permission procedure for providing information to the outside, and does not need to perform the permission setting procedure again when receiving the provision of other services. Become. As a result, convenience is improved when the user adds a service.

Further, in this embodiment, the data transmitted from the MFP 100 can be made appropriate data according to the status of service usage registration. That is, common permission settings are provided for each service, and log information is transmitted when permission settings are made. Then, the status information is transmitted according to whether or not the status information notified from the service management server 200 can be transmitted. In this way, by controlling to transmit information in two stages, it is possible to prevent unnecessary information from being transmitted.

<<other embodiments>>
In the above-described embodiment, the MFP 100 is described as an example of an electronic device, but the present invention is not limited to this. Any electronic device may be used as long as the electronic device periodically or irregularly transmits information on the state of use or history of use of the electronic device by the user to the server. Alternatively, any electronic device may be used as long as the electronic device periodically or irregularly transmits the status information of the electronic device to the server. In the above-described embodiment, a relatively large device such as the MFP 100 has been described as an example, but electronic devices worn by humans (eg, glasses, watches, etc.) may also be used. Also, the electronic device may be a sensor installed at an arbitrary location. Also, other home appliances (for example, refrigerators, lights, televisions, vacuum cleaners, home speakers) and the like may be used. Also, the electronic device may be mounted on various vehicles such as automobiles, trains, airplanes, and unmanned aerial vehicles.

Furthermore, in the above-described embodiment, the service management server 200 is composed of one information processing device, but it is not limited to this. For example, a plurality of information processing apparatuses may work together to function as the service management server 200 . Although each of the service providing servers 420, 430, and 440 is also composed of one information processing device in the above-described embodiment, the present invention is not limited to this. Each service providing server may be composed of a plurality of information processing devices.

The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in the computer of the system or apparatus reads and executes the program. It can also be realized by processing to It can also be implemented by a circuit (for example, ASIC) that implements one or more functions.

100 MFPs
143 Log information transmission unit 144 Status information transmission unit 200 Service management server

Claims (13)

An electronic device capable of communicating with a management server capable of transmitting information to a plurality of service providing servers,
display means for displaying a screen for accepting an instruction for permission to transmit information from the electronic device to the management server;
storage means for storing permission status information received via the screen and indicating whether or not a user has permitted transmission of information from the electronic device to the management server ;
a first transmission means for periodically or irregularly transmitting the first information of the electronic device to the management server on condition that the permission status information stored in the storage means indicates the permission setting;
second information different from the first information of the electronic device on condition that the permission status information indicates permission setting and that a notification indicating that information transmission is possible is received from the management server; a second transmission means for periodically or irregularly transmitting to the management server;
An electronic device comprising: When the permission status information is changed to the permission status, the electronic device sends a registration request to the management server to register the electronic device as a target device for transmitting information to the service providing server through the management server. Further comprising a third transmission means for transmitting to the server,
2. The electronic device according to claim 1, wherein said notification is received as a response to said registration request. 3. The electronic device according to claim 1, wherein the notification is received as a response to an inquiry from the electronic device to the management server as to whether information can be transmitted. The management server is configured to be able to transmit at least part of the second information to each service providing server that provides services,
4. The notification is sent from the management server when the management server detects that the electronic device is registered for use of the service. or the electronic device according to item 1. 5. The electronic device according to claim 4, wherein the second information is information corresponding to all services of each service providing server. 6. The first information is log information indicating a log of the electronic device, and the second information is status information indicating a state of the electronic device. The electronic device described in . When the permission status information stored in the storage means is changed to information indicating permission cancellation, the first transmission means and the second transmission means transmit the first information and the second information to the management server. 7. The electronic device according to any one of claims 1 to 6, wherein transmission is stopped. When the permission status information stored in the storage means is changed to information indicating permission cancellation, the electronic device registered in the management server as a target device for transmitting information to the service providing server through the management server 8. The electronic device according to any one of claims 1 to 7, further comprising fourth transmission means for transmitting a deletion request for deleting registration of the device to the management server. If the permission status information stored in the storage means is changed to information indicating permission settings before the management server notifies the completion of registration deletion in response to the deletion request, the deletion of the registration is canceled . 9. The method according to claim 8, wherein after the completion is notified, a request is transmitted through the management server to re -register the electronic device with the management server as a target device for transmitting information to the service providing server. electronics. An information processing system comprising the electronic device according to any one of claims 1 to 9, a management server, and a service providing server for providing a service,
The information processing system, wherein the management server has transfer means for extracting information necessary for a service provided by the service providing server from the second information and transferring the extracted information to the service providing server. 11. The service according to claim 10, wherein provision of said service is started on condition that said permission status information indicates permission setting and registration of a user to said service providing server is completed. Information processing system. A control method for an electronic device capable of communicating with a management server capable of transmitting information to a plurality of service providing servers,
a display step of displaying, on a display means of the electronic device, a screen for accepting an instruction for permission to transmit information from the electronic device to the management server;
a writing step of writing permission status information received via the screen and indicating whether or not the user has permitted transmission of information from the electronic device to the management server into a storage means of the electronic device;
a first transmission step of periodically or irregularly transmitting the first information of the electronic device to the management server on condition that the permission status information written in the storage means indicates a permission setting;
second information different from the first information of the electronic device on condition that the permission status information indicates permission setting and that a notification indicating that information transmission is possible is received from the management server; a second transmission step of periodically or irregularly transmitting to the management server;
A control method for an electronic device, comprising: A program for causing a computer to execute the electronic device control method according to claim 12 .

Images