JP4336291B2 - Receiving terminal device - Google Patents

Description

  The present invention relates to a receiving terminal device having a function of receiving information broadcast by a center device and processing the received information.

  In recent years, services that multiplex and broadcast information other than video and audio have been provided in the broadcasting field. A receiving terminal device that receives such a new service has a function of executing software for using the new service and a function of receiving the software itself.

  Conventional pay broadcasting services include a service for viewing by setting a reception contract by setting a period such as a monthly pole and a service for viewing by performing a reception contract for each individual data. A service that sets a period and makes a reception contract can use the service any number of times during the contract period once a reception contract is made. A service that performs a reception contract for each piece of data downloads necessary data when necessary, and pays a fee for the downloaded data. A technique for realizing this service is disclosed in JP-A-8-32530.

  The known technique described in this publication will be described with reference to FIG.

  In the data transmission device 3801, first, multimedia data 3802 is supplied to a scrambler 3803 and scrambled using a scramble key 3804 that is periodically changed. The scramble key is also supplied to the encryption unit 3805 and encrypted using the scramble master key 3806. Here, the scramble master key is different for each type of multimedia data, and is changed periodically or irregularly.

  The encryption unit 3805 is also supplied with the common information 3807 and the work key 3808, and the scramble key 3804 and the common information 3807 are encrypted using the work key 3808. The encrypted data is supplied to the multiplexing unit 3809 as related information.

  The multiplexing unit 3805 multiplexes the scrambled multimedia data 3802 supplied by the scrambler 3803 and the related information supplied by the encryption unit 3805, and transmits the multiplexed data to the data reception device 3811 by the transmission circuit 3810.

  In the data reception device 3811, the reception circuit 3812 receives the digital signal and outputs it to the signal separation circuit 3813. The signal separation circuit 3813 separates the multimedia data and the related information from the input signal, outputs the multimedia data to the descrambler 3814 and outputs the related information to the decoding circuit 3815.

  The decryption circuit 3815 decrypts the related information using the work key 3817 recorded on the IC card 3816. The encrypted scramble key as the decryption result of the related information is output to the scramble key decryption circuit 3818, and the data identifier included in the common information is output to the download determination unit 3819.

  The IC card 3816 is supplied to the contractor by concluding a reception contract with the information provider. The work key 3817, the contract content 3820, the information fee 3821, the scramble master key 3822, and the accounting total 3823 are recorded in advance. . The recorded contents of the IC card 3816 are periodically changed and supplied to the contractor whenever there is a change.

  In the contract contents of the IC card, a data identifier corresponding to the multimedia data for which the reception contract has been made is recorded. In the information fee, a fee for each download of each type of data is recorded. The scramble master key 3822 is the same as the scramble master key 3806. The accounting total records the total value of the charges read from the information charges.

  Upon receiving the data identifier, the download determination unit 3819 determines whether there is the same data identifier in the contract contents of the IC card 3816 and the download request unit 3824. If the same data identifier exists in both, the download determination unit 3819 corresponds to the data identifier. The scramble master key 3822 to be read is read from the IC card 3816 and transferred to the scramble key decryption circuit 3818. Here, the contractor selects what he / she wants to download in advance in the download request unit 3824, and the data identifier is recorded.

  The scramble key decryption circuit 3818 decrypts the encrypted scramble key with the scramble master key 3822 and sends it to the descrambler 3811. The descrambler 3811 decodes data corresponding to the scramble key in the multimedia data, and records the data in the MO 3825.

  In addition, the download determination unit 3819 extracts the fee corresponding to the scramble master key 3822 from the information fee 3821 and adds the amount to the accounting total 3823. The accounting information totaling circuit 3826 periodically accesses the accounting total 3823 of the IC card 3816 and transmits the amount to a center station (not shown) where the data transmission device 3801 is located.

  However, in the technical idea disclosed in Japanese Patent Application Laid-Open No. 8-32530, the contractor makes a download reception contract in order to obtain the desired data and selects the data desired to be downloaded in advance. It takes time and effort. Further, every time download or reading from the MO, a charge is added to the billing summary, so if the same data is downloaded or read twice, a double charge is made. Furthermore, since it is recorded on a removable medium such as an MO, it is likely to be an object of unauthorized copying. Furthermore, since the IC card, which is a portable storage device, is exchanged regularly and irregularly, inconveniences such as wasteful costs for both the pay data distributor and the contractor occur.

  From the viewpoint of the contractor, it is not desirable to charge each time the data is used many times, such as software. In addition, it is desirable that data once charged is usable on any receiving terminal device in the home, for example. Therefore, it is not desirable to be charged for each download. In order that the data for which the contractor is charged can be used on all the receiving terminal devices, a mechanism capable of storing paid data on all the receiving terminal devices without being charged at the time of downloading is required. However, in this case, a person other than the contractor who purchased the paid data can also use the paid data, and a contractor who has not purchased the data can illegally use the paid data.

  In the present invention, a contractor who has contracted receiving a pay broadcast can immediately purchase only necessary pay data without regularly or irregularly changing the portable storage device. It is intended to make it possible to use it on any receiving terminal device any number of times and to prevent a contractor who has not purchased paid data from illegally using the paid data.

The receiving terminal device according to the present invention is a receiving terminal device connectable to a center device via a network, and includes a storing means for storing software, and a matching means for obtaining an attribute value of the software stored in the storing means Charging means for charging software stored in the storage means with the center apparatus, execution means for executing software stored in the storage means, and receiving a request from a user Software for managing the stored software information, which is information related to the software stored in the storage means, and a selection means for passing the processing execution right to the accounting means or the execution means based on the attribute value of the software Pluggable removable storage device that manages management software and available software information consisting of a list of available software names And a portable storage device operating unit that reads and writes available software information managed by the portable storage device, and the verification unit receives the request from the selection unit and receives the request from the selection unit Obtaining usable software information from the portable storage device via the portable storage device operating means, collating the acquired usable software information with the stored software information managed by the software management means, The attribute value of the software that has received the request from the selection unit is obtained, the obtained attribute value is passed to the selection unit, and the charging unit obtains the execution right from the selection unit that received the attribute value from the matching unit Then, a billing process is executed, and the software name of the software that has received a request from the user is entered through the portable storage device operating means. Writing in the available software information device manages, receives the write completion notification from the portable storage device operating means, a software name software having received the request from the user to the execution means passes said In this case, the verification means includes a software name, a software fee, a character string briefly explaining the software, a use permission flag indicating whether or not the software is used, and the software A first step of preparing a stored software verification result table having an element of a storage flag indicating whether or not the data is stored in the storage means; a software name, a software fee, and a software for all entries of stored software information A character string that briefly describes the software is copied to the stored software verification result table, all use permission flags are set to 0, and all A second step for setting the storage flag to 1, a third step for marking the first line of the available software information as a read mark, and a check software for checking the entry of the line with the read mark for the usable software information. A fourth step for extracting as a software name, a fifth step for determining whether a check software name exists in the stored software verification result table, and a check software name exists in the stored software verification result table When performing the sixth step of setting the use permission flag of the entry including the software name in the stored software verification result table to 1, and when the checking software name does not exist in the stored software verification result table Is an entry with the software name as the check software name in the stored software verification result table. The newly added entry software fee for the newly added entry and the character string that briefly describes the software are emptied, the seventh step of setting the use permission flag = 1 and the storage flag = 0, and usable software information If it is possible to move the readout mark of the available software information to the next line in the eighth step of determining whether the readout mark of the next software can be moved to the next line, and the eighth step, the readout mark of the available software information is moved to the next line. And the ninth step of returning to the fourth step, the obtained usable software information is collated with the stored software information managed by the software management means, and the stored software collation result Based on the table, as the attribute value of the software that has received the request from the selection means, the usage permission flag is stored in the stored software verification result table. = 0, storage flag = 1 if attribute value = 01, billing process, usage flag = 1, attribute value consisting of storage flag = 0, unavailable, usage flag = 1, storage flag When the attribute value consisting of = 1 = 11, the attribute value meaning “usable” is obtained .

  According to the present invention, software stored in advance in the software storage means cannot be used unless purchased, so that the copyright and license of the software can be protected, and the user can connect to the receiving terminal device. Of the stored unpurchased software, it is possible to purchase only the desired software and use it as many times as possible. For the unused software already stored in the software storage means when purchasing the receiving terminal device This has the effect of eliminating the need to pay a fee.

  In addition, a software vendor that supplies software that operates on a broadcast center having a center device and a receiving terminal device uses a recording medium that can be used by an external storage device to receive a new reception that is not stored in the receiving terminal device. It becomes possible to supply the software for the terminal device to the user, and the user has an effect that the options of the software to be purchased are expanded.

  Furthermore, the center device and the software vendor can immediately supply software for a new receiving terminal device not stored in the receiving terminal device to the user, and the user is transmitted from the center. It has the effect that it becomes possible to download existing download software and use it immediately.

  Further, the receiving terminal device can identify a plurality of software having the same name but different versions, and the software vendor has an effect that the version can be assigned to the software.

(Embodiment 1)
FIG. 1 shows a configuration example of a software execution management system that uses software stored in a receiving terminal device 101 in a receiving terminal device 101 having a software performance management mechanism of the present invention. In FIG. 1, 101 is a receiving terminal device that receives information broadcast by the center device 103, 102 is user identification information that is given to a user who has a software use contract with the center device 103, and identifies the user. A portable storage device that manages available software information consisting of a list of software names that can be used by the user, 103 is a center device that broadcasts information to the receiving terminal device, and 104 is removable from the portable storage device 102 A portable storage device operating means for reading and writing software names managed by the portable storage device 102, 105 for software storage means for storing software, and 106 for storing in the software storage means 105. Name of the software being used, price, character string briefly describing the software, software rating Software management means for managing software storage information including storage locations in the means 105 and controlling execution of software; 107, software information available from the portable storage device operating means 104 and software management means 106; Check the software storage information managed by the software name, the software fee, the flag indicating whether the software name is included in the available software information, and the software name in the software storage information. Storage software verification means 108 for generating and managing a stored software verification result table having a flag indicating whether it is included or not, and 108 has a function of accepting a software selection menu display request and a software execution request from the user. Stored software verification result received from stored software verification means 107 The software selection means 109 responds to the user's request based on the table, and 109 includes the software name selected by the user by the software selection means 108 and the user identification information received from the portable storage device operation means 104. Billing means for outputting the billing information to the sending means A110 and outputting the software name to the portable storage device operating means 104, 110 for sending the billing information sent from the billing means 109, 111 for sending from the sending means A110 Transmission means A and 112 for transmitting data to be transmitted receive accounting information from the transmission means A111 and output the accounting information to the accounting processing means 115. Receiving means A and 113 are software names and software for all software. Software fee management means 114 for managing software fee information including the fee of the wear, User management means having user information consisting of user identification information and account number of the user, 115 charging information received from the receiving means A112, user information received from the user management means 114 and software charge management means Billing processing means for collating the software fee information received from 113 and outputting the user's account number and software fee to the transmission means B116. Transmission for transmitting the data received from the billing processing means 115 to the financial system Means B and 117 are software execution means for receiving the software name selected by the user by the software selection means 108 and issuing an execution request for the software to the software management means 106.

  The operation of the software execution management system configured as described above will be described below.

  The portable storage device 102 is delivered from a broadcast center (not shown) having the center device 103 to a user who has made a software use contract with the center device 103 in a state where user identification information of the user is recorded. An example of the portable storage device 102 is an IC card. As shown in FIG. 2, the portable storage device 102 records user identification information and a list of software names to which the user is permitted to use as usable software information. The user always inserts the portable storage device 102 into the insertion port of the portable storage device operating means 104 before using the software.

  The software management means 106 of the receiving terminal device 101 has the table shown in FIG. 3, the software name of the software stored in the software storage means 105, the price of the software, a character string that briefly describes the software, The software storage location is managed as stored software information.

  When using the software, the user inputs a software selection menu display request to the software selection means 108 by remote control operation (not shown). The software selection means 108 that has received the software selection menu display request issues a stored software verification request to the stored software verification means 107. Upon receiving the stored software verification request, the stored software verification unit 107 issues a request for reading available software information to the portable storage device operating unit 104. In response to the request for reading available software information, the portable storage device operating unit 104 reads the available software information from the portable storage device 102 and passes the available software information to the stored software verification unit 107.

  The storage software collation means 107 that has received the usable software information reads the storage software information managed by the software management means 106 and performs a storage software collation process for collating with the usable software information. The flow of the stored software verification process will be described with reference to FIG. Software name, software fee, character string briefly describing the software, use permission flag indicating whether or not the software is licensed, and the software is stored in the software storage means 105 A stored software collation result table having an element called a storage flag indicating whether or not there is prepared is prepared (step 401). For all entries in the stored software information, copy the character string that briefly describes the software name, software fee, and software to the stored software verification result table, set all use permission flags to 0, and set all stored flags to 1 (step 402). A read mark is added to the first line of the available software information (step 403). An entry in a line with a read mark of available software information is taken out as a check software name (step 404). It is determined whether the check software name exists in the stored software verification result table (step 405). If the check software name exists in the stored software verification result table, the use permission flag of the entry including the software name in the stored software verification result table is set to 1 (step 406). If the check software name does not exist in the stored software verification result table, an entry having the software name as the check software name is newly added to the stored software verification result table. The software fee of the newly added entry and the character string briefly describing the software are emptied, and the use permission flag = 1 and the storage flag = 0 are set (step 407). It is determined whether the read mark of the available software information can be moved to the next line (step 408). If the read mark of available software information can be moved to the next line in step 408, the read mark of available software information is moved to the next line, and the process returns to step 404 (step 409). If it is not moved in step 408, the process ends. FIG. 5 shows a stored software verification result table generated from the usable software information of FIG. 2 and the stored software information of FIG. 3 by this verification processing. Since both the software 501 and 502 appear in the usable software information and the stored software information, both the use permission flag and the storage flag are set to 1 through steps 405 and 406. Since 503 and 504 are software that appears only in the stored software information, the steps after step 404 are not performed, so only the storage flag is an entry. Since 505 and 506 are software that appears only in the available software information, the use permission flag is 1 through steps 405 and 407, and there is no character string that briefly describes the software fee and software. The stored software verification unit 107 passes the generated stored software verification result table to the software selection unit 108.

  The software selection unit 108 that has received the stored software verification result table from the stored software verification unit 107 performs software selection menu generation processing based on the stored software verification result table. The software selection means 108 has the attribute table shown in FIG. 6, and obtains the software attribute by comparing the use permission flag and the storage flag of each entry of the attribute table with the software selection table in the software selection menu generation process. The description of FIG. 6 will be given. In FIG. 6, the attribute value is a 2-bit binary number, and each bit of the attribute value corresponds in turn to a use permission flag and a storage flag. Reference numeral 601 denotes a use permission flag = 0, an attribute value of storage flag = 1 = “01”, and software having this attribute value can be used as long as it has been stored in the receiving terminal device 101 and charged. This attribute is called “billing”. 602 is charged with attribute value = '10 ', but since the software itself is not stored in the receiving terminal device 101, software having this attribute value cannot be used. This attribute is called “unusable”. 603 can be used because the attribute value = '11 'is charged and stored in the receiving terminal device 101. This attribute is called “available”.

  The software selection means 108 selects the software name of each entry of the software selection table, the price of the software, the character string briefly explaining the software, and the character string briefly explaining the attribute from the software selection menu. A menu screen is displayed on a screen (not shown). Here, software charges are not displayed for items whose use permission flag is 1. For example, since 501 in FIG. 5 is the use permission flag = 1 and the storage flag = 1, the attribute value is “11”, the attribute can be used, and the software for displaying the “HTML Browser, HTML file on the software selection menu screen” “Available” is displayed. The user selects one entry in the software selection menu and inputs a software execution request. However, an entry having an unavailable attribute in the software selection menu cannot be selected.

  A display example of the software selection menu screen generated from the stored software verification result table of FIG. 5 is shown in FIG.

  In response to the software execution request, the software selection means 108 performs billing execution selection processing. The charging execution selection process will be described with reference to FIG. The software selection means 108 obtains an attribute from the attribute value of the entry selected by the user (step 801). It is checked whether the attribute is “billing” or “available” (step 802). If the attribute is “charging” in step 802, the software name of the selected entry is passed to the charging means 109 (step 803). If the attribute is “available” in step 802, the software name of the selected entry is software executing means. 117 (step 804).

  When the charging unit 109 receives the software name, it executes the receiving terminal device charging process. The receiving terminal device billing process will be described with reference to FIG. Upon receiving the software name, the billing unit 109 issues a user identification information acquisition request to the portable storage device operation unit 104 (step 901). Receiving the user identification information acquisition request, the portable storage device operating means 104 reads the user identification information from the portable storage device 102 and returns the user identification information to the charging means 109 (step 902). The charging unit 109 that has received the user identification information transmits a charging request including the user identification information and the software name to the center apparatus 103 using the transmission unit A110 (step 903). Further, the charging unit 109 issues a portable storage device write request including the software name to the portable storage device operating unit 104 (step 904). Receiving the portable storage device writing process, the portable storage device operating means 104 writes the received software name in the usable software information of the portable storage device 102 (step 905). The portable storage device operating means 104 issues a portable storage device write completion notification to the charging means 109 (step 906). Upon receiving the portable storage device write end notification, the billing unit 109 passes the software name to the software execution unit 117 (step 907).

  The software execution unit 117 that has received the software name passes a software execution request including the software name to the software management unit 106. The software management means 106 that has received the software execution request refers to the stored software information, recognizes the storage location of the corresponding software, and activates the software at the corresponding storage location of the software storage means 105.

  The billing processing means 115 of the center apparatus 103 that has received a billing request including user identification information and software name from the billing means 109 of the receiving terminal apparatus 101 using the transmitting means A110, transmission means A111, and receiving means A112 is the center billing process. Execute. The flow of the center billing process is shown in FIG. The billing processing unit 115 issues a software fee reference request including the software name to the software fee management unit 113 (step 1001). The software fee management means 113 having received the software fee reference request has the software fee table shown in FIG. 11 and takes one entry including the same software name as the software name received from the table. The software fee is returned to the billing processing means 115 (step 1002). Upon receiving the software fee from the software fee management unit 113, the billing processing unit 115 issues a user account reference request including user identification information to the user management unit 114 (step 1003). Upon receipt of the user account reference request, the user management means 114 finds one entry including the same user identification information as the user identification information received from the user management table shown in FIG. 12, and purchase software in the entry. The received software name is registered, and the user account number in the entry is returned to the accounting processing means (step 1004). Upon receiving the user account number from the user management unit 114, the billing processing unit 115 debits the software fee and the user account number from the user account to an external financial system (not shown) using the transmission unit B116. A request is issued (step 1005).

  As described above, in the first embodiment, the portable storage device 102 used in the receiving terminal device 101 that receives a digital broadcast has user identification information for identifying a user who has signed a software use contract and the user is authorized. Includes a mechanism for recording available software information including a list of software names of purchased software, a mechanism for storing the software in the receiving terminal device 101, a mechanism for detaching the portable storage device 102, and a portable storage device A mechanism capable of reading and writing the area of the available software information 102, and a mechanism for notifying the user that the user has purchased the software in the receiving terminal device 101 toward the center device 103 via an uplink, If the software name is not registered in the software information of the portable storage device 102, the software is useful. By providing an impossible mechanism, the user cannot use the software without purchasing the software in the receiving terminal device 101, so that the copyright and license of the software can be protected, and the user can receive the receiving terminal. Of the unpurchased software stored in the device 101, only the desired software can be purchased immediately and used any number of times, and the received terminal device 101 is not used when it is stored in the receiving terminal device 101 when purchased. No need to pay for software.

  Further, for example, a user who owns two or more receiving terminal devices 101 of the same model in a home purchases software stored in the receiving terminal device A on the receiving terminal device A, for example, and the software name is For example, when recorded in the portable storage device A, the software stored in the reception terminal device B is transferred to the reception terminal device B by replacing the portable storage device A with another reception terminal device B in the home. You can use the software without purchasing it. As a result, a user who owns two or more receiving terminal apparatuses of the same model in the home can avoid purchasing one software by the number of all receiving terminal apparatuses in the home. However, in this case, since the software name of the software is not recorded in the software information of the portable storage device for the receiving terminal device B, the portable storage device for the receiving terminal device B is attached to the receiving terminal device B. Even if it is installed, the software cannot be used on the receiving terminal device B.

  This protects the software license. In addition, even when a receiving terminal device is replaced due to a failure of the receiving terminal device, the portable storage device used on the old receiving terminal device is used on the new receiving terminal device. If the purchased software is stored in the new receiving terminal device, it can be used on the new receiving terminal device without purchasing the software again.

  The charging processing unit 115 of the center apparatus 103 that has received the charging request including the user identification information and the software name refers to the user payment arrears information in the user management table managed by the user management unit 114, and It is determined whether or not to allow the user who made the billing request to purchase the software subject to billing, and only when it is determined to permit it, the software license information is returned and the user's receiving terminal device The center determines that it is difficult to collect the fee by recording the software name in the portable storage device 102 only when the charging means 109 receives the software usage permission information after transmitting the charging request. Software can be prevented from being sold to users.

  In this case, if the price of the software to be purchased is within a certain price, the software can be written to the portable storage device 102 without waiting for the use permission from the center device. For software that is determined to be easy, the user can quickly use the software without waiting for the usage permission information by issuing a billing request.

  The charging unit 109 of the receiving terminal device 101 issues a software name write request to the portable storage operation unit 104 without issuing a charging request to the center device 103, and the charging processing unit 115 of the center device 103 periodically By accessing the charging means 109 of the receiving terminal device 101 and receiving the information for identifying the user and the software name list written in the portable storage device 102, the receiving terminal device 101 becomes the center each time software is purchased. There is no need to access the device 103, and it does not take time to purchase software.

(Embodiment 2)
FIG. 13 uses the software stored in the receiving terminal device 101 and the software stored in the external storage device 1301 connected to the receiving terminal device 101 in the receiving terminal device 101 having the software performance management mechanism of the present invention. 2 shows an example of the configuration of an external storage device software execution management system. In FIG. 13, reference numeral 1301 denotes an interface that can be connected to the receiving terminal device 101. A plurality of software, software names of the software, software fees, character strings that briefly describe the software, and software storage An external storage device for storing removable media in which external storage device information including locations is stored, and 1302 has an interface that can be connected to the external storage device 1301, and issues a read request and an execution request to the external storage device 1301 to issue a read request. If it is issued, external storage device information sent from the external storage device 1301 is received, and if an execution request is issued, external storage device operating means for executing the software in the external storage device 1301, 1303 is stored software verification means The stored software verification result table received from 107 The external storage device information that is returned when an external storage device information request is sent to the external storage device operating means 1302 is used to check the software name, the fee for the software, the character string that briefly describes the software, and the software name A flag indicating whether or not the software name is included in the software information, a flag indicating whether or not the software name is included in the stored software information, and whether or not the software name is included in the external storage device information External storage device software verification means for generating and managing an external storage device software verification result table in which the external media flag and the location of the external storage device 1301 in which the software is recorded are associated with each other, 117 is a software selection means 108 The software name selected by the user is received by the software management means 106 or the external storage device operator. 1302 is a software execution means to issue the software execution request.

  The portable storage device 102 is delivered from the center device 103 to the user who has made a software use contract with the center device 103 in a state where the user identification information of the user is recorded. An example of the portable storage device is an IC card. As shown in FIG. 2, the portable storage device 102 records user identification information and a list of software names to which the user is permitted to use as usable software information. The user always inserts the portable storage device 102 into the insertion port of the portable storage device operating means 104 before using the software.

  The software management means 106 of the receiving terminal device 101 has the table shown in FIG. 3, the software name of the software stored in the software storage means 105, the price of the software, a character string that briefly describes the software, The software storage location is managed as stored software information.

  When using the software, the user inputs a software selection menu display request to the software selection means 108 by remote control operation (not shown). The software selection means 108 that has received the software selection menu display request issues a software verification request to the external storage device software verification means 1303. Receiving the software verification request, the external storage device software verification unit 1303 issues a stored software verification request to the stored software verification unit 107. Upon receiving the stored software verification request, the stored software verification unit 107 issues a request for reading available software information to the portable storage device operating unit 104.

  In response to the request for reading available software information, the portable storage device operating unit 104 reads the available software information from the portable storage device 102 and passes the available software information to the stored software verification unit 107. The stored software verification unit 107 that has received the usable software information reads the stored software information managed by the software management unit 106 and compares it with the available software information received from the portable storage device operating unit 104. The collation process performs the same operation as the operation from step 401 to step 409 in FIG. FIG. 5 shows a stored software verification result table generated from the usable software information of FIG. 2 and the stored software information of FIG. 3 by this verification processing. The stored software verification unit 107 passes the generated stored software verification result table to the external storage device software verification unit 1303.

  The external storage device software verification unit 1303 that has received the stored software verification result table issues an external storage device information read request to the external storage device operation unit 1302. Upon receiving the external storage device information read request, the external storage device operating unit 1302 reads the external storage device information shown in FIG. 14 from the external storage device 1301 and passes it to the external storage device software verification unit 1303. The external storage device software verification means 1303 compares the external storage device information received from the external storage device operation means 1302 with the stored software verification result table. The flow of the external storage device verification process will be described with reference to FIG. External storage device software having elements such as software name, software fee, character string briefly describing the software, use permission flag, storage flag, external media flag, and storage location stored in the external storage device 1301 A verification result table is prepared (step 1501). For all entries in the stored software verification result table, the software name, software fee, character string briefly describing the software, use permission flag, and storage flag are copied to the external storage device software verification result table (step 1502). ). A read mark is added to the first line of the external storage device information (step 1503). A row with a read mark of the external storage device information is taken out as a check entry (step 1504). It is determined whether or not the same software name as that of the check entry exists in the entry of the external storage device software verification result table (step 1505). If an entry with the same software name as the software name of the check entry exists in the external storage device software verification result table, the external media flag of the entry in the external storage device software verification result table is set to 1, and the check entry The storage location element is copied to the entry storage location element (step 1506). If an entry with the same software name as the software name of the check entry does not exist in the external storage device software verification result table, the software name and software name of the check entry in the external storage device software verification result table Add an entry with the same elements as the charge and storage location. The use permission flag and storage flag of the newly added entry are set to 0, and the external media flag is set to 1 (step 1507). It is determined whether or not the read mark of the external storage device information can be moved to the next line (step 1508). The readout mark is moved to the next line, and the process returns to step 1504 (step 1509). If the readout mark cannot be moved to the next line in step 1508, the process is terminated. FIG. 16 shows an external storage device software verification result table generated from the external storage device information of FIG. 14 and the stored software verification result table of FIG. 6 by this verification processing. In FIG. 16, reference numeral 1601 denotes software registered in all available software information, stored software information, and external storage device information. Since 1602 is software registered in the usable software information and stored software information but not registered in the external storage device information, the storage location item is empty. Reference numeral 1603 denotes software that is not registered only in the available software information. Since 1604 is software registered only in the stored software information, the storage location item is empty. Reference numeral 1605 denotes software that is not registered only in the stored software information. Since 1606 is software registered only in the available software information, the software fee, the character string briefly describing the software, and the storage location items are empty. Reference numeral 1607 denotes software registered only in the external storage device information. The external storage device software verification unit 1303 passes the generated external storage device software verification result table to the software selection unit 108 for management.

  The software selection means 108 performs a software selection menu generation process based on the external storage device software verification result table received from the external storage device software verification means 1303. The software selection means 108 has the attribute table shown in FIG. 17 and collates the use permission flag, storage flag, and external media flag of each entry of the attribute table and the external storage device software verification result table in the software selection menu generation process. To determine the software attributes. The description of FIG. 17 will be given. In FIG. 17, the attribute value is a 3-bit binary number, and each bit of the attribute value sequentially corresponds to a use permission flag, a storage flag, and an external media flag. 1701 is a usage permission flag = 0, storage flag = 0, and external media flag = 1 attribute value = '001', which is not charged or stored, but exists in the external storage device 1301, so software having this attribute value. In order to use, the external storage device 1301 can be charged and used. The attribute of the software having the attribute value = “001” is referred to as “charging external storage device”. 1702 is software with attribute value = “010” or “011”, and the storage flag is 1, that is, software having this attribute value can be used as long as the receiving terminal apparatus 101 has already stored the fee. This attribute is called “billing”. 1703 is charged with attribute value = '100', but since the software itself is stored in both the receiving terminal device 101 and the external storage device 1301, software having this attribute value cannot be used. This attribute is called “unusable”. 1704 is charged with attribute value = “101” and can be used from the external storage device 1301. This attribute is called “external storage device available”. 1705 can be used because it has been charged with the software of attribute value = '110' or '111' and stored in the receiving terminal device 101. This attribute is called “available”. The software selection means 108 is a software selection menu, the software name of each entry of the external storage device software verification result table, the price of the software, a character string that briefly describes the software, and a character string that briefly describes the attribute Is displayed on a screen (not shown) as a software selection menu screen. Here, software charges are not displayed for items whose use permission flag is 1. For example, 1601 in FIG. 16 indicates that the use permission flag = 1, the storage flag = 1, and the external media flag = 1, so that the attribute value is “111” and the attribute can be used and “HTML Browser, HTML file is displayed on the software selection menu screen. Is now available ". The user selects one entry in the software selection menu and inputs a software execution request. However, an entry having an unavailable attribute in the software selection menu cannot be selected. FIG. 18 shows a display example of the software selection menu screen generated from the external storage device software verification result table of FIG.

  If the attribute of the entry selected by the software execution request is “billing external storage device” or “billing”, the software name and storage location of the selected entry are passed to the billing means 109. If the attribute of the entry selected by the software execution request is “available” or “external storage device available”, the software name and storage location of the selected entry are passed to the software execution means 117.

  When the charging unit 109 receives the software name and the storage location, the charging unit 109 executes a receiving terminal device charging process. The receiving terminal apparatus billing process performs the same operation as in steps 901 to 907 of FIG. However, in step 907, not only the software name but also the storage location is given to the execution means.

  Upon receiving the software name and storage location, the software execution means 117 performs software execution processing. The flow of software execution processing is shown in FIG. The software execution means 117 checks whether or not the received storage location is empty (step 1901). If the storage location is empty, the software execution means 117 passes a software execution request including the software name to the storage software management means 106 (step 1902). The software management means 106 that has received the software execution request refers to the stored software information, recognizes the storage location of the corresponding software, and activates the software at the corresponding storage location of the software storage means 105 (step 1903). ). If the storage location is not empty in step 1901, the software execution unit 117 issues a software execution request including the software name and storage location to the external storage device operation unit 1302 (step 1904). Receiving the software execution request, the external storage device operating means 1302 accesses the software indicated in the storage location and starts the software (step 1905).

  The billing processing means 115 of the center apparatus 103 that has received a billing request including user identification information and software name from the billing means 109 of the receiving terminal apparatus 101 using the transmitting means A110, transmission means A111, and receiving means A112 is the center billing process. Execute. The center billing process performs the same operation as step 1001 to step 1005 shown in FIG.

  As described above, when the receiving terminal device 101 of the software performance management system includes a mechanism that enables the software in the external storage device 1301 to be executed, the center device 103 and a software vendor (not shown) are included in the receiving terminal device 101. Software for a new receiving terminal device 101 that is not stored can be supplied to the user, and the user has a wider choice of software to purchase. For example, a CD-ROM, DVD-ROM, DVD-RAM, PD, MO, MD, ZIP, or IC card can be used as the external storage device 1301.

(Embodiment 3)
FIG. 20 shows a configuration example of a download software performance management system using the receiving terminal device 101 having the software performance management mechanism of the present invention. In FIG. 20, reference numeral 2001 denotes a software name of software that the center apparatus 103 downloads by download broadcasting, a character string that briefly describes the software, download software information including a channel through which the software flows, and a substance of the software to be downloaded. Download software management means for managing the software, and 2002 transmits the software name of the software that the center apparatus 103 broadcasts in the download broadcast, a character string that briefly describes the software, and the download software information including the channel through which the software flows. Download software list sending means 2003 for downloading, download software sending means 2003 for sending software according to instructions from the download software management means 2001, and 2004 for downloading Transmission means C and 2005 for multiplexing and transmitting the download software information sent from the load software list sending means 2002 and the software sent from the download software sending means 2003 transmit data sent from the sending means A110. The transmission means C and 2006 that receive the data from the transmission means C2005, download software information, and the reception means C and 2007 that output the data separately from the software. Download management that manages the download software information received from the reception means C2006 Means 2008 compares the stored software verification result table received from the stored software verification means 107 with the downloaded software information received from the download management means 2007 to check the software name, software fee, A character string briefly describing the software, a flag indicating whether the software name is included in the available software information, a flag indicating whether the software name is included in the stored software information, the software Download software verification means for generating and managing a flag indicating whether or not the software name is included in the download software information, a download software verification result table in which the software is downloaded and broadcast, and 2009 is software The download means downloads the software name from the receiving means C2006 upon receiving the software name selected by the user by the wear selection means 108 and the channel through which the software is downloaded and broadcast.

  The operation of the download software performance management system configured as described above will be described below.

  The download software management means 2001 has software entities and download software information shown in FIG. The download software management means 2001 associates the software entity with the channel for broadcasting each software and passes it to the download software sending means 2003, and passes the download software information to the download software list sending means 2002. The download software list sending means 2002 repeatedly sends the received download software information to the sending means C2004 for all channels. The download software sending means 2003 repeatedly sends the received software entity to the sending means C2004 through a channel designated by the software.

  The transmission means C2004 multiplexes and transmits the download software information received from the download software list transmission means 2002 and the software received from the download software transmission means 2003. The transmission means C2005 transmits the multiplexed data received from the transmission means C2004.

  The receiving means C2006 separates the multiplexed data received from the transmitting means C2005 into download software information and software. The download management means 2007 receives and manages download software information from the receiving means C2006.

  The portable storage device 102 is delivered from the center device 103 to the user who has made a download broadcast reception contract with the center device 103 in a state where the user identification information of the user is recorded. As shown in FIG. 2, the portable storage device 102 records user identification information and a list of software names to which the user is permitted to use as usable software information. The user always inserts the portable storage device 102 into the insertion port of the portable storage device operating means 104 before using the software.

  The software management means 106 manages stored software information of software stored in the software storage means 105 in the table shown in FIG.

  When using the software, the user inputs a software selection menu display request to the software selection means 108 by remote control operation (not shown). The software selection means 108 that has received the software selection menu display request issues a software verification request to the download software verification means 2008. Upon receiving the software verification request, the download software verification unit 2008 issues a stored software verification request to the stored software verification unit 107. Upon receiving the stored software verification request, the stored software verification unit 107 issues a request for reading available software information to the portable storage device operating unit 104. In response to the request for reading available software information, the portable storage device operating unit 104 reads the available software information from the portable storage device 102 and passes the available software information to the stored software verification unit 107.

  The stored software verification unit 107 that has received the usable software information reads the stored software information managed by the software management unit 106 and compares it with the available software information received from the portable storage device operating unit 104. The collation process performs the same operation as the operation from step 401 to step 409 in FIG. FIG. 5 shows a stored software verification result table generated from the usable software information of FIG. 2 and the stored software information of FIG. 3 by this verification processing. The stored software verification unit 107 passes the generated stored software verification result table to the download software verification unit 2008.

  Upon receiving the stored software verification result table from the stored software verification unit 107, the download software verification unit 2008 reads the download software information managed by the download management unit 2007, and compares the downloaded software information with the stored software verification result table. . The flow of download software verification processing will be described with reference to FIG. Software name, software fee, character string briefly describing the software, use permission flag, storage flag, download flag indicating whether or not the software can be downloaded, and channel for downloading the software A download software verification result table having elements is prepared (step 2201). For all entries in the stored software verification result table, the software name, software fee, character string briefly describing the software, use permission flag, and storage flag are copied to the downloaded software verification result table. At this time, the download flag = 0 and the channel = 0 are set (step 2202). A read mark is added to the first line of the download software information (step 2203). The entry in the line marked with the readout mark of the download software information is taken out as a check entry (step 2204). It is determined whether or not the same software name as the software name of the check entry exists in the entry of the download software verification result table (step 2205). If an entry with the same software name as the software name of the check entry exists in the download software verification result table, the download flag of the entry in the download software verification result table is set to 1, and the channel of the check entry is set to the entry Copy to the channel (step 2206).

  If an entry having the same software name as the software name of the check entry does not exist in the download software verification result table in step 2205, the software name of the check entry in the download software verification result table and the software fee Add an entry with the same element as the channel. The use permission flag and storage flag of the newly added entry are set to 0, and the download flag is set to 1 (step 2207). It is determined whether or not the read mark of the download software information can be moved to the next line (step 2208). The readout mark is moved to the next line, and the process returns to step 2204 (step 2209). If the readout mark cannot be moved to the next line in step 2208, the process is terminated. FIG. 23 shows a download software verification result table generated from the download software information of FIG. 21 and the stored software verification result table of FIG. 6 by this download software verification process. In FIG. 23, reference numeral 2301 denotes software registered in all available software information, stored software information, and download software information. Since 2302 is software registered in the available software information and stored software information but not registered in the download software information, the channel item is 0. Reference numeral 2303 denotes software that is not registered only in the available software information. Since 2304 is software registered only in the stored software information, the channel item is 0.

  Reference numeral 2305 denotes software that is not registered only in the stored software information. Since 2306 is software registered only in the available software information, the fee of the software, the character string briefly describing the software is empty, and the channel item is 0. Reference numeral 2307 denotes software registered only in the download software information. The download software verification unit 2008 passes the generated download software verification result table to the software selection unit 108 for management.

  The software selection unit 108 performs a software selection menu generation process based on the download software verification result table received from the download software verification unit 2008. The software selection means 108 has the attribute table shown in FIG. 24, and in the software selection menu generation process, the use permission flag, the storage flag, and the download flag of each entry in the attribute table and the download software verification result table are collated. Find the attributes of. The description of FIG. 24 will be given. In FIG. 24, the attribute value is a 3-bit binary number, and each bit of the attribute value sequentially corresponds to a use permission flag, a storage flag, and a download flag. 2401 is a use permission flag = 0, a storage flag = 0, and a download flag = 1 attribute value = '001', which is not charged and stored, and can be downloaded. Downloading to use software having this attribute value You have to pay later. The attribute of the software having the attribute value = “001” is called “download charge”. 2402 is software with attribute value = '010' or '011', and the storage flag is 1, that is, the software having this attribute value is already stored in the receiving terminal device 101, and it is not necessary to newly download it. it can. This attribute is called “billing”. 2403 is charged with the attribute value = '100', but since the software itself is not stored in the receiving terminal device 101 and cannot be downloaded, software having this attribute value cannot be used. This attribute is called “unusable”. 2404 is charged with attribute value = '101' and is not stored in the receiving terminal device 101, but can be used if it is downloaded. This attribute is called “download”. 2405 can be used because it has been charged by the software of attribute value = '110' or '111' and stored in the receiving terminal device 101. This attribute is called “available”. The software selection means 108 is a software selection menu in which the software name of each entry in the downloaded software verification result table, the price of the software, a character string that briefly describes the software, and a character string that simply describes the attribute It is displayed on a screen (not shown) as a wear selection menu screen. Here, software charges are not displayed for items whose use permission flag is 1. For example, in 2301 of FIG. 23, since the use permission flag = 1, the storage flag = 1, and the download flag = 1, the attribute value becomes “111” so that the attribute can be used and “HTML Browser, HTML file is displayed on the software selection menu screen. Is now available ".

  The user selects one entry in the software selection menu and inputs a software execution request. However, an entry having an unavailable attribute in the software selection menu cannot be selected. FIG. 25 shows a display example of the software selection menu screen generated from the download software verification result table of FIG.

  The software selection means 108 obtains an attribute from the attribute value of the entry selected by the software execution request, and if the attribute is download charge or download, the software name, use permission flag, and channel of the entry are used as download execution information. To pass. If the attribute of the entry selected by the software execution request is charging, the software name of the selected entry is passed to the charging unit 109. If the attribute of the entry selected by the software execution request is available, the software name of the selected entry is passed to the software execution means 117.

  The operation of the download unit 2009 that has received the download execution information will be described with reference to FIG. Software is received by specifying a channel in the download execution information to the receiving means C2006 (step 2601). A software storage request including the download execution information and the received software is issued to the software management means 106 (step 2602).

  A software storage completion notice is received from the software management means 106 (step 2603). The use permission flag in the download execution information is determined (step 2604). If the use permission flag is 1 in step 2604, the software name is passed to the execution means (step 2605). If the use permission flag is 0 in step 2604, the software name is passed to the billing means 109 (step 2606).

  Upon receiving the download execution information and the software storage request including the software from the download unit 2009, the software management unit 106 passes the software storage request including the software to the software storage unit 105. The software storage unit 105 that has received the software storage request stores the delivered software and returns the storage location to the software management unit 106. The software management means 106 given the storage location from the software storage means 105 receives the software name of the download execution information, the fee of the software, the character string briefly describing the software, and the software storage means 105. The stored location is added to the stored software information as a new entry, and a software storage completion notification is returned to the download means 2009.

  When the charging unit 109 receives the software name and the storage location, the charging unit 109 executes a receiving terminal device charging process. The receiving terminal apparatus billing process performs the same operation as in steps 901 to 907 of FIG.

  The billing processing means 115 of the center apparatus 103 that has received a billing request including user identification information and software name from the billing means 109 of the receiving terminal apparatus 101 using the transmitting means A110, transmission means A111, and receiving means A112 is the center billing process. Execute. The center billing process performs the same operation as step 1001 to step 1005 shown in FIG.

  The software execution unit 117 that has received the software name passes a software execution request including the software name to the software management unit 106. The software management means 106 that has received the software execution request refers to the stored software information, recognizes the storage location of the corresponding software, and activates the software at the corresponding storage location of the software storage means 105.

  As described above, if the receiving terminal device 101 of the software performance management system has a mechanism capable of receiving software download broadcasting, the center device 103 and a software vendor (not shown) are not stored in the receiving terminal device 101. The software for the receiving terminal device 101 can be immediately supplied to the user, and the user can immediately use the download software transmitted from the center device 103.

(Embodiment 4)
By the way, depending on the software, there is a software group in which the software name, which is information for identifying the software, is the same but the version is different by improving and upgrading the version.

  From the viewpoint of the contractor, when purchasing software, if the software is a new version of software that has already been purchased, it is desirable that the software can be purchased at a lower price than the newly purchased price.

  Therefore, in the download software performance management system shown in FIG. 20, the center device 103 broadcasts and adds the software version and the upgrade fee to the download software information managed by the download management means 2007 of the receiving terminal device 101. It is possible.

  The download software performance management system in this case is shown below.

  The download software management means 2001 has the software entity and the download software information with version shown in FIG. As in the second embodiment, the center apparatus 103 sends the software entity and version-added download software information from the download software sending means 2003.

  The portable storage device 102 is delivered from the center device 103 to the user who has made a download broadcast reception contract with the center device 103 in a state where the user identification information of the user is recorded. As shown in FIG. 28, the portable storage device 102 records user identification information and a list of software names and software versions to which the user is permitted to use as usable software information. The user always inserts the portable storage device 102 into the insertion port of the portable storage device operating means 104 before using the software.

  The software management means 106 manages stored software information of software stored in the software storage means 105 in the table shown in FIG.

  When using the software, the user inputs a software selection menu display request to the software selection means 108 by remote control operation (not shown). The software selection means 108 that has received the software selection menu display request issues a software verification request to the download software verification means 2008. Upon receiving the software verification request, the download software verification unit 2008 issues a stored software verification request to the stored software verification unit 107. Upon receiving the stored software verification request, the stored software verification unit 107 issues a request for reading available software information to the portable storage device operating unit 104. In response to the request for reading available software information, the portable storage device operating unit 104 reads the available software information from the portable storage device 102 and passes the available software information to the stored software verification unit 107.

  The stored software verification unit 107 that has received the usable software information reads the stored software information managed by the software management unit 106 and compares it with the available software information received from the portable storage device operating unit 104. The verification process of the stored software verification unit will be described with reference to FIG.

  Software name, software version, software fee, software fee due to version upgrade, character string briefly describing the software, usage permission flag indicating whether the software is licensed, Stored software verification result table having elements of a storage flag indicating whether or not the software is stored in the software storage means 105 and an upgrade flag indicating whether or not the software needs to be upgraded Is prepared (step 3001). For all entries in the stored software information, copy the software name, software version, software fee, software fee due to the upgrade, and a character string that briefly describes the software into the stored software verification result table. All use permission flags are set to 0 and all storage flags are set to 1 (step 3002). A read mark is added to the first line of the available software information (step 3003). The entry in the line marked with the readout of available software information is taken out as a check entry (step 3004). It is determined whether or not an entry having the same software name as the software name of the check entry exists in the stored software verification result table (step 3005). If it exists in step 3005, it is determined whether the software version of the check entry is lower than the software version of the corresponding entry in the stored software verification result table (step 3006). If it is determined in step 3006 that the value is low, the use permission flag of the corresponding entry in the stored software verification result table is set to 0, and the version upgrade flag is set to 1 (step 3007). If it is determined in step 3006 that the value is not low, the use permission flag of the corresponding entry in the stored software verification result table is set to 1, and the version upgrade flag is set to 0 (step 3008). If it does not exist in step 3005, an entry having the software name as the checking software name is newly added to the stored software verification result table. The newly added entry software charge, the software charge due to version upgrade, and the character string briefly describing the software are emptied, the use permission flag = 1, the storage flag = version upgrade flag = 0 (step 3009). It is determined whether the read mark of the available software information can be moved to the next line (step 3010). If the read mark of available software information can be moved to the next line in step 3010, the read mark of available software information is moved to the next line, and the process returns to step 3004 (step 3011). If it is not moved in step 3010, the process ends. FIG. 31 shows a stored software verification result table generated from the usable software information of FIG. 28 and the stored software information of FIG. 29 by this verification processing. The stored software verification unit 107 passes the generated stored software verification result table to the download software verification unit.

  The download software verification unit 2008 that has received the stored software verification result table from the stored software verification unit 107 reads the version-downloaded software information managed by the download management unit 2007, and the version-downloaded software information and the stored software verification result. Check the table. The flow of download software verification processing will be described with reference to FIG. Software name, software version, software fee, software fee due to version upgrade, character string briefly describing the software, usage permission flag, storage flag, whether the software can be downloaded A download flag indicating that the software is a version upgrade target and a download software verification result table having an element of a channel through which the software can be downloaded (step 3201). Download software name, software version, software fee, software fee due to upgrade, character string briefly describing software, usage permission flag, storage flag for all entries in stored software verification result table Copy to the software verification result table. At this time, the fee for software due to version upgrade is emptied, and download flag = 0 and channel = 0 are set (step 3202). A read mark is added to the first line of the version-downloaded software information (step 3203). A line with a read mark of the download software information with version is taken out as a check entry (step 3204). It is determined whether or not the same software name as that of the check entry exists in the entry of the download software verification result table (step 3205). If an entry with the same software name as the software name of the check entry exists in the download software verification result table, the software version of the check entry is the software version of the corresponding entry in the download software verification result table. It is determined whether it is higher than the version (step 3206). If it is determined that the software version is high, the download flag and the upgrade flag of the entry are set to 1, and the corresponding value in the software charge due to the upgrade of the check entry is set to the software charge due to the upgrade. And the channel of the check entry is copied to the channel of the entry (step 3207). If the software versions match or are low in step 3206, the download flag is set to 1, the version upgrade flag is set to 0, and the channel of the check entry is copied to the channel of the entry (step 3208). If an entry with the same software name as the software name of the check entry does not exist in the download software verification result table in step 3205, the software name and software version of the check entry in the download software verification result table Add an entry with the same elements as the software fee, a string that briefly describes the software, and the channel. The fee for the software due to the upgrade of the newly added entry is emptied, the use permission flag, the storage flag, the upgrade flag are set to 0, and the download flag is set to 1 (step 3209). It is determined whether or not the readout mark of the download software information with version can be moved to the next line (step 3210). The readout mark is moved to the next line, and the process returns to step 3204 (step 3211). If the readout mark cannot be moved to the next line in step 3210, the process ends. FIG. 33 shows a download software verification result table generated from the download software information of FIG. 27 and the stored software verification result table of FIG. 31 by this download software verification process.

  In FIG. 33, reference numeral 3301 denotes software recorded in the available software information. 3302 is software having the same name as 3301, but the version is higher than that of 3301 software. Therefore, the version upgrade flag is 1, and the version upgrade fee is written. The download software verification unit 2008 passes the generated download software verification result table to the software selection unit 108 for management.

  The software selection unit 108 performs a software selection menu generation process based on the download software verification result table received from the download software verification unit 2008. The software selection means 108 has the attribute table shown in FIG. 24, and in the software selection menu generation process, the use permission flag, the storage flag, and the download flag of each entry in the attribute table and the download software verification result table are collated. Find the attributes of. The attributes are the same as those in the second embodiment, and in particular, an attribute whose version upgrade flag is 1 is “version up”. For example, 3302 in FIG. 33 corresponds to the attribute “version up”.

  FIG. 34 shows a display example of the software selection menu screen generated from the download software verification result table of FIG. In the software selection menu screen, the software fee does not display items for which the use permission flag is 1, and displays the upgrade fee for items for which the upgrade flag is 1.

  The software selection unit 108 obtains an attribute from the attribute value of the entry selected by the software execution request, and proceeds with the process based on the attribute. The operation of the software selection means 108 that has received the download execution request is the same as in the second embodiment. However, the information passed to each means is the software name and software version.

  The charging processing means 115 of the center apparatus 103 that has received a charging request including user identification information, software name, and software version performs center charging processing. The center billing process will be described with reference to FIG. The billing processing unit 115 passes the received user identification information, software name, and software version to the user management unit 114 (step 3501). The user management means 114 collates the software name purchased by the user and the version of the software from the user management table, and determines whether or not this billing request is “version up” (step 3502). If it is determined in step 3502 that the billing request is for version upgrade, the billing processing unit obtains the corresponding version upgrade fee from the software fee management table managed by the software fee management unit 113 (step 3503). If it is determined in step 3502 that the charge request is not an upgrade, the charge processing unit 115 obtains the corresponding software fee from the software fee table managed by the software fee management unit 113 (step 3504). The billing processing means 115 receives the user account number from the user management table managed by the user management means 114, and transmits the user account number and software fee to an external financial system (not shown) using the transmission means B116. A charge debit request is issued from the user account (step 3505).

  Even if a version is added to the software identification information by the download software performance management system as described above, the receiving terminal device can determine that the software differs depending on the version, even if it has already been purchased. Even software having the same software name as that of software cannot be executed on the receiving terminal device, and the software license can be protected. Also, by providing a version upgrade fee structure, the user can purchase new software at a lower price than when purchasing a new version.

  However, it may not be possible to broadcast all versions of software with the same software name because of the broadcast bandwidth. In that case, the latest version of the software stored in the external storage device is processed by the external storage device operation means and the external storage device software verification means as in the present embodiment. The software group can be transmitted by download broadcasting, and the old version of the software group can be provided on a medium such as a PD that can be read by an external storage device.

The figure of the software execution management system in the 1st embodiment of the present invention The figure showing the user identification information and usable software information which are recorded on the portable storage device in the 1st Embodiment of this invention The figure showing the storage software information which the storage software management means in the 1st Embodiment of this invention manages The flowchart explaining the storage software collation process performed by the storage software collation means in the 1st Embodiment of this invention The figure showing the storage software collation result table which the storage software collation means in the 1st Embodiment of this invention outputs The figure showing the attribute table which the software selection means in the 1st Embodiment of this invention manages The figure showing the software selection menu screen which the software selection means in the 1st Embodiment of this invention displays Flow chart for explaining charge execution selection means performed by the charge means in the first embodiment of the present invention FIG. 3 is a flowchart for explaining a receiving terminal device charging process performed by the charging means in the first embodiment of the present invention. The flowchart explaining the center billing process performed by the billing execution means in the 1st Embodiment of this invention The figure showing the software fee table which the software fee management means in the 1st Embodiment of this invention manages The figure showing the user management table | surface managed by the user management means in the 1st Embodiment of this invention Software execution management system according to the second embodiment of the present invention The figure showing the external storage device information currently recorded on the external storage device in the 2nd Embodiment of this invention The flowchart explaining the external storage apparatus software collation process performed by the external storage apparatus software collation means in the 2nd Embodiment of this invention The figure showing the external storage apparatus software collation result table which the external storage apparatus software collation means in the 2nd Embodiment of this invention outputs The figure showing the attribute table which the software selection means in the 2nd Embodiment of this invention manages The figure showing the software selection menu screen which the software selection means in the 2nd Embodiment of this invention displays The flowchart explaining the software execution process performed by the software execution means in the 2nd Embodiment of this invention Software execution management system according to the third embodiment of the present invention Diagram of download software information managed by download software management means in the third embodiment of the present invention The flowchart explaining the download software collation process performed by the download software collation means in the 3rd Embodiment of this invention The figure showing the download software collation result table which the download software collation means in the 3rd Embodiment of this invention outputs The figure showing the attribute table which the software selection means in the 3rd Embodiment of this invention manages The figure showing the software selection menu screen which the software selection means in the 3rd Embodiment of this invention displays The flowchart explaining the operation | movement performed with the download means in the 3rd Embodiment of this invention Diagram of download software information with version managed by download software management means in the fourth embodiment of the present invention The figure showing the user identification information and usable software information which are recorded on the portable storage device in the 4th Embodiment of this invention The figure showing the stored software information which the stored software management means in the 4th Embodiment of this invention manages The flowchart explaining the storage software collation process performed by the storage software collation means in the 4th Embodiment of this invention The figure showing the storage software collation result table which the storage software collation means in the 4th Embodiment of this invention outputs The flowchart explaining the download software collation process performed by the download software collation means in the 4th Embodiment of this invention The figure showing the download software collation result table which the download software collation means in the 4th Embodiment of this invention outputs The figure showing the software selection menu screen which the software selection means in the 4th Embodiment of this invention displays Flow chart for explaining the center billing process performed by the billing execution means in the fourth embodiment of the present invention The figure showing the user management table which the user management means in the 4th Embodiment of this invention manages The figure showing the software fee table which the software fee management means in the 4th Embodiment of this invention manages The figure explaining the prior art example of this invention

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Receiving terminal apparatus 102 Portable storage apparatus 103 Center apparatus 104 Portable storage apparatus operation means 105 Software storage means 106 Software management means 107 Stored software collation means 108 Software selection means 109 Charging means 114 User management means 113 Software Wear charge management means 115 Billing processing means 117 Software execution means 1301 External storage device 1302 External storage device operation means 1303 External storage device software verification means 2001 Download software management means 2002 Download software list sending means 2003 Download software sending means 2003 2007 Download management means 2008 Download software verification means

Claims (1)

A receiving terminal device connectable to a center device via a network,
Storage means for storing software;
Collation means for obtaining an attribute value of software stored in the storage means;
Billing means for billing software stored in the storage means with the center device;
Execution means for executing software stored in the storage means;
Based on the attribute value of the software that has received a request from the user, a selection unit that passes the right to execute processing to the charging unit or the execution unit;
Software management means for managing stored software information, which is information about the software stored in the storage means;
A portable storage device that manages available software information that consists of a list of available software names is equipped with an insertion / removal port, and the available software information managed by the portable storage device can be read and written. A portable storage device operating means,
The verification means includes
In response to a request from the selection means, obtains usable software information from the portable storage device via the portable storage device operation means, and manages the obtained usable software information and the software management means. The stored software information is collated, the attribute value of the software that has received the request from the selection means is obtained, and the obtained attribute value is passed to the selection means,
The billing means is
When the execution right is acquired from the selection means that has received the attribute value from the matching means, the accounting process is executed, and the software of the software that has received a request from the user via the portable storage device operation means The name is written in the usable software information managed by the portable storage device, the writing completion notification is received from the portable storage device operating means, and the execution means receives the request from the user. It passed the software name,
At that time, the verification means
Software name, software fee, character string briefly describing the software, usage permission flag indicating whether the software is licensed for use, and whether the software is stored in the storage means A first step of preparing a storage software verification result table having an element of a storage flag indicating
For all entries in the stored software information, copy the character string that briefly describes the software name, software fee, and software to the stored software verification result table, set all use permission flags to 0, and set all stored flags to A second step of 1;
A third step of marking the first line of available software information as read,
A fourth step of taking out the entry of the line marked with the readout of available software information as a check software name;
A fifth step of determining whether a check software name exists in the stored software verification result table;
A sixth step of setting a use permission flag of an entry including the software name in the stored software verification result table to 1 when a check software name exists in the stored software verification result table;
If the check software name does not exist in the stored software verification result table, a new entry is added to the stored software verification result table with the software name as the check software name. A seventh step in which the charge of the entry software and the character string briefly describing the software are emptied, the use permission flag = 1 and the storage flag = 0;
An eighth step of determining whether the readout mark of the available software information can be moved to the next line;
If the available software information readout mark is moved to the next line in the eighth step, the ninth step of moving the available software information readout mark to the next line and returning to the fourth step;
By comparing the acquired available software information with the stored software information managed by the software management means,
Based on the stored software verification result table, as an attribute value of the software received from the selection means, in the stored software verification result table, an attribute including a use permission flag = 0 and a storage flag = 1 When the value = 01, the charging process is performed. When the attribute value = 10 including the usage flag = 1 and the storage flag = 0, the usage is disabled. When the attribute value = 11 including the usage flag = 1 and the storage flag = 1 Finds the attribute value meaning each available ,
Receiving terminal device.

Images