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

Description

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

Conventionally, cloud services that provide computer resources via a network such as the Internet are known. Users use cloud services using devices at hand. In order to use such cloud services, users must perform settings such as registering the device to the cloud service (Patent Document 1).

Patent No. 4383738

However, on devices with poor user interfaces (e.g., devices without a display), it is not easy for users to operate the device and configure it.

The present invention aims to make it easier for devices to use services provided via a network.

An information processing device according to one 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 to register a device, a device registration unit that notifies the device of information for identifying the device when information used to register the device is obtained from the device, and a linking unit that obtains information related to the application and information for identifying the device from the device and links the device to the application and registers it.

The present invention makes it easier for devices to use services provided via a network.

FIG. 1 is a diagram for explaining an overview of a service according to an embodiment of the present invention. 1 is an overall configuration diagram according to an embodiment of the present invention; 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. 2 is a functional block diagram of a server and a device according to an embodiment of the present invention. FIG. 11 is a sequence diagram of a process for associating a device with an application according to an embodiment of the present invention. FIG. 11 is a sequence diagram of a process for associating a device with an application according to an embodiment of the present invention. FIG. 2 is a diagram for explaining association between a device and an application according to an embodiment of the present invention. 11 is an example of a screen according to an embodiment of the present invention.

The following describes an embodiment of the present disclosure with reference to the drawings.

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 device 20 to use cloud services provided by servers 11 to 15 (hereinafter also referred to as server 10). A device partner (B in FIG. 1) registers a workflow (WF) application to a tenant (a group of devices using cloud services) to which the user belongs. A developer of a workflow (WF) application (C (cloud service partner) in FIG. 1) develops a workflow (WF) application using a WF application development tool, in which QR code linkage settings are permitted and the type of data that can be input (such as still images or videos). A2 is a customer administrator, and D is a sales company of the device. In the following, a cloud service provided by the server 10 is used as an example of a service provided to the device 20 via a 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 an on-premise service to the device 20 by installing the server 10 in the same network as the device 20.

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

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

The devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. 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 over any type of communication link, including a network, shared memory, etc., and perform the processes disclosed herein.

<<Devices>>
The device 20 is a device used by a user who uses a cloud service. For example, the device 20 is a device (for example, a spherical imaging device) that has an image capturing function but does not have a display function.

The device 20 is not limited to a spherical imaging device, so long as it is a device equipped with a communication function. The device 20 may be, for example, a PJ (Projector), an IWB (Interactive White Board: a white board with an electronic blackboard function capable of mutual communication), an output device such as a digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, an automobile (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.

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

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

Of these, the CPU 1001 controls the operation of the entire server 10. The ROM 1002 stores programs used to drive the CPU 1001, such as 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 from the HD 1004 according to the control of the CPU 1001. The display 1006 displays various information such as a cursor, menu, window, character, or image. The external device connection I/F 1007 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. 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, or the like for electrically connecting each component such as the CPU 1001 shown in FIG. 3.

The keyboard 1010 is a type of input means equipped with multiple keys for inputting characters, numbers, 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 the reading and writing of various data from a DVD-RW 1012, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I/F 1015 controls the reading and writing (storing) of data from a recording medium 1014, such as a flash memory.

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

In the following, the omnidirectional imaging device 20 is described as an omnidirectional (all-directional) omnidirectional imaging device using two imaging elements, but the number of imaging elements may be two or more. In addition, the device does not necessarily have to be dedicated to omnidirectional imaging, and an ordinary digital camera, smartphone, or the like may be provided with an omnidirectional imaging unit as a retrofit, so that the device has substantially the same functions as the omnidirectional imaging device 20.

As shown in FIG. 4, the omnidirectional imaging device 20 is composed 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 I/F 2014, a communication unit 2015, an antenna 2015a, an electronic compass, a gyro sensor, an acceleration sensor, and a concave terminal for a Micro USB.

The imaging unit 2001 includes wide-angle lenses (so-called fisheye lenses) 2002a and 2002b each having an angle of view of 180° or more for forming a hemispherical image, and two imaging elements 2003a and 2003b provided corresponding to each wide-angle lens. The imaging elements 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 captured by the fisheye lenses 2002a and 2002b into image data of an electrical signal and outputs it, a timing generation circuit that generates horizontal or vertical synchronization signals and pixel clocks for the image sensors, and a group of registers in which various commands and parameters required for the operation of the imaging elements are set.

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

The image processing unit 2004 takes in the image data output from the image sensors 2003a and 2003b via a parallel I/F bus, performs a predetermined process on each piece of image data, and then synthesizes the image data to create equirectangular projection image data.

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

The imaging control unit 2005 also instructs the imaging elements 2003a and 2003b to output image data when the shutter button on the operation unit 2013 is pressed. Some omnidirectional imaging devices 20 have a preview display function or a video display function on a display (e.g., a smartphone display). In this case, the image data is output from the imaging elements 2003a and 2003b continuously at a predetermined frame rate (frames/minute).

The imaging control unit 2005 also functions as a synchronization control means that cooperates with the CPU 2009 to synchronize the output timing of image data from the imaging elements 2003a and 2003b, as described below. Note that in this embodiment, the omnidirectional imaging device 20 is not provided with a display, but a display unit may be provided.

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

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

The operation unit 2013 is a general term for operation buttons such as the shutter button. The user operates the operation unit 2013 to input various shooting modes, shooting conditions, etc.

The external device connection I/F 2014 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a PC (Personal Computer). The data of the equirectangular 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 necessary.

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

The acceleration/orientation sensor 2016 calculates the orientation of the omnidirectional imaging device 20 from the earth's magnetism and outputs orientation information. This orientation information is an example of related information (metadata) according to Exif, and is used for image processing such as image correction of the captured image. The related information also includes the image capture date and time and the data capacity of the image data. The acceleration/orientation sensor 2016 is a sensor that detects angle changes (roll angle, pitch angle, yaw angle) accompanying the movement of the omnidirectional imaging device 20. The angle changes are an example of related information (metadata) according to Exif, and are used for image processing such as image correction of the captured image. The acceleration/orientation 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 (the omnidirectional imaging device 20) based on the acceleration detected by the acceleration/orientation sensor 2016. The accuracy of image correction is improved by providing the acceleration/orientation sensor 2016 to the omnidirectional imaging device 20.

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

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

The code distribution unit 101 generates and distributes a code (e.g., a QR code (registered trademark)) that includes information about applications provided by the cloud service and information used to register a device. 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 numeric string, an image, etc.

The following describes "information about an application." Information about an application includes information for identifying the application (application ID). Information about an application may also include the type of data that can be input to the application (still images, video, etc.) and an identifier for determining whether or not it can be used.

The following describes "information used to register a device." Information used to register a device includes the site destination to obtain information to identify the device, and a token (access token) to access the site.

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

The linking unit 103 acquires information about the application and information for identifying the device from the device 20, and links the application to the device 20 and registers it. Specifically, the linking unit 103 links the application provided by the cloud service to the device 20 and stores the link in the storage unit 104.

The storage unit 104 stores information for identifying the device 20 (e.g., a device ID) and information for identifying an application provided by the cloud service (e.g., an application ID) in association with each other. Furthermore, the storage unit 104 may store the type of data that can be input to the application (still images, videos, etc.) in association with each other.

<<Devices>>
The device 20 includes a device registration unit 201, a linking unit 202, and an image capturing unit 203. The device 20 also functions as the device registration unit 201, the linking unit 202, and the image capturing unit 203 by executing a program.

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 to register the device that was obtained by reading the code (i.e., obtained from the code read by the photographing unit 203). The device registration unit 201 also obtains information for identifying the device (e.g., a device ID) from the server 10.

The linking unit 202 requests the server 10 to link and register the device 20 with an application provided by the cloud service. Specifically, the linking unit 202 notifies the server 10 of information about the application acquired by reading the code (i.e., acquired from the code read by the photographing unit 203) and information for identifying the device (e.g., device ID) acquired from the server 10 (i.e., acquired by the device registration unit 201).

The photographing unit 203 reads the code (e.g., a QR code) generated and distributed by the code distribution unit 101 of the server 10.

<Processing method>
6 is a sequence diagram of a process for linking a device and an application according to an embodiment of the present invention, which will be described separately for a <WF application registration phase> and a <WF application execution phase>.

<WF application registration phase>
The following describes a process of registering a workflow (WF) application provided by a cloud service in association with the device 20. The workflow (WF) application is an application in the server 10 that performs a predetermined process.

The developer of the WF application (C in Figure 1 (cloud service partner)) is assumed to have developed a WF application using a WF application development tool, in which the QR code integration setting is permitted and the type of data that can be input (still images, videos, etc.) is set. The device partner (B in Figure 1) registers the WF application in the tenant (a group of devices that use cloud services) to which the user belongs.

In step 11 (S11), the server (code distribution unit) 10 generates and distributes a code (e.g., a QR code) that includes information about the application provided by the cloud service and information used to register the device.

Specifically, the user logs in to a site (IoT site in Figure 1) where applications are configured using a PC (personal computer) 30, selects a WF application to be linked to the device 20 (device plug-in in Figure 1), and issues a QR code.

In step 12 (S12), it is assumed that the shutter button on device 20 is pressed.

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

In step 14 (S14), the device 20 acquires the connection destination of the site for acquiring information for identifying the device, which is included in the QR code, a token for accessing the site (access token), and information related to the application (e.g., application ID (here, "App 1") and input type (here, "still image")).

In step 15 (S15), 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 to register the device, which was obtained by reading the code in S14 (in more detail, the device 20's serial number is sent to the connection destination using an access token).

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 the certificate.

In step 17 (S17), the device 20 requests the server (collaboration unit) 10 to link the device 20 to the application and register it. Specifically, the device 20 notifies the server (collaboration unit) 10 of the application ID (i.e., "App 1"), input type (i.e., "still image"), and device ID (i.e., "Device A") along with the certificate of S16. The server (collaboration unit) 10 then links and registers the application ID, input type, and device ID (see FIG. 8).

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

In step 21 (S21), it is assumed that the shutter button on device 20 is pressed.

In step 22 (S22), the device 20 acquires a uniform resource locator (URL). Specifically, the device 20 acquires the URL from the server (device registration unit) 10.

In step 23 (S23), 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 image capture. Specifically, the device 20 notifies the server (device registration unit) 10 of the device ID (i.e., "Device A") and the URL.

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

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

In step 27 (S27), the server (collaboration unit) 10 causes the workflow (WF) application to execute the job. Specifically, the server (collaboration unit) 10 notifies the application (i.e., "App 1") linked to the device ID of the input type (i.e., "still image").

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

Figure 7 is a sequence diagram of the process of linking a device and an application according to one embodiment of the present invention. The process is explained in sections: <Preparation>, <WF application settings>, and <WF execution>. The workflow (WF) application is a workflow (WF) application that uploads to an online storage service.

<Advance preparations>
As a preliminary step, the linking process shown in FIG. 6 is carried out.

In the workflow (WF) platform provided by the server 10, devices 20 can be registered in advance for tenants who use the workflow (WF) using the model number of each device. This allows the workflow (WF) platform to know the devices to be used for each tenant.

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 model number of camera device A 21.

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

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 model number of camera device B 22.

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

<WF app settings>
The WF application is configured.

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

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

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

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

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

In step 205 (S205), the PC 30 performs operations for account linking (linking storage service B and camera device B) on the WF application setting screen provided by the server 10.

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

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

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

<Workflow execution>
The WF application is executed.

In step 301 (S301), camera device A 21 takes a photo.

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

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

In step 304 (S304), the server (WF platform) 10 executes the WF application. Specifically, the server (WF platform) 10 notifies the WF application of storage service A linked to the machine number and the access token.

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

In step 306 (S306), camera device B 22 takes a photo.

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

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

In step 309 (S309), the server (WF platform) 10 executes the WF application. Specifically, the server (WF platform) 10 notifies the WF application of storage service B linked to the machine number and the access token.

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

In this way, the image is uploaded to the online storage service linked to the camera device.

<Data structure>
Fig. 8 is a diagram for explaining the association between the device 20 and an application according to an embodiment of the present invention. As shown in Fig. 8, information for identifying an application (e.g., application ID), an input type (type of data that can be input to the application (still image, video, etc.)), and information for identifying the device 20 (e.g., device ID) are associated and managed.

<Screen example>
9 shows an example of a screen according to an embodiment of the present invention. A UI (user interface) is provided for performing authentication processing required for account linking of an online storage service. This executes a workflow application that was automatically set when a photograph was taken, and uploads the photograph to the online storage service associated with the camera device used for taking the photograph.

In step 1001 (S1001), a list of multiple workflow applications managed on the tenant is displayed. When one of the workflow applications is selected, the process proceeds to step 1002.

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

In step 1003 (S1003), a linking screen for the online storage service is displayed. The user accesses the external service authentication page of the online storage service and logs in to link with the online storage service.

This specification describes a workflow application that can upload images captured by a digital camera to storage on a cloud computing platform. Although an online storage service has been given as an example in this specification, the present invention can be applied to any service that requires account linkage in a workflow. For example, it is conceivable to link with an account for a message queuing service to send a message with a captured image, or to link with an account for a calendar service to register schedule results as a daily report with a captured image.

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

The present invention is not limited to the configurations shown here, including combinations of the configurations and other elements in the above-mentioned embodiments. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

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 Collaboration unit 104 Storage unit 201 Device registration unit 202 Collaboration unit 203 Photography unit

Claims (10)

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

Images