throbber
Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 1 of 10
`
`Exhibit 18
`
`

`

`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 2 of 10
`
`e
`beeble~
`
`••
`
`Hardware Stamping™
`Technology Overvievv
`White Paper
`
`Version 1 :o
`
`Author:
`
`Miki Mullor, CTO
`
`Published:
`
`September, 2001
`
`Exhibit A
`·"
`'--- - -
`
`ANCORA_00000272
`
`

`

`••
`
`•
`
`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 3 of 10
`
`' • beeble~
`
`...
`
`Complying with all applicable copyright laws is the
`responsibility of the reader. Without limiting the rights
`under copyright, no part of this documenJ may be
`reproduced, stored in or introduced into a retrieval system,
`or transmitted in any form or by any means (electronic,
`mechanical, photocopying, recording, or otherwise), or for
`any purpose, without the express written permission of
`Beeb/e, Inc.
`Beeble may have patents, patent applications, trademarks,
`copyrights, or other intellectual property rights covering
`subject matter in this document. Except as expressly
`provided in any wrillen license agreement from Beeb/e, the
`furnishing of this document does not give you any license Jo
`these patents, trademarks, copyrighls, or other intellectual
`property.
`© 200/ Beeble, Inc. All rights reserved
`The names of actual companies and products mentioned
`herein may be the trademarks of their respective owners.
`Beeb/e, Inc., 22 Parthenia, Irvine, CA 92606 USA
`09/2001
`
`© 2001 Copyright Beeble, lnc.
`
`-Confidential-
`
`Page 2 of9
`
`ANCORA_00000273
`
`

`

`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 4 of 10
`
`e
`
`e
`beceble~
`
`System Architecture
`
`The following diagram outlines Beeble' s general architecture and main
`components. In the diagram, BXL™ and Hardware Stamping™ are proprietary
`processes that encapsulate Beeble's technological innovations. This white paper
`focuses on Hardware Stamping™, therefore BXL will not be discussed.
`
`beeble~
`
`License Server
`
`beeble~
`
`Web Portals
`
`- - - - - , G I
`
`_ ___ J
`
`beeble~
`Licensing 1 - - - - - i
`.......,,_ ..... Customer PC
`Manager
`
`,ii r BXl License ~
`
`BXL Statements
`Interpretation
`
`Beebllzed
`Application
`
`( BXL )
`
`Figure I: Beeble System Architecture
`
`Software Vendor
`
`Software Distribution
`C rn
`w
`
`:::!:
`w
`0
`
`© 2001 Copyright Beeble, Inc.
`
`-Confidential-
`
`Page 3 of9
`
`ANCORA_00000274
`
`

`

`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 5 of 10
`
`e
`beeble~
`
`Hardware Stamping TM
`
`Hardware Stamping is a method of binding a software product with a specific
`computer. The act of stamping is achieved by writing BXL licenses to non(cid:173)
`volatile memory chips (EEPROM) present in PCs. More specifically, Beeble
`writes BXL licenses to the PC's BIOS EEPROM. EEPROMs are electronic chips
`that can hold data with no dependency on electric current. EEPROMs do not
`have mechanical parts in them and are considered an extremely reliable method of
`storage. Writing to EEPROMs can be accomplished through software; therefore
`Beeble does not require any additional hardware to be added to the PC.
`
`BIOS EEPROM provide a stable, predicted envirorunent for holding BXL
`licenses. Unlike disk drives, access to the BIOS is limited and not supported in
`operating systems. In order for a user to access the BIOS EEPROM proprietary
`software would need to be developed, since this type of software is not
`commercially available.
`
`Beeble accesses its BXL licenses from the BIOS EEPROM through direct
`memory read and write operations, therefore it is untraceable. Other software
`licensing systems, which rely on standard OS IO support to access licensing
`information, can be easily traced by means the OS provides.
`
`Access to the BIOS EEPROM (where BXL licenses are stored) is not trivial,
`requires thought and effort: therefore it is possible to assume that any
`modifications made to BXL licenses that are not performed by Beeble are of
`malicious in nature. Detecting differences between Beeble's records of installed
`licenses and actual licenses present on the PC can identify illegal tampering with
`Beeble's licenses installed and prove fraud. Beeble's ability to detect fraud is a
`key component in deterring potential hackers from tampering with the Beeble
`system.
`Hardware stamping is patent pending in the US.
`
`© 2001 Copyright Beeble, lnc.
`
`-Confidential-
`
`Page 4 of9
`
`ANCORA_00000275
`
`

`

`•
`
`•
`
`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 6 of 10
`
`e
`beeble~
`
`Beeble Client Architecture
`
`Beeble Client Side component include a Kernel mode windows driver, and a
`control panel applet.
`
`Winlnet
`
`License Manager
`
`Beeblized Application
`
`Control Panel
`Applet
`
`BXL Interface
`Library
`
`Beeble Kernel-mode Driver
`
`Beeble File H
`
`
`H
`BXL
`~-Sys_ tem_~H~_0eayp _ __ 10_r ~H ~_E_JCeCU_ t_or~
`
`BIOS EEPROM
`
`Figure 2: Beeble Client Architecture
`
`© 2001 Copyright Beeble, Inc.
`
`-Confidential-
`
`Page 5 of 9
`
`ANCORA_00000276
`
`

`

`•
`
`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 7 of 10
`
`e
`bceceble~
`
`Beeble License Manager
`
`Beeble License Manager is a windows control panel applet that allows users to
`self manage Beeb le licenses installed on their machine. The license manager is
`one focal point from which from users can purchase software, rent applications,
`manage licenses (transfer, return), deploy corporate licenses, etc.
`
`1·
`' I Beeblizer Version 1.0
`
`: beeble~
`
`' -
`
`---------
`
`. - ~- -- -----------· - - ·--- -
`Currently Installed Applications
`
`i!!illiiJIE3
`
`- -
`
`··-
`
`·-=
`
`Application Name
`~ Microsoft Power Point
`~ Microsoft Publisher
`Iii Microsoft Word
`!!ii Microsoft Excel
`~Scribble
`r. Adobe Photoshop
`(EAdobe Acrobat
`'9 Real Movie Player
`ml Quicklime
`
`I
`
`I
`
`License Status
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`Unlicensed
`
`Figure 3: Beeble License Manager
`
`The Beeble License Manager manages all Beeblized applications installed on the
`PC, of all vendors using Beeble, simplifying the end-user's experience. The
`Beeble Licensing Manager will be installed during the installation of any
`Beeblized application on the targeted PC.
`
`The control panel applet (pictured above) is responsible for installation and
`removal ofBeeble licenses. This installation and removal requires
`
`© 200 I Copyright Beeble, Inc.
`
`-Confidential-
`
`Page 6 of9
`
`ANCORA_00000277
`
`

`

`•
`
`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 8 of 10
`
`e
`beeble~
`
`communications to Beeble' s license server. Beeble client communicates to the
`license server using HTTP protocol over the Internet, secured with SSL. This
`standard communication method allows Beeble interoperability with different
`kinds of Firewalls. Beeble uses Window's standard components (Winlnet) to
`handle HTTP communications to the license server; hence no changes to the OS
`configuration are required. The Beeble Protocol (BP) defines the language used
`to communicate messages between the user and Client-License server.
`
`Kernel mode Driver
`
`Beeble's core technology is implemented in a Kernel mode driver. A driver-level
`implementation allows Beeble direct access to BIOS EEPROM needed to store
`licenses and maximum control on Beeblized applications.
`
`The driver is responsible for maintaining Beeble licenses in the EEPROM. This is
`achieved by a "Beeble File System" component. This component is responsible
`for locating space to store Beeble licenses in the BIOS EEPROM and executing
`the proper instruction set for writing data to the Flash chip.
`
`Accomplishing this challenging task is two-fold:
`
`I. Data Location
`
`The BIOS is a central part of the PC. In order to ensure integrity of the Beeble
`licenses, Beeble File System component must ensure no other process
`overwrites Beeble's data. Also, each BIOS' memory map is different in its
`structure hence it is impossible to assume that specific available memory
`locations in one PC's BIOS will be available in another's.
`
`The solution to this problem is to utilize a BIOS feature called D:rvtl 1 (stands
`for Desktop Management Interface), also known as SMBIOS. DMI is an
`industry standard for management of PC hardware configuration and has been
`adopted and deployed in PCs for over 10 years. The D:rvtl stores system
`configuration data in the BIOS EEPROM in a form of linked data structures.
`DMI specifications allow the addition of custom structures. Beeble stores data
`in the BIOS by creating a new custom DMI structure and writing it to the end
`
`1 SMBIOS Reference Specificatiori, Version 2.2, 16 March 1998, page 25 (http://www.dmtf.org)
`
`-
`
`© 200 I Copyright Beeble, Inc.
`
`-Confidential-
`
`Page 7 of9
`
`ANCORA_00000278
`
`

`

`r-
`
`••
`
`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 9 of 10
`
`e
`beeble~
`
`of the existing DMI structure table. Beeb le ensures compatibility with BIOS
`memory map and achieves integrity for its data for the data is written in an
`area pre-allocated by the BIOS manufacturer for DMI data and by disguising
`Beeble data as legitimate DMI data.
`
`2. EEPROM Writing
`
`Beeble will attempt to write license data by utilizing the DMI Function 52h2,
`which is designed to write DMI structures to EEPROM. IfBIOS
`manufactures do not support DMI function 52h, then Beeble will write to a
`EEPROM generically. Beeble's File System incorporates a driver that
`contains a library of different EEPROM chips and proper instructions set to
`write to different chip manufacturers. If the Beeble driver does not recognize
`the EEPROM, the Beeble driver will attempt to download a new driver from
`the Beeble License server.
`
`The driver also encapsulated BXL elements implementation: during run-time, the
`driver will execute BXL tokens according to their definition in the BXL license
`for that specific application.
`
`The driver is also responsible to compute BXL code segment entry point from the
`license and place the proper APC call to the entry point.
`
`The driver's memory footprint is estimated at about 50KB. The drive's impact on
`the CPU cycles is minimal and negligible.
`
`2 SMBIOS Reference Specifications, Version 2.2, 16 March 1998, page 11
`(htttp://www.dJntf.org)
`
`© 2001 Copyright Beeble, lnc.
`
`-Confidential-
`
`Page 8 of9
`
`ANCORA_00000279
`
`

`

`Case 1:20-cv-00034-ADA Document 50-2 Filed 04/10/20 Page 10 of 10
`
`••
`
`-beeble~
`
`Summary
`
`Beeble is a next generation software licensing technology that delivers a
`technological breakthrough over other software licensing technologies. Beeble
`focuses on addressing the needs and requirements of large software companies
`with a large customer base and a variety of distribution channels.
`
`Beeble's highlight features include:
`
`• Simplicity, End-user friendly -
`Designed with large software companies' needs in mind,
`Beeble supports all real life scenarios that end-users
`encounter (license transferring, PC upgrades, software
`returns, etc.) while maximizing protection of intellectual
`property. Beeble is an easy to use system designed to
`reduce support calls and maximize market potential for
`software companies.
`• Security, Fraud detection capabilities -
`Beeble's security features are comprised of several lines of
`defense to protect intellectual property and deter hackers
`from attacking the system. Beeble is the first software
`licensing system which provides detection capabilities of
`system integrity infringement.
`
`• Flexibility -
`
`Compatible with any sales model (Rent, Volume Licensing,
`OEM bundling, Retail, etc.) and any distribution media
`(CDROM, Floppy, DVD, ESD, etc.)
`• Stability, Reliable -
`The system is designed for a high tolerance level of PC
`environment changes including hard drive failure, hardware
`configuration changes, virus attacks etc.
`
`• Low-cost -
`
`Beeble is a software product with no production costs
`associated with it.
`• Compatibility -
`Beeble is compatible with all Intel x86 based PCs
`manufactured since the early 90's.
`
`© 2001 Copyright Beeble, lnc.
`
`-Confidential-
`
`Page 9 of9
`
`ANCORA_00000280
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket