JP2021092857A - Database device, generation system, generation method, and generation program - Google Patents

Abstract

To provide a database device for facilitating handling of IoT devices, and a generation system, generation method, and generation program.SOLUTION: A system includes device equipment 1 connected to a network, and a bind database device 5 to which a use permitted person of the device equipment 1 is associated with. By creating a bind database for associating the device equipment 1 and a purchase user by the bind database device 5, the convenience of eliminating initial setting when purchasing the device equipment 1 is achieved.SELECTED DRAWING: Figure 8

Description

Embodiments relate to a database device, a generation system, a generation method and a generation program.

In recent years, devices related to Internet of Things (IoT) (hereinafter referred to as IoT devices) that connect things to the Internet have become widespread. Since the IoT device is connected to a network such as the Internet, an application that generates communication between different IoT devices is possible. In the future, with the development of wireless technology such as the 5th generation mobile communication system (hereinafter referred to as 5G), if IoT devices can be connected to the network more easily, the spread of IoT devices to general users will accelerate and individual devices will be used. It is expected that users will own a large number of IoT devices. Normally, in order to connect a device to a network, it is necessary to set and register parameters and the like for the device.

Japanese Unexamined Patent Publication No. 2005-55940 Japanese Unexamined Patent Publication No. 2005-44201 JP-A-2002-189935 JP-A-2002-74135 Japanese Unexamined Patent Publication No. 2001-256317

However, when individual users own many IoT devices and perform complicated operations on the network such as linking the IoT devices, the setting and registration to the IoT devices become very complicated. Further, general users are not limited to users who are familiar with information and communication technology (ICT), and it is necessary to facilitate the handling of IoT devices in order to spread and expand in the future.

An object to be solved by the present invention is to provide a database device, a generation system, a generation method and a generation program in order to facilitate the handling of IoT devices.

The database device according to the embodiment includes a device device connected to the network and connected to the network, and a database in which a licensee of the device device is associated with the device device.

FIG. 1 is a diagram showing a configuration example of the entire system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of the device device according to the embodiment. FIG. 3 is a block diagram showing an example of the functional configuration of the application server device according to the embodiment. FIG. 4 is a block diagram showing an example of the functional configuration of the store server device according to the embodiment. FIG. 5 is a block diagram showing an example of the functional configuration of the information server device according to the embodiment. FIG. 6 is a block diagram showing an example of the functional configuration of the bind database device according to the embodiment. FIG. 7 is a diagram showing a system installation example in the first embodiment. FIG. 8 is a sequence chart showing an example of processing operation of the system until the user purchases and uses the device device in the same embodiment. FIG. 9A is a diagram showing an example of data generated and managed by the bind database device for one user in the same embodiment. FIG. 9B is a diagram showing an example of data generated and managed by the bind database device for a plurality of users in the same embodiment. FIG. 10 is a diagram showing a system installation example in the second embodiment. FIG. 11 is a sequence chart showing an example of processing operation of the system until the user purchases and uses the device device in the same embodiment. FIG. 12 is a diagram showing a system installation example in the third embodiment. FIG. 13 is a diagram showing a system installation example in the fourth embodiment. FIG. 14 is a diagram showing a system installation example in the fifth embodiment. FIG. 15 is a sequence chart showing an example of processing operation of the system when a user gives a device device to another user in the same embodiment. FIG. 16 is a sequence chart showing a second processing operation example of the system when a user gives a device device to another user in the same embodiment. FIG. 17 is a diagram illustrating an example of the relationship between the types of data used in the embodiment and each data.

Hereinafter, embodiments will be described with reference to the drawings.

FIG. 1 is a diagram showing a configuration example of the entire system according to the embodiment.

Device devices 1A and 1B (referred to simply as device device 1 unless otherwise specified) are all types of IoT devices, which are connected to the network 100 and carry out data communication with the devices on the network 100. The device device 1 may be, for example, sensors such as a temperature detection sensor, a water leak detection sensor, a door open / close sensor, or a detection device using these sensors. Further, the device device 1 may be a home appliance such as an air conditioner, a television, a lighting, and a camera. Further, as long as it is connected to the network 100, a mobile terminal such as a smartphone may be used.

The application server device 2 is built on, for example, a computer having a CPU and a memory installed on the network 100, and provides an application using the device device 1. The application server device 2 may be a cloud server. For example, a water leak detection device is assumed as the device device 1. When the device device 1 detects a water leak, the application server device 2 transfers an application using the device device 1 such as transferring a notification from the device device 1 to a smartphone registered in advance with an alarm notified to the application server device 2. provide. Although only one application server device 2 is shown in the figure, a plurality of application server devices 2 may be installed for each type of device device 1. Further, the application server device 2 may provide an application in which a plurality of device devices 1 are combined. In particular, in this embodiment, an application using the bind database device 5 described later is assumed.

The store server device 3 is built on, for example, a computer having a CPU and a memory installed on the network 100. The store server device 3 may be a cloud server. The store server device 3 is installed, for example, in a company that sells the device device 1 to the user, and when the user obtains the device device 1, exchanges necessary data with the device in the system via the network 100. carry out. The method for the user to obtain the device device 1 is described in the case of purchasing in the present embodiment, but the user can obtain it by leasing or renting, free acquisition by campaign, discount acquisition, gift from another person, prize, prize, etc. But it may be. The store server device 3 may have a function of a POS (Point Of Sale) terminal. The store server device 3 identifies information (users of device device 1) such as user IDs, e-mail addresses, and telephone numbers from cards such as credit cards, point cards, and My Numbers (registered trademarks). Hereinafter, a card reader for acquiring user identification information) may be provided. Further, the store server device 3 may set a Uniform Resource Locator (URL) for providing a service to the client via the network 100.

The information server device 4 is built on, for example, a computer having a CPU and a memory installed on the network 100. The information server device 4 manages user personal information such as a name, address, and telephone number (hereinafter referred to as user information) in association with user identification information, and provides information in response to a request.

The bind database device 5 is built on, for example, a computer having a CPU and a memory installed on the network 100. The bind database device 5 stores (bound) data in which the user information of the purchaser and the purchased product information are associated with each other, and generates a database (particularly referred to as a bind database). Here, the product information is, for example, a product name, a manufacturer name, a model number, a serial number, or the like. Further, the bind database device 5 may generate information unique to the device / device to be registered (particularly referred to as device / device-specific information) using, for example, a manufacturer name, a model number, a serial number, etc., and add it to the database. The device device-specific information is information that can identify individual device devices, and may be a character string including numbers and symbols that can be identified from the manufacturer name, model number, serial number, and the like.

The PC 6 is, for example, a personal computer, and is a client terminal for accessing the store server device 3 via, for example, the network 100. The PC 6 may be a personal computer owned by the user at home in the case of mail order, or may be a personal computer installed in the store in the case of store sales.

The network 100 includes not only the Internet but also all networks and communication paths for connecting the above-mentioned devices and devices, and a network formed by combining them. For example, when the store server device 3 communicates with the information server device 4 that handles user information, a dedicated line for ensuring confidentiality, a Virtual Private Network (VPN) realized on the Internet, or the like is used. Communication paths are also included in the network 100. Further, the network 100 may be wireless as well as wired, and may include, for example, a communication method such as WiFi (registered trademark) or 5G. In the case of wired communication, for example, a communication method using an Ethernet cable may be included. Further, in data transmission / reception on the network 100, a communication protocol predetermined by devices and devices and their data communication paths is used.

FIG. 2 is a block diagram showing an example of the functional configuration of the device device according to the embodiment.

The communication unit 11 is connected to the network 100, and the device device 1 communicates with a device or device on the network 100. The communication unit 11 includes a wired or wireless communication interface. Further, the communication unit 11 may include not only an interface with the network 100 but also an interface such as a Universal Serial Bus (USB) for connecting to a personal computer, for example.

The application processing unit 12 performs processing for making the application provided by the application server device 2 available by a computer program or the like stored in the device device 1.

The storage unit 13 stores settings and the like required for the device device 1. Settings to the storage unit 13 and the like are performed from a personal computer or the like via a control unit (not shown), a USB provided in the communication unit 11, or the like.

FIG. 3 is a block diagram showing an example of the functional configuration of the application server device according to the embodiment.

The communication unit 21 is connected to the network 100 and communicates with devices and devices on the network 100. The communication unit 21 includes a wired or wireless communication interface.

The application service unit 22 performs processing for providing an application by using a computer program or the like stored in the application server device 2. For example, when assuming a temperature detection application using the device device 1, the application service unit 22 receives and processes the temperature detection result transmitted by the device device 1, and another device or device on the preset network 100. Provide an application such as notifying an alarm via a communication unit 11.

The information inquiry processing unit 23 makes an information inquiry to the device on the network 100 via the communication unit 21 in accordance with the command from the application service unit 22, acquires the inquired information, and outputs the inquired information to the application service unit 22. .. In the present embodiment, the information inquiry processing unit 23 queries the bind database device 5 for information.

FIG. 4 is a block diagram showing an example of the functional configuration of the store server device according to the embodiment.

The UI unit 31 is a user interface, and is, for example, a card reader that reads user identification information from a credit card, a point card, or a My Number card. The UI unit 31 outputs the read user identification information to the control unit 32. Further, the UI unit 31 may read information from a smartphone, or may be a computer peripheral device such as a keyboard or a mouse. When the UI unit 31 is a keyboard, the user or the seller may input information about the user including the user identification information from the keyboard.

The control unit 32 controls each function of the store server device 3 based on the user identification information input from the UI unit 31. In FIG. 4, data can be exchanged with all the other functional blocks that are not connected to the control unit 32.

The information inquiry processing unit 33 inquires the external device of necessary information via the communication unit 34 based on the command input from the control unit 32, and acquires the information. In the present embodiment, the information inquiry processing unit 33 makes an inquiry to the information server device 4 based on the user identification information input from the control unit 32, and acquires the user information.

The communication unit 34 is connected to the network 100 and communicates with devices and devices on the network 100. The communication unit 34 includes a wired or wireless communication interface.

The bind database registration unit 35 transmits necessary information to the bind database device 5, such as user information and product information of purchased products.

The service providing unit 36 includes, for example, an electronic commerce site for enabling a user to purchase a product via the Internet, and a processing function at the time of purchase. This function does not have to be used for store sales instead of online sales. The service providing unit 36 acquires the purchase information of the user.

FIG. 5 is a block diagram showing an example of the functional configuration of the information server device according to the embodiment.

The information registration unit 41 includes a user interface such as a keyboard for importing user information into the information server device 4, processes the information imported from the user interface as necessary, and outputs the information to the storage unit 42. For example, when the information registration unit 41 creates a database of user information at a credit card company or a point card company, the information input from the user interface is processed into a database as necessary. The information registration unit 41 issues user identification information, which is user-specific identification information (ID), when registering user information in the database. The user identification information is, for example, a credit card number, a point card ID, or the like, and is stored in an integrated circuit (IC) or the like on a card such as a credit card or a point card. The function of the information registration unit 41 is usually executed when a credit card, a point card, or the like is issued.

The storage unit 42 stores data such as user information input from the information registration unit 41.

The information providing unit 43 receives a request for providing data stored in the storage unit 42 from an external device, acquires the requested data from the storage unit 42, and sends the acquired data to the requesting external device via the communication unit 44. And send.

The communication unit 44 is connected to the network 100 and communicates with devices and devices on the network 100. The communication unit 44 includes a wired or wireless communication interface.

The control unit 45 controls each function of the information server device 4. In FIG. 5, data can be exchanged between the control unit 45 and all the other functional blocks that are not connected.

FIG. 6 is a block diagram showing an example of the functional configuration of the bind database device according to the embodiment.

The control unit 51 controls each function of the bind database device 5. Specifically, the control unit 51 receives a request from an external device on the network 100, and controls each function of the bind database device 5 according to the received request. In FIG. 6, data can be exchanged between the control unit 51 and all the other functional blocks that are not connected.

The communication unit 52 is connected to the network 100 and communicates with devices and devices on the network 100. The communication unit 52 includes a wired or wireless communication interface.

The information registration unit 53 creates information registration, that is, a bind database, in accordance with an information registration request received by the control unit 51 from an external device on the network 100. In the present embodiment, when the control unit 51 receives the information registration request from the store server device 3, the information registration unit 53 receives the user information, product information, and the like transmitted by the store server device 3 according to the control of the control unit 51. It is stored in the storage unit 54 and a bind database is created.

The specific information generation unit 531 creates a bind data user ID which is user specific information for identifying a user on the bind database. The bind data user ID may be a number or a character string including characters, numbers and the like. Further, the specific information generation unit 531 creates a device management number assigned to each user for the device device 1 registered in the bind database. The device management number may be a number or a character string including characters, numbers and the like. The device management number can be used as device device-specific information, which is device-specific information.

The storage unit 54 stores data input from the information registration unit 53.

When the control unit 51 receives an information provision request from an external device on the network 100, the information providing unit 55 acquires data from the storage unit 54 in accordance with the request, and requests the data via the communication unit 52. Send to the device.

(First Embodiment)
In this embodiment, an operation example of the system when a user purchases a device device 1 from a home PC 6 at a mail-order company on the network 100 will be shown.

FIG. 7 is a diagram showing a system installation example in the first embodiment.

The user is the purchaser of the device device 1 and owns the PC 6. The mail-order company is a seller of the device device 1, and owns the store server device 3 and the information server device 4. The information server device 4 manages user identification information (customer ID) required when a user purchases a product at a mail-order company. In addition, the mail-order company stores the device device 1 which is a product purchased by the user. The service provider is an application provider of the device device 1, and owns the application server device 2 and the bind database device 5.

FIG. 8 is a sequence chart showing an example of processing operation of the system until the user purchases and uses the device device in the embodiment.

This sequence chart shows each process of PC 6, store server device 3, information server device 4, bind database device 5, device device 1, and application server device 2 in chronological order from top to bottom from the left. In the PC 6 and the store server device 3, the operation behaviors by the user and the store clerk, including the presence of the user and the store clerk of the mail order company, are shown by dotted lines in this sequence chart. The clerk of the mail-order company ships the device device 1 to the user. At that time, the clerk may make settings for the device device 1 as necessary. The processing by the PC 6, the store server device 3, and other devices (processing that does not depend on humans) is shown by a solid line.

Hereinafter, this sequence chart will be described in chronological order from the top.

The user pre-registers the user information with the mail-order company, obtains the user identification information (customer ID), and purchases the device device 1 (Phase P1). Hereinafter, details will be described.

The user accesses the electronic commerce site provided by the store server device 3 from the PC 6 and registers user information and the like in order to acquire an account (step S11). Specifically, the user transmits the user information from the PC 6 to the store server device 3 together with the user information registration request.

Upon receiving the user information registration request, the control unit 32 of the store server device 3 causes the service providing unit 36 to execute the user information registration (step S12). The service providing unit 36 transmits the user information and the like to the information server device 4 together with the user information registration request.

In the information server device 4, when the control unit 45 receives the user information registration request, the control unit 45 outputs the user information or the like to the information registration unit 41 to execute the user information registration. The information registration unit 41 adds the received user information to the database of the storage unit 42, issues the user identification information (customer ID), and transmits the user identification information from the communication unit 44 to the store server device 3 (step S13). .. The store server device 3 notifies the user by transmitting the received user identification information to the PC 6 or the like (step S14). By using the user identification information received by the PC 6, the user can purchase the product from the mail order company.

The user purchases the device device 1 from the PC 6 at the electronic commerce site of the store server device 3 (steps S15 and S16). Specifically, the user accesses the electronic commerce site provided by the service providing unit 36 of the store server device 3 from the PC 6 via the network 100. On the electronic commerce site, for example, when the user clicks the name of the device / device 1 to be purchased (step S15) or inputs user payment information (information such as credit payment or bank payment) or user identification information. (Step S16), purchase information such as product information of device device 1 and user payment information and user identification information are transmitted to the service providing unit 36. When the service providing unit 36 receives the information, the service providing unit 36 displays, for example, "purchase completed" on a display unit (not shown) of the PC 6, thereby completing the purchase process by the user.

Next, the store server device 3 executes a database generation process (Phase P2).

The store server device 3 transmits a user information inquiry from the information inquiry processing unit 33 to the information server device 4 via the communication unit 34 together with the user identification information acquired in the phase P1 (step S21). In the information server device 4, when the control unit 45 receives the user information inquiry, the control unit 45 causes the information providing unit 43 to transmit the user information (step S22). Specifically, when the information providing unit 43 is instructed to transmit the user information from the control unit 45, the information providing unit 43 acquires the user information from the storage unit 42 based on the received user identification information. The information providing unit 43 transmits the user information acquired via the communication unit 44 to the store server device 3.

The store server device 3 transmits the received user information and product information as database information to the bind database device 5 (step S23). Specifically, in the store server device 3, the bind database registration unit 35 combines the user information received by the information inquiry processing unit 33 and the product information received by the service providing unit 36, and processes them as necessary. And create database information. The bind database registration unit 35 transmits a database registration request (data bind request) together with the created database information to the bind database device 5.

When the bind database device 5 receives the database registration request, it registers the received database information in the database (step S24). More specifically, when the control unit 51 receives the database registration request in the bind database device 5, the control unit 51 outputs the received database information to the information registration unit 53. The information registration unit 53 registers the database information in the storage unit 54. By the above procedure, a database (bind database) in which user information and product information are linked is generated on the bind database device 5.

FIG. 9A is a diagram showing an example of data generated and managed by the bind database device for one user in the embodiment.

The bind data 500 includes user-specific data 501 and product data 502, and basically one is created for one user. For example, when a certain organization uses all the devices and devices 1 in common, one bind data 500 is created as an organization. In this embodiment, an example of creating one bind data 500 for one user is shown.

The user-specific data 501 stores user-specific information (for example, the bind data user ID) given to the user who manages the data in the bind database device 5. The user-specific data 501 may be user identification information or the like in addition to the bind data user ID as data that can identify the individual user. Further, as long as the user can be identified, the user-specific data 501 may be, for example, only a telephone number or an e-mail address, and data that can identify an individual user without much change is desirable. Further, the user-specific data 501 may include user personal information such as a name, an address, and a date of birth.

The product data 502 includes data such as "No", "product name", "manufacturer", "model number", and "serial number" shown as column items for each device device 1 which is a product. Every time the user purchases the device device 1, a row is added and the information of each column item is registered. “No” is a device management number managed by the bind database device 5 for the device device 1. It is desirable to assign the device management number so that the device that can be used by each user is a unique number, and select one from the following "product name", "manufacturer", "model number", "serial number", etc. The device management number may be used, or the device management number may be generated from the selected one. In addition, a plurality of products may be selected from the following "product name", "manufacturer", "model number", "serial number", etc., and the combination may be used as the device management number, or a device management number may be generated from the selected combinations. May be good. The "product name" is the name of the device device 1. "Manufacturer" is the name of the manufacturer of the device device 1. The "model number" is a character string including characters, numbers, and the like given by the manufacturer to the model and the like of the device device 1. The "serial number" may be a character string including characters, numbers, etc. uniquely assigned to the device / device 1 by the manufacturer. Column items can be added. For example, when an IP address is assigned to the device device 1, the IP address may be added to the database. Further, the IP address of a certain application server device 2 that provides an application that can use the device device 1 may be added.

D11, D12, D13, and D14 of the product data 502 are "product name", "manufacturer", "model number", and "serial number" for the device device 1 having No = 1, respectively. The "product name", "manufacturer", "model number", and "serial number" for the device device 1 of No = i are Di1, Di2, Di3, and Di4, respectively. N of the item "No" corresponds to the number of registered devices 1 that can be used by the user.

FIG. 9B is a diagram showing an example of data generated and managed by the bind database device for a plurality of users in the embodiment.

In the storage unit 54 of the bind database device 5, bind data 500A, 500B, and 500C for each of a plurality of different users (or organizations such as corporations) are stored.
Returning to FIG. 8, when the specific information generation unit 531 of the bind database device 5 issues the bind data user ID, the information registration unit 53 transmits a completion notification (step S25). Further, in step S25, the bind data user ID issued together with the completion notification may be transmitted. When the store server device 3 receives the bind data user ID, the store server device 3 displays it on a display unit (not shown) of the store server device 3. If the user information registered when the device device 1 was purchased in the past is already registered in the bind database device 5 and the bind data user ID is given to the user, the bind data user ID is completed. Send with notification. The device management number may also be transmitted at the same time.

Next, the mail-order company ships the product to the product (Phase P3). Further, in the phase P3, parameters may be set in the device device as needed.

The mail-order company may set information such as necessary parameters for the newly purchased device / device 1 (step S31). The setting information includes a "serial number", a "model number", a "device management number", and the like of the device device 1 as device device-specific information for identifying the device device 1, and is set in the storage unit 13. Further, the bind data user ID is set in the storage unit 13 as the user identification information for identifying the user. Further, the user-specific information may be a telephone number, an e-mail address, or the like. Further, the user identification information may be used as the user identification information. Further, the setting information includes the IP address of the application server device 2 which is information that enables communication with the application server device 2, the application site URL provided by the application server device 2, and the like, and is stored in the storage unit 13. .. Further, instead of the application server device 2, the setting may include the IP address and URL of the bind database device 5. The mail-order company ships the device device 1 to the user who purchased it (step S32). In step S32, the mail-order company may ship the device / device 1 whose parameters are set in step S31 to the user who purchased it. On the other hand, the mail-order company may ship the device / device 1 having no parameter setting to the purchased user without performing step S31.

It should be noted that the device / device 1 having exactly the same "manufacturer", "serial number", "model number", etc. may be registered in the bind data 500 of different users. For example, it corresponds to the case where one device / device 1 is shared by different users in advance. In this case, the user-specific information of the shared user and the product information of the new device device 1 are bound and registered in the bind data 500 of the user shared in the steps S16 to S26 of FIG. This will be described in detail.

The user identification information of the user who purchases the device device (hereinafter referred to as the purchasing user) and the user identification information of the shared user (hereinafter referred to as the shared user) are transmitted to the store server device 3 (step S16). The store server device 3 transmits the received user identification information of each of the purchased user and the shared user to the information server device 4, inquires about the user information, and acquires the respective user information (steps S21 and S22). The store server device 3 transmits the user information and product information of the purchasing user and the shared user to the bind database device 5 (step S23). The bind database device 5 creates a bind database for each of the purchasing user and the shared user (step S24).

If the shared user is a user who has already been registered in the bind data 500, the bind data user ID has already been acquired. Therefore, the processes of steps S21 and S22 are omitted, and the bind data user ID and the new user ID are added in step S23. By transmitting the product information of the device device 1 to the bind database device 5, the new device device 1 may be registered in the bind data 500 of the user.

Next, the user who purchased the device device 1 receives, installs, and uses the device device 1 which is a product (Phase P4).

When the user receives the device / device 1 shipped by the mail-order company, the user installs it at a required place (step S41). When a wired connection is required to connect to the network 100, for example, an Ethernet cable is connected to the device device 1 and installed so as to enable access to the network 100. The user activates the device device 1 by pressing the power switch of the device device 1 (step S42). When the power of the device device 1 is turned on, the device device 1 is started (step S43). When the device device 1 is started, the application processing unit 12 accesses the application server device 2 via the network 100 by referring to the IP address of the application server device 2 stored in the storage unit 13, for example (step S44). At the time of access, the user-specific information (bind data user ID, e-mail address, telephone number, etc.) and device-specific information stored in the storage unit 13 are transmitted to the application server device 2. The user-specific information and device device-specific information may be used as an account for permission when the device device 1 accesses the application server device 2.

When the application service unit 22 detects the access from the application processing unit 12 in the application server device 2, it is confirmed whether or not the received user identification information and the device device specific information are linked, that is, the device device 1 is the purchasing user. Alternatively, the bind database device 5 is requested to confirm whether the product is bound to a user who is permitted to use the product (hereinafter referred to as confirmation of bind information) (step S45). More specifically, when the application service unit 22 requests the information inquiry processing unit 23 to confirm the binding information, the information inquiry processing unit 23 binds the binding information confirmation request together with the user specific information and the device device specific information. It is transmitted to the database device 5.

When the bind database device 5 receives the confirmation request of the bind information, the received user identification information and the device device specific information are associated with each other, that is, the device device 1 having the device device specific information is a user having the user specific information. It is confirmed whether it is owned or usable, and the confirmation result of the binding information is transmitted to the application service unit 22 (step S46). More specifically, when the control unit 51 receives the request for the bind information, the control unit 51 outputs the user-specific information and the device device-specific information received at the same time to the information providing unit 55. The information providing unit 55 confirms whether or not there is data matching the received user-specific information and device device-specific information in the bind data 500 stored in the storage unit 54. When the information providing unit 55 finds the device device 1 that matches the received user identification information and device device specific information in the bind data 500, the information providing unit 55 transmits a response of "YES" to the application server device 2. If there is no device / device 1 that matches the received user-specific information and device / device-specific information, a “NO” response is transmitted to the application server device 2.

When the application server device 2 receives "YES", the application server device 2 starts the application using the device device 1 purchased in step S13 (step S47). When the application server device 2 receives "NO", the application server device 2 prohibits the use of the application by the accessing device / device 1. At this time, the application server device 2 may make a reply of, for example, "access prohibited" to the device device 1 that has accessed.

By the above procedure, the user can use the application using the device device 1. According to the embodiment of the present embodiment, the user can use the device device 1 simply by purchasing the device device 1 on the electronic commerce site, installing the device device 1, and pressing the power switch. Further, in the bind database device 5, by creating a bind database that connects the device device 1 and the purchasing user, there is an effect of eliminating the complexity such as initial setting when the device device 1 is purchased. Further, by creating the bind database, the convenience that the initial setting at the time of purchasing the device device 1 becomes unnecessary is brought about. These effects are effective for both the user and the store clerk who sets parameters and the like for the device device 1, and the effect increases as the number of device devices 1 registered for individual users increases. Further, by clarifying the owner and the user of the device device 1 by the bind database device 5, there is a security effect such as prohibiting the use of the device device 1 by a user other than the owner and the user.

Considering that the number of device devices 1 connected to the network 100 (Internet) will increase in the future and will be used by many users, the effectiveness of facilitating the handling of device devices by the bind database device 5 will further increase. Further, the bind database device 5 shown in the present embodiment can also be used for an application in which a plurality of device devices 1 owned by the user are linked. Further, by collecting the bind data of a plurality of users in the bind database device 5, it can be used for cooperation between devices owned by different users.

In the present embodiment, the case where the user has never purchased the device device 1 and the user information is not registered in the bind database device 5 has been shown. However, for example, the user has purchased the device device 1 in the past. When the user information is registered in the bind database device 5 and the bind data user ID is already assigned to the bind data for the user, the procedure can be further simplified.

Further, in the present embodiment, in the parameter setting in step S31, for example, any one of the bind data user ID, e-mail address, telephone number, etc. may be set as the user identification information, or any one of a plurality of them. The combination may be set. For example, the strength of security in using the service of the application server device 2 by the device device 1 (step S47) can be changed depending on the number of user-specific information set in the device device 1. Specifically, in steps S45 and S46, the greater the number of user-specific information used by the information providing unit 55 as a determination condition in the response of the bind database device 5 to the information inquiry processing from the application server device 2, the more security. You can increase the strength of. Further, in the bind database device 5, priority may be given to the user-specific information, and the determination condition of the information providing unit 55 may be weighted. For example, when the bind user ID is given priority to the e-mail address (when weighted), the device device 1 that uses the bind user ID as the user identification information is not permitted to use the e-mail address. It may be possible to read advanced information (eg, information about checking the balance) or to have important controls (eg, controls related to payment of money) that are not permitted by the use of email addresses.

(Second embodiment)
In the present embodiment, a system in which a user (purchaser) who owns a customer ID of a mail-order company purchases a product (device device 1) at the mail-order company, and the mail-order company orders a product from a service company. An operation example of is shown. Further, an operation example of the system when the user has purchased the device device 1 in the past and the user information is already registered in the bind database device 5 is also shown.

FIG. 10 is a diagram showing a system installation example in the second embodiment.

The user is the purchaser of the device device 1 and owns the PC 6. The mail-order company is a seller of the device device 1, and owns the store server device 3 and the information server device 4. The service provider is an application provider of the device device 1, and owns the application server device 2 and the bind database device 5. In the present embodiment, unlike the first embodiment, it is the service provider that stores the device device 1 which is a product purchased by the user.

FIG. 11 is a sequence chart showing an example of processing operation of the system until the user purchases and uses the device device in the same embodiment, and the same phase as that of the procedure shown in FIG. 8 is shown in the same phase. Give the code of the step. The same parts as those in FIG. 8 will be omitted or simplified.

Since the procedure of pre-registration and purchase is the same as that of Phase P1 of FIG. 8, the description thereof will be omitted.

When the user pre-registration and purchase procedure is completed, a database of bind data is generated (Phase P22). Specifically, when the store server device 3 acquires the customer ID, which is the user identification information of the mail-order company (step S16 in FIG. 8), the store server device 3 inquires of the information server device 4 about the user information of the customer ID (step S221). .. The information server device 4 takes out the received user information of the customer ID from the storage unit 42 of the information server device 4 and transmits it to the store server device 3 (step S222). The store server device 3 transmits the database information including the received user information and the purchase information acquired in the phase P1 to the bind database device 5 (step S223). The bind database device 5 confirms whether the received user information is registered in the user-specific data 501 of the storage unit 54, and if it has already been registered, registers the received purchase information in the product data 502 (S224). Further, if the received user information is not registered in the user-specific data 501 of the storage unit 54, the bind database device 5 registers the user information in the user-specific data 501 and registers the received purchase information in the product data 502. , Issue a bind data user ID to that user. When the bind database device 5 completes the registration of the database information, the bind database device 5 notifies the service provider by displaying the bind data user ID, for example, on a display unit (not shown) of the bind database device 5 (step S225).

Next, the service provider ships the product to the product (Phase P23). Further, in this phase, parameters may be set in the device device as needed. In this phase, from the phase P3 shown in the first embodiment, the implementing entity only changes from the mail-order company to the service company. Since the contents of the implementation will not change, the description will be omitted.

Next, the user who purchased the device device 1 receives, installs, and uses the device device 1 which is a product (Phase P4). Since this phase is the same as the phase P4 shown in the first embodiment, the description thereof will be omitted.

By the above procedure, even when the user (purchaser) purchases the product (device device 1) at the mail-order company and the mail-order company orders the product from the service company, the user (purchaser) is the electronic mail-order company. The device device 1 can be used by purchasing the product (device device 1) from the commercial transaction site by a simple procedure.

(Third Embodiment)
In the present embodiment, an operation example of the system when a user (purchaser) purchases a product (device device 1) at a store using a point card issued by the store is shown.

FIG. 12 is a diagram showing a system installation example in the third embodiment.
The user is a purchaser of the device device 1. The store is a seller and a place of sale of the device device 1, and owns a PC 6, a store server device 3, and an information server device 4. The information server device 4 manages the user information of the owner of the point card. The service provider is an application provider of the device device 1, and owns the application server device 2 and the bind database device 5. The only difference between the present embodiment and the first embodiment is that the seller of the device device 1 has changed from a mail-order company to a store sales, and the operation processing flow of the system is the same as the sequence chart of FIG. Therefore, only the differences from the first embodiment will be described with reference to FIG.

The user goes to the store and registers user information in order to obtain a point card issued by the store. (Step S11). When the user inputs the user information from the PC 6 of the store, the user information is transmitted to the store server device 3 together with the point card registration request.

Upon receiving the point card registration request, the control unit 32 of the store server device 3 causes the service providing unit 36 to execute account registration (step S12). The service providing unit 36 transmits user information and the like to the information server device 4 together with a point card registration request.

In the information server device 4, when the control unit 45 receives the point card registration request, the control unit 45 outputs user information or the like to the information registration unit 41 to execute the point card registration. The information registration unit 41 adds the received user information to the database of the storage unit 42, issues the user identification information (user ID of the point card), and transmits the user identification information from the communication unit 44 to the store server device 3 ( Step S13). In the information server device 4, the registered user information is managed in association with the user identification information.

The store server device 3 notifies the user by transmitting the received user identification information to the PC 6 or the like. (Step S14). Normally, a card equipped with a memory containing user identification information data is issued to the user as a point card.

When the purchase information is transmitted to the store clerk, the store clerk inputs the purchase information from the PC 6 and transmits the purchase information to the store server device 3 (step S15). When the user holds the point card over a card reader or the like connected to the PC 6, the user identification information is input to the PC 6 and the user identification information is transmitted to the store server device 3 (step S16). Since the following are the same as the phases and steps shown in FIG. 8, the description thereof will be omitted.

By the above procedure, even when the user (purchaser) purchases the product (device device 1) at the store using the point card, the user (purchaser) purchases the product (device device 1) by a simple procedure. The device device 1 can be used.

(Fourth Embodiment)
In the present embodiment, an operation example of the system when the user A (purchaser) purchases a product (device device 1) by using a credit card at a store is shown.

FIG. 13 is a diagram showing a system installation example in the fourth embodiment.
The user is a purchaser of the device device 1. The store is the seller and the place of sale of the device device 1, and owns the PC 6 and the store server device 3. The credit card company owns the information server device 4. The information server device 4 manages the user information of the credit card owner. The service provider is an application provider of the device device 1, and owns the application server device 2 and the bind database device 5. Since the operation processing flow of the system is the same as the sequence chart of FIG. 8, only the differences from the first and third embodiments will be described with reference to FIG.

When the user goes to the store and conveys the purchase information to the clerk, the clerk inputs the purchase information to the clerk in the PC 6 and sends the purchase information to the store server device 3 (step S15). When the user holds the credit card over the card reader connected to the PC 6, the user identification information is input to the PC 6 and the user identification information is transmitted to the store server device 3 (step S16). Here, it is assumed that the user registration of the credit card itself has already been completed, and the user information of the credit card owner is registered in the information server device 4, and the description of steps S11 to S14 is omitted. Since the following are the same as the phases and steps shown in FIG. 8, the description thereof will be omitted.

By the above procedure, even when the user (purchaser) purchases the product (device device 1) at the store using a credit card, the user (purchaser) can purchase the product (device device 1) by a simple procedure. You can purchase and use device device 1.

(Fifth Embodiment)
In the present embodiment, an operation example of the system when the user A (purchaser) gives the device device 1 to the user B (recipient) is shown. User A (purchaser) purchases device device 1 at a mail-order company. The mail-order company registers the information of the user B in the bind database device, acquires the bind database ID of the user B, sets the necessary parameters for the device device 1, and ships the device device 1 to the user B. There are cases where user B is not registered in the bind database device and cases where it is already registered. First, an operation example of the system is shown for the case where it is not registered.

FIG. 14 is a diagram showing a system installation example in the fifth embodiment.

The user is the purchaser of the device device 1 and owns the PC 6. The mail-order company is a seller of the device device 1, and owns the store server device 3 and the information server device 4. In addition, the mail-order company stores the device device 1 which is a product purchased by the user. The service provider is an application provider of the device device 1, and owns the application server device 2 and the bind database device 5. The system installation in FIG. 14 is the same as the example in FIG. 7 shown in the first embodiment, but in this figure, two users A and B are assumed. In this example, for example, when a child (user A) introduces a device device for a separate parent household (user B) who is unfamiliar with various setting work, or for a child (user B) who is boarding. It is assumed that the parent (user A) introduces the device.

FIG. 15 is a sequence chart showing an example of processing operation of the system when a user gives a device device to another user in the same embodiment.
Hereinafter, this sequence chart will be described in chronological order from the top.

User information of user B is pre-registered, and user A purchases device device 1 (Phase P51).

In the present embodiment, it is assumed that the pre-registration of the user information of the user B is performed by the user B in advance, and the user identification information of the user B (user B identification information) is issued. (Steps S151 to S154). The details of the issuing procedure are the same as in steps S11 to S14 of FIG. 8, and thus the description thereof will be omitted.

The user A receives the user identification information of the user B from the user B, and purchases the device device 1 from the PC 6 (steps S155 and S156). Specifically, the user A accesses the electronic commerce site provided by the service providing unit 36 of the store server device 3 from the PC 6 via the network 100. On the electronic commerce site, for example, the user A clicks the name of the device device 1 to be purchased, selects the device device 1 to be purchased, inputs the user identification information and payment information of the user B, and inputs the user identification information, payment information, etc. When the "OK" button or the like is clicked, purchase information such as product information and payment information of the device device 1 and user identification information of the user B are transmitted to the service providing unit 36. When the service providing unit 36 receives the information, for example, the service providing unit 36 displays a display such as "purchase completed" on the PC 6, so that the purchase process by the user A is completed.

Next, the store server device 3 executes a database generation process (Phase P52).

The store server device 3 transmits the user information inquiry of the user B from the information inquiry processing unit 33 to the information server device 4 via the communication unit 34 together with the user identification information of the user B acquired in the phase P51 (step S251). In the information server device 4, when the control unit 45 receives the user information inquiry of the user B, the control unit 45 causes the information providing unit 43 to transmit the user information of the user B (step S252). Specifically, when the information providing unit 43 is instructed by the control unit 45 to transmit the user information of the user B, the information providing unit 43 acquires the user information of the user B from the storage unit 42 based on the received user identification information of the user B. To do. The information providing unit 43 transmits the user information of the user B acquired via the communication unit 44 to the store server device 3.

The store server device 3 transmits the received user information and product information of the user B to the bind database device 5 as database information (step S253). Specifically, in the store server device 3, the bind database registration unit 35 needs to combine the user information of the user B received by the information inquiry processing unit 33 with the product information received by the service providing unit 36. Processing is performed accordingly, and the database information of user B is created. The bind database registration unit 35 transmits a database registration request to the bind database device 5 together with the created database information.

When the bind database device 5 receives the database registration request (data bind request), the bind database device 5 registers the received database information in the database (step S254). More specifically, when the control unit 51 receives the database registration request in the bind database device 5, the control unit 51 outputs the received database information to the information registration unit 53. The information registration unit 53 registers the database information in the storage unit 54. By the above procedure, it is possible to generate a database in which the user information of the user B and the product information purchased by the user A are linked (bound).

When the registration of the bind data 500 is completed, the information registration unit 53 of the bind database device 5 transmits a completion notification together with the Indian data user ID of the user B created by the specific information generation unit 531 (step S255). The store server device 3 receives the bind data user ID and displays it on a display unit (not shown) of the store server device 3.

Next, the mail-order company sets parameters for the product and ships the product (Phase P3). Since the operation example in this phase is the same as that in FIG. 8, the description thereof will be omitted, but unlike the case of the first embodiment, the mail-order company is not the purchaser user A but the user B the device device 1. To ship.

Next, the user B receives, installs, and uses the device device 1 (Phase P54).

When the user B receives the device / device 1 shipped by the mail-order company, the user B installs it at a necessary place (step S451). If necessary, an Ethernet cable for connecting to the network 100 is connected to the device device 1, and the device device 1 is connected to the network 100. The user B activates the device device 1 by pressing the power switch of the device device 1 (step S452). When the power of the device device 1 is turned on, the device device 1 is started (step S453). When the device device 1 is activated, the application server device 2 is accessed via the network 100 (step S454). Hereinafter, steps S454 to S457 are the same as steps S44 to S47 in FIG. 8, and therefore detailed description thereof will be omitted.

When the application service unit 22 detects the access from the application processing unit 12 in the application server device 2, is the device device 1 that has the access and the user (user B in the case of this embodiment) linked? The binding database device 5 is requested to confirm the binding information (step S455). The bind database device 5 confirms the bind information and transmits the confirmation result of the bind information to the application service unit 22 (step S456).

When the application server device 2 receives "YES" as the confirmation result of the binding information, the application server device 2 starts the application using the device device 1 purchased in step S153 (step S457). When the application server device 2 receives "NO" as the confirmation result of the binding information, the application server device 2 prohibits the use of the application by the accessing device / device 1.

According to the above procedure, when the user A (purchaser) gives the device device 1 to the user B (recipient) who does not have the bind database ID, the user B (recipient) can use the device device 1. it can. Next, a case where the user B has registered the user-specific information in the bind database device and has the bind database ID will be described.

FIG. 16 is a sequence chart showing a second processing operation example of the system when a user gives a device device to another user in the same embodiment.

Hereinafter, this sequence chart will be described in chronological order from the top.

User A purchases device device 1 (Phase P61).

User A has obtained the bind user ID of user B from user B in advance. When the user A accesses the electronic commerce site provided by the service providing unit 36 of the store server device 3 from the PC 6 and inputs the purchase information regarding the device device 1 to be purchased and the bind user ID of the user B, the purchase information and the user B The bind user ID is transmitted to the store server device 3 (steps S163 and S164).

Next, the store server device 3 executes a database generation process (Phase P62).

The store server device 3 transmits the bind user ID of the user B acquired in the phase P61 and the product information of the device device 1 to be purchased as database information to the bind database device 5 together with the database registration request (step S263).

When the bind database device 5 receives the database registration request, the bind database device 5 registers the received database information in the database (step S264). More specifically, the bind database device 5 searches for the bind data 500 in which the received bind data ID is registered among the bind data 500 registered in the storage unit 54, and receives the product in the found bind data 500. Add information. By the above procedure, it is possible to generate a database in which the user information of the user B and the product information purchased by the user A are linked.

Hereinafter, the phase of setting parameters to the product and the phase of shipping the product is the same as the phase P3 of FIG. 8, and the phase of installing and using the product is the same as the phase P54 of FIG. 8, so the description thereof will be omitted.

According to the above procedure, when the user B has the bind database ID, that is, when the user-specific information has been registered in the bind database device, the user A (purchaser) gives the user B (recipient) the device device 1. The user B (recipient) can use the device device 1.

(Sixth Embodiment)
In this embodiment, an example is shown in which a store clerk of a store (mail order company) uses a purchase number as an item to be set in a device device. The purchase number will be described below.

FIG. 17 is a diagram illustrating an example of the relationship between the types of data used in the embodiment and each data, and also includes an example of the types of data up to the fifth embodiment and the relationship between the data. FIG. 17 describes the data used and the data stored in the user X, the device device 1, the store server device 3, the information server device 4, and the bind database device 5. However, this is just an example, and various forms of devices for storing data can be easily considered.

The user information is information about the user X, for example, a name, an address, a telephone number, an e-mail address, an affiliated company name, and the like. The user information is provided by the user X, whose information source is the user X. When the user X gives the device device 1 to the user Y (case of the fifth embodiment), the user information may be information about the user Y. For user information, information server device 4 (owned by a credit card company, point card company, etc.), store server device 3 (owned by a store selling device devices, a mail-order company, etc.), and bind database device 5 (owned by a device device) were used. It may be provided to (owned by an application service provider, etc.). When the user information includes information corresponding to the user specific information, the store server device 3 does not necessarily have to send information other than the information to the bind database device 5.

The information server device 4 generates (issues) a user identification number such as a credit card number or a point card number (user ID) from the obtained user information.

The user identification number is a number or character issued by a credit card company, a point card company, or the like in order to identify the user X, and is provided to the user X, the store server device 3, the bind database device 5, or the like. To. Further, a user-specific number generated by an ID or password specified by the user may be used as the user identification number. In this case, for example, a user authentication server (not shown) that issues a user-specific number when the user inputs a user-specific ID or password from the store server device 3 may be used. A user-specific number (which may include numbers, characters, etc.) issued by the user authentication server may be used as the user identification number. In this way, the user does not need to provide the store server device 3 or the bind database device 5 with highly secure information such as a credit card number. Further, the user identification number is not necessarily a character string or a number string, and for example, when image authentication or voice authentication is used instead of the card reader of the UI unit 31 of the store server device 3, "image data" is used. It may be authentication data such as or "sound data".

The user X obtains the user identification number by, for example, a credit card equipped with a memory in which the user identification number is stored.

The store server device 3 obtains a user identification number from a user X, for example, a credit card, using a card reader. The store server device 3 can obtain the user information stored in the information server device 4 by using the obtained user identification number. It is also possible for the user X to provide the user information directly from the client PC 6 or the like to the store server device 3. Further, although FIG. 17 shows an example in which the store server device 3 holds the user information and the user identification information separately, both of them may be transmitted to the bind database device 5 as the user information.

The bind database device 5 is included in the database information (DB information) from the store server device 3 to acquire user information. The bind database device 5 stores the acquired user information in the user-specific data 501. Further, the store server device 3 may include the user identification number in the database information (DB information) and transmit the user identification number to the bind database device 5. The bind database device 5 stores the user identification number in the user-specific data 501.

The bind database device 5 extracts or generates user-specific information from user-specific data 501. The user-specific information is information that can identify the user X if there is such information. Specifically, the address, telephone number, e-mail address, company name, etc. are extracted as user-specific information from the user information of the user-specific data 501. For example, when the device to be obtained is used in an organization such as a home or a company at a specific address, the "address" and "company name" can be used as user-specific information. As for the "telephone number" and "email address", for example, when the user X is a user such as a smartphone, the "telephone number" and the "email address" can be used as the user identification information for identifying the user X. The user X may decide which item is used as the user-specific information.

The bind database device 5 generates a bind data user ID for identifying the user X in the database of the bind database device 5. The bind data user ID compares the user identification information and the user identification information extracted from the user information with the bind database of another already registered user, and generates the bind data user ID unique to the user X. The bind database device 5 stores the generated bind data user ID in the user-specific data 501. Further, the bind database device 5 transmits the bind data user ID as "selected user identification information" to the store server device 3. The store server device 3 transmits the bind data user ID as "selected user identification information" to the user X. Further, the store server device 3 sets the bind data user ID as "selected user identification information" in the device device 1. The "selected user-specific information" may be not only the bind data user ID but also one or more items selected from the user-specific information. For example, the combination of the telephone number and the e-mail address may be the "selected user-specific information", or only the e-mail address may be the "selected user-specific information". The combination of the telephone number, the e-mail address, and the bind data user ID may be the "selected user identification information". Further, the user identification information may be "selected user identification information".

The purchase information is user payment information such as product information of the device device 1 that the user X intends to obtain and a payment method of the acquisition price of the device device 1, user X is the information source, and the purchase information is determined by the user X. Provided.

The product information includes the manufacturer name, model number, serial number, etc. of the device device 1 (product) to be obtained. The product information itself is placed in the store server device 3, and if the user X clicks a picture of the device device 1 (product) displayed on the electronic commerce site of the store server device 3, the user X tries to obtain the product information. The device device 1 and the product information thereof may be linked in the store server device 3.

The user payment information is a payment method or amount such as a price for obtaining a device. In the case of bank payment, the type of card such as a bank account, a prepaid card, or an electronic wallet may be included in the user payment information. When the user X pays in cash at the store, the payment method is "cash payment". The user X transmits the product information and the user payment information to the store server device 3. The store server device 3 includes the received product information in the DB information and transmits it to the bind database device 5. The bind database device 5 stores the product information received in the product data 502.

The bind database device 5 generates device device-specific information which is information for identifying a product from the received product information. Specifically, the item "No" (device management number) of the product data item in the bind database of user X may be generated as device device-specific information. The generated device control number is stored in the product data 502. Further, the received product information elements such as "manufacturer name" and "serial number" may be used as device device-specific information, or a combination of a plurality of elements may be used as device device-specific information. The bind database device 5 transmits device device-specific information to the store server device 3. The device device-specific information received by the store server device 3 is set in the device device 1 by, for example, a clerk of a store or a clerk of a mail-order company.

When the store server device 3 obtains the user payment information from the user X, the store server device 3 generates a purchase number. The store server device 3 has information on user-specific data 501 related to user X, information on product data 502 that user X is trying to obtain this time, user payment information, and purchase history. The purchase history includes, for example, the place of purchase, the time of purchase, and the like. Therefore, by using these information, the store server device 3 can generate a purchase number that simultaneously considers the user-specific information of the user X and the device device-specific information that the user X is trying to obtain this time. That is, the store server device 3 sets the generated purchase number in the device device 1 and registers it in the bind database device 5. The purchase number may be a date, a place, an e-mail address, a number concatenated with a serial number of product information, a string of characters, or the like. The bind data user ID and telephone number may be used instead of the e-mail address, or a combination thereof may be used. When the device device 1 obtained by the user X transmits the purchase number to the application server device 2, the application server device 2 transmits the received purchase number to the bind database device 5, and the device device 1 and the device device 1 Know who is authorized to use it.

As described above, the user X can use the device device 1 without complicated procedures only by setting the purchase number in the device device 1 by the clerk of the store (mail order company).

According to at least one embodiment described above, it is possible to provide a database device, a generation system, a generation method, and a generation program for facilitating the handling of IoT devices.

In the above-described embodiment, for example, the application server device 2 and the bind database device 5 have been described as separate devices, but they may be built on the same hardware device. Similarly, for other devices, various configurations and combinations can be considered for the functions of the devices and the hardware on which the functions are executed, and the present invention is not limited to the examples of the embodiments shown above.

Further, in the present embodiment, the case where the user purchases the device device 1 as a method of obtaining the device device 1 is shown, but leasing and rental, free acquisition by campaign, discount acquisition, gifts from others, prizes, prizes, etc. It may be obtained by.

In any case, the store server device 3 binds when the store server device 3 obtains the user information of the user who is the prospective user, the user identification information, and the product information of the device device 1 that the user intends to obtain. It is possible to link (bind) the user information and the product information in the database device 5. If the acquisition method is not purchase but rental, for example, the store server device 3 may issue a number corresponding to the purchase number by using the rental date, rental location, etc. instead of the purchase date or purchase location. Good. In the case of a free gift, the store server device 3 may issue a number corresponding to the purchase number by using the free gift shipping date, the idea place, etc. instead of the purchase date and the purchase place.

Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof. Furthermore, in each of the constituent elements of the claim, even if the constituent elements are divided and expressed, a plurality of the constituent elements are expressed together, or a combination thereof is expressed, it is within the scope of the present invention. Further, a plurality of embodiments may be combined, and examples composed of these combinations are also within the scope of the invention.

Further, in order to clarify the explanation, the drawings may be schematically represented by the width, thickness, shape, etc. of each part as compared with the actual embodiment. In the block diagram, data and signals may be exchanged between blocks that are not connected, or even if they are connected but in a direction in which an arrow is not shown. Each function shown in the block diagram and the processing shown in the flowchart and the sequence chart may be realized by hardware (IC chip or the like) or software (program or the like) or a combination of hardware and software. Further, the apparatus of the present invention is applied even when the claim is expressed as a control logic, when it is expressed as a program including an instruction for executing a computer, and when it is expressed as a computer-readable recording medium in which the instruction is described. is there. Further, the names and terms used are not limited, and other expressions are included in the present invention as long as they have substantially the same contents and the same purpose.

1 ... device device, 2 ... application server device, 3 ... store server device, 4 ... information server device, 5 ... bind database device, 6 ... PC, 11 ... communication unit, 12 ... application processing unit, 13 ... storage unit, 21 ... Communication unit, 22 ... Application service unit, 23 ... Information inquiry processing unit, 31 ... UI unit, 32 ... Control unit, 33 ... Information inquiry processing unit, 34 ... Communication unit, 35 ... Bind database registration unit, 36 ... Service provision Unit, 51 ... Control unit, 52 ... Communication unit, 53 ... Information registration unit, 54 ... Storage unit, 55 ... Information provision unit, 100 ... Network.

Claims (13)

A database device connected to a network
A database device including a device device connected to the network and a database in which a licensee of the device device is associated with the device device. The database device according to claim 1, wherein the database includes user-specific information that identifies the licensee and device-specific information that identifies the device / device that can be used by the licensee. The database device according to claim 2, further comprising a specific information generation unit that generates device-specific information. The user-specific information includes an e-mail address, a telephone number, an address, a company name to which the user belongs, a My Number (registered trademark), a card ID unique to the licensee including a credit card ID, authentication data obtained as user identification information, and the like. The database device according to any one of claim 2 or 3, which includes at least one selected from the information group for identifying the licensee. The database device according to any one of claims 2 to 4, further comprising a specific information generation unit that generates the user specific information. The database device according to claim 2, further comprising an information providing unit that determines permission to use the device / device based on the device / device-specific information and the user-specific information. The first device device-specific information and the first user-specific information of the database,
Claim 1 or claim comprising an information providing unit that determines permission to use the device device based on the second device device-specific information and the second user identification information input from the device device connected to the network. Item 2. The database device according to any one of items 2. A store server provided with a data binding request transmitting means for outputting the product information and the user information, as well as a binding request for linking the product information about the device and the device obtained by the user with the user information which is the user's unique information. Equipment and
A request receiving processing means for receiving and processing the product information, the user information, and the binding request,
A generation system including a bind database device including a data binding means for linking the user information and the product information. The bind database device issues user identification information that identifies the user based on the user information, and identifies the device device in user-specific data that is unique data of the user in the database based on the product information. The generation system according to claim 8, further comprising a specific information generation means for issuing device-specific information. The store server device includes specific information receiving means for receiving the user specific information and the device device specific information.
The generation system according to claim 9, wherein the data binding request transmitting means outputs the user-specific information and the device device-specific information. The tenth aspect of the present invention, wherein the store server device includes specific information receiving means for receiving the user specific information, and the data binding request transmitting means outputs the user specific information as the user information. Generation system. The product information and the user information are output together with a bind request for linking the product information about the device and the device obtained by the user with the user information which is the user's unique information.
Receives and processes the product information, the user information, and the bind request.
A generation method characterized by linking the user information and the product information. A generation program for a computer to acquire product information of a device or device purchased by a user and user information which is unique information of the user, and bind the product information and the user information to a bind database device. ,
A generation program for causing the computer to execute a procedure of acquiring the product information and the user information and transmitting the product information and the user information together with a binding request for binding the product information and the user information.

Images