Sales control system based on data erasure status

Abstract

To provide a system for preventing a commodity of which data has not been erased, from being sold.SOLUTION: A system equipped with at least one computer device includes commodity selling means which executes sale start processing to start selling a commodity based on erasure information on erasure of data stored in the commodity, or settlement processing for the commodity. The system equipped with at least one computer device includes availability output means which outputs, based on erasure information on erasure of data stored in a commodity, availability information as to whether the commodity can be sold or not, and / or the erasure information of the commodity.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a system and a method. [Background technology]

[0002] BACKGROUND ART Conventionally, so-called reuse sales have been carried out in which items such as personal computers, smartphones, and home appliances are purchased from users of the items and sold to other users.

[0003] If the product being sold for reuse is a device with a memory unit, such as a smartphone, tablet, personal computer, hard disk drive (HDD), or solid state drive (SSD), the data stored in the product's memory unit will be erased by the seller before the product is sold to another user.

[0004] Data can be erased using dedicated erasing software, but there is a risk that products with unerased data may be sold due to human error. Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to provide a system for preventing the sale of products whose data has not been erased. [Means for solving the problem]

[0006] The object of the present invention is to [1] A system including at least one computer device, the system including a product sales means for executing a sales start process for starting sales of a product or a payment process for the product based on erasure information regarding erasure of data stored in the product; [2] A system including at least one computer device, the system including a sales availability output means for outputting sales availability information regarding the sales availability of a product and / or sales availability information regarding the product, based on erasure information regarding the erasure of data stored in the product; [3] The system according to [1] or [2], further comprising: an erasure unit that erases data stored in the product; and an erased information storage unit that, when data is erased by the erasure unit, stores erased information associated with the product, indicating that the data stored in the product has been erased, wherein the erased information is an erasure flag indicating that the data has been erased, or an erasure history indicating that the data has been erased; [4] The system according to [3], further comprising a sales availability information storage means for storing sales availability information indicating that the product is available for sale when deleted information associated with the product is stored; [5] The system according to any one of [1] to [4], further comprising: an unerased information storage means for storing, when a product is purchased, unerased information associated with the product, which indicates that the data stored in the product has not been erased; [6] The system according to any one of [1] to [5] above, comprising: a disc ID acquisition means for acquiring a disc ID for identifying the storage unit of the product; a disc ID writing means for erasing data stored in the storage unit of the product and then storing the disc ID acquired by the disc ID acquisition means in the storage unit of the product as the disc ID of the storage unit of the product; and an erasure information storage means for storing erasure information of the product in association with the disc ID of the storage unit of the product; [7] The system according to any one of [1] and [3] to [6], further comprising a sales availability output means for outputting sales availability information regarding sales availability of the product and / or erasure information of the product based on erasure information regarding erasure of data stored in the product; [8] A method executed in a system including at least one computer device, the method comprising: a product sales step of performing a sales start process for starting sales of a product or a payment process for the product based on erasure information regarding erasure of data stored in the product; [9] A method executed in a system including at least one computer device, the method including a step of outputting sales availability information regarding whether or not a product is available for sale and / or erasure information regarding the product based on erasure information regarding the erasure of data stored in the product; This can be achieved by: [Effects of the Invention]

[0007] According to the present invention, it is possible to provide a system for preventing products from being sold that have not had their data erased. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a block diagram showing a configuration of a system according to an embodiment of the present invention; [Figure 2] 2 is a block diagram showing a hardware configuration of a store terminal according to an embodiment of the present invention; FIG. [Figure 3] FIG. 2 is a block diagram showing a hardware configuration of a seller server according to an embodiment of the present invention. [Figure 4] 10 is a flowchart of a first data erasure process according to an embodiment of the present invention. [Figure 5] 10 is a flowchart of a first erasure flag setting process according to an embodiment of the present invention. [Figure 6] 10 is a flowchart of a sale availability flag setting process according to an embodiment of the present invention. [Figure 7] 10 is a flowchart of a sales process according to an embodiment of the present invention. [Figure 8] 10 is a flowchart of a second erasure flag setting process according to an embodiment of the present invention. [Figure 9] 10 is a flowchart of a second data erasure process according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0009] The following describes embodiments of the present invention, but the present invention is not limited to the following embodiments as long as they do not violate the spirit of the present invention. The order of each process constituting the flowcharts described below is random as long as no contradictions or inconsistencies occur in the process content. Furthermore, it is possible to omit some of the processes constituting the flowcharts or add new processes to each process constituting the flowcharts as long as they do not violate the spirit of the present invention. Furthermore, the device that executes each process constituting the flowcharts can be changed to another device as long as it does not violate the spirit of the present invention. In this case, the process content can be changed so as not to cause contradictions or inconsistencies in the process content.

[0010] (First embodiment) An outline of a first embodiment of the present invention will be described below. In the first embodiment of the present invention, an example will be described in which devices that have been assigned a unique serial number or IMEI are purchased, the data is erased, and then the devices are sold for reuse.

[0011] [system] FIG. 1 is a block diagram showing the configuration of a system according to an embodiment of the present invention. The system 1 shown in FIG. 1 includes a store terminal 2, a seller server 3, and an EC server 4. The store terminal 2, seller server 3, and EC server 4 are communicatively connected to one another via a communication network 6. The store terminal 2, seller server 3, and EC server 4 are also communicatively connected to an erasure software server 5 via the communication network 6. In the system 1, any of the store terminal 2, seller server 3, EC server 4, and erasure software server 5 can function as an information processing device. When any of the store terminal 2, seller server 3, EC server 4, and erasure software server 5 functions as an information processing device, information is transmitted and received between the store terminal 2, seller server 3, EC server 4, and / or erasure software server 5 as necessary.

[0012] The store terminal 2 may be a terminal installed in a store that sells reused goods. The store may be a physical store that actually displays and sells products. The store terminal 2 stores information about the products sold in the store as a store database (store DB).

[0013] The number of store terminals 2 provided in the system 1 may be two or more. Furthermore, the number of store terminals 2 provided in one store may be two or more. The system 1 may be provided with a plurality of store terminals 2 provided in a plurality of stores. When the system 1 is provided with a plurality of store terminals 2 provided in a plurality of stores, the products stored in the store DB of each store may be different from each other, or at least some of the products may be the same.

[0014] The store terminal 2 may be operated by a store staff member (hereinafter also referred to as store staff member). The store staff member refers to a person who buys devices, registers products, sells products, etc. in the store.

[0015] The seller server 3 may be a server device managed by a seller who sells reused products. The seller server 3 stores information about products that the seller owns and / or manages for reused sales as a master database (master DB).

[0016] The EC server 4 may be a server device for selling reused products through electronic commerce. An EC site for selling reused products can be constructed using the EC server 4. The EC server 4 stores information about products sold on the EC site as an EC site database (EC site DB).

[0017] The registration of products on the EC site, the sale of products, etc. may be performed by EC site staff (hereinafter also referred to as EC site staff). The EC site staff may use a terminal (hereinafter also referred to as EC site staff terminal) to register products on the EC site, sell products, etc.

[0018] Among the products that a seller possesses and / or manages for reuse sales, information about products sold in stores is stored in a store DB, and information about products sold on an EC site is stored in an EC site DB. The products stored in the store DB and the products stored in the EC site DB may be different from each other, or at least some of the products may be the same.

[0019] The store and / or the e-commerce site may be managed by the seller who sells reused products, or at least a part of the store and / or the e-commerce site may be managed by a party other than the seller who sells reused products, such as a franchisee.

[0020] The erasing software server 5 may be a server device managed by an erasing software business that manufactures and / or sells erasing software. The erasing software server 5 may also be a server device managed by a business that provides a service for erasing data from devices using erasing software. The erasing software server 5 may store a history of data erasure using the erasing software (hereinafter also referred to as erasure history). The erasing software server 5 may also execute at least a part of the process of erasing data using the erasing software.

[0021] The seller server 3, the EC server 4, and the deletion software server 5 may each function in a distributed manner across multiple computer devices. For example, instead of a server device, a distributed ledger technology such as a blockchain may be used.

[0022] The system of the present invention may include at least one computer device. For example, the system may include a store terminal 2. Alternatively, for example, the system may include a seller server 3. Alternatively, for example, the system may include a store terminal 2 and a seller server 3. At least one of the store terminal 2, seller server 3, EC server 4, and erasure software server 5 may execute at least some of the functions of the other components. At least some of the processes described below may be executed by any of the computers included in the system.

[0023] 2 is a block diagram showing the hardware configuration of a store terminal according to an embodiment of the present invention. The store terminal 2 includes a control unit 21, a RAM 22, a storage unit 23, an input unit 24, a display unit 25, and a communication interface 26, all of which are connected via a bus.

[0024] The control unit 21 is composed of a CPU and a ROM. The control unit 21 executes programs stored in the storage unit 23 and controls the store terminal 2. The RAM 22 is a work area for the control unit 21. The storage unit 23 is a memory area for saving programs and data. In other words, the storage unit 23 functions as a recording medium that stores programs. The control unit 21 performs arithmetic processing based on the programs and data read from the RAM 22 and data input via the input unit 24.

[0025] The display unit 25 has a display screen. The control unit 21 outputs a video signal for displaying an image on the display screen according to the result of the arithmetic processing. Here, the display screen of the display unit 25 may be a touch panel equipped with a touch sensor. In this case, the touch panel functions as the input unit 24.

[0026] The communication interface 26 can be connected to the communication network 6 wirelessly or via a wire, and can transmit and receive data to and from other computer devices via the communication network 6. Data received via the communication interface 26 is loaded into the RAM 22, and the control unit 21 performs arithmetic processing on the data.

[0027] The store terminal 2 may be, for example, a POS (Point of Sale) terminal or a personal computer.

[0028] 3 is a block diagram showing the hardware configuration of a seller server according to an embodiment of the present invention. The seller server 3 includes at least a control unit 31, a RAM 32, a storage unit 33, and a communication interface 34, which are connected to each other via an internal bus.

[0029] The control unit 31 is composed of a CPU and a ROM, and executes programs stored in the storage unit 33 to control the seller server 3. The control unit 31 also has an internal timer that measures time. The RAM 32 is the work area of ​​the control unit 31. The storage unit 33 is a memory area for saving programs and data. In other words, the storage unit 33 functions as a recording medium that stores programs. The control unit 31 reads the programs and data from the RAM 32 and performs program execution processing based on information received from the store terminal 2, the EC server 4, and the erasure software server 5.

[0030] The program may also be stored in a recording medium such as a CD-ROM. In this case, the program stored in the recording medium may be installed in the store terminal 2, seller server 3, EC server 4, and / or erasure software server 5 to execute predetermined functions.

[0031] Alternatively, the program may be distributed from a computer device external to the system. In this case, the program distributed from the computer device external to the system may be installed in the store terminal 2, seller server 3, EC server 4, and / or erasure software server 5 to execute a predetermined function.

[0032] Regarding the hardware configuration of the EC server 4 and the erasure software server 5, the description of the hardware configuration of the seller server 3 may be adopted to the extent necessary.

[0033] An example will be described below in which the system 1 is used to erase data stored in equipment purchased from users and then sell the equipment for reuse.

[0034] The purchase of a device equipped with a storage unit may be carried out, for example, at a store. The type of device is not particularly limited. For example, the type of device may be a smartphone, a tablet terminal, a personal computer, a hard disk drive (HDD), a solid state drive (SSD), etc.

[0035] The store staff stores information about the purchased device in the master DB as product-related information. Hereinafter, storing product-related information in the database is also referred to as registering the product. The master DB may store information about the product, such as a management serial number, a manufacturing number or IMEI (International Mobile Equipment Identifier), a product name, a price, a date of receipt, and an inventory quantity, each associated with the other. The management serial number refers to an identifier unique to the product that the seller uses to manage the product. The management serial number may be assigned by the store staff, by system 1, or by a system different from system 1. The manufacturing number or IMEI refers to an identifier assigned to the device by the manufacturer that produced it. The store staff can store product-related information in the master DB by entering it into the store terminal 2 and sending it to the seller server 3.

[0036] Furthermore, the master DB may store information about erasure of data stored in the product (hereinafter also referred to as erasure information) as information about the product. The erasure information is not particularly limited as long as it is information about erasure of data. For example, the erasure information may be information indicated by an erasure flag or information indicated by an erasure history.

[0037] When erasure information is indicated by an erasure flag, the erasure flag indicates whether the data has been erased or not. Here, when the erasure flag is ON, it indicates that the data has been erased, and when the erasure flag is OFF, it indicates that the data has not been erased. In other words, when the erasure flag is ON, erased information indicating that the data has been erased is stored as the erasure information, and when the erasure flag is OFF, not erased information indicating that the data has not been erased is stored as the erasure information.

[0038] When erasure information is indicated by an erasure history, the erasure history may store the date and time when erasure was completed, the results of erasure, etc. For example, when the erasure history stores the date and time when erasure was completed and the results of erasure, etc., the erasure information may store erased information indicating that the data has been erased. Also, when the erasure history does not store the date and time when erasure was completed and the results of erasure, etc., the erasure information may store not-erased information indicating that the data has not been erased.

[0039] When storing information about the purchased device in the master DB, the data stored in the device does not need to be erased. In this case, non-erased information indicating that the data has not been erased may be stored as the erasure information.

[0040] After registering a product, the store staff may affix a sticker or the like on the product that displays a code (QR code (registered trademark), barcode, etc.) that can identify the product. By reading the code affixed to the product using the store terminal 2, it may be possible to confirm information that can identify the product, such as a management serial number, a manufacturing number, or an IMEI. The manufacturing number or IMEI may also be written in advance on a sticker or the like affixed to the exterior of the device.

[0041] The registered products may be sold in stores and / or e-commerce sites. The store selling the products may be the store that purchased the products, or may be a store different from the store that purchased the products.

[0042] When a product is sold in a store, the staff of the store who sells the product registers the product in the store by storing information about the product in the store DB of the store.

[0043] The types (items) of product information stored in the store DB may be the same as the types (items) of product information stored in the master DB, or at least some of them may be different. The store DB may store information about products, such as a management serial number, a manufacturing number or an IMEI (International Mobile Equipment Identifier), a product name, a price, a stocking date, and a quantity in stock, each associated with the other. A store staff member may input a request to send product information to the store terminal 2. The store terminal 2 may send a request to send product information to the seller server 3 and receive at least some of the product information stored in the master DB from the seller server 3, thereby storing product information in the store DB. It is preferable that information of types (items) common to the store DB and the master DB be processed so that the contents are synchronized at a predetermined time interval.

[0044] Furthermore, the store DB may store information about whether or not a product is available for sale (hereinafter also referred to as sales availability information) as information about the product. The sales availability information is not particularly limited as long as it is information about whether or not a product is available for sale. For example, the sales availability information may be information indicated by a sales availability flag.

[0045] When the sales availability information is indicated by a sales availability flag, the sales availability flag indicates whether the product is available for sale or not. Here, when the sales availability flag is ON, it indicates that the product is available for sale, and when the sales availability flag is OFF, it indicates that the product is not available for sale. In other words, when the sales availability flag is ON, sales availability information indicating that the product is available for sale is stored as the sales availability information, and when the sales availability flag is OFF, sales unavailability information indicating that the product is not available for sale is stored as the sales availability information.

[0046] Furthermore, the store DB may store information about the sales status of the product (hereinafter also referred to as sales status information) as information about the product. The sales status information may be any information about the sales status of the product, and is not particularly limited. For example, the sales status information may be information indicated by a sales flag.

[0047] When sales status information is indicated by a sales flag, the sales flag indicates whether the product is on sale or not. Here, when the sales flag is ON, it indicates that the product is on sale, and when the sales flag is OFF, it indicates that the product is not on sale. In other words, when the sales flag is ON, on-sale information indicating that the product is on sale is stored as sales status information, and when the sales availability flag is OFF, unsold information indicating that the product is not on sale is stored as sales status information.

[0048] When a product is registered in the store DB, the product may not be available for sale and sales may not have started. In this case, unsaleable information indicating that the product is not available for sale may be stored as the sales availability information, and unsold information indicating that the product is not being sold may be stored as the sales status information.

[0049] When a product is sold on an e-commerce site, the staff of the e-commerce site selling the product registers the product on the e-commerce site by storing information about the product in the e-commerce site database of the e-commerce site. The product information stored in the e-commerce site database may use the above-mentioned product information stored in the store database to the extent necessary. The e-commerce site database may store information about the product, such as sales availability information and sales status information.

[0050] Although the above describes an example in which a product is registered in the master DB and then in the store DB and / or EC site DB, the order in which the product is registered is not particularly limited and can be designed as appropriate. For example, the product may be registered in the store DB and / or EC site DB and then in the master DB.

[0051] In addition, although an example will be described here in which the purchased device is registered as a commodity and then the data stored in the commodity is erased, the order of registering the commodity and erasing the data is not particularly limited and can be designed as appropriate. For example, the purchased device may be registered as a commodity after the data stored in the device is erased.

[0052] If the store is able to erase data stored in the purchased device, the data may be erased by a first data erasure process as described below. In this case, a dedicated application for using the erasure software may be installed in the store terminal 2. If the erasure software can be used on a browser, the store terminal 2 does not need to have a dedicated application for using the erasure software installed.

[0053] [First data erasure process] 4 is a flowchart of a first data erasure process according to an embodiment of the present invention. First, a store staff member connects the store terminal 2 to a device from which data is to be erased (hereinafter also referred to as a target device) (step S101). The store terminal 2 accepts an input of a request to erase data stored in the connected device (hereinafter also referred to as an erasure request) (step S102). The store terminal 2 erases the data stored in the connected device in accordance with the erasure request (step S103). The store terminal 2 transmits erasure information regarding the data erasure to the erasure software server 5 (step S104). The erasure software server 5 receives the transmitted erasure information (step S105). The erasure software server 5 stores the received erasure information (step S106), and the first data erasure process ends.

[0054] In step S101, the manner in which the store terminal 2 and the target device are connected is not particularly limited and can be designed as appropriate. The store terminal 2 and the target device may be connected in a manner that allows the process of erasing data from the target device to be executed. The store terminal 2 and the target device may be connected by wire or wirelessly.

[0055] When the store terminal 2 and the target device are connected, information about the target device can be output from the store terminal 2. Information about the target device includes, for example, the serial number or IMEI of the target device, and data stored in the memory of the target device. For example, the store staff can display the data stored in the memory of the target device on erasure software and select the data to be erased. The store staff may input the erasure request in step S102 by selecting the data to be erased and pressing a button or the like for erasing the selected data.

[0056] In step S102, along with the erasure request, input of information that can identify the data to be erased may be accepted.

[0057] The method of erasing data in step S103 is not particularly limited and can be designed as appropriate. Examples of the data erasure method include the zero write method, random write method, NIST 800-88 method, random & zero write method, NIST 800-88 Advanced method, the current NSA method (random random zero), the U.S. Department of Defense compliant method DoD5200.28-M, the U.S. Air Force method AFSSI5020, the U.S. Department of Defense compliant method DoD5220.22-M, the U.S. Navy method NAVSO P-5239-26-MFM, the U.S. Navy method NAVSO P-5239-26-RLL, the former NSA method Bit Toggle, the German standard VSITR, the Gutmann recommended method, the Secure Erase method, and the Extended Secure Erase method. In step S103, it is sufficient that the data to be erased is erased.

[0058] The erasure information in step S104 is not particularly limited and can be designed as appropriate. The erasure information includes, for example, the serial number or IMEI of the target device, the management serial number, the date and time when the erasure request was received, the date and time when data erasure was completed, and the erasure result. The erasure result may indicate that all of the data to be erased has been erased, that only a portion of the data to be erased has been erased, or that not all of the data to be erased has been erased. The erasure result may also include information that enables identification of the erased data and / or the data that was not erased.

[0059] In step S106, the erasure information may be stored in a storage unit of the erasure software server 5. The erasure software server 5 may store the erasure information as an erasure history. For example, the erasure software server 5 may store, as the erasure history, the serial number or IMEI of the device from which the data was erased, the management serial number, the date and time when the erasure request was received, the date and time when the data erasure was completed, the erasure result, and the like, in association with one another. The erasure history stored in the erasure software server 5 may be displayable on the store terminal 2, etc.

[0060] Furthermore, although not shown, the erasure information may be stored in the storage unit 22 of the store terminal 2. The timing of transmitting the erasure information from the store terminal 2 to the erasure software server 5 is not particularly limited and can be designed as appropriate. For example, as described above, the erasure information may be transmitted to the erasure software server 5 when the erasure of data from the target device is completed. Alternatively, for example, when the erasure of data from the target device is completed, the erasure information may be stored in the storage unit 22 of the store terminal 2, and the stored erasure information may be transmitted to the erasure software server 5 at a predetermined timing or frequency. The predetermined timing is not particularly limited and can be designed as appropriate. The predetermined timing may be, for example, when a predetermined time is reached, when a predetermined number of erasure information pieces have been stored in the store terminal 2, or when an input for transmitting the erasure information is received. The predetermined frequency may also be once every 1 / 30 seconds, once per minute, once per hour, or once per day. When erasure information stored in the store terminal 2 is sent to the erasure software server 5 at a predetermined timing or frequency, erasure information that has not yet been sent to the erasure software server 5 may also be sent to the erasure software server 5.

[0061] The store staff may attach a sticker or the like to the product after the data has been erased to indicate that the data has been erased.

[0062] Furthermore, if the purchased device is a device with an OS pre-installed, such as a personal computer, the store staff may convert the OS image into an image file and store it in the store terminal 2 before erasing the data, and after erasing the data, expand the image file to restore the OS image.

[0063] Note that if the data stored in the device is not erased at the store, steps S101 to S104 do not have to be executed. For example, if the device is sent to an establishment of a business that provides a service to erase data from devices using erasure software, and the data is erased at that establishment, steps S101 to S104 may be executed on a business terminal operated by the business. The erasure software server 5 can receive and store the erasure information sent from the business terminal.

[0064] Furthermore, erasure information regarding data erasure does not need to be stored in the erasure software server 5. For example, if erasure software is installed in the store terminal 2 and erases data and stores erasure information without accessing the erasure software server 5, the erasure information may be stored in the store terminal 2.

[0065] That is, after the device is purchased, the data on the device is erased and the erasure information is stored in one of the computers. The computer that stores the erasure information may be, for example, the erasure software server 5, the store terminal 2, or the seller server 3. The erasure information stored in one of the computers may be referenced and the following processing may be performed.

[0066] The erasure information stored in the erasure software server 5 may be reflected in the master DB stored in the seller server 3 by the following first erasure flag setting process.

[0067] [First erasure flag setting process] 5 is a flowchart of the first erasure flag setting process according to an embodiment of the present invention. The seller server 3 sends a request to the erasure software server 5 to refer to the erasure information of the product (hereinafter also referred to as the erasure information reference request) (step S201). The erasure software server 5 receives the sent erasure information reference request (step S202). The erasure software server 5 sends the erasure information to the seller server 3 (step S203). The seller server 3 receives the sent erasure information (step S204). The seller server 3 determines whether the data stored in the product has been erased (step S205).

[0068] If it is determined that the data has been erased (YES in step S205), the erasure flag for the product stored in the master DB is set to ON (step S206), and the first erasure flag setting process ends.

[0069] If it is not determined that the data has been erased (NO in step S205), step S206 is not executed, and the first erase flag setting process ends.

[0070] Step S201 may be executed at a predetermined timing or frequency. The predetermined timing may be, for example, when a predetermined time arrives, when the number of products whose deletion flags are OFF in the master DB reaches a predetermined number, or when a seller terminal operated by a seller receives an input for sending a deletion information reference request. The predetermined frequency may be once every 1 / 30 seconds, once per minute, once per hour, or once per day.

[0071] In step S201, the product that is the subject of the erasure information reference request is not particularly limited and can be designed as appropriate. The product that is the subject of the erasure information reference request may, for example, be all or part of a product whose erasure flag is OFF, or may be all or part of a product regardless of the state of the erasure flag. In step S201, information that can identify the product that is the subject of the erasure information reference request may be transmitted together with the erasure information reference request. The information that can identify the product that is the subject of the erasure information reference request may be, for example, a serial number or IMEI, or a management serial number. When the seller determines the product that is the subject of the erasure information reference request, information that can identify the product that is the subject of the erasure information reference request may be input to the seller terminal.

[0072] In step S203, erasure information for the product that is the subject of the erasure information reference request is transmitted. The erasure information transmitted here may be part or all of the erasure information stored in the erasure software server 5, or may be information indicating at least part of the erasure information stored in the erasure software server 5. The information indicating at least part of the erasure information stored in the erasure software server 5 may be, for example, information indicating whether data stored in the product that is the subject of the erasure information reference request has been erased. The information indicating whether data has been erased may be, for example, the erasure result, the date and time when erasure was completed, or information indicating that data has not been erased.

[0073] In step S205, the seller server 3 determines whether the data stored in the product has been erased based on the erasure information received in step S204. If the received erasure information includes information indicating that the data stored in the product has been erased, the seller server 3 may determine that the data has been erased. The information indicating that the data stored in the product has been erased may be, for example, the erasure result or the date and time when the erasure was completed.

[0074] In step S206, the seller server 3 sets the deletion flag stored in association with the product for which it has determined that data has been deleted to ON. The deletion flag being ON indicates that the data has been deleted. Therefore, when data stored in a product is deleted, it is possible to store, in association with the product, deleted information indicating that the data stored in the product has been deleted.

[0075] Although the above describes a mode in which erased information is stored using an erasure flag, erased information may also be stored using an erasure history. For example, in step S203, some or all of the erasure information stored in the erasure software server 5 may be transmitted to the seller server 3, and in step S206, the seller server 3 may associate some or all of the received erasure information with the product for which it has determined that data has been erased, and store that information as an erasure history. The erasure information stored here may specifically be, for example, the erasure result or the date and time when erasure was completed. Erasure information such as the erasure result and the date and time when erasure was completed can be considered to correspond to an erasure history indicating that data has been erased.

[0076] If the data stored in a product is deleted, it is possible to sell the product in a store and / or on an EC site, and therefore the product can be sold. Therefore, the sales availability information stored in the store DB and / or EC server DB may be updated by the following sales availability flag setting process.

[0077] [Sales availability flag setting process] 6 is a flowchart of the sales flag setting process according to the embodiment of the present invention. Here, the sales flag setting process is executed in the store terminal 2 and the seller server 3.

[0078] First, the store terminal 2 transmits a request to the seller server 3 to refer to information related to the deletion flag (hereinafter also referred to as a deletion flag reference request) (step S301). The seller server 3 receives the transmitted deletion flag reference request (step S302). The seller server 3 transmits information related to the deletion flag (hereinafter also referred to as deletion flag information) to the seller server 3 (step S303). The store terminal 2 receives the transmitted deletion flag information (step S304). The store terminal 2 determines whether the deletion flag is ON (step S305).

[0079] If it is determined that the deletion flag is ON (YES in step S305), the store terminal 2 sets the sales flag of the product stored in the store DB to ON (step S306), and the sales flag setting process ends.

[0080] If it is not determined that the deletion flag is ON (NO in step S305), step S306 is not executed, and the sale availability flag setting process ends.

[0081] When the sales availability flag setting process is executed by the EC server 4 and the seller server 3, step S301 and steps S304 to S306 can be executed by the EC server 4. In this case, in step S306, the EC server 4 can set the sales availability flag of the product stored in the EC server DB to ON.

[0082] Step S301 may be executed at a predetermined timing or frequency. The predetermined timing may be, for example, when a predetermined time is reached, when the number of products in the store DB whose sales availability flags are OFF reaches a predetermined number, or when an input for transmitting a deletion flag reference request is received. Furthermore, the predetermined frequency may be once every 1 / 30 seconds, once per minute, once per hour, or once per day. If, in addition to erasing data, a condition for updating sales availability information requires checking the condition of the product for defects or whether the product is functioning properly, step S301 may be executed when an input for transmitting a deletion flag reference request is received.

[0083] In step S301, the product that is the target of the erasure flag reference request is not particularly limited and can be designed as appropriate. The product that is the target of the erasure flag reference request may be, for example, some or all of the products whose sales availability flags are OFF, or some or all of the products regardless of the state of the sales availability flag. In step S301, information that can identify the product that is the target of the erasure flag reference request may be transmitted together with the erasure flag reference request. The information that can identify the product that is the target of the erasure flag reference request may be, for example, a manufacturing number or IMEI, or a management serial number. Alternatively, a store staff member may identify the product that is the target of the erasure information reference request and input it into the store terminal 2.

[0084] In step S303, erasure flag information of the product that is the target of the erasure flag reference request is transmitted. The erasure flag information transmitted here may be information indicating whether the erasure flag is ON or OFF.

[0085] In step S305, the store terminal 2 determines whether the deletion flag is ON or not based on the deletion flag information received in step S304.

[0086] In step S306, the store terminal 2 sets the sales availability flag stored in association with the product for which it has determined that the deletion flag is ON to ON. The sales availability flag being ON indicates that the product is available for sale. Therefore, when deleted information is stored in association with a product, sales availability information indicating that the product is available for sale can be stored.

[0087] Although the above describes an aspect in which the sales availability information is updated based on the deletion flag stored in the master DB, the sales availability information may also be updated based on other deletion information. For example, the sales availability information may be updated based on the deletion history stored in the master DB. In this case, the seller server 3 may transmit at least a portion of the deletion history or information indicating at least a portion of the deletion history to the store terminal 2 as the deletion information. If the received deletion information includes information indicating that the data stored in the product has been deleted, the store terminal 2 may set the sales availability flag to ON.

[0088] Although the above describes a mode in which the sales availability information is stored using a sales availability flag, the sales availability information may be stored using a method other than the sales availability flag. The specific mode is not particularly limited, and it is sufficient if the system 1 can store sales availability information indicating that the product is available for sale when deleted information associated with the product is stored.

[0089] When the sales availability information is stored in association with a product, the product may be sold in a store and / or an EC site. When selling a product, for example, the following sales process may be executed.

[0090] [Sales Processing] 7 is a flowchart of a sales process according to an embodiment of the present invention. Here, an aspect in which the sales process is executed in the store terminal 2 will be described.

[0091] First, the store terminal 2 receives an input of a request to execute a sales start process to start selling a product (hereinafter also referred to as a request to execute the sales start process) (step S401). The store terminal 2 determines whether the sales availability flag of the product that is the subject of the request to execute the sales start process is ON (step S402).

[0092] If it is determined that the sales availability flag is ON (YES in step S402), the store terminal 2 executes a sales start process for the product (step S403), and the sales process ends.

[0093] If it is not determined that the sales availability flag is ON (NO in step S402), the store terminal 2 outputs an error (step S404), and the sales process ends.

[0094] When starting to sell products on the EC site, the sales process may be executed by the EC site staff terminal and the EC server 4. For example, steps S401 and S404 may be executed by the EC site staff terminal, and steps S402 to S403 may be executed by the EC server 4.

[0095] In step S401, the method for inputting the request to execute the sales start process into the store terminal 2 is not particularly limited and can be designed as appropriate. For example, a store staff member may input the request to execute the sales start process by reading a code (QR code (registered trademark), barcode, etc.) attached to a product and pressing a button or the like for registering the product as a product for sale. In step S401, it is sufficient that the request to execute the sales start process can be input in accordance with the specifications of the sales system installed in the store. In step S401, information capable of identifying the product that is the subject of the request to execute the sales start process may also be input.

[0096] In step S402, it is determined whether the sales availability flag stored in association with the product that is the subject of the execution request input in step S401 is ON.

[0097] If the sales availability flag is ON, that is, if sales availability information indicating that the product is available for sale is stored, sales start processing is executed in step S403. That is, in the system 1, sales start processing is executed to start selling the product based on the sales availability information regarding whether the product is available for sale.

[0098] Furthermore, since the fact that the sale flag is ON also means that the deletion flag is ON, it can be said that if erased information indicating that the data stored in the product has been erased is stored, the sales start process is executed in step S403. In other words, in the system 1, the sales start process for starting the sale of the product is executed based on the erasure information regarding the erasure of the data stored in the product.

[0099] The content of the sales start processing in step S403 is not particularly limited and can be designed as appropriate. The content of the sales start processing may be, for example, a process of storing information indicating that the product is on sale in a store DB, or a process of displaying information indicating that the product is on sale on an electronic shelf label or the like in the store. In step S403, it is sufficient if the sales start processing can be executed in accordance with the specifications of the sales system installed in the store.

[0100] When starting sales of a product on an EC site, the content of the sales start process may be, for example, a process of storing information indicating that the product is on sale in the EC server DB, or a process of displaying information indicating that the product is on sale on the EC site. In step S403, it is sufficient that the sales start process can be executed in accordance with the specifications of the sales system installed on the EC site.

[0101] Furthermore, when the sales start process in step S403 is executed, the sales status information stored in the store DB and / or the EC server DB may be updated. For example, a sales flag stored in association with the product that has been the subject of the sales start process may be set to ON.

[0102] The manner in which the error is output in step S404 is not particularly limited and can be designed as appropriate. For example, the error may be displayed on the display screen of the store terminal 2, or may be output as sound from the speaker of the store terminal 2.

[0103] When the sale of the product begins on the EC site, for example, the error may be displayed on the display screen of the EC site staff terminal, or may be output as audio from the speaker of the EC site staff terminal.

[0104] The content of the error is not particularly limited and can be designed as appropriate. For example, the content of the error may be a content indicating that the product cannot be sold, or a content indicating that the data stored in the product has not been erased.

[0105] The case where it is not determined that the sales availability flag is ON may be the case where the sales availability flag is OFF. In other words, if sales availability information indicating that the product cannot be sold is stored, it can be said that sales availability information indicating that the product cannot be sold and / or non-erased information indicating that the data has not been erased is output in step S404. In other words, in system 1, sales availability information regarding the sale availability of the product and / or erasure information of the product are output based on sales availability information regarding the sale availability of the product.

[0106] Furthermore, since the fact that the sale flag is OFF means that the erasure flag is also OFF, if non-erasure information indicating that the data stored in the product has not been erased is stored, it can be said that non-sale information indicating that the product cannot be sold and / or non-erasure information indicating that the data has not been erased is output in step S404. In other words, in system 1, sale information regarding the sale of the product and / or erasure information for the product is output based on erasure information regarding the erasure of the data stored in the product.

[0107] Although not shown, if it is determined in step S402 that the sales availability flag is ON, that is, if the deletion flag is ON, sales availability information indicating that the product is available for sale and / or deleted information indicating that the data stored in the product has been deleted may be output before or simultaneously with the execution of step S403.

[0108] Furthermore, although the above describes an embodiment in which the sales start process is not executed if it is not determined that the sales availability flag is ON, the system 1 may be configured to execute the sales start process, for example, through operational input by a store staff member, even if it is not determined that the sales availability flag is ON. For example, based on the result of the determination of the sales availability information in step S402, sales availability information regarding whether or not the product can be sold and / or product deletion information may be output, and then an input regarding whether or not to execute the sales start process may be accepted. By outputting sales availability information regarding whether or not the product can be sold and / or product deletion information, the store staff can recognize that the data stored in the product has not been erased and / or that the product cannot be sold, and therefore can determine that it is better not to execute the sales start process.

[0109] Furthermore, although the above describes an aspect in which the sales availability information is referenced when starting sales of a product, the sales availability information may also be referenced when making payment for the product. In this case, in step S401 of the above-mentioned sales processing, input of a request to execute payment processing may be accepted, and if it is determined in step S402 that the sales availability flag is ON, the payment processing may be executed in step S403. In other words, the system 1 may execute payment processing for the product based on sales availability information regarding the sale of the product. Furthermore, since the sales availability information for the product is based on deletion information for the product, the system 1 may execute payment processing for the product based on deletion information regarding the deletion of data stored in the product.

[0110] Furthermore, in the above, we have described an aspect in which, when starting to sell a product, sales availability information regarding whether or not the product can be sold and / or erasure information for the product is output based on erasure information regarding the erasure of data stored in the product. However, when making payment for the product, sales availability information regarding whether or not the product can be sold and / or erasure information for the product may also be output based on erasure information regarding the erasure of data stored in the product.

[0111] Although the above describes an embodiment in which the sales availability information is updated based on the deletion information, and the sales start process or the settlement process is executed based on the sales availability information, and the sales availability information and / or the deletion information is output, the sales start process or the settlement process may be executed, and the sales availability information and / or the deletion information may be output, based on the deletion information. In this case, for example, the deletion information may be stored in the store terminal 2 and / or the EC server 4, and the sales start process or the settlement process may be executed, and the sales availability information and / or the deletion information may be output, based on the deletion information stored in the store terminal 2 and / or the EC server 4. Alternatively, for example, the sales start process or the settlement process may be executed, and the sales availability information and / or the deletion information may be output, based on the deletion information by referencing the deletion information stored in the seller server 3.

[0112] In addition to erasing data, when selling a product, if certain conditions must be met, such as the state of defects on the product and whether the product operates normally, it is considered preferable to execute the sales start process or settlement process based on the sales availability information, or to output the sales availability information and / or erasure information. The system configuration, processing content, etc. can be designed appropriately based on the circumstances of the seller.

[0113] When a product that has been put on sale is purchased by another user, the data is likely to be stored again in the storage unit of the product. Therefore, when the product is purchased, the following second deletion flag setting process may be performed.

[0114] [Second erasure flag setting process] 8 is a flowchart of the second deletion flag setting process according to the embodiment of the present invention, in which a case where a product is purchased in a store will be described.

[0115] First, the store terminal 2 executes payment processing for the product (step S501). The store terminal 2 sets the sales availability flag stored in association with the product in the store DB to OFF (step S502). The store terminal 2 transmits information regarding the purchase of the product (hereinafter also referred to as purchase information) to the seller server 3 (step S503). The seller server 3 receives the transmitted purchase information (step S504). The seller server 3 sets the deletion flag stored in association with the product in the master DB to OFF (step S505), and the second deletion flag setting process ends.

[0116] When a product is purchased on an EC site, steps S501 to S503 may be executed by the EC site server 4.

[0117] The payment process in step S501 may be executed by, for example, a store staff member reading a code (QR code (registered trademark), barcode, etc.) attached to the product and inputting a request to execute the payment process into the store terminal 2.

[0118] The payment method is not particularly limited and can be designed as appropriate. Payment may be made by cash, credit card, or electronic money. Store staff can input the information required for payment processing into the store terminal 2.

[0119] In step S502, the sales availability information stored in association with the product that was the subject of the payment process in step S501 is updated. At this time, the sales status information stored in association with the product may also be updated. For example, the store terminal 2 may set the sales flag stored in association with the product to OFF. If the same product is sold both in the store and on the EC site, it is preferable to similarly update the sales availability information and / or sales status information stored in association with the product in the EC site DB.

[0120] The purchase information in step S503 is not particularly limited and can be designed as appropriate. For example, the purchase information may include information capable of identifying the product that was the subject of the payment process, the date and time of the payment process, the sales price, information capable of identifying the store that sold the product, information capable of identifying the store staff that sold the product, etc. Information capable of identifying the product may be, for example, a management serial number.

[0121] In step S505, the erasure information stored in association with the product corresponding to the purchase information received in step S504, i.e., the product that was the subject of the payment process, is updated. Since the erasure flag being OFF indicates that the data has not been erased, when a product is purchased, non-erasure information indicating that the data stored in the product has not been erased is stored in association with the product.

[0122] In step S505, the deletion flag stored in the master DB is set to OFF, so that even if the purchaser returns or trades in the product after purchase, the product cannot be sold unless the data for the product is deleted again.

[0123] In this way, a system having at least one computer device can be provided that is equipped with a product sales means that executes a sales start process to start selling the product or a payment process for the product based on erasure information regarding the erasure of data stored in the product, thereby preventing the sale of products whose data has not been erased.

[0124] Furthermore, by providing a system having at least one computer device with a means for outputting sales eligibility information regarding whether or not a product can be sold and / or erasure information regarding the product based on erasure information regarding the erasure of data stored in the product, it is possible to provide a system for preventing products from being sold if their data has not been erased.

[0125] Furthermore, in this way, the system is provided with an erasure means for erasing data stored in a product, and an erased information storage means for storing erased information indicating that the data stored in the product has been erased, in association with the product, when data has been erased by the erasure means; the erased information is an erasure flag indicating that data has been erased, or an erasure history indicating that data has been erased, so that when data is erased by the system, information indicating that the data has been erased can be stored using the erasure flag or erasure history.

[0126] Furthermore, when the system has stored erased information associated with a product, it is possible to store information indicating that the product is available for sale by providing a sales availability information storage means for storing sales availability information indicating that the product is available for sale when data on the product has been erased.

[0127] Furthermore, by providing the system with an unerased information storage means that stores unerased information indicating that the data stored in the product has not been erased in association with the product when the product is purchased, it becomes possible to prevent a product that has been purchased once from being sold again without the data being erased.

[0128] (Second embodiment) An overview of a second embodiment of the present invention will be described. A purchased device may not be assigned a unique serial number or IMEI by the manufacturer. On the other hand, a device equipped with a storage unit can store a disk ID for identifying a disk, called a disk signature, in the storage unit. A disk signature is an identifier that can be read even if the connected device is changed. In the second embodiment of the present invention, an example will be described in which product erasure information is managed by linking a disk signature with a management serial number.

[0129] [system] In the second embodiment, the system configuration described in the first embodiment can be adopted to the extent necessary.

[0130] Regarding the manner in which a device having a storage unit is purchased and the product is registered, the contents described in the first embodiment can be adopted to the extent necessary.

[0131] If the store is able to erase data stored in the purchased device, the data may be erased by the following second data erasure process. In this case, a dedicated application for using the erasure software may be installed in the store terminal 2. If the erasure software can be used on a browser, the store terminal 2 does not need to have a dedicated application for using the erasure software installed.

[0132] [Second data erasure process] 9 is a flowchart of a second data erasure process according to an embodiment of the present invention. First, a store staff member connects the store terminal 2 to a target device from which data is to be erased (step S601). The store terminal 2 creates an image file of the OS (Operating System) image of the target device (step S602). Next, the store terminal 2 determines whether the target device has a disk signature (step S603).

[0133] In step S601, the manner in which the store terminal 2 and the target device are connected may be the same as that described in the first embodiment, as long as necessary. By connecting the store terminal 2 and the target device, information about the target device may be output from the store terminal 2.

[0134] If the target device is a device with an OS pre-installed, such as a personal computer, in step S602, the OS image is made into an image file and stored in the store terminal 2, so that the data on the target device can be erased and the OS restored before being sold for reuse. Before making the image file in step S602, the target device may be recovered (initialized) using a recovery function to return it to its factory default state.

[0135] If the target device is a device such as a HDD on which an OS is not pre-installed, step S602 does not need to be executed.

[0136] In step S603, the store terminal 2 may determine whether the target device has a disk signature based on whether it can detect that a disk signature is stored in the memory unit of the target device. If it can detect that a disk signature is stored in the memory unit of the target device, the store terminal 2 may determine that the target device has a disk signature.

[0137] In step S603, if it is determined that the target device has a disk signature (YES in step S603), the store terminal 2 obtains the disk signature of the target device by reading the disk signature stored in the memory unit of the target device (step S605).

[0138] On the other hand, if it is not determined in step S603 that the target device has a disk signature (NO in step S603), the store terminal 2 generates a disk signature to be assigned to the target device (step S604) and acquires the disk signature of the target device (step S605). In step S604, the store terminal 2 can generate the disk signature by combining any characters, numbers, symbols, etc. The generated disk signature may be assigned to the target device by being stored in a memory unit of the target device.

[0139] Furthermore, before assigning a disk signature to the target device, the store terminal 2 may initialize the target device. The format of the initialization is not particularly limited. For example, the initialization may be performed in a GPT (GUID Partition Table) format or an MBR (Master Boot Record) format.

[0140] As mentioned above, the disc signature functions as a disc ID, so the system can obtain the disc ID in step S605.

[0141] The store terminal 2 transmits the disk signature acquired in step S605 to the erasure software server 5 (step S606). The erasure software server 5 receives the transmitted disk signature (step S607) and stores it in the storage unit (step S608).

[0142] In step S608, the erasure software server 5 may store the disk signature as part of the erasure history. After erasing the data of the target device, the erasure software server 5 can store the erasure information of the target device as the erasure history in association with the disk signature stored in advance.

[0143] In step S606, other information that can identify the target device, such as the serial number or IMEI of the target device, management serial number, etc., may be transmitted together with the disk signature. In step S608, the erasure software server 5 may store other information that can identify the target device in association with the disk signature.

[0144] On the other hand, after step S606, the store terminal 2 accepts input of a request to erase data stored in the connected device (step S609). The store terminal 2 erases the data stored in the connected device in accordance with the erasure request (step S610). The store terminal 2 transmits erasure information regarding the data erasure to the erasure software server 5 (step S611). The erasure software server 5 receives the transmitted erasure information (step S612). The erasure software server 5 stores the received erasure information in association with the disc signature stored in step S608 (step S613).

[0145] Regarding the reception of an input of an erasure request, the erasure of data, and the erasure information, the contents described in the first embodiment can be adopted to the extent necessary.

[0146] When the data is deleted in step S610, the disk signature stored in the memory unit of the target device is also deleted.

[0147] The erasure information stored in step S613 may include, for example, the disk signature of the target device, the serial number or IMEI, the management serial number, the date and time when the input of the erasure request was accepted, the date and time when the data erasure was completed, the erasure result, etc. In other words, the erasure software server 5 may store the disk signature of the target device, the serial number or IMEI, the management serial number, the date and time when the input of the erasure request was accepted, the date and time when the data erasure was completed, the erasure result, etc. in association with each other as erasure information.

[0148] If a single product has multiple storage units, and a single disk signature is stored in each storage unit, the erasure history may store erasure information associated with each disk signature. Alternatively, erasure information corresponding to a single disk signature may be stored associated with a single management serial number.

[0149] The erasure software server 5 transmits the disk signature stored in association with the erasure information stored in step S613 to the store terminal 2 (step S614). The store terminal 2 receives the transmitted disk signature (step S615). The store terminal 2 writes the received disk signature by storing it in the memory unit of the connected device (step S616). Next, the store terminal 2 unpacks the image file and restores the OS image (step S617), and the second data erasure process ends.

[0150] In step S616, the store terminal 2 stores the disc signature in the storage unit of the target device as the disc signature (disc ID) of the storage unit of the device.

[0151] If the target device is a personal computer or the like, the original disk signature (the disk signature detected in step S603) is stored in the storage unit and automatically written back when the OS image is restored in step S617, so step S616 does not need to be executed. By obtaining the disk signature of the target device in advance and storing it in the erasure history, it is possible to easily link the disk signature of the device after the OS image has been restored to the erasure history based on the disk signature.

[0152] Also, if the target device is a HDD or the like, it is not necessary to restore the OS image in step S617.

[0153] The store staff may attach a sticker or the like indicating that the data has been erased to the product after the data erasure has been completed. Also, a sticker or the like bearing a disk signature may be attached to the product. The disk signature may be able to be confirmed by reading a code attached to the product.

[0154] Furthermore, the store staff may register the disk signature as information about the product in the master DB, the store DB, and / or the EC site DB. If one product has multiple storage units, multiple disk signatures may be registered as information about one product. In this case, one management serial number and multiple disk signatures are stored in association with each other.

[0155] [First erasure flag setting process] The erasure information stored in the erasure software server 5 may be reflected in the master DB stored in the seller server 3 by a first erasure flag setting process.

[0156] In step S201 of the first erasure flag setting process, erasure information may be referenced based on the disk signature, the serial number or IMEI, and / or the management serial number. In this case, in step S203, the erasure software server 5 can transmit the erasure information stored in association with the disk signature, the serial number or IMEI, and / or the management serial number transmitted together with the erasure information reference request.

[0157] In addition, if multiple disk signatures are registered as information about one product, in step S206 of the first erasure flag setting process, one piece of erased information may be stored in association with one product, or each piece of erased information may be stored in association with each disk signature.

[0158] Additionally, for the first erasure flag setting process, the contents described in the first embodiment can be adopted to the extent necessary.

[0159] [Sales availability flag setting process] After the data stored in the product is deleted, the sales availability information stored in the store DB and / or EC server DB may be updated by a sales availability flag setting process.

[0160] In step S301 of the sale flag setting process, erasure flag information may be referenced based on the disk signature, the serial number or IMEI, and / or the management serial number. In this case, in step S303, the seller server 3 can transmit the erasure flag information stored in association with the disk signature, the serial number or IMEI, and / or the management serial number transmitted together with the erasure flag reference request.

[0161] When multiple disk signatures are registered as information related to one product and erasure flag information is stored in association with each disk signature, the erasure flag information may be referenced for all disk signatures stored in association with one product. When erased information is stored in association with all disk signatures stored in association with one product, sale availability information may be stored in association with one product in step S306 of the sale availability flag setting process.

[0162] Additionally, for the first erasure flag setting process, the contents described in the first embodiment can be adopted to the extent necessary.

[0163] [Sales Processing] The product for which the sales availability information is stored may be sold in a store and / or an e-commerce site. When selling the product, a sales process may be executed. The sales process may employ the content described in the first embodiment to the extent necessary.

[0164] [Second erasure flag setting process] If a product that was on sale is purchased, a second deletion flag setting process may be performed.

[0165] In addition, when multiple disk signatures are registered as information about one product and erasure flag information is stored in association with each disk signature, in step S505 of the second erasure flag setting process, unerased information may be stored in association with all disk signatures stored in association with the purchased product.

[0166] Additionally, for the second erasure flag setting process, the contents described in the first embodiment can be adopted to the extent necessary.

[0167] The identifier used as information for identifying a product when referencing information about the product including erasure information among the erasure history stored in the erasure software server 5, the master DB stored in the seller server 3, the store DB stored in the store terminal 2, and / or the EC site DB stored in the EC site server 4 is not particularly limited and can be designed as appropriate. The identifier used as information for identifying a product among the erasure history, master DB, store DB, and / or EC site DB may be a disk signature, a serial number or IMEI, and / or an administrative serial number. Furthermore, in the erasure history, master DB, store DB, and / or EC site DB, information about the product including erasure information may be stored in association with the disk signature, the serial number or IMEI, and / or the administrative serial number.

[0168] In this way, the system can manage data erasure information based on the disk ID by comprising: disk ID acquisition means for acquiring a disk ID for identifying the storage unit of a product; disk ID writing means for erasing data stored in the storage unit of the product and then storing the disk ID acquired by the disk ID acquisition means in the storage unit of the product as the disk ID of the storage unit of the product; and erasure information storage means for storing erasure information of the product in association with the disk ID of the storage unit of the product. Furthermore, by managing data erasure information based on the disk ID, when one product is equipped with multiple storage units, it becomes possible to manage erasure information for each storage unit. [Explanation of symbols]

[0169] 1 System 2. Store terminal 3. Merchant Server 4. EC Server 5. Erasure software server 6. Communication Networks 21 Control section 22 RAM 23 Storage Department 24 Input section 25 Display section 26 Communication Interface 31 Control Unit 32 RAM 33 Storage Department 34 Communication Interface

Claims

1. 1. A system comprising at least one computer device, a deletion information storage means for storing, in a database storing information relating to a plurality of products, deletion information relating to the deletion of data stored in the products in association with the products; a merchandise sales means for executing a sales start process for starting sales of the merchandise or a payment process for the merchandise based on erasure information regarding erasure of data stored in the merchandise; Equipped with The database stores information about products that a seller who sells reused goods possesses and / or manages for reuse sales, When the data stored in the product is erased, the erasure information storage means stores, as the erasure information, erasure completion information indicating that the data stored in the product has been erased; When the deleted information is stored in association with the product in the database, the product sales means executes a sales start process for the product or a payment process for the product. system.

2. 1. A system comprising at least one computer device, a deletion information storage means for storing, in a database storing information relating to a plurality of products, deletion information relating to the deletion of data stored in the products in association with the products; a sales availability output means for outputting sales availability information regarding whether the product is available for sale and / or erasure information regarding the product, based on erasure information regarding erasure of data stored in the product; Equipped with The database stores information about products that a seller who sells reused goods possesses and / or manages for reuse sales, When the data stored in the product is erased, the erasure information storage means stores, as the erasure information, erasure completion information indicating that the data stored in the product has been erased; When erased information is stored in the database in association with the product, the sales availability output means outputs, as the sales availability information, sales available information indicating that the product can be sold, and / or, as the erasure information, erased information indicating that the data stored in the product has been erased; and / or, when erased information is not stored in the database in association with the product, the sales availability output means outputs, as the sales availability information, unsaleable information indicating that the product cannot be sold, and / or, as the erasure information, not erased information indicating that the data has not been erased. system.

3. an erasing means for erasing data stored in the product; an erased information storage means for storing erased information indicating that the data stored in the product has been erased in association with the product when the data has been erased by the erasing means; Equipped with The erased information is an erase flag indicating that the data has been erased, or an erase history indicating that the data has been erased.

3. The system according to claim 1 or 2.

4. a sales availability information storage means for storing sales availability information indicating that the product is available for sale when the deleted information is stored in association with the product; Equipped with The system of claim 3.

5. an unerased information storage means for storing, when a product is purchased, unerased information associated with the product and indicating that data stored in the product has not been erased; Equipped with 3. The system according to claim 1 or 2.

6. a disc ID acquisition means for acquiring a disc ID for identifying a storage unit of the product; a disc ID writing means for erasing the data stored in the storage unit of the product, and then storing the disc ID acquired by the disc ID acquisition means in the storage unit of the product as the disc ID of the storage unit of the product; an erasure information storage means for storing erasure information of the product in association with the disk ID of the product storage section; Equipped with 3. The system according to claim 1 or 2.

7. a sales availability output means for outputting sales availability information regarding whether the product is available for sale and / or erasure information regarding the product based on erasure information regarding erasure of data stored in the product; Equipped with The system of claim 1 .

8. 1. A method executed in a system comprising at least one computer device, comprising: an erasure information storage step of storing erasure information relating to erasure of data stored in a product in association with the product in a database that stores information about the product; a merchandise selling step of executing a sales start process for starting sales of the merchandise or a payment process for the merchandise based on erasure information regarding erasure of data stored in the merchandise; and The database stores information about products that a seller who sells reused goods possesses and / or manages for reuse sales, When the data stored in the product is erased, the erasure information storage step stores, as the erasure information, erased information indicating that the data stored in the product has been erased; When the deleted information is stored in association with the product in the database, a product sales step executes a sales start process for the product or a payment process for the product. method.

9. 1. A method executed in a system comprising at least one computer device, comprising: an erasure information storage step of storing erasure information relating to erasure of data stored in a product in association with the product in a database that stores information about the product; a sales availability output step of outputting sales availability information regarding whether the product is available for sale and / or erasure information regarding the product based on erasure information regarding erasure of data stored in the product; and The database stores information about products that a seller who sells reused goods possesses and / or manages for reuse sales, When the data stored in the product is erased, the erasure information storage step stores, as the erasure information, erased information indicating that the data stored in the product has been erased; When erased information is stored in the database in association with the product, the sales availability output step outputs, as the sales availability information, sales available information indicating that the product can be sold, and / or, as the erasure information, erased information indicating that the data stored in the product has been erased; and / or, when erased information is not stored in the database in association with the product, the sales availability output step outputs, as the sales availability information, unsaleable information indicating that the product cannot be sold, and / or, as the erasure information, not erased information indicating that the data has not been erased. method.

Images