JP7796173B2 - Sales control system based on data erasure status - Google Patents

Description

The present invention relates to a system and a method.

So-called reuse sales have traditionally been carried out, in which items such as personal computers, smartphones, and home appliances are purchased from users and sold to other users.

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.

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.

The object of the present invention is to provide a system that prevents products from being sold if their data has not been erased.

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 sales availability of a product and/or sales availability information of the product based on erasure information regarding erasure of data stored in the product;
[3] The system according to [1] or [2], comprising: an erasure unit that erases data stored in a 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 erased flag indicating that the data has been erased, or an erased 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 a 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 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 after erasing the data stored in 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 including a product selling 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 sales availability output step of outputting sales availability information regarding sales availability of a product and/or erasure information of the product based on erasure information regarding erasure of data stored in the product;
This can be achieved by:

The present invention provides a system for preventing the sale of products from which data has not been erased.

1 is a block diagram showing a configuration of a system according to an embodiment of the present invention; 2 is a block diagram showing a hardware configuration of a store terminal according to an embodiment of the present invention; FIG. FIG. 2 is a block diagram showing a hardware configuration of a seller server according to an embodiment of the present invention. 10 is a flowchart of a first data erasure process according to an embodiment of the present invention. 10 is a flowchart of a first erasure flag setting process according to an embodiment of the present invention. 10 is a flowchart of a sale availability flag setting process according to an embodiment of the present invention. 10 is a flowchart of a sales process according to an embodiment of the present invention. 10 is a flowchart of a second erasure flag setting process according to an embodiment of the present invention. 10 is a flowchart of a second data erasure process according to an embodiment of the present invention.

The following describes embodiments of the present invention, but the present invention is not limited to the following embodiments, provided that they do not violate the spirit of the present invention. The order of the processes that make up the flowcharts described below is random, provided that no contradictions or inconsistencies occur in the process content. Furthermore, it is possible to omit some of the processes that make up the flowcharts, or to add new processes to the processes that make up the flowcharts, provided that no contradictions or inconsistencies occur in the process content. Furthermore, the device that executes each process that makes up the flowcharts can be changed to another device, provided that this does not violate the spirit of the present invention. In doing so, it is possible to change the process content so that no contradictions or inconsistencies occur in the process content.

(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 a device to which a unique serial number or IMEI is assigned is purchased, the data is erased, and then the device is sold for reuse.

[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.

The store terminal 2 may be a terminal installed in a store that sells reused goods. The store may be a physical store where products are actually displayed and sold. The store terminal 2 stores information about the products sold at the store in a store database (store DB).

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 multiple store terminals 2 provided in multiple stores. When the system 1 is provided with multiple store terminals 2 provided in multiple 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.

The store terminal 2 may be operated by store staff (hereinafter also referred to as store staff). Store staff refers to people who purchase devices, register products, sell products, etc. at the store.

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).

The EC server 4 may be a server device for conducting reuse sales through electronic commerce. The EC server 4 can be used to build an EC site for reuse sales. The EC server 4 stores information about products sold on the EC site in an EC site database (EC site DB).

Product registration and sales on the EC site may be performed by EC site staff (hereinafter also referred to as EC site staff). EC site staff may use a terminal (hereinafter also referred to as EC site staff terminal) to perform product registration and sales on the EC site.

Of the products held and/or managed by a seller 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.

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

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

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

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. Furthermore, 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 processing described below may be executed by any of the computer devices included in the system.

Figure 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, RAM 22, storage unit 23, input unit 24, display unit 25, and communication interface 26, all of which are connected via a bus.

The control unit 21 is composed of a CPU and ROM. The control unit 21 executes programs stored in the storage unit 23 and controls the store terminal 2. The RAM 22 is the work area of 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.

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 results of the calculation process. 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.

The communication interface 26 can be connected to the communication network 6 wirelessly or via a wired connection, and can send and receive data to and from other computer devices via the communication network 6. Data received via the communication interface 26 is loaded into RAM 22, where it is processed by the control unit 21.

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

Figure 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, RAM 32, storage unit 33, and communication interface 34, all of which are connected via an internal bus.

The control unit 31 is composed of a CPU and 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.

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

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 perform the specified functions.

For 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.

Below, we will explain an example of using system 1 to erase data stored on equipment purchased from users and then resell the equipment for reuse.

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

The store staff stores information about the purchased equipment in the master DB as product information. Hereinafter, storing product information in a database is also referred to as registering the product. The master DB may store information about the product, such as the management serial number, production number, or IMEI (International Mobile Equipment Identifier), product name, price, date of receipt, and inventory quantity, each associated with the other. The management serial number refers to a unique identifier for the product used by the seller when managing 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 production number or IMEI refers to an identifier assigned to the device by the manufacturer that produced it. The store staff can store product information in the master DB by entering it into the store terminal 2 and sending it to the seller server 3.

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

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.

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 the erasure, and so forth. For example, if the erasure history stores the date and time when erasure was completed and the results of the erasure, the erasure information may store erased information indicating that the data has been erased. Also, for example, if the erasure history does not store the date and time when erasure was completed and the results of the erasure, the erasure information may store not-erased information indicating that the data has not been erased.

When information about purchased equipment is stored in the master DB, the data stored on the equipment 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.

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

Registered products can be sold in stores and/or e-commerce sites. The store selling the product may be the store that purchased the product, or it may be a store different from the store that purchased the product.

When a product is sold in a store, the store staff selling the product registers the product at the store by storing information about the product in the store's store database.

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 may be at least partially different. The store DB may store product information such as a management serial number, manufacturing number or IMEI (International Mobile Equipment Identifier), product name, price, date of receipt, and inventory quantity, each associated with the other. A store staff member may input a request to send product information into 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 master DB be processed so that the contents are synchronized at a predetermined time interval.

The store DB may also store information about the availability of a product for sale (hereinafter referred to as "sale availability information") as information about the product. The sale availability information may be information about the availability of a product for sale, and is not particularly limited. For example, the sale availability information may be information indicated by a sale availability flag.

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.

Furthermore, the store DB may store information about the sales status of a 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 a product, and is not particularly limited. For example, the sales status information may be information indicated by a sales flag.

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.

When a product is registered in the store database, it may be unavailable for sale, and sales may not have begun. In this case, unsaleable information indicating that the product is unavailable for sale may be stored as sales availability information, and unsold information indicating that the product is not on sale may be stored as sales status information.

When a product is sold on an EC site, the staff member at the EC site selling the product registers the product on the EC site by storing information about the product in the EC site DB of the EC site. The product information stored in the EC site DB can use the same descriptions of product information stored in the store DB as described above, to the extent necessary. The EC site DB may store information about the product, such as sales availability information and sales status information.

Note that, although the above describes an example in which products are registered in the master DB and then in the store DB and/or EC site DB, the order in which products are registered is not particularly limited and can be designed as appropriate. For example, products may be registered in the store DB and/or EC site DB and then in the master DB.

In addition, here we will explain an example in which the purchased device is registered as a product and then the data stored on the product is erased, but the order in which the product is registered and the data is erased is not particularly limited and can be designed as appropriate. For example, the purchased device may be registered as a product after the data stored on it is erased.

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

[First Data Erasure Process]
4 is a flowchart of the 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 the target device) (step S101). The store terminal 2 accepts 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.

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 need only 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 via a wired or wireless connection.

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 using 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 to erase the selected data.

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

The method of erasing data in step S103 is not particularly limited and can be designed as appropriate. Examples of methods for erasing data 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 US Department of Defense compliant method DoD5200.28-M, the US Air Force method AFSSI5020, the US Department of Defense compliant method DoD5220.22-M, the US Navy method NAVSO P-5239-26-MFM, the US Navy method NAVSO P-5239-26-RLL, the former NSA method Bit Toggle, the German standard method VSITR, the Gutmann recommended method, the Secure Erase method, and the extended Secure Erase method. In step S103, the data to be erased is erased.

The erasure information in step S104 is not particularly limited and can be designed as appropriate. Examples of the erasure information include the target device's serial number or IMEI, management serial number, the date and time the erasure request was received, the date and time the data erasure was completed, and the erasure results. The erasure results may indicate that all of the data to be erased has been erased, that some of the data to be erased has been erased, or that not all of the data to be erased has been erased. Furthermore, the erasure results may include information that enables identification of the erased data and/or the data that was not erased.

In step S106, the erasure information may be stored in the 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 the erasure request was received, the date and time the data erasure was completed, the erasure results, and other information in association with one another. The erasure history stored in the erasure software server 5 may be displayable on the store terminal 2, etc.

Although not shown, the erasure information may also 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 complete. Alternatively, for example, when the erasure of data from the target device is complete, 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 to transmit 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 specified 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.

In addition, store staff may affix a sticker or other marking to products after the data has been erased to indicate that the data has been erased.

Furthermore, if the purchased device is a personal computer or other device with an OS pre-installed, the store staff may create an image file of the OS image and store it on the store terminal 2 before erasing the data, and then, after erasing the data, unpack the image file to restore the OS image.

Note that if the data stored on the device is not erased at the store, steps S101 to S104 do not need to be executed. For example, if the device is sent to an office of a business that provides a service that erases data from devices using erasure software, and the data is erased at that office, 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.

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

In other words, after the device is purchased, the data on that device is erased and the erasure information is stored in one of the computer devices. The computer device 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 computer devices is referenced and the following processing is performed.

The erasure information stored on the erasure software server 5 may be reflected in the master DB stored on the seller server 3 by the first erasure flag setting process described below.

[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 reference product erasure information (hereinafter also referred to as an erasure information reference request) (step S201). The erasure software server 5 receives the transmitted erasure information reference request (step S202). The erasure software server 5 transmits erasure information to the seller server 3 (step S203). The seller server 3 receives the transmitted erasure information (step S204). The seller server 3 determines whether the data stored in the product has been erased (step S205).

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.

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

Step S201 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 master DB whose deletion flags are OFF reaches a predetermined number, or when a seller terminal operated by the seller receives input to send a deletion information reference request. The predetermined frequency may also be once every 1/30 seconds, once per minute, once per hour, or once per day.

In step S201, the products that are the subject of the erasure information reference request are not particularly limited and can be designed as appropriate. The products that are the subject of the erasure information reference request may, for example, be all or part of a product whose erasure flag is OFF, or all or part of a product regardless of the state of the erasure flag. In step S201, information that can identify the products that are the subject of the erasure information reference request may be sent along with the erasure information reference request. Information that can identify the products that are the subject of the erasure information reference request may be, for example, the manufacturing number or IMEI, or the management serial number. When the seller decides the products that are the subject of the erasure information reference request, information that can identify the products that are the subject of the erasure information reference request may be input to the seller terminal.

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 some or all of the erasure information stored in the erasure software server 5, or may be information indicating at least some of the erasure information stored in the erasure software server 5. The information indicating at least some 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, for example, be the erasure result, the date and time when erasure was completed, or information indicating that data has not been erased.

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.

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 erased to ON. The deletion flag being ON indicates that the data has been erased. Therefore, when data stored in a product is erased, it is possible to store, in association with the product, erased information indicating that the data stored in the product has been erased.

Note that, 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 sent 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. Specifically, the erasure information stored here may 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 said to correspond to an erasure history indicating that data has been erased.

If the data stored in a product is erased, it is possible to sell the product in a store and/or on an EC site, and it is therefore possible to sell the product. Therefore, the sales availability information stored in the store DB and/or EC server DB may be updated using the sales availability flag setting process described below.

[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.

First, the store terminal 2 sends a request to the seller server 3 to reference information about the deletion flag (hereinafter also referred to as a deletion flag reference request) (step S301). The seller server 3 receives the sent deletion flag reference request (step S302). The seller server 3 sends information about the deletion flag (hereinafter also referred to as deletion flag information) to the seller server 3 (step S303). The store terminal 2 receives the sent deletion flag information (step S304). The store terminal 2 determines whether the deletion flag is ON (step S305).

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

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

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 for the product stored in the EC server DB to ON.

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 input for sending a deletion flag reference request is received. The predetermined frequency may also be once every 1/30 seconds, once per minute, once per hour, or once per day. If the conditions for updating sales availability information require, in addition to erasing data, checking the condition of the product for defects or whether the product is operating normally, step S301 may be executed when input for sending a deletion flag reference request is received.

In step S301, the product that is the subject of the deletion flag reference request is not particularly limited and can be designed as appropriate. The product that is the subject of the deletion flag reference request may, for example, be some or all of the products whose sales availability flag is 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 subject of the deletion flag reference request may be sent along with the deletion flag reference request. Information that can identify the product that is the subject of the deletion flag reference request may be, for example, the manufacturing number or IMEI, or the management serial number. Alternatively, store staff may identify the product that is the subject of the deletion information reference request and input it into the store terminal 2.

In step S303, erasure flag information for the product that is the subject 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.

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

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

Note that, although the above describes an aspect in which sales availability information is updated based on the deletion flag stored in the master DB, sales availability information may also be updated based on other deletion information. For example, 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 data stored in the product has been deleted, the store terminal 2 may set the sales availability flag to ON.

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

If sales availability information is stored in association with a product, the product may be sold in a store and/or on an e-commerce site. When selling a product, for example, the following sales process may be performed.

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

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

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

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.

When starting sales of products on an EC site, sales processing 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.

In step S401, the method for inputting a 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 a 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 to register 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 that can identify the product that is the subject of the request to execute the sales start process may also be input.

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.

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. In other words, in system 1, sales start processing is executed to start selling the product based on the sales availability information regarding the sales availability of the product.

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

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, for example, be a process of storing information indicating that the product is on sale in a store database, 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.

When starting sales of a product on an EC site, the sales start process may, for example, be 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 if the sales start process can be executed in accordance with the specifications of the sales system installed on the EC site.

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

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 audio from the speaker of the store terminal 2.

When the sale of the product begins on the EC site, 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, for example.

Furthermore, the content of the error is not particularly limited and can be designed as appropriate. For example, the content of the error may indicate that the product cannot be sold, or that the data stored in the product has not been erased.

When the sales availability flag is not determined to be ON, it may be the case that 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 for the product is output based on sales availability information regarding the sale availability of the product.

Furthermore, since the saleability flag being 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 in step S404, non-saleability information indicating that the product cannot be sold and/or non-erasure information indicating that the data has not been erased is output. In other words, in system 1, saleability information regarding the saleability 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.

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.

In addition, although the above describes an aspect in which the sales start process is not executed if the sales availability flag is not determined to be ON, system 1 may also be configured to be able to execute the sales start process in response to operational input by store staff, even if the sales availability flag is not determined to be ON. For example, based on the results of the determination of the sales availability information in step S402, sales availability information regarding the sale availability of the product and/or product deletion information may be output, and then input regarding whether or not to execute the sales start process may be accepted. By outputting sales availability information regarding the sale availability of the product and/or product deletion information, 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.

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

In addition, the above describes 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 be output based on erasure information regarding the erasure of data stored in the product.

In addition, the above describes an embodiment in which the sales availability information is updated based on the deletion information, and the sales start process or payment process is executed based on the sales availability information, and the sales availability information and/or deletion information is output. However, the sales start process or payment process may be executed, and the sales availability information and/or 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 payment process may be executed, and the sales availability information and/or 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 deletion information stored in the seller server 3 may be referenced, and the sales start process or payment process may be executed, and the sales availability information and/or deletion information may be output, based on the deletion information.

In addition, when selling a product, if certain conditions need to be met in addition to erasing data, such as the condition of the product's defects or whether the product is functioning properly, it may be preferable to execute the sales start process or payment process based on the sales availability information, or to output sales availability information and/or erasure information. The system configuration and processing content can be designed appropriately based on the seller's circumstances.

If a product that has been put on sale is purchased by another user, the data will likely be stored in the product's memory again. Therefore, when a product is purchased, a second deletion flag setting process may be performed, as described below.

[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.

First, the store terminal 2 executes payment processing for the product (step S501). The store terminal 2 sets the sales availability flag associated with the product and stored 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 associated with the product and stored in the master DB to OFF (step S505), and the second deletion flag setting process ends.

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

The payment process in step S501 may be performed, for example, by store staff 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.

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 enter the information necessary for payment processing into the store terminal 2.

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.

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 the payment process was performed, the sales price, information capable of identifying the store that made the sale, and information capable of identifying the store staff member who made the sale. Information capable of identifying the product may be, for example, a management serial number.

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.

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 that product is deleted again.

In this way, a system comprising at least one computer device can be provided that prevents the sale of products whose data has not been erased by including a product sales means that performs a sales start process to start the sale of the product or a payment process for the product based on erasure information regarding the erasure of data stored in the product.

Furthermore, by providing a system comprising at least one computer device with a means for outputting sales availability information regarding the saleability of a product and/or erasure information for the product based on erasure information regarding the erasure of data stored in the product, it is possible to provide a system for preventing the sale of products whose data has not been erased.

In this way, the system is equipped 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 the data has been erased, or an erasure history indicating that the 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.

Furthermore, when deleted information is stored in association with a product, the system is provided with a sales availability information storage means that stores sales availability information indicating that the product is available for sale, making it possible to store information indicating that the product from which data has been erased is available for sale.

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

(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. The 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 the disk signature with a management serial number.

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

The details described in the first embodiment can be adopted to the extent necessary for purchasing devices equipped with a memory unit and registering the products.

If the store is able to erase data stored on purchased devices, the data may be erased using a second data erasure process such as the one described below. In this case, a dedicated application for using the erasure software may be installed on the store terminal 2. If the erasure software can be used on a browser, a dedicated application for using the erasure software does not need to be installed on the store terminal 2.

[Second Data Erasure Process]
9 is a flowchart of the second data erasure process according to an embodiment of the present invention. First, a store staff member connects the store terminal 2 to the 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 device (step S602). Next, the store terminal 2 determines whether the device has a disk signature (step S603).

In step S601, the manner in which the store terminal 2 and the target device are connected can be the same as described in the first embodiment, to the extent necessary. Connecting the store terminal 2 and the target device may allow the store terminal 2 to output information about the target device.

If the target device is a device with a pre-installed OS, such as a personal computer, in step S602, the OS image is converted into an image file and stored in the store terminal 2. This allows the target device to be sold for reuse after the data on it has been erased and the OS restored. Before converting the image file in step S602, the target device may be restored to its factory default state by performing recovery (initialization) using the recovery function.

Note that if the target device is a device that does not have an OS pre-installed, such as a HDD, step S602 does not need to be executed.

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.

If it is determined in step S603 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).

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 a disk signature by combining any characters, numbers, symbols, etc. The generated disk signature may be assigned to the target device by being stored in the memory unit of the target device.

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

As mentioned above, the disc signature functions as a disc ID. Therefore, the system can obtain the disc ID in step S605.

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).

In step S608, the erasure software server 5 may store the disk signature as part of the erasure history. After erasing the data from the target device, the erasure software server 5 can associate the erasure information of the target device with the pre-stored disk signature and store it as the erasure history.

In addition, in step S606, other information that can identify the target device, such as the target device's serial number, IMEI, or management serial number, may be transmitted along 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.

Meanwhile, 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 disk signature stored in step S608 (step S613).

Regarding the acceptance of 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.

When the data is erased in step S610, the disk signature stored in the memory unit of the target device is also erased.

The erasure information stored in step S613 may include, for example, the target device's disk signature, serial number or IMEI, management serial number, date and time when the erasure request was received, date and time when data erasure was completed, and the erasure results. In other words, the erasure software server 5 may store the target device's disk signature, serial number or IMEI, management serial number, date and time when the erasure request was received, date and time when data erasure was completed, and the erasure results, all of which may be correlated with one another and stored as erasure information.

If a single product has multiple storage units, one disk signature is stored in one storage unit, and therefore erasure information for each disk signature may be stored in the erasure history in association with that disk signature. Alternatively, erasure information corresponding to multiple disk signatures may be stored in association with a single management serial number.

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.

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

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 when the OS image is restored in step S617, and is automatically written back, so step S616 does not need to be performed. 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.

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

Store staff may affix a sticker or similar to indicate that the data has been erased to products after the data has been erased. Products may also be affixed with a sticker or similar bearing a disk signature. The disk signature may be able to be verified by reading a code affixed to the product.

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

[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.

In step S201 of the first erasure flag setting process, erasure information may be referenced based on the disk signature, serial number or IMEI, and/or 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, serial number or IMEI, and/or management serial number transmitted together with the erasure information reference request.

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.

In addition, the first deletion flag setting process described in the first embodiment can be adopted to the extent necessary.

[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.

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

Note that if 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. If erased information is stored in association with all disk signatures stored in association with one product, then in step S306 of the sales availability flag setting process, sales availability information may be stored in association with one product.

In addition, the first deletion flag setting process described in the first embodiment can be adopted to the extent necessary.

[Sales Processing]
The product for which the sales availability information is stored may be sold in a store and/or an EC 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.

[Second Erasure Flag Setting Process]
If a product that was on sale is purchased, a second deletion flag setting process may be performed.

In addition, if 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.

In addition, the second deletion flag setting process described in the first embodiment can be adopted to the extent necessary.

When referencing information about a product including erasure information between 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, the identifier used to identify the product is not particularly limited and can be designed as appropriate. The identifier used to identify the product between 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 a product including erasure information may be stored in association with the disk signature, a serial number or IMEI, and/or an administrative serial number.

In this way, the system comprises a disk ID acquisition means for acquiring a disk ID for identifying the product's storage unit, a disk ID writing means for erasing the data stored in the product's storage unit and then storing the disk ID acquired by the disk ID acquisition means in the product's storage unit as the disk ID of the product's storage unit, and an erasure information storage means for storing the product's erasure information in association with the disk ID of the product's storage unit, thereby making it possible to manage data erasure information based on the disk ID. Furthermore, by managing data erasure information based on the disk ID, if a single product has multiple storage units, it becomes possible to manage erasure information for each storage unit.

1 System 2 Store terminal 3 Seller server 4 EC server 5 Eraser software server 6 Communication network 21 Control unit 22 RAM
23 Storage unit 24 Input unit 25 Display unit 26 Communication interface 31 Control unit 32 RAM
33 Storage unit 34 Communication interface

Claims (9)

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 relating to erasure of data stored in the merchandise ;
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. 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 sales availability of the product and/or erasure information of the product based on erasure information regarding erasure of data stored in the product ,
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. an erasing means for erasing data stored in the 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 the data has been erased by the erasing means;
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. a sales availability information storage means for storing sales availability information indicating that a product is available for sale when deleted information associated with the product is stored;
The system of claim 3 . 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;
3. The system according to claim 1 or 2. 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;
3. The system according to claim 1 or 2. 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;
The system of claim 1 . 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 sales 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 ;
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. 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 sales availability of the product and/or erasure information of the product based on erasure information regarding erasure of data stored in the product,
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.