United States Patent [191
`Katznelson
`
`[11] Patent Number:
`[45] Date of Patent:
`
`5,010,571
`Apr. 23, 1991
`
`[54] METERING RETRIEVAL OF ENCRYPTED
`DATA STORED IN CUSTOMER DATA
`RETRIEVAL TERMINAL
`Inventor: Ron D. Katznelson, San Diego, Calif.
`[75]
`[73] Assignees: Titan Linkabit Corporation;
`Cable/Home Communication
`Corporation, both of San Diego,
`Calif.
`[21] Appl. No.: 905,775
`[22] Filed:
`Sep. 10, 1986
`[51]
`Int. Cl.' ............................................... H04L 9/00
`[52] U.S. Cl ........................................... 380/4; 380/25;
`380/29
`[58] Field of Search .................................... 380/23-25,
`380/28, 16,20,3,4,5;358/84-46;364/200,900
`References Cited
`U.S. PATENT DOCUMENTS
`3,573,747 4/1971 Adams et al .................... 364/200 X
`3,956,615 5/1976 Anderson et al. .................... 380/24
`4,048,619 9/1977 Forman, Jr. et al ............. 380/34 X
`4,196,310 4/1980 Forman et al. ....................... 380/46
`4,262,329 4/1981 Bright et al. ...................... 380/25 X
`4,323,921 4/1982 Guillou ................................. 380/20
`4,337,483 6/1982 Guillou ................................. 380/20
`4,433,207 2/1984 Best ......................................... 380/4
`4,484,217 11/1984 Block et al. ........................... 358/84
`4,677,434 6/1987 Fascenda .............................. 380/23
`4,712,238 12/1987 Gilhousen et al .................... 380/20
`4,827,508 5/1989 Shear ...................................... 380/4
`
`[56]
`
`FOREIGN PATENT DOCUMENTS
`0135422 3/1985 European Pat. Off ..
`2136175 9/1984 United Kingdom .
`0002310 5/1985 World Int. Prop. 0 ..
`
`OTHER PUBLICATIONS
`"The New Alexandria", Alexandria Institute, vol. I,
`No. 1, Jul.-Aug. 1986.
`Denning and Denning, "Data Security", Computing
`Surveys, vol. 11, No. 3, Sep. 1979.
`Primary Examiner-Stephen C. Buczinski
`Assistant Examiner-Bernarr Earl Gregory
`Attorney, Agent, or Firm-Edward W. Callan
`ABSTRACT
`[57]
`A system for controlling and accounting for retrieval of
`data from a CD-ROM memory containing encrypted
`data files from which retrieval must be authorized. The
`system includes an authorization and key distribution
`terminal and a plurality of customer data retrieval ter(cid:173)
`minals having such memories loaded therein. The au(cid:173)
`thorization terminal authorizes retrieval of data by au(cid:173)
`thorized customer terminals by providing to the autho(cid:173)
`rized customer terminals an encryption key for enabling
`retrieval of the data and a authenticated credit signal for
`use in limiting the amount of data to be retrieved from
`the files. The encryption key is encrypted for communi(cid:173)
`cation to the customer terminals in unique unit keys that
`are stored in the respective customer terminals. The
`customer terminal limits the amount of data retrieved
`from the files in accordance with the credit signal; re(cid:173)
`cords the amount of data retrieved from the files; and
`provides to the authorization termimal an authenticated
`report of the recorded amount of data retrieved from
`said files. The memory includes data files of different
`data vendors; and the customer terminal separately
`records the retrieval of data from the files of the differ(cid:173)
`ent vendors.
`
`43 Claims, S Drawing Sheets
`
`FILE USE REQUEST AND UNIT ID
`
`ENCRYPTED FILE KEY
`
`AUTHENTICATED CREDIT DATA
`
`'--12
`
`'-13
`
`'-14
`
`AUTHORIZATION AND
`KEY DISTRIBUTION
`TERMINAL
`
`INTERROGATION
`'-61
`
`CUSTOMER
`DATA
`RETRIEVAL
`TERMINAL
`
`AU THEN TICA TED ll~At:F" REPORT AND UNIT ID
`'-53
`AUTHENTICATED CREDIT AND
`DEBIT STATUS REPORT AND UNIT ID
`'--64
`
`.
`
`REFRESH REGISTERS COMMAND
`'-70
`
`r--10
`
`11-
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 1
`
`

`

`U.S. Patent
`
`Apr. 23, 1991
`
`Sheet 1 of 5
`
`5,010,571
`
`FIG 1
`•
`FILE USE REQUEST AND UNIT ID
`
`ENCRYPTED FILE KEY
`
`AUTHENTICATED CREDIT DATA
`
`12
`
`'-13
`
`'-14
`
`AUTHORIZATION AND
`KEY DISTRIBUTION
`TERMINAL
`
`INTERROGATION
`
`'-61
`
`CUSTOMER
`DATA
`RETRIEVAL
`TERMINAL
`
`AU THEN TICA TEO USAGE REPORT ANO UNIT ID
`"-63
`
`--
`
`AUTHENTICATED CREDIT AND
`DEBIT STATUS REPORT AND UNIT ID
`'-64
`
`REFRESH REGISTERS COMMAND
`~70
`
`'-10
`
`11__....
`
`KEY aJ
`
`KEY bJ
`
`KEY CJ
`I
`I
`
`I
`
`I
`
`I
`
`2
`
`COMPANY NAME
`AND ADDRESS
`
`ZIP CODE
`
`fl OF
`EMPLOYEES
`
`I
`
`PLANT
`AREA
`
`I
`
`ANNUAL
`REVENUE
`
`I
`
`I
`
`I
`
`I
`
`I
`
`ID
`
`I
`
`I
`
`I
`I '
`
`31
`
`TIER A
`
`TIER B
`
`FIG. 7
`
`TIER C
`
`'II
`
`' I
`
`'I
`
`I
`' I 111
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 2
`
`

`

`U.S. Patent
`
`Apr. 23, 1991
`
`Sheet 2 of 5
`
`5,010,571
`
`ROM
`FILE A I BLK 1 BLK 21BLK 3 BLK 4IBLK 5
`FILE B I BLK 1 BLK 21BLK 3 BLK 4IBLK 5
`
`r 37
`
`FIG. 2
`
`12"'
`
`I
`
`,,
`39__..
`UNIT 10
`'13.-/
`
`..
`
`CREDIT
`... DATA
`'14_.I
`
`ENCRYPTED
`44-...; ADDRESS 4S- ......
`'" DATA
`DECRYPT DAT~
`BLOCK ID
`KEYBOARD
`34,
`r35
`DATA
`'-..47
`FILE
`FILE USE
`ACCESS
`REQUEST
`COMMAND
`I
`
`. .,..-16
`
`~8
`
`I
`
`r33
`48-..
`
`r-49
`Fl ADORE~
`.
`ENCRYPTED FILE KEY
`RAM
`.
`i.:.:.::.J)
`-
`~g
`2s-,'(
`AUll-lENTICA TE
`CREDIT
`DATA
`
`-~1
`
`FILE
`r17 KEY
`DECRYPT
`FILE KEY I\ ... 50
`42---9 r24
`UNIT KEY
`MEMORY
`
`..
`
`,-42
`
`22--....
`
`,,.-48
`AUll-lENTICA TE
`COST
`DATA
`
`COST
`DATA
`
`RETRIEVAL CONTROL UNIT
`UNIT ID
`27 (_54
`.
`r31
`,,..-20 66 lfriCREDI~; ~
`'~39
`ENABLE
`...-29 COM-
`GENERA TE
`\...
`4
`LOGIC
`6
`~ AUll-lENTICA TED1c:
`'-56
`!jACCUMULA TEl,I:-/
`a? DEBIT STATUS !Cl ~ ..... ~2
`CREDIT ANO
`
`I
`
`DEBIT: -
`
`53
`I
`
`REPORT
`
`t, .......
`
`42~,
`UNIT KEY
`
`i--55
`
`E:NABI F'
`
`cn~T OATA
`51../
`
`ENABLE
`
`23,
`USE
`HISTORY
`STORAGE
`
`'--so
`
`-
`
`BLOCK ID
`~
`\_47'
`
`UN~~ ID
`....-39
`
`a?
`
`..
`,
`
`;r-62
`
`r21
`GENERATE
`AUTHENTICATED
`USAGE
`REPORT
`
`-
`
`,..42
`
`,,
`
`UNIT KEY
`,61
`INTERROGATION
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 3
`
`

`

`UNIT.
`ID
`
`DESIRED
`UNIT FILE ID
`l,-11
`KEY
`
`,78
`
`GENERATE ·
`.UTHENTICA TEDI 9
`FILE USE
`REQUEST
`
`79
`
`UNIT
`KEY
`.
`
`78
`
`DECRYPT
`FILE KEY
`
`------
`
`'"'2
`
`91
`
`ENCRYPT
`FILE KEY
`
`I
`I
`I
`I _..,
`
`DECRYPT UNIT
`ID ANO
`FILE ID
`
`87
`
`8
`
`LOOK UP
`FILE KEY
`
`ENCRYPTED
`DATA FILE
`I
`
`96
`
`94
`
`95
`
`DECRYPT
`FILE
`HEADER
`
`ERROR
`ESSAGES
`
`9
`
`CUSTOMER DATA
`RETRIEVAL
`TERMINAL
`1.2.
`
`100
`DECRYPT
`DATA
`FILE
`
`YES
`
`99
`
`NO
`
`FIG. 3
`
`AUTHORIZATION AND
`KEY DISlRIBUTION
`TERMINAL
`1J.
`
`101
`GENERATE
`TRANSACTION
`REPORT
`
`1.02. Bl'-~..ING TERMINAL
`
`•
`~
`
`~ • 00
`fO ....
`tD = ....
`
`~
`
`>
`'= :,
`JN ...
`~ ...
`
`r:Jl
`::r'
`ti)
`
`ti) ....
`w
`0 ...,
`
`UI
`
`...
`OI
`0 .....
`...
`0
`OI
`....:a
`.....
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 4
`
`

`

`115
`USE HISTORY
`STORAGE
`
`117
`
`DEBIT AND
`CREDIT REGISTERS
`
`FIG. 4
`
`136
`UPDATE CREDIT
`REGISTER
`
`137
`
`ENABLE
`DECRYPTION
`
`0 • r.11
`
`•
`i-c:,
`D)
`~
`
`('I) = ~
`
`N
`
`~
`.. ~
`~
`
`~
`
`~
`
`tD
`
`00. =(cid:173)
`tD ....
`.,:.
`Q ....
`
`U1
`
`UI
`,..
`
`0 ....
`....
`
`0
`,..
`UI
`-...l
`
`UNIT KEY
`CUSTOMER
`DATA
`RETRIEVAL
`TERMINAL
`
`---------
`
`AUTHORIZATION
`TERMINAL
`~
`
`106
`
`133
`
`132
`
`GENERATE
`AU THEN TICA TED
`CREDIT
`DATA SIGNAL
`
`130
`.........
`
`110
`
`UNIT
`KEY
`
`BILLING
`12.6. TERMINAL ·
`
`UNIT ID
`.J
`109
`
`107
`
`GENERATE
`AUTHORIZATION
`REQUEST
`
`UNIT KEY
`HJ
`
`I
`
`AUTHENTICATED I
`
`,
`,
`GENERATE
`
`REPORTS
`
`116
`,,118
`'
`
`~9 , DISPLAY ERROR
`MESSAGES
`
`·108
`
`12
`
`11
`AU THEN TICA TED
`INTERROGATION
`COMMAND
`
`09
`
`110
`
`LOOK UP
`UNIT KEY
`, ·128
`~1-----1
`CREDi~i~OKUP ~tea~-..
`
`YES
`
`125
`I
`
`,
`
`,
`
`STORE USE
`HISTORY
`
`I
`
`~29
`
`.f25a
`
`BAD CREDIT UST
`
`REPORT FOR BILLING
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 5
`
`

`

`U.S. Patent
`
`Apr. 23, 1991
`
`Sheet 5 of 5
`
`5,010,571
`
`5/5
`
`140
`
`RETRIEVE N BLOCKS
`HAVING RETRIEVAL
`COST R UNITS FROM
`VENDOR Y'S DA TA
`FILES
`
`INCREMENT VENDOR
`Y DEBIT REGISTER
`BY N · R RETRIEVAL
`UNITS
`
`142
`
`FIG. 5
`
`141
`
`UPDATE VENDOR Y
`USE HISTORY
`STORAGE
`
`NO
`
`144
`
`YES
`
`DISABLE
`DECRYPTION
`
`145
`
`DISPLAY
`•uNAU TH ORI ZED"
`MESSAGE
`_____________ J
`
`107
`
`GENERATE
`AUTHORIZATION
`REQUEST
`
`CD-ROM DRIVE
`
`[§§§JI D
`
`149
`
`0
`
`FIG. 6
`
`TELEPHONE LINE
`
`1 4
`
`150
`
`DATA RETRIEVAL
`RMINAL (FIG. 2
`
`-----
`
`153
`TELEPHONE
`MODEM
`
`151
`
`PERSONAL COMPUTER
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 6
`
`

`

`METERING RETRIEVAL OF ENCRYPTED DATA
`STORED IN CUSTOMER DATA RETRIEVAL
`TERMINAL
`
`BACKGROUND OF THE INVENTION
`The present invention generally pertains to data re(cid:173)
`trieval and is particularly directed to limiting and ac(cid:173)
`counting for the retrieval of data from encrypted data
`files.
`
`55
`
`1
`
`5,010,571
`
`2
`data retrieval terminal 11. Different data files in the
`memory may be associated with different data vendors.
`Typically, communications between the authorization
`and key distribution terminal 10 and the customer data
`5 retrieval terminal 11 are transmitted over telephone
`lines.
`In order to gain authorization to retrieve encrypted
`data from a given file stored in the memory loaded in
`the customer data retrieval terminal 11, the customer
`10 causes a file use request signal 12 to be communicated to
`the authorization and key distribution terminal 10. The
`SUMMARY OF THE INVENTION
`file use request signal identifies the file for which re-
`trieval authorization is requested and also contains an
`The present invention is a method and system for
`ID number identifying the customer terminal 11 from
`controlling and accounting for retrieval of data from a
`memory containing an encrypted data file from which 15 which the request signal 12 is sent.
`The authorization and key distribution terminal 10
`retrieval must be authorized. The system includes
`means for authorizing such. retrieval by providing an
`processes the request signal to determine whether the
`encryption key for enabling retrieval of the data and a
`customer terminal 11 identified by the ID number con-
`credit signal for use in limiting the amount of data to be
`tained in the file usc request signal 12 is authorized to
`retrieved from the file; means for limiting the amount of 20 retrieve data from the file identified in the file use re-
`quest signal 12. Such determination includes checking
`data retrieved from the file in accordance with the
`credit signal; and means for recording the amount of
`on the status of a customer account associated with the
`~ta retrieved from the ~le. The sytem may further
`customer terminal 11 from which the request signal 12
`mclude ?1eans for reportmg the recorded amou°:t of
`is received; and may further include determining the
`~ata retneved frou1 the file; and means for authenticat- 25 eligibility of the customer to retrieve data from such file
`mg such report..
`. .
`.
`.
`.
`notwithstanding the outcome of the credit check .
`. ~e present 1nvent1on .IS part1cularly ~u1ted for re-
`Upon determining that the status of the customer
`account associated with the customer terminal 11 war-
`tnevmg data files stored m a compact disc read-only-
`1 f d
`f
`memory (CD-ROM).
`·
`· ·
`h
`h fil
`·d
`·
`Add"f al r,
`t
`· f th
`·
`f
`d"
`d . 30 rants aut onzmg retneva o
`ata rom t e
`e 1 entl-
`. 1 ion
`ea ur~ ?
`tied in the file use request signal 12, the authorization
`e inven ion are
`iscus~ m
`terminal 10 authorizes the customer terminal 11 to re-
`relation to the descnpt1on of the preferred embocbment.
`BRIEF DESCRIPTION OF THE ORA WING
`trieve data from said file by providing to the customer
`FIG. 1 is a block diagram illustrating the signals coms
`terminal 11 both and encrypted file key 13 and an au-
`municated between an authorization and key distribu- 35 thenticated credit data signal 14. The credit data signal
`14 indicates an amount of credit to be extended to the
`tion terminal and a customer data retrieval terminal in a
`customer terminal 11 for retrieval of data from the file
`preferred embodiment of the present invention.
`FIG. 2 is a functional block diagram of the customer
`identified in the file usc request signal 12.
`data retrieval terminal in the embodiment of FIG. 1
`The file key 13 is encrypted in a unit key that is
`FIG. 3 is a flow diagram showing operational r~u- 40 unique to the customer terminal 1~ to which. th: en-
`crypted ~le key 13 a°:d the aut~ent1cated credit signal
`tines in an alternative preferred embodiment of the
`14 are bemg c?mmumcated .. Umt k~ys fo~ each of th_e
`present invention.
`FIG. 4 is a flow diagram showing operational rou-
`cus_tomer termm~ls _11 ~soc1at~ with a given au!hon-
`tines in another alternative preferred embodiment of the
`zat1on and key d1stnbut10n termmal 10 are stored m the
`present invention.
`45 authorization and key distribution terminal 10 and are
`FIG. 5 is a flow diagram showing certain aspects of
`indiV:idually retrieved in a~c?rdance ~ith the customer
`termmal ID number that ts mcluded m the file usc re-
`the operational routines in still another alternative pre-
`ferred embodiment of the present invention.
`quest signal 12. Each customer data retrieval terminal
`FIG. 6 is a block diagram illustrating the usc of a
`also permanently stores it own unique unit key. The
`customer data retrieval terminal in a personal computer 50 authenticated credit data signal 14 is generated by in-
`for retrieving data from a CD-ROM.
`eluding both unencrypted credit data and encrypted
`FIG. 7 illustrates an exemplary scheme of tiering the
`credit data that is formed by encrypting the unen-
`retrieval of different types of data fields from a memory
`crypted credit data with the unit key of the customer
`in accordance with a preferred embodiment of the pres-
`terminal that is being authorized.
`ent invention.
`-
`The operation of the customer data retrieval terminal
`11 in retrieving the encrypted data from the memory
`loaded therein is described with reference to FIG. 2.
`Certain functional units of the customer data retrieval
`terminal 11 are implemented in a microcomputer. These
`functional units include a data decryption unit 16, a file
`key decryption unit 17, a cost data authentication unit
`18, a credit data authentication unit 19, an authenticated
`credit and debit status report generation unit 20, an
`authenticated usage report generation unit 21, a re(cid:173)
`trieval control unit 22 associated with each data vendor,
`a use history storage unit 23 associated with each data
`vendor, a unit key memory 24 and a random access
`memory (RAM) 25. The retrieval control unit 22 in-
`
`DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`The use of a preferred embodiment of the system of
`the present invention is generally described with refer- 60
`ence to FIG. 1. The system essentially includes an au-
`·
`thorization and key distribution terminal 10 and a cus- ·
`tomer data retrieval terminal 11; it being undentood
`that in practice there are a plurality of customer data
`retrieval terminals 11 that communicate with a single 65
`authorization and key distribution terminal 10. A mem(cid:173)
`ory containing an encrypted data file from which re(cid:173)
`trieval must be authorized is loaded in the customer
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 7
`
`

`

`5,010,571
`
`4
`3
`with the applicable file key for the file containing the
`eludes a credit register 27, a debit register 28, an accu-
`mulator 29, a comparator 30 and a logic unit 31. The
`block of data that is being retrieved.
`customer data retrieval terminal 11 further includes a
`The applicable encrypted file key 13 is retrieved from
`the RAM 25 in response to a file address 49 included in
`keyboard 33 for generating a file use request 34 and a
`5 the file access command 35 and decrypted by the file
`file access command 35.
`A read only memory (ROM) 37 containing the en-
`key decryption unit 17, which is keyed by the unit key
`42 stored in the unit key memory 24. The file key de-
`crypted data files is loaded in the customer data re-
`cryption unit 17 provides a decrypted file key SO to the
`trieval terminal 11. The ROM 37 includes a plurality of
`data decryption unit 16 and the cost data authentication
`encrypted data files, File A, File B. Each data file in-
`eludes encryted data blocks, Block 1, Block 2, ... Block 10 unit 18.
`5. Each data file includes blocks of data of a given type
`The retrieved cost data signal 48 containing cost data
`of association. The different data files may be associated
`in both encrypted and unencrypted form is authenti-
`cated by the cost data authentication unit 18, which is
`with different data vendors and there may be a plurality
`of data files associated with each of the different ven-
`keyed by the file key 50 and initialized by the block ID
`· dors. Each block of data includes encrypted data, a 15 signal 47 (used as an initialization vector) to decrypt the
`block ID (identification) signal, and authenticated cost
`encrypted cost data and thereby provide a decrypted
`data. The authenticated cost data indicates the cost
`cost data signal, which is compared with the unen-
`·
`th
`. d
`· ·
`· h
`·
`t d bl
`,. f
`crypted cost data signal in the retrieved cost data signal
`OC&. o
`th
`t'
`t th
`t d ta ·
`l
`associate wit retneving e given encryp e
`to au en ica e
`e cos
`a
`signa .
`d
`48
`aTta.
`bl h
`t
`d ta
`t .
`1 t
`. al 11 t 20 An authenticated cost data signal 51 is provided to
`-
`.
`.
`h
`re neva ermin
`o
`·
`29 Th
`o ena e t e cus omer a
`f
`·
`fil
`· th ROM 37 th fil
`the debit register 28 and t e accumulator
`.
`e debit
`·
`d
`. ' . e I e
`retneve ata r~m a~y ~iven i .e in e .
`register 28 is not immediately incremented by the cost
`data signal 51, however. First the accumulator 29 adds
`use request 34 identifying a give? file i~ generat~d by
`use of the keyboard 33 and comb~ned with the ~mt ID
`the cost data signal 51 to a debit signal 52. The debit
`number 39 for th7 customer ter:nnnal 11 t~ provide the 25 signal 52 indicates the sum of previous data retrieval
`file u5«: re~uest signal 1~ t~at ~s comm~mcated to t~e
`costs accumulated in the debit register 28. The sum 53
`authonzation and key dist~b~tion terminal ~O. ~s ~is-
`of the cost data and the previously accumulated data
`retrieval costs indicated in the accumulator 29 is then
`cussed above, the authonzation and key distnbution
`term~n~l 10 responds to the file use request signal 12 br
`compared by the comparator 30 with an accumulated
`providing ~he enc~ypted file key 13 and the au~henti- 30 credit signal 54 from the credit register 27 to determine
`cated credit data signal 14 to the customer terminal 11
`whether the customer terminal 11 has been credited
`when the authorization an.d key distribution terminal
`with sufficient credilt to authorize retrieval of data from
`determ~nes that the c~sto~er te~inal 11 is authorized
`the requested file. When the compensation indicates
`to retneve the data identified in the file use request
`that there is sufficient accumulated credit to authorize
`35 such retrieval, the logic unit 31 provides an enable sig-
`signal 12.
`.
`.
`The encrypted file key 13 is stored in the RAM 25.
`nal 56 to the data decryption unit 16, the debit register
`~e rece~ved credit data signal 14 containing t~e
`28 and the use history storage unit 23. The enable signal
`credit data in both encrypted and unencrypted form is
`56 enables the cost data 51 to be incremented into the
`debit register 28. As noted above, the customer terminal
`authenticated by the credit data authentication unit 19,
`which is keyed by the unit key 42 stored in the unit key 40 11 includes a plurality of retrieval control units 22 car-
`memory 24 ~o decrypt the enc~pted c~edit da~ an~
`responding to a plurality of different vendors for ac-
`thereby provide a decrypted credit data signal, which is
`counting for the retrieval of data from the files associ-
`ated with each of the different vendors.
`compared with the unencrypted credit data signal in the
`authenticated credit data signal 14 to authenticate the
`The enable signal 56 also enables the operation of the
`received credit data signal 14. An authenticated credit 45 data decryption unit 16. The data decryption unit 16 is
`data signal 41 is stored in the credit register 27 of the
`keyed by the unit key 42 stored in the unit key memory
`retrieval control unit 22 associated with the same ven-
`24 for decrypting the encrypted data 46 and providing
`retrieved data 58. The block ID signal 47 is used as an
`dor as the file from which data retrieval is being autho-
`rized. If the credit register 27 already has a credit bal-
`initialization vector by the data decryption unit 16 in
`ance, such balance is incremented by the amount indi- so combination with the decrypted file key SO for decrypt-
`cated by the authenticated credit signal 41.
`ing the decrypted data 46.
`Upon being enabled by the enable signal 56, the use
`A message (not shown) indicating that authorization
`has been granted for the customer terminal 11 to re-
`history storage unit 23 stores the block ID signal 47 to
`trieve data from the requested file is also communicated
`record the identity of the block of data retrieved from
`by the authorization and key distribution center 10 to ss the ROM 37. The block ID signal identifies the file from
`which the data was retrieved and includes an address
`the customer terminal 11 and displayed on a monitor
`identifyfog the vendor associated with the retrievede
`(not shown) at the customer terminal 11.
`To retrieve a given block of data from an authorized
`file for addressing the use history storage unit 23 associ-
`data file in the ROM 37, the keyboard 33 is operated to
`ated with the vendor of the data in the retrieved file. As
`provide a file access command 35 which includes an 60 noted above, the customer terminal 11 includes a plural-
`ity of use history storage units 23 corresponding to a
`address signal 44 directed to the ROM 37 for accessing
`the given block of data. In the example shown in FIG.
`plurality of different vendors for separately recording
`1, the accessed block of data is block 5 of file B. Upon
`the amount of data retrieved from the files associated
`the block of data being accessed, the encrypted data 46,
`with each of the different vendors.
`the block ID signal 47 and authenticated cost data 48 65 A usage report 60 indicating the usage history re-
`corded in the use history storage unit 23 is generated for
`are read therefrom. The authenticated cost data in-
`eludes both unencrypted cost data and encrypted cost
`communication to the authorization and key distribu-
`tion terminal 10 in response to either operation of the
`data formed by encrypting the unencrypted cost data
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 8
`
`

`

`5,010,571
`
`6
`5
`keyboard 33 or an interrogation signal 61 received from
`The terminal 73 then performs another look-up rou-
`tine 83, wherein the decrypted file ID number 84 is used
`the authorization and key distribution terminal 10.
`to look up the file key 85 that was used for encrypting
`The block ID number further identifies the retrieved ·
`data by type; whereupon the type of data retrieved is
`the file identified by the decrypted file number 84.
`The terminal 73 also performs an authentication rou-
`recorded in the history storage unit 23 and included in 5
`tine 86 for determining whether the received message
`the usage report 60.
`An authenticated usage report 62 is generated by the
`79 is authentic, wherein the decrypted unit ID number
`authenticated usage report generation unit 21, which is
`87 is compared with the unit ID number contained in
`the received message 79. If it is determined from such
`keyed by the unit key 42 stored in the unit key memory
`24, to encrypt the usage report. The authenticated usage 10 comparison 86 that the message 79 is not authentic, the
`report generation unit 21 provides the authenticated
`terminal 73 generates an error message 88 indicating
`that the received message 89 is not authentic. The error
`usage report 62, which includes the usage report in both
`encrypted and unencrypted form and is combined with
`message is then communicated to and displayed 89 at
`the unit ID number 39 for communication to the autho-
`the customer terminal 72.
`rization and key distribution terminal 10 as an authenti- 15
`If it is determined from the comparison 86 that the
`cated usage report and unit ID signal 63.
`message 79 is authentic, the terminal 73 performs a
`Together with the authenticated usage. report and
`credit check routine 90 for the customer terminal 72
`unit ID signal 63, there also is communicated to the
`identified by the unit ID number. If it is determined
`authorization and key distribution terminal lOan authen-
`from such credit check 90, that credit should not be
`ticated credit and debit status report and unit ID signal 20 extended for retrieval of data from the requested file by
`64. This signal 64 is provided in response to either oper-
`the identified customer terminal 72, the authorization
`ation of the keyboard 33 or the interrogation signal 61
`and key distribution terminal 73 generates an error mes-
`being directed to the retrieval control unit 22. Signals 66
`sage 88 indicating that credit is not authorized and com-
`and 67 respectively indicating the status of the credit 25 municates the error message to the customer terminal
`for display 89 at the customer terminal 72.
`and debit registers 27 and 28 are encrypted by the au-
`thenticated credit and debit · status report generation
`If it is determined from the credit check 90 that credit
`unit 20, which is keyed by the unit key 42 stored in the
`should be extended for retrieval of data from the re-
`unit key memory 24. The authenticated credit and debit
`quested file by the identified customer terminal 72, the
`status report generator 20 provides an authenticated 30 file key 85 is encrypted in the unit key 81 for the identi-
`credit and debit status report signal 68, which includes
`fled customer terminal 72 by an encryption routine 91
`such status report in both encrypted and unencrypted
`and the encrypted file key 92 is communicated to the
`form, and which is combined with the unit ID number
`· customer terminal 72.
`The customer terminal 72 than performs a decryption
`39 to provide the authenticated credit and debit status
`report and unit ID signal 64.
`35 routine 93, wherein the unit key 78 stored therein is
`The credit register 27, the debit register 28 and the
`used to decrypt the encrypted file key 92.
`Next, the customer terminal performs a decryption
`use history storage unit 23 for any given vendor can be
`reset to zero when desired in response to a refresh regis-
`routine 94, wherein the decrypted file key 95 is used to
`ters command 70 (FIG. 1) communicated from the
`decrypt the file header for the encrypted data file 96
`authorization and key distribution terminal 10. Such 40 identified by the desired file number 77. The decrypted
`file header 97 is communicated to the authorization and
`command 70 would be communicated, for example,
`key distribution terminal 73, which in turn performs a
`when a given customer · terminal account associated
`with a given vendor is closed out.
`comparison routine 98 to determine whether the de-
`In an alternative preferred embodiment, as shown in
`crypted header is the correct header for the file identi-
`FIG. 3, a separate file use request is communicated from 45 fled by the decrypted file number 84. This routine 98
`a customer data retrieval terminal 72 to an authorization
`verifies the decryption of the encrypted file key 92
`and key distribution terminal 73 for each data file that is
`communicated to the customer terminal 72 prior to
`be retrieved. The operational routines .illustrated in
`debiting the account maintained for the customer termi-
`FIG. 3 are implemented by a microcomputer.
`nal 72. Ifit is determined that the correct header has not
`Initially, a routine 75 is performed in the customer so been decrypted, the terminal 73 performs an error mes-
`sage routine 88, wherein an error message indicating the
`terminal 72. for generating an authenticated file use
`request containing a unit ID number 76 for the cus-
`error is generated and communicated to the customer
`tamer terminal 72 and the file number 77 for the desired
`terminal 72 for display 89.
`file. The generated file use request is encrypted in the
`If it is determined that the correct header has been
`unit encryption key 71 that is unique to the customer 55 decrypted, an enable signal is communicated to the
`customer terminal 72 to enable a data file decryption
`terminal 72 and communicated to the authorization and
`key distribution terminal 73 in an authenticated file use
`routine 100. The enable signal 99 also initiates a routine
`request message 79 that also includes the unencrypted
`101 in the j authorization and key distribution terminal
`unit ID nummber 76.
`73, wherein a transaction report identifying the cus-
`Upon receipt of the message 79, the authorization and 60 tomer terminal 72 and the data file is generated and
`key distribution terminal 73 performs a look-up routine
`communicated to a billing terminal 102 for billing the
`80 for looking up the unit key for the customer terminal
`customer associated with the customer terminal 72 for
`72 identified by the received unencrypted unit ID num-
`the retrievalof data from the requested file.
`In an alternative preferred embodiment shown in
`ber.
`Using the looked-up unit key 81, the authorization 65 FIG. 4, an authorization terminal 105 and a customer
`terminal 106 perform several authentication and report-
`and key distribution terminal 73 performs a decryption
`routine 12 for decrypting the unit ID number and the
`ing routines. The operational routines illustrated in
`desired file ID number from the received message 79.
`FIG. 4 are implemented by a microcomputer.
`
`APPLE EXHIBIT 1081
`APPLE v. PMC
`IPR2016-01520
`Page 9
`
`

`

`5,010,571
`
`20
`
`7
`Initially, the customer terminal 106 performs a rou(cid:173)
`tine 107 wherein an authorization request 108 contain(cid:173)
`ing the customer terminal unit ID number 109 is gener(cid:173)
`ated and communicated to the authorization terminal
`105. The authorization terminal 105 performs a look-up 5
`routine 109 for looking up the unit key 110 for the cus(cid:173)
`tomer terminal 106 identified by the unit ID number
`contained in the request 108.
`The authorization terminal then performs an authen(cid:173)
`ticated signal generation routine 111, wherein the unit 10
`key 110 is used to encrypt an interrogation command.
`The encrypted interrogation command 112 is combines
`with the unencrypted interrogation command to pro(cid:173)
`vide an authenticated interrogation command, which is
`communicated othe customer terminal 106, where it is 15
`authenticated by using the unit key 113 stored therein.
`The routines for generating authenticated given data
`that are described herein include the steps ofencrypting
`the given data and generating a signal that includes the
`given data in both encrypted and unencrypted form.
`The routines for authenticating given data that are
`described herein include the steps of decrypting given
`data that has been encrypted and comparing the de(cid:173)
`crypted data to the given data in unencrypted form.
`It is to be understood thl!t other techniques of gener~ 25
`ating authenticated data and of authenticating given
`data may be used in other embodiments of the present
`invention.
`The customer terminal 106 responds to the interroga(cid:173)
`tion command 112 by retrieving a use history report 114 30
`for the user terminal 106 from a use history storage unit
`115 and a debit and credit report 116 for the customer
`terminal 106 from debit and credit registers 117. The
`customer terminal then performs an authentication rou(cid:173)
`tine 118, wherein the unit key 113 is used to encrypt the 35
`use history report 114 and the debit and credit report
`116. An authenticated report 119 including the reports
`114 and 116 in both encrypted and unencrypted form is
`communicated to the authorization terminal 105.
`The authorizaiton terminal performs a routine 121 40
`using the unit key 110 to authenticate the report 119.
`The use history and debit and credit reports also are
`processed in lation to each other in accordance with
`certain criteria to determine their authenticity. If it is
`determined that the rport 119 is not authentic, a report 45
`123 is generated in the authorization terminal 105 and an
`error message is communicated to and displayed 124 in
`customer terminal 106.
`If it is determined that the reports 119 is authentic, the
`use history is stored 125 for report 125a to a billing 50
`terminal 126 and the authorization terminal 105 per(cid:173)
`forms a credit check routine 127 in view of the status of
`the accounts for the customer terminal 106, as updated
`by the authenticated report 119, to determine whether
`the customer ter