(19)
`
`0,
`
`_ropsaces Faint MIO
`European Patent Office
`Office européen des brevets
`
`EP 0 766 1 65 A2
`
`(11)
`
`(12)
`
`EUROPEANPATENT APPLICATION
`
`(51) Int. cl.6: GO6F 1/00
`
`
`
`(72) Inventors:
`« Hasebe, Takayuki,
`c/o Fujitsu Limited
`Kawasaki-shi, Kanagawa 211 (JP)
`* Torii, Naoya,
`c/o Fujitsu Limited
`Kawasaki-shi, Kanagawa 211 (JP)
`
`(74) Representative: Seeger, Wolfgang,Dipl.-Phys.
`Georg-Hager-Strasse 40
`81369 Munchen (DE)
`
`FIG. 6
`
`
`
`
`iS THERE
`
`CORRESPONDING
`N
`DATA?
`
`
`
`
`EXECUTE MAIN PROGRAM
`
`(48) Date of publication:
`02.04.1997 Bulletin 1997/14
`
`(21) Application number: 96111086.3
`
`(22) Dateoffiling: 10.07.1996
`
`(84) Designated Contracting States:
`DE FR GB
`
`(30) Priority: 31.08.1995 JP 224338/95
`
`(71) Applicant: FUJITSU LIMITED
`Kawasaki-shi, Kanagawa 211 (JP)
`
`(54)
`
`Licenseenotification system
`
`There is disclosed a licensee notification sys-
`(57)
`tem for implementing a software sales system wherein
`license information for converting to executable form
`software that is presented to a user in non-executable
`form is communicated to the user from a management
`center on condition of payment of a charge, and the
`software is converted into executable form at the user
`
`terminal using this license information. The subject of
`the licensee notification system is software that decides
`whether
`or
`not
`the
`correspondence
`relationship
`between user identification information and signature
`information stored in the licensefile is legitimate, and, if
`it is legitimate, displays the user identification informa-
`tion to the user before starting proper operation; or,if it
`is not legitimate, does not start proper operation. The
`licensee notification system is constituted by connecting
`the management center and user terminals by commu-
`nication circuits.If license information is requested from
`the user terminal, the management center transmits
`license information combining in integral form the user
`identification information identifying the user and con-
`version information for converting the software to exe-
`cutable form. The user terminal enables the software
`
`using the conversion information contained in this
`license information and writes user identification infor-
`
`is
`mation and signature information whose content
`determined in accordance with the content of the user
`identification information to a licensefile that is referred
`
`to whenthis software is operating.
`
`EP0766165A2
`
`Printed by Rank ees Services
`
`Roku EX1015
`U. S ; Patent No ; 6,4 1 1 94 1
`
`Roku EX1015
`U.S. Patent No. 6,411,941
`
`

`

`1
`
`EP 0 766 165 A2
`
`2
`
`Description
`
`BACKGROUND OF THE INVENTION
`
`1.Field of the Invention
`
`The presentinvention relates to a licensee notifica-
`tion system employed for the sale of software using a
`high speed communication network such as B-ISDN
`and a large-capacity storage medium such as a CD-
`ROM.
`
`2.Description of the Related Art
`
`With the development of high speed communica-
`tion technology such as B-ISDN (broad-band integrated
`services digital network) and high-capacity storage
`media such as CD-ROMs (compact disk read only
`memory) such means can now be usedto distribute
`computer programs or video data or audio data. For
`example, video works which were previously supplied
`on video tape are now being sold stored on CD-ROM.
`Also, game programsetc, which contain a large amount
`of picture data, are being sold stored on CD-ROM. The
`same applies to high speed communication networks,in
`which the software supplier can now distribute the soft-
`ware by various methods.
`One of these methodsof software sales is the so-
`called "locked software” sales system.
`In the locked
`software sales system, a CD ROM on whichare stored
`a large numberof software items whose functions are
`restricted is sold cheaply. By using the various items of
`software of software on the CD-ROMthat is purchased,
`in a condition with the functional restrictions imposed,
`the end useris able to make a decision as to whetheror
`
`not he needs each software item. Then, if the end user
`does require the software, he obtains (purchases) a
`restriction-removal code corresponding to this software
`from a management center operated by the software
`distributor, and is able to use this restriction-removal
`code to remove the functional restrictions on the soft-
`ware.
`
`Such a sales system may be implemented, as a
`specific example, using the software sales system
`shownin Fig. 10. As shownin this Figure, this software
`sales system comprises user terminals 31 and manage-
`ment center 32. The user terminal 31 and the manage-
`ment center 32 are connected by means of a
`communication circuit.
`
`Whenactually purchasing the software (i.e. when
`purchasing a restriction-removal code), the end user,
`using a userID etc, sets up a communication path with
`the management center and executes the prescribed
`procedure required to requestthat a restriction-removal
`code be sent to the user terminal 31. This procedure
`includes the input of a “contents ID’, which is informa-
`tion for identifying the software item that is to be pur-
`chased actually. In response to the execution of such a
`procedure, the user terminal 31 sends to the manage-
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`ment center 32 the contents ID and for example the
`characteristic information of the user, consisting of the
`ID of the CPU providedin user terminal 31.
`Within the management center 32, there is pro-
`vided a software database (software DB)in which soft-
`ware decoding keys employed for encoding the various
`software items are stored in association with the con-
`tents ID. When a contents ID is received from userter-
`
`minal 31, the software decoding key corresponding to
`the contents ID is read from software database 33. Also,
`encoding unit 34 in management center 32 generates a
`user individual key by encoding the user characteristic
`information from user terminal 31 by the key "Ks”.
`Encoding unit 35 sendsthe results of the encoding of
`the software decoding key from software database 33 to
`user terminal 31 as restriction-removal code, using the
`userindividual key from encoding unit 34.
`Encoding unit 36 in user terminal 31 generates a
`user individual key by encoding the user characteristic
`information with the key "Ks". Decoding unit 37 uses the
`user individual key generated by encoding unit 36 to
`decode the restriction removal code from management
`center 32, thereby generating the software decoding
`key. Installation unit 38 then uses this software decod-
`ing key to decodethe software in CD-ROM correspond-
`ing to the contents ID sent to center terminal 32: thus
`the software is put in a condition where it can be used
`with the functional restrictions removed, and,
`in this
`form, is installed on to a storage device such as a hard
`disk device.
`
`With such a software sales system,it is possible to
`determine the software item to be purchased after actu-
`ally ascertaining its contents: thus, the possibility that
`the purchased software might be completely different
`from that intended, as could happen if the purchase
`were made solely on the basis of the details contained
`in a catalogue, can be completely eliminated. Also,
`since the software on the CD ROMis stored in a form
`which is not executable without knowing special infor-
`mation, illicit installation can be prevented.
`However, once the software has beeninstalled, it is
`an extremely easy operation to copy this. Thus, the
`problem has arisen of unscrupulous persons copying
`the software without the consent of the software sup-
`plier. Various methods (so-called protection methods)of
`preventing suchillicit copying are known butthere is no
`way to preventillicit copying by a person possessing
`knowledge at the level of the BIOS (basic input/output
`system). Whichever methodis used, it can do no more
`than make it more difficult to performillicit copying.
`Forthis reason, softwareis sold in which the name
`of the authorized useris displayed on start-up, with the
`object of preventingillicit copying psychologically rather
`than physically. That is, the aim is to preventillicit copy-
`ing of software by displaying the name of the authorized
`user of the software whentheillicitly copied software is
`executed.
`
`However, even with such software, if the copying is
`inclusive of the installation software that sets the user
`
`

`

`3
`
`EP 0 766 165 A2
`
`4
`
`name, whenthe softwareis run, it can be madeto dis-
`play the nameof the person who made theillicit copy:
`thus, sufficient effectiveness in preventingillicit copying
`wasnotobtained.
`
`SUMMARYOF THE INVENTION
`
`An object of the present invention is to provide a
`licensee notification system whose psychological effec-
`tivenessin preventingillicit copying is very high.
`A first licensee notification system according to the
`present invention consists in a system for implementing
`a software sales system in which software in non-exe-
`cutable form is presented to a user, andlicense informa-
`tion for converting the software into executable form is
`informed to the user on condition of payment of a
`charge, and the software is converted into executable
`form using this license information.
`The first licensee notification system is constituted
`of a management center and userterminals; its subject
`is software which includesinstructions that command a
`terminal
`to read user identification information in a
`
`license file and to notify the user identification informa-
`tion to the user on commencementofits operation.
`The management center comprisesa license infor-
`mation generating unit that generates license informa-
`tion combining in integrated form user identification
`information that specifies a user and conversioninfor-
`mation for converting software to executable form.
`The user terminal comprises a storage unit, a con-
`version unit, andlicensefile creating unit. In more detail,
`the storage unit is employed for storing the licensefile
`and software converted to executable form. The license
`
`information, which is generated by the license informa-
`tion generating unit in the management center, is given
`to the conversion unit. The conversion unit then con-
`
`verts the software to executable form using the license
`information andinstalls it in the storage unit. The license
`file creating unit creates the license file which contains
`the user identification information contained in the
`
`license information, and stores the licensefile in the
`storageunit.
`Thatis, in thefirst licensee notification system, soft-
`wareis installed in the user terminal so that the user
`
`identification information of the legitimate user is noti-
`fied to the useronits start-up, using the license informa-
`tion which is generated in the management center and
`contains the useridentification information.
`
`A secondlicenseenotification system according to
`the present invention is constituted of a management
`center and user terminal; its subject is software which
`includes instructions that commands the user terminal
`
`to read useridentification information in the prescribed
`location in the software andto notify the user identifica-
`tion information to the user on commencementofits
`
`operation.
`The management center comprisesa license infor-
`mation generating unit that generates license informa-
`tion combining in integrated form user identification
`
`information identifying a user and conversion informa-
`tion for converting software into executable form.
`The user terminal comprises a storage unit, a con-
`version unit and a software rewriting unit. Of these, the
`storage unit is employed for storing the software after
`this has been converted to executable form. The con-
`version unit converts the software to executable condi-
`
`tion using the license information generated by the
`license information generating unit in the management
`center, and theninstalls it in the storage unit. The soft-
`ware rewriting unit rewrites the information of the pre-
`scribed location of the software that has beeninstalled
`
`by the conversion unit with the user identification infor-
`mation contained in the license information.
`
`Thatis, in this second licensee notification system,
`installation is performed with the contentof the software
`rewritten such that the useridentification information of
`
`the legitimate user is notified on start-up, using the
`license information which is generated in the manage-
`ment center and contains the useridentification infor-
`mation.
`
`The third licensee notification system according to
`the presentinvention hasasits subject software that, on
`commencement of operation,
`includes
`instructions
`commanding the user terminal to read useridentifica-
`tion information in a license file and to notify the user
`identification information to the user.
`
`The managementcenterin the third licensee notifi-
`cation system comprisesa license information generat-
`ing unit that generateslicense information consisting of
`an integral combination of conversion information for
`converting the software to executable form and user
`identification information identifying a user.
`The user terminal comprises a storage unit for stor-
`ing a licensefile, a licensefile creating unit, and a soft-
`ware execution unit. The license file creating unit
`creates the license file containing the license informa-
`tion generated by the license information generating
`unit, and stores the licensefile in the storing unit. The
`software execution unit, when execution of the software
`is designated, converts the software to executable form
`using the license information stored in the licensefile
`and expandsit into memory, and commences operation
`in accordance with the expanded software.
`Thatis, in the third licensee notification system, the
`software, which is presented to the user in non-execut-
`able form,
`is converted to executable form in accord-
`ance with the license information containing the user
`identification information every time execution is desig-
`nated.
`
`The fourthlicensee notification system according to
`this invention is constituted of management center and
`user terminal. The subject of the system is software
`which judges the legitimacy of user identification infor-
`mation on the basis of signature information stored in a
`license file on commencementof operation and, if the
`useridentification information is legitimate, commences
`proper operation after notifying this user identification
`information to the user, and,
`if the user identification
`
`10
`
`15
`
`20
`
`26
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`

`

`5
`
`EP 0 766 165 A2
`
`6
`
`information is not legitimate, terminates operation.
`The management center comprisesa license infor-
`mation generating unit that generates license informa-
`tion combining in integral form the user identification
`information identifying the user and signature informa-
`tion whose content is determined in accordance with
`the useridentification information.
`
`The user terminal comprises a storage unit for stor-
`ing the licensefile and a licensefile creating unit that
`creates the license file containing the useridentification
`information contained in the license information gener-
`ated by the license information generating unit and
`stores the licensefile in the storage unit.
`Thatis, in the fourth licensee notification system,
`the license information which is necessary for running
`the software normally is generated on the basis of the
`user
`identification information in
`the management
`centerandis informedto the user terminal.
`
`It may be noted that although in the first to the
`fourth licensee notification system any means could be
`employed for notification of the license information,
`if
`notification of license information is performed using a
`communication circuit, a system that is simple to oper-
`ate can be formed.
`
`Also,it is possible to employ information including
`the nameof the user as useridentification information.
`
`Itis also possible to employ a unit that generateslicense
`information including user
`identification information
`encoded with a characteristic key of the software. In this
`case, software is presented to user which including
`instructions that command the user terminalto notify to
`the user the result of decoding the user identification
`information using the characteristic key.
`In the first to the third licensee notification systems,
`itis also possible to make the softwarethat is presented
`to the user encoded, and to make the conversioninfor-
`mation for decoding the encoded software. Also,
`it is
`possible to employ, in such a licensee notification sys-
`tem, license information containing the useridentitica-
`tion information in a form that cannot be separated
`without special information. For example, it is possible
`to employ information, as license information, which is
`the result of encoding the conversion information and
`user identification information, combined in integrated
`manner.
`
`Also, itis possible to make the first to third licensee
`notification system a system whose subject is software
`that, if the signature information stored in the licensefile
`does not correspond to the useridentification informa-
`tion, terminates operation, and, as the licensefile creat-
`ing unit,
`to employ a unit that generates signature
`information whose content is determined in accordance
`
`with the content of the useridentification information,
`and creates the license file containing the signature
`information. In this case, it can be made moredifficult to
`alter the useridentification informationthatis notified to
`
`the useron start-up of the software. Also, in the case of
`such software,it is possible to employ as license infor-
`mation generating unit a unit that generates license
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`information containing signature information whose
`contents are determined in accordance with the con-
`
`tents of the user identification information, and, as
`licensefile creating unit, to employ a unit that creates
`the license file containing signature information con-
`tained in the license information.
`
`is possible to make the second licensee
`it
`Also,
`notification system a system whose subject is software
`that, if signature information stored in the second prede-
`termined location does not correspond to useridentifi-
`cation information stored in a prescribed location,
`terminates its operation, and, as software rewriting unit,
`to employ a unit that rewrites the information of the pre-
`scribed location of the software with the user identifica-
`tion information containedin the license information and
`
`that rewrites the information at the second prescribed
`location of
`the software with signature information
`whose content is determined in accordance with the
`
`user identification information. Also, in the case of such
`software,it is possible to employ aslicense information
`generating unit a unit that generateslicense information
`containing signature information whose content
`is
`determined in accordance with the content of the user
`
`identification information, and, as software rewriting
`unit, to employ a unit that rewrites information of the
`prescribed location with user identification information
`contained in the license information and that rewrites
`
`the information at the second prescribed location in the
`software by signature information contained in the
`license information.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`is a functional block diagram illustrating the
`Fig. 1
`layout ofa licensee notification system according to
`a first embodimentof the present invention;
`Fig. 2 is a diagram given in explanation of the con-
`tent of the user database provided in the manage-
`ment center comprised in the licensee notification
`system according to the first embodiment;
`Fig. 3 is a diagram illustrating the content of the
`software database provided in the management
`center comprised in the licensee notification sys-
`tem according to the first embodiment;
`Fig. 4 is a diagram illustrating the content of a
`licensefile provided in a user terminal comprised in
`the licensee notification system according to the
`first embodiment;
`Fig. 5 is a diagram illustrating the structure of soft-
`ware that is the subject of the licensee notification
`system according to the first embodiment;
`Fig. 6 is a flow chart
`illustrating the operating
`sequenceof softwarethat is the subject of the licen-
`see notification system according to the first
`embodiment;
`Fig. 7 is a function block diagram illustrating the
`organization of a user terminal employed in the
`licensee notification system according to a second
`embodiment;
`
`

`

`7
`
`EP 0 766 165 A2
`
`8
`
`Fig. 8 is a diagram illustrating the structure of soft-
`warethat is the subject of the licensee notification
`system according to the second embodiment;
`Fig. 9 is a flow chart showing the operating
`sequenceof software thatis the subjectof the licen-
`see notification system according to the second
`embodiment; and
`Fig. 10 is a functional block diagram showing the
`structure of the licensee notification system usedin
`a prior art locked software sales system.
`
`DESCRIPTION OF THE PREFERRED EMBODI-
`MENTS
`
`The present invention is described in detail below
`with reference to the drawings.
`
`First embodiment
`
`is a functional block diagram of a licensee
`1
`Fig.
`notification system according to a first embodiment of
`the presentinvention. This licensee notification system
`is a system where CD-ROMsstoring a large numberof
`software items of restricted function are sold cheaply,
`and software sales are effected by selling the informa-
`tion needed to cancel the function restrictions of the
`software in this CD-ROM. Paymentof the fee could be
`effected by for example notification of the subscriber
`numberof a cash card ornotification of a bank account
`withdrawal numberorthe like.
`
`As shownin the drawings,the licensee notification
`system is constituted by user terminals 11 and manage-
`ment center 12 connected by means of a communica-
`tion circuit. User terminals 11 and management center
`12 may be described as computers and commence
`operation as an ensemble of the function blocksillus-
`trated when prescribed programsare run.
`First ofall, the operation of management center 12
`will be described.
`
`Managementcenter 12 is provided with two data-
`bases, called user database (user DB) 13 and software
`database (software DB) 14. As shownin Fig. 2, user DB
`13 stores the correspondencerelationship between the
`userID, whichis identification information given to users
`of this system by the manager, and the user name,
`whichis the identification information of the user as
`
`employed in ordinary society. As shownin Fig. 3, soft-
`ware DB 14 stores the correspondencerelationship
`betweenthe contents ID, whichis the identification infor-
`mation of each software item supplied and stored in the
`CD ROM, and the software decoding key, which is the
`decoding information needed to decode this software
`item.
`
`A link-up unit 15 in management center 12 gener-
`ates license information by combining the two data
`items: user name and software decoding key. An encod-
`ing unit 16 generates a user's individual key by encod-
`ing with key "Ks” the user characteristic information
`(details to be explained later) from user terminal 11. An
`
`10
`
`15
`
`20
`
`26
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`encoding unit 17 generates coded license information
`by encoding the license information from link-up unit 15
`using the user's individual key generated by encoding
`unit 16.
`In the present licensee notification system, a
`DES (data encryption standard) algorithm is employed
`for encoding and decoding.
`The various function blocks that are not in manage-
`ment center 12 are arranged to operate synchronously
`whenthere is a request from user terminal 11 for infor-
`mation for removal of the function restrictions. Specifi-
`cally, when managementcenter 12 receives a request
`for information for removal of function restrictions relat-
`
`ing to a software item from user terminal 11, it transmits
`to user terminal 11 coded license information containing
`the user’s name and the software decoding key needed
`to remove the functional restrictions on the software
`item.
`
`the operation of user terminal 11 will be
`Next,
`described. Whenuserterminal 11 runs the programsfor
`communication andinstallation, it executes the opera-
`tion described below.
`
`A request transmission unit 18 in user terminal 11
`transmits to managementcenter 12 information includ-
`ing the user ID, contents ID, and user's characteristic
`information. Request transmission unit 18 commences
`operation when the keyboard (not shown) of user termi-
`nal 11 is operated in accordancewith a prescribed pro-
`cedure that
`is predetermined as the procedure for
`requestof information for removal of functional restric-
`tions. This request procedureincludes keyboard inputof
`the user ID and contents ID; request transmission unit
`18 transmits to management center 12 the keyboard
`input information and the user's characteristic informa-
`tion, which is constituted by the ID of the CPU whichis
`employed in user terminal 11.
`As already explained, when a requestfor informa-
`tion for removal of functional restrictions is received
`
`from user terminal 11, management center 12 sendsto
`user terminal 11 encoded license information. As a
`
`result, after request transmission unit 18 has been oper-
`ated, user terminal 11 receives encodedlicenseinfor-
`mation from management center 12.
`As shown in the drawings, the encoded license
`information is input to decoding unit 20 in user terminal
`11. Decoding unit 20 also inputs the user's individual
`key, which is generated by encoding unit 19 using the
`user's characteristic information and "Ks". Using this
`user's individual key, decoding unit 20 decodes the
`encoded license information from center terminal 12.
`
`The license information, which is the result of this
`decoding, is input to separating unit 21, which is a unit
`that performs reverse processing against link-up unit 15
`in managementcenter 12. Separating unit 21 separates
`and extracts the software decoding key and user name
`from the license information, and respectively supplies
`the extracted software decoding key and user name to
`installation unit 22 andlicensefile compilation unit 23.
`Installation unit 22, using the software decoding key
`from separating unit 21, removes the functional restric-
`
`

`

`9
`
`EP 0 766 165 A2
`
`10
`
`tions on the specific software item (details to be
`described later) in accordance with the contents ID
`transmitted by request transmission unit 18. Licensefile
`compilation unit 23 compiles a license file 24 using the
`user name and contents ID from separating unit 21.
`Fig. 4 shows diagrammatically the contents of
`license file 24. As shownin the drawing, licensefile 24
`stores information consisting of contents ID and user
`name, and signature information, which is information
`encoded using a signature key.
`Further detailed description of the operation of
`installation unit 22 and the operation of the software
`installed byinstallation unit 22 is given below using Fig.
`5 and Fig. 6. Of these Figures, Fig. 5 is a view showing
`diagrammatically the structure of software that is the
`subject of the presentlicensee notification system and
`Fig. 6 is a flow chart showing the operating sequenceof
`the CPU in the user terminal when the software thatis
`the subject of the presentlicensee notification system is
`actuated.
`
`As shownin Fig. 5, the software that is the subject
`of the present system includesa license display routine
`25 and main program 26. In the main program there are
`defined the operating proceduresrelating to the proper
`functions of this software; in license display routine 25,
`there is defined the content to be executed prior to exe-
`cution of main program 26.
`Whenthis software is actuated, as shownin Fig. 6,
`the CPU,first of all, by checking the contents ID in the
`license file, decides whether or not data corresponding
`to the software that is being actuated is present in the
`license file (step $101). Then, if the corresponding data
`exists (step S101:Y), the CPU performs a checkof the
`legitimacy of the corresponding data (step 102). In this
`step, the CPU encodesthe information consisting of
`contents ID and user name stored in the licensefile
`
`using the signature key that is set as data in license dis-
`play routine 25, and if the result of this encoding agrees
`with the signature information, decides that the data is
`legitimate.
`If it is legitimate (step $102:OK), the CPU displays
`the user namewhichis read from the licensefile (step
`$103), and commences operation in accordance with
`the main program (step $104).
`Also, if the corresponding data is not presentin the
`licensefile (step S101:N)orif the content of the license
`file is found to be not legitimate (step $102:NG), i.e.if
`the content of the licensefile is found to be different
`
`from the result of the compilation performed bylicense
`file compilation unit 23, the CPU terminates operation
`without displaying the user name or executing the main
`program.
`As described above, with the licensee notification
`system according to the first embodiment,
`in the user
`terminal, installation of the software is performed such
`that the user nameis displayed on start-up, using the
`encodedlicense information supplied from the manage-
`ment center. Also, the installed software is executed
`only whenthe legitimacyof thelicensefile is verified. As
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`a result, with this licensee notification system, even if
`the software and license file are copiedillicitly after
`being installed,
`it is difficult to change the user name
`appearing on start-up of the software. The person who
`has made the illicit copy has no alternative but to use
`the software with the nameof another personbeing dis-
`played. As a result,illicit copying of the software can be
`preventedif the present licensee notification system is
`employed.
`It should be noted that the licensee notification sys-
`tem of thefirst embodiment could be modified in various
`
`ways.
`It would for example be possible to constitute the
`system such that notification of the contents ID etc to
`the management center and notification of the encoded
`license information to the user terminal were performed
`by another information transmission unit, such as the
`post. In this case, the user terminal is constituted such
`that installation is effected using encoded licenseinfor-
`mation input from the keyboard.
`It is also possible to
`constitute the system such that the license information
`is notified in un-encoded form.
`
`It is also possible to arrangethat the signature infor-
`mation is generated at the management center end,
`and encodedlicense information containing this signa-
`ture informationis notified to the user terminal.
`
`It is also possible to constitute the system suchthat,
`instead of the user name and signature information,
`information representing the user name in encoded
`form is stored in the license file, and, when the installed
`software is executed, the informationin the licensefile is
`decodedbythe software anddisplayed.
`It would also be possible to arrange that the soft-
`ware was converted into executable condition not on
`
`installation of the software but rather every time execu-
`tion of the software was specified, the software then
`being expanded in the memory and operation com-
`menced in accordance with the software now in the
`
`memory.
`Also, the medium wherebythe software is supplied
`is not restricted to CD-ROM; a supply mode could be
`adopted in which the software was stored on another
`recording medium such asa floppy disk, or downloaded
`through a communication circuit.
`
`Second embodiment
`
`A licensee notification system according to a sec-
`ond embodiment of the present invention is described
`below with reference to Fig. 7 and Fig. 9. Of these Fig-
`ures, Fig. 7 is a functional block diagramillustrating the
`layout of a user terminal wherein a licensee notification
`system according to the second embodimentis pro-
`vided. Fig. 8 is a diagram illustrating the structure of
`software that is the subject of this licensee notification
`system.Fig. 9 is a flow chart showing the operating pro-
`cedure of the CPU whenthe softwarethatis the subject
`of the present licensee notification system is executed.
`In the licensee notification system according to the
`
`

`

`11
`
`EP 0 766 165 A2
`
`12
`
`second embodiment, a managementcenterof the same
`construction as management center 12 in the first
`embodimentis employed. Also, as can be seen from the
`functional block diagram shownin Fig. 7, the difference
`of the action of the user terminal 11 is slight, so the
`description will be confined to the parts of which the
`details of operation differ with respect to the licensee
`notification system of the first embodiment.
`As shownin Fig.7, in user terminal 11 according to
`the second embodiment, the software decoding key and
`user namethat are separated by separating unit 21 are
`both inputto the installation unit 29. Installation unit 29
`effects installation by decoding the so