JP2015130027A - File providing server device, file providing system, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a burden on a provider for confirming charge collection when providing files, such as a program and a firmware.SOLUTION: A file providing server device includes: file storage means for storing files corresponding to product names; and file output means for retrieving a first sale record including an inputted individual number and a second sale record including an inputted product name from sale record storage means for storing a sale record including a product name of a product, a purchaser's name, and the individual number for each product after the individual number and product name are inputted, and for acquiring a file corresponding to the inputted product name from the file storage means and for outputting the file when the two sale records are obtained and the purchaser's names included in the two sale records agree.

Description

  The present invention relates to a file providing server device, a file providing system, a method, and a program, and more particularly to a file providing server device, a file providing system, a method, and a program that use a sales history.

  In recent years, data traffic flowing through networks has increased explosively due to the increase in large-capacity content and the spread of mobile terminals. In order to enhance the functions of economical networks and nodes, it is preferable to upgrade existing nodes rather than purchasing new nodes. In order to correctly understand whether additional functions have been sold for the target node and the update file has been applied to the target node on the occasion of adding the function of the node, the sales department and the file providing department It was necessary to witness the cooperation and file update work of the customer. In relation to this problem, the following techniques are disclosed.

  The system of Patent Document 1 provides a database that stores router identification information and firmware identification information (firmware name + version information) in association with each other, and associates the firmware identification information of the collected firmware with the router identification information. Register in the database. When the router identification information and the firmware identification information are designated and the firmware download is requested, the database is referred to, and only when the correspondence between the designated router identification information and the firmware identification information is registered in the database 3a Firmware download is allowed.

  Patent Document 2 discloses a server terminal that encrypts and outputs an update program of package software stored in a user terminal. When this update program is combined, the update program checks conditions such as whether the usage status such as the accumulated usage amount stored in the usage status database of the user terminal is within the usage limit.

  Patent Document 3 discloses that license information is incorporated into an application program and the license information is confirmed at the time of upgrade.

  Patent Document 4 discloses a card that communicates with a terminal and a server via the Internet, acquires a key for encrypting the content, and passes the key for encrypting the content to the terminal based on a request from the terminal. The card checks whether the terminal is a valid terminal or not when delivering a key for encrypting content, and does not output the key unless it is a valid terminal. The card passes the key after confirming the legitimacy of the other party by known mutual authentication or the like.

  Patent Document 5 discloses an SD (Secure Digital) card having an authentication function.

JP 2005-235112 A JP 2005-63207 A International Publication No. 2006/106689 International Publication No. 2008/004524 JP 2006-079449 A

  In the system of Patent Document 1, it is necessary to prepare a special database in order to confirm whether or not to charge for the firmware to be updated. This is a heavy burden on the person who provides the program / firmware. An object of this invention is to provide the technique which reduces this burden.

  The techniques of Patent Documents 2 and 3 are not techniques for confirming whether or not the update program and the upgrade program can be used. This is a technology for confirming whether or not a base program can be used. The techniques of Patent Documents 4 and 5 are not related to the above problem.

  A file providing server device according to an embodiment of the present invention has a file storage means for storing a file corresponding to a product name, an individual number and a product name, and the product name and purchaser name of the product for each product. The sales record storage means for storing the sales record including the individual number is searched for the first sales record including the input individual number and the second sales record including the input product name, and the two sales A file output unit that obtains a file corresponding to the input product name from the file storage unit when a record is obtained and a purchaser name included in the two sales records matches, and outputs the file; Is provided.

  A method according to an embodiment of the present invention stores a file corresponding to a product name, inputs an individual number and a product name, and includes a sales record including the product name, purchaser name, and individual number of the product for each product. From the sales record storage means for storing the first sales record including the input individual number and the second sales record including the input product name, and the two sales records are obtained, and When the purchaser names included in the two sales records match, a file corresponding to the input product name is acquired from the file storage means and output.

  A program according to an embodiment of the present invention includes a process for storing a file corresponding to a product name, an individual number and a product name are input, and each product includes a product name, a purchaser name, and an individual number of the product. From the sales record storage means for storing the sales record, the first sales record including the input individual number and the second sales record including the input product name are searched, and the two sales records are obtained. In addition, when the purchaser names included in the two sales records match, the computer acquires a file corresponding to the input product name from the file storage unit and outputs the file.

  According to the present invention, it is possible to reduce a burden on a provider for confirming charge collection when providing a file such as a program / firmware.

FIG. 1 is a diagram showing the configuration of the file providing system 60. FIG. 2 shows data related to the file 14 stored in the file storage unit 12. FIG. 3 shows the format of the sales record. FIG. 4 is an operation flowchart of the file output unit 11 of the file providing server device 10. FIG. 5 is an operation flowchart of the sales management unit 21 of the sales history server device 20. FIG. 6 is an operation flowchart of the node device 50. FIG. 7 is a configuration diagram of the file providing server device 10 according to the second embodiment.

<First Embodiment>
The file providing system 60 according to the present embodiment identifies the sales information and the individual number of the node device 50 for the file update for the function upgrade for the network device and the terminal device (hereinafter referred to as the node device 50). Software, firmware, or field-programmable gate array (FPGA) file provision is systematized. This makes it possible to provide an upgrade file that matches the contract and to provide the file to the user on demand. Further, the file providing system 60 realizes a vendor upgrade file medium creation and transmission work reduction. Hereinafter, the file providing system 60 will be described with reference to the drawings.

  FIG. 1 is a diagram showing the configuration of the file providing system 60. It includes a file providing server device 10, a sales history server device 20, and an NM device 40 (Network Management) connected to the file providing server device 10 via a network. One or more node devices 50 are connected to the NM device 40.

  The file providing server device 10 is, for example, a server device operated by software or firmware vendor. The file providing server device 10 includes a file storage unit 12 that stores the file 14 transmitted to the node device 50, and a file output unit 11 that transmits the designated file 14 to the NM device 40.

  The file 14 is, for example, a program or firmware provided for a fee and executed by the node device 50. Normally, the program and firmware are products that are newly added to the node device 50, or upgrade products that are already installed. If provided for a fee, this program or firmware may be an updated product that has absorbed bugs.

  The file storage unit 12 is a storage device such as a disk device. The file output unit 11 is a logic circuit. The file output unit 11 may be realized by a program that is stored in a memory (not shown) provided in the file providing server device 10 that is a computer and executed by a processor (not shown) provided in the file providing server device 10. .

  The sales history server device 20 is, for example, a server device operated by software or firmware vendors or their vendors. The sales history server device 20 includes a sales record storage unit 22 that stores sales records and a sales management unit 21 that searches for sales records and transmits the information to the file providing server device 10.

  The sales record storage unit 22 is a storage device such as a disk device. The sales management unit 21 is a logic circuit. The sales management unit 21 may be realized by a program stored in a memory (not shown) included in the sales history server device 20 that is a computer and executed by a processor (not shown) included in the sales history server device 20. .

  The NM device 40 is, for example, a computer equipped with an NMS (Network Management System), and acquires the file 14 from the file providing server device 10 in accordance with a user instruction input from the keyboard 41 or the like, or sends it to the node device 50. Or send.

  The node device 50 receives the file 14 from the NM device 40 and installs it in its own device. The node device 50 stores the individual number 51 of its own device in a non-rewritable memory (not shown).

  FIG. 2 shows data related to the file 14 stored in the file storage unit 12. The file storage unit 12 stores a product name 13 and a file 14 of the product in association with each other for each of a plurality of products.

  FIG. 3 shows the format of the sales record. The sales record includes, for each of a plurality of products, a product name 23, a purchaser name 24 of the product, and an individual number 25 of the product sold to the purchaser. The individual number 25 is identification information unique to each individual product, for example, a manufacturing number. For example, when the product is the node device 50, the individual number 25 may be a MAC address (Media Access Control address). The sales record may include other information. A sales record is, for example, a copy of a sales slip created every time a product is sold. The sales record storage unit 22 normally stores a plurality of sales records.

  FIG. 4 is an operation flowchart of the file output unit 11 of the file providing server device 10. When the user inputs the product name of the file 14 to be installed and the individual number of the node device 50 that executes the installation from the keyboard 41, the NM device 40 transmits these pieces of information to the file providing server device 10.

  When the file output unit 11 receives these pieces of information from the NM device 40 (C101), both the product name acquired from the NM device 40 (the product name of the file 14 to be installed) and the individual number of the node device 50 that executes the installation Is sent to the sales history server device 20 (C102), and a response is received (C103).

  The response includes a sales record in which the individual number 25 matches the individual number acquired from the NM device 40 (hereinafter, the first sales record), and a sales record in which the product name 23 matches the product name acquired from the NM device 40 ( Hereinafter, the second sales record) is included. There is one first sales record, but there can be a plurality of second sales records. If the first sales record is not in the sales record storage unit 22, the response includes a notification to that effect. If the second sales record is not in the sales record storage unit 22, the response includes a notification to that effect.

  In the file output unit 11, the received response includes both the first and second sales records, and among the second sales records, the first sales record matches the purchaser name 24. It is determined whether or not (C104). If the determination is true (OK in C104), the file output unit 11 encrypts the file 14 (C105). At this time, the file output unit 11 takes out the file 14 having the product name 13 that matches the product name acquired from the NM device 40 from the file storage unit 12, and encrypts it using the individual number acquired from the NM device 40 as a key. . The file output unit 11 may use any existing encryption method. Here, it is assumed that a common key encryption method using an individual number as a secret key is used.

  Finally, the file output unit 11 outputs the result including the encrypted file 14 to the NM device 40 (C106).

  If the received response does not include the first or second sales record or the purchaser name 24 is not the same (NG in C104), the file output unit 11 outputs a result including an error to the NM device 40 (C106). ). The reason for the error termination is that it is possible to determine that both the node device 50 that executes the installation and the file 14 have not been purchased by the same user.

  The NM device 40 that has received the encrypted file 14 from the file providing server device 10 stores the file 14 in its own device. Thereafter, when the user inputs a transfer instruction from the keyboard 41, the NM device 40 transfers the file 14 to the node device 50.

  FIG. 5 is an operation flowchart of the sales management unit 21 of the sales history server device 20. First, the sales management unit 21 receives a sales information request including both the product name of the file 14 to be installed and the individual number of the node device 50 that executes the installation from the file providing server device 10 (C201).

  First, the sales management unit 21 searches the sales record storage unit 22 using the received individual number as a key, and acquires a first sales record with the same individual number 25. Next, the sales management unit 21 searches the sales record storage unit 22 using the received product name as a key, and obtains a second sales record that matches the product name 23 (C202).

  Thereafter, the sales management unit 21 creates a response to the sales information request including the first and second sales records, and transmits the response to the file providing server device 10 (C203). If there is no first or second sales record in the sales record storage unit 22, the sales management unit 21 includes a display to that effect in the response.

  FIG. 6 is an operation flowchart of the node device 50. First, the node device 50 receives an encrypted file 14, for example, an update file for upgrade, from the NM device 40 (C104). Thereafter, the node device 50 reads out the individual number 51 of the own device, and decrypts the file 14 using this as a key (C402). If the decryption is successful (success in C402), the node device 50 installs the file 14 (C403). That is, when the file 14 is an upgrade file, the node device 50 executes the upgrade.

  Finally, the node device 50 transmits success or failure of installation to the NM device 40 (C404). If the decryption of the file 14 fails (failed in C402), the node device 50 does not execute the installation and transmits the failure to the NM device 40 (C404). The reason is that the received file 14 is not intended for its own device.

  The file providing server device 10 may include a sales record storage unit 22. In this case, the file output unit 11 reads the sales record from the sales record storage unit 22 without going through communication.

  Further, the file providing server device 10 and the NM device 40 may not be connected via a network. In this case, the encrypted file 14 is carried from the file providing server device 10 to the NM device 40 via the exchangeable storage medium.

  The file providing server device 10 according to the present embodiment can exhibit the following effects.

  The first effect is that the file 14 can be provided only to the purchased user by using a copy of the sales slip. That is, the file providing server device 10 can reduce the burden for sales confirmation on the provider of the program / firmware and the like when providing the file 14 such as the program / firmware. The reason is that the file output unit 11 acquires the first and second sales records from the sales record storage unit 22 of the sales history server device 20 and confirms that the purchaser name 24 matches. The sales record storage unit 22 only needs to store a copy of the sales slip, and it is not necessary to prepare a special database.

  The second effect is that installation can be performed only on an appropriate node device 50 by using the individual number of the node device 50. The reason is that the file output unit 11 encrypts and outputs the file 14 using the individual number of the node device 50 confirmed to be purchased as a key.

  The third effect is that the creation / provision of the file medium of the provider of the file 14 and the management work of the individual number of the node device 50 can be reduced. The reason is that the user acquires the individual number from the installation execution node device 50 and inputs it to the file providing server device 10 to acquire the file 14.

The fourth effect is that the user can acquire the file 14 for upgrading the node device 50 at a necessary timing. The reason is that the file providing server device 10 uses the sales history, so there is no need to wait for the creation of a special database.
<Modification of First Embodiment>
Note that the file providing system 60 according to the present embodiment can be modified to perform a series of systemization from the purchase of a program / firmware product to the installation of the file 14.

In this modification, the user inputs the product name of the product to be purchased and the individual identification number of the node device 50 that executes the installation to the file providing server device 10. The file output unit 11 makes a sales request for the product in C102. Upon receiving this, the sales management unit 21 executes the product sales / fee collection process, and then registers the sales record of the product in the sales record storage unit 22 and the file output unit as the second sales record. Output to 11. The file output unit 11 may operate in the same manner as in the first embodiment after C106.
<Second Embodiment>
FIG. 7 is a configuration diagram of the file providing server device 10 according to the second embodiment.

  The file providing server device 10 of this embodiment includes a file storage unit 12 and a file output unit 11. The file storage unit 12 stores a file 14 corresponding to the product name 13. The file output unit 11 receives the individual number and product name, and for each product, the individual input from the sales record storage unit 22 that stores the sales record including the product name, purchaser name, and individual number of the product. The first sales record including the number and the second sales record including the input product name are searched. Thereafter, the file output unit 11 stores the file 14 corresponding to the input product name when the two sales records are obtained and the purchaser names 24 included in the two sales records match. Obtained from part 12 and output.

  The file providing server device 10 of the present embodiment can provide the file 14 only to the purchased user by using a copy of the sales slip. That is, the file providing server device 10 can reduce the burden for sales confirmation on the provider of the program / firmware and the like when providing the file 14 such as the program / firmware. The reason is that the file output unit 11 acquires the first and second sales records from the sales record storage unit 22 and confirms that the purchaser name 24 matches. The sales record storage unit 22 only needs to store a copy of the sales slip, and it is not necessary to prepare a special database.

  Although the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

10 File providing server device
11 File output section
12 File storage
13, 23 Product name
14 files
20 Sales history server device
21 Sales Management Department
22 Sales record storage
24 Buyer name
25, 51 Individual number
40 NM equipment
50 node equipment
60 File provision system

Claims (7)

File storage means for storing a file corresponding to the product name;
Enter individual number and product name,
For each product, from the sales record storage means for storing the sales record including the product name, purchaser name and individual number of the product, the first sales record including the input individual number and the input product name are included. Search for the second sales record,
A file for obtaining and outputting a file corresponding to the input product name from the file storage means when the two sales records are obtained and the purchaser names included in the two sales records match. And an output unit.   The file providing apparatus according to claim 1, wherein the file output unit encrypts the acquired file using the input individual number as a key. A sales history server device comprising the sales record storage means;
A file providing system including the file providing apparatus according to claim 1, which is connected to the sales history server apparatus. Memorize the file corresponding to the product name,
Enter individual number and product name,
For each product, from the sales record storage means for storing the sales record including the product name, purchaser name and individual number of the product, the first sales record including the input individual number and the input product name are included. Search for the second sales record,
A method for obtaining and outputting a file corresponding to the input product name from the file storage means when the two sales records are obtained and the purchaser names included in the two sales records match. .   The method according to claim 4, wherein the obtained file is encrypted using the input individual number as a key. Processing to store files corresponding to product names,
Enter individual number and product name,
For each product, from the sales record storage means for storing the sales record including the product name, purchaser name and individual number of the product, the first sales record including the input individual number and the input product name are included. Search for the second sales record,
Processing for obtaining and outputting a file corresponding to the input product name from the file storage means when the two sales records are obtained and the purchaser names included in the two sales records match. A program that causes a computer to execute.   The program according to claim 6, which causes a computer to execute a process of encrypting an acquired file using the input individual number as a key.

Images