Information processing device, method, program, and system

Abstract

To allow a service that is provided via a network to be easily used by a device.SOLUTION: An information processing device includes: a code distribution unit that generates and distributes a code including information on an application and information used for registering a device; a device registration unit that when obtaining the information used for registering the device from the device, notifies the device of information for identifying the device; and a coordination unit that obtains the information on the application and the information for identifying the device, from the device and registers the device in association with the application.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, method, program, and system.

Background Art

[0002] Conventionally, cloud services that provide computer resources via a network such as the Internet have been known. A user uses a cloud service using a device at hand. In order to use such a cloud service, the user has to perform settings such as registering the device with the cloud service (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, on a device with a poor user interface (for example, a device without a display), it is not easy for the user to operate the device to perform settings.

[0005] Therefore, an object of the present invention is to facilitate the use of services provided via a network by a device.

Means for Solving the Problems

[0006] An information processing apparatus according to an embodiment of the present invention includes a code distribution unit that generates and distributes a code including information related to an application and information used for device registration, a device registration unit that, when acquiring information used for device registration from the device, notifies the device of information for identifying the device, and a cooperation unit that acquires information related to the application and information for identifying the device from the device and registers the device in association with the application.

[0007] According to the present invention, it facilitates the use of services provided via a network by a device.

Brief Description of Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0010] FIG. 1 is a diagram for explaining an overview of a service according to an embodiment of the present invention. A user (a customer user, A1 in FIG. 1) uses a cloud service provided by servers 11 to 15 (hereinafter also referred to as server 10) using a device 20. Also, a device partner (B in FIG. 1) registers a workflow (WF) application in a tenant (a group of devices using the cloud service) to which the user belongs. Further, a developer of the workflow (WF) application (C (cloud service partner) in FIG. 1) develops a workflow (WF) application in which permission for QR code linkage setting and data types that can be input (such as still images or videos) are set using a WF application development tool. A2 is a customer administrator, and D is a device sales company. Hereinafter, the cloud service provided by server 10 as a service provided to device 20 via a network will be described as an example. However, the service used by device 20 is not limited to this, and any service that uses functions provided via a network may be used. For example, by installing server 10 in the same network as device 20, server 10 may provide an on-premises service to device 20.

[0011] <System Configuration> FIG. 2 is an overall configuration diagram according to an embodiment of the present invention. System 1 includes server 10 and device 20. Server 10 and device 20 are communicably connected via a communication network N. Each will be described below.

[0012] <<Server>> Server 10 (an example of an information processing device) performs processing for associating an application provided by a cloud service with device 20.

[0013] The device group described in the embodiments merely shows one of the multiple computing environments for implementing the embodiments disclosed in this specification. In one embodiment, the server 10 includes multiple computing devices such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link including a network or shared memory, and implement the processes disclosed in this specification.

[0014] <<Device>> The device 20 is a device used by a user who utilizes cloud services. For example, the device 20 is a device that has a photographing function and does not have a display function (e.g., an omnidirectional imaging device).

[0015] Note that the device 20 is not limited to an omnidirectional imaging device as long as it is a device equipped with a communication function. The device 20 may be, for example, an output device such as a PJ (Projector), an IWB (Interactive White Board), a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collection device, a medical device, a network home appliance, a connected car, a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

[0016] <Hardware Configuration> FIG. 3 is a hardware configuration diagram of an information processing apparatus (in the case of a server) 10 according to an embodiment of the present invention.

[0017] As shown in FIG. 3, the server 10 is constructed by a computer and includes a CPU 1001, a ROM 1002, a RAM 1003, an HD 1004, an HDD (Hard Disk Drive) controller 1005, a display 1006, an external device connection I / F (Interface) 1007, a network I / F 1008, a data bus 1009, a keyboard 1010, a pointing device 1011, a DVD-RW (Digital Versatile Disk Rewritable) drive 1013, and a media I / F 1015, as shown in FIG. 3.

[0018] Among these, the CPU 1001 controls the operation of the entire server 10. The ROM 1002 stores programs used for driving the CPU 1001 such as the IPL. The RAM 1003 is used as a work area for the CPU 1001. The HD 1004 stores various data such as programs. The HDD controller 1005 controls the reading or writing of various data to and from the HD 1004 according to the control of the CPU 1001. The display 1006 displays various information such as a cursor, menu, window, characters, or images. The external device connection I / F 1007 is an interface for connecting various external devices. External devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, and the like. The network I / F 1008 is an interface for performing data communication using the communication network N. The bus line 1009 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 1001 shown in FIG. 3.

[0019] Also, the keyboard 1010 is a type of input means having a plurality of keys for inputting characters, numerical values, various instructions, etc. The pointing device 1011 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 1013 controls reading or writing of various data with respect to the DVD-RW 1012 as an example of a removable recording medium. Note that it is not limited to DVD-RW, and it may be DVD-R or the like. The media I / F 1015 controls reading or writing (storage) of data with respect to the recording medium 1014 such as a flash memory.

[0020] FIG. 4 is a hardware configuration diagram of a device (in the case of an omnidirectional imaging device) 20 according to an embodiment of the present invention.

[0021] Hereinafter, the omnidirectional imaging device 20 is an omnidirectional (360-degree) omnidirectional imaging device using two imaging elements, but the number of imaging elements may be two or more. Also, it is not necessarily a device dedicated to omnidirectional imaging, and a substantially omnidirectional imaging unit may be attached to a normal digital camera, smartphone, etc. to have the same function as the omnidirectional imaging device 20.

[0022] As shown in FIG. 4, the omnidirectional imaging device 20 includes an imaging unit 2001, an image processing unit 2004, an imaging control unit 2005, a microphone 2006, an audio processing unit 2007, a CPU (Central Processing Unit) 2009, a ROM (Read Only Memory) 2010, an SRAM (Static Random Access Memory) 2011, a DRAM (Dynamic Random Access Memory) 2012, an operation unit 2013, an external device connection I / F 2014, a communication unit 2015, an antenna 2015a, an electronic compass, a gyro sensor, an acceleration sensor, and a concave terminal for Micro USB.

[0023] Among these, the imaging unit 2001 includes wide-angle lenses (so-called fish-eye lenses) 2002a and 2002b each having an angle of view of 180° or more for forming a hemispherical image, and two image sensors 2003a and 2003b provided corresponding to each wide-angle lens. The image sensors 2003a and 2003b are image sensors such as CMOS (Complementary Metal Oxide Semiconductor) sensors or CCD (Charge Coupled Device) sensors that convert the optical image by the fish-eye lenses 2002a and 2002b into image data of an electrical signal and output it, a timing generation circuit that generates a horizontal or vertical synchronization signal, a pixel clock, etc. of this image sensor, and a register group in which various commands, parameters, etc. necessary for the operation of this image sensor are set.

[0024] The image sensors 2003a and 2003b of the imaging unit 2001 are each connected to the image processing unit 2004 via a parallel I / F bus. On the other hand, the image sensors 2003a and 2003b of the imaging unit 2001 are connected to the imaging control unit 2005 via a serial I / F bus (such as an I2C bus). The image processing unit 2004, the imaging control unit 2005, and the audio processing unit 2007 are connected to the CPU 2009 via the bus 2008. Further, the ROM 2010, SRAM 2011, DRAM 2012, operation unit 2013, external device connection I / F (Interface) 2014, communication unit 2015, and acceleration / azimuth sensor 2016, etc. are also connected to the bus 2008.

[0025] The image processing unit 2004 takes in the image data output from the image sensors 2003a and 2003b through the parallel I / F bus, performs predetermined processing on each image data, and then synthesizes these image data to create data of an orthographic cylindrical projection image.

[0026] The imaging control unit 2005 generally sets commands and the like in the register groups of the image sensors 2003a and 2003b using the I2C bus, with the imaging control unit 2005 as the master device and the image sensors 2003a and 2003b as slave devices. The necessary commands and the like are received from the CPU 2009. Also, the imaging control unit 2005 similarly uses the I2C bus to capture status data and the like of the register groups of the image sensors 2003a and 2003b and send it to the CPU 2009.

[0027] In addition, the imaging control unit 2005 instructs the image sensors 2003a and 2003b to output image data at the timing when the shutter button of the operation unit 2013 is pressed. Depending on the omnidirectional imaging device 20, it may have a preview display function using a display (e.g., the display of a smartphone) or a function corresponding to video display. In this case, the output of image data from the image sensors 2003a and 2003b is continuously performed at a predetermined frame rate (frames / minute).

[0028] Also, as will be described later, the imaging control unit 2005 also functions as synchronization control means for synchronizing the output timing of the image data of the image sensors 2003a and 2003b in cooperation with the CPU 2009. In this embodiment, the omnidirectional imaging device 20 is not provided with a display, but a display unit may be provided.

[0029] The microphone 2006 converts sound into sound (signal) data. The sound processing unit 2007 captures the sound data output from the microphone 2006 through the I / F bus and performs predetermined processing on the sound data.

[0030] The CPU 2009 controls the overall operation of the omnidirectional imaging device 20 and executes necessary processes. The ROM 2010 stores various programs for the CPU 2009. The SRAM 2011 and the DRAM 2012 are working memories, which store programs executed by the CPU 2009, data during processing, etc. In particular, the DRAM 2012 stores image data during processing in the image processing unit 2004 and data of the processed orthographic cylindrical projection image.

[0031] The operation unit 2013 is a general term for operation buttons such as a shutter button. By operating the operation unit 2013, the user inputs various shooting modes, shooting conditions, etc.

[0032] The external device connection I / F 2014 is an interface for connecting various external devices. External devices in this case are, for example, a USB (Universal Serial Bus) memory, a PC (Personal Computer), etc. The data of the orthographic cylindrical projection image stored in the DRAM 2012 is recorded on an external medium via this network I / F 2014, or transmitted to an external terminal (device) such as a smartphone via the network I / F 2014 as needed.

[0033] The communication unit 2015 communicates with an external terminal (device) such as a smartphone by means of short-range wireless communication technologies such as Wi-Fi, NFC (Near Field Communication), and Bluetooth (registered trademark) via an antenna 2015a provided in the omnidirectional imaging device 20. Also by this communication unit 2015, the data of the orthographic cylindrical projection image can be transmitted to an external terminal (device) such as a smartphone.

[0034] The acceleration and azimuth sensor 2016 calculates the azimuth of the omnidirectional imaging device 20 from the earth's magnetism and outputs azimuth information. This azimuth information is an example of related information (metadata) conforming to Exif and is used for image processing such as image correction of the captured image. Note that the related information also includes each data such as the shooting date and time of the image and the data volume of the image data. Further, the acceleration and azimuth sensor 2016 is a sensor that detects changes in angles (Roll angle, Pitch angle, Yaw angle) accompanying the movement of the omnidirectional imaging device 20. The change in angle is an example of related information (metadata) conforming to Exif and is used for image processing such as image correction of the captured image. Furthermore, the acceleration and azimuth sensor 2016 is a sensor that detects acceleration in three axial directions. The omnidirectional imaging device 20 calculates the attitude (angle with respect to the gravity direction) of its own device (omnidirectional imaging device 20) based on the acceleration detected by the acceleration and azimuth sensor 2016. By providing the omnidirectional imaging device 20 with the acceleration and azimuth sensor 2016, the accuracy of image correction is improved.

[0035] <Functional block> FIG. 5 is a functional block diagram of a server and a device according to an embodiment of the present invention.

[0036] <<Server>> The server 10 includes a code distribution unit 101, a device registration unit 102, a cooperation unit 103, and a storage unit 104. Further, the server 10 functions as the code distribution unit 101, the device registration unit 102, and the cooperation unit 103 by executing a program.

[0037] The code distribution unit 101 generates and distributes a code (for example, a QR code (registered trademark)) including information on an application provided by a cloud service and information used for registration of a device. Hereinafter, the case of using a two-dimensional code as the code will be described as an example, but it is not limited thereto, and a one-dimensional code, a symbol, a character string, a numerical string, an image, or the like may be used.

[0038] Describe "information related to an application". Information related to an application includes information for identifying the application (application ID). Note that information related to an application can further include the type of data that can be input into the application (such as still images or videos) and an identifier for determining availability.

[0039] Describe "information used for device registration". Information used for device registration includes the connection destination of a site for obtaining information for identifying the device and a token for accessing the site (access token).

[0040] The device registration unit 102 registers the device 20. Specifically, when the device registration unit 102 obtains information used for device registration from the device 20, it notifies the device 20 of information for identifying the device (for example, device ID). Note that the device registration unit 102 can notify the device 20 of a certificate together with information for identifying the device (for example, device ID).

[0041] The cooperation unit 103 obtains information related to the application and information for identifying the device from the device 20, and registers the device 20 by associating it with the application. Specifically, the cooperation unit 103 associates the application provided by the cloud service with the device 20 and stores it in the storage unit 104.

[0042] In the storage unit 104, information for identifying the device 20 (for example, device ID) and information for identifying the application provided by the cloud service (for example, application ID) are stored in association with each other. Further, the type of data that can be input into the application (such as still images or videos) may be stored in association with the storage unit 104.

[0043] <<Device>> Device 20 includes a device registration unit 201, a cooperation unit 202, and a photographing unit 203. Further, by executing a program, device 20 functions as device registration unit 201, cooperation unit 202, and photographing unit 203.

[0044] The device registration unit 201 requests the server 10 to register the device 20. Specifically, the device registration unit 201 notifies the server 10 of information used for registering the device obtained by reading a code (that is, obtained from the code read by the photographing unit 203). Further, the device registration unit 201 obtains information (for example, device ID) for identifying the device from the server 10.

[0045] The cooperation unit 202 requests the server 10 to register the device 20 by associating it with an application provided by a cloud service. Specifically, the cooperation unit 202 notifies the server 10 of information regarding the application obtained by reading a code (that is, obtained from the code read by the photographing unit 203), and information (for example, device ID) for identifying the device obtained from the server 10 (that is, obtained by the device registration unit 201).

[0046] The photographing unit 203 reads a code (for example, QR code) generated and distributed by the code distribution unit 101 of the server 10.

[0047] <Processing method> FIG. 6 is a sequence diagram of the process of associating a device and an application according to an embodiment of the present invention. It will be described separately for the <WF app registration phase> and the <WF app execution phase>.

[0048] <WF app registration phase> The process of registering a workflow (WF) application provided by a cloud service by associating it with the device 20 will be described. Note that the workflow (WF) application is an application that performs predetermined processing on the server 10.

[0049] Note that the developer of the WF application (C (cloud service partner) in FIG. 1) develops a WF application that sets the permission for QR code linking settings and the data types that can be input (such as still images or videos) using the WF application development tool. Also, the device partner (B in FIG. 1) registers the WF application with the tenant (group of devices that use cloud services) to which the user belongs.

[0050] In step 11 (S11), the server (code distribution unit) 10 generates and distributes a code (for example, a QR code) that includes information about the application provided by the cloud service and information used for device registration.

[0051] Specifically, the user logs in to a site (IoT site in FIG. 1) for setting the application on a PC (personal computer) 30, selects a WF application to be linked with the device 20 (device plug-in in FIG. 1), and issues a QR code.

[0052] In step 12 (S12), it is assumed that the shutter button of the device 20 is pressed.

[0053] In step 13 (S13), the device 20 reads the QR code distributed by the server (code distribution unit) 10 in S11 and displayed on the PC 30.

[0054] In step 14 (S14), the device 20 obtains the connection destination of the site for obtaining information for identifying the device included in the QR code, a token (access token) for accessing the site, and information about the application (for example, application ID (here, "App 1") and input type (here, "still image")).

[0055] In step 15 (S15), device 20 requests the server (device registration unit) 10 to register device 20. Specifically, device 20 notifies the server 10 of the information used for registering the device obtained by reading the code in S14 (specifically, sends the serial number of device 20 to the connection destination using the access token).

[0056] In step 16 (S16), the server (device registration unit) 10 notifies device 20 of the information for identifying the device (device ID (here, "device A")) and the certificate.

[0057] In step 17 (S17), device 20 requests the server (linkage unit) 10 to register by linking device 20 to the application. Specifically, device 20 notifies the server (linkage unit) 10 of the application ID (that is, "app 1"), the input type (that is, "still image"), and the device ID (that is, "device A") together with the certificate in S16. Then, the server (linkage unit) 10 registers by linking the application ID, the input type, and the device ID (see FIG. 8).

[0058] <WF application execution phase> The process of executing the workflow (WF) application will be described.

[0059] Assume that the shutter button of device 20 is pressed in step 21 (S21).

[0060] In step 22 (S22), device 20 obtains a URL (Uniform Resource Locator). Specifically, device 20 obtains the URL from the server (device registration unit) 10.

[0061] In step 23 (S23), device 20 uploads the image taken in S21 to the URL in S22.

[0062] In step 24 (S24), the device 20 notifies the server (device registration unit) 10 of the shooting. Specifically, the device 20 notifies the server (device registration unit) 10 of the device ID (that is, "Device A") and the URL.

[0063] In step 25 (S25), the server (device registration unit) 10 sends the device ID and the URL obtained in S24 to the server (coordination unit) 10.

[0064] In step 26 (S26), the server (coordination unit) 10 downloads the image uploaded to the URL obtained in S25.

[0065] In step 27 (S27), the server (coordination unit) 10 causes the workflow (WF) application to execute a job. Specifically, the server (coordination unit) 10 notifies the application associated with the device ID (that is, "App 1") of the input type (that is, "still image").

[0066] In step 28 (S28), the WF application uploads the image to the online storage service. Note that the upload and storage of the image to the online storage service is an example of a service provided via the network.

[0067] FIG. 7 is a sequence diagram of the linking process between the device and the application according to an embodiment of the present invention. It will be described separately as <preparation>, <WF app setting>, and <WF execution>. Note that the workflow (WF) application is a workflow (WF) application that uploads to the online storage service.

[0068] <Preparation> As preparation, the linking process in FIG. 6 is performed.

[0069] In the workflow (WF) platform provided by server 10, for tenants using the workflow (WF), the registration of device 20 can be performed in advance using the serial number of each device, etc. As a result, the workflow (WF) platform can grasp the devices used by each tenant.

[0070] In step 101 (S101), camera device A 21 (an example of device 20) requests server (WF platform) 10 to register camera device A 21 using the serial number of camera device A 21.

[0071] In step 102 (S102), camera device A 21 requests server (WF platform) 10 to register by associating device A 21 with the WF application.

[0072] In step 103 (S103), camera device B 22 (an example of device 20) requests server (WF platform) 10 to register camera device B 22 using the serial number of camera device B 22.

[0073] In step 104 (S104), camera device B 22 requests server (WF platform) 10 to register by associating device B 22 with the WF application.

[0074] <WF app settings> The settings of the WF application are made.

[0075] In one embodiment of the present invention, the same WF application with different set values can be replicated within a tenant. By associating the replicated application with a device and performing account settings for the online storage service for each application, the WF application called from a specific camera device can be executed using the account of the online storage service associated therewith.

[0076] In step 201 (S201), the PC 30 performs an operation for account linkage (linkage between storage service A and camera device A) on the WF application setting screen provided by the server 10.

[0077] In step 202 (S202), the server 10 requests authentication of the account from the storage service A.

[0078] In step 203 (S203), the storage service A notifies the access token to the server 10.

[0079] In step 204 (S204), the serial number of the camera device A, the storage service A, and the access token are linked and registered.

[0080] In step 205 (S205), the PC 30 performs an operation for account linkage (linkage between storage service B and camera device B) on the WF application setting screen provided by the server 10.

[0081] In step 206 (S206), the server 10 requests authentication of the account from the storage service B.

[0082] In step 207 (S207), the storage service B notifies the access token to the server 10.

[0083] In step 208 (S208), the serial number of the camera device B, the storage service B, and the access token are linked and registered.

[0084] <WF Execution> The WF application is executed.

[0085] In step 301 (S301), the camera device A 21 takes a photo.

[0086] In step 302 (S302), the camera device A 21 notifies the server (WF platform) 10 of the shooting. Specifically, the camera device A 21 notifies the server (WF platform) 10 of the serial number and the still image captured in S301.

[0087] In step 303 (S303), the server (WF platform) 10 acquires the information of the WF application associated with the serial number.

[0088] In step 304 (S304), the server (WF platform) 10 causes the WF application to execute. Specifically, the server (WF platform) 10 notifies the WF application of the storage service A and the access token associated with the serial number.

[0089] In step 305 (S305), the WF application uploads the still image to the storage service A.

[0090] In step 306 (S306), the camera device B 22 takes a photo.

[0091] In step 307 (S307), the camera device B 22 notifies the server (WF platform) of the shooting. Specifically, the camera device B 22 notifies the server (WF platform) 10 of the serial number and the still image captured in S306.

[0092] In step 308 (S308), the server (WF platform) 10 acquires the information of the WF application associated with the serial number.

[0093] In step 309 (S309), the server (WF platform) 10 causes the WF application to execute. Specifically, the server (WF platform) 10 notifies the WF application of the storage service B and the access token associated with the serial number.

[0094] In step 310 (S310), the WF application uploads a still image to the storage service B.

[0095] In this way, the upload is performed to the online storage service associated with the camera device.

[0096] <Data Structure> FIG. 8 is a diagram for explaining the association between the device 20 and the application according to an embodiment of the present invention. As shown in FIG. 8, information for identifying an application (for example, an application ID), an input type (the type of data that can be input to the application (such as a still image or a moving image)), and information for identifying the device 20 (for example, a device ID) are associated and managed.

[0097] <Screen Example> FIG. 9 is an example of a screen according to an embodiment of the present invention. A UI (user interface) for performing authentication processing necessary for account linking of the online storage service is provided. As a result, the workflow application automatically set at the time of photographing is executed, and the upload is performed to the online storage service associated with the camera device used for photographing.

[0098] In step 1001 (S1001), a list of a plurality of workflow applications managed on the tenant is displayed. When any workflow application is selected, the process proceeds to step 1002.

[0099] In step 1002 (S1002), a setting screen of the workflow application is displayed. Each application has setting values regarding storage (storage service, account information, upload destination folder information), which can be set from the setting screen. Also, a QR code for device connection can be displayed for each application, and by reading this with a registered camera device, the camera device can be associated with the workflow application with the online storage service already set up.

[0100] In step 1003 (S1003), a connection screen for the online storage service is displayed. Access to the external service authentication page of the online storage service is made to log in, and the connection with the online storage service is performed.

[0101] Note that in this specification, a workflow application that can upload an image taken by a digital camera to storage on cloud computing has been described. In this specification, an online storage service has been given as an example, but the present invention can be applied to any service that requires account connection in a workflow. For example, it is conceivable to send a message with an attached image by associating with an account of a message queuing service, or to register the achievement of a schedule as a daily report with an attached image by associating with an account of a calendar service.

[0102] Each function of the embodiments described above can be realized by one or more processing circuits. Here, the "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit) designed to execute each function described above, a DSP (digital signal processor), an FPGA (field programmable gate array), and devices such as conventional circuit modules.

[0103] Note that the configurations and the like described in the above embodiments are not limited to the configurations shown here, such as combinations with other elements. Regarding these points, it is possible to make changes without departing from the spirit of the present invention, and they can be appropriately determined according to the application form.

Explanation of Reference Numerals

[0104] 1 System 10 Server 20 Device 21 Camera Device A 22 Camera Device B 30 PC 101 Code Distribution Unit 102 Device Registration Unit 103 Cooperation Unit 104 Storage Unit 201 Device Registration Unit 202 Cooperation Unit 203 Photographing Unit

Claims

1. A code distribution unit that generates and distributes a code including information related to an application and information used for device registration; A device registration unit that, when obtaining information used for device registration from the device, notifies the device of information for identifying the device; A cooperation unit that obtains information related to the application and information for identifying the device from the device, and registers the device in association with the application An information processing apparatus comprising the above.

2. The information processing apparatus according to claim 1, wherein a service that cooperates with the application is changed according to the device when the application is executed.

3. The information processing apparatus according to claim 2, wherein a user interface for performing authentication processing for account cooperation of the service is provided when the application is set.

4. The information processing apparatus according to any one of claims 1 to 3, wherein the information used for device registration includes a connection destination of a site for obtaining information for identifying the device and a token for accessing the site.

5. The information processing apparatus according to any one of claims 1 to 4, wherein the information related to the application includes information for identifying the application.

6. The information processing apparatus according to any one of claims 1 to 5, wherein the device has a photographing function and does not have a display function.

7. The information processing apparatus according to any one of claims 1 to 6, wherein the code is a QR code.

8. A method executed by an information processing apparatus, comprising: Generating and distributing a code including information related to an application and information used for device registration; When obtaining information used for device registration from the device, notifying the device of information for identifying the device; Obtaining information related to the application and information for identifying the device from the device, and registering the device in association with the application Including the above steps.

9. An information processing apparatus A code distribution unit that generates and distributes a code including information related to an application and information used for device registration, A device registration unit that, when acquiring information used for registering the device from the device, notifies the device of information for identifying the device. A cooperation unit that acquires information regarding the application and information for identifying the device from the device, and registers the device in association with the application. A program for causing the above to function.

10. A system including a server and a device, wherein the server includes a code distribution unit that generates and distributes a code including information regarding an application and information used for registering a device, a device registration unit that, when acquiring information used for registering the device from the device, notifies the device of information for identifying the device, and a cooperation unit that acquires information regarding the application and information for identifying the device from the device, and registers the device in association with the application. The server is provided with wherein the device includes a device registration unit that notifies the server of information used for registering the device acquired by reading the code, and acquires information for identifying the device from the server, and a cooperation unit that notifies the server of information regarding the application acquired by reading the code and information for identifying the device acquired from the server. A system provided with the above.

Images