Information processing devices, methods, programs, and systems

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 must 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, it is not easy for a user to operate a device to perform settings on a device with a poor user interface (for example, a device without a display).

[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 is The application comprises: a code distribution unit that generates and distributes a code containing information used to register a device with an application; a device registration unit that, upon obtaining the information used to register the device obtained by reading the code with the device, notifies the device of information for identifying the device; and a linkage unit that associates and registers the information for identifying the device with the application. Upon receiving a notification from the device containing information for identifying the device, the application that has been registered with the information for identifying the device is executed. .

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

Brief Description of the Drawings

[0008] [Figure 1] This is a diagram illustrating the overview of a service related to one embodiment of the present invention. [Figure 2] This is an overall configuration diagram of one embodiment of the present invention. [Figure 3] This is a hardware configuration diagram of an information processing device (server) according to one embodiment of the present invention. [Figure 4] This is a hardware configuration diagram of a device (spherical imaging device) according to one embodiment of the present invention. [Figure 5] This is a functional block diagram of a server and device relating to one embodiment of the present invention. [Figure 6] This is a sequence diagram of the device and application linking process related to the present invention. [Figure 7] This is a sequence diagram of the device and application linking process related to the present invention. [Figure 8] This diagram illustrates the linking of devices and applications related to the present invention. [Figure 9] This is an example of a screen related to one embodiment of the present invention. [Modes for carrying out the invention]

[0009] Embodiments of this disclosure will be described below with reference to the drawings.

[0010] Figure 1 is a diagram illustrating the overview of a service relating to one embodiment of the present invention. A user (customer's user, A1 in Figure 1) uses device 20 to utilize cloud services provided by servers 11-15 (hereinafter also referred to as server 10). A device partner (B in Figure 1) registers a workflow (WF) application to the tenant (group of devices using the cloud service) to which the user belongs. A workflow (WF) application developer (C in Figure 1 (cloud service partner)) develops a workflow (WF) application using a WF application development tool, setting permissions for QR code linkage and the types of data that can be input (still images or videos, etc.). A2 is the customer's administrator, and D is the device sales company. In the following explanation, the cloud service provided by server 10 is used as an example of a service provided to device 20 via the network. However, the services used by device 20 are not limited to this; any service that utilizes functions provided via the network is acceptable. For example, by installing server 10 on the same network as device 20, server 10 may provide on-premise services to device 20.

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

[0012] <<Server>> Server 10 (an example of an information processing device) performs the process of linking applications provided by cloud services with devices 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, server 10 includes a plurality of computing devices such as a server cluster. The plurality of 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>> Device 20 is a device used by a user who utilizes cloud services. For example, 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 device 20 is not limited to an omnidirectional imaging device as long as it is a device equipped with a communication function. 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, as shown in FIG. 3, includes a CPU 1001, a ROM 1002, a RAM 1003, a HD 1004, a 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.

[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, etc. The network I / F 1008 is an interface for 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] The keyboard 1010 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 1011 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The DVD-RW drive 1013 controls the reading or writing of various data to the DVD-RW 1012, which is an example of a removable recording medium. Note that it is not limited to DVD-RW, but may also be DVD-R, etc. The media I / F 1015 controls the reading or writing (storage) of data to the recording medium 1014, such as flash memory.

[0020] Figure 4 is a hardware configuration diagram of a device (in the case of a 360-degree imaging device) 20 according to one embodiment of the present invention.

[0021] In the following, the 360-degree spherical imaging device 20 is defined as a 360-degree (omnidirectional) 360-degree spherical imaging device using two image sensors, but it may use two or more image sensors. Furthermore, it does not necessarily have to be a device dedicated to omnidirectional imaging; a standard digital camera or smartphone can be fitted with an aftermarket omnidirectional imaging unit to achieve essentially the same functionality as the 360-degree spherical imaging device 20.

[0022] As shown in Figure 4, the 360-degree imaging device 20 consists of an imaging unit 2001, an image processing unit 2004, an imaging control unit 2005, a microphone 2006, a sound 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 interface 2014, a communication unit 2015, an antenna 2015a, an electronic compass, a gyro sensor, an acceleration sensor, and a recessed terminal for Micro USB.

[0023] Of these, the imaging unit 2001 includes two wide-angle lenses (so-called fisheye lenses) 2002a and 2002b, each having a field of view of 180° or more for forming a hemispherical image, and two image sensors 2003a and 2003b, each corresponding to a wide-angle lens. The image sensors 2003a and 2003b include an image sensor such as a CMOS (Complementary Metal Oxide Semiconductor) sensor or a CCD (Charge Coupled Device) sensor that converts the optical image from the fisheye lenses 2002a and 2002b into electrical signal image data and outputs it, a timing generation circuit that generates horizontal or vertical synchronization signals and pixel clocks for these image sensors, and a group of registers in which various commands and parameters necessary for the operation of these image sensors 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 sound processing unit 2007 are connected to the CPU 2009 via bus 2008. Furthermore, ROM 2010, SRAM 2011, DRAM 2012, the control unit 2013, the external device connection I / F (Interface) 2014, the communication unit 2015, and the acceleration / direction sensor 2016 are also connected to bus 2008.

[0025] The image processing unit 2004 receives image data output from image sensors 2003a and 2003b via a parallel I / F bus, performs predetermined processing on each image data, and then combines these image data to create equirectangular projection image data.

[0026] The imaging control unit 2005 generally uses the I2C bus to set commands and other information in the registers of the image sensors 2003a and 2003b, with the 2005 acting as the master device and the image sensors 2003a and 2003b as slave devices. The necessary commands and other information are received from the CPU 2009. The imaging control unit 2005 also uses the I2C bus to capture status data and other information from the registers of the image sensors 2003a and 2003b and send it to the CPU 2009.

[0027] Furthermore, the imaging control unit 2005 instructs the image sensors 2003a and 2003b to output image data when the shutter button on the operation unit 2013 is pressed. Some 360-degree imaging devices 20 may also have functions to support preview display on a display (for example, a smartphone display) or video display. In this case, the image data output from the image sensors 2003a and 2003b is performed continuously at a predetermined frame rate (frames / minute).

[0028] Furthermore, as will be described later, the imaging control unit 2005 also functions as a synchronization control means that works in cooperation with the CPU 2009 to synchronize the output timing of image data from the image sensors 2003a and 2003b. In this embodiment, the 360-degree imaging device 20 is not provided with a display, but a display unit may be provided.

[0029] Microphone 2006 converts sound into sound (signal) data. Sound processing unit 2007 receives the sound data output from microphone 2006 via the I / F bus and performs predetermined processing on the sound data.

[0030] CPU2009 controls the overall operation of the 360-degree imaging device 20 and performs necessary processing. ROM2010 stores various programs for CPU2009. SRAM2011 and DRAM2012 are work memories that store programs executed by CPU2009 and data in progress. In particular, DRAM2012 stores image data in progress and processed equirectangular projection image data from the image processing unit 2004.

[0031] The control unit 2013 is a collective term for the operation buttons, such as the shutter button. Users input various shooting modes and shooting conditions by operating the control unit 2013.

[0032] The External Device Connection I / F2014 is an interface for connecting various external devices. These external devices include, for example, USB (Universal Serial Bus) memory and PCs (Personal Computers). The equirectangular projection image data stored in DRAM2012 can be recorded to external media via this Network I / F2014, or transmitted to external terminals (devices) such as smartphones via the Network I / F2014 as needed.

[0033] The communication unit 2015 communicates with external terminals (devices) such as smartphones via an antenna 2015a provided on the 360-degree imaging device 20, using short-range wireless communication technologies such as Wi-Fi, NFC (Near Field Communication), and Bluetooth (registered trademark). This communication unit 2015 can also transmit equirectangular projection image data to external terminals (devices) such as smartphones.

[0034] The acceleration / direction sensor 2016 calculates the orientation of the 360-degree imaging device 20 from the Earth's magnetic field and outputs orientation information. This orientation information is an example of related information (metadata) in accordance with Exif and is used for image processing such as image correction of captured images. The related information also includes the date and time the image was captured and the data size of the image data. Furthermore, the acceleration / direction sensor 2016 is a sensor that detects changes in angle (Roll angle, Pitch angle, Yaw angle) associated with the movement of the 360-degree imaging device 20. These angle changes are an example of related information (metadata) in accordance with Exif and are used for image processing such as image correction of captured images. In addition, the acceleration / direction sensor 2016 is a sensor that detects acceleration in three axes. Based on the acceleration detected by the acceleration / direction sensor 2016, the 360-degree imaging device 20 calculates its own orientation (angle relative to the direction of gravity). The installation of the acceleration / direction sensor 2016 in the 360-degree imaging device 20 improves the accuracy of image correction.

[0035] <Function Block> Figure 5 is a functional block diagram of a server and device according to one embodiment of the present invention.

[0036] <<Server>> Server 10 comprises a code distribution unit 101, a device registration unit 102, a linkage unit 103, and a storage unit 104. Furthermore, by executing a program, Server 10 functions as the code distribution unit 101, the device registration unit 102, and the linkage unit 103.

[0037] The code distribution unit 101 generates and distributes a code (for example, a QR code®) containing information about the application provided by the cloud service and information used for device registration. The following explanation uses a two-dimensional code as an example, but is not limited to this; one-dimensional codes, symbols, strings of characters, sequences of numbers, images, etc., may also be used.

[0038] This section explains "Application Information." Application information includes information to identify the application (Application ID). Furthermore, application information may also include the types of data that can be input into the application (still images, videos, etc.) and identifiers to determine availability.

[0039] This section explains the information used for device registration. This information includes the destination site for obtaining device identification information, and a token (access token) for accessing the site.

[0040] The device registration unit 102 registers the device 20. Specifically, when the device registration unit 102 obtains the information used for device registration from the device 20, it notifies the device 20 of information to identify the device (e.g., a device ID). The device registration unit 102 can also notify the device 20 of a certificate along with the information to identify the device (e.g., a device ID).

[0041] The linking unit 103 obtains information about the application and information to identify the device from the device 20, and registers the device 20 in association with the application. Specifically, the linking unit 103 associates the application provided by the cloud service with the device 20 and stores it in the storage unit 104.

[0042] The memory unit 104 stores information for identifying the device 20 (e.g., device ID) and information for identifying the application provided by the cloud service (e.g., application ID), linked together. Furthermore, the memory unit 104 may also store the type of data that can be input to the application (e.g., still images or videos).

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

[0044] The device registration unit 201 requests the server 10 to register device 20. Specifically, the device registration unit 201 notifies the server 10 of information used for registering the device (i.e., obtained from the code read by the photographing unit 203). Also, the device registration unit 201 obtains information (e.g., device ID) for identifying the device from the server 10.

[0045] The cooperation unit 202 requests the server 10 to register and link device 20 to an application provided by the cloud service. Specifically, the cooperation unit 202 notifies the server 10 of information regarding the application (i.e., obtained from the code read by the photographing unit 203) and information for identifying the device (e.g., device ID) obtained from the server 10 (i.e., obtained by the device registration unit 201).

[0046] The photographing unit 203 reads a code (e.g., 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 linking process between the device and the application according to an embodiment of the present invention. It will be described separately in the <WF app registration phase> and the <WF app execution phase>.

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

[0049] Furthermore, the developer of the WF application (C in Figure 1 (Cloud Service Partner)) is assumed to have developed a WF application using the WF application development tool, which includes settings for allowing QR code integration and specifying the types of data that can be input (such as still images or videos). The device partner (B in Figure 1) registers the WF application to the tenant (group of devices using the cloud service) to which the user belongs.

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

[0051] Specifically, the user logs into a site for configuring applications (the IoT site in Figure 1) on a PC (personal computer) 30, selects a WF application to link with device 20 (the device plug-in in Figure 1), and generates a QR code.

[0052] Assume that in step 12 (S12), the shutter button of device 20 is pressed.

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

[0054] In step 14 (S14), device 20 obtains the destination of a site to obtain information for identifying the device, a token to access the site (access token), and information about the application (for example, an application ID (here referred to as "App 1") and an input type (here referred to as "Still Image")) contained in the QR code.

[0055] In step 15 (S15), device 20 requests the server (device registration unit) 10 to register device 20. Specifically, device 20 notifies 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. Thereafter, 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 server (device registration unit) 10.

[0061] In step 23 (S23), device 20 uploads the image captured 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 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 of FIG. 6 is performed.

[0069] In the workflow (WF) platform provided by server 10, for tenants using the workflow (WF), 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 linking device A 21 to 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 linking device B 22 to the WF application.

[0074] <WF application settings> Settings of the WF application are performed.

[0075] In one embodiment of the present invention, the same WF application with different set values can be replicated within a tenant. By linking the replicated application to 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 linked thereto.

[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 server 10 of an access token.

[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 server 10 of an access token.

[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), camera device A 21 notifies the server (WF platform) 10 that it has taken a picture. Specifically, camera device A 21 notifies the server (WF platform) 10 of its serial number and the still image taken in S301.

[0087] In step 303 (S303), the server (WF platform) 10 obtains information about the WF application associated with the machine number.

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

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

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

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

[0092] In step 308 (S308), the server (WF platform) 10 obtains information about the WF application associated with the machine number.

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

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

[0095] In this way, the data is uploaded to an online storage service linked to the camera device.

[0096] <Data structure> Figure 8 is a diagram illustrating the linking of a device 20 and an application according to one embodiment of the present invention. As shown in Figure 8, information for identifying the application (e.g., application ID), input type (type of data that can be input into the application (e.g., still image or video)), and information for identifying the device 20 (e.g., device ID) are linked and managed together.

[0097] <Screen example> Figure 9 shows an example of a screen according to one embodiment of the present invention. A UI (user interface) is provided for performing the authentication process necessary for linking accounts to an online storage service. As a result, a workflow application that has been set up automatically is executed when a photo is taken, and the photo is uploaded to the online storage service associated with the camera device used for shooting.

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

[0099] In step 1002 (S1002), the workflow application settings screen is displayed. Each application has its own storage-related settings (storage service, account information, upload destination folder information), which can be configured from the settings screen. In addition, each application can display a QR code for device linking, and by scanning this with a registered camera device, the camera device can be linked to the configured workflow application with the online storage service.

[0100] In step 1003 (S1003), the online storage service integration screen is displayed. Access the external service authentication page of the online storage service, log in, and the integration with the online storage service will be completed.

[0101] This specification describes a workflow application that allows images captured by a digital camera to be uploaded to cloud computing storage. While this specification uses an online storage service as an example, the present invention can support any service that requires account linking in a workflow. For example, it is possible to link with a message queuing service account to send messages with captured images, or to link with a calendar service account to register schedule results as daily reports with captured images.

[0102] Each of the functions of the embodiments described above can be realized by one or more processing circuits. Hereinafter, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays), and conventional circuit modules designed to execute each of the functions described above.

[0103] It should be noted that the present invention is not limited to the configurations shown in the above embodiments, including combinations with other elements. These aspects can be modified without departing from the spirit of the present invention and can be appropriately determined according to their application. [Explanation of Symbols]

[0104] 1 System 10 servers 20 devices 21 Camera device A 22 Camera device B 30 PC 101 Code Distribution Department 102 Device Registration Section 103 Liaison Department 104 Storage section 201 Device Registration Section 202 Liaison Department 203 Photography Department

Claims

1. A code distribution unit that generates and distributes a code containing information used to register a device with an application, A device registration unit, upon obtaining information used for registering the device, which is acquired by reading the code with the aforementioned device, notifies the device of information for identifying the device. A linkage unit that associates and registers information for identifying the device with the aforementioned application. Equipped with, An information processing device that, upon receiving a notification from the device containing information for identifying the device, executes the application registered in association with the information for identifying the device.

2. The information processing apparatus according to claim 1, wherein the information used for registering the device includes the destination of a site for obtaining information to identify the device.

3. The information processing apparatus according to claim 1 or 2, wherein the device has a shooting function but does not have a display function.

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

5. A method executed by an information processing device, The steps include generating and distributing a code that contains information used to register a device with the application, The step of obtaining information used for registering the device, which is obtained by reading the code with the device, from the device, and notifying the device of information for identifying the device, The steps include registering information for identifying the device with the aforementioned application, and Includes, A method for receiving a notification from the device containing information for identifying the device, which involves executing the application that is registered and associated with the information for identifying the device.

6. Information processing equipment, A code distribution unit that generates and distributes code containing information used to register a device with an application. A device registration unit, upon obtaining information used for registering the device, which is acquired by reading the code with the aforementioned device, notifies the device of information for identifying the device. A linkage unit that associates and registers information for identifying the device with the aforementioned application. To make it function as, A program that, upon receiving a notification from the device containing information for identifying the device, executes the application registered in association with the information for identifying the device.

7. A system including a server and a device, The aforementioned server, A code distribution unit that generates and distributes a code containing information used to register a device with an application, A device registration unit, upon obtaining information used for registering the device, which is acquired by reading the code with the aforementioned device, notifies the device of information for identifying the device. A linkage unit that associates and registers information for identifying the device with the aforementioned application. Equipped with, When the device receives a notification containing information for identifying the device, it executes the application that is registered and associated with the information for identifying the device. The device described above, A device registration unit is provided which notifies the server of the information used for registering the device obtained by reading the code, and obtains information for identifying the device from the server. The device is a system that notifies the server of a notification containing information for identifying the acquired device.

8. The device is a device having a shooting function, The system according to claim 7, wherein the device obtains a URL from the server for uploading the captured image and uploads the captured image to the obtained URL.

Images