JP2023040466A - Information processing device, method, program, and system - Google Patents

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

The present invention relates to an information processing device, method, program, and system.

Conventionally, cloud services are known that provide computer resources via networks such as the Internet. The user uses the cloud service using the device at hand. In order to use such a cloud service, the user must perform settings such as device registration with the cloud service (Patent Document 1).

Japanese Patent No. 4383738

However, it is not easy for a user to operate a device with a poor user interface (for example, a device without a display) to make settings.

Accordingly, it is an object of the present invention to facilitate the use of services provided via a network by devices.

An information processing apparatus according to an embodiment of the present invention includes a code distribution unit that generates and distributes a code that includes information about an application and information used for registering a device; a device registration unit that notifies the device of information for identifying the device; and a device registration unit that obtains information about the application and information for identifying the device from the device, and links the device to the application. and a linking unit for registering the information.

The present invention facilitates the use of services provided via a network by devices.

1 is a diagram for explaining an overview of a service according to one embodiment of the present invention; FIG. 1 is an overall configuration diagram according to an embodiment of the present invention; FIG. 1 is a hardware configuration diagram of an information processing device (server) according to an embodiment of the present invention; FIG. 1 is a hardware configuration diagram of a device (omnidirectional imaging device) according to an embodiment of the present invention; FIG. 1 is a functional block diagram of a server and device according to an embodiment of the invention; FIG. FIG. 4 is a sequence diagram of processing for associating a device and an application according to an embodiment of the present invention; FIG. 4 is a sequence diagram of processing for associating a device and an application according to an embodiment of the present invention; FIG. 4 is a diagram for explaining how devices and applications are linked according to an embodiment of the present invention; It is an example of a screen according to one embodiment of the present invention.

Embodiments of the present disclosure will be described below based on the drawings.

FIG. 1 is a diagram for explaining an outline of a service according to one embodiment of the present invention. A user (user of a customer, A1 in FIG. 1) uses a device 20 to use cloud services provided by servers 11 to 15 (hereinafter also referred to as server 10). Also, the device partner (B in FIG. 1) registers a workflow (WF) application in the tenant to which the user belongs (group of devices using cloud services). In addition, the workflow (WF) application developer (C (cloud service partner) in Fig. 1) sets permission for QR code linkage settings and the type of data that can be input (still image, video, etc.) using the WF application development tool. Develop a custom workflow (WF) application. A2 is the customer's administrator and D is the device vendor. Note that the cloud service provided by the server 10 will be described below as an example of the service provided to the device 20 via the network. However, the service used by the device 20 is not limited to this, and any service that uses a function provided via a network may be used. For example, the server 10 may provide on-premises services to the device 20 by placing the server 10 within the same network as the device 20 .

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

<<Server>>
A server (which is an example of an information processing device) 10 performs a process of linking an application provided by a cloud service and a device 20 .

The devices described in the examples are merely representative of one of several computing environments for implementing the embodiments disclosed herein. In some embodiments, server 10 includes multiple computing devices, such as a server cluster. Multiple computing devices are configured to communicate with each other over any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein.

<<Device>>
The device 20 is a device used by a user who uses the cloud service. For example, the device 20 is a device (for example, an omnidirectional imaging device) that has an imaging function and does not have a display function.

Note that the device 20 is not limited to an omnidirectional imaging device as long as it has a communication function. The device 20 is, for example, a PJ (Projector), an IWB (Interactive White Board), an output device such as a digital signage, a HUD (Head Up Display) device, an industrial Machines, imaging devices, sound collectors, medical equipment, network appliances, automobiles (connected cars), notebook PCs (personal computers), mobile phones, smartphones, tablet devices, game consoles, PDAs (Personal Digital Assistants), digital cameras, wearables It may be a PC, a desktop PC, or the like.

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

As shown in FIG. 3, the server 10 is constructed by a computer, and as shown in FIG. , 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 .

Among these, the CPU 1001 controls the operation of the server 10 as a whole. The ROM 1002 stores programs used to drive the CPU 1001 such as IPL. A 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 reading or writing of various data to/from the HD 1004 under the control of the CPU 1001 . A display 1006 displays various information such as cursors, menus, windows, characters, and images. The external device connection I/F 1007 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. A network I/F 1008 is an interface for data communication using the communication network N. FIG. A bus line 1009 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 1001 shown in FIG.

Also, the keyboard 1010 is a kind of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. A pointing device 1011 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A DVD-RW drive 1013 controls reading or writing of various data to a DVD-RW 1012 as an example of a removable recording medium. It should be noted that not only DVD-RW but also DVD-R or the like may be used. A media I/F 1015 controls reading or writing (storage) of data to a recording medium 1014 such as a flash memory.

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

In the following description, the omnidirectional (omnidirectional) omnidirectional imaging device 20 is assumed to be an omnidirectional (omnidirectional) omnidirectional imaging device using two imaging elements, but the number of imaging elements may be two or more. Further, the device does not necessarily have to be dedicated to omnidirectional photography, and by attaching an omnidirectional imaging unit to a normal digital camera, smartphone, or the like, it can have substantially the same functions as the omnidirectional photography device 20. can be

As shown in FIG. 4, the omnidirectional imaging apparatus 20 includes 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, SRAM (Static Random Access Memory) 2011, DRAM (Dynamic Random Access Memory) 2012, operation unit 2013, external device connection I/F 2014, communication unit 2015, antenna 2015a, electronic compass, gyro sensor, acceleration sensor , and a recessed terminal for Micro USB.

Among them, 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 imaging units provided corresponding to each wide-angle lens. It has elements 2003a and 2003b. The imaging elements 2003a and 2003b are image sensors such as CMOS (Complementary Metal Oxide Semiconductor) sensors and CCD (Charge Coupled Device) sensors that convert optical images formed by the fisheye lenses 2002a and 2002b into electrical signal image data and output them. and a timing generation circuit for generating horizontal or vertical synchronizing signals, pixel clocks, etc., and a group of registers for setting various commands and parameters necessary for the operation of this imaging device.

The imaging elements 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 imaging elements 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 , imaging control unit 2005 and sound processing unit 2007 are connected to the CPU 2009 via a bus 2008 . Furthermore, the bus 2008 is also connected to a ROM 2010, an SRAM 2011, a DRAM 2012, an operation unit 2013, an external device connection I/F (Interface) 2014, a communication unit 2015, an acceleration/direction sensor 2016, and the like.

The image processing unit 2004 fetches the image data output from the imaging devices 2003a and 2003b through the parallel I/F bus, performs predetermined processing on each image data, and then synthesizes these image data. , to create the equirectangular projection image data.

The imaging control unit 2005 generally uses the I2C bus with the imaging control unit 2005 as a master device and the imaging elements 2003a and 2003b as slave devices to set commands and the like in registers of the imaging elements 2003a and 2003b. Necessary commands and the like are received from the CPU 2009 . The imaging control unit 2005 also uses the I2C bus to take in status data and the like of the registers of the imaging elements 2003 a and 2003 b and send them to the CPU 2009 .

Further, the imaging control unit 2005 instructs the imaging devices 2003a and 2003b to output image data at the timing when the shutter button of the operation unit 2013 is pressed. The omnidirectional imaging device 20 may have a preview display function or a function corresponding to moving image display on a display (for example, the display of a smartphone). In this case, the image data are output continuously from the imaging elements 2003a and 2003b at a predetermined frame rate (frames/minute).

In addition, 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 imaging devices 2003a and 2003b in cooperation with the CPU 2009. FIG. In this embodiment, the omnidirectional imaging device 20 is not provided with a display, but may be provided with a display unit.

A microphone 2006 converts sound into sound (signal) data. The sound processing unit 2007 takes in sound data output from the microphone 2006 through the I/F bus and performs predetermined processing on the sound data.

A CPU 2009 controls the overall operation of the omnidirectional imaging device 20 and executes necessary processing. ROM 2010 stores various programs for CPU 2009 . The SRAM 2011 and DRAM 2012 are work memories, and store programs to be executed by the CPU 2009, data during processing, and the like. In particular, the DRAM 2012 stores image data being processed by the image processing unit 2004 and data of the processed equirectangular projection image.

An 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, and the like.

The external device connection I/F 2014 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a PC (Personal Computer), or the like. The data of the equirectangular projection image stored in the DRAM 2012 is recorded on an external medium via the network I/F 2014, or is transferred to an external terminal (apparatus) such as a smart phone via the network I/F 2014 as necessary. or sent to

The communication unit 2015 communicates with an external device such as a smartphone via an antenna 2015a provided in the omnidirectional imaging device 20 by short-range wireless communication technology such as Wi-Fi, NFC (Near Field Communication), or Bluetooth (registered trademark). Communicate with a terminal (device). The communication unit 2015 can also transmit the data of the equirectangular projection image to an external terminal (device) such as a smartphone.

The acceleration/azimuth sensor 2016 calculates the azimuth of the omnidirectional imaging device 20 from the magnetism of the earth and outputs the azimuth information. This azimuth information is an example of related information (metadata) according to Exif, and is used for image processing such as image correction of a captured image. The related information also includes data such as the date and time when the image was taken and the data volume of the image data. The acceleration/azimuth sensor 2016 is a sensor that detects changes in angles (Roll angle, Pitch angle, Yaw angle) accompanying movement of the omnidirectional imaging device 20 . A change in angle is an example of related information (metadata) according to Exif, and is used for image processing such as image correction of a captured image. Furthermore, the acceleration/direction 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 direction of gravity) of its own device (omnidirectional imaging device 20 ) based on the acceleration detected by the acceleration/azimuth sensor 2016 . By providing the acceleration/azimuth sensor 2016 in the omnidirectional imaging device 20, the accuracy of image correction is improved.

<Functional block>
FIG. 5 is a functional block diagram of a server and device according to one embodiment of the invention.

<<Server>>
The server 10 includes a code distribution section 101 , a device registration section 102 , a cooperation section 103 and a storage section 104 . The server 10 also functions as a code distribution unit 101, a device registration unit 102, and a cooperation unit 103 by executing programs.

The code distribution unit 101 generates and distributes a code (for example, a QR code (registered trademark)) containing information about applications provided by cloud services and information used for device registration. In the following, a case where a two-dimensional code is used as the code will be described as an example, but the code is not limited to this, and may be a one-dimensional code, a symbol, a character string, a number string, an image, or the like.

Describes "Information about applications". The application information includes information (application ID) for identifying the application. The information about the application can further include the type of data that can be input to the application (still image, moving image, etc.) and an identifier for determining whether the data can be used.

"Information used for device registration" is explained. The information used for device registration includes a site connection destination for acquiring information for identifying the device and a token (access token) for accessing the site.

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

The linking unit 103 acquires information about the application and information for identifying the device from the device 20, and registers the device 20 in association with the application. Specifically, the cooperation unit 103 associates the application provided by the cloud service with the device 20 and causes the storage unit 104 to store them.

Information for identifying the device 20 (eg, device ID) and information for identifying the application provided by the cloud service (eg, application ID) are linked and stored in the storage unit 104. ing. Furthermore, the storage unit 104 may store the type of data that can be input to the application (still image, moving image, etc.) in association with each other.

<<Device>>
The device 20 includes a device registration section 201 , a cooperation section 202 and an imaging section 203 . The device 20 also functions as a device registration unit 201, a cooperation unit 202, and an imaging unit 203 by executing programs.

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 device registration obtained by reading the code (that is, obtained from the code read by the imaging unit 203). Also, the device registration unit 201 acquires information for identifying the device (for example, device ID) from the server 10 .

The linking unit 202 requests the server 10 to register the device 20 in association with an application provided by the cloud service. Specifically, the linking unit 202 acquires information about the application acquired by reading the code (that is, acquired from the code read by the imaging unit 203), and information acquired from the server 10 (that is, the device registration unit 201 The server 10 is notified of the information (for example, device ID) for identifying the device acquired by the server 10 .

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

<Processing method>
FIG. 6 is a sequence diagram of device-application linking processing according to an embodiment of the present invention. The description will be divided into <WF application registration phase> and <WF application execution phase>.

<WF application registration phase>
Processing for linking and registering a workflow (WF) application provided by a cloud service to the device 20 will be described. Note that the workflow (WF) application is an application that performs predetermined processing on the server 10 .

In addition, the WF application developer (C (cloud service partner) in Fig. 1) uses the WF application development tool to set permission for QR code linkage settings and the type of data that can be input (still image or video, etc.). is being developed. Also, the device partner (B in FIG. 1) registers the WF application in the tenant to which the user belongs (group of devices using the cloud service).

In step 11 (S11), the server (code distribution unit) 10 generates and distributes a code (for example, a QR code) containing information about applications provided by the cloud service and information used for device registration.

Specifically, a user logs in to a site (IoT site in FIG. 1) for setting an application using a PC (personal computer) 30, and executes a WF application to be linked with the device 20 (device plug-in in FIG. 1). Select to issue a QR code.

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

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

In step 14 (S14), the device 20 receives the connection destination of the site for acquiring the information for identifying the device, the token (access token) for accessing the site, and the Information about the application (for example, an application ID (here, "application 1") and an input type (here, "still image")) is acquired.

At step 15 ( S<b>15 ), the device 20 requests the server (device registration unit) 10 to register the device 20 . Specifically, the device 20 notifies the server 10 of the information used for device registration obtained by reading the code in S14 (more specifically, the serial number of the device 20 is sent to the connection destination using the access token). send).

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

At step 17 (S17), the device 20 requests the server (coordination unit) 10 to associate the device 20 with the application and register it. Specifically, the device 20 sends the application ID (ie, “application 1”), input type (ie, “still image”), and device ID (ie, “device A”) to the server (ie, “device A”) together with the certificate of S16. The communication unit) 10 is notified. After that, the server (collaborating unit) 10 associates and registers the application ID, the input type, and the device ID (see FIG. 8).

<WF application execution phase>
Processing for executing a workflow (WF) application will be described.

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

At step 22 (S22), the device 20 acquires a URL (Uniform Resource Locator). Specifically, the device 20 acquires the URL from the server (device registration unit) 10 .

In step 23 (S23), the device 20 uploads the image captured in S21 to the URL of S22.

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.

At step 25 (S25), the server (device registration unit) 10 sends the device ID and URL acquired at S24 to the server (coordination unit) 10. FIG.

At step 26 (S26), the server (coordination unit) 10 downloads the image uploaded to the URL obtained at S25.

At step 27 (S27), the server (coordination unit) 10 causes the workflow (WF) application to execute the job. Specifically, the server (collaborating unit) 10 notifies the application (ie, "application 1") associated with the device ID of the input type (ie, "still image").

At step 28 (S28), the WF application uploads the image to the online storage service. Note that uploading and saving images to an online storage service is an example of a service provided via a network.

FIG. 7 is a sequence diagram of device-application linking processing according to an embodiment of the present invention. <preparation>, <WF application setting>, and <WF execution> will be explained separately. Note that the workflow (WF) application is a workflow (WF) application that uploads to an online storage service.

<Advance preparation>
As a preparation, the linking process of FIG. 6 is performed.

In the workflow (WF) platform provided by the server 10, it is possible to register the device 20 in advance using the serial number of each device and the like for tenants using the workflow (WF). With this, the workflow (WF) platform can grasp the device to be used for each tenant.

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

In step 102 (S102), the camera device A 21 requests the server (WF platform) 10 to associate the device A 21 with the WF application and register it.

In step 103 (S103), the camera device B 22 (which is an example of the device 20) requests the server (WF platform) 10 to register the camera device B 22 using the model number of the camera device B 22. .

At step 104 (S104), the camera device B 22 requests the server (WF platform) 10 to associate the device B 22 with the WF application and register it.

<WF application settings>
WF application settings are made.

In one embodiment of the present invention, the same WF application with different settings can be replicated within a tenant. By associating this duplicated application with the device and setting an online storage service account for each application, the WF application called from a specific camera device is executed using the associated online storage service account. be able to.

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

At step 202 (S202), the server 10 requests storage service A to authenticate the account.

At step 203 (S203), the storage service A notifies the server 10 of the access token.

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

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

At step 206 (S206), the server 10 requests storage service B to authenticate the account.

At step 207 (S207), the storage service B notifies the server 10 of the access token.

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

<Execute WF>
WF application is executed.

At step 301 (S301), the camera device A 21 takes a picture.

At step 302 (S302), the camera device A 21 notifies the server (WF platform) 10 of shooting. Specifically, the camera device A 21 notifies the server (WF platform) 10 of the model number and the still image captured in S301.

At step 303 (S303), the server (WF platform) 10 acquires information on the WF application linked to the machine number.

At 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 the access token linked to the device number.

At step 305 (S305), the WF application uploads the still image to storage service A.

At step 306 (S306), the camera device B 22 takes a picture.

At step 307 (S307), the camera device B 22 notifies the server (WF platform) of shooting. Specifically, the camera device B 22 notifies the server (WF platform) 10 of the model number and the still image captured in S306.

At step 308 (S308), the server (WF platform) 10 acquires information on the WF application linked to the machine number.

At 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 the access token linked to the device number.

At step 310 (S310), the WF application uploads the still image to storage service B.

In this way, uploading is performed to the online storage service linked to the camera device.

<Data structure>
FIG. 8 is a diagram for explaining how devices 20 and applications are associated 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 (type of data that can be input to the application (still image, moving image, etc.)), and for identifying the device 20 information (for example, device ID) are linked and managed.

<Screen example>
FIG. 9 is an example of a screen according to one embodiment of the present invention. A UI (user interface) is provided for performing authentication processing necessary for account linkage of the online storage service. As a result, the automatically set workflow application is executed when the photo is taken, and the photo is uploaded to the online storage service linked to the camera device used for the photo shoot.

At step 1001 (S1001), a list of multiple workflow applications managed on the tenant is displayed. If any workflow application is selected, go to step 1002 .

At step 1002 (S1002), a workflow application setting screen is displayed. Each application has settings related to storage (storage service, account information, upload destination folder information), which can be set from the setting screen. In addition, a QR code for device cooperation can be displayed for each application, and by reading this with a registered camera device, the camera device can be associated with the set workflow application of the online storage service.

At step 1003 (S1003), the online storage service cooperation screen is displayed. Access the external service authentication page of the online storage service and log in to link with the online storage service.

In this specification, a workflow application that can upload images captured by a digital camera to storage on cloud computing has been described. In this specification, an online storage service is used as an example, but the present invention can deal with any service that requires account linkage in a workflow. For example, linking with a message queuing service account to send a message with a captured image, or linking with a calendar service account to register schedule results as a daily report with a captured image. be done.

Each function of the embodiments described above may be implemented by one or more processing circuits. Here, the "processing circuit" in this specification means a processor programmed by software to perform each function, such as a processor implemented by an electronic circuit, or a processor designed to perform each function described above. devices such as ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays) and conventional circuit modules.

It should be noted that the present invention is not limited to the configurations shown here, such as combinations with other elements, etc., in the configurations described in the above embodiments. These points can be changed without departing from the gist of the present invention, and can be determined appropriately according to the application form.

1 system 10 server 20 device 21 camera device A
22 camera device B
30 PCs
101 code delivery unit 102 device registration unit 103 cooperation unit 104 storage unit 201 device registration unit 202 cooperation unit 203 photographing unit

Claims (10)

a code distribution unit that generates and distributes a code containing information about applications and information used for device registration;
a device registration unit that notifies the device of information for identifying the device when information used for registration of the device is acquired from the device;
and a linking unit that acquires information about the application and information for identifying the device from the device, and registers the device in association with the application. 2. The information processing apparatus according to claim 1, wherein when said application is executed, a service linked with said application is changed according to said device. 3. The information processing apparatus according to claim 2, which provides a user interface for performing authentication processing for account linkage of said service when setting said application. 4. The information used for registering the device includes a connection destination of a site for obtaining information for identifying the device and a token for accessing the site. The information processing device according to the item. The information processing apparatus according to any one of claims 1 to 4, wherein the information on the application includes information for identifying the application. 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. The information processing apparatus according to any one of claims 1 to 6, wherein said code is a QR code. A method executed by an information processing device, comprising:
generating and delivering a code containing information about the application and information used to register the device;
a step of notifying the device of information for identifying the device when the information used for registration of the device is obtained from the device;
and obtaining information about the application and information for identifying the device from the device, and registering the device in association with the application. a code distribution unit that generates and distributes a code that includes information related to an application and information used for device registration of an information processing device;
a device registration unit that notifies the device of information for identifying the device when information used for registration of the device is acquired from the device;
A program for functioning as a linking unit that acquires information about the application and information for identifying the device from the device, associates the device with the application, and registers the device. A system including a server and a device,
The server is
a code distribution unit that generates and distributes a code containing information about applications and information used for device registration;
a device registration unit that notifies the device of information for identifying the device when information used for registration of the device is acquired from the device;
a linking unit that acquires information about the application and information for identifying the device from the device, associates the device with the application, and registers the device;
The device is
a device registration unit for notifying the server of information used for registering the device obtained by reading the code and obtaining information for identifying the device from the server;
and a linking unit that notifies the server of information about the application obtained by reading the code and information for identifying the device obtained from the server.

Images