JP2003331139A - Apparatus and method for sales processing - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize an apparatus and a method for sales processing which can prevent the sold right to use from illegally being used and provide the right to use free of charge when the right to use can not properly be exercised. <P>SOLUTION: At a site 2, whether there is a sales history regarding a user terminal 1 is retrieved from a sales history database 10 at a purchase request from the user terminal 1 and when there is a sales history, it is decided whether the sold right to use is already downloaded by reference to its contents; when it is decided that the downloading is incomplete, the right to use is downloaded to the user terminal 1 free of charge. Further, the user terminal 1 retrieves a purchase ID overlapping a purchase ID included in the currently purchased right to use from a purchase history database 22c and when an overlapping purchase ID is retrieved, the purchase ID is regarded as a forged or altered illegal one to invalidate the currently purchased right to use. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for selling software usage rights by utilizing the Internet, and in particular, it prevents unauthorized use of the sold usage rights or uses the usage rights that the user has purchased legally. The present invention relates to a sales processing device and a sales processing method for providing the usage right free of charge when the customer cannot properly exercise.

[0002]

2. Description of the Related Art In recent years, various business models are emerging with the increase in the population using the Internet, and services for distributing various contents such as music and software are also known as one form thereof. These services consist of a distribution site that is connected via the Internet and users who have a distribution contract with that site. When a user accesses the distribution site and requests download of desired data, the distribution site responds to the request. While sending the data to the user, the fee is collected from the user.

[0003]

By the way, in the form of distributing the software to the user, there is a concern that the distributed software will be copied and illegally used by the user.
Various schemes have been devised to limit or cancel the functions of software to be distributed. As a mechanism for this, for example, a usage restriction function is provided in software to be distributed to users, and only the user who wants to properly use this software releases the file for which the usage restriction function is released as "use right".
To sell as. However, even if the unauthorized use of the software distributed in this way is prevented, there is a problem that it is difficult to prevent the unauthorized use or modification of the sold “use right” itself.

In addition, in the form of selling the "usage right" via the Internet, if the user side does not download normally due to a communication error or the like, the "use right" is a legally purchased "use right" on the user side. However, there may be situations where it cannot be exercised. In such a case, the user will have to purchase the “use right” again, and there is also a problem that the purchase price will be double paid.

Therefore, the present invention has been made in view of such circumstances, and it is possible to prevent the illegal use of the sold usage right, and when the usage right purchased by the user cannot be properly exercised. It is an object of the present invention to provide a sales processing device and a sales processing method that can provide the product free of charge.

[0006]

In order to achieve the above-mentioned object, in the invention described in claim 1, the usage restriction is released by the site selling the usage right via the network and the usage right purchased from this site. A device provided in a user terminal provided with the software, the site stores sales history database means for storing and managing a sales history, and stores a sales history related to the user terminal in response to a purchase request from the user terminal. The presence / absence is searched from the sales history database means, and if there is a sales history, a determination means for determining whether or not the usage right sold is referred to by referring to the content, and the determination means determines that the download is not completed. If it is, or even if it has been downloaded, the sales history of the previous time and the sales history of the time before the one searched from the sales history database means match. In the case of a purchase request, the user terminal that has issued the purchase request is provided with a download means for downloading the usage right free of charge, the user terminal is a purchase history database means for storing and managing a purchase history, and is downloaded from the site, The purchase history database means searches for a purchase ID that duplicates the purchase ID included in the usage right purchased this time, and if the duplicate purchase ID is found, the invalidation means invalidates the usage right purchased this time. It is characterized by doing.

According to the second aspect of the present invention, the processing executed by the site that sells the usage right via the network and the user terminal equipped with the software whose usage restriction is released by the usage right purchased from this site In the method, in response to a purchase request from the user terminal, the site searches the sales history database that stores and manages the sales history for the presence or absence of a sales history related to the user terminal. A determination process for determining whether or not the usage right sold by referring to the content has been downloaded, and a case in which it is determined that the download is not completed in this determination process, or even if the download is completed, the previous time when the sales history database is searched. If the sales history of the previous two times matches, the usage right is downloaded to the user terminal that issued the purchase request free of charge. ; And a download process, in the user terminal, is downloaded from the site,
Search for a purchase ID that duplicates the purchase ID included in the usage right purchased this time from the purchase history database that stores and manages the purchase history, and invalidates the usage right purchased this time if a duplicate purchase ID is found. And a conversion process.

According to a third aspect of the present invention, there is provided a device provided on a site side that sells a usage right in response to a purchase request from a user terminal that is accessed via a network. Sales history storage means for storing sales history data including a user ID sent from the terminal, a previous purchase ID, and a download flag indicating whether or not the usage right sold has been downloaded to the user terminal side; User ID included
First search means for searching the sales history storage means based on the presence / absence of the corresponding sales history, and when the sales history is searched by the first search means, the download flag in the searched sales history data. And a first downloading means for downloading the usage right to the relevant user free of charge when the downloading is not completed by this judging means. If it is determined by the means that the download has been completed, a second search means for searching the previous purchase ID and the purchase ID before the last purchase from the sales history storage means, and the previous purchase I searched by the second search means
If D and the previous purchase ID match, the second download means for downloading the usage right to the corresponding user free of charge and the previous purchase ID searched by the second search means.
When the purchase ID does not match with the previous purchase ID, it is considered that the usage right is not officially purchased, and a notification means for notifying the user of new purchase is provided.

According to a fourth aspect of the present invention, there is provided a method of processing at a site which sells a usage right in response to a purchase request from a user terminal accessed via a network, at least at the time of the purchase request. The purchase request is provided with a sales history database that stores sales history data including a user ID sent from the user side, a previous purchase ID, and a download flag indicating whether or not the usage right sold has been downloaded to the user side. User I included
The first search step of searching the sales history database for the presence or absence of the corresponding sales history based on D, and when the sales history is searched in the first search step, the download in the searched sales history data is performed. A determination process of determining whether or not the usage right has been downloaded with reference to the flag, and a first download process of downloading the usage right to the corresponding user free of charge when it is determined that the download is not completed in this determination process, When it is determined that it has been downloaded in the determination process, the second search process of searching the previous purchase ID and the purchase ID of the last-one purchase from the sales history database, and the previous purchase ID searched in the second search process. A second download process of downloading the usage right to the corresponding user free of charge when the purchase ID matches the previous-second purchase ID, and the second search. If the previous purchase ID and the previous purchase ID found in the previous step do not match, it is considered that the usage right is not a regular purchase, and a notification process of notifying the user of a new purchase is provided. To do.

According to a fifth aspect of the present invention, there is provided a device for managing the expiration date of software operating on the user terminal side according to the usage right purchased from the site via the network, and at least the purchase right identifying the purchased usage right. I
D, a purchase history storage unit that stores purchase data including a status flag indicating the status of the usage right and an expiration date, and a purchase ID that is downloaded from the site side according to the purchase and that is included in the usage right purchased this time. First searching for whether or not a purchase ID is stored in the purchase history storage means
When the duplicate purchase ID is searched by the first search means and the invalidating means that invalidates the usage right purchased this time, and the duplicate purchase ID is not searched by the search means, Registration means for generating new purchase data having a status flag indicating that the purchased usage right is in an unused state and valid time of the usage right, and registering the new purchase data in the purchase history storage means, and the registration means. By means of changing the state represented by the state flag of the new purchase data registered in the purchase history storage means during function use to release the use restriction of the software, and the use restriction is released by this release means. When the software is in operation, a second retrieval device that retrieves purchase data having a status flag indicating that the function is in use from the purchase history storage means at regular time intervals. When the expiration date of the purchase data retrieved by the second retrieval means has expired, the state represented by the state flag of the purchase data is changed to the usage right invalid, and if the expiration date has not expired, the usage restriction is released. And a term management means for updating the term of validity according to the elapsed time from.

According to a sixth aspect of the present invention, which is dependent on the fifth aspect, the deadline management means stores the purchase data whose usage restrictions have been released from the purchase history storage means just before the execution of the software ends. It is characterized in that the software is searched for, the status flag of the corresponding purchase data is changed to the usage right invalid status, and then the software is terminated.

According to a seventh aspect of the present invention, there is provided a method of managing the expiration date of software operating on the user terminal side according to the usage right purchased from the site via the network, which purchase method identifies at least the purchased usage right. I
D, a purchase history database that stores purchase data including a status flag indicating the status of usage rights and an expiration date,
A purchase ID that is downloaded from the site according to your purchase and that overlaps with the purchase ID included in the usage right you purchased this time.
The first search step of searching whether or not is stored in the purchase history database, and if a duplicate purchase ID is searched in this first search step, the use right purchased this time is invalidated. And a new flag including a status flag indicating that the usage right purchased this time is in an unused state and a valid time of the usage right when a duplicate purchase ID is not searched by the first searching means. A registration process of generating new purchase data and registering it in the purchase history database, and changing the state represented by the status flag of the new purchase data registered in the purchase history database during the registration process to use the function. Purchase with a release process for releasing the usage restriction of the software and a status flag indicating that the function is in use when the software whose usage restriction has been released by this cancellation process is in operation A second search step of searching the purchase history database at regular intervals, and if the purchase data searched in this second search step has expired, the status flag of the purchase data is changed. It is characterized by including a period management process of changing the state shown to invalidation of the usage right, and updating the expiration date according to the elapsed time from the time when the usage restriction is released if it has not expired.

In the invention according to claim 8 subordinate to claim 7, in the deadline management process, the purchase history database is searched for purchase data whose usage restrictions have been released just before the execution of the software ends. Then, the state flag of the corresponding purchase data is changed to the use right invalid state, and then the execution of the software is terminated.

According to the present invention, at a site that sells usage rights via a network, in response to a purchase request from a user terminal, the sales history database is searched for the presence or absence of a sales history related to the user terminal, and the sales history exists. If so, it is determined whether the sold usage right has been downloaded by referring to the content, and if it is determined that the download is not completed, or even if it has been downloaded, the sales history of the previous and the previous two times retrieved from the sales history database If they match, the usage right is downloaded to the user terminal that issued the purchase request free of charge. For example, although the payment was made at the time of the previous purchase, the download was not performed normally due to a failure such as a communication error. In some cases, the right to use shall be provided free of charge when a repurchase request is made due to the expiration of the right to use the legitimately purchased right to use. Possible to become. Also, in a user terminal equipped with software whose usage restrictions are released by the usage right purchased from the site, a purchase ID that is the same as the purchase ID included in the usage right purchased this time is searched from the purchase history database, and the duplicate purchase ID is found. If the purchase ID is found, the purchase ID is regarded as falsified or falsified and the usage right purchased this time is invalidated, so that it is possible to prevent the unauthorized use of the sold usage right.

[0015]

DETAILED DESCRIPTION OF THE INVENTION An embodiment of the present invention will be described below with reference to the drawings. A. System Configuration FIG. 1 is a diagram showing a schematic configuration of a sales processing system according to an embodiment. The system shown in this figure includes a site 2 that sells usage rights of the client software 12, and a user terminal 1 that accesses the site 2 via a network NT such as the Internet. The user terminal 1 includes a purchase history database 10 and history management software 1
1, client software 12 and Web browser 13
Is composed of a personal computer or the like that operates.

The purchase history database 10 includes a usage right purchased from the site 2 (a usage restriction release file LF described later).
(Corresponding to (1)) purchase data representing the purchase history is stored and managed.
The purchase data for each record is, as shown in FIG. 2, purchase_db [0] [0] to [0].
It is formed from [5]. purchase_db [0]
[0] is a serial number sysID assigned by history management software 11 (described later), purchase_db [0]
[1] is the date of purchase. purchase_d
b [0] [2] represents the purchase ID issued by site 2 p
purchaseID, purchase_db [0]
[3] is status indicating the status of the purchased usage right. When this status is "0", it means unused, "1"
When, the function is being used, and when it is “2”, the usage right is invalid (finished). purchase_db [0]
[4] is "remainTim" indicating the remaining time of the usage right
e, purchase_db [0] [5] are checksums checksum for alteration prevention.

The history management software 11 releases the usage restriction of the client software 12 based on the usage restriction release file LF downloaded from the site 2 in accordance with the purchase of the usage right. Specifically, it is determined whether the purchase ID (purchaseID) included in the usage restriction release file LF is an unused one, and if it is not used, new purchase data generated from the usage restriction release file LF is purchased. Register in the history database 10. By registering new purchase data in the purchase history database 10, the use restriction of the client software 12 is released. Also, the history management software 11 is the client software 12 whose usage restrictions have been released.
Is being executed, the usage period is managed according to the remaining time "remainTime" stored in the purchase history database 10.

The usage restriction of the client software 12 is released according to the contents of the purchase data stored in the purchase history database 10. That is, client software 1
2, the usage restriction is set for each processing function, and the purchase history database 10 is searched for the purchase data n for which the usage restriction is released corresponding to the processing function to be executed. Purchase_db
Remaining time remainingTim stored in [n] [4]
When e is valid, the use restriction of the processing function to be executed is released. The Web browser 13 has a function of accessing the site 2 to generate a browsing request, and also delivers the usage restriction release file LF downloaded from the site 2 to the history management software 11.
The processing request generated by the client software 12 is sent to the site 2
It has a function of sending to the side.

The site 2 is composed of a Web server 20, a management server 21 and a database 22. Web
The server 20 has a function of blocking an intranet (not shown) connected to the management server 21 side described later and a network NT such as the Internet, and controls communication between both networks. Further, the Web server 20 responds to a browsing request from a legitimate user who has authenticated the access, that is, a user terminal 1 who has registered as a user on the site 2.
While browsing page b or relaying a processing request from a valid user to the management server 21, each response from the management server 21 corresponding thereto is returned to the corresponding user terminal 1.

The management server 21 executes various processes in response to a request from a legitimate user relayed from the Web server 20. For example, from the user terminal 1 to the client software 12
When a request to purchase the usage right is received, the information related to the usage right sale is registered in the sales history database 22c described later as a sales history. When a request for browsing desired content (Web page) is received from the user terminal 1, the corresponding content is extracted from the content database 22a and sent to the requesting user terminal 1 side. Further, when selling the usage right to the user terminal 1, the management server 21 accesses the payment system 40 via the network NT and makes online payment for the usage right sales.

The management server 21 includes a sales information stack SS that holds sales information when the usage right is sold to the user terminal 1. Here, the configuration of the stack SS will be described with reference to FIG. This sales information stack S
S is the last added stack cellData
The so-called LI in which [0] and [0] are first processed
It is configured as a FO stack. Each stack is s
It is formed from elData [0] [0] to [0] [6]. sellData [0] [0] is sellDataID, which represents the serial number, sellData [0] [1]
Is the userID and sellD that represent the purchased user ID
ata [0] [2] represents the login name of the purchasing user n
It is ame.

SellData [0] [3] is reqdate representing the date and time of receipt of the purchase request from the user,
sellData [0] [4] is the user terminal 1 at the time of purchase.
Purchase ID sent from the customer (purcha
(seID) lastSellID, sellDa
ta [0] [5] is status indicating the purchase state. When the status is "0", it indicates immediately after the purchase request is accepted, when it is "1", it indicates a new purchase, when it is "2", it indicates repurchase, and when it is "3", it means that an external settlement institution is processing (payment in process). Represent sellData [0] [6] is a date indicating the date and time when the stack contents are updated. The processing using the sales information stack SS will be described in detail later.

The database 22 stored and managed by the management server 21 is the content database 2 described above.
In addition to 2a, a user database 22b and a sales history database 22c are provided. User database 22b
Stores and manages personal information of the user terminal 1 registered by the user, and has a record structure shown in FIG. User data for each record is user
It is formed from [0] [0] to [0] [4]. user
[0] [0] is a user ID representing a user ID (serial number) assigned by the system, user [0] [1] is a login name name, user [0] [2] is an authentication password passwd, user [0] [ 3] is an email address mailaddress, user [0]
[4] is a flag login that indicates whether or not login is in progress.

The sales history database 22b is a database for managing sales information extracted from the sales information stack SS as a sales history, and has a record structure shown in FIG. Sales history data for each record is
It is formed from sellHist [0] [0] to [0] [8]. sellHist [0] [0] is the serial number sellHistID, sellH assigned by the system.
ist [0] [1] is the purchaser's userID, se
llHist [0] [2] is the login name n of the purchasing user
ame and sellHist [0] [3] are on sale date dat
It is e.

SellHist [0] [4] is the request date reqDate, se when the purchase request is received from the user terminal 1.
llHist [0] [5] is sellI representing a sales ID
D, sellHist [0] [6] are purchase IDs sent from the user terminal 1 side at the time of purchase (purc at the time of the previous purchase).
(haseID) is the lastSellID. s
ellHist [0] [7] is a flag IsRet indicating "0" in the case of new sale and "1" in the case of resale.
It is ry. sellHist [0] [8] is a flag IsDownload indicating "1" when the usage restriction release file LF has been downloaded to the user terminal 1 and "0" when it has not been downloaded.

B. Operation Next, the operation of the sales processing system will be described with reference to FIGS. In the following, first, the overall operation relating to the sale of the usage right will be described with reference to the sales processing flow shown in FIG. 6, and then the “sales history confirmation processing” executed by the site 2 side and the user terminal 1 side executed in the sales processing flow. "Usage restriction release process", "Expiration date management process" to be executed
And will be described in detail.

(1) Overall operation In the user terminal 1, the user uses the client software 1
When an attempt is made to execute a certain processing function of No. 2, the client software 12 judges whether or not the usage of the processing function instructed to be executed is restricted. If the usage restriction is released, the processing function is executed, but if the usage restriction is set, that is, the usage right to release the usage restriction has not been purchased, the purchase corresponding to the processing function instructed to be executed. If the data is not registered in the purchase history database 10 or is invalid purchase data such as that the usage right has already been purchased but the expiration date has passed, the client software 12 proceeds to step S1 in FIG. A purchase request for the usage right (usage restriction release file LF) is generated.

Next, in step S2, the client software 12 searches the purchase history database 10 for the purchase ID (purchaseID) of the previous purchase. Next, in step S3, the site 2 is accessed through the Web browser 13 and the purchase request generated in step S1 is acquired along with the purchase ID (purchaseID), user ID, and password for the previous purchase searched in step S2. Etc. to the site 2 side. Then, in step S4, the site 2 determines whether or not the user data that matches the user ID and password received from the user terminal 1 side is registered in the user database 22b (see FIG. 4) and performs access authentication.

If the user is authenticated as a legitimate user, the site 2 executes a sales history confirmation process in step S5. In the sales history confirmation process, the purchase ID (purchaseID) at the time of the previous purchase received from the user terminal 1 side
And sales history database 22c based on the user ID
Is checked to see if there is a sales history, and if there is no sales history, the user terminal 1 side is notified that it is a new purchase. If the usage right (usage restriction release file LF) is not completely downloaded although there is a sales history, repurchase processing is performed. The repurchasing process omits step S7, which will be described later, in order to avoid double payment, and steps S8 to S are performed.
Refers to the process of executing 10.

Next, in step S6, the user terminal 1 receives a notification of a new purchase from the site 2, generates a purchase request, and returns it to the site 2 side. The purchase request includes at least the user's user ID, password, and payment information (for example, a credit card number or a prepaid card number that can be used on the Internet). Next, in step S7, the site 2 receives the purchase request from the user terminal 1 and executes the payment process. In the payment process,
The payment system 40 is requested to make payment based on the payment information included in the purchase request. Subsequently, in step S8, the corresponding sales history data in the sales history database 22c is updated according to the payment settlement, or the corresponding sales history data in the sales history database 22c is updated according to the repurchase. Then, in step S9, the usage restriction release file LF is created.

As shown in FIG. 7, the usage restriction release file LF includes chkwd, IHeader, and IDat.
a, IExtInfo, ExtInfo, Data and ckecksum. chkwd is an identifier representing the function name of the client software for which usage restrictions are to be released. IHeader represents the file header size. IData is Data and ckecksu
represents the total size of m. IExtInfo represents the size of additional header information. ExtInfo represents additional information such as the user ID and the purchase date. Data is a purchase ID (pur) registered in the purchase history database 10 (see FIG. 2).
chaseID) and the like. ckecksum
Is a checksum for preventing alteration.

When such a usage restriction release file LF is created, the site 2 proceeds to step 10 and downloads it to the user terminal 1 side which issued the purchase request. As a result, in the user terminal 1 that has issued the purchase request, step S1
In 1, the usage restriction release file LF is received and stored in the memory. Next, in step S12, the history management software 11 determines whether or not the purchase ID (purchaseID) included in the usage restriction release file LF is an unused one, and if it is not used, it is generated from the usage restriction release file LF. The new purchase data is registered in the purchase history database 10 and the use restriction releasing process for releasing the use restriction of the client software 12 is executed.

Subsequently, in step S13, the client software 12 searches the purchase history database 10 for purchase data for which usage restrictions have been released for each timer event, and if the corresponding purchase data has expired, it is used. The right is invalidated, and if it has not expired, the remaining time remain according to the elapsed time from the cancellation time to the current time
The purchase history database 10 is searched for purchase data whose usage restrictions have been released at the end of execution of the execution of the time, and the expiration date management process is executed to terminate the execution after invalidating the usage right of the corresponding purchase data.

(2) Operation of Sales History Confirmation Process Next, the operation of the sales history confirmation process will be described with reference to FIG. In this process, the management server 21 of the site 2 is the main subject of operation. When this processing is executed through step S5 (see FIG. 6) described above, the process proceeds to step SA1 in FIG.
In step SA1, the user number of the user terminal 1 that has accessed in response to the purchase request is stored in the register no, while the purchase ID of the previous purchase (purchaseID: called the previous purchase ID) received from the user terminal 1 side at the time of access is stored. The user ID is stored in the register lastID, and the user ID is stored in the register userID. Next, at step SA2, the flag rtn is set to "1" and the stack pointer iS is reset to zero. In addition,
The flag rtn represents a new purchase when the flag value is "1", and represents a repurchase when the flag value is "2". Stack pointer i
S is a pointer for searching the sales information stack SS (see FIG. 3).

Then, in step SA3, an empty stack area number is retrieved from the sales information stack SS, stored in the stack pointer iS, and the serial number sel is selected.
Generate 1DataID. Next, in step SA4, of the sales information stack SS, the stack pointer iS
Register new sales information in the empty stack area indicated by.
That is, the newly generated cellDataID is se
In llData [iS] [0], register userID
The user ID stored in cellData [iS]
Register in [1]. Also, the login name name (user [no] [1]) read from the user database 22b according to the user number stored in the register no.
Is registered in sellData [iS] [2]. Furthermore, the current date and time is set to cellData [iS] [3],
Se the previous purchase ID stored in the register lastID
Register with llData [iS] [4]. And se
In llData [iS] [5], a flag status is set to indicate the state immediately after the purchase request is accepted, and sellData is set.
The current date and time is registered in [iS] [6].

When the stack registration is completed, step SA
5, the number of history records registered in the sales history database 22c is stored in the pointer iH, while register se
Resets q1 and seq2 to zero. Next, step S
In A6 to SA8, it is determined whether or not the user ID of the user terminal 1 requested to purchase this time is registered in the sales history database 22c, that is, whether or not there is a sales history. Less than,
The operation description will be divided into cases where there is no sales history and cases where there is a sales history.

When there is no sales history If the corresponding sales history is not registered in the sales history database 22c, the value of the pointer iH decremented every time the search is advanced reaches "0", and as a result, the judgment result of step SA6. Becomes "YES", and step SA1
Go to 3. In step SA13, the content of the register seq2 is stored in the register lastID.
It is determined whether or not
Since eq2 remains zero-reset, the determination result is "NO", and the flow proceeds to step SA15. Step S
At A15, the flag rtn is set to s in the sales information stack SS.
Set to elData [iS] [5] (status). Since the flag rtn remains set to "1" in step SA2, the sellData
The flag status of [iS] [5] becomes “1”,
Represents a new purchase. Then, the process proceeds to step SA16 to notify the user terminal 1 that it is a new purchase. As a result, the user terminal 1 executes the above-described step S6 (see FIG. 6).

When there is a sales history If there is a sales history, the judgment result of step SA7 is "YE
S ”, and the process proceeds to step SA9. At step SA9, sellHist in the sales history database 22c
It is determined whether [iH] [8] is "0", that is, whether the usage restriction release file LF is incompletely downloaded.
Hereinafter, description will be given separately for the case where the download is not completed and the case where the download is completed.

(A) When the download is not completed, the usage right (usage restriction release file L
The case where F) is not downloaded to the user terminal 1 refers to a case in which the payment was not made normally due to a failure such as a communication error, etc. even though the payment was made at the time of the previous purchase. In such a case, the determination result of step SA9 is “YES”, and step SA
In step 14, the flag "rtn" is set to "2" indicating repurchase. Then, in step SA15, the flag st of the sellData [iS] [5] of the sales information stack SS is set.
"2" is set in "atus", and the repurchase process is executed in the subsequent step SA16. The repurchase process mentioned here is
It refers to steps S8 to S10 (see FIG. 6) described above. That is, after updating the corresponding sales history data in the sales history database 22c according to the repurchase, the usage restriction release file LF is created and downloaded to the user terminal 1.

(B) In the case where the download has been completed On the other hand, when the download has been completed, the determination result in step SA9 becomes "NO", and the flow proceeds to step SA10. In step SA10, it is determined whether the value of the register seq1 is "0". In the first pass, the above step SA
Since the register seq1 is reset to zero at step 5, the result of the determination is "YES", and the routine proceeds to step SA11. At step SA11, sellHist [iH] [6] from the sales history database 22c, that is, the last purchase ID
Is stored in the register seq1 and the process is returned to step SA8.

Then, in the process of searching for the presence or absence of the sales history (steps SA6 to SA8), if there is the sales history of the previous two times and it has been downloaded, the judgment result of step SA10 becomes "NO" and step SA1.
Go to 2. In step SA12, the purchase ID before last is stored in the register seq2 and the process is returned to step SA8. In this way, when the previous purchase ID and the two-previous purchase ID are stored in the registers seq1 and seq2 respectively, the determination result of step SA6 becomes “YES”, and step S6
The process proceeds to A13.

At step SA13, the register seq2
Pre-previous purchase ID and register lastID stored in
It is determined whether or not the previous purchase ID stored in is matched. If the previous purchase ID and the purchase ID before the last match,
The result of the determination is "YES", the flow proceeds to step SA14, where "2" indicating repurchase is set in the flag rtn.
Then, in step SA15, the flag status of the sellData [iS] [5] of the sales information stack SS is set.
Is set to "2", and the repurchase process is executed in step SA16. In other words, if the sales history of the previous time and the sales history of the previous time are the same, it is regarded as a repurchase request due to the expiration of the usage right of the legally purchased usage right. On the other hand, if the sales history of the previous time and the sales history of the previous time do not match, the determination result of the above step SA13 becomes “NO”, and in this case, it is considered that the usage right is not officially purchased, and steps SA15 to SA16 are executed. And notifies the user terminal 1 that it is a new purchase.

As described above, on the site 2 side, in response to a purchase request from the user terminal 1, the sales history database 22c is searched based on the user ID included in the purchase request to determine whether or not there is a sales history. If there is no sales history, the new purchase is notified to the user terminal 1. On the other hand, if there is a sales history, sel in the corresponding sales history data iH
Flag IsDo stored in lHist [iH] [8]
Usage rights based on wnload (usage restriction release file L
F) determines whether the download is incomplete. If there is a sales history but the download is not completed, a re-purchase process for creating a usage restriction release file LF and downloading it to the user terminal 1 for free is executed. On the other hand, if it has been downloaded, the previous purchase ID and the two-precedent purchase ID are searched from the sales history database 22c, and if the sales history of the previous purchase and the previous purchase of the previous purchase match, the expiration date of the right to use the purchase is expired. The repurchase process that provides the usage right free of charge is regarded as a repurchase request due to this. On the other hand, if the sales history of the previous time and the sales history of the previous time do not match, it is considered that the usage right is not officially purchased, and the user terminal 1 is notified of the new purchase.

(3) Operation of Usage Restriction Canceling Process Next, the operation of the usage restriction canceling process will be described with reference to FIGS. This process is mainly performed by the history management software 11 of the user terminal 1. Step S12 described above
When this processing is executed via (see FIG. 6), the process proceeds to step SB1 in FIG. In step SB1, chkwd, IHeader, IData, IExtI are extracted from the usage restriction release file LF received in step S11.
nfo, ExtInfo, Data and ckecks
Extract each data element of um. Next, step SB2
Then, IHeader (file header size) + ID
It is checked whether the value of ata (total size of Data and ckecksum) matches the file size of the received usage restriction release file LF, that is, whether the file has been properly downloaded. Here, if the file sizes do not match, the determination result is "NO", the process proceeds to step SB3, an error message indicating that the file has not been properly downloaded is generated, and this process is completed.

On the other hand, if the file sizes match, the determination result is "YES", the flow proceeds to step SB4, and the purchase history inspection process shown in FIG. 10 is executed. When the purchase history inspection process is executed, the history management software 11 is displayed in FIG.
The process proceeds to step SB4-1 of 0, and the purchase ID (pur is acquired from the data element Data of the usage restriction release file LF.
chaseID) is extracted and stored in the register purID. Next, in step SB4-2, the search pointer i for searching the purchase history database 10 is reset to zero, and the flag rtn is also reset to zero, indicating that the usage restriction release file LF is in an unused state.

Then, in steps SB4-3 to 4-5, the register pur is incremented according to the step of the search pointer i.
PurchaseI matching the purchase ID stored in the ID
The purchase history database 10 is searched for purchase data having D (purchase_db [i] [2]). When the corresponding purchase data is retrieved, step S
The determination result in B4-4 is “YES”, and step SB
In step 4-6, the flag rtn is set to "1" to complete this processing. That is, when purchase data having a purchase ID that duplicates the purchase ID extracted from the usage restriction release file LF purchased this time is registered in the purchase history database 10, the previously registered purchase ID has been tampered with or altered. Since the usage right (use restriction release file LF) purchased this time is invalidated, the flag rtn is set to "1" to indicate that the use restriction release file LF has been used.

On the other hand, when the purchase data having the purchase ID that is the same as the purchase ID extracted from the usage restriction release file LF purchased this time is not searched from the purchase history database 10 and the inspection is completed, the determination result of step SB4-3. Becomes "YES" and the process proceeds to step SB4-7. In step SB4-7, the valid time of the usage restriction release file LF is stored in the register remainTime, and the checksum value of the file LF is calculated and stored in the register checksum.

Then, in step SB4-8, purchase_db [i] is set as new purchase data.
In [0], the newly issued sysID is
e_db [i] [1] is the current date and time, purchas
The purchase ID stored in the register purID is stored in e_db [i] [2] as purchase_db [i] [3].
, The value “0” of the flag rtn indicating the unused state is set to
The register rema is stored in rchase_db [i] [4].
The valid time stored in inTime is purchas
After the checksum values stored in the register checksum are registered in e_db [i] [5] and the purchase history database 10 is updated, this processing is completed.

When the purchase history inspection is completed in this way, the process proceeds to step SB5 of the above-mentioned use restriction releasing process (see FIG. 9). In step SB5, it is determined whether the flag rtn obtained in the above-mentioned purchase history inspection process is "0", that is, whether the usage restriction release file LF is in the unused state. When the flag rtn is "1" (used state), the determination result is "NO", and an error message indicating that the usage right has been invalidated by an illegal process such as falsification or alteration of the purchase ID is generated. On the other hand, if the usage restriction release file LF is in the unused state, the determination result is “YES”.
Therefore, the process proceeds to step SB6. Step SB
At 6, it is determined whether the client software 12 is being activated. If not started, the judgment result is "NO".
Then, the process proceeds to step SB7. In step SB7,
When the client software 12 is activated, the fact that the usage restriction is released is displayed on, for example, a display screen to notify the user.

On the other hand, if the client software 12 is running, the result of the determination in step SB6 is "YE
S ”, and the release process shown in FIG. 11 is executed via step SB8. When the release processing is executed, the history management software 11 advances the processing to step SB8-1 in FIG. In steps SB8-1 to SB8-2, the register p
The resetID, the remainTime and the search pointer i are each reset to zero. Then, in steps SB8-3 to SB8-5, the search pointer i
Purchase_db [i] [3]
The purchase history database 10 is searched for purchase data whose flag status is “0”, that is, unused purchase data.

If the corresponding purchase data is not found and the search is ended, the determination result of step SB8-3 is "Y".
However, when the corresponding purchase data is retrieved, the determination result of step SB8-4 becomes "YES", and the process proceeds to step SB8-6. At step SB8-6, the purchase data of the corresponding purchase data is purchased.
“1” in flag stutas of se_db [i] [3]
Set and change while using the function. As a result, the use restriction of the client software 12 that refers to this purchase data is released. In addition, the purchase of the corresponding purchase data
purchase ID (p read from ase_db [i] [2]
(urchaseID) in the register purID, pur
The valid time read from chase_db [i] [4] is set in the register remain, and the release time (current time) ticktime at which the usage restriction is released is set in the register start.
Store each in Time and complete this process.

As described above, in the usage restriction releasing process, the usage restriction releasing file LF downloaded from the site 2 is used.
If the file size is checked and it is correct, then the purchase I extracted from the usage restriction release file LF purchased this time
It is determined whether or not a purchase ID that is the same as D is registered in the purchase history database 10. Then, if the duplicate purchase ID is registered, the purchase ID is regarded as a falsified or altered fraudulent item, and the usage right (use restriction release file LF) purchased this time is invalidated. On the other hand, if there is no duplicate purchase ID, the purchase right to be newly registered, such as setting the usage right purchased this time (use restriction release file LF) to an unused state or setting the valid time of the use restriction release file LF. Data is generated and registered in the purchase history database 10. Then, if the client software 12 is running, purchase_db [i] of the registered unused purchase data.
[3] (Flag stutas) is set to "1" to change the function during use and release the use restriction.

(4) Operation of Expiration Date Management Process Next, the operation of the expiration date management process will be described with reference to FIG. This process is mainly performed by the client software 12 of the user terminal 1. When this processing is executed through step S13 (see FIG. 6) described above, step SC
In step 1, the purchase data generated by the release processing of the history management software 11 (see FIG. 11) is fetched as an argument. That is, the purchase ID (p
(urchaseID), valid time (predetermined time limit) stored in register remain, and register star
The release time ticktime stored in tTime is fetched. Next, in steps SC2 to SC3, presence or absence of a timer event in an idle state waiting for event input,
Determine whether there is a state transition (end of execution). Hereinafter, the operation will be described separately for the case where a timer event occurs in the idle state and the case where the state transitions.

When a Timer Event Occurs When the client software 12 is in the idle state and a timer event occurs, the result of the determination in step SC2 is "YES", the flow proceeds to step SC4, and the search pointer i is reset to zero. Then, step SC5
At SC8, pu is incremented according to the step of the search pointer i.
flag stutas of rchase_db [i] [3]
Is "1" and purchase_db [i]
The purchase history database 10 is searched for purchase data in which the purchase ID (purchaseID) of [2] and the purchase ID stored in the register purID match, that is, purchase data in which the use restriction is released. If there is no corresponding purchase data, the determination result of step SC5 becomes "YES", and this processing is completed. However, if the corresponding purchase data is searched, the determination result of step SC7 becomes "YES", and the process proceeds to step SC9. Proceed with processing.

At step SC9, the current time tickt
Store time in register nowTime. Next, at step SC10, this current time ticki
The time obtained by subtracting the release time ticktime stored in the register startTime from me is represented by the register re
It is determined whether it is less than the valid time stored in main, that is, whether the valid period has expired. If the time limit has expired, the judgment result will be "YES" and step SC
Proceed to 11. In step SC11, the flag st of purchase_db [i] [3] of the corresponding purchase data is acquired.
This process is completed after setting "2" in "atus" to invalidate the usage right.

On the other hand, if the time limit has not expired, the result of the determination in step SC10 is "NO", and step SC1
Proceed to 2 and purchase_d of the corresponding purchase data
The remaining time remainingTime is registered in b [i] [4]. That is, the remaining time remainTime is obtained by subtracting the elapsed time (current time-release time) from the valid time (predetermined time limit) stored in the register remai.
Register as. Then, the process is returned to step SC2 described above.

In case of state transition (end of execution) In this case, the judgment result of the above-mentioned step SC3 is "YE
S ", the process proceeds to step SC13, and the search pointer i is reset to zero. Then, steps SC14 to S
In C17, similar to steps SC5 to SC8 described above,
The purchase history database 10 is searched for purchase data for which the usage restriction has been released, while stepping the search pointer i. If there is no corresponding purchase data, step SC14
The result of the determination is "YES", and the processing ends without performing any processing. On the other hand, when the corresponding purchase data is searched, the determination result of step SC16 becomes “YES”, the process proceeds to step SC18, and the purchase_db [i] [3] flag st of the corresponding purchase data is st.
The "us" is set to "2" to invalidate the usage right, and then the execution ends.

As described above, in the expiration date management processing, every time a timer event occurs in the idle state, the purchase history database 10 is searched for purchase data whose usage limit has been released, and the expiration date of the corresponding purchase data is expired. If it has expired, the usage right is invalidated, and if it has not expired, the remaining time rem according to the elapsed time from the cancellation time to the current time
Update ainTime. Then, when the execution of the client software 12 is completed, the purchase history database 10 is searched for purchase data for which usage restrictions have been released, and the right to use the corresponding purchase data is invalidated and execution is completed.

As described above, according to the present embodiment, the user terminal 1 has the purchase I for identifying the purchased usage right.
D, a purchase history database 1 that stores and manages purchase data including a flag indicating the state (unused, in use, and invalid) of the usage right corresponding to the purchase ID and the remaining time of the usage right.
0, while site 2 has user I
D, last purchase I sent from the user terminal 1 side at the time of purchase I
D and usage rights sold (usage restriction release file LF)
A sales history database 22c for storing and managing sales history data including a flag IsDownload indicating whether or not has been downloaded to the user terminal 1;
When there is a purchase request from the user terminal 1, the site 2 side searches the sales history database 22c based on the user ID included in the purchase request and determines whether or not there is a sales history.

If there is a sales history, it is determined whether or not the usage right (usage restriction release file LF) is incompletely downloaded based on the flag IsDownload in the corresponding sales history data. If the usage right is incomplete, the usage restriction is released free of charge. Since the file LF is downloaded to the user terminal 1,
If the usage right purchased by the user cannot be properly exercised, the usage right can be provided free of charge. If downloaded, sales history database 22
If the purchase history of the previous purchase and the purchase ID of the previous purchase are matched from c, and if the purchase history of the previous purchase and the purchase purchase of the previous purchase match, it is considered as a repurchase request due to the expiration of the usage right of the regular purchase, and it is free of charge. Use restriction release file LF to user terminal 1
To download. In this case as well, the usage right can be provided free of charge. On the other hand, when the purchase history of the previous time and the purchase history of the previous time do not match, it is considered that the usage right is not officially purchased, and as a result of notifying the user terminal 1 of the new purchase, the purchase ID is falsified on the user terminal 1 side. Can be prevented.

On the user terminal 1 side, the file size of the usage restriction release file LF downloaded from the site 2 is inspected, and if it is proper, it overlaps with the purchase ID extracted from the usage restriction release file LF purchased this time. It is determined whether the purchase ID is registered in the purchase history database 10. If a duplicate purchase ID is registered, the purchase ID is considered to be falsified or falsified, and the use right (purchase restriction release file LF) purchased this time is invalidated. It can prevent unauthorized use of rights.

On the other hand, if there is no duplicate purchase ID, the usage right (usage restriction release file LF) purchased this time is set to an unused state, or the effective time of the use restriction release file LF is newly registered. Purchase data to be generated is generated and registered in the purchase history database 10. If the client software 12 has been activated, the registered purchase data in the unused state is changed to the function being used to release the use restriction. When the client software 12 is running, the purchase history database 10 is searched for purchase data for which usage restrictions have been released for each timer event, and the usage right is invalidated if the corresponding purchase data has expired, If not expired, the remaining time remainTime is updated according to the elapsed time from the release time to the current time. Then, the purchase history database 10 is searched for purchase data whose usage restrictions have been released just before the client software 12 finishes executing, and the usage right of the corresponding purchase data is invalidated and execution ends, resulting in the expiration date of the usage right. Can be managed, and thus it is possible to prevent unauthorized use of the sold usage right.

[0063]

According to the invention described in claims 1 and 2, the site side selling the usage right via the network determines whether or not there is a sales history regarding the user terminal in response to a purchase request from the user terminal. Search the sales history database, if there is a sales history, refer to the contents to determine whether the usage right sold has been downloaded, and if it is determined that the usage right has not been downloaded, or if it has been downloaded, the sales history If the sales history of the previous time and the previous sales time retrieved from the database match, the usage right will be downloaded to the user terminal that issued the purchase request free of charge. Due to a problem with the download, the download may not be performed normally, or the right to use may not be issued when a repurchase request is made due to the expiration of the right to use. In can be provided to the user terminal side. In addition, the user terminal searches the purchase history database for a purchase ID that duplicates the purchase ID included in the usage right purchased this time, and if a duplicate purchase ID is found, the purchase ID is tampered or altered to be an unauthorized one. Since the usage right purchased this time is regarded as invalid, it is possible to prevent the illegal use of the sold usage right. According to the inventions of claims 3 and 4, if there is a sales history and the download is not completed, it is judged that the properly purchased usage right cannot be properly exercised, and the usage right is provided free of charge. it can. Also, even if there is a sales history and it has been downloaded, if the purchase history of the previous and the previous two times is the same, it is considered as a re-purchase request due to the expiration of the usage right of the legitimate purchase, In this case as well, it is possible to provide the usage right free of charge by judging that the usage right that has been legally purchased cannot be properly exercised. Further, when the purchase history of the previous time and the purchase history of the previous time do not match, the user terminal is notified of the new purchase assuming that the usage right has not been officially purchased, and thus the purchase ID is falsified on the user terminal 1 side. Can be prevented. According to the invention described in claims 5 and 7,
If a purchase ID that is the same as the purchase ID included in the usage right purchased this time is registered in the purchase history database, the purchase ID is considered to be falsified or altered and the usage right purchased this time is invalidated. Therefore, it is possible to prevent unauthorized use of the sold usage right. On the other hand, if there is no duplicate purchase ID, purchase data to be newly registered, such as setting the usage right purchased this time to an unused state or setting the valid time of the usage right, is created and used as the purchase history database. When registered in 10, the registered purchase data in the unused state is changed to use the function to release the use restriction of the software, and if the software whose release the use restriction has been released is operating, the function is in use. When the purchase history database is searched for purchase data with a status flag at regular intervals, and the expiration date of the searched purchase data is expired, the status represented by the status flag of the purchase data is changed to usage right invalid and expired. Otherwise, the expiration date of the usage right can be managed as a result of updating the expiration date according to the elapsed time from the time when the usage restriction is released, and thus the illegal use of the sold usage right It is possible to prevent the use. According to the inventions of claims 6 and 8, when the software is about to end execution,
The purchase data whose usage restrictions have been released is searched from the purchase history database, the status flag of the corresponding purchase data is changed to the usage right disabled state, and the software is terminated. Can manage
Therefore, it is possible to prevent unauthorized use of the sold usage right.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of a sales processing system according to an embodiment of the present invention.

FIG. 2 is a purchase history database 1 provided in the user terminal 1.
It is a figure which shows the structure of 0.

FIG. 3 is a sales information stack SS included in the management server 21.
It is a figure which shows the structure of.

FIG. 4 is a diagram showing a configuration of a user database 22b included in the site 2.

FIG. 5 is a sales history database 22c included in the site 2
It is a figure which shows the structure of.

FIG. 6 is a sales processing flow showing the overall operation of the sales processing system.

FIG. 7 is a diagram showing a configuration example of a usage restriction release file LF.

FIG. 8 is a flowchart showing an operation of sales history confirmation processing.

FIG. 9 is a flowchart showing an operation of a usage restriction releasing process.

FIG. 10 is a flowchart showing an operation of purchase history inspection processing.

FIG. 11 is a flowchart showing an operation of a cancellation process.

FIG. 12 is a flow chart showing the operation of the expiration date management processing.

[Explanation of symbols]

1 user terminal 2 sites 10 purchase history database 11 History management software 12 Client software 13 Web browser 20 Web server 21 Management server 22 Database 22a content database 22b User database 22c Sales history database 40 payment system

Claims (8)

[Claims] 1. A device provided in a site that sells a usage right via a network and a user terminal equipped with software whose usage restriction is released by the usage right purchased from this site, wherein the site is In response to a purchase request from the user terminal, a sales history database unit that stores and manages a sales history is searched from the sales history database unit for the presence or absence of a sales history related to the user terminal. If the determination means determines whether the usage right sold by reference has been downloaded, and if this determination means determines that the download is not completed,
Alternatively, even if it has been downloaded, it is provided with a download means for downloading the usage right to the user terminal which issued the purchase request free of charge, when the sales history of the previous time and the sales history of the time before last searched from the sales history database means match, The user terminal stores and manages a purchase history, a purchase history database unit, and a purchase ID that is downloaded from the site and that is the same as the purchase ID included in the usage right purchased this time. A sales processing device comprising: an invalidating unit that invalidates the usage right purchased this time when the purchase ID is searched. 2. A processing method executed by a site that sells a usage right via a network and a user terminal equipped with software whose usage restriction is released by the usage right purchased from the site, wherein the site Then, in response to a purchase request from the user terminal, the presence or absence of a sales history regarding the user terminal is searched from a sales history database that stores and manages the sales history, and if there is a sales history, the contents are referenced to sell. In the judgment process of judging whether the usage right has been downloaded, and in the judgment process, if the download is not completed,
Alternatively, a download process of downloading the usage right to the user terminal that has issued the purchase request free of charge when the previous sales history and the previous sales history retrieved from the sales history database match even if it has been downloaded, The user terminal searches the purchase history database that stores and manages the purchase history for a purchase ID that is downloaded from the site and that is included in the usage right purchased this time, and if a duplicate purchase ID is found, A sales processing method comprising: a revocation process for revoking the usage right purchased this time. 3. A device provided on a site side that sells a usage right in response to a purchase request from a user terminal accessed via a network, wherein the user ID is sent from the user terminal at least when the purchase request is made. , A sales history storage unit that stores sales history data including a previous purchase ID and a download flag indicating whether or not the sold usage right has been downloaded to the user terminal side, and the sales history storage unit stores the sales history data based on the user ID included in the purchase request. First searching for the presence or absence of the corresponding sales history from the sales history storage means
When the sales history is searched by the search means of and the first search means,
A determination means for determining whether or not the usage right has been downloaded by referring to the download flag in the searched sales history data, and when the determination means determines that the download is not completed, the usage right is given to the corresponding user free of charge. First to download
Download means, a second search means for searching the sales history storage means for a previous purchase ID and a purchase ID two times before, and a second search means when the determination is made by the determination means. If the previous purchase ID and the previous purchase ID are the same, the second download means for downloading the usage right to the relevant user free of charge, and the previous purchase ID and the previous purchase ID searched by the second searching means. A sales processing device comprising: a notification means for notifying the user of a new purchase when the usage right is regarded as not being properly purchased. 4. A method of being processed by a site selling a usage right in response to a purchase request from a user terminal accessed via a network, wherein the user is sent out at least at the time of the purchase request. A sales history database that stores sales history data including an ID, a previously purchased ID, and a download flag indicating whether or not the sold usage right has been downloaded to the user side is provided, and the sales history database stores the sales history data based on the user ID included in the purchase request. The first search process of searching the sales history database for the presence or absence of the corresponding sales history, and when the sales history is searched in the first search process, the download flag in the searched sales history data is referred to. And the judgment process to judge whether the usage right has been downloaded. If,
In the first download process in which the usage right is downloaded to the corresponding user free of charge, and when it is determined that the download is completed in the determination process,
If the previous purchase ID and the previous purchase ID searched in the second search process and the second purchase process for searching the previous purchase ID and the previous purchase ID from the sales history database match, the corresponding user is free of charge. When the second download process of downloading the usage right with the previous purchase ID and the purchase ID before the second searched in the second search process do not match, it is considered that the usage right is not officially purchased. And a notification process for notifying the user of new purchase. 5. A device for managing the expiration date of software operating on the user terminal according to the usage right purchased from the site via the network, wherein at least the purchase ID for identifying the purchased usage right and the status of the usage right are displayed. A purchase history storage unit that stores purchase data including a status flag and an expiration date, and a purchase ID that is downloaded from the site side according to the purchase and that is the same as the purchase ID included in the usage right purchased this time.
First search means for searching whether or not is stored in the purchase history storage means, and if a duplicate purchase ID is searched by the first search means, the use right purchased this time is invalidated. And a new purchase data including a status flag indicating that the right to use purchased this time is in an unused state and a valid time of the right to use when the duplicate purchase ID is not searched by the searching unit. Registration means for generating and registering in the purchase history storage means, and use of the software by changing the state represented by the status flag of the new purchase data registered in the purchase history storage means by the registration means to use the function. When the software whose usage restrictions are canceled by the cancellation means for canceling the restrictions is in operation, the purchase data having a status flag indicating that the function is in use Second retrieval means for retrieving data from the purchase history storage means at regular time intervals, and if the expiration date of the purchase data retrieved by the second retrieval means has expired, the status flag of the purchase data indicates A sales processing device, comprising: a expiration management unit that changes the state to invalid usage right and updates the expiration date according to the elapsed time from the time when the usage restriction is released if the expiration date has not expired. 6. The expiration date management means searches the purchase history storage means for purchase data for which usage restrictions have been released just before the execution of the software ends, and invalidates the status flag of the corresponding purchase data. The sales processing device according to claim 5, wherein the execution of the software is terminated after the state is changed to the above state. 7. A method of managing the expiration date of software operating on the user terminal side according to the usage right purchased from a site via a network, wherein at least a purchase ID for identifying the purchased usage right and a status of the usage right are displayed. A purchase history database that stores purchase data including a status flag and an expiration date is stored, and a purchase ID that is downloaded from the site according to the purchase and that is the same as the purchase ID included in the usage right purchased this time is used.
The first search step for searching whether or not is stored in the purchase history database, and if a duplicate purchase ID is searched in the first search step, the use right purchased this time is invalidated. And a new flag having a status flag indicating that the usage right purchased this time is in an unused state and a valid time of the usage right when the duplicate purchase ID is not searched by the first searching means. A registration process of generating new purchase data and registering it in the purchase history database, and changing the state represented by the status flag of the new purchase data registered in the purchase history database during the registration process to use the function. A release process of releasing the use restriction of the software, and a purchase flag having a status flag indicating that the function is in use when the software whose use restriction is released by the release process is in operation. A second search step of searching the purchase history database for incoming data at regular time intervals, and if the purchase data searched in the second search step has expired, the status flag of the purchase data is changed. A sales processing method comprising: changing the state shown to invalidation of the usage right; and, if not expired, updating the expiration date according to the elapsed time from the time when the usage restriction is released. 8. The expiration date management process searches the purchase history database for purchase data for which usage restrictions have been released just before the software finishes executing, and sets a status flag of the corresponding purchase data to indicate that the usage right is invalid. 8. The sales processing method according to claim 7, wherein execution of the software is terminated after changing to the state.