throbber
Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 1 of 19 PageID #: 239
`
`Petitioner Ex. 1044 Page 1
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 2 of 19 PageID #: 240
`
`Petitioner Ex. 1044 Page 2
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 3 of 19 PageID #: 241
`
`Petitioner Ex. 1044 Page 3
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 4 of 19 PageID #: 242
`
`Petitioner Ex. 1044 Page 4
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 5 of 19 PageID #: 243
`
`Petitioner Ex. 1044 Page 5
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 6 of 19 PageID #: 244
`
`Petitioner Ex. 1044 Page 6
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 7 of 19 PageID #: 245
`
`Petitioner Ex. 1044 Page 7
`
`

`
`-------·------
`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 8 of 19 PageID #: 246
`
`would also readily recognize the patent discloses hardware, e.g., a summer, as structure capable
`,_,
`of generating licensee unique IDs. '216 Patent at col. 12, 11. 62-65. Therefore, one of ordinary
`
`skill in the art would read the '216 patent as disclosing both software and hardware as structures
`
`capable of performing the function of generating licensee unique IDs. Moreover, one of
`
`ordinary skill in the art would find no suggestion in the specification, or within the art, to limit
`
`the invention as claimed only to a hardware implementation
`
`Mode-Switching Means
`
`11.
`
`One of ordinary skill in the art would recognize the structure disclosed by the
`
`'216 patent for performing the function of the mode-switching means can be software or
`
`hardware. First, one of ordinary skill in the art would readily recognize the '216 patent discloses
`
`software logic capable of acting as a mode switching means. See, e.g., '216 Patent at col. 6, 11.
`
`12-14; col. 7, 11. 36-50; col. 8, 11. 15-28; col. I 0, 11. 35-44; col. 11, 11. 5-13; col. 11, 1. 58 - col. 12,
`
`I. 2. Second, one of ordinary skill in the art would also readily recognize the patent discloses
`
`hardware, e.g., a comparator, as structure capable of generating licensee unique IDs. See, e.g.,
`
`'216 Patent at col. 13, 11. 37-40. Therefore, one of ordinary skill in the art would read the '216
`
`patent as disclosing both software and hardware as structures capable of performing the function
`
`of mode-switching means.
`
`Use Mode
`
`12.
`
`One of ordinary skill in the art would understand the term "use mode" as used in
`
`the context of the patent as having a meaning consistent with Uniloc's proposed construction.
`
`Microsoft's proposed construction reads in an additional specification passage into the term.
`
`8
`
`Klausner Declaration re: Plaintiff's Opening
`Claim Construction Brief
`
`Petitioner Ex. 1044 Page 8
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 9 of 19 PageID #: 247
`
`Petitioner Ex. 1044 Page 9
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 10 of 19 PageID #: 248
`
`Information Uniquely Descriptive of the Intended Licensee
`
`13.
`
`One of ordinary skill in the art would understand this term as having a meaning
`
`consistent with Uniloc's proposed construction. Microsoft's proposed construction adds several
`
`limitations that one of ordinary skill in the art would understand is inconsistent with the intrinsic
`
`evidence. First, as previously discussed, the patent uses the term ''unique" in a manner
`
`consistent with its use in the field to mean a low probability of duplication, and expressly
`
`contemplates information that is not one-of-a-kind but that is nonetheless unique. Second,
`
`Microsoft appears to be limiting its definition to the specification's disclosure of information
`
`such as credit card information and name. As an initial matter, even this type of information is
`
`often not "one-of-a-kind." People have the same name, and people can share credit card
`
`numbers. More importantly, the specification discloses other types of information that can be
`
`uniquely descriptive of an intending licensee such as Product IDs. Therefore, one of ordinary
`
`skill in the art would understand this term as having a meaning consistent with Uniloc's
`
`proposed definition.
`
`Checking by the Registration Authority that Information Unique to the User is
`Correctly Entered
`
`14.
`
`One of ordinary skill in the art would understand this term, as used in the '216
`
`patent, as having a meaning consistent with Uniloc's proposed construction. Microsoft's
`
`proposed construction is inconsistent with how one of ordinary skill in the art would understand
`
`the disclosure in the specification, and with how one of ordinary skill in the art would understand
`
`the ways to implement the disclosed invention. First, there is no requirement in the claim or in
`
`the other intrinsic evidence that the remote side check "at the point in time when the security key
`
`is generated on the local side." In fact, some of the embodiments disclose exactly the opposite of
`
`10
`
`Klausner Declaration re: Plaintiff's Opening
`Claim Construction Brief
`
`Petitioner Ex. 1044 Page 10
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 11 of 19 PageID #: 249
`
`what Microsoft requires of the claim -- the remote authority checks at some point after the
`
`security key is generated on the local side. Moreover, from an implementation perspective, one
`
`of ordinary skill in the art would find little value in the simultaneity required by Microsoft.
`
`Therefore, one of ordinary skill in the art would not read the' claim language to include the
`
`limitation added by Microsoft. Second, one of ordinary skill in the art would not read the term at
`, ..
`issue to require, as Microsoft does, that the "rem~te side checks to ensure that information
`
`unique to the user was entered by the user without errors or mis-entry, with respect to how the
`
`. !
`
`user intended to enter it." As an initial matter, this form of checking required by Microsoft is
`
`found nowhere in the intrinsic evidence. Rather, the intrinsic evidence makes clear that the
`
`system verifies that the information is correctly entered by comparing the outputs of the
`
`algorithm on each side. That is, the remote side checks the information by inputting the
`
`information into the algorithm on the remote side. One of ordinary skill in the art would read the
`
`file history as supporting this interpretation. UNILOC 0128 (Response to First Office Action at
`
`3) ("The uniqueness is ultimately provided by the end users of the software in the course of
`
`supplying their own identification details, which are subsequently checked by use of a matching
`
`algorithm at a remote location."); UNILOC 0143 (Response to Second Office Action at 6) ("The
`
`algorithm used to generate locally the "Licensee Unique ID" is replicated remotely for the
`
`purposes of remote generation of a separate "Licensee Unique ID" for matching purposes.")
`
`Finally, the requirement Microsoft seeks to add is impossible in many circumstances. Aside
`
`from circumstances such as spell-check, Microsoft's reading of the claim term would require the
`
`computer to understand the subjective intent of the user. For all of these reasons, one of ordinary
`
`skill in the art would interpret this term consistent with Uniloc's proposed construction.
`
`Klausner Declaration re: Plaintiff's Opening
`Claim Construction Brief
`
`Petitioner Ex. 1044 Page 11
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 12 of 19 PageID #: 250
`
`Petitioner Ex. 1044 Page 12
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 13 of 19 PageID #: 251
`
`Petitioner Ex. 1044 Page 13
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 14 of 19 PageID #: 252
`
`Petitioner Ex. 1044 Page 14
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 15 of 19 PageID #: 253
`
`Petitioner Ex. 1044 Page 15
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 16 of 19 PageID #: 254
`
`Petitioner Ex. 1044 Page 16
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 17 of 19 PageID #: 255
`
`Wherein said registration system is replicated at the registration authority
`
`22.
`
`One of ordinary skill in the art would understand this phrase as used in the patent
`
`as having a meaning consistent with the construction proposed by Uniloc. Microsoft first
`
`requires all of the features present on the local side be present on the remote side. This makes no
`
`sense. First, all the embodiments relate to replicating the licensee unique ID generating means
`
`on the remote side. Second, one of ordinary skill in the art would understand there would be no
`
`reason at all to include functionality such as the mode-switching means on the remote side.
`
`Finally, one of ordinary skill in the art would understand Microsoft's reading of the claim as
`
`covering no embodiments of the patent. Moreover, one of ordinary skill in the art would
`
`recognize Microsoft is seeking to import its misreading of "checking" into this claim term. As
`
`previously discussed, this is wrong. Finally, as discussed elsewhere, Microsoft is misreading the
`
`file history as clearly and unambiguously disclai~ing the use of encryption/decryption when one
`
`of ordinary skill in the art would clearly recoguize it does not. For all of these reasons, one of
`
`ordinary skill in the art would understand this phrase as used in the patent as having a meaning
`
`consistent with Uniloc's construction.
`
`Has matched
`
`23.
`
`One of ordinary skill in the art would understand the term "has matched" as used
`
`in the context of the '216 patent as having a meaning consistent with Uniloc's proposed
`
`construction. First, one of ordinary skill in the art would not require something to match as a
`
`result of a "direct comparison." Particularly in the art, matching can involve an indirect
`
`comparison. For example, two groups can match after an indirect comparison shows an
`
`association between the two groups. As a simple example, there are two sets of numbers below:
`
`17
`
`Klausner Declaration re: Plaintiff's Opening
`Claim Construction Brief
`
`Petitioner Ex. 1044 Page 17
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 18 of 19 PageID #: 256
`
`I
`
`I
`
`2
`
`4
`
`3
`
`9
`
`4
`
`16
`
`5
`
`25
`
`6
`
`36
`
`7
`
`49
`
`8
`
`64
`
`A direct comparison of the top set of numbers with the bottom set of numbers would lead
`
`one to conclude these sets of numbers do not match. However, when the square of the top
`
`numbers are compared with the bottom number they do match -- as a result of an indirect
`
`comparison. Similarly, one of ordinary skill in the art would also understand that two values can
`
`match even though the are not the same. As another simple example, consider the following two
`
`numbers:
`
`1st Number: 123456789
`
`2nd Number: 929496989
`
`Obviously, these numbers are not the same, and would not match under Microsoft's
`
`construction. However, if the test is whether the numbers in the even numbered-position, i.e.,
`
`the second, fourth, sixth and eighth place, are the same then these numbers do match. Thus, one
`
`of ordinary skill in the art recognizes two values may not be the same but can still match.
`
`Finally, combining the two scenarios, consider the following two numbers:
`
`1st Number: 123456789
`
`2nd Number: 949169369649
`
`Obviously, these two numbers are not the same. However, the values between each "9"
`
`in the 2nd number is the square of the values in the even-numbered position of the 1st number,
`
`and the 2nd number matches the 1st number based on this correspondence. These types of
`
`relationships and correspondences are an important part of computer programming, and one of
`
`ordinary skill in the art would understand the term "has matched" to include these concepts.
`
`18
`
`Klausner Declaration re: Plaintiff's Opening
`Claim Consttuction Brief
`
`Petitioner Ex. 1044 Page 18
`
`

`
`Case 1:03-cv-00440-WY-DLM Document 138 Filed 02/24/06 Page 19 of 19 PageID #: 257
`
`Petitioner Ex. 1044 Page 19

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