Digital Work Cross Program To Broaden {The license {management|administration} program 3a reads out, from the {user|consumer|person} account database 3b, the license {data|information|knowledge} that corresponds to the {received|acquired|obtained} {application|software|utility} ID "a-1" and the {user|consumer|person} ID "3" (s88, s90), and judges {whether|whether or not} the license {data|information|knowledge} is {valid|legitimate} or not (s92).

|Next, the license administration program 3a issues the pass based on the license knowledge which has simply been created/saved.|After the license administration program 3a receives the passes "1" and "3" and the consumer ID "3" (s164), the license management server machine 3 reads, from the person account database 3b, the license validity corresponding to the application IDs "a-1" and "b-1" within the passes "1" and "3" and corresponding to the consumer ID "3" (s166), and judges the license validity (s168).|When this happens, the license administration program 3a reads the license menu corresponding to the application ID "e-1" from the appliance info database 3c (s94) and sends the license menu to the consumer terminal 4 (s96).|The processing for this is carried out by way of the license menu manager 1a executed from the supplier terminals 1, 2. That is, as shown in FIG. 6, when the license menu supervisor 1a is booted on the provider terminal 1 (s10) and the supplier then inputs the application ID (s12), the license menu manager 1a then accesses the application data database 3c of the license management server machine three based on the application ID it has obtained (s14), and then reads the license menu that corresponds to that software ID (s16).} What's displayed right now is the license menu that corresponds to the appliance ID "a-1" shown in FIG. 5. The consumer sees this license menu and can choose it in the case the place he or she agrees to the content material thereof (s102). The license administration program 3a in the license administration server machine three reads out, from the consumer account database 3b, the license knowledge that corresponds to the obtained person ID "3" and to the applying ID "e-1" (s88, s90), and judges the validity of this license data (s92). As said above, the license administration server machine 3 is configured such that the license administration program 3a accesses the user account database 3b, whereby it might immediately detect, with respect to every consumer (i.e., for every consumer ID), the following: the appliance (i.e., software ID) for which license is granted; the circumstances of the license contract (i.e., license base); and the current standing of that license (i.e., license validity). Since it is being assumed here that the new usage-approval has not but been acquired with respect to the perform, the time period, the variety of occasions of usage and the like for the software program, the cross doesn't exist. As the license information, there is given an "application ID (AppID)" for specifying the software (i.e., together with such content material because the software program in its entirety, a partial functional program of the software program, image data that can be used with the software program, musical information or the like) which is permitted for use with respect to each consumer, and for each software ID there are saved a "license base (LicenseBase)" and a "license validity (LicenseValidity)".