WO2021109798A1 - 数据库装置、生成系统和生成方法 - Google Patents

数据库装置、生成系统和生成方法 Download PDF

Info

Publication number
WO2021109798A1
WO2021109798A1 PCT/CN2020/127175 CN2020127175W WO2021109798A1 WO 2021109798 A1 WO2021109798 A1 WO 2021109798A1 CN 2020127175 W CN2020127175 W CN 2020127175W WO 2021109798 A1 WO2021109798 A1 WO 2021109798A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
information
database
binding
data
Prior art date
Application number
PCT/CN2020/127175
Other languages
English (en)
French (fr)
Inventor
井泽秀人
Original Assignee
海信视像科技股份有限公司
东芝视频解决方案株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 海信视像科技股份有限公司, 东芝视频解决方案株式会社 filed Critical 海信视像科技股份有限公司
Priority to CN202080008575.1A priority Critical patent/CN113273139B/zh
Publication of WO2021109798A1 publication Critical patent/WO2021109798A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the embodiments of the present application relate to a database device, a generation system, and a generation method.
  • IoT Internet of Things
  • IoT devices Internet of Things related devices
  • 5G 5th generation mobile communication system
  • 5G 5th generation mobile communication system
  • Patent Document 1 Japanese Patent Application Publication No. 2005-55940
  • Patent Document 2 Japanese Patent Application Publication No. 2005-44201
  • Patent Document 3 Japanese Patent Laid-Open No. 2002-189935
  • Patent Document 4 Japanese Patent Laid-Open No. 2002-74135
  • Patent Document 5 Japanese Patent Application Publication No. 2001-256317
  • ICT Information Communication Technology
  • the subject to be solved by this application is to provide a database device, generation system, and generation method to facilitate the operation of IoT devices.
  • the database device is connected to a network, and has a device connected to the network and a database corresponding to an authorized user of the device.
  • FIG. 1 is a diagram showing an example of the structure of the entire system according to the embodiment.
  • Fig. 2 is a block diagram showing an example of a functional configuration of a device according to an embodiment.
  • Fig. 3 is a block diagram showing an example of a functional configuration of an application server device according to an embodiment.
  • Fig. 4 is a block diagram showing an example of a functional configuration of a shop server device according to an embodiment.
  • Fig. 5 is a block diagram showing an example of a functional configuration of an information server device according to an embodiment.
  • Fig. 6 is a block diagram showing an example of a functional configuration of a binding database device according to an embodiment.
  • Fig. 7 is a diagram showing an example of system installation in the first embodiment.
  • FIG. 8 is a sequence diagram showing an example of the processing operation of the system before the user purchases and uses the device in the first embodiment.
  • FIG. 9A is a diagram showing an example of data generated and managed by the binding database device for one user in the first embodiment.
  • FIG. 9B is a diagram showing an example of data generated and managed by the binding database device for a plurality of users in the first embodiment.
  • Fig. 10 is a diagram showing an example of system installation in the second embodiment.
  • FIG. 11 is a sequence diagram showing an example of the processing operation of the system before the user purchases and uses the device in the second embodiment.
  • FIG. 12 is a diagram showing an example of system installation in the third embodiment.
  • FIG. 13 is a diagram showing an example of system installation in the fourth embodiment.
  • FIG. 14 is a diagram showing an example of system installation in the fifth embodiment.
  • 15 is a sequence diagram showing an example of the processing operation of the system when the user gives away the device to another user in the fifth embodiment.
  • FIG. 16 is a sequence diagram showing a second processing operation example of the system when the user gives away the device to another user in the fifth embodiment.
  • FIG. 17 is a diagram describing an example of the type of data used in the embodiment and the relationship between each data.
  • 1...equipment 2...application server device, 3...shop server device, 4...information server device, 5...binding database device, 6...PC, 11...communication Department, 12...Application Processing Department, 13...Storage Department, 21...Communication Department, 22...Application Service Department, 23...Information Query Processing Department, 31...UI Department, 32. .. control unit, 33... information query processing unit, 34... communication unit, 35... binding database registration unit, 36... service provider unit, 51... control unit, 52... Communication section, 53...information registration section, 54...storage section, 55...information provision section, 100...network.
  • FIG. 1 is a diagram showing an example of the structure of the entire system according to the embodiment.
  • the devices 1A and 1B are various IoT devices that are connected to the network 100 and perform data communication with devices on the network 100.
  • the device 1 may be, for example, a temperature detection sensor, a water leakage detection sensor, a door open/close sensor, or other sensors, or may be a detection device using these sensors.
  • the device 1 may be household appliances such as air conditioners, televisions, lighting, cameras, etc.
  • the device 1 may also be a mobile terminal such as a smartphone.
  • the application server device 2 is built on a computer having a CPU or a memory provided on the network 100, for example, and provides an application using the device 1.
  • the application server device 2 may be a cloud server.
  • the application server device 2 provides an application that uses the device 1, for example, sends an alarm notified by the device 1 to the application server device 2 to a pre-registered smartphone and forwards the notification.
  • the application server apparatus 2 may also provide an application in which a plurality of devices 1 are combined. Particularly in this embodiment, an application using the bound database device 5 described later is assumed.
  • the shop server device 3 is constructed on a computer having a CPU or a memory provided on the network 100, for example.
  • the shop server device 3 may be a cloud server.
  • the shop server device 3 is, for example, installed in a merchant that sells the device 1 to the user, and when the user obtains the device 1, it exchanges necessary data with devices in the system via the network 100.
  • the method by which the user obtains the device 1 although the purchase is shown in this embodiment, it may also be obtained through leasing, rental, etc., obtained for free through promotional activities, obtained at a discount, or obtained through gifts, prizes, and premiums from others. Wait for it, wait.
  • the shop server device 3 may also have the function of a POS (Point Of Sale, point of sale) terminal.
  • POS Point Of Sale, point of sale
  • the shop server device 3 may also have a card reader that obtains a user ID, e-mail address, telephone number, etc. from cards such as credit cards, point cards, and Mianna (personal number) (registered trademark in Japan). Information that identifies the user (the user of the device 1) (hereinafter referred to as user identification information).
  • the shop server device 3 may set a uniform resource locator (URL) for providing services to clients through the network 100.
  • URL uniform resource locator
  • the information server device 4 is built on a computer having a CPU or a memory provided on the network 100, for example.
  • the information server device 4 establishes a correspondence relationship between user personal information (hereinafter referred to as user information) such as name, address, phone number and user identification information for management, and provides information according to the request.
  • user information user personal information
  • user information such as name, address, phone number and user identification information for management
  • the binding database device 5 is constructed on a computer having a CPU or a memory provided on the network 100, for example.
  • the binding database device 5 stores data for associating (binding) the user information of the purchaser and the purchased product information, and generates a database (referred to specifically as a binding database).
  • the product information is, for example, product name, manufacturer name, model number, serial number, etc.
  • the binding database device 5 uses, for example, the manufacturer name, model number, serial number, etc., to generate device specific information to be registered (specifically referred to as device specific information), and adds it to the database.
  • the device specific information is information that identifies each device, and may be a character string containing numbers or symbols that can be specified based on the manufacturer's name, model, serial number, and the like.
  • the PC 6 is, for example, a personal computer, and is, for example, a client terminal that accesses the shop server device 3 through the network 100.
  • the PC6 may be a personal computer owned by the user at home; in the case of store sales, the PC6 may be a personal computer installed in the store.
  • the network 100 includes not only the Internet, but also all networks and communication paths for connecting the above-mentioned devices and equipment, and a network formed by combining them.
  • a dedicated line that ensures confidentiality or a virtual private network (VPN: Virtual Private Network) implemented on the Internet is used.
  • This communication path also includes In the network 100.
  • the network 100 may be not only wired but also wireless, and may include, for example, a communication method such as WiFi (registered trademark) or 5G.
  • a communication method using an Ethernet cable may be included.
  • a communication protocol predetermined by devices or devices and their data communication paths is used.
  • Fig. 2 is a block diagram showing a functional configuration of a device according to an embodiment.
  • the communication unit 11 is connected to the network 100 so that the device 1 communicates with devices or devices on the network 100.
  • the communication unit 11 has a wired communication interface or a wireless communication interface.
  • the communication unit 11 may not only have an interface for communicating with the network 100, but may also have an interface such as a Universal Serial Bus (USB: Universal Serial Bus) for connecting to a personal computer.
  • USB Universal Serial Bus
  • the application processing unit 12 performs processing for making the application provided by the application server device 2 available through a computer program or the like stored in the device 1.
  • the storage unit 13 stores settings and the like required for the device 1.
  • the setting of the storage unit 13 and the like are performed by a personal computer or the like through a USB or the like included in the control unit or the communication unit 11 (not shown).
  • Fig. 3 is a block diagram showing an example of a functional configuration of an application server device according to an embodiment.
  • the communication unit 21 is connected to the network 100 to communicate with devices or equipment on the network 100.
  • the communication part 21 includes a wired or wireless communication interface.
  • the application service unit 22 uses a computer program or the like stored in the application server device 2 to perform processing for providing applications. For example, when assuming a temperature detection application that uses the device 1, the application service unit 22 receives the temperature detection result sent by the device 1, and notifies the alarm to other devices or presets on the network 100 through the communication unit 11 equipment.
  • the information query processing unit 23 performs information query on the devices on the network 100 through the communication unit 21 according to the instruction from the application service unit 22, obtains the query information, and outputs the query information to the application service unit 22.
  • the information query processing unit 23 queries the bound database device 5 for information.
  • Fig. 4 is a diagram showing an example of a functional configuration of a shop server device according to an embodiment.
  • the UI unit 31 is a user interface, for example, a card reader that reads user identification information from a credit card, a point card, or a personal number card.
  • the UI unit 31 outputs the read user identification information to the control unit 32.
  • the UI unit 31 may read information from a smart phone, or may be a computer peripheral device such as a keyboard and a mouse.
  • the UI part 31 is a keyboard, the user or the seller can input user-related information including user identification information from the keyboard.
  • the control unit 32 controls each function of the shop server device 3 based on the user identification information input from the UI unit 31. In addition, data can be exchanged with all other functional blocks not connected to the control unit 32 in FIG. 4.
  • the information inquiry processing unit 33 inquires an external device through the communication unit 34 and obtains necessary information based on the instruction input from the control unit 32.
  • the information query processing unit 33 queries the information server device 4 based on the user identification information input from the control unit 32 to obtain user information.
  • the communication unit 34 is connected to the network 100 to communicate with devices or equipment on the network 100.
  • the communication unit 34 has a wired or wireless communication interface.
  • the binding database registration unit 35 sends required information such as user information or product information of purchased products to the binding database device 5.
  • the service providing unit 36 includes, for example, an e-commerce website for enabling users to purchase products through the Internet or processing functions at the time of purchase. In the case of not online sales but store sales, this function may not be used.
  • the service provider 36 obtains the user's purchase information.
  • Fig. 5 is a block diagram showing an example of a functional configuration of an information server device according to an embodiment.
  • the information registration section 41 includes a user interface such as a keyboard for inputting user information to the information server device 4, processes the information input from the user interface as necessary, and outputs it to the storage section 42.
  • a user interface such as a keyboard for inputting user information to the information server device 4
  • the information registration section 41 processes the information input from the user interface as necessary to create the database.
  • the information registration unit 41 issues user identification information, that is, user-specific identification information (ID).
  • ID user-specific identification information
  • the user identification information is, for example, a credit card number, a point card ID, etc., and is stored in an integrated circuit (IC: Integrated Circuit) on a credit card or a point card.
  • IC integrated Circuit
  • the storage unit 42 stores data such as user information input from the information registration unit 41.
  • the information providing section 43 receives a request from an external device to provide data stored in the storage section 42, obtains the requested data from the storage section 42, and transmits the obtained data to the requesting external device through the communication section 44 .
  • the communication unit 44 is connected to the network 100 to communicate with devices or equipment on the network 100.
  • the communication unit 44 has a wired or wireless communication interface.
  • the control section 45 controls each function of the information server device 4. In addition, data can be exchanged with all other functional blocks that are not connected to the control section 45 in FIG. 5.
  • Fig. 6 is a block diagram showing an example of a functional configuration of a binding database device according to an embodiment.
  • the control section 51 controls each function of the binding 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 binding database device 5 according to the received request. In addition, data can be exchanged with all other functional blocks that are not connected to the control section 51 in FIG. 6.
  • the communication unit 52 is connected to the network 100 to communicate with devices or equipment on the network 100.
  • the communication part 52 includes a wired communication interface or a wireless communication interface.
  • the information registration unit 53 creates an information registration, that is, a binding database, according to a registration request of information received by the control unit 51 from an external device on the network 100.
  • the information registration unit 53 stores the user information, product information, etc. sent by the shop server device 3 in the storage unit 54 under the control of the control unit 51 In, create a bound database.
  • the determination information generating part 531 creates a bound data user ID, which is user identification information used to identify the user on the bound database.
  • the bound data user ID can be a number or a string containing characters, numbers, etc.
  • the identification information generating section 531 creates a device management number assigned to each user for the device 1 registered in the binding database.
  • the device management number can be a number or a string containing characters, numbers, etc.
  • the device management number can be used as device specific information that is unique to the device.
  • the storage unit 54 stores data input from the information registration unit 53.
  • control section 51 When the control section 51 receives an information provision request from an external device on the network 100, the information provision section 55 acquires data from the storage section 54 according to the request, and transmits the data to the requested external device through the communication section 52.
  • Fig. 7 is a diagram showing an example of system installation in the first embodiment.
  • the user is the purchaser of device 1 and owns PC6.
  • the mail orderer is a seller of the equipment 1 and owns the shop server device 3 and the information server device 4.
  • the information server device 4 manages user identification information (user ID) required when the user purchases goods from a mail orderer.
  • the mail orderer keeps the equipment 1 i.e. the product purchased by the user.
  • the service provider is the application provider of the device 1 and owns the application server device 2 and the binding database 5.
  • FIG. 8 is a sequence diagram showing an example of the processing operation of the system before the user purchases and uses the device in the embodiment.
  • the respective processes of the PC 6, the shop server device 3, the information server device 4, the binding database device 5, the device 1, and the application server device 2 are shown from top to bottom in chronological order from the left.
  • the PC 6 and the shop server device 3 respectively include a user and a mail order shop clerk, and the operation behaviors of the user and the shop clerk are shown by dotted lines in the sequence diagram.
  • the clerk of the mail orderer sends the device 1 to the user. At this time, the clerk can set up the device 1 as needed.
  • the processing (non-human processing) performed by the PC 6, the shop server device 3, and other devices is shown by solid lines.
  • the user registers user information with the mail orderer in advance, obtains user identification information (customer ID), and purchases equipment 1 (stage P1). The details will be described below.
  • the user accesses the e-commerce website provided by the shop server device 3 through the PC 6, and registers user information, etc., to obtain an account (step S11). Specifically, the user transmits the user information from the PC 6 to the shop server device 3 together with the user information registration request.
  • control unit 32 of the shop server device 3 When the control unit 32 of the shop server device 3 receives the user information registration request, it causes the service providing unit 36 to perform 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.
  • the control unit 45 when the control unit 45 receives a user information registration request, it outputs user information and the like to the information registration unit 41 to execute user information registration.
  • the information registration unit 41 adds the received user information to the database of the storage unit 42, releases user identification information (customer ID), and transmits the user identification information from the communication unit 44 to the shop server device 3 (step S13).
  • the shop server device 3 transmits the received user identification information to the PC 6 or the like, and notifies it to the user (step S14).
  • the user can purchase products from a mail order merchant by using the user identification information received from the PC6.
  • the user purchases the device 1 on the e-commerce website of the shop server device 3 through the PC 6 (steps S15 and S16). Specifically, the user uses the PC 6 to access the e-commerce website provided by the service providing unit 36 of the shop server device 3 through the network 100. On the e-commerce website, for example, when the user clicks the name of the device 1 to be purchased, etc. (step S15) and inputs user payment information (such as credit card payment, bank payment information) or user identification information, etc. (step S16), Purchase information such as product information of the device 1 and user payment information and user identification information are sent to the service providing section 36. When the service providing unit 36 receives these pieces of information, for example, “purchase complete” or the like is displayed on a display unit (not shown) of the PC 6 to complete the user's purchase process.
  • user payment information such as credit card payment, bank payment information
  • user identification information such as credit card payment, bank payment information
  • step S16 Purchase information such as product information of the device 1 and user payment information and user identification information
  • the shop server device 3 executes database generation processing (stage P2).
  • the shop server device 3 transmits the user information query together with the user identification information acquired in the stage P1 from the information query processing unit 33 to the information server 4 via the communication unit 34 (step S21).
  • the control unit 45 when the control unit 45 receives the user information query, it causes the information providing unit 43 to transmit the user information (step S22).
  • the control section 45 instructs the information providing section 43 to send user information
  • the information providing unit 43 acquires the user information from the storage section 42 based on the received user identification information.
  • the information providing unit 43 transmits the acquired user information to the shop server device 3 through the communication unit 44.
  • the shop server device 3 transmits the received user information and product information as database (DB) information to the binding database device 5 (step S23). Specifically, in the shop server device 3, the binding database registration unit 35 combines the user information received by the information query processing unit 33 and the product information received by the service providing unit 36, and processes as needed to create database information. The binding database registration unit 35 sends a database registration request (data binding request) to the binding database device 5 together with the created database information.
  • DB database
  • the bound database device 5 When the bound database device 5 receives the database registration request, it registers the received database information in the database (step S24). More specifically, in the binding database device 5, when the control unit 51 receives a database registration request, the control unit 51 outputs the received database information to the information registration unit 53. The information registration unit 53 registers database information to the storage unit 54. Through the above process, a database (binding database) that associates user information and product information is generated on the binding database device 5.
  • FIG. 9A is a diagram showing an example of data generated and managed by the binding database device for one user in the embodiment.
  • the binding data 500 includes user-specific data 501 and product data 502, and basically creates one for one user. For example, when a certain organization uses all devices 1 in common, one binding data 500 is created as one organization. In this embodiment, an example of creating one binding data 500 for one user is shown.
  • the user-specific data 501 stores user identification information (for example, a bound data user ID), which is provided to the user who manages the data in the bound database device 5.
  • the user-specific data 501 may be user identification information, etc., in addition to the data-bound user ID.
  • the user inherent data 501 may only be, for example, a telephone number, or an email address, etc., and a data that can identify the user's individual without much change is desired.
  • the user-specific data 501 may include personal information of the user such as name, address, date of birth, and so on.
  • the product data 502 includes data such as “No”, “product name”, “manufacturer”, “model number”, and “serial number” shown as column items for each device 1 as a product. Each time a user purchases device 1, a row is added and the information of each column item is registered. “No” is the equipment management number of the equipment 1 managed by the binding database device 5. It is preferable to assign a device management number so that the device that each user can use is a specific number. You can select one of the following "product name”, “manufacturer”, “model”, “serial number”, etc. as the device management number. The device management number can be generated based on the selected one.
  • “Product name” is the name of the device 1.
  • “Manufacturer” is the name of the manufacturing company of the device 1.
  • the "model number” is a character string including characters, numbers, etc. assigned to the model type of the device 1 by the manufacturing company.
  • the “serial number” may be a character string including characters, numbers, etc. uniquely assigned to the device 1 by the manufacturing company.
  • column items can be added. For example, when assigning an IP address to the device 1, the IP address can be added to the database. In addition, the IP address of a certain application server device 2 that provides an application that can use the device 1 can be added.
  • the "product name”, “manufacturer”, “model”, and “serial number” are Di1, Di2, Di3, and Di4, respectively.
  • N in the item "No" corresponds to the number of registered devices 1 that the user can use.
  • FIG. 9B is a diagram showing an example of data generated and managed by the binding database device for a plurality of users in the embodiment.
  • binding data 500A, 500B, 500C of each of a plurality of different users are stored.
  • the determination information generating section 531 of the binding database device 5 issues the binding data user ID
  • the information registration section 53 sends a completion notification (step S25).
  • the published binding data user ID can be sent together with the completion notification.
  • the shop server device 3 receives the bound data user ID, it displays it on a display unit (not shown) of the shop server device 3.
  • the binding data user ID is sent together with the completion notification .
  • the device management number can also be sent at the same time.
  • the mail orderer sends the product to the product (stage P3).
  • the device can be parameterized as needed.
  • the mail orderer can set required parameters and other information for the newly purchased device 1 (step S31).
  • the “serial number”, “model number”, “device management number”, and the like of the device 1 are set in the storage unit 13 as device specific information identifying the device 1.
  • the binding data user ID is set in the storage section 13 as user identification information for identifying the user. Externally, as user identification information, it can also be a phone number, e-mail address, etc.
  • user identification information can also be used as user identification information.
  • the setting information includes information capable of communicating with the application server device 2, that is, the IP address of the application server device 2, the URL of the application website provided by the application server device 2, and the like, and is stored in the storage unit 13.
  • the setting information may include the IP address or URL of the binding database device 5.
  • the mail orderer sends the device 1 to the user who purchased it (step S32).
  • the mail orderer may send the device 1 whose parameters have been set in step S31 to the user who purchased the device.
  • the mail order merchant can also send the device 1 without parameter settings to the user who purchased the device without performing step S31.
  • the user identification information of the user who purchased the device (hereinafter referred to as the purchasing user) and the user identification information of the sharing user (hereinafter referred to as the sharing user) are transmitted to the shop server apparatus 3 (step S16).
  • the shop server device 3 sends the received user identification information of the purchase user and the shared user to the information server device 4, inquires about the user information, and obtains the respective user information (steps S21, S22).
  • the shop server device 3 transmits the respective user information and product information of the purchasing user and the sharing user to the binding database device 5 (step S23).
  • the binding database device 5 creates a binding database for each of the purchasing user and the sharing user (step S24).
  • step S23 the binding data user ID and the user ID are combined in step S23.
  • the product information of the new device 1 is sent to the binding database means 5, so that the new device 1 can be registered in the binding data 500 of the user.
  • stage P4 the user who has purchased the device 1 receives the device 1 as a product, and sets up and uses it.
  • step S41 When the user receives the device 1 sent by the mail orderer, he installs it in a desired location (step S41).
  • a wired connection to the network 100 for example, an Ethernet cable is connected to the device 1, and it is set to be able to access the network 100.
  • the device 1 is started by turning on the power of the device 1 (step S43).
  • the application processing unit 12 refers to the IP address of the application server device 2 stored in the storage unit 13, and accesses the application server device 2 via the network 100 (step S44).
  • the user identification information (bind data user ID, e-mail address, telephone number, etc.) and device identification information stored in the storage unit 13 are sent to the application server device 2.
  • the user identification information and the device specific information can also be used as an account for authorizing access when the device 1 accesses the application server device 2.
  • binding information confirmation a product that is bound to the purchasing user or the user authorized to use (hereinafter referred to as binding information confirmation) (step S45). More specifically, when the application service unit 22 requests the information query processing unit 23 to confirm the binding information, the information query processing unit 23 sends the request to confirm the binding information to the binding database device 5 together with the user identification information and the device specific information. .
  • the binding database device 5 when receiving the binding information confirmation request, confirms whether the received user-specific information and the device-specific information are associated, that is, whether the device 1 with the device-specific information is owned by the user with the user-specific information.
  • the owned item or whether it is a usable item, and the confirmation result of the binding information is sent to the application server 22 (step S46).
  • the control unit 51 when receiving a request for binding information, the control unit 51 simultaneously outputs the received user identification information and device specific information to the information providing unit 55.
  • the information providing unit 55 confirms whether there is data matching the received user identification information and device specific information in the binding data 500 stored in the storage unit 54.
  • the information providing unit 55 finds the device 1 matching the received user identification information and device specific information in the binding data 500, it sends a “YES” response to the application server device 2. When there is no device 1 matching the received user-specific information and device specific information, a “NO” response is sent to the application server device 2.
  • step S47 When the application server device 2 receives "YES”, it starts the application using the device 1 purchased in step S13 (step S47). When the application server apparatus 2 receives "NO”, the access device 1 is prohibited from using the application. At this time, the application server apparatus 2 may send a response such as "access prohibited" to the accessed device 1.
  • the user can use the application using the device 1.
  • a user purchases the device 1 on an e-commerce website, and only needs to install the device 1 and press the power switch to use the device 1.
  • the binding database device 5 by creating a binding database that associates the device 1 with the purchasing user, the effect of eliminating the cumbersomeness of the initial setting when purchasing the device 1 is achieved.
  • the convenience of not requiring initial settings when purchasing the device 1 is brought about.
  • the binding database device 5 shown in this embodiment can also be used for an application that enables multiple devices 1 owned by a user to cooperate with each other.
  • the user has not purchased the device 1 in the past, and the user information has not been registered in the binding database device 5.
  • the user has purchased in the past and the user information has been registered in the binding database device 5.
  • the process can be further simplified.
  • step S31 in the parameter setting of step S31, as the user determination information, for example, any one of the binding data user ID, mail address, phone number, etc. can be set, or any combination of them can be set. .
  • the security strength of the device 1 using the service of the application server apparatus 2 (step S47) can be changed by, for example, the amount of user determination information set in the device 1.
  • steps S45 and S46 in the response of the binding database device 5 to the information query processing from the application server device 2, it is more effective to increase the number of user-defined information used by the information providing unit 55 as the judgment condition. Improve the strength of security.
  • user identification information may be given priority, and the judgment conditions of the information providing unit 55 may be weighted.
  • the device 1 that uses the bound data user ID as the user identification information can read that the email address is not used. Allowed high-level information (for example, information about balance inquiry), or important control that is not allowed in the use of the mail address (for example, control related to the payment of money) can be performed.
  • an operation example of the system is shown when a user (purchaser) who owns a customer ID of a mail orderer purchases a product (device 1) at the mail orderer and the mail orderer orders the product from a service provider.
  • an operation example of the system when the user purchased the device 1 in the past and the user information has been registered in the binding database device 5 is also shown.
  • Fig. 10 is a diagram showing an example of system installation in the second embodiment.
  • the user is the purchaser of device 1 and owns PC6.
  • the mail orderer is a seller of the equipment 1 and owns the shop server device 3 and the information server device 4.
  • the service provider is the application provider of the device 1 and owns the application server device 2 and the binding database 5. In this embodiment, unlike the first embodiment, the service provider keeps the equipment 1, that is, the product purchased by the user.
  • FIG. 11 is a sequence diagram showing an example of the processing operation of the system before the user purchases and uses the device in the second embodiment.
  • the same parts as the flow shown in FIG. 8 are given the same phases and steps. The description is omitted or simplified for the same parts as in FIG. 8.
  • the pre-registration and purchase process is the same as the stage P1 in FIG. 8, so the description is omitted.
  • a database of bound data is generated (stage P22).
  • the shop server device 3 obtains the customer ID as the user identification information of the mail orderer (step S16 in FIG. 8)
  • the information server device 4 queries the user information of the customer ID (step S221).
  • the information server device 4 acquires the received user information of the customer ID from the storage unit 42 of the information server device 4, and transmits it to the shop server device 3 (step S222).
  • the shop server device 3 transmits database information including the received user information and the purchase information acquired in the stage P1 to the binding database device 5 (step S223).
  • the binding 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 is registered, the received purchase information is registered in the product data 502 (S224). In addition, if the received user information is not registered in the user specific data 501 of the storage unit 54, the binding database device 5 registers the user information in the user specific data 501, and registers the received purchase information in the product data 502 , And publish the bound data user ID to the user. When the binding database device 5 completes the registration of the database information, for example, the binding data user ID and the like are displayed on a display unit (not shown) of the binding database device 5, and it is notified to the service provider (step S225).
  • the mail orderer sends the product to the product (stage P23).
  • This stage only starts from stage P3 shown in the first embodiment, and the implementation subject changes from a mail order merchant to a service provider. Since the implementation content remains unchanged, the description is omitted.
  • stage P4 the user who purchased the device 1 receives the device 1 as a product, installs and uses it. This stage is the same as stage P4 shown in the first embodiment, so the description is omitted.
  • the user purchases the product (device 1) at the mail orderer, and the mail orderer orders the product from the service provider. Even in this case, the user (purchaser) can also order the product through simple steps Use the device 1 by purchasing the product (device 1) on the merchant’s e-commerce website.
  • FIG. 12 is a diagram showing an example of system installation in the third embodiment.
  • the user is the purchaser of the device 1.
  • the shop is a seller of the equipment 1 and a sales place, and owns a PC 6, a shop server device 3, and an information server device 4.
  • the information server device 4 manages user information of the owner of the point card.
  • the service provider is the application provider of the device 1 and owns the application server device 2 and the binding database 5.
  • the difference between this embodiment and the first embodiment is only that the seller of the device 1 has changed from a mail orderer to a store sales.
  • the operation processing flow of the system is the same as the sequence diagram of FIG. 8, so the use of FIG. 8 is only for the first embodiment. Describe different places.
  • the user goes to the store, and registers user information in order to obtain the point card issued by the store (step S11).
  • the user information is sent to the shop server device 3 together with the registration request of the point card.
  • control unit 32 of the shop server device 3 When the control unit 32 of the shop server device 3 receives the registration request for the point card, it causes the service providing unit 36 to perform account registration (step S12).
  • the service providing unit 36 transmits user information and the like to the information server device 4 together with the registration request of the point card.
  • the control unit 45 when the control unit 45 receives the registration request of the point card, it outputs user information and the like to the information registration unit 41 to execute the registration of the point card.
  • the information registration unit 41 adds the received user information to the database of the storage unit 42, and issues user identification information (user ID of the point card), and sends the user identification information from the communication unit 44 to the shop server device 3 (step S13) .
  • registered user information is managed in association with user identification information.
  • the shop server device 3 notifies the user by sending the received user identification information to the PC 6 or the like (step S14).
  • a card equipped with a memory into which user identification information data is input is issued to the user as a point card.
  • the shop assistant When the purchase information is delivered to the shop assistant, the shop assistant inputs the purchase information from the PC 6, and the purchase information is transmitted to the shop server device 3 (step S15).
  • the shop server device 3 When the user places the point card in 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 sent to the shop server device 3 (step S16).
  • the subsequent stages and steps are the same as those shown in FIG. 8, so the description is omitted.
  • the user (purchaser) uses the loyalty card to purchase the product (device 1) in the store. Even in this case, the user (purchaser) can purchase the product (device 1) through simple steps to use device 1 .
  • FIG. 13 is a diagram showing an example of system installation in the fourth embodiment.
  • the user is the purchaser of the device 1.
  • the shop is a seller of the equipment 1 and a sales place, and has a PC 6 and a shop 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 the application provider of the device 1 and owns the application server device 2 and the binding database 5.
  • the operation processing flow of the system is the same as the sequence diagram of FIG. 8, so only the differences from the first embodiment and the third embodiment will be described using FIG. 8.
  • step S15 When the user goes to the store to deliver the purchase information to the store clerk, the store clerk inputs the purchase information from the PC 6, and the purchase information is sent to the store server device 3 (step S15).
  • step S16 When the user places the credit card in the card reader connected to the PC 6, the user identification information is input to the PC 6, and the user identification information is sent to the shop server device 3 (step S16).
  • steps S11 to S14 are omitted. The subsequent stages and steps are the same as those shown in FIG. 8, so the description is omitted.
  • the user (purchaser) uses a credit card to purchase the product (device 1) in the store. Even in this case, the user (purchaser) can purchase the product (device 1) through simple steps to use the device 1 .
  • an operation example of the system when the user A (purchaser) gives away the device 1 to the user B (recipient) is shown.
  • the user A (purchaser) purchases the device 1 at a mail orderer.
  • the mail orderer registers the user B's information in the binding database device, obtains the user B's binding database ID, sets the parameters required by the device 1, and sends the device 1 to the user B.
  • FIG. 14 is a diagram showing an example of system installation in the fifth embodiment.
  • the user is the purchaser of device 1 and owns PC6.
  • the mail orderer is a seller of the equipment 1 and owns the shop server device 3 and the information server device 4. In addition, the mail orderer keeps the device 1 which is the product purchased by the user.
  • the service provider is the application provider of the device 1 and owns the application server device 2 and the binding database 5.
  • the system setup of FIG. 14 is the same as the example of FIG. 7 shown in the first embodiment, but in this figure, it is assumed that the users are two persons A and B.
  • 15 is a sequence diagram showing an example of the processing operation of the system when the user gives away the device to another user in the fifth embodiment.
  • the user information of the user B is registered in advance, and the user A purchases the device 1 (stage P51).
  • user B pre-registers user B's user information, and releases user B's user identification information (user B identification information) (steps S151 to S154).
  • user B identification information user B identification information
  • the user A obtains the user identification information of the user B from the user B, and purchases the device 1 from the PC 6 (steps S155, S156). Specifically, the user A uses the PC 6 through the network 100 to access an e-commerce website provided by the service providing unit 36 of the shop server device 3. In this e-commerce website, for example, when user A clicks the name of the purchased device 1, selects the purchased device 1, enters user B’s user identification information or payment information, etc., and clicks the "OK" button on the website, etc., the device Purchase information such as product information or payment information of 1 and user identification information of user B are sent to the service providing unit 36. When the service provider 36 receives these pieces of information, for example, it causes the user A to complete the purchase process by displaying "Purchase Complete" or the like on the PC6.
  • the shop server device 3 executes database generation processing (stage P52).
  • the shop server device 3 transmits the user information query of the user B together with the user identification information of the user B obtained in stage P51 from the information query processing unit 33 to the information server device 4 via the communication unit 34 (step S251).
  • the control unit 45 when the control unit 45 receives the user information query of the user B, it causes the information providing unit 43 to transmit the user information of the user B (step S252).
  • the control unit 45 instructs the information providing unit 43 to send 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.
  • the information providing unit 43 transmits the acquired user information of the user B to the shop server device 3 through the communication unit 44.
  • the shop server device 3 transmits the received user information and product information of the user B as database information to the binding database device 5 (step S253).
  • the binding database registration unit 35 combines the user information of the user B received by the information query processing unit 33 and the product information received by the service provider 36, and processes as needed to create User B's database information.
  • the bound database registration unit 35 sends the database registration request to the bound database device 5 together with the created database information.
  • the binding database device 5 When the binding database device 5 receives the database registration request (data binding request), it registers the received database information in the database (step S254). More specifically, in the binding database device 5, when the control unit 51 receives a database registration request, the control unit 51 outputs the received database information to the information registration unit 53. The information registration unit 53 registers database information to the storage unit 54. Through the above process, it is possible to generate a database that associates the user information of user B with the device information purchased by user A (bound together).
  • the information registration section 53 of the binding database device 5 sends a completion notification together with the binding data user ID of the user B created by the determination information generating section 531 (step S255).
  • the shop server device 3 receives the binding data user ID and displays it on a display unit (not shown) of the shop server device 3.
  • the mail orderer implements parameter setting and product delivery to the product (phase P3).
  • the operation example in this stage is the same as that in FIG. 8, so the description is omitted.
  • the mail orderer sends the device 1 to the user B instead of sending the device 1 to the user A, which is the purchaser.
  • the user B receives the device 1, and installs and uses it (phase P54).
  • step S451 When the device 1 sent by the mail orderer is received, the user B installs it in a desired location (step S451).
  • the Ethernet cable used to connect to the network 100 is connected to the device 1 as needed, and the device 1 is connected to the network 100.
  • the user B presses the power switch or the like of the device 1 to start the device 1 (step S452).
  • the device 1 is started by turning on the power of the device 1 (step S453).
  • step S454 When the device 1 starts up, it accesses the application server apparatus 2 via the network 100 (step S454). After that, steps S454 to S457 are the same as steps S44 to S47 in FIG. 8, so detailed descriptions are omitted.
  • the application service unit 22 when the application service unit 22 detects an access from the application processing unit 12, it requests the binding database device 5 to confirm binding information, such as whether the access device 1 is connected to the user (in this embodiment, User B) Association etc. (step S455).
  • the binding database device 5 confirms the binding information, and sends the confirmation result of the binding information to the application service unit 22 (step S456).
  • the application server apparatus 2 When the application server apparatus 2 receives "YES” as the confirmation result of the binding information, it starts the application using the device 1 purchased in step S153 (step S457). When the application server apparatus 2 receives "NO" as the confirmation result of the binding information, the access device 1 is prohibited from using the application.
  • user A purchaser
  • user B who does not have a bound database ID.
  • user B can use device 1.
  • it shows a case where user B has registered user specific information in the binding database device and has a binding database ID.
  • 16 is a sequence diagram showing an example of the processing operation of the system when the user gives away the device to another user in the fifth embodiment.
  • User A obtains user B's bound data user ID from user B in advance.
  • the user A accesses the e-commerce website provided by the service provider 36 of the shop server device 3 from the PC 6, and when the purchase information related to the purchased device 1 and the binding data user ID of the user B are input, the purchase information is bound to the user B
  • the predetermined data user ID is transmitted to the shop server device 3 (steps S163, S164).
  • the shop server device 3 executes database generation processing (stage P62).
  • the shop server device 3 sends the binding data user ID of the user B acquired in stage P61 and the product information of the purchased device 1 as database information to the binding database device 5 together with the database registration request (step S263).
  • the binding database device 5 registers the received database information in the database (step S264). More specifically, the binding database device 5 searches the binding data 500 registered in the storage unit 54 for the binding data 500 registered with the received binding data ID, and adds the received product information to the searched binding data 500. The binding data 500. Through the above process, a database that associates (binds) the user information of user B with the device information purchased by user A can be generated.
  • the product parameter setting and product delivery stage are the same as stage P3 in FIG. 8, and the installation and use stage of the product is the same as stage P54 in FIG. 8, so the description is omitted.
  • user B has a bound database ID, that is, when user specific information has been registered in the bound database device, user A (purchaser) presents device 1 to user B (recipient), and user B can Use device 1.
  • FIG. 17 is a diagram describing an example of the type of data used in the embodiment and the relationship between each data, and also includes an example of the type of data and the relationship between each data before the fifth embodiment.
  • FIG. 17 describes the data used and stored in the user X, the device 1, the shop server device 3, the information server device 4, and the binding database device 5. However, what is shown here is an example, and various forms of data storage devices can be easily thought of.
  • User information is information related to user X, such as name, address, phone number, email address, and company name.
  • User X is the source of information, and user information is provided by user X.
  • the user information may be information related to the user Y.
  • User information can also be provided to the information server device 4 (owned by a credit card company or point card company, etc.), shop server device 3 (owned by equipment sales shops, mail orders, etc.), and bound database device 5 (owned by using equipment Owned by application service providers, etc.).
  • the shop server device 3 does not need to send information other than the information to the binding 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) based on the obtained user information.
  • the user identification number is a number or character issued by a credit card company, a point card company, etc. for identifying the user X, and is provided to the user X, the shop server device 3, the binding database device 5, and the like.
  • a user-specific number generated by an ID or password specified by the user can be used as the user identification number.
  • an authentication server (not shown) that issues a user-specific number can be used.
  • the user-specific number (which may include numbers, characters, etc.) issued by the user authentication server can be used as the user identification number.
  • the user does not need to provide high-security information such as a credit card number to the shop server device 3 or the binding database device 5.
  • the user identification number does not have to be a character string or a number string.
  • image authentication or voice authentication is used instead of the card reader of the UI unit 31 of the shop server device 3, it may be "image data” or “sound data "And other authentication data.
  • the user X obtains the user identification number through, for example, a credit card equipped with a memory storing the user identification number.
  • the shop server device 3 uses a card reader to obtain a user identification number from, for example, a credit card of the user X.
  • the shop server device 3 can use the obtained user identification number to obtain the user information stored in the information server device 4.
  • the user X may directly provide user information from the client PC 6 or the like to the shop server device 3.
  • FIG. 17 an example is shown in which the shop server device 3 separately stores user information and user identification information, but the two may be combined and sent to the binding database device 5 as user information.
  • the binding database device 5 obtains the user information included in the database information (DB information) from the shop server device 3.
  • the binding database device 5 stores the obtained user information in the user specific data 501.
  • the shop server device 3 may also include the user identification number in the database information (DB information), and send the user identification number to the bound database device 5.
  • the binding database device 5 stores the user identification number in the user specific data 501.
  • the binding database device 5 extracts or generates user identification information from the user specific data 501.
  • the user identification information is information that can identify the user X as long as the information exists. Specifically, the address, telephone number, email address, company name, etc. are extracted from the user information of the user specific data 501 as user identification information. For example, if the acquired device is used in an organization such as a home or company at a specific address, the "address" and "company name” can be used as user identification information. For example, in a case where the user X is a user of a smartphone or the like, the “phone number” and the “email address” are used as user identification information for identifying the user X. User X can decide which item is user-defined information.
  • the binding database device 5 generates a binding data user ID for identifying the user X in the database of the binding database device 5.
  • the binding data user ID compares the user identification information or user identification information extracted from the user information with the binding database of other registered users to generate a user X-specific binding data user ID.
  • the binding database device 5 stores the generated binding data user ID in the user specific data 501.
  • the binding database device 5 transmits the binding data user ID to the shop server device 3 as “selected user identification information”.
  • the shop server device 3 sends the bound data user ID to the user X as the “selected user identification information”.
  • the shop server device 3 sets the binding data user ID as the "selected user determination information" in the device 1.
  • the "selected user identification information" may not only be the bound data user ID, but also one or more items selected from the user identification information.
  • a combination of a telephone number and an e-mail address may be used as the "selected user identification information", or only the e-mail address may be used as the "selected user identification information”. It is also possible to use a combination of phone number, e-mail address, and bound data user ID as "selected user identification information”.
  • user identification information may also be used as "selected user identification information”.
  • the purchase information is user payment information such as the product information of the device 1 that the user X wants to obtain, and the payment method for the user X to obtain the payment required by the device 1.
  • the user X is the information source and is provided by the user X.
  • the product information includes the manufacturer's name, model, serial number, etc. of the device 1 (product) to be obtained.
  • the product information itself is stored in the shop server device 3. If the user X clicks on a photo of the device 1 (product) displayed on the e-commerce website of the shop server device 3, the user X can also be stored in the shop server device 3.
  • the desired device 1 is associated with its product information.
  • the user payment information is a payment method, amount, etc., used to obtain payment for equipment.
  • the bank account card type (for example, prepaid card, electronic wallet, etc.), and others may also be included in the user payment information.
  • the payment method is "cash payment”.
  • the user X sends product information and user payment information to the shop server device 3.
  • the shop server device 3 includes the received product information in the DB information, and sends it to the binding database device 5.
  • the binding database device 5 stores the received product information in the product data 502.
  • the binding database device 5 generates equipment specific information, which is information used to determine a product from the received product information. Specifically, the item “No” (device management number) of the product data of the binding database of the user X may be generated as the device identification information. The generated device management number is stored in the product data 502. In addition, elements of the received product information, such as "manufacturer name", "serial number", etc., may be used as device specific information, or a combination of multiple elements may be used as device specific information.
  • the binding database device 5 transmits the equipment identification information to the shop server device 3.
  • the device identification information received by the shop server device 3 is set in the device 1 by, for example, a clerk of a sales shop or a clerk of a mail order.
  • the shop server device 3 generates a purchase number when obtaining user payment information from the user X.
  • the shop server device 3 also has user payment information and purchase history.
  • the purchase history includes, for example, the place of purchase, the time of purchase, and the like. Therefore, the shop server device 3 can generate a purchase number in consideration of both the user identification information of the user X and the equipment identification information that the user X wants to obtain this time by using these pieces of information. That is, the shop server device 3 sets the generated purchase number in the device 1 and registers it in the binding database device 5.
  • the purchase number can be a date, a location, an email address, a string of numbers or a character string connecting the serial numbers of the product information. Instead of the email address, you can also use the binding data user ID or phone number, or a combination of them.
  • the device 1 obtained by the user X sends the purchase number to the application server device 2
  • the application server device 2 sends the received purchase number to the binding database device 5
  • the device 1 and the authorized user of the device 1 can be known.
  • the clerk of the store sets the purchase number in the device 1
  • the user X can use the device 1, without requiring complicated steps.
  • a database device, generation system, and generation method are provided to facilitate the operation of IoT devices.
  • the application server device 2 or the bound database device 5 is described as a separate device, but they may also be built on the same hardware device.
  • various structures and combinations of the function of the device and the hardware that executes the function can also be considered, but it is not limited to the example of the embodiment shown above.
  • the purchase is shown as a method for the user to obtain the device 1, but it can also be obtained through leases and rentals, free for events, discounts, gifts from others, prizes, premiums, etc. ,and many more.
  • the shop server device 3 can bind the user information in the database device 5 by obtaining the user information of the authorized user, the user identification information, and the product information of the device 1 that the user wants to obtain. Combine (bind) with product information.
  • the shop server device 3 may use the lease date, lease place, etc. instead of the purchase date and place of purchase to issue a number equivalent to the purchase number.
  • the shop server device 3 uses the gift delivery date, delivery location, etc. instead of the purchase date and purchase location to issue a number corresponding to the purchase number.
  • the drawings sometimes schematically show the width, thickness, shape, etc. of each part compared with the actual form.
  • the block diagram sometimes data or signals are exchanged between unconnected blocks, or in the direction of arrows that are connected but not shown.
  • the functions shown in the block diagrams, the flowcharts, and the processing shown in the timing diagrams can also be realized by hardware (IC chips, etc.), or software (programs, etc.), or a combination of hardware and software.
  • control logic when expressed as a program containing instructions to be executed by a computer, and when expressed as a computer-readable recording medium in which the above-mentioned instructions are recorded, they can also be applied.
  • the device of this application there are no limitations on the names or terms used, and even other expressions are included in the present invention if they have substantially the same content and the same purpose.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Health & Medical Sciences (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Bioethics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种数据库装置，连接至网络，其具有连接到所述网络的设备和与所述设备的授权使用人对应的数据库，以便于IoT(物联网)设备的操作。

Description

数据库装置、生成系统和生成方法
相关申请的交叉引用
本申请要求于2019年12月6日提交的日本专利申请第2019-221546号的优先权，上述日本专利申请的全部内容通过引用并入本文。
技术领域
本申请的实施方式涉及一种数据库装置、生成系统和生成方法。
背景技术
近年来，将物体连接到因特网的物联网(IoT：Internet of Thing)相关设备(以下称为IoT设备)越来越普及。由于IoT设备连接到诸如因特网之类的网络，所以能够实现在不同的IoT设备之间产生通信的应用。今后，若随着第5代移动通信系统(以下称为5G)等无线技术的发展能够使得IoT设备更容易地连接到网络，则有望加速IoT设备向普通用户的普及，使单个用户拥有多个IoT设备。通常，为了将设备连接到网络，需要对设备进行参数等的设定、注册等。
相关技术文献
专利文献
专利文献1：日本特开2005-55940号公报
专利文献2：日本特开2005-44201号公报
专利文献3：日本特开2002-189935号公报
专利文献4：日本特开2002-74135号公报
专利文献5：日本特开2001-256317号公报
发明内容
本申请所要解决的技术问题
然而，当单个用户拥有多个IoT设备并在网络上执行复杂的操作如使IoT设备之间协作等时，对IoT设备的设定、注册变得非常繁杂。此外，普通用户不只是限于熟悉信息通信技术(ICT：Information Communication Technology)的用户，在今后的广泛普及中需要使IoT设备的操作变得容易。
本申请所要解决的课题是提供一种数据库装置、生成系统和生成方法，以便于IoT设备的操作。
解决技术问题的技术方案
根据本申请的实施方式的数据库装置连接至网络，其具有连接到所述网络的设备和与所述设备的授权使用者对应的数据库。
附图说明
图1是示出根据实施方式的整个系统的结构示例的图。
图2是示出根据实施方式的设备的功能配置的示例的框图。
图3是示出根据实施方式的应用服务器装置的功能配置的示例的框图。
图4是示出根据实施方式的店铺服务器装置的功能配置的示例的框图。
图5是示出根据实施方式的信息服务器装置的功能配置的示例的框图。
图6是示出根据实施方式的绑定数据库装置的功能配置的示例的框图。
图7是示出第1实施方式中的系统设置示例的图。
图8是示出在第1实施方式中用户购买并使用设备之前的系统的处理操作示例的时序图。
图9A是示出在第1实施方式中由绑定数据库装置针对一个用户生成和管理的数据的示例的图。
图9B是示出在第1实施方式中由绑定数据库装置针对多个用户生成和管理的数据的示例的图。
图10是示出第2实施方式中的系统设置示例的图。
图11是示出在第2实施方式中用户购买并使用设备之前的系统的处理操作示例的时序图。
图12是示出第3实施方式中的系统设置示例的图。
图13是示出第4实施方式中的系统设置示例的图。
图14是示出第5实施方式中的系统设置示例的图。
图15是示出在第5实施方式中用户将设备赠送给其他用户时的系统的处理操作示例的时序图。
图16是示出在第5实施方式中用户将设备赠送给其他用户时的系统的第2处理操作示例的时序图。
图17是描述实施方式中使用的数据的种类和各数据的关系的示例的图。
符号说明：
1...设备、2...应用服务器装置、3...店铺服务器装置、4...信息服务器装置、5...绑定数据库装置、6...PC、11...通信部、12...应用处理部、13...存储部、21...通信部、22...应用服务部、23...信息查询处理部、31...UI部、32...控制部、33...信息查询处理部、34...通信部、35...绑定数据库注册部、36...服务提供部、51...控制部、52...通信部、53...信息注册部、54...存储部、55...信息提供部、100...网络。
具体实施方式
下面参照附图对实施方式进行描述。
图1是示出根据实施方式的整个系统的结构示例的图。
设备1A、1B(除非另有说明，否则简称为设备1)是各种IoT设备，其连接至网络100，并与网络100上的装置进行数据通信。设备1例如可以是温度检测传感器、漏水检测传感器、门开/关传感器等传感器，也可以是使用了这些传感器的检测装置。此外，设备1可以是空调、电视、照明、照相机等家用电器。此外，如果与网络100连接，则设备1也可以是智能手机那样的移动终端。
应用服务器装置2例如构建在具有设置在网络100上的CPU或存储器的计算机上，并提供使用了设备1的应用。应用服务器装置2可以是云服务器。例如，假设漏水检测装置为设备1。当设备1检测到漏水时，应用服务器装置2提供使用了设备1的应用，例如，将设备1通知给应用服务器装置2的报警传送给事先注册的智能手机中并转送通知等。尽管在图中仅示出了一个应用服务器装置2，但是对于每种设备1可以安装多个应用服务器装置2。此外，应用服务器装置2也可以提供组合了多个设备1的应用。特别是在本实施方式中，假设一种使用了稍后描述的绑定数据库设备5的应用。
店铺服务器装置3例如构建在具有设置在网络100上的CPU或存储器的计算机上。店铺服务器装置3可以是云服务器。店铺服务器装置3例如设置在将设备1销售给用户的商家中，并且在用户获得设备1时，通过网络100与系统内的装置交换所需的数据。对于用户获得设备1的方法，虽然在本实施方式示出了购买的情况，但也可以是通过租赁及出租等出借获得、通过促销活动免费获得、折扣获得、通过来自他人的礼物、奖品、赠品等获得，等等。店铺服务器装置3也可以具有POS(Point Of Sale，销售点)终端的功能。店铺服务器装置3也可以具有读卡器，所述读卡器从诸如信用卡、积分卡、マイナンバー(个人号码)(日本注册商标)等卡片中获得用户ID、电子邮件地址、电话号码等用于识别用户(设备1的使用者)的信息(以下称为用户标识信息)。此外，店铺服务器装置3可以设定用于通过网络100向客户端提供服务的统一资源定位符(URL)。
信息服务器装置4例如构建在具有设置在网络100上的CPU或存储器的计算机上。信息服务器装置4将诸如姓名、住址、电话号码之类的用户个人信息(以下称为用户信息)与用户标识信息建立对应关系进行管理，并根据请求提供信息。
绑定数据库装置5例如构建在具有设置在网络100上的CPU或存储器的计算机上。绑定数据库装置5存储将购买者的用户信息和购买的产品信息相关联(绑定)的数据，并生成数据库(特别称为绑定数据库)。在此，产品信息例如是产品名称、制造商名称、型号、序列号等。此外，绑定数据库装置5例如使用制造商名称、型号、序列号等来生成要注册的设备特定信息(特别地称为设备特定信息)，并将其添加到数据库中。设备特定信息是识别各个设备的信息，并且可以是包含能够根据制造商名称、型号、序列号等指定的数字或符号等在内的字符串。
PC6例如是个人计算机，例如是通过网络100访问店铺服务器装置3的客户终端。在邮购的情况下，PC6可以是用户在家中拥有的个人计算机；在店铺销售的情况下，PC6可以是设置在店铺内的个人计算机。
网络100不仅包括因特网，而且还包括用于连接上述装置、设备的所有网络、通信路径，以及将它们组合而形成的网络。例如，当店铺服务器装置3与处理用户信息的信息服务器装置4通信时，使用确保机密性的专用线路或在因特网上实现的虚拟专用网络(VPN：Virtual Private Network)等，这种通信路径也包括在网络100中。此外，网络100不仅可以是有线，也可以是无线的，例如也可以包括WiFi(注册商标)或5G这样的通信方法等。此外，在有线的情况下，例如可以包括使用以太网电缆的通信方法。此外，在网络100上的数据收发中，使用由装置或设备间以及其数据通信路径预定的通信协议。
图2是示出根据实施方式的设备的功能配置的框图。
通信部11与网络100连接，以使设备1与网络100上的装置或设备进行通信。通信部11具有有线通信接口或无线通信接口。此外，通信部11不仅可以具有与网络100通信的接口，而且还可以具有例如用于连接至个人计算机的通用串行总线(USB：Universal Serial Bus)等接口。
应用处理部12通过存储在设备1中的计算机程序等，进行用于使应用服务器装置2提供的应用可用的处理。
存储部13存储设备1所需的设置等。对存储部13的设置等由个人计算机等通过未图示的控制部或通信部11所具有的USB等来实施。
图3是示出根据实施方式的应用服务器装置的功能配置的示例的框图。
通信部21与网络100连接，以与网络100上的装置或设备进行通信。通信部21包括有线或无线通信接口。
应用服务部22使用存储在应用服务器装置2中的计算机程序等，进行用于提供应用的处理。例如，当假设一种使用了设备1的温度检测应用时，应用服务部22对设备1发送的温度检测结果进行接收处理，并通过通信部11将报警通知给网络100上预设的其他装置或设备。
信息查询处理部23根据来自应用服务部22的指令，通过通信部21对网络100上的设备进行信息查询，获得所查询的信息，并将所查询的信息输出到应用服务部22中。在本实施方式中，信息查询处理部23向绑定数据库装置5查询信息。
图4是示出根据实施方式的店铺服务器装置的功能配置的示例的图。
UI部31是用户接口，例如是从信用卡或积分卡、个人号码卡中读取用户标识信息的读卡器。UI部31将读取到的用户标识信息输出到控制部32。此外，UI部31可以从智能电话中读取信息，也可以是键盘、鼠标等计算机外围设备。当UI部31是键盘时，用户或销售商可以从键盘输入包含用户标识信息的与用户有关的信息。
控制部32基于从UI部31输入的用户标识信息来控制店铺服务器装置3的每个功能。另外，可以与图4中未连接至控制部32的所有其他功能块进行数据交换。
信息查询处理部33基于从控制部32输入的指令，通过通信部34对外部装置查询并获得所需的信息。在本实施方式中，信息查询处理部33基于从控制部32输入的用户标识信息来向信息服务器装置4进行查询，获得用户信息。
通信部34与网络100连接，以与网络100上的装置或设备进行通信。通信部34具有有线或无线通信接口。
绑定数据库注册部35将所需信息例如用户信息或购买的产品的产品信息等发送到绑定数据库装置5。
服务提供部36例如包括用于使用户能够通过因特网购买产品的电子商务网站或购买时的处理功能。在不是网络销售而是店铺销售的情况下，也可以不使用本功能。服务提供部36获得用户的购买信息。
图5是示出根据实施方式的信息服务器装置的功能配置的示例的框图。
信息注册部41包括用于将用户信息输入到信息服务器装置4的诸如键盘之类的用户接口，必要时对从用户接口输入的信息进行处理，并将其输出到存储部42。例如，当信用卡公司或积分卡公司创建用户信息数据库时，信息注册部41根据需要处理从用户接口输入的信息以创建数据库。信息注册部41在数据库中注册用户信息时，发布用户标识信息即用户特定的标识信息(ID)。用户标识信息例如是信用卡号、积分卡ID等，存储在信用卡或积分卡等卡上的集成电路(IC：Integrated Circuit)等中。信息注册部41的功能通常在发行信用卡、积分卡等时执行。
存储部42存储从信息注册部41输入的用户信息等数据。
信息提供部43接收来自外部装置的提供存储在存储部42中的数据的请求，并从存储部42获得所请求的数据，并通过通信部44将所获得的数据发送到有请求的外部装置中。
通信部44与网络100连接，以与网络100上的装置或设备进行通信。通信部44具有有线或无线通信接口。
控制部45控制信息服务器装置4的每个功能。另外，可以与图5中未连接至控制部45的所有其他功能块进行数据交换。
图6是示出根据实施方式的绑定数据库装置的功能配置的示例的框图。
控制部51控制绑定数据库装置5的每个功能。具体而言，控制部51接收来自网络100上的外部装置的请求，并根据接收到的请求控制绑定数据库装置5的每个功能。另外，可以与图6中未连接至控制部51的所有其他功能块进行数据交换。
通信部52与网络100连接，以与网络100上的装置或设备进行通信。通信部52包括有线通信接口或无线通信接口。
信息注册部53根据控制部51从网络100上的外部装置中接收到的信息的注册请求，创建信息注册，即绑定数据库。在本实施方式中，当控制部51从店铺服务器装置3接收到信息注册请求时，信息注册部53根据控制部51的控制将店铺服务器装置3发送的用户信息、产品信息等存储在存储部54中，创建绑定数据库。
确定信息生成部531创建绑定数据用户ID，所述绑定数据用户ID是用于在绑定数据库上确定用户的用户确定信息。绑定数据用户ID可以是数字，也可以是包含字符、数字等在内的字符串。此外，确定信息生成部531对注册在绑定数据库中的设备1创建赋予给每个用户的设备管理编号。设备管理编号可以是数字，也可以是包含字符、数字等在内的字符串。设备管理编号可以用作作为设备固有的信息的设备特定信息。
存储部54存储从信息注册部53输入的数据。
当控制部51从网络100上的外部装置接收到信息提供请求时，信息提供部55根据该请求从存储部54获取数据，并通过通信部52向有请求的外部装置发送数据。
(第1实施方式)
在本实施方式中，将示出用户利用自己家的PC6在网络100上的邮购商处购买设备1时的系统的操作示例。
图7是示出第1实施方式中的系统设置示例的图。
用户是设备1的购买者，拥有PC6。邮购商是设备1的销售者，拥有店铺服务器装置3、信息服务器装置4。信息服务器装置4管理用户在邮购商处购买商品时所需的用户标识信息(用户ID)。此外，邮购商保管设备 1即用户购买的产品。服务提供商是设备1的应用提供者，拥有应用服务器装置2、绑定数据库5。
图8是示出在实施方式中用户购买并使用设备之前的系统的处理操作示例的时序图。
在本时序图中，从左侧开始按照时间顺序从上到下示出了PC6、店铺服务器装置3、信息服务器装置4、绑定数据库装置5、设备1、应用服务器装置2各自的处理。在PC6、店铺服务器装置3中，分别包括用户和邮购商店员，在该时序图中用虚线示出了用户和店员的操作行为。邮购商的店员将设备1发送给用户。此时，店员可以根据需要对设备1进行设置等。用实线示出了由PC6、店铺服务器装置3以及其他装置进行的处理(非人为处理)。
下面，将从上方开始按照时间顺序描述本时序图。
用户预先向邮购商注册用户信息，得到用户标识信息(顾客ID)，并购买设备1(阶段P1)。下面，将对详细情况进行描述。
用户通过PC6访问由店铺服务器装置3提供的电子商务网站，并注册用户信息等，以获得账户(步骤S11)。具体而言，用户将用户信息与用户信息注册请求一起从PC6发送到店铺服务器装置3中。
店铺服务器装置3的控制部32当接收到用户信息注册请求时，使服务提供部36执行用户信息注册(步骤S12)。服务提供部36将用户信息等与用户信息注册请求一起发送到信息服务器装置4。
在信息服务器装置4中，控制部45当接收到用户信息注册请求时，向信息注册部41输出用户信息等使其执行用户信息注册。信息注册部41将接收到的用户信息添加到存储部42的数据库中，发布用户标识信息(顾客ID)，并将用户标识信息从通信部44发送到店铺服务器装置3(步骤S13)。店铺服务器装置3将接收到的用户标识信息发送到PC6等，并将其通知给用户(步骤S14)。用户能够通过使用从PC6接收到的用户标识信息来从邮购商处购买产品。
用户通过PC6在店铺服务器装置3的电子商务网站上购买设备1(步骤S15、S16)。具体而言，用户使用PC6通过网络100访问店铺服务器装置3的服务提供部36提供的电子商务网站。在该电子商务网站上，例如，当用户点击要购买的设备1的名称等(步骤S15)并且输入用户支付信息(诸如信用卡支付、银行支付的信息)或用户标识信息等时(步骤S16)，诸如设备1的产品信息、用户支付信息等购买信息和用户标识信息被发送到服务提供部36。服务提供部36当接收到这些信息时，例如通过使“购买完成”等显示在PC6的未图示的显示部上，从而完成用户的购买处理。
接着，店铺服务器装置3执行数据库生成处理(阶段P2)。
店铺服务器装置3将用户信息查询与在阶段P1获取的用户标识信息一起从信息查询处理部33经由通信部34发送到信息服务器4(步骤S21)。在信息服务器装置4中，控制部45当接收到用户信息查询时，使信息提供部43发送用户信息(步骤S22)。具体而言，当控制部45指示信息提供部43发送用户信息时，信息提供单元43基于接收到的用户标识信息从存储部42获取用户信息。信息提供部43通过通信部44将获取的用户信息发送到店铺服务器装置3。
店铺服务器装置3将接收到的用户信息和产品信息作为数据库(DB)信息发送到绑定数据库装置5(步骤S23)。具体而言，在店铺服务器装置3中，绑定数据库注册部35将信息查询处理部33接收到的用户信息和服务提供部36接收到的产品信息合并，根据需要进行处理，创建数据库信息。绑定数据库注册部35将数据库注册请求(数据绑定请求)与所创建的数据库信息一起发送到绑定数据库装置5。
绑定数据库装置5当接收到数据库注册请求时，将接收到的数据库信息注册在数据库中(步骤S24)。更详细而言，在绑定数据库装置5中，当控制部51接收到数据库注册请求时，控制部51将接收到的数据库信息输出到信息注册部53。信息注册部53将数据库信息注册到存储部54。通过以上流程，在绑定数据库装置5上生成将用户信息和产品信息关联在一起的数据库(绑定数据库)。
图9A是示出在实施方式中由绑定数据库装置针对一个用户生成和管理的数据的示例的图。
绑定数据500包括用户特定数据501和产品数据502，并且基本上为一个用户创建一个。例如，当某个组织共同使用所有设备1时，将一个绑定数据500创建为一个组织。在本实施方式中，示出了为一个用户创建一个绑定数据500的示例。
用户特定数据501存储用户确定信息(例如，绑定数据用户ID)，该用户确定信息提供给管理绑定数据库装置5中的数据的用户。用户特定数据501作为能够确定用户个人的数据，除了是绑定数据用户ID以外，也可以是用户标识信息等。此外，只要可以确定用户，则用户固有数据501可以仅仅是例如电话号码，也可以是电子邮件地址等，并且期望一种能够在没有太大改变的情况下确定用户个人的数据。此外，用户特定数据501可以包括姓名、住址、出生年月日等用户个人信息。
产品数据502包括针对每个作为产品的设备1而示出为列项目的“No”、“产品名称”、“制造商”、“型号”和“序列号”这样的数据。每次用户购买设备1时，都会添加一行并注册各列项目的信息。“No”是绑定数据库装置5管理设备1的设备管理编号。优选分配设备管理编号以使每个 用户可以使用的设备为特定编号，可以从下述“产品名称”、“制造商”、“型号”、“序列号”等中选择一个作为设备管理编号，也可以根据所选择的一个生成设备管理编号。此外，可以从下述“产品名称”、“制造商”、“型号”、“序列号”等中选择多个，将其组合作为设备管理编号，也可以由选择的多个组合生成设备管理编号。“产品名称”是设备1的名称。“制造商”是设备1的制造公司的名称。“型号”是包含制造公司对设备1的型号类型等赋予的字符、数字等在内的字符串。“序列号”也可以是包含制造公司唯一地赋予给设备1的文字、数字等在内的字符串。此外，可以添加列项目。例如，在对设备1赋予IP地址时，可以将IP地址添加到数据库中。此外，可以添加提供可以使用设备1的应用的某个应用服务器装置2的IP地址。
产品数据502的D11、D12、D13和D14分别是针对No＝1的设备1的“产品名称”、“制造商”、“型号”、“序列号”。对No＝i的设备1的“产品名称”、“制造商”、“型号”、“序列号”分别是Di1、Di2、Di3、Di4。项目“No”中的N相当于用户可以使用的已注册的设备1的数量。
图9B是示出在实施方式中由绑定数据库装置针对多个用户生成和管理的数据的示例的图。
在绑定数据库装置5的存储部54中，保存有多个不同用户(或法人等组织)中的每一个的绑定数据500A、500B、500C。返回到图8，当绑定数据库装置5的确定信息生成部531发布绑定数据用户ID时，信息注册部53发送完成通知(步骤S25)。此外，在步骤S25中，可以将发布的绑定数据用户ID与完成通知一起发送。店铺服务器装置3当接收到绑定数据用户ID时，使其显示在店铺服务器装置3的未图示的显示部上。另外，如果过去购买设备1时所注册的用户的信息已注册在绑定数据库装置5中，并且该用户已被赋予了绑定数据用户ID，则将该绑定数据用户ID与完成通知一起发送。设备管理编号也可以同时发送。
接着，邮购商对产品实施产品发送(阶段P3)。此外，在阶段P3中，可以根据需要对设备进行参数设置。
邮购商可以对新购买的设备1设置所需参数等信息(步骤S31)。作为设定信息，将设备1的“序列号”“型号”、“设备管理编号”等作为确定设备1的设备特定信息设置在存储部13中。此外，将绑定数据用户ID设置在存储部13中作为确定用户的用户确定信息。从外，作为用户确定信息，也可以是电话号码、电子邮件地址等。此外，也可以使用用户标识信息作为用户确定信息。此外，设置信息包括能够与应用服务器装置2进行通信的信息即应用服务器装置2的IP地址、应用服务器装置2提供的 应用网站URL等，并保存在存储部13中。此外，代替应用服务器装置2的IP地址或URL，设置信息可以包括绑定数据库装置5的IP地址或URL。邮购商将设备1发送给购买它的用户(步骤S32)。在步骤S32中，邮购商可以将通过步骤S31设置了参数的设备1发送给购买该设备的用户。另一方面，邮购商也可以在不执行步骤S31的情况下将无参数设置的设备1发送给购买该设备的用户。
另外，也可以在不同用户的绑定数据500中注册完全相同的设备1、即“制造商”、“序列号”、“型号”等相同的设备1。例如，这相当于不同用户预先共享一个设备1的情况等。在这种情况下，在图8的步骤S16至S26的流程中共享的用户的绑定数据500中，注册共享用户的用户特定信息和新设备1的产品信息等。将对此进行详细描述。
将购买了设备的用户(以下称为购买用户)的用户标识信息和共享用户(以下称为共享用户)的用户标识信息发送到店铺服务器装置3(步骤S16)。店铺服务器装置3将接收到的购买用户和共享用户各自的用户标识信息发送到信息服务器装置4，查询用户信息，获得各自的用户信息(步骤S21、S22)。店铺服务器装置3将购买用户和共享用户各自的用户信息和产品信息发送到绑定数据库装置5(步骤S23)。绑定数据库装置5为购买用户和共享用户中的每一个创建绑定数据库(步骤S24)。
此外，当共享用户是过去在绑定数据500中已注册的用户时，则已获得绑定数据用户ID，因此，省略步骤S21、S22的处理，并在步骤S23中将绑定数据用户ID和新设备1的产品信息发送到绑定数据库装置5，从而可以将新设备1注册在该用户的绑定数据500中。
其次，购买了设备1的用户接收作为产品的设备1，并对其进行设置以及使用(阶段P4)。
用户收到邮购商发送的设备1时将其安装在所需位置(步骤S41)。在需要有线连接网络100的情况下，例如将以太网电缆连接到设备1，并将其设置成能够访问网络100。用户按下设备1的电源开关等，启动设备1(步骤S42)。通过接通设备1的电源来启动设备1(步骤S43)。当设备1启动时，应用处理部12例如参照保存在存储部13中的应用服务器装置2的IP地址，并经由网络100访问应用服务器装置2(步骤S44)。在进行访问时，保存在存储部13中的用户确定信息(绑定数据用户ID、电子邮件地址、电话号码等)和设备特定信息发送到应用服务器装置2。用户确定信息和设备特定信息也可以用作设备1访问应用服务器装置2时的用于授权访问的账户。
在应用服务器装置2中，当应用服务部22检测到来自应用处理部12的访问时，请求绑定数据库装置5确认接收到的用户确定信息和设备特定 信息是否关联在一起，即确认设备1是否是与购买用户或被授权使用的用户绑定的产品(以下称为绑定信息确认)(步骤S45)。更具体而言，当应用服务部22请求信息查询处理部23确认绑定信息时，信息查询处理部23将确认绑定信息的请求与用户确定信息和设备特定信息一起发送到绑定数据库装置5。
绑定数据库装置5当接收到绑定信息确认请求时，确认所接收到的用户确定信息和设备特定信息是否关联在一起，即确认具有设备特定信息的设备1是否是具有用户确定信息的用户所拥有的物品或者是否是可使用的物品，并将绑定信息的确认结果发送到应用服务器22(步骤S46)。更详细而言，控制部51当接收到绑定信息的请求时，同时将接收到的用户确定信息和设备特定信息输出到信息提供部55。信息提供部55确认在存储部54保存的绑定数据500中是否存在与所接收到的用户确定信息和设备特定信息匹配的数据。信息提供部55在绑定数据500中找到与所接收到的用户标识信息和设备特定信息相匹配的设备1时，则向应用服务器装置2发送“是(YES)”的响应。当没有与接收到的用户固有信息和设备特定信息匹配的设备1时，将“否(NO)”响应发送到应用服务器装置2。
应用服务器装置2当接收到“YES”时，开启使用在步骤S13中购买的设备1的应用(步骤S47)。应用服务器装置2当接收到“NO”时，禁止访问的设备1使用应用。此时，应用服务器装置2可以对访问的设备1发送例如“禁止访问”的应答。
通过以上流程，用户可以使用利用设备1的应用。根据本实施方式的实施例，用户在电子商务网站购买设备1，只需安装设备1并按下电源开关就能够使用设备1。此外，在绑定数据库装置5中，通过创建将设备1和购买用户关联的绑定数据库，从而达到消除购买设备1时的初始设置等繁杂性的效果。此外，通过创建绑定数据库，从而带来了在购买设备1时不需要初始设置的便利性。这些效果对用户和设置设备1参数等的店员都有效，单个用户注册的设备1的数量越多效果越好。此外，通过利用绑定数据库装置5明确设备1的所有者或使用者，从而实现禁止所有者或使用者以外的用户使用设备1等安全方面的效果。
考虑到今后与网络100(因特网)连接的设备1增加，会有很多用户使用的情况，通过绑定数据库装置5使设备的操作变得容易的有效性会进一步增大。此外，本实施方式所示的绑定数据库装置5还可以用于使用户拥有的多个设备1彼此协作的应用。此外，通过在绑定数据库装置5中汇集多个用户的绑定数据，也可以用于不同用户所拥有的设备之间的协作。
另外，在本实施方式中，示出了用户过去没有购买设备1，用户信息没有注册在绑定数据库装置5中的情况，但是，例如，在过去购买过，用 户信息注册在绑定数据库装置5中，且该用户的绑定数据已经赋予了绑定数据用户ID的情况下，能够进一步简化流程。
另外，在本实施方式中，在步骤S31的参数设置中，作为用户确定信息，例如可以设置绑定数据用户ID、邮件地址、电话号码等中的任意一个，也可以设置它们的任意多个组合。能够通过例如设备1中设置的用户确定信息的数量来改变设备1使用应用服务器装置2的服务(步骤S47)的安全强度。具体而言，在步骤S45、S46中，在绑定数据库装置5对来自应用服务器装置2的信息查询处理的响应中，增加由信息提供部55用作判断条件的用户确定信息的数量就更能提高安全性的强度。此外，在绑定数据库装置5中，也可以对用户确定信息赋予优先权，对信息提供部55的判断条件进行加权。例如，在绑定数据用户ID对优先于邮件地址的情况下(赋予了权重的情况下)，对于使用绑定数据用户ID作为用户确定信息的设备1，能够读取在邮件地址的使用中不被允许的高度的信息(例如关于余额查询的信息)，或者可以进行在邮件地址的使用中不被允许的重要控制(例如与钱币的支付相关的控制)。
(第2实施方式)
在本实施方式中示出了当拥有邮购商的顾客ID的用户(购买者)在该邮购商处购买产品(设备1)并且邮购商向服务提供商订购产品时的系统的操作示例。此外，还示出了用户过去购买设备1并且用户信息已注册在绑定数据库装置5中时的系统的操作示例。
图10是示出第2实施方式中的系统设置示例的图。
用户是设备1的购买者，拥有PC6。邮购商是设备1的销售者，拥有店铺服务器装置3、信息服务器装置4。服务提供商是设备1的应用提供者，拥有应用服务器装置2、绑定数据库5。在本实施方式中，与第1实施方式不同，服务提供商保管设备1即用户购买的产品。
图11是示出在第2实施方式中用户购买并使用设备之前的系统的处理操作示例的时序图，对于与图8所示的流程相同的部分，赋予相同的阶段、步骤的符号。对于与图8相同的部分省略描述或简化描述。
事先注册和购买流程与图8中的阶段P1相同，因此省略描述。
当用户完成事先注册和购买流程时，生成绑定数据的数据库(阶段P22)。具体而言，店铺服务器装置3获得作为邮购商的用户标识信息的顾客ID时(图8中的步骤S16)，在信息服务器装置4中查询顾客ID的用户信息(步骤S221)。信息服务器装置4从信息服务器装置4的存储部42获取所接收到的顾客ID的用户信息，并将其发送到店铺服务器装置3(步骤S222)。店铺服务器装置3将包含接收到的用户信息和在阶段P1中取得的购买信息的数据库信息发送到绑定数据库装置5(步骤S223)。 绑定数据库装置5确认接收到的用户信息是否注册在存储部54的用户特定数据501中，如果已注册，则将接收到的购买信息注册在产品数据502中(S224)。此外，如果接收到的用户信息没有注册在存储部54的用户特定数据501中，则绑定数据库装置5将用户信息注册在用户特定数据501中，将接收到的购买信息注册在产品数据502中，并向该用户发布绑定数据用户ID。绑定数据库装置5当完成数据库信息的注册时，例如在绑定数据库装置5的未图示的显示部上显示绑定数据用户ID等，并将其通知给服务提供商(步骤S225)。
接着，邮购商对产品实施产品发送(阶段P23)。此外，在本阶段可以根据需要对设备进行参数设置。本阶段只是从第1实施方式所示的阶段P3开始，实施主体从邮购商变为服务提供商。由于实施内容不变，所以省略描述。
接着，购买了设备1的用户接收作为产品的设备1，并对其进行安装以及使用(阶段P4)。本阶段与第1实施方式所示的阶段P4相同，所以省略描述。
通过以上流程，用户(购买者)在邮购商处购买产品(设备1)，并且邮购商向服务提供商订购产品，即使在这种情况下，用户(购买者)也能够通过简单的步骤在邮购商的电子商务网站上购买产品(设备1)来使用设备1。
(第3实施方式)
在本实施方式中，示出了用户(购买者)在店铺内利用店铺发行的积分卡购买产品(设备1)时的系统的操作示例。
图12是示出第3实施方式中的系统设置示例的图。
用户是设备1的购买者。店铺是设备1的销售者并且是销售场所，拥有PC6、店铺服务器装置3、信息服务器装置4。信息服务器装置4管理积分卡的所有者的用户信息。服务提供商是设备1的应用提供者，拥有应用服务器装置2、绑定数据库5。本实施方式与第1实施方式的不同点仅在于设备1的销售者从邮购商变为店铺销售，系统的操作处理流程与图8的时序图相同，因此使用图8仅对与第1实施方式不同的地方进行描述。
用户前往店铺，为了取得店铺发行的积分卡，进行用户信息的注册(步骤S11)。当用户从店铺的PC6输入用户信息时，用户信息与积分卡的注册请求一起被发送到店铺服务器装置3。
店铺服务器装置3的控制部32在接收到积分卡的注册请求时，使服务提供部36执行账户注册(步骤S12)。服务提供部36将用户信息等与积分卡的注册请求一起发送到信息服务器装置4。
在信息服务器装置4中，控制部45在接收到积分卡的注册请求时，向信息注册部41输出用户信息等使其执行积分卡的注册。信息注册部41将接收到的用户信息添加到存储部42的数据库中，并发布用户标识信息(积分卡的用户ID)，将用户标识信息从通信部44发送到店铺服务器装置3(步骤S13)。在信息服务器装置4中，与用户标识信息相关联地管理注册的用户信息。
店铺服务器装置3通过将接收到的用户标识信息发送到PC6等来通知用户(步骤S14)。通常，将搭载有输入了用户标识信息数据的存储器的卡作为积分卡发行给用户。
当将购买信息传递给店员时，店员从PC6输入购买信息，购买信息被发送到店铺服务器装置3(步骤S15)。当用户将积分卡置于与PC6连接的读卡器等中时，用户标识信息被输入到PC6，用户标识信息被发送到店铺服务器装置3(步骤S16)。之后与图8所示的阶段、步骤相同，所以省略描述。
通过以上流程，用户(购买者)使用积分卡在店铺购买产品(设备1)，即使在这种情况下，用户(购买者)也能够通过简单的步骤购买产品(设备1)，从而使用设备1。
(第4实施方式)
本实施方式中，示出了用户A(购买者)在店铺内利用信用卡购买产品(设备1)时的系统的操作示例。
图13是示出第4实施方式中的系统设置示例的图。
用户是设备1的购买者。店铺是设备1的销售者并且是销售场所，拥有PC6、店铺服务器装置3。信用卡公司拥有信息服务器装置4。信息服务器装置4管理信用卡所有者的用户信息。服务提供商是设备1的应用提供者，拥有应用服务器装置2、绑定数据库5。系统的操作处理流程与图8的时序图相同，因此使用图8仅对与第1实施方式以及第3实施方式不同的地方进行描述。
当用户前往店铺将购买信息传递给店员时，店员从PC6输入购买信息，购买信息被发送到店铺服务器装置3(步骤S15)。当用户将信用卡置于与PC6连接的读卡器中时，用户标识信息被输入到PC6，用户标识信息被发送到店铺服务器装置3(步骤S16)。在此，假设信用卡本身的用户注册已经完成，并且在信息服务器装置4中注册了信用卡所有者的用户信息，省略步骤S11至S14的描述。之后与图8所示的阶段、步骤相同，所以省略描述。
通过以上流程，用户(购买者)在店铺内使用信用卡购买产品(设备1)，即使在这种情况下，用户(购买者)也能够通过简单的步骤购买产品(设备1)，从而使用设备1。
(第5实施方式)
在本实施方式中，示出了用户A(购买者)将设备1赠送给用户B(接收者)时的系统的操作示例。用户A(购买者)在邮购商处购买设备1。邮购商将用户B的信息注册在绑定数据库装置中，取得用户B的绑定数据库ID，并设置设备1所需的参数，向用户B发送设备1。存在用户B未注册在绑定数据库装置中的情况和已注册在绑定数据库装置中的情况，首先示出了在未注册的情况下系统的操作示例。
图14是示出第5实施方式中的系统设置示例的图。
用户是设备1的购买者，拥有PC6。邮购商是设备1的销售者，拥有店铺服务器装置3、信息服务器装置4。此外，邮购商保管作为用户购买的产品的设备1。服务提供商是设备1的应用提供者，拥有应用服务器装置2、绑定数据库5。图14的系统设置与第1实施方式中所示的图7的例子相同，但在本图中假设用户为A、B两人。在该示例中，例如，假设如下情况：孩子(用户A)为不熟悉各种设置操作的异地的父母(用户B)引入设备的情况、父母(用户A)为留守在家里的孩子(用户B)引入设备的情况等。
图15是示出在第5实施方式中用户将设备赠送给其他用户时的系统的处理操作示例的时序图。
在下文中，将从上方开始按时间顺序描述本时序图。
事先注册用户B的用户信息，用户A购买设备1(阶段P51)。
在本实施方式中，假设由用户B预先进行用户B的用户信息的事先注册，并发布了用户B的用户标识信息(用户B标识信息)(步骤S151至S154)。发布流程的详细情况与图8中的步骤S11至S14相同，所以省略描述。
用户A从用户B获取用户B的用户标识信息，并且从PC6购买设备1(步骤S155、S156)。具体而言，用户A通过网络100使用PC6访问由店铺服务器装置3的服务提供部36提供的电子商务网站。在该电子商务网站中，例如，当用户A点击购买的设备1的名称，选择购买的设备1，输入用户B的用户标识信息或支付信息等，点击网站上的“OK”按钮等时，设备1的产品信息或支付信息等购买信息和用户B的用户标识信息被发送到业务提供部36。服务提供部36接收到这些信息时，例如通过使“购买完成”等显示在PC6上，从而使得用户A完成购买处理。
然后，店铺服务器装置3执行数据库生成处理(阶段P52)。
店铺服务器装置3将用户B的用户信息查询与在阶段P51中获得的用户B的用户标识信息一起从信息查询处理部33经由通信部34发送到信息服务器装置4(步骤S251)。在信息服务器装置4中，控制部45当接收到用户B的用户信息查询时，使信息提供部43发送用户B的用户信息(步骤S252)。具体而言，当控制部45指示信息提供部43发送用户B的用户信息时，信息提供单元43基于接收到的用户标识信息从存储部42获取用户B的用户信息。信息提供部43通过通信部44将获取的用户B的用户信息发送到店铺服务器装置3。
店铺服务器装置3将接收到的用户B的用户信息和产品信息作为数据库信息发送到绑定数据库装置5(步骤S253)。具体而言，在店铺服务器装置3中，绑定数据库注册部35将信息查询处理部33接收到的用户B的用户信息和服务提供部36接收到的商品信息合并，并根据需要进行处理，创建用户B的数据库信息。绑定数据库注册部35将数据库注册请求与创建的数据库信息一起发送到绑定数据库装置5。
绑定数据库装置5当接收到数据库注册请求(数据绑定请求)时，将接收到的数据库信息注册在数据库中(步骤S254)。更详细而言，在绑定数据库装置5中，当控制部51接收到数据库注册请求时，控制部51将接收到的数据库信息输出到信息注册部53。信息注册部53将数据库信息注册到存储部54。通过以上流程，能够生成将用户B的用户信息和用户A购买的设备信息关联在一起的(绑定在一起)的数据库。
当完成绑定数据500的注册时，绑定数据库装置5的信息注册部53将完成通知与确定信息生成部531创建的用户B的绑定数据用户ID一起发送(步骤S255)。店铺服务器装置3接收绑定数据用户ID，并将其显示在店铺服务器装置3的未图示的显示部上。
接着，邮购商对产品实施参数设置和产品发送(阶段P3)。本阶段中的操作示例与图8相同，因此省略描述，但与第1实施方式的情况不同，邮购商向用户B发送设备1，而不是向购买者即用户A发送设备1。
接着，用户B接收设备1，并对其进行安装以及使用(阶段P54)。
当接收到邮购商发送的设备1时用户B将其安装在所需位置(步骤S451)。根据需要将用于与网络100连接的以太网电缆与设备1连接，并将设备1与网络100连接。用户B按下设备1的电源开关等，使设备1启动(步骤S452)。通过接通设备1的电源来启动设备1(步骤S453)。当设备1启动时，经由网络100访问应用服务器装置2(步骤S454)。之后，步骤S454至S457与图8中的步骤S44至S47相同，因此省略详细描述。
在应用服务器装置2中，当应用服务部22检测到来自应用处理部12的访问时，请求绑定数据库装置5确认绑定信息，例如存在访问的设备1 是否与用户(在本实施例中为用户B)相关联等(步骤S455)。绑定数据库装置5进行绑定信息的确认，并将绑定信息的确认结果发送到应用服务部22(步骤S456)。
应用服务器装置2当接收到“YES”作为绑定信息的确认结果时，开启使用在步骤S153中购买的设备1的应用(步骤S457)。应用服务器装置2当接收到“NO”作为绑定信息的确认结果时，禁止访问的设备1使用应用。
通过以上流程，用户A(购买者)向不具有绑定数据库ID的用户B(接收者)赠送设备1，在该情况下用户B(接收者)可以使用设备1。其次，示出了用户B已在绑定数据库装置中注册了用户特定信息，并且具有绑定数据库ID的情况。
图16是示出在第5实施方式中用户将设备赠送给其他用户时的系统的处理操作示例的时序图。
在下文中，将从上方开始按时间顺序描述本时序图。
用户A购买设备1(阶段P61)。
用户A预先从用户B获得用户B的绑定数据用户ID。用户A从PC6访问由店铺服务器装置3的服务提供部36提供的电子商务网站，当输入与购买的设备1有关的购买信息和用户B的绑定数据用户ID时，购买信息和用户B的绑定数据用户ID被发送到店铺服务器装置3(步骤S163、S164)。
接着，店铺服务器装置3执行数据库生成处理(阶段P62)。
店铺服务器装置3将在阶段P61中取得的用户B的绑定数据用户ID和购买的设备1的产品信息作为数据库信息与数据库注册请求一起发送到绑定数据库装置5(步骤S263)。
当接收到数据库注册请求时，绑定数据库装置5将接收到的数据库信息注册在数据库中(步骤S264)。更具体而言，绑定数据库装置5在存储部54中注册的绑定数据500中搜索注册有接收到的绑定数据ID的绑定数据500，并将接收到的产品信息添加到已搜索到的绑定数据500中。通过以上流程，能够生成将用户B的用户信息和用户A购买的设备信息关联(绑定)在一起的数据库。
之后，产品参数设置以及产品发送阶段与图8中的阶段P3相同，产品的安装使用阶段与图8中的阶段P54相同，因此省略描述。
通过以上流程，在用户B具有绑定数据库ID时，即已将用户特定信息注册在绑定数据库装置中时，用户A(购买者)将设备1赠送给用户B(接收者)，用户B可以使用设备1。
(第6实施方式)
在本实施方式中，示出了店铺(邮购商)的店员使用购买编号作为在设备中设置的项目的情况的例子。下面，对购买编号进行描述。
图17是描述了实施方式中使用的数据的种类和各数据的关系的示例的图，也包括第5实施方式之前的数据的种类、各数据的关系的示例。图17描述了在用户X、设备1、店铺服务器装置3、信息服务器装置4、绑定数据库装置5中使用的数据、存储的数据。但是，这里所示的是一个示例，对于存储数据的装置等，可以轻易地想到各种形态。
用户信息是与用户X有关的信息，例如是姓名、住址、电话号码、电子邮件地址、所属公司名称等。用户X是信息源，用户信息由用户X提供。另外，在用户X将设备1赠送给用户Y的情况下(第5实施方式的情况下)，用户信息可以是与用户Y有关的信息。用户信息也可以提供给信息服务器装置4(由信用卡公司或积分卡公司等所拥有)、店铺服务器装置3(由设备的销售店铺、邮购商等所拥有)、绑定数据库装置5(由使用设备的应用服务提供商等所拥有)。另外，店铺服务器装置3在用户信息包含有相当于用户确定信息的信息的情况下，也可以不必将该信息以外的信息发送给绑定数据库装置5。
信息服务器装置4根据所获得的用户信息，生成(发布)信用卡号码或积分卡号码(用户ID)等用户标识号。
用户标识号是由信用卡公司、积分卡公司等发布的用于识别用户X的数字或字符等，并且被提供给用户X、店铺服务器装置3、绑定数据库装置5等。此外，可以将由用户指定的ID或密码等生成的用户特定的号码用作用户标识号。在该情况下，例如，当用户从店铺服务器装置3输入用户专用ID或密码时，可以使用发布用户特定号码的未图示的认证服务器。可以将用户认证服务器发布的用户特定号码(可以包括号码、字符等)用作用户标识号。这样，用户不需要将信用卡号码等需要高安全性的信息提供给店铺服务器装置3或绑定数据库装置5。此外，用户标识号不一定是字符串或号码串等，例如在使用图像认证或声音认证等来代替店铺服务器装置3的UI部31的读卡器时，可以是“图像数据”、“声音数据”等认证数据。
用户X通过例如搭载有存储了用户标识号的存储器的信用卡等来获得用户标识号。
店铺服务器装置3使用读卡器从用户X的例如信用卡中获取用户标识号。店铺服务器装置3能够使用所获得的用户标识号来获取存储在信息服务器装置4中的用户信息。另外，用户X也可以将用户信息从客户端PC6等直接提供给店铺服务器装置3。此外，在图17中，示出了店铺服务器装 置3分别保存有用户信息和用户标识信息的示例，但也可以将双方合并作为用户信息发送到绑定数据库装置5。
绑定数据库装置5从店铺服务器装置3获得包含在数据库信息(DB信息)中的用户信息。绑定数据库装置5将获得的用户信息存储在用户特定数据501中。另外，店铺服务器装置3也可以将用户标识号包含在数据库信息(DB信息)中，向绑定数据库装置5发送用户标识号。绑定数据库装置5将用户标识号存储到用户特定数据501中。
绑定数据库装置5从用户特定数据501中提取或生成用户确定信息。用户确定信息是只要有该信息就能确定用户X的信息。具体而言，从用户特定数据501的用户信息中提取住址、电话号码、电子邮件地址、公司名称等作为用户确定信息。例如，在处于某特定的住址的家庭、公司等组织中使用所获得的设备，则可以将“住址”、“公司名称”用作用户确定信息。例如，在用户X是智能手机等的使用者的情况下，将“电话号码”、“电子邮件地址”用作确定用户X的用户确定信息。用户X可以决定哪个项目是用户确定信息。
绑定数据库装置5生成用于在绑定数据库装置5的数据库中确定用户X的绑定数据用户ID。绑定数据用户ID将从用户信息中提取的用户确定信息或用户标识信息与其他已经注册的用户的绑定数据库进行比较，生成用户X特定的绑定数据用户ID。绑定数据库装置5将所生成的绑定数据用户ID存储在用户特定数据501中。此外，绑定数据库装置5将绑定数据用户ID作为“所选择的用户确定信息”发送到店铺服务器装置3。店铺服务器装置3将绑定数据用户ID作为“所选择的用户确定信息”发送给用户X。此外，店铺服务器装置3将绑定数据用户ID作为“所选择的用户确定信息”设置在设备1中。另外，“所选择的用户确定信息”不仅可以是绑定数据用户ID，也可以是从用户确定信息中选择的一个以上的项目。例如，可以将电话号码和电子邮件地址的组合作为“所选择的用户确定信息”，也可以仅将电子邮件地址作为“所选择的用户确定信息”。也可以将电话号码、电子邮件地址和绑定数据用户ID的组合作为“所选择的用户确定信息”。此外，也可以将用户标识信息作为“所选择的用户确定信息”。
购买信息是用户X想要获得的设备1的产品信息、用户X获得设备1所需货款的支付方法等用户支付信息，用户X是信息源，由用户X提供。
产品信息包括要获得的设备1(产品)的制造商名称、型号、序列号等。另外，产品信息本身保存在店铺服务器装置3中，如果用户X点击显示在店铺服务器装置3的电子商务网站上的设备1(产品)的照片等，则也可以在店铺服务器装置3中将用户X想要获得的设备1和其产品信息进行关联。
用户支付信息是用于获得设备的货款等的支付方法或金额等。在银行支付的情况下，也可以将银行账户、卡的类型(例如，预付卡、电子钱包等)、以及其他包含在用户支付信息中。另外，当用户X在销售店铺内以现金的方式进行支付时，支付方法为“现金支付”。用户X向店铺服务器装置3发送产品信息和用户支付信息。店铺服务器装置3将接收到的产品信息包含在DB信息中，并将其发送到绑定数据库装置5。绑定数据库装置5将接收到的产品信息存储在产品数据502中。
绑定数据库装置5生成设备特定信息，所述设备特定信息是用于从接收到的产品信息中确定产品的信息。具体而言，也可以生成用户X的绑定数据库的产品数据的项目“No”(设备管理编号)作为设备特定信息。所生成的设备管理编号存储在产品数据502中。此外，可以将接收到的产品信息的要素，例如“制造商名称”、“序列号”等作为设备特定信息，也可以将多个要素的组合作为设备特定信息。绑定数据库装置5将设备特定信息发送到店铺服务器装置3。由店铺服务器装置3接收到的设备特定信息例如由销售店铺的店员、邮购商的店员设置在设备1中。
店铺服务器装置3当从用户X获得用户支付信息时，生成购买编号。店铺服务器装置3除了拥有与用户X相关的用户特定数据501的信息、用户X本次要获得的产品数据502的信息之外，还拥有用户支付信息、购买历史。购买历史例如包括购买地点、购买时间等。因此，店铺服务器装置3通过使用这些信息，能够生成同时考虑了用户X的用户确定信息和用户X本次要获得的设备特定信息的购买编号。即，店铺服务器装置3将生成的购买编号设置到设备1中，并注册到绑定数据库装置5中。购买编号可以是日期、场所、邮件地址、使产品信息的序列号连接起来的数字串、字符串等。代替邮件地址，也可以使用绑定数据用户ID或电话号码，也可以使用它们的组合。当用户X获得的设备1向应用服务器装置2发送购买编号时，如果应用服务器装置2向绑定数据库装置5发送接收到的购买编号，则可以知道设备1和该设备1的授权使用人。
以上，只要店铺(邮购商)的店员在设备1中设置购买编号，用户X就能够使用设备1，无需进行复杂的步骤。
根据上述至少一个实施方式，提供一种数据库装置、生成系统、生成方法，以便于IoT设备的操作。
另外，在上述实施方式中，例如应用服务器装置2或绑定数据库装置5被描述为单独的装置，但它们也可以构建在同一硬件装置上。对于其他装置也同样可以考虑装置的功能和执行该功能的硬件的各种结构、组合，但不限于上述所示的实施方式的示例。
此外，在本实施方式中，示出了购买作为用户获得设备1的方法的情况，但也可以通过租赁及出租等出借获得、活动免费获得、折扣获得、来自他人的礼物、奖品、赠品等获得，等等。
无论在哪种情况下，店铺服务器装置3都能够通过获得作为授权使用人的用户的用户信息、用户标识信息、用户想要获得的设备1的产品信息，将绑定数据库装置5中的用户信息和产品信息结合(绑定)在一起。在获得方法不是购买而是例如租赁的情况下，店铺服务器装置3也可以利用租赁日期、租赁场所等代替购买日期、购买场所，以发布相当于购买编号的号码。在是赠品的情况下，店铺服务器装置3使用赠品发送日期、发送场所等代替购买日期、购买场所，以发行相当于购买编号的号码。
虽然对本申请的一些实施方式进行了描述，但这些实施方式是示例性的，并不意图限制本申请的范围。这些新的实施方式能够以其他各种方式实施，在不脱离本申请的主旨的范围内，能够进行各种省略、置换、变更。这些实施方式或其变形包含在本申请的范围或要旨内，并且包含在权利要求书所述的发明及其均等的范围内。此外，即使是在权利要求的各构成要素中将构成要素分割表述的情况，或者将多个要素合并表述的情况，或者将其组合表述的情况，也是本申请的范畴。此外，可以组合多个实施方式，并且由该组合构成的实施例也是本申请的范畴。
此外，为了使描述更加清楚，附图与实际的形态相比，有时示意性地表示各部分的宽度、厚度、形状等。在方框图中，有时也在未被连接的方框之间，或者在虽连接但未图示箭头的方向上进行数据或信号的交换。也可以通过硬件(IC芯片等)、或者软件(程序等)、或者硬件和软件的组合来实现方框图所示的各功能、流程图、时序图所示的处理。此外，在将权利要求表述为控制逻辑的情况下，在表述为包含使计算机执行的指令的程序的情况下，以及在表述为记载了上述指令的计算机可读记录介质的情况下，也可以应用本申请的装置。此外，对于所使用的名称或术语也没有限定，即使是其他的表述，如果实质上是相同的内容、相同的宗旨，也包含在本发明中。

Claims (12)

  1. 一种连接到网络的数据库装置，具有连接到所述网络的设备和与所述设备的授权使用者对应的数据库。
  2. 根据权利要求1所述的数据库装置，所述数据库包含确定所述授权使用者的用户确定信息和确定所述授权使用者可使用的设备的设备特定信息。
  3. 根据权利要求2所述的数据库装置，具有：
    确定信息生成部，其生成所述设备特定信息。
  4. 根据权利要求2或3所述的数据库装置，所述用户确定信息包括从用于确定所述授权使用者的信息组中选择的至少一个信息，包括电子邮件地址、电话号码、住址、所属公司名称、个人号码(注册商标)、包含信用卡ID在内的所述授权使用者固有的卡ID、作为用户标识信息而得到的认证数据等。
  5. 根据权利要求2-4中任一项所述的数据库装置，具有：
    确定信息生成部，其生成所述用户确定信息。
  6. 根据权利要求2所述的数据库装置，具有：
    信息提供部，其基于所述设备特定信息和所述用户确定信息，决定所述设备的使用的授权。
  7. 根据权利要求1或2所述的数据库装置，具有：
    信息提供部，其基于所述数据库中的第1设备特定信息和第1用户确定信息、从连接到所述网络的设备输入的第2设备特定信息和第2用户确定信息，决定所述设备的使用的授权。
  8. 一种生成系统，具有：
    店铺服务器装置，其包括数据绑定请求发送部，所述数据绑定请求发送部将产品信息和用户信息与绑定请求一起输出，所述绑定请求用于将与用户获得的设备有关的产品信息和作为所述用户的特定信息的用户信息结合在一起；以及
    绑定数据库装置，其包括请求接收处理部与数据绑定部，所述请求接收处理部对所述产品信息、所述用户信息和所述绑定请求进行接收处理，所述数据绑定部将所述用户信息与所述产品信息结合在一起。
  9. 根据权利要求8所述的生成系统，所述绑定数据库装置包括确定信息生成部，所述确定信息生成部基于所述用户信息发布确定所述用户的用户确定信息，并基于所述产品信息发布设备特定信息，所述设备特定信息 能够在数据库中的作为所述用户的固有数据的用户特定数据中确定所述设备。
  10. 根据权利要求9所述的生成系统，
    所述店铺服务器装置包括确定信息接收部，所述确定信息接收部接收所述用户确定信息和所述设备特定信息，
    所述数据绑定请求发送部输出所述用户确定信息和所述设备特定信息。
  11. 根据权利要求10所述的生成系统，
    所述店铺服务器装置包括确定信息接收部，所述确定信息接收部接收所述用户确定信息，所述数据绑定请求发送部输出所述用户确定信息作为所述用户信息。
  12. 一种生成方法，包括：
    将产品信息和用户信息与绑定请求一起输出，所述绑定请求用于将与用户获得的设备有关的产品信息和作为所述用户的特定信息的用户信息结合在一起，
    对所述产品信息、所述用户信息和所述绑定请求进行接收处理，
    将所述用户信息与所述产品信息结合在一起。
PCT/CN2020/127175 2019-12-06 2020-11-06 数据库装置、生成系统和生成方法 WO2021109798A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202080008575.1A CN113273139B (zh) 2019-12-06 2020-11-06 数据库装置、生成系统和生成方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2019-221546 2019-12-06
JP2019221546A JP7214616B2 (ja) 2019-12-06 2019-12-06 データベース装置、データ処理システム、データ処理法およびデータ処理プログラム

Publications (1)

Publication Number Publication Date
WO2021109798A1 true WO2021109798A1 (zh) 2021-06-10

Family

ID=76221421

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127175 WO2021109798A1 (zh) 2019-12-06 2020-11-06 数据库装置、生成系统和生成方法

Country Status (3)

Country Link
JP (1) JP7214616B2 (zh)
CN (1) CN113273139B (zh)
WO (1) WO2021109798A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20240013592A (ko) * 2022-07-22 2024-01-30 삼성전자주식회사 이동 통신 시스템에서 사용자와 단말을 바인딩하는 방법 및 장치

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104883402A (zh) * 2015-05-29 2015-09-02 四川长虹电器股份有限公司 一种信息处理方法及云端服务平台
CN105228089A (zh) * 2015-09-30 2016-01-06 成都信汇聚源科技有限公司 一种可穿戴设备多传感器适配及实时数据采集方法
US20170359338A1 (en) * 2014-12-17 2017-12-14 Arm Ip Limited Management of relationships between a device and a service provider
CN107705172A (zh) * 2017-09-19 2018-02-16 北京小艾智联科技有限公司 一种物联网商品租赁运营系统及方法
CN108111895A (zh) * 2017-12-12 2018-06-01 浙江视野环境艺术装饰工程有限公司 一种智能化家居控制系统、方法及其控制端
CN109361535A (zh) * 2018-09-27 2019-02-19 北京小米移动软件有限公司 智能设备绑定方法、装置及存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002133071A (ja) * 2000-11-27 2002-05-10 E Kikai.Com:Kk 営業支援システム、営業支援方法、営業支援プログラムを記録した媒体、営業支援装置、営業支援装置の制御方法および営業支援装置の制御プログラムを記録した媒体
JP2003271559A (ja) * 2002-03-18 2003-09-26 Sony Corp 情報処理システム、情報処理装置および方法、並びにプログラム
JP2004171107A (ja) * 2002-11-18 2004-06-17 Sony Corp ソフトウエア提供システム、ソフトウエア提供装置および方法、記録媒体、並びにプログラム
WO2005122492A1 (ja) * 2004-06-07 2005-12-22 Nippon Telegraph And Telephone Corporation 宅内ネットワーク設定方法、ホームゲートウェイ装置、ホームゲートウェイプログラム、記録媒体
US20080126258A1 (en) * 2006-11-27 2008-05-29 Qualcomm Incorporated Authentication of e-commerce transactions using a wireless telecommunications device
JP2016201659A (ja) * 2015-04-09 2016-12-01 株式会社ピーシーデポコーポレーション サービス提供システム、サービス提供方法、及びプログラム
CN109409893A (zh) * 2018-08-20 2019-03-01 杭州复杂美科技有限公司 一种信任系统及其构建方法、设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170359338A1 (en) * 2014-12-17 2017-12-14 Arm Ip Limited Management of relationships between a device and a service provider
CN104883402A (zh) * 2015-05-29 2015-09-02 四川长虹电器股份有限公司 一种信息处理方法及云端服务平台
CN105228089A (zh) * 2015-09-30 2016-01-06 成都信汇聚源科技有限公司 一种可穿戴设备多传感器适配及实时数据采集方法
CN107705172A (zh) * 2017-09-19 2018-02-16 北京小艾智联科技有限公司 一种物联网商品租赁运营系统及方法
CN108111895A (zh) * 2017-12-12 2018-06-01 浙江视野环境艺术装饰工程有限公司 一种智能化家居控制系统、方法及其控制端
CN109361535A (zh) * 2018-09-27 2019-02-19 北京小米移动软件有限公司 智能设备绑定方法、装置及存储介质

Also Published As

Publication number Publication date
CN113273139B (zh) 2023-04-28
JP2021092857A (ja) 2021-06-17
JP7214616B2 (ja) 2023-01-30
CN113273139A (zh) 2021-08-17

Similar Documents

Publication Publication Date Title
US20150154592A1 (en) Authorizing a transaction between a client device and a server using a scannable code
WO2013185147A2 (en) Authorizing a transaction between a client device and a server using a scannable code
CN109285044A (zh) 应用销售管理服务器系统
JP2019204479A (ja) 知人の商品購買履歴、関心商品及び利用後記を活用した商品販売システム
JP5779615B2 (ja) 多様な決済手段を用いるａｒｓ認証ベースの決済システム及び決済方法
KR20150095969A (ko) 오픈마켓의 통합관리 시스템
US20160132956A1 (en) Electronic Commerce Platform and Transaction Method Using the Same
JP5266807B2 (ja) 情報処理装置、決済システム、決済方法及びプログラム
JP6680733B2 (ja) 生成装置、生成方法及び生成プログラム
CN109286652A (zh) 应用销售管理服务器系统以及边缘服务器
JP5496398B1 (ja) 決済装置、決済プログラム、及びｅｃサーバ
WO2021109798A1 (zh) 数据库装置、生成系统和生成方法
KR20200006708A (ko) 가상화폐를 이용한 결제 시스템
KR100880277B1 (ko) 홈 네트워크를 이용한 결제 방법 및 결제 시스템
CN109285045A (zh) 应用销售管理服务器系统
KR20160014378A (ko) 특정한 개인만 접속할 수 있고 방문자로서 개인을 대리하여 다른 사이트를 방문하고 그리고 자체적으로 다른 사이트를 방문할 수 있는 기능을 보유한 인터넷 사이트와 그리고 상기 사이트를 이용하여 수익을 창출하는 사업방법과 분실된 카드의 사용을 방지하는 방법.
KR101505032B1 (ko) Ｕｒｌ을 이용한 전자상거래 관리서버 및 그 관리방법
JP6899179B2 (ja) 決済システムおよび決済方法
JP2006268416A (ja) 取引情報管理装置及び取引情報管理方法及び取引情報管理プログラム及び取引情報管理システム
TW201415389A (zh) 用於安全交換資料之通訊系統、運算裝置及方法
KR20100120570A (ko) 이동통신단말 이용한 마일리지와 휴대폰 결제의 복합 결제 시스템 및 그 복합 결제 방법
KR20140121495A (ko) 공동구매 서비스 제공방법
JP7493578B1 (ja) 本人確認支援システム及びプログラム
US20230186298A1 (en) User-linked payment methods for completion of an online transaction
US20230230073A1 (en) User-linked payment methods for completion of an online transaction

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20895658

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20895658

Country of ref document: EP

Kind code of ref document: A1