Information processing apparatus, control method, program and support system

Abstract

To provide an information processing apparatus, a control method, a program, and a support system that support registration of an electronic device to a cloud service.SOLUTION: In a support system, a mobile terminal, which is an information processing apparatus, acquires device information on an imaging apparatus, which is an electronic device, from the imaging apparatus, and transmits a registration request for the electronic device, including the acquired device information, to a management apparatus that manages users and devices registered in association with the users for a predetermined service. The mobile terminal then acquires usage information required for the imaging apparatus to use the predetermined service from the management apparatus, and transmits the acquired usage information to the imaging apparatus on condition that registration of the imaging apparatus by the management apparatus has been completed based on the registration request.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to an information processing device, a control method, a program, and a support system, and more particularly to a technique for supporting the use of cloud services in electronic devices. [Background technology]

[0002] From the standpoint of privacy and security, there is a technology that enables a user to perform specific functions on an information appliance terminal that has been pre-registered for that user by performing user authentication using a mobile phone terminal when using the information appliance terminal (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-323070 A Summary of the Invention [Problem to be solved by the invention]

[0004] The technology of Patent Document 1 is premised on the fact that information on a legitimate user of an electronic device such as an information appliance terminal is preregistered in an authentication server. That is, in order to authenticate whether a user who is going to use an electronic device is a legitimate user, it is necessary to operate the electronic device prior to the authentication and to perform an operation to register information identifying the electronic device in association with the account of the legitimate user. In other words, in order to make the electronic device compatible with a service (cloud service) provided via a network, a registration operation to register a legitimate user on the electronic device is required.

[0005] However, various types of electronic devices have been developed in response to customer needs, and some electronic devices may not be suitable for registration operations for registering with existing cloud services. For example, if the user input interface of an electronic device has limited functionality, or if the performance of the display device is insufficient to display information related to registration, a user may need to perform complicated input operations to perform a registration operation using such an electronic device.

[0006] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide an information processing device, a control method, a program, and a support system that support the registration of electronic devices to a cloud service. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, the information processing device of the present invention is an information processing device that registers an electronic device that uses a specified service in association with a user, and is characterized in having: a first acquisition means that acquires device information related to the electronic device from the electronic device; a first transmission means that transmits a registration request for the electronic device to a management device that manages the user and the devices registered in association with the user for the specified service, the registration request including the device information acquired by the first acquisition means; a second acquisition means that acquires usage information necessary for the electronic device to use the specified service from the management device; and a second transmission means that transmits the usage information acquired by the second acquisition means to the electronic device on the condition that registration of the electronic device by the management device has been completed based on the registration request. Effect of the Invention

[0008] With this configuration, the present invention makes it possible to assist in the registration of electronic devices in cloud services. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a support system according to an embodiment and a modification of the present invention. [Diagram 2]FIG. 1 is a block diagram illustrating a hardware configuration of a mobile terminal 101 according to an embodiment and a modification of the present invention. [Diagram 3] FIG. 1 is a diagram illustrating a software configuration of a mobile terminal 101 according to an embodiment and a modification of the present invention. [Figure 4] FIG. 1 is a block diagram illustrating a hardware configuration of an image capture device 102 according to an embodiment and a modification of the present invention. [Diagram 5] FIG. 1 is a block diagram illustrating a hardware configuration of a management device 103 according to an embodiment and a modification of the present invention. [Figure 6] FIG. 1 is a sequence diagram illustrating a registration sequence performed in the support system according to the first embodiment of the present invention. [Figure 7] FIG. 13 shows an example of a screen configuration displayed in response to a user's input according to the embodiment and modified example of the present invention. [Figure 8] FIG. 13 illustrates an example of a cloud service API provided by a management device 103 according to an embodiment and a modification of the present invention. [Figure 9] 1 is a flowchart illustrating a request process executed by the mobile terminal 101 according to the first embodiment of the present invention. [Figure 10] 1 is a flowchart illustrating a connection process executed by the mobile terminal 101 according to an embodiment and a modification of the present invention. [Figure 11] 1 is a flowchart illustrating an authentication process executed by the mobile terminal 101 according to an embodiment and a modification of the present invention; [Figure 12] 1 is a flowchart illustrating a control process according to a first embodiment of the present invention; [Figure 13] FIG. 11 is a sequence diagram illustrating a registration sequence performed in the support system according to the second embodiment of the present invention. [Figure 14] 11 is a flowchart illustrating a control process executed by the mobile terminal 101 according to the second embodiment of the present invention. [Figure 15] FIG. 13 is a diagram illustrating a connected device list managed by a mobile terminal 101 according to an embodiment and a modification of the present invention. [Figure 16] 11 is a flowchart illustrating a pairing process executed by the mobile terminal 101 according to the third embodiment of the present invention. [Figure 17] 11 is a flowchart illustrating a registration process executed by the mobile terminal 101 according to the third embodiment of the present invention. [Figure 18] 11 is a flowchart illustrating a transmission process executed by the mobile terminal 101 according to the third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] [Embodiment 1] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0011] In the embodiment described below, the present invention is applied to a mobile terminal that transmits a request to register a device that a user desires to use a cloud service as the user's device, as an example of an information processing device. However, the present invention can be applied to any device that can register an electronic device for a specific service provided via a network instead of the electronic device.

[0012] Support System 1 is a diagram illustrating the configuration of a support system according to this embodiment. As shown in the figure, the support system according to this embodiment includes a management device 103 that manages various information about cloud services described below, and a mobile terminal 101 that is configured to be able to communicate with the management device 103.

[0013] The mobile terminal 101 is used by a user of the cloud service, and may be, for example, a general-purpose information communication terminal such as a smartphone or a PC. When using the cloud service, the user can register the electronic device he or she uses, thereby allowing the electronic device to use functions related to the cloud service. The user can transmit a registration request for the electronic device to the management device 103 by using a dedicated application on the mobile terminal 101.

[0014] The management device 103 manages information in a user DB 104 that manages users who use cloud services, and a device DB 105 that manages electronic devices that are registered in association with users and can use cloud services. As will be described in detail later, when the management device 103 receives a registration request for an electronic device from the mobile terminal 101, it executes various processes for registering the electronic device.

[0015] 1, an imaging device 102 is illustrated as an example of an electronic device for which a registration request is made by a user. The mobile terminal 101 acquires information required for registration from the imaging device 102, and performs a procedure for associating the imaging device 102 with the user and registering it in the management device 103. By registering the imaging device 102 as an electronic device used by the user, the user becomes able to use functions that utilize the imaging device 102 when using cloud services.

[0016] The transmission and reception of such information is performed via a network 106. The network 106 establishes a communication connection between devices and realizes information transfer using a standard protocol. In this embodiment, the network 106 allows the mobile terminal 101 to communicate with the imaging device 102 and the management device 103 to transmit and receive information. In the example shown in the figure, the communication connection between the mobile terminal 101 and the management device 103, and between the mobile terminal 101 and the imaging device 102, is realized via one network 106, but the embodiment of the present invention is not limited to this. The communication between the mobile terminal 101 and the imaging device 102 and the communication between the mobile terminal 101 and the management device 103 may be realized via different networks. For example, the mobile terminal 101 and the management device 103 are connected via a wide area information communication network such as the Internet. On the other hand, the mobile terminal 101 and the imaging device 102 may be connected via a narrow area information communication network that performs a wired connection or a wireless connection such as Wi-Fi (registered trademark) or Bluetooth (registered trademark).

[0017] By registering the imaging device 102 in association with a user, the imaging device 102 can execute processing using functions provided by cloud services on the imaging device 102. Examples of such cloud services include an image storage service that stores captured images recorded in the imaging device 102 in a cloud storage, and a monitoring service that distributes captured images in real time by remotely controlling the imaging device 102. In this embodiment, in order to facilitate understanding of the invention, the cloud services are described as being provided by the management device 103. That is, the imaging device 102 that has been associated with a user and is able to use functions related to the cloud services can directly communicate with the management device 103 via the network 106 and use the cloud services without going through the mobile terminal 101.

[0018] The management device 103 does not need to be configured by one server, and may be configured by a plurality of devices. Such devices may include, for example, an information management server that manages information about users, a storage server that provides online storage for users, a distribution server that distributes still images and moving images, etc. Therefore, after the image capture device 102 is registered in association with a user, it may connect to a server different from the device used for registration and use a function related to a cloud service provided by that server.

[0019] In the support system of this embodiment, the imaging device 102 is the registration target, and a cloud service using the imaging device 102 is provided, but the implementation of the present invention is not limited to this. The support system according to the present invention only needs to support the registration of an electronic device associated with a user, and the use of the electronic device is not limited to the cloud service for the above-mentioned purpose, and can include a specified service. The specified service can also include, for example, a print service that accepts print requests online and prints by registering a user's network printer.

[0020] Hardware Configuration of Mobile Terminal 101 First, the hardware configuration of the mobile terminal 101 will be described with reference to FIG.

[0021] The display unit 201 is a display device such as an LCD that the mobile terminal 101 has. The screen displayed on the display unit 201 is configured in the VRAM 202, and a series of display transitions can be provided by sequentially transferring the screen from the VRAM 202 to the display unit 201 and updating the display. The display unit 201 displays various graphical user interfaces (GUIs), as well as screens related to the OS, web browsing applications (hereinafter referred to as browsers), and applications according to the present invention.

[0022] A BMU (Bit Move Unit) 203 controls data transfer between memories (eg, between the VRAM 202 and other memories) and between memories and various I / O devices (eg, the network I / F 209).

[0023] The input I / F 204 is a user input interface provided in the mobile terminal 101. The input I / F 204 may include input interfaces such as a mouse and a keyboard connected to the mobile terminal 101, in addition to physically provided buttons and switches. When an operation input is made to various input interfaces, the input I / F 204 detects the operation input and transmits a corresponding control signal to the CPU 205. In addition, in an aspect in which the display unit 201 is configured to be able to detect a touch input, the input I / F 204 may include various sensors for detecting the touch input, and by analyzing the touch input, it is possible to transmit a corresponding control signal to the CPU 205 in the same manner. In a broad sense, the input I / F 204 may also include GUIs such as icons and software keyboards displayed on the display unit 201 as input interfaces.

[0024] The CPU 205 controls the operation of each block of the mobile terminal 101. Specifically, the CPU 205 reads out a program for controlling the operation of each block stored in the ROM 206 or the storage device 208, expands the program in the RAM 207, and executes the program, thereby controlling the operation of each block. Here, the ROM 206 and the storage device 208 are storage devices capable of permanently storing information, and store various control programs, data, and the like. In contrast, the RAM 207 is a storage device that temporarily stores information, such as a volatile memory. The RAM 207 is used as an area for expanding various control programs, a work area for the CPU 205, an area for comparing data during error processing, and the like.

[0025] The network I / F 209 is a communication interface with an external device provided in the mobile terminal 101. Through the network I / F 209, the mobile terminal 101 can communicate information with the management device 103 and various electronic devices (such as the imaging device 102 and a printer) used for cloud services via the network 106. A program for controlling the operation of the mobile terminal 101 may be pre-stored in the ROM 206 or the storage device 208, or may include a program acquired via the network I / F 209 via the network 106.

[0026] The bus 210 is a bus for transferring information between each block, and may include an address bus, a data bus, and a control bus.

[0027] <Software Configuration of Mobile Terminal 101> Next, the configuration of various software executed on the mobile terminal 101 in the support system of this embodiment will be described with reference to FIG.

[0028] 3, the software executed on the mobile terminal 101 is roughly divided into an operating system (OS) 310 related to the basic operations of the mobile terminal 101, and other application software 300. Applications that realize operations specific to the browser and support system are classified as application software 300. For these software, corresponding programs are stored in the ROM 206 or the storage device 208.

[0029] The OS 310 is started when the power supply of the mobile terminal 101 is turned on, and can cause the mobile terminal 101 to execute various operations related to predetermined functions. The OS 310 includes, for example, a communication function module 311 that realizes a basic communication function with an external device, and a copy-paste function module 312 that realizes a function of copying and moving data via a clipboard.

[0030] The communication function module 311 controls turning on and off the communication function, establishing a communication connection with an external device, and data communication with the connected external device. The communication function module 311 also controls providing data obtained by the communication function to an application, and sending and receiving data to and from an external device in response to a request from the application. The copy and paste function module 312 stores any character string on an application in a clipboard, and realizes copying or moving the character string to any location in the same application or another application.

[0031] On the other hand, the application software 300 is software that becomes available after the mobile terminal 101 is in a state where it can execute various operations by the OS 310. The application software 300 also includes modules that realize unique control using functions provided by the OS 310. The modules can include a display control module 301, a communication function control module 302 that connects to the imaging device 102 and the management device 103 and controls communication related to the support system, a copy-paste function control module 303 that controls the use of the clipboard, and the like.

[0032] Hardware Configuration of the Imaging Device 102 Next, the hardware configuration of the imaging device 102 will be described with reference to FIG.

[0033] The imaging unit 403 is an imaging element such as a CCD or CMOS element. The imaging unit 403 converts an optical image formed on the imaging surface of the imaging element via the photographing lens 401 into an electrical signal (analog image signal). The photographing lens 401 is an imaging optical system including a focus lens. In the example shown in the figure, a shutter 402 with an aperture function is present on the optical path of the imaging optical system. The photographing lens 401, the shutter 402, and the imaging unit 403 are covered by a barrier 405 to prevent them from becoming dirty or being damaged.

[0034] The A / D converter 404 converts the analog image signal output by the imaging unit 403 into a digital image signal (image data). The image processing unit 406 applies various types of image processing to the image data converted by the A / D converter 404. Such image processing may include pixel interpolation, resizing, and color conversion. The image processing unit 406 also executes predetermined arithmetic processing on the image data for exposure control and distance measurement control by the system control unit 408 described later. Note that the various types of image processing by the image processing unit 406 are not limited to the image data output by the A / D converter 404, and may also be applied to image data read out by the memory control unit 407, for example.

[0035] The image data output by the A / D converter 404 is written into the memory 409 via the image processing unit 406 and the memory control unit 407, or via only the memory control unit 407. The memory 409 stores the image data output by the A / D converter 404 and image data to be displayed on the display unit 410. The memory 409 has a capacity sufficient to store a predetermined number of still images, a predetermined amount of moving images (frame images of a predetermined number of frames), and audio. The memory 409 also serves as a video memory for display.

[0036] The D / A converter 411 converts the image data for display stored in the memory 409 into an analog image signal and supplies it to the display unit 410. Therefore, the image data for display written in the memory 409 is displayed on the display unit 410 via the D / A converter 411. The display unit 410 is a display device such as an LCD included in the imaging device 102, and can perform display according to the analog image signal.

[0037] The system control unit 408 controls the operation of each block of the imaging device 102. The system control unit 408 reads out a program stored in a non-volatile memory 412, expands the program in a system memory 413, and executes the program to control the operation of each block.

[0038] The non-volatile memory 412 is a storage device such as an EEPROM that can be electrically erased and recorded. Programs and constants for the operation of the system control unit 408, various programs required for using cloud services, etc. are stored in the non-volatile memory 412. The system memory 413 is a volatile memory such as a RAM. In the system memory 413, control programs and the like for each block are deployed, and constants and variables required for the operation of each block are stored.

[0039] The operation unit 414 is various user input interfaces such as buttons and controller wheels that the imaging device 102 includes. When the operation unit 414 detects that an operation input has been made to the user input interface, it outputs a control signal corresponding to the operation input to the system control unit 408. The release button of the operation unit 414 is configured to be able to accept two-stage operation input according to the amount of depression. When the release button is half-pressed, the operation unit 414 sends a first shutter switch signal SW1 related to a shooting preparation instruction, and when the release button is fully pressed, it sends a second shutter switch signal SW2 related to a shooting instruction. At this time, the system control unit 408 starts a series of shooting processes from reading a signal from the imaging unit 403 to writing image data to the recording medium 419 based on the second shutter switch signal SW2. At this time, the system control unit 408 controls each component of the imaging unit 403 based on a pulse signal.

[0040] In addition, in an embodiment in which the display unit 410 includes a touch input interface, the operation unit 414 also detects touch input made via the touch input interface. When the operation unit 414 detects that a touch input has been made, it similarly outputs a control signal corresponding to the touch input to the system control unit 408.

[0041] The power supply control unit 415 controls the power supply to each block. The power supply control unit 415 is composed of a battery detection circuit, a DC-DC converter, a switch circuit for switching the block to be energized, and the like. The power supply control unit 415 also detects whether the power supply unit 416 is attached, the type of the power supply unit 416, and the remaining power. Based on these detection results and instructions from the system control unit 408, the power supply control unit 415 controls the DC-DC converter and supplies the necessary power for the necessary period to each component including the recording medium 419. The power supply unit 416 may include a primary battery such as an alkaline battery or a lithium battery, a secondary battery such as a NiCd battery, a NiMH battery, or a Li battery, an AC adapter, and the like.

[0042] The communication unit 417 is a communication interface with an external device included in the imaging device 102. The communication unit 417 is an interface for communicating with an external device mainly via a cable connected to the communication unit 417, and transmits an image stored in a recording medium 419 to the external device.

[0043] The interface 418 is an interface with a recording medium 419. The recording medium 419 is a recording device constituted by, for example, a semiconductor memory such as a memory card, a magnetic disk, or the like.

[0044] The network I / F 420 is controlled by the system control unit 308 and performs communication via the network 106. The network I / F 420 connects to the network 106 mainly by wireless communication such as Wi-Fi. For example, when a cloud service is available, the network I / F 420 transmits images stored in the recording medium 419 to a server such as the management device 103 that provides the cloud service.

[0045] 4 shows the imaging device 102 having a general configuration, but in a mode in which the support system according to the present invention is used, the imaging device 102 does not need to be equipped with the display unit 410 or the operation unit 414. In order to eliminate the complication of inputting information for various procedures related to registration to a cloud service in the imaging device 102, the support system of this embodiment substitutes the registration procedures for the mobile terminal 101. Therefore, the imaging device 102 itself does not need to be equipped with the operation unit 414 that is highly operable or the display unit 410 that has a display capability that is highly viewable.

[0046] <Hardware Configuration of Management Device 103> Finally, the hardware configuration of the management device 103 will be described with reference to FIG.

[0047] A BMU (Bit Move Unit) 501 controls data transfer between memories and data transfer between memories and various I / O devices (for example, a network I / F 506).

[0048] The CPU 502 controls the operation of each block of the management device 103. Specifically, the CPU 502 reads out a program for controlling the operation of each block stored in the ROM 503 or the storage device 505, expands the program in the RAM 504, and executes the program, thereby controlling the operation of each block. Here, the ROM 503 and the storage device 505 are storage devices capable of permanently storing information, and store various control programs, data, and the like. In contrast, the RAM 504 is a storage device that temporarily stores information, such as a volatile memory. The RAM 504 is used as an area for expanding various control programs, a work area for the CPU 502, an area for comparing data during error processing, and the like.

[0049] The network I / F 506 is a communication interface with an external device provided in the management device 103. Through the network I / F 506, the management device 103 can communicate information with the mobile terminal 101 and various electronic devices (such as the imaging device 102 and a printer) that use cloud services via the network 106. A program for controlling the operation of the management device 103 may be stored in advance in the ROM 503 or the storage device 505, or may include a program acquired via the network I / F 506 via the network 106.

[0050] The bus 507 is a bus for transferring information between each block, and may include an address bus, a data bus, and a control bus.

[0051] Registration sequence for supporting registration of electronic device In the support system of this embodiment, a series of registration sequences for registering an electronic device in association with a user for a cloud service and making the electronic device available for the cloud service will be described with reference to the sequence diagram of FIG. 6. Each process in the sequence diagram is realized by the control unit or CPU of each device expanding a program stored in a ROM or the like into a RAM or the like and executing it. More specifically, in the mobile terminal 101, the CPU 205 expands a program related to a dedicated application stored in the ROM 206 or the storage device 208 into the RAM 207 and executes it, thereby realizing each process. In the imaging device 102, the system control unit 408 expands a program stored in the non-volatile memory 412 into the system memory 413 and executes it, thereby realizing each process. In the management device 103, the CPU 502 expands a program stored in the ROM 503 into the RAM 504 and executes it, thereby realizing each process.

[0052] In this registration sequence, it is assumed that the user has logged in to the cloud service using his / her user ID and password, etc., in a dedicated application on the mobile terminal 101. Therefore, it is assumed that the CPU 502 of the management device 103 is in a state where it is possible to identify which user the various requests made from the mobile terminal 101 to the management device 103, as shown below, are made to.

[0053] 6, a user who uses a mobile terminal 101 links the imaging device 102 to his / her account in order to manage still images and moving images captured using, for example, a cloud storage service provided by the management device 103. Here, linking the imaging device 102 means registering the imaging device 102 in the user's account as an electronic device used by the user, and enabling the imaging device 102 to use a function for uploading images, etc. to cloud storage. In other words, by registering the imaging device 102 in association with the user, images, etc. uploaded from the imaging device 102 are stored in an area of ​​the cloud storage associated with the user, and the user is able to view the images on any device.

[0054] Therefore, when the registration sequence starts, the image capture device 102 is not associated with the user who uses the mobile terminal 101, and the mobile terminal 101 registers the image capture device 102 to the cloud service instead of the image capture device 102.

[0055] When the registration sequence starts, in S601, the CPU 205 of the mobile terminal 101 transmits a communication connection request to the imaging device 102. Furthermore, upon receiving the communication connection request, in S602, the system control unit 408 of the imaging device 102 returns a connection response, whereby a communication connection between the mobile terminal 101 and the imaging device 102 is established.

[0056] When the communication connection is established, in S603, the CPU 205 of the mobile terminal 101 requests device information from the imaging device 102. Here, the device information is information including various information related to the imaging device 102. In the support system of this embodiment, for example, the following information is acquired as device information for registering an electronic device to be used in a cloud service. A part of the device information is information for uniquely identifying an electronic device (device), and may include, for example, the manufacturer name, model name, model ID, serial number, firmware version, MAC address, etc. of the electronic device. In addition, in a mode in which the cloud service has a plurality of service modes and which service can be used changes depending on the function (capability) supported by the electronic device, the device information may include device capability information. The function supported by the electronic device may change depending on, for example, the firmware version of the device, so the capability information and the firmware version may be collectively referred to as "device capability information". Here, the device information may be data described using a language used for data exchange, such as xml or json.

[0057] In S604, the system control unit 408 of the imaging device 102 returns its own device information in response to the request from the mobile terminal 101. The device information may be stored in the non-volatile memory 412, for example.

[0058] When the device information is received from the imaging device 102, the CPU 205 of the mobile terminal 101 accepts, in S605, input of authentication information required for registering the imaging device 102. Although details will be described later, the support system of this embodiment provides a process for authenticating a user when associating the user with an electronic device. The authentication information is information for performing a series of processes related to the authentication process, and in this embodiment is configured based on an input by a user who is about to perform registration.

[0059] The input of authentication information is accepted by displaying an input screen such as that shown in Fig. 7(a) on the display unit 201. The input screen shown in the figure includes a text box 701 for accepting input of an email address as the user's contact information, and a text box 702 for accepting input of a passcode for authentication, as authentication information. The user can select each text box in the input screen and input the corresponding text. The input of authentication information is completed by operating an OK button 703 for completing input when text corresponding to the text boxes 701 and 702 has been entered.

[0060] In S606, the CPU 205 of the mobile terminal 101 transmits a registration request for provisional registration of the imaging device 102 to the management device 103. In the support system of this embodiment, a cloud service API is provided for various processes and information transmission to be performed by the CPU 502 of the management device 103, as shown in Fig. 8. The CPU 205 can cause the CPU 502 of the management device 103 to execute the corresponding process or receive the necessary information by calling the corresponding API while supplying necessary information to the management device 103 as request parameters.

[0061] The registration request in this step is made by using the device provisional registration API. As shown in Fig. 8, the request parameters of the device provisional registration API include authentication information and device information. Therefore, the CPU 205 can request the management device 103 to register the imaging device 102 by sending the authentication information and the device information as request parameters and calling the device provisional registration API.

[0062] When the device provisional registration API is called, the CPU 502 of the management device 103 issues various information related to the provisional registration of the imaging device 102 and returns it as a response to the mobile terminal 101. The information generated in relation to the provisional registration includes a device registration ID for uniquely identifying the electronic device, and usage information required for the device to use a cloud service after official registration. The usage information includes a device access ID and a device password required for service login and API invocation when the imaging device 102 uses a cloud service.

[0063] In S607, the CPU 205 of the mobile terminal 101 transmits device capability information about the imaging device 102 that has made the registration request. More specifically, the CPU 205 transmits the device registration ID returned in S606 and the firmware version and capability information acquired from the imaging device 102 as request parameters, and calls the device capability declaration API. This call enables the CPU 502 of the management device 103 to grasp cloud services that can be provided to the electronic device (imaging device 102) corresponding to the device registration ID after the electronic device is officially registered. In other words, the CPU 502 can grasp services that can be used by the electronic device among functions that the management device 103 can provide as cloud services, and therefore can control which service is to be used when the electronic device is officially registered thereafter. When the device capability declaration API is called, the CPU 502 returns a receipt confirmation to the mobile terminal 101 as a response.

[0064] In S608, the CPU 502 of the management device 103 provisionally registers the device management information of the imaging device 102 for which the registration request has been made in the device DB 105, based on the various information acquired as request parameters in S606 and S607 and the issued information. The device management information includes the received device information, information on available cloud services, and the issued device access ID and device password, in association with the device registration ID issued for the imaging device 102. The device management information may also include information on a logical provisional registration flag indicating that provisional registration is in progress. Furthermore, the CPU 502 associates the device management information with a user ID, or adds the device registration ID to information on the user in the user DB 104, or both, thereby realizing association of the provisionally registered imaging device 102 with the user.

[0065] In addition, in the provisional registration, the CPU 502 issues an authentication page for performing authentication processing for the imaging device 102 to be provisionally registered, and an authentication URL (authentication connection destination) for accessing the authentication page. The authentication page is a Web page published by the management device 103 in a form accessible only to those who know the authentication URL, and is configured with content requesting input of a passcode as shown in FIG. 7B, for example. The passcode requested to be input on the authentication page is the passcode included in the authentication information acquired in S606, and is the passcode input by the user in S605. That is, in the support system of this embodiment, an authentication process is provided for authenticating, for a registration request received via a dedicated application, an electronic device corresponding to device information included as a request parameter of the registration request as the electronic device used by the user. For this reason, the user is authenticated by having the passcode specified at the time of the registration request input again on the authentication page, not by the dedicated application that issued the registration request.

[0066] In S609, the CPU 502 of the management device 103 notifies the user of the authentication URL issued in S608. In the support system of this embodiment, the authentication URL is notified by including the authentication URL in the body of an email sent to the email address related to the user input as authentication information. To facilitate understanding of the invention, the email address input by the user as authentication information will be described as being receivable by the mobile terminal 101. That is, a user who performs an operation related to a registration request in a dedicated application running on the mobile terminal 101 for the imaging device 102 can then receive an email notifying the user of the authentication URL at his or her own email address.

[0067] When the user inputs an operation for the authentication URL described in the email, that is, when the user requests a connection to the authentication page, the CPU 205 of the mobile terminal 101 starts up a browser in S610 to connect to the authentication page and accepts the input of a passcode. The input of the passcode is completed when the user inputs an operation for the OK button 712 for completing the input with the text related to the passcode being input in the text box 711 in the authentication page shown in FIG. 7(b).

[0068] When the input of the passcode is accepted, the CPU 205 of the mobile terminal 101 transmits the passcode information input in the text box 711 to the server of the authentication page, that is, the management device 103, in S611.

[0069] In S612, the CPU 502 of the management device 103 updates the device management information of the imaging device 102 from a provisionally registered state to a formally registered state when the passcode entered for the authentication page matches the passcode previously received as authentication information. Note that the CPU 502 may delete the provisionally registered device management information from the device DB 105, for example, when a mismatch in passcode occurs a predetermined number of times. Also, input of a passcode for the authentication page may be accepted only for a predetermined period (validity period of provisional registration) after the authentication page is issued, for example.

[0070] After the passcode is input in the authentication process, the CPU 205 of the mobile terminal 101 inquires in S613 whether the association (registration) of the imaging device 102 that has made the registration request has been completed. The inquiry as to whether the registration has been completed is made by calling a device registration completion confirmation API with the device registration ID notified as a response to the registration request as a request parameter. In response to the call, the CPU 502 of the management device 103 in S614 refers to device management information stored in the device DB 105 in association with the device registration ID, and returns registration result information indicating whether the registration has been completed as a response. If the device management information of the imaging device 102 has been officially registered, the registration result information indicates that the registration has been completed, and otherwise indicates that the registration has not been completed. The registration result information indicating that the registration has been completed can also include information specifying cloud services that the imaging device 102 can use, information on the expiration date (available period) set for each cloud service, and the like.

[0071] If the received registration result information indicates that registration has been completed, the CPU 205 of the mobile terminal 101 transmits usage information to the imaging device 102 in S615, and then terminates the communication connection with the imaging device 102. At this time, the usage information may include at least a part of the registration result information (e.g., information on available cloud services and expiration date) in addition to the above-mentioned device access ID and device password. The usage information transmitted in this manner is stored, for example, in the non-volatile memory 412 of the imaging device 102, so that the imaging device 102 is able to use a function for using a cloud service (e.g., image upload). That is, the imaging device 102 is able to use a cloud service when it is located within the communication range of the network 106, for example, by being set by the user or by storing setting information changed in response to receiving the usage information.

[0072] <<Processing of each step on a mobile device>> In this way, in the registration sequence in the support system of this embodiment, the processing performed by the mobile terminal 101 can be classified into three steps 621, 622, and 623 as shown in Fig. 6. More specifically, the processing performed by the mobile terminal 101 is classified into a request step 621 for acquiring various information and transmitting information, an authentication step 622 for authenticating a user, and a control step 623 for controlling the state of the imaging device 102 according to the registration result. That is, the request step 621 corresponds to the processing of S601 to S607 in the registration sequence, the authentication step 622 corresponds to the processing of S610 and S611 in the same sequence, and the control step 623 corresponds to the processing of S613 to S615 in the same sequence. Details of the processing of each step will be described below with reference to the corresponding flowchart.

[0073] <Required process processing> First, the request step processing related to the request step 621 will be specifically described with reference to the flowchart in Fig. 9. The processing corresponding to the flowchart can be realized by CPU 205 reading out the corresponding processing program stored in ROM 206 or storage device 208, for example, and expanding and executing the program in RAM 207. The request step processing will be described as being started when an operation input related to the registration of an electronic device to be used for a cloud service is performed in a dedicated application, for example.

[0074] In S901, the CPU 205 executes a connection process to establish a communication connection with an electronic device to be registered (hereinafter referred to as a target device) and acquire device information from the target device. That is, the target device corresponds to the imaging device 102 in the support system of the aspect shown in Fig. 1. The connection process performed in this step corresponds to the processes of S601 to S604 in the registration sequence.

[0075] (Connection processing) The connection process performed in this step will be described in detail with reference to the flowchart in Fig. 10. Note that in this connection process, an upper limit is set for the number of attempts for each of the processes of establishing a communication connection between the target device and mobile terminal 101 and acquiring device information from the target device. The connection process returns a return value indicating successful acquisition of device information when a communication connection between mobile terminal 101 and the target device is established and acquisition of device information from the target device is completed. The connection process also returns an error return value when establishment of a communication connection or acquisition of device information fails.

[0076] In S1001, the CPU 205 initializes (sets to 0) a timeout counter that counts the number of attempts to make a communication connection request to the target device.

[0077] In S1002, CPU 205 determines whether the number of attempts to make a communication connection request has reached a predetermined number (timeout has occurred). If CPU 205 determines that the number of attempts to make a communication connection request has reached the predetermined number, it shifts the process to S1012, and if it determines that the number has not reached the predetermined number, it shifts the process to S1003.

[0078] In S1003, the CPU 205 issues a communication connection request for starting a communication connection via the network 106 to a target device to be associated with the user, and waits for a response from the target device for a predetermined period of time.

[0079] In S1004, the CPU 205 receives a connection response from the target device and determines whether or not a communication connection has been established between the mobile terminal 101 and the target device. If the CPU 205 determines that a communication connection has been established, the process proceeds to S1006, and if the CPU 205 determines that a communication connection has not been established, the process proceeds to S1005.

[0080] In S1005, the CPU 205 updates (increments) a timeout counter related to the number of attempts of a communication connection request, and returns the process to S1002.

[0081] On the other hand, if it is determined in S1004 that a communication connection between the mobile terminal 101 and the target device has been established, the CPU 205 initializes (sets to 0) in S1006 a timeout counter that counts the number of attempts to request the target device to transmit device information.

[0082] In S1007, CPU 205 determines whether the number of transmission request attempts has reached a predetermined number (timeout has occurred). If CPU 205 determines that the number of transmission request attempts has reached the predetermined number, it shifts the process to S1012, and if CPU 205 determines that the number has not reached the predetermined number, it shifts the process to S1008.

[0083] In S1008, the CPU 205 issues a request to transmit device information to the target device, and waits for a response from the target device for a predetermined period of time.

[0084] In S1009, the CPU 205 determines whether or not device information has been received from the target device. If the CPU 205 determines that the device information has been received, the process proceeds to S1011, and if the CPU 205 determines that the device information has not been received, the process proceeds to S1010.

[0085] In S1010, the CPU 205 updates (increments) a timeout counter related to the number of attempts to transmit a request for device information, and returns the process to S1007.

[0086] On the other hand, if it is determined in step S1009 that the device information has been received, the CPU 205 returns a return value indicating that the information has been acquired successfully in step S1010, and completes this connection process.

[0087] Moreover, if it is determined in steps S1002 and S1007 that a timeout has occurred, the CPU 205 returns an error as a return value in step S1012 and ends this connection process.

[0088] When the return value of the connection process is obtained, the CPU 205 transfers the request process to S902.

[0089] In S902, CPU 205 determines whether or not device information of the target device has been acquired. The determination in this step can be made based on the return value of the connection process executed in S901. If CPU 205 determines that device information of the target device has been acquired, it moves the process to S903. If CPU 205 determines that device information of the target device has not been acquired, it displays, for example, a notice on display unit 201 that the electronic device to be registered cannot be found, and completes this request process. In this case, the registration sequence ends without proceeding to authentication process 622.

[0090] In S903, the CPU 205 causes the display unit 201 to display an input screen relating to authentication information as exemplified in Fig. 7(a). Prior to or together with the display of the input screen, the CPU 205 may cause the display unit 201 to display matters requesting consent regarding the handling of the user's personal information, and proceed with the process on the condition that the user consents to the matters.

[0091] In S904, CPU 205 determines whether or not an operational input has been made to OK button 703 with significant text information having been entered in the text boxes for various information related to authentication information (email address and passcode). If CPU 205 determines that an operational input has been made to OK button 703 with authentication information text information having been entered, CPU 205 transfers the process to S905. If an operational input has not been made to OK button 703, or if an operational input has been made to OK button 703 with significant text information not having been entered in at least any of the text boxes, CPU 205 repeats the process of this step.

[0092] In S905, the CPU 205 stores the text information entered in each text box on the input screen relating to authentication information in, for example, the RAM 207 as authentication information.

[0093] In S906, the CPU 205 transmits a registration request for provisional registration of the target device to the management apparatus 103. The processing of this step is realized by calling the device provisional registration API, as described above for S606 of the registration sequence. In executing this step, the CPU 205 generates information (request parameters) to be transmitted as the registration request, including the device information acquired in S901 and the authentication information stored in S905.

[0094] In step S907, the CPU 205 acquires, as a response to the call of the device provisional registration API, a device registration ID and usage information from the management apparatus 103. The CPU 205 stores the acquired information in the RAM 207, for example.

[0095] In S908, the CPU 205 transmits the device capability information to the management apparatus 103, and completes this request process.

[0096] (Authentication process) Next, the authentication process related to the authentication process 622 will be specifically described with reference to the flowchart in Fig. 11. The process corresponding to the flowchart can be realized by the CPU 205 reading out the corresponding processing program stored in, for example, the ROM 206 or the storage device 208, and executing it by expanding it in the RAM 207. The authentication process will be described as being started on the condition that, for example, a registration request related to provisional registration is transmitted in a dedicated application and a request process is completed.

[0097] In S1101, the CPU 205 determines whether a connection request to an authentication page has been made. More specifically, the CPU 205 determines whether a connection request has been made to an authentication URL included in an email received from the management device 103 in response to a registration request for a target device. If the CPU 205 determines that a connection request to an authentication page has been made, the CPU 205 moves the process to S1102, and if it determines that a connection request has not been made, the CPU 205 repeats the process of this step.

[0098] In S1102, the CPU 205 causes the authentication page to be displayed on the display unit 201. The processing of this step is realized by the CPU 205 performing display control based on data received in response to starting up the browser and connecting to the authentication URL.

[0099] In S1103, CPU 205 determines whether or not an operational input has been made to OK button 712 with text information being entered in passcode text box 711 on the authentication page. If CPU 205 determines that an operational input has been made to OK button 712 with passcode text information being entered, CPU 205 transfers the process to S1104. If an operational input has not been made to OK button 712, or if an operational input has been made to OK button 712 with no text information being entered in text box 711, CPU 205 repeats the process of this step.

[0100] In S1104, the CPU 205 transmits the text information (passcode) entered in the text box to the management apparatus 103, and completes this authentication process.

[0101] This authentication process can be realized, for example, by monitoring the behavior of the browser when processing a dedicated application, or by connecting to the authentication page via a browser in the dedicated application using attributes attached to the authentication URL and monitoring input.

[0102] (Control Process Processing) Next, the control process related to the control process 623 will be described in detail with reference to the flowchart in Fig. 12. The process corresponding to the flowchart can be realized by the CPU 205 reading out the corresponding processing program stored in, for example, the ROM 206 or the storage device 208, and executing it by expanding it in the RAM 207. This control process will be described as being started a predetermined time after the completion of, for example, the authentication process or the request process.

[0103] In S1201, the CPU 205 inquires whether the registration of the target device has been completed. The processing of this step is realized by calling the device registration completion confirmation API, as described above with respect to S613 of the registration sequence.

[0104] In step S1202, the CPU 205 receives registration result information as a response to the call of the device registration completion confirmation API.

[0105] In S1203, the CPU 205 determines whether the registration result information received in S1202 indicates that registration is complete. If the CPU 205 determines that the registration result information indicates that registration is complete, the process proceeds to S1204, and if the CPU 205 determines that the registration result information indicates that registration is incomplete, the process proceeds to S1205.

[0106] In S1204, the CPU 205 transmits usage information enabling the target device to use the cloud service to the target device, and completes this control process. The usage information transmitted in this step may be configured to include at least a part of the registration result information received in S1202, in addition to the usage information acquired in S907 of the request process, as described above.

[0107] On the other hand, if it is determined in S1203 that the registration result information indicates that registration is incomplete, the CPU 205 in S1205 causes the display unit 201 to display, for example, an error notification indicating that registration of the target device has failed, and completes this control process.

[0108] As described above, the information processing device and the support system of the present embodiment can support the registration of an electronic device to a cloud service. In particular, the information processing device can provide a registration method that is more convenient for an electronic device having an operation input interface with low operability than performing operations related to registering the device to a cloud service on the electronic device.

[0109] In this embodiment, the user's email address can be arbitrarily input for user authentication, but the present invention is not limited to this. For example, the user's email address may be an email address that has already been authenticated in the cloud service. In addition, the user's contact information for user authentication is not limited to the user's email address, and it goes without saying that contact information for other contact methods can be used.

[0110] [Embodiment 2] In the above-described embodiment, a mode has been described in which the communication connection between the mobile terminal 101 and the imaging device 102 established in S602 of the registration sequence is maintained until the transmission of usage information to the imaging device 102 in S615. On the other hand, the communication connection between the mobile terminal 101 and the imaging device 102 may be disconnected during the progress of the registration sequence due to reasons such as the occurrence of a communication trouble or an interruption operation by the user. In the support system of the present embodiment, a mode will be described in which the communication connection between the mobile terminal 101 and the imaging device 102 is permitted to be disconnected during the progress of the registration sequence, and the communication connection between the mobile terminal 101 and the imaging device 102 is re-established as necessary to continue the processing.

[0111] Registration sequence Fig. 13 illustrates a sequence diagram of a registration sequence related to the support system of this embodiment. In the registration sequence shown in Fig. 13, steps that perform the same processes as those in the registration sequence of the first embodiment are given the same reference numerals, and the steps that perform processes unique to this embodiment will be particularly described below. Note that the registration sequence shown in Fig. 13 illustrates an example in which, after the system control unit 408 of the imaging device 102 returns device information in S604, the communication connection between the mobile terminal 101 and the imaging device 102 is cut off due to loss of power of the power supply unit 416 of the imaging device 102.

[0112] When the registration result information returned from the management device 103 is received in S614, the CPU 205 of the mobile terminal 101 determines in S1301 whether or not the communication connection with the imaging device 102 is maintained. At this time, if the communication connection with the imaging device 102 is maintained, the CPU 205 executes transmission of the usage information to the imaging device 102 as it is in S615. On the other hand, if the communication connection with the imaging device 102 is not maintained, the CPU 205 executes the communication connection with the imaging device 102 and acquisition of device information in S1302 to S1305 in the same manner as in S601 to S604 in order to re-establish the communication connection with the imaging device 102. Then, when the communication connection with the imaging device 102 is re-established, the CPU 205 advances the process to S615 and executes transmission of the usage information to the imaging device 102. Whether or not the communication connection with the imaging device 102 is re-established can be determined based on the device information acquired in S1305. If the communication connection established in S1303 is not with the imaging device 102 that was registered, the CPU 205 may perform control to, for example, cancel the registration. That is, the CPU 205 performs control to discard the usage information that it has held, and delete the device management information of the imaging device 102 that has been officially registered for the user from the management device 103.

[0113] Control process processing The control step processing performed by the mobile terminal 101 for the control step 623 of the registration sequence of this embodiment will be specifically described below with reference to the flowchart of Fig. 14. The processing corresponding to this flowchart can be realized by the CPU 205 reading out a corresponding processing program stored in, for example, the ROM 206 or the storage device 208, and executing it by expanding it in the RAM 207. This control step processing will be described as being started a predetermined time after, for example, the authentication step processing or the request step processing is completed. In the description of the control step processing of this embodiment, the steps that perform the same processing as in embodiment 1 are given the same reference numbers, and only the steps that perform processing unique to this embodiment will be described below.

[0114] If it is determined in S1203 that the registration result information indicates that registration is complete, the CPU 205 determines whether or not a communication connection with the target device is maintained in S1401. If the CPU 205 determines that a communication connection with the target device is maintained, the process proceeds to S1204, and if it determines that a communication connection is not maintained, the process proceeds to S1402.

[0115] In S1402, the CPU 205 executes a connection process to re-establish a communication connection with the target device and acquire device information from the target device. The process of this step may be the same as the connection process of FIG. 10 executed in S901 of the request process.

[0116] In S1403, the CPU 205 determines whether or not a communication connection with the target device has been re-established. If the CPU 205 determines that a communication connection with the target device has been re-established, the CPU 205 moves the process to S1204. If the CPU 205 determines that a communication connection with the target device has not been re-established, the CPU 205 executes a process for canceling registration in S1404, and completes this control process.

[0117] As described above, according to the information processing device and assistance system of this embodiment, even if the communication connection between the mobile terminal 101 and the target device (imaging device 102) is disconnected while the registration sequence is in progress, the registration sequence can be completed by reconnecting.

[0118] [Variation 1] In the above embodiment, it has been described that if the communication connection between the mobile terminal 101 and the target device is cut off while the registration sequence is in progress and the communication connection is not re-established thereafter, the process for canceling the registration is executed. However, the implementation of the present invention is not limited to this, and for example, for an electronic device in which the registration result information indicates the completion of registration, that is, the electronic device is officially registered by the user in the service, the usage information may be stored and transmitted the next time the communication connection is established.

[0119] More specifically, if the electronic device with which the communication connection is established in the control process is different from the target device, the CPU 205 inquires of the user whether to suspend the registration of the target device. Then, when an operation input related to the suspension is made, the CPU 205 further inquires of the user whether to hold the usage information of the target device. That is, the CPU 205 suspends the cloud service linkage of the target device in response to these inquiries, but checks whether to hold the information so that the cloud service linkage of the target device can be resumed when the target device is reconnected. When an operation input to hold the usage information is made, the CPU 205 associates the usage information of the target device with, for example, the device information of the target device and stores it in the storage device 208, so that it can be transmitted when the target device is reconnected. That is, for the target device in which the usage information is stored, when a communication connection with the mobile terminal 101 is established, the usage information can be configured to be provided without executing all the steps of the registration sequence again.

[0120] Such transmission of usage information can be realized, for example, by storing in the storage device 208 or the like a connected device list that manages information (device information) of electronic devices that have established a communication connection with the mobile terminal 101 in a manner that allows the progress status of a registration sequence related to the electronic device to be grasped. Information may be added to the connected device list when an electronic device is first connected to the mobile terminal 101 for communication, and when a communication connection is established thereafter, the information in the corresponding connected device list is updated.

[0121] In one aspect, the information managed for each electronic device in the connected device list can be configured as shown in Fig. 15, for example. In the example of Fig. 15, the connected device list manages device information 1502 of each electronic device connected for communication with the mobile terminal 101, in association with ID 1501 that uniquely identifies the information in the connected device list. In the example of Fig. 15, the device information 1502 shows the model name and serial number of the electronic device. The connected device list also includes, for each electronic device, a registration flag 1503 indicating whether a registration request has been made to the management device 103, registration result information 1504 acquired for the electronic device, and a transmitted flag 1505 indicating whether usage information has been transmitted to the electronic device.

[0122] The registration flag 1503, the registration result information 1504, and the transmitted flag 1505 are updated according to the progress of the registration sequence, and therefore the initial values ​​are set to "not registered (registration request not made)", "(formal registration) incomplete", and "(usage information) not transmitted", respectively. The registration flag 1503 is changed to "registered" when the CPU 205 calls a device provisional registration API for the corresponding electronic device. The registration result information 1504 is changed to the value of the registration result information when the CPU 205 calls a device registration completion confirmation API for the corresponding electronic device and receives the registration result information. The transmitted flag 1505 is changed to "transmitted" when the CPU 205 transmits the corresponding usage information to the corresponding electronic device. Therefore, the CPU 205 can grasp the progress of the registration sequence related to the electronic device by referring to the information in the connected device list for each electronic device.

[0123] The connected device list does not need to manage the registration result information 1504 for each electronic device. The information can be specified, for example, by the CPU 205 inquiring of the management device 103 as to whether or not the electronic device in question has been registered in association with the user. Similarly, the connected device list does not need to manage the transmitted flag 1505 for each electronic device. The information can be specified, for example, based on whether or not usage information associated with the electronic device in question is stored in the storage device 208.

[0124] In this embodiment, when a communication connection with an electronic device is established and device information is acquired, the CPU 205 can refer to information in the connected device list that indicates the same device information as the electronic device and determine which step of the registration sequence to proceed from. In the above embodiment, when the registration result information 1504 of the corresponding information in the connected device list indicates "registration completed" and the transmitted flag 1505 is "not transmitted", the CPU 205 reads the corresponding usage information from the storage device 208 and transmits it to the electronic device.

[0125] If the information is not to be retained so that the electronic device can resume cloud service linkage when the electronic device reconnects, the information related to the electronic device in the connected device list can be deleted, so that the entire registration sequence can be repeated the next time the electronic device reconnects.

[0126] [Variation 2] In the above-described embodiment and modified example, a description has been given of an aspect that basically assumes that the communication connection between the mobile terminal 101 and the target device is maintained during the progress of the registration sequence, but the implementation of the present invention is not limited to this. That is, the registration sequence may be configured to establish a communication connection with the electronic device every time it becomes necessary to transmit and receive information between the mobile terminal 101 and the electronic device, and to disconnect the connection after the information is transmitted and received. For example, in the registration sequence described in the first embodiment, the CPU 205 may perform control to establish a communication connection with the electronic device at the start of the request step 621 and before the transmission of the usage information in the control step 623.

[0127] In such an embodiment, the registration sequence can be classified into a process (S605-S614) of acquiring authentication information and making a request to management device 103 to register the electronic device, and a process (S615) of transmitting usage information to the electronic device, from the viewpoint of using a communication connection with the electronic device as a trigger. In other words, in an embodiment in which the progress of the registration sequence is managed for each electronic device connected in the connected device list as in Modification 1, CPU 205 may control which of these two types of processes to perform, based on device information of the electronic device with which a communication connection has been established.

[0128] For example, when the mobile terminal 101 establishes a communication connection with an arbitrary electronic device and receives device information, the CPU 205 grasps the progress of the registration sequence related to the electronic device corresponding to the device information by referring to the connected device list. Then, the CPU 205 may determine whether to execute the process of S605 and subsequent steps of the registration sequence or the process of S615 based on the progress. That is, in the mobile terminal 101 of this modification, when a communication connection with an electronic device is established in a dedicated application, if the information of the electronic device is not registered in the connected device list, the CPU 205 executes the process of the registration sequence from S605 onwards. Also, if the information of the electronic device is registered in the list and the registration of the electronic device by the management device 103 has been completed, the CPU 205 executes the process of the registration sequence from S615 and transmits the usage information to the electronic device.

[0129] In this way, for an electronic device that has been registered in association with a user, usage information can be provided when a communication connection with the mobile terminal 101 is established after the registration. In other words, according to this modification, it is not necessary to keep the mobile terminal 101 and the electronic device that desires cloud service cooperation in a state in which they can communicate with each other during the registration sequence. Therefore, once an electronic device is communicatively connected to the mobile terminal 101 and a registration request is made, the user can connect the electronic device to the mobile terminal 101 at a desired timing and operate the electronic device in a state in which the cloud service can be used.

[0130] [Embodiment 3] In the above-described embodiment and modified example, a registration request is made to the management device 103 in response to communication connection to an electronic device and acquisition of device information in the registration sequence, but the present invention is not limited to this. That is, the request step 621 in the registration sequence does not need to be executed all at once, and may be configured such that, for example, after communication connection is made to a plurality of electronic devices and device information is acquired, a registration request is made by specifying one of the electronic devices.

[0131] In the support system of this embodiment, the request step 621 is divided into a first step of acquiring device information from the electronic device and a second step of making a registration request to the management device 103 for any one of the electronic devices, and is configured to be independently executable. For example, a menu for acquiring device information (pairing menu) and a menu for registering a paired electronic device in a cloud service (registration menu) may be provided in the dedicated application, and the request step may be executed when each menu is selected. More specifically, when the pairing menu is selected in the dedicated application, the CPU 205 controls to execute the processing related to the first step (S601 to S604 and adding information to the connected device list). When the registration menu is selected in the dedicated application, the CPU 205 controls to execute the second step, the authentication step, and the processing related to confirmation of registration completion (S605 to S614). In the following description, the state in which an electronic device is communicatively connected to the mobile terminal 101, the mobile terminal 101 acquires device information about the electronic device, and adds the information about the electronic device to the connected device list is referred to as the state in which the electronic device is paired with the mobile terminal 101.

[0132] In this embodiment, in order to facilitate understanding of the invention, the dedicated application is further provided with a send menu for sending the usage information to the paired electronic device. When the send menu is selected in the dedicated application, the CPU 205 controls to execute a process for sending the usage information (S615).

[0133] Hereinafter, a detailed description will be given with reference to a flowchart of the process performed by the mobile terminal 101 when each menu is selected in the dedicated application of this embodiment. <Pairing process> First, the pairing process executed when the pairing menu is selected will be described in detail with reference to the flowchart in Fig. 16. The process corresponding to the flowchart can be realized by CPU 205 reading out a corresponding processing program stored in ROM 206 or storage device 208, for example, and expanding and executing the program in RAM 207. In the description of this pairing process, steps that perform the same processes as the request process shown in Fig. 9 are given the same reference numbers and will not be described below, and steps that perform processes unique to this pairing process will be described below. In addition, in this pairing process, the "target device" refers to an electronic device that is communicatively connected to mobile terminal 101 in this pairing process.

[0134] If it is determined in S902 that the device information of the target device has been acquired, the CPU 205 determines in S1601 whether or not pairing with the target device has been completed. The determination in this step can be made, for example, based on whether or not information indicating the same device information 1502 as the acquired device information is included in the connected device list. If the CPU 205 determines that the target device has been paired, it shifts the process to S1603, and if it determines that the device has not been paired, it shifts the process to S1602.

[0135] In step S1602, the CPU 205 newly adds information about the target device to the connected device list.

[0136] In S1603, the CPU 205 disconnects the communication connection with the target device and completes this pairing process.

[0137] In this way, information about the paired electronic device (the electronic device from which the device information has been acquired) is added to the connected device list.

[0138] Registration process Next, the registration process executed when the registration menu is selected will be described in detail with reference to the flowchart of Fig. 17. The process corresponding to the flowchart can be realized by CPU 205 reading out the corresponding processing program stored in ROM 206 or storage device 208, for example, and developing and executing the program in RAM 207. In the description of the registration process, steps that perform the same processes as the request process shown in Fig. 9 and the control process shown in Fig. 12 are given the same reference numbers and will not be described below, and steps that perform processes unique to the registration process will be described below. In the registration process, the "target device" refers to an electronic device selected as a target for registration to the cloud service in S1702 shown below.

[0139] In S1701, the CPU 205 determines whether or not there is an electronic device among the paired electronic devices that has not yet requested registration with the management device 103. The determination in this step can be made, for example, based on whether or not information about an electronic device whose registration flag 1503 is "unregistered" is included in the connected device list. If the CPU 205 determines that there is an electronic device among the paired electronic devices that has not yet requested registration with the management device 103, the process proceeds to S1702. If the CPU 205 determines that all of the paired electronic devices have requested registration, the CPU 205 causes the display unit 201 to display, for example, a notice that there are no electronic devices that can be registered with the cloud service, and completes the main registration process.

[0140] In S1702, the CPU 205 displays on the display unit 201 a list of paired electronic devices for which a registration request to the management device 103 has not yet been made, and accepts selection of an electronic device (target device) to be registered in the cloud service. At this time, the user selects one electronic device from the list by operating the mobile terminal 101. The list of electronic devices displayed on the display unit 201 in this step includes only paired electronic devices for which a registration request has not yet been made, and therefore electronic devices for which a registration request has been made are excluded from the selection targets. When the CPU 205 accepts an operational input to select one electronic device from the list, it stores information of the selected electronic device in the RAM 207 as information of the target device, and moves the process to S903.

[0141] When a registration request for provisional registration of the target device is transmitted in S906, the CPU 205 changes the registration flag 1503 of the information of the target device included in the connected device list to "registered" in S1703.

[0142] Furthermore, when the device capability information of the target device is transmitted in S908, the CPU 205 executes an authentication process in S1704.

[0143] Furthermore, when registration result information for the target device is received in S1202, CPU 205 updates registration result information 1504 for the information of the target device included in the connected device list based on the registration result information in S1705. That is, CPU 205 updates registration result information 1504 for the information of the target device to "registration completed" if the received registration result information indicates that registration is complete, and updates it to "incomplete" if the registration is incomplete (or leaves it as the initial value "incomplete").

[0144] In this way, a registration request is made for the target device selected by the user, and the connected device list can be updated to a state in which registration result information indicating whether or not official registration has been performed is stored.

[0145] <<Transmission process>> Next, the specific processing of the transmission processing executed when the transmission menu is selected will be explained using the flowchart of Fig. 18. The processing corresponding to this flowchart can be realized by CPU 205 reading out the corresponding processing program stored in ROM 206 or storage device 208, for example, and expanding it in RAM 207 and executing it. In the explanation of this transmission processing, steps that perform the same processing as the control process shown in Fig. 12 are given the same reference numbers and their explanations are omitted, and the following will explain the steps that perform processing unique to this transmission processing. In addition, in this transmission processing, the "target device" refers to the electronic device with which a communication connection is established in S1802 shown below and device information is acquired.

[0146] In S1801, the CPU 205 displays a notification prompting connection of the electronic device that transmits the usage information on the display unit 201. In response to the notification, the user operates the electronic device to which the user desires to transmit the usage information to transition to a state in which the electronic device can be connected for communication, for example.

[0147] In step S1802, the CPU 205 executes a connection process for electronic devices that are present within the communication range of the mobile terminal 101 and are capable of being connected to the mobile terminal 101 for communication.

[0148] In S1803, the CPU 205 determines whether or not the device information of the target device has been acquired. If the CPU 205 determines that the device information of the target device has been acquired, the process proceeds to S1804. If the CPU 205 determines that the device information of the target device has not been acquired, the CPU 205 displays a notice on the display unit 201, for example, that the electronic device to which the transmission is to be made cannot be found, and then ends this transmission process.

[0149] In S1804, CPU 205 determines whether or not the usage information has not been transmitted to the target device. The determination in this step can be made based on whether or not the connected device list includes information of an electronic device whose registration result information 1504 is "registration completed" and whose transmission flag 1505 is "not transmitted." If CPU 205 determines that the usage information has not been transmitted to the target device, it moves the process to S1204. If CPU 205 determines that the usage information has not been transmitted to the target device, that is, that the usage information has been transmitted to the target device or the target device has not been officially registered, it displays a notice on display unit 201 that the usage information cannot be transmitted, and completes this transmission process.

[0150] After transmitting the usage information in S1204, the CPU 205 updates the transmitted flag 1505 of the information of the target device included in the connected device list to "transmitted" in S1805, and ends this transmission process.

[0151] In this way, it is possible to provide untransmitted usage information for a target device that is connected for communication with the mobile terminal 101, and to make the target device available for using cloud services.

[0152] [Variation 3] In the above-described embodiment and modified example, an electronic device that is to be registered for use with a cloud service receives input of any text information as a passcode in a registration request, and then requests input of the text information as a passcode on an authentication page. That is, in the above-described embodiment, the user is required to input the same passcode in both the request step 621 and the authentication step 622. In addition, in consideration of the security and robustness of the cloud service, it is preferable that the passcode is set to text that is not easily predictable, but the use of such a passcode by requiring it each time may give the user an impression of cumbersomeness. In addition, since a passcode that is not easily predictable is difficult for a user to remember, for example, the user may forget the passcode between the time of inputting authentication information and the time of inputting the passcode on the authentication page.

[0153] In the support system of this modification, in order to improve the user's convenience in the authentication step 622, when the authentication page is displayed on the mobile terminal 101, the passcode input by the user as authentication information is controlled to be input as a default value in the text box 711. This control is realized by the CPU 205 storing the input text information in the RAM 207 as authentication information in S905 of the request step processing, for example, and temporarily storing the same text information in the clipboard. The text information related to the authentication information temporarily stored in the clipboard is read by the CPU 205 when the authentication page is displayed in S1102 of the authentication step processing, and is set as the input value of the text box 711. In this way, when the authentication page is displayed on the display unit 201, the passcode set by the user in the request step 621 is input in the text box 711. At this time, the CPU 205 may cause the display unit 201 to display a notice indicating that the passcode has been pasted from the clipboard. Therefore, the user can formally register the electronic device currently being provisionally registered in the CPU 502 of the management apparatus 103 by operating the OK button 712 without changing the input contents in the text box 711 .

[0154] In addition, by adopting such an embodiment, it is possible to eliminate the need for the user to memorize a passcode, and it is also possible to use, for example, text information randomly generated by the CPU 205 when accepting input of authentication information.

[0155] In this modified example, the temporary storage of authentication information is realized by using the clipboard function (copy-paste function module 312) provided by the OS 310, but the present invention is not limited to this. For example, the present invention can be implemented by temporarily storing authentication information in a data storage area (shared folder, etc.) that is provided for a dedicated application and can be referenced by other applications.

[0156] In this modified example, the temporarily stored authentication information is automatically input into the text box 711 of the authentication page, but the authentication information may simply be temporarily stored in a clipboard or the like and the user may paste it. In this case, the display unit 201 of the mobile terminal 101 may be notified that the authentication information can be input by pasting in conjunction with the display of the authentication page.

[0157] [Variation 4] In the above-described embodiment and modified example, when registering an electronic device to be used for a cloud service, the mobile terminal 101 is communicatively connected to the electronic device to receive device information, but the implementation of the present invention is not limited to this. The device information may be acquired, for example, by displaying a code image generated by converting the device information on a display device provided in the electronic device, and converting the image information obtained by capturing the code image with an imaging unit (not shown) of the mobile terminal 101.

[0158] [Variation 5] In the above-described embodiment and modified example, the information accepted for input on the authentication page is only the passcode among the email address and passcode entered as authentication information, but the present invention is not limited to this. The information accepted on the authentication page may also include an email address. In other words, the information requested to be entered by the user in the authentication step 622 may be at least a part of the information entered as authentication information.

[0159] [Variation 6] In the above-described embodiment, from the viewpoint of user authentication, the transmission of information related to authentication information setting is performed by calling the device provisional registration API in a dedicated application, and the transmission of information related to passcode confirmation is performed by HTTP via an authentication page. In addition, from the viewpoint of electronic device registration to a cloud service, the reception of usage information is performed as a response to the calling of the device provisional registration API in a dedicated application, and the reception of information of the connection destination for authentication (authentication URL) is performed via email. That is, the above-described embodiment and modified example have described a mode in which some information transmission and reception related to the registration sequence is not completed by a dedicated application, but the implementation of the present invention is not limited to this. For example, the transmission and reception of information can be configured to be completed within the dedicated application by using the information transmission and reception function of the dedicated application. In this case, the dedicated application does not need to monitor the processing related to the browser in the mobile terminal 101 or the operation input performed.

[0160] [Variation 7] In the above-described embodiment and modified example, in the control process, the registration result information indicating whether or not the formal registration of the electronic device has been completed is acquired by calling the device registration completion confirmation API from the mobile terminal 101. However, the embodiment of the present invention is not limited to this, and it goes without saying that the registration result information may be transmitted from the management device 103 to the mobile terminal 101 at the stage when the formal registration is completed.

[0161] [Variation 8] In the above-described embodiment and modified example, a part of the processing of the registration sequence is executed by executing a dedicated application, but the implementation of the present invention is not limited to this. A series of processes related to the mobile terminal 101 in the registration sequence may be provided to the mobile terminal 101 as a browser-based Web application so that the processes are completed in the browser.

[0162] [Summary of the embodiment and modifications] The disclosure of this specification includes the following information processing device, control method, program, and support system. (Item 1) An information processing device that registers an electronic device that uses a predetermined service in association with a user, a first acquisition means for acquiring device information relating to the electronic device from the electronic device; a first transmission means for transmitting a registration request for the electronic device to a management device that manages a user and devices registered in association with the user for the predetermined service, the registration request including the device information acquired by the first acquisition means; a second acquisition means for acquiring from the management device usage information required for the electronic device to use the predetermined service; a second transmission means for transmitting the usage information acquired by the second acquisition means to the electronic device on condition that the registration of the electronic device by the management device is completed based on the registration request; 13. An information processing device comprising: (Item 2) a confirmation unit for inquiring of the management device as to whether or not the registration of the electronic device has been completed; The second transmission means transmits the usage information to the electronic device when a result of the inquiry by the confirmation means indicates completion of registration. 2. The information processing device according to item 1, (Item 3) the registration request further includes authentication information for authenticating a user who performs registration; the information processing device further includes a third acquisition means for acquiring information on a connection destination for authentication issued by the management device based on the registration request; The authentication destination is configured to request input of at least a part of the authentication information; The information processing device further includes a third transmission means for communicating with the authentication destination and inputting and transmitting at least a part of the authentication information, The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination. 3. The information processing device according to item 1 or 2. (Item 4) 4. The information processing device according to item 3, wherein the acquisition by the third acquisition means and the acquisition by the second acquisition means, and the transmission by the third transmission means and the transmission by the first transmission means are performed using different communication methods. (Item 5) the registration request further includes authentication information for authenticating a user who performs registration; The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination issued based on the registration request. 3. The information processing device according to item 1 or 2. (Item 6) 6. The information processing device according to any one of items 3 to 5, further comprising an input unit for accepting an input of the authentication information. (Item 7) The authentication information includes the user's contact information and a passcode; The registration of the electronic device by the management device is completed on the condition that the passcode is input at the authentication connection destination notified to the user's contact information. 7. The information processing device according to any one of items 3 to 6, (Item 8) the registration request further includes authentication information for authenticating a user who performs registration; The information processing device includes: an input means for receiving an input of the authentication information; a storage means for temporarily storing the authentication information received by the input means; a third acquisition means for acquiring information on a connection destination for authentication issued by the management device based on the registration request; means for communicating with the authentication destination on condition that information on the authentication destination is acquired by the third acquisition means; and The authentication destination is configured to request input of at least a part of the authentication information; The information processing device includes: a means for inputting at least a part of the authentication information temporarily stored in the storage means when a communication connection is established with the authentication destination; A third transmission means for transmitting the input information; and The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination. 3. The information processing device according to item 1 or 2. (Item 9) The information processing device further includes an establishment unit for establishing a communication connection between the information processing device and the electronic device, the first acquisition means acquires the device information on the condition that a communication connection between the information processing device and the electronic device is established; The second transmission means transmits the usage information to the electronic device on condition that registration of the electronic device by the management device is completed and the established communication connection is maintained. 9. The information processing device according to any one of items 1 to 8, (Item 10) a storage unit configured to store the usage information when the registration of the electronic device by the management device is completed but the established communication connection is not maintained; The second transmission means transmits the usage information stored in the storage means to the electronic device when the communication connection between the information processing device and the electronic device is re-established by the establishment means. 10. The information processing device according to item 9, (Item 11) an establishment unit for establishing a communication connection between the information processing device and the electronic device; A storage means for storing the usage information; and the first acquisition means acquires the device information on the condition that a communication connection between the information processing device and the electronic device has been established; The second transmission means transmits the usage information stored in the storage means to the electronic device on condition that a communication connection between the information processing device and the electronic device is established after the registration of the electronic device by the management device is completed. 9. The information processing device according to any one of items 1 to 8, (Item 12) a storage means for storing the device information acquired by the first acquisition means; a selection unit that receives a selection of an electronic device that makes the registration request from among the electronic devices whose device information is stored in the storage unit, The first transmission means transmits the registration request including the device information corresponding to the electronic device selected by the selection means. 12. The information processing device according to any one of items 1 to 11, (Item 13) The storage means further stores, in association with the device information, information indicating whether the usage information has been transmitted to a device corresponding to the device information; The selection means excludes, from among the devices whose device information is stored in the storage means, the device to which the usage information has been transmitted, from selection targets. 13. The information processing device according to item 12, (Item 14) 14. The information processing device according to item 12 or 13, wherein when the device information is acquired by the first acquisition means, if the storage means already stores the same device information, the storage means does not store the acquired device information. (Item 15) 15. The information processing device according to any one of items 1 to 14, wherein the first acquisition means acquires the device information by capturing an image of a code displayed on the electronic device. (Item 16) The information processing device according to any one of items 1 to 15, characterized in that the specified service is a service provided by a server when the electronic device communicates with the server without going through the information processing device. (Item 17) A method for controlling an information processing device that registers an electronic device that uses a predetermined service in association with a user, comprising: a first acquisition step of acquiring device information related to the electronic device from the electronic device; a first transmission step of transmitting a registration request for the electronic device to a management device that manages a user and devices registered in association with the user for the predetermined service, the registration request including the device information acquired in the first acquisition step; a second acquisition step of acquiring, from the management device, usage information necessary for the electronic device to use the predetermined service; a second transmission step of transmitting the usage information acquired in the second acquisition step to the electronic device on condition that the registration of the electronic device by the management device has been completed based on the registration request; A control method comprising the steps of: (Item 18) A program for causing a computer to function as each of the means of the information processing device according to any one of items 1 to 16. (Item 19) A support system for supporting registration associated with a user of an electronic device that uses a predetermined service, comprising: the support system includes a management device that manages users and devices registered in association with the users for the predetermined service, and an information processing device that is capable of communicating with the management device and the electronic device; The information processing device includes: a first acquisition means for acquiring device information relating to the electronic device from the electronic device; a first transmission means for transmitting a registration request for the electronic device, the registration request including the device information acquired by the first acquisition means, to the management device; a second acquisition means for acquiring from the management device usage information required for the electronic device to use the predetermined service; a second transmission means for transmitting the usage information acquired by the second acquisition means to the electronic device; having The management device includes: a receiving means for receiving the registration request transmitted by the first transmitting means; a third transmission means for generating the usage information based on reception of the registration request and transmitting the usage information to the information processing device; a registration means for registering the electronic device in association with a user based on the registration request; having The second transmission means transmits the usage information to the electronic device on condition that the registration means has completed the registration of the electronic device. A support system comprising:

[0163] [Other embodiments] The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0164] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0165] 101: mobile terminal, 102: imaging device, 103: management device, 105: device DB, 106: network, 201: display unit, 204: input I / F, 205: CPU, 206: ROM, 207: RAM, 208: storage device, 209: network I / F

Claims

1. An information processing device that registers an electronic device that uses a predetermined service in association with a user, a first acquisition means for acquiring device information relating to the electronic device from the electronic device; a first transmission means for transmitting a registration request for the electronic device to a management device that manages a user and devices registered in association with the user for the predetermined service, the registration request including the device information acquired by the first acquisition means; a second acquisition means for acquiring from the management device usage information required for the electronic device to use the predetermined service; a second transmission means for transmitting the usage information acquired by the second acquisition means to the electronic device on condition that the registration of the electronic device by the management device has been completed based on the registration request; 13. An information processing device comprising:

2. a confirmation unit for inquiring of the management device as to whether or not the registration of the electronic device has been completed; The second transmission means transmits the usage information to the electronic device when a result of the inquiry by the confirmation means indicates completion of registration.

2. The information processing apparatus according to claim 1,

3. the registration request further includes authentication information for authenticating a user who performs registration; the information processing device further includes a third acquisition means for acquiring information on a connection destination for authentication issued by the management device based on the registration request; The authentication destination is configured to request input of at least a part of the authentication information; The information processing device further includes a third transmission means for connecting to the authentication destination and inputting and transmitting at least a part of the authentication information, The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination.

2. The information processing apparatus according to claim 1,

4. 4. The information processing apparatus according to claim 3, wherein the acquisition by the third acquisition means and the acquisition by the second acquisition means, and the transmission by the third transmission means and the transmission by the first transmission means are performed using different communication methods.

5. the registration request further includes authentication information for authenticating a user who performs registration; The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination issued based on the registration request.

2. The information processing apparatus according to claim 1,

6. 4. The information processing apparatus according to claim 3, further comprising an input unit for receiving an input of the authentication information.

7. The authentication information includes the user's contact information and a passcode; The registration of the electronic device by the management device is completed on the condition that the passcode is input at the authentication connection destination notified to the user's contact information.

4. The information processing apparatus according to claim 3.

8. the registration request further includes authentication information for authenticating a user who performs registration; The information processing device includes: an input means for receiving an input of the authentication information; a storage means for temporarily storing the authentication information received by the input means; a third acquisition means for acquiring information on a connection destination for authentication issued by the management device based on the registration request; means for communicating with the authentication destination on condition that information on the authentication destination is acquired by the third acquisition means; and The authentication destination is configured to request input of at least a part of the authentication information; The information processing device includes: a means for inputting at least a part of the authentication information temporarily stored in the storage means when a communication connection is established with the authentication destination; a third transmission means for transmitting the input information; and The registration of the electronic device by the management device is completed on the condition that at least a part of the authentication information is input to the authentication connection destination.

2. The information processing apparatus according to claim 1,

9. The information processing device further includes an establishment unit for establishing a communication connection between the information processing device and the electronic device, the first acquisition means acquires the device information on the condition that a communication connection between the information processing device and the electronic device is established; The second transmission means transmits the usage information to the electronic device on condition that registration of the electronic device by the management device is completed and the established communication connection is maintained.

2. The information processing apparatus according to claim 1,

10. a storage unit configured to store the usage information when the registration of the electronic device by the management device is completed but the established communication connection is not maintained; The second transmission means transmits the usage information stored in the storage means to the electronic device when the communication connection between the information processing device and the electronic device is re-established by the establishment means.

10. The information processing apparatus according to claim 9,

11. an establishment unit for establishing a communication connection between the information processing device and the electronic device; A storage means for storing the usage information; and the first acquisition means acquires the device information on the condition that a communication connection between the information processing device and the electronic device has been established; The second transmission means transmits the usage information stored in the storage means to the electronic device on condition that a communication connection between the information processing device and the electronic device is established after the registration of the electronic device by the management device is completed.

2. The information processing apparatus according to claim 1,

12. a storage unit for storing the device information acquired by the first acquisition unit; a selection unit that receives a selection of an electronic device that makes the registration request from among the electronic devices whose device information is stored in the storage unit, The first transmission means transmits the registration request including the device information corresponding to the electronic device selected by the selection means.

2. The information processing apparatus according to claim 1,

13. The storage means further stores, in association with the device information, information indicating whether the usage information has been transmitted to a device corresponding to the device information; The selection means excludes, from among the devices whose device information is stored in the storage means, the device to which the usage information has been transmitted, from selection targets.

13. The information processing apparatus according to claim 12.

14. 13. The information processing apparatus according to claim 12, wherein when the device information is acquired by the first acquisition means, the retention means does not retain the acquired device information if the same device information is already retained.

15. The information processing apparatus according to claim 1 , wherein the first acquisition means acquires the device information by capturing an image of a code displayed on the electronic device.

16. 2 . The information processing apparatus according to claim 1 , wherein the predetermined service is a service provided by a server when the electronic device is connected to the server for communication without going through the information processing apparatus.

17. A method for controlling an information processing device that registers an electronic device that uses a predetermined service in association with a user, comprising: a first acquisition step of acquiring device information related to the electronic device from the electronic device; a first transmission step of transmitting a registration request for the electronic device to a management device that manages a user and devices registered in association with the user for the predetermined service, the registration request including the device information acquired in the first acquisition step; a second acquisition step of acquiring, from the management device, usage information required for the electronic device to use the predetermined service; a second transmission step of transmitting the usage information acquired in the second acquisition step to the electronic device on condition that the registration of the electronic device by the management device has been completed based on the registration request; A control method comprising the steps of:

18. A program for causing a computer to function as each of the means of the information processing apparatus according to any one of claims 1 to 16.

19. A support system for supporting registration associated with a user of an electronic device that uses a predetermined service, comprising: the support system includes a management device that manages users and devices registered in association with the users for the predetermined service, and an information processing device that is capable of communicating with the management device and the electronic device; The information processing device includes: a first acquisition means for acquiring device information relating to the electronic device from the electronic device; a first transmission means for transmitting a registration request for the electronic device, the registration request including the device information acquired by the first acquisition means, to the management device; a second acquisition means for acquiring from the management device usage information required for the electronic device to use the predetermined service; a second transmission means for transmitting the usage information acquired by the second acquisition means to the electronic device; having The management device includes: a receiving means for receiving the registration request transmitted by the first transmitting means; a third transmission means for generating the usage information based on reception of the registration request and transmitting the usage information to the information processing device; a registration means for registering the electronic device in association with a user based on the registration request; having The second transmission means transmits the usage information to the electronic device on condition that the registration of the electronic device by the registration means is completed. A support system comprising:

Images