throbber
 
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`May 3, 2001
`
`August 2, 2005
`
`In re U.S. Patent No. 6,925,481
`
`Filed:
`
`Issued:
`
`Inventor: Singhal et al.
`
`Assignee: Clouding IP, LLC
`
`Title:
`
`Technique for Enabling Remote Data Access and Manipulation from
`a Pervasive Device
`
`
`
`Mail Stop PATENT BOARD, PTAB
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`PETITION FOR INTER PARTES REVIEW OF U.S. PATENT NO. 6,925,481
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.100 ET SEQ.
`
`
`
`i
`
`

`

`
`TABLE OF CONTENTS
`
`TABLE OF CONTENTS ............................................................................................................. ii
`EXHIBIT LIST ............................................................................................................................ iii
`I.
`INTRODUCTION ................................................................................................................. 1
`II. MANDATORY NOTICES ................................................................................................... 2
`A. Real Party-In-Interest .................................................................................................... 3
`B. Related Maters ................................................................................................................ 3
`C. Lead And Back-Up Counsel ........................................................................................... 3
`D.
`Service Information ........................................................................................................ 3
`III. PAYMENT OF FEES ........................................................................................................... 4
`IV. REQUIREMENTS FOR INTER PARTES REVIEW ........................................................ 4
`A. Grounds For Standing .................................................................................................... 4
`B.
`Identification of Challenge ............................................................................................. 5
`1. The specific art and statutory ground(s) on which the challenge is based .............. 5
`2. How the construed claims are unpatentable under the statutory grounds
`identified in 37 C.F.R. § 42.204(b)(2) and supporting evidence relied upon to
`support the challenge .................................................................................................... 6
`V. FACTUAL BACKGROUND ............................................................................................... 7
`A. Declaration Evidence ...................................................................................................... 7
`B.
`The State of the Art......................................................................................................... 8
`C. The ‘349 Patent Application .......................................................................................... 9
`D.
`Prosecution History of the ‘481 Patent ....................................................................... 11
`VI. BROADEST REASONABLE CONSTRUCTION ........................................................... 11
`A. Location ......................................................................................................................... 12
`B. Means For Receiving .................................................................................................... 13
`C. Means For Obtaining .................................................................................................... 13
`D. Means For Determining ............................................................................................... 14
`E. Means For Returning ................................................................................................... 14
`F. Means For Requesting .................................................................................................. 15
`G. Means For Performing ................................................................................................. 15
`VII. REPRESENTATIVE PROPOSED REJECTIONS SHOWING THAT PETITIONER
`HAS A REASONABLE LIKELIHOOD OF PREVAILING ................................................. 16
`A. Claims 1, 2, 25, 28, and 50-57 Are Anticipated by Schilit under 35 U.S.C. § 102(e)
`......................................................................................................................................... 16
`B. Claim 32 Is Rendered Obvious by Schilit in View of Hutsch Under 35 U.S.C. § 103
`......................................................................................................................................... 29
`C. Claims 1, 2, 25, 28, and 50-57 Are Rendered Obvious by Flynn in View of Schilit
`Under 35 U.S.C. § 103. .................................................................................................. 32
`D. Claim 32 is Rendered Obvious by Flynn in View of Schilit and Further in View of
`Hutsch Under 35 U.S.C. § 103 ..................................................................................... 47
`E. Claims 1, 2, 25, 28, and 50-57 are Rendered Obvious by Barrett in view of Schilit
`Under 35 U.S.C. § 103 ................................................................................................... 49
`VIII. CONCLUSION ............................................................................................................. 60
`CERTIFICATE OF SERVICE ................................................................................................. 61
`
`
`
`ii
`
`

`

`
`1001
`
`1002
`
`
`1003
`
`1004
`
`1005
`
`
`1006
`
`
`1007
`
`EXHIBIT LIST
`
`U.S. Patent No. 6,925,481 to Singhal et al.
`
`Excerpts from the Prosecution History of Application No.
`09/848,394, which matured into the ‘481 patent.
`
`U.S. Patent No. 6,670,968 to Schilit et al.
`
`U.S. Patent No. 7,269,664 to Hutsch et al.
`
`Flynn, M., et al., “The Satchel System Architecture: Mobile
`Access to Documents and Services,” Mobile Networks and
`Applications, Vol. 5 (December 2000).
`
`Barrett, R., et al., “Intermediaries: New Places for Producing
`and Manipulating Web Content,” Computer Networks and
`ISDN Systems, Vol. 30 (April 1998).
`
`Declaration of Dr. Benjamin B. Bederson, Ph.D.
`
`
`
`
`
`
`
`
`
`
`
`iii
`
`

`

`
`I.
`
`INTRODUCTION
`
`Petitioner Oracle Corporation (“Oracle” or “Petitioner”) respectfully
`
`requests inter partes review for claims 1, 2, 25, 28, 32, and 50-57 of U.S. Patent
`
`No. 6,924,481 (the “’481 patent,” attached as Ex. 1001) in accordance with 35
`
`U.S.C. §§ 311–319 and 37 C.F.R. § 42.100 et seq.
`
`The ‘481 patent is generally directed to methods and systems for enabling
`
`pervasive computing devices (e.g., the Palm Pilot PDA or the Compaq iPAQ
`
`Home Internet Appliance IA-1(Ex. 1001 at 1:23-25, 2:24-25)) to access and
`
`manipulate data, such as, for example, an internet web page or a document stored
`
`on a file server. (See id. at 3:28-33). More particularly, the ‘481 patent is directed
`
`to methods and systems wherein a series of proxy servers are used to (1) obtain
`
`data that was requested by a pervasive device, and (2) return the requested data to
`
`the pervasive device along with information regarding one or more data
`
`manipulation operations (e.g., printing and faxing) determined to be available for
`
`the obtained data. (See, e.g., id. at 3:28-3, claim 1).
`
`As demonstrated by various references which were not before the Examiner,
`
`this technique was developed and published years prior to the earliest effective
`
`filing date of the ‘481 patent. For instance, by 1997 proxy servers were being used
`
`to transform web page content for optimized display on web browsers. (Ex. 1007
`
`at ¶ 21). Moreover, by the mid-1990s, context-aware or location based computing
`
`
`
`1
`
`

`

`
`had rapidly spread across the academic community, leading to the development of
`
`the “ParcTab” mobile computer. (Id. at ¶¶ 22-24). ParcTab allowed users to
`
`wirelessly share a document with other nearby devices or manipulate a document –
`
`by faxing or printing it – to a nearby printer or fax machine. (Id.)
`
`The natural progression of this research led to the development of various
`
`proxy based systems in which data requested by a pervasive device was not only
`
`manipulated for optimal display on the requesting device, but also linked to
`
`services that could print or fax the requested data. For instance, U.S. Patent No.
`
`6,670,968 to Schilit et al. (“Schilit,” Ex. 1003) discloses a server which, in
`
`response to a data access request received from a mobile device, obtains the
`
`requested web documents, parses the content into selectable hyperlinks, and
`
`determines “situation, or context-appropriate services, such as printing or faxing,”
`
`which may be carried out on the obtained data. (Ex. 1003 at 5:34-51; Ex. 1007 at
`
`¶¶ 38, 39).
`
`Schilit and similar references were not before the Examiner during
`
`prosecution of the ‘481 patent. These references anticipate or render obvious the
`
`challenged claims of the ‘481 patent, as shown in the following discussion.
`
`II. MANDATORY NOTICES
`
`Pursuant to 37 C.F.R. § 42.8(a)(1), Oracle provides the following mandatory
`
`disclosures.
`
`
`
`2
`
`

`

`
`A. Real Party-In-Interest
`Pursuant to 37 C.F.R. § 42.8(b)(1), Petitioner certifies that Oracle is the real
`
`party-in-interest.
`
`B. Related Maters
`Pursuant to 37 C.F.R. § 42.8(b)(2), Petitioner states that the ‘481 Patent is
`
`asserted in co-pending litigation captioned Clouding IP, LLC v. Oracle Corp.,
`
`D.Del., Case No. 1:12-cv-00642. This litigation remains pending. The patents-in-
`
`suit are U.S. Patents 6,631,449; 6,918,014; 7,596,784; 7,065,637; 6,738,799;
`
`5,944,839; 5,825,891; 5,678,042; 5,495,607; 7,254,621; 6,925,481. This IPR
`
`petition is directed to U.S. Patent 6,925,481; however, petitions corresponding to
`
`the remaining patents will be filed in the forthcoming weeks.
`

`
`C. Lead And Back-Up Counsel
`
`Pursuant to 37 C.F.R. § 42.8(b)(3), Petitioner provides the following
`
`designation of counsel: Lead counsel is Greg Gardella (Reg. No. 46,045) and
`
`back-up counsel is Scott A. McKeown (Reg. No. 42,866).
`
`Service Information
`
`D.
`Pursuant to 37 C.F.R. § 42.8(b)(4), papers concerning this matter should be
`
`served on the following.
`
`Address: Greg Gardella or Scott McKeown
`Oblon Spivak
`1940 Duke Street
`Alexandria, VA 22314
`cpdocketgardella@oblon.com and
`3
`
`Email:
`
`
`
`

`

`
`cpdocketmckeown@oblon.com
`Telephone: (703) 413-3000
`Fax:
`
`(703) 413-2220
`
`
`III. PAYMENT OF FEES
`
`The undersigned authorizes the Office to charge $27,200 to Deposit Account
`
`No. 15-0030 as the fee required by 37 C.F.R. § 42.15(a) for this Petition for inter
`
`partes review. The undersigned further authorizes payment for any additional fees
`
`that might be due in connection with this Petition to be charged to the above
`
`referenced Deposit Account.
`
`IV. REQUIREMENTS FOR INTER PARTES REVIEW
`
`As set forth below and pursuant to 37 C.F.R. § 42.104, each requirement for
`
`inter partes review of the ‘481 patent is satisfied.
`
`A. Grounds For Standing
`Pursuant to 37 C.F.R. § 42.104(a), Petitioner hereby certifies that the ‘481
`
`patent is available for inter partes review and that the Petitioner is not barred or
`
`estopped from requesting inter partes review challenging the claims of the ‘481
`
`patent on the grounds identified herein. This is because the ‘481 patent has not
`
`been subject to a previous estoppel based proceeding of the AIA, and, the
`
`complaint served on Oracle referenced above in Section II(B) was served within
`
`the last 12 months.
`
`
`
`4
`
`

`

`
`B.
`Identification of Challenge
`Pursuant to 37 C.F.R. §§ 42.104(b) and (b)(1), Petitioner requests inter
`
`partes review of claims 1, 2, 25, 28, 32, and 50-57 of the ‘481 patent, and that the
`
`Patent Trial and Appeal Board (“PTAB”) invalidate the same.
`
`1.
`
`The Specific Art and Statutory Ground(s) on Which the
`Challenge is Based
`
`Pursuant to 37 C.F.R. § 42.204(b)(2), inter partes review of the ‘481 patent
`

`
`is requested in view of the following references, each of which is prior art to the
`
`‘481 patent under 35 U.S.C. § 102(a), (b), and/or (e):
`
`(1) U.S. Patent No. 6,670,968 to Schilit et al. (“Schilit,” Ex. 1003), issued
`
`December 30, 2003 from an application filed July 10, 2000. Schilit is prior art to
`
`the ‘481 patent under at least 35 U.S.C. § 102(e).
`
`(2) U.S. Patent No. 7,269,664 to Hutsch et al. (“Hutsch,” Ex. 1004),
`
`issued September 11, 2007 from an application filed January 12, 2001. Hutsch is
`
`prior art to the ‘481 patent under at least 35 U.S.C. § 102(e).
`
`(3)
`
`The Satchel System Architecture: Mobile Access to Documents and
`
`Services by Flynn, M., et al. (“Flynn,” Ex. 1005) published December 2000 in
`
`Mobile Networks and Applications, Vol. 5, Issue 4, pgs. 243-258. Flynn is prior
`
`art to the ‘481 patent under at least 35 U.S.C. § 102(a).
`
`(4)
`
`Intermediaries: New Places For Producing And Manipulating Web
`
`Content by Barrett, R., et al. (“Barrett,” Ex. 1006) published April 1998 in
`
`
`
`5
`
`

`

`
`Computer Networks and ISDN Systems, volume 30, pgs. 509-518. Barrett is prior
`
`art to the ‘481 patent under at least 35 U.S.C. § 102(b).
`
`Schilit (Ex. 1003) anticipates claims 1, 2, 25, 28, and 50-57 of the ‘481
`
`patent under 35 U.S.C. § 102(e). Claim 32 is rendered obvious by Schilit in view
`
`of Hutsch (Ex. 1004) under 35 U.S.C. § 103.
`
`Flynn (Ex. 1005) taken in view of Schilit renders obvious claims 1, 2, 25,
`
`28, and 50-57 of the ‘481 patent under 35 U.S.C. § 103. Claim 32 is rendered
`
`obvious by Flynn in view of Schilit and further in view of Hutsch under 35 U.S.C.
`
`§ 103.
`
`Barrett (Ex. 1006) taken in view of Schilit renders obvious claims 1, 2, 25,
`
`28, and 50-57 of the ‘481 patent under 35 U.S.C. § 103.
`
`2.
`
`How the Construed Claims Are Unpatentable Under the
`Statutory Grounds Identified in 37 C.F.R. § 42.204(B)(2)
`and Supporting Evidence Relied upon to Support the
`Challenge
`
`Pursuant to 37 C.F.R. § 42.204(b)(4), an explanation of how claims 1, 2, 25,
`
`  
`
`28, 32, and 50-57 of the ‘481 patent are unpatentable under the statutory grounds
`
`identified above, including the identification of where each element of the claim is
`
`found in the prior art, is provided in Section VII, below, in the form of claims
`
`charts. Pursuant to 37 C.F.R. § 42.204(b)(5), the exhibit numbers of the supporting
`
`evidence relied upon to support the challenges and the relevance of the evidence to
`
`the challenges raised, including identifying specific portions of the evidence that
`
`
`
`6
`
`

`

`
`support the challenges, are provided in Section VII, below, in the form of claim
`
`charts.
`
`V.
`
`FACTUAL BACKGROUND
`A. Declaration Evidence
`This Petition is supported by the declaration of Professor Benjamin B.
`
`Bederson from the University of Maryland. (Ex. 1007). Prof. Bederson offers his
`
`opinion with respect to the content and state of the prior art.
`
`Prof. Bederson is a Professor in the Computer Science Department and the
`
`Institute of Advanced Computer Studies at the University of Maryland. Prof.
`
`Bederson is also Co-Founder and Chief Scientist for Zumobi, Inc., a venture
`
`capital funded startup created to commercialize mobile media for cell phones, and
`
`the Co-Founder and Technical Director for the International Children’s Digital
`
`Library Foundation, which provides free online children’s books to its members.
`
`(Ex. 1007 at ¶ 1). Prof. Bederson is the author or co-author of 10 book chapters
`
`and over 100 technical articles directed to web browsing, mobile computing, user
`
`interfaces, user experience, and the software and technology underlying these
`
`systems. (Id. at ¶ 9). Prof. Bederson is also a co-inventor on 7 U.S. patents
`
`generally directed to user interfaces/experience. (Id. at ¶ 5). In 2011, Prof.
`
`Bederson was recognized as an Association of Computing Machinery (“ACM”)
`
`distinguished scientist and elected to the Computer-Human Interaction (“CHI”)
`
`
`
`7
`
`

`

`
`Academy for his substantial contributions made in the field of CHI. (Id. at ¶ 7).
`
`Prof. Bederson is also one of the principal inventors of the PadPrints’ proxy-based
`
`web browser that offered a graphical web history to users by visually showing
`
`what web pages a user had visited. (Id. at ¶ 19).
`
`B. The State of the Art
`Proxies work by intercepting all web traffic coming from and going to a web
`
`browser and, once intercepted, the proxy can manipulate the requested web page in
`
`any number of different ways. (Ex. 1007 at ¶ 19). By 1997, proxy servers were
`
`being used to modify web content based on the location of the client computer and
`
`to automatically re-author a web page designed for a desktop computer to
`
`appropriately display on a mobile web browser. (Id. at ¶ 21). By 1998, web
`
`proxies were enhanced to automatically manipulate requested content by “adding
`
`annotations, highlighting links, adding toolbars, translating document format (e.g.,
`
`from Rich Text Format to HTML), changing form information, and adding scripts”
`
`all before returning the content to the requesting device. (Id. at ¶ 42).
`
`Ubiquitous computing was developing in parallel with the aforementioned
`
`proxies. Ubiquitous computing was based on broadly available mobile computing
`
`devices. (Id. at ¶ 22). These devices, known as “Tabs” or “Pads,” continually
`
`tracked their location and, based on the device’s sensed location, offered various
`
`services to the user, such as document sharing, printing, or faxing. (Id. at ¶¶ 22-
`
`
`
`8
`
`

`

`
`25). The ubiquitous computing field quickly evolved into calling its work “context
`
`aware computing” upon the realization that location awareness, and the ability of a
`
`mobile device to interact with nearby printers, displays, facsimiles, etc. was at the
`
`core of the technology. (Id. at ¶ 28).
`
`With this deep research focus in mobile web browsing and contextual
`
`computing, the natural and obvious technological progression was to put all of
`
`these features together to offer mobile, web-based contextualized document
`
`services. (Id. at ¶¶ 30, 31). In this manner, rather than simply returning a
`
`requested web page that has been optimized for display on a requesting device, the
`
`returned data could also be contextualized, such that nearby services (e.g., printing
`
`and faxing) could be executed. (Id.). For instance, U.S. Patent No. 6,670,968 to
`
`Schilit et al. (“Schilit,” Ex. 1003) discloses a server which, in response to a data
`
`access request received from a mobile device, obtains the requested web
`
`documents, parses the content into selectable hyperlinks, and determines
`
`“situation, or context-appropriate services, such as printing or faxing,” which may
`
`be carried out on the obtained data. (Ex. 1003 at 5:34-51; Ex. 1007 at ¶¶ 38, 39).
`
`C. The ‘349 Patent Application
`Application No. 09/848,349 (“the ‘349 application”)) was filed May 3, 2001
`
`and does not claim priority to a prior application. The ‘349 application discussed
`
`methods and systems for enabling pervasive computing devices to access and
`
`
`
`9
`
`

`

`
`manipulate data, such as, for example, content stored on a web server, or a
`
`document stored on a file server. (See, e.g., Ex. 1001 at 3:28-33). First, the
`
`pervasive device submits a request for information (e.g., through a web browser),
`
`which is received by a protocol proxy. (See id. at 6:33-41, 10:17-22). Second, the
`
`protocol proxy forwards the data request from the pervasive device to the
`
`appropriate information source, such as a web server. (See id. at 5:42-56; 10:29-
`
`34). Third, after receiving the requested data from the appropriate information
`
`source, the protocol proxy, by querying a data manipulation server (“DMS”),
`
`determines what services are available to manipulate the retrieved content. (See id.
`
`at 10:35-53). The DMS maintains a repository of available services for different
`
`types of data (See id. at 7:49-54) and forwards content to be manipulated to the
`
`appropriate output agent. (See id. at 7:13-16). Services may include, for example,
`
`printing, faxing, or e-mailing the retrieved content. (See id. at 3:33-37). Fourth,
`
`the protocol proxy forwards the retrieved content, along with a list of available
`
`services, to the requesting device. (See id. at 15:52-54, Fig. 1, message flow 7).
`
`Preferably, the list of available services will comprise a set of links, which
`
`correspond to each available service. (See id. at 12:3-14). The list of available
`
`services may be limited to those services available at the device’s location. (See
`
`id. at 11:28-31). Lastly, assuming the user of the pervasive device invokes an
`
`
`
`10
`
`

`

`
`
`
`availablle service rrequest, thee request iss received
`
`
`
`
`
`
`
`
`
`by the DMMS and, theereafter,
`
`
`
` 4).
`executed. (See, e.g., id.16:332-34, Fig.
`
`
`
`
`
`
`
`D. Pros
`
`
`
`
`ecution History of tthe ‘481 Paatent
`
`
`
`
`
`
`
`
`
`
`
`
`
`TThe ‘349 appplication rreceived a first actionn Notice o
`
`
`
`ce, which
`f Allowanc
`
`
`
`include the followwing statemment of reassons for al
`
`
`
`
`
`
`
`lowance:
`
`
`
`
`he ‘349 appwance). Thce of Allow2004 Noticember 24, 2(Ex. 10002 at Nove
`
`plication
`
`
`
`
`
`
`
`
`
`
`
`
`
`issued aas U.S. Pattent No. 6,9925,481, thhe subject
`
`
`
`
`
`
`
`
`
`of the instaant petitionn.
`
`
`
`
`
`
`
`
`
`TThus, the prrosecution history indicates thaat the ‘481
`
`
`
`
`
`
`
`
`
`s allowed
`patent was
`
`
`
`becausee the Examminer believved that thee prior art
`
`
`
`
`
`
`
`
`
`failed to teeach a dataa access
`
`
`
`
`
`techniquue whereinn (1) a dataa access reqquest is recceived fromm a pervassive devicee; (2)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`the pervvasive deviice in turn receives thhe requesteed data; annd (3) the ppervasive
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`device aalso receivves informaation regarding one oor more datta manipullation
`
`
`
`
`
`
`
`operatioons determmined to be available ffor the obttained dataa.
`
`
`
`
`
`
`
`
`
`
`
`
`
`VI. BBROADESST REASOONABLE CONSTRRUCTIONN
`
`
`
`
`
`
`
`
`
`
`
`
`
`BBecause thee standardss of claim iinterpretatiion used byy the federral courts aare
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`differennt from the standards used by thhe Patent OOffice in cllaim examiination
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`proceeddings (incluuding this iinter partees review),
`
`
`
`
`
`
`
`
`
`
`
`
`
`any claimm interpretaations usedd or
`
`
`
`11
`
`

`

`
`applied in these proceedings are neither binding upon Petitioner in patent
`
`infringement litigation or on any other litigants, nor do such claim interpretations
`
`correspond to the construction of claims under the legal standards used by the
`
`courts. Accordingly, any interpretation of claims presented either implicitly or
`
`explicitly herein should not be viewed as constituting, in whole or in part,
`
`Petitioner’s own interpretation and/or construction of such claims for the purposes
`
`of litigation. Instead, any constructions in this proceeding should be viewed only
`
`under the “broadest reasonable construction” standard required here.
`
`All claimed terms not specifically addressed in this section have been
`
`accorded their broadest reasonable interpretation in light of the patent specification
`
`including their plain and ordinary meaning. Any claim term which uses the phrase
`
`“means for” is presumed for purposes of this petition to invoke 35 U.S.C. § 112 ¶
`
`6. (See, e.g., M.P.E.P. § 2181, Eighth Ed., Rev. Nine, August 2012).
`
`A. Location
`
`Challenged claims 1, 50, 52, 54, and 56 require a “location of each available
`
`data manipulation operation” to be returned to the requesting pervasive device
`
`along with the determined data manipulation operations. The ‘481 patent in one
`
`embodiment uses term “location” to refer to the physical location of a pervasive
`
`device relative to the physical location of available data manipulations. (See Ex.
`
`1001 at 11:28-57). However, the term “location,” given its broadest reasonable
`
`
`
`12
`
`

`

`
`interpretation in this proceeding, broadly corresponds to a URL or other similar
`
`reference specifying the location on a computer network of an available data
`
`manipulation. (See id. at 5:52-53, 9:10-14; Ex. 1007 at ¶ 15).
`
`B. Means For Receiving
`
`Claim 50 uses the term “means for receiving a data access request from a
`
`pervasive device.” Under the broadest reasonable interpretation of this limitation,
`
`the structure most closely corresponding to this means-plus-function element is a
`
`protocol proxy, which “provides a bridge between the client … and the information
`
`that it seeks to access and manipulate. A protocol proxy is responsible for
`
`accessing information on behalf of the client…” (Ex. 1001 at 5:43-47; see also
`
`Ex. 1007 at ¶46).
`
`C. Means For Obtaining
`
`Claim 50 uses the term “means for obtaining the requested data.” The
`
`specification does not clearly disclose structure for performing the function
`
`“obtaining the requested data.” Under the broadest reasonable interpretation of
`
`this limitation, however, the structure most closely corresponding to this means-
`
`plus-function element is either the protocol proxy which, “forwards the [data]
`
`request to the appropriate information source” (see Ex. 1001 at 10:29-33), or the
`
`file access proxy, which is used to “access data from a local repository, within
`
`remote data stores…” (Id. at 6:53-60; see also Ex. 1007 at ¶ 49).
`
`
`
`13
`
`

`

`
`D. Means For Determining
`
`Claim 50 uses the term “means for determining what data manipulation
`
`operations are available for the obtained data, as well as a location of each
`
`available data manipulation operations.” The specification does not clearly
`
`disclose structure for performing the function “determining what data manipulation
`
`operations are available for the obtained data, as well as a location of each
`
`available data manipulation operations.” Under the broadest reasonable
`
`interpretation of this limitation, however, the structure most closely corresponding
`
`to this means-plus-function element is either the protocol proxy or the data
`
`manipulation server (“DMS”). (Compare Ex. 1001 at 10:38-53 (stating that “[t]he
`
`protocol proxy then determines, in Block 340, which services are available to the
`
`WID for manipulating the returned content. … In a preferred embodiment, the
`
`protocol proxy issues a query to the DMS for a list of available services. … In an
`
`alternative embodiment, the protocol proxy may be statically pre-configured with a
`
`list of available services…”) with id. at 10:54-58 (stating that the DMS
`
`“determines which services are available for the data being returned to the WID”
`
`after being queried by the protocol proxy)). (See also Ex. 1007 at ¶ 52).
`
`E. Means For Returning
`
`Claim 50 uses the term “means for returning the determined data
`
`manipulation operations and locations to the pervasive device, in addition to the
`
`
`
`14
`
`

`

`
`obtained data.” Under the broadest reasonable interpretation of this limitation, the
`
`structure most closely corresponding to this means-plus-function element is the
`
`protocol proxy, which transmits “the content, along with the annotated list of
`
`available services,” to the pervasive device. (Ex. 1001 at 15:52-55, Fig. 1,
`
`message flow 7; see also Ex. 1007 at ¶ 60).
`
`F. Means For Requesting
`
`Claim 51 uses the term “means for requesting operation of a selection of the
`
`determined data manipulation operations.” Under the broadest reasonable
`
`interpretation of this limitation, the structure most closely corresponding to this
`
`means-plus function element is a user interface to execute a desired manipulation
`
`operation. (See Ex. 1001 at 18:8-15, Fig. 6A, elements 601-604; see also Ex. 1007
`
`at ¶ 63).
`
`G. Means For Performing
`
`Claim 51 uses the term “means for performing the requested operation,
`
`wherein the means for performing is executed by another device on behalf of the
`
`pervasive device.” Claim 53 uses the term “means for performing is executed by
`
`another device on behalf of the pervasive device.” The specification does not
`
`clearly disclose structure for performing the function “performing the requested
`
`operation, wherein the means for performing is executed by another device on
`
`behalf of the pervasive device.” Under the broadest reasonable interpretation of
`
`
`
`15
`
`

`

`
`this limitation, however, the structure most closely corresponding to this means-
`
`plus-function element is either the data output agents 170 or the DMS. (Compare
`
`Ex. 1001 at 9:44-46 (“[t]he DMS passes data to selected ones of these [data output]
`
`agents to perform the manipulation services which are managed by the DMS) with
`
`id. at 7:13-16 (stating that “[i]n its roll of providing data manipulation services,
`
`those services may be provided by the DMS either directly, or indirectly by
`
`invoking one or more data output agents 170…”)). (See also Ex. 1007 at ¶ 65).
`
`VII. REPRESENTATIVE PROPOSED REJECTIONS SHOWING THAT
`PETITIONER HAS A REASONABLE LIKELIHOOD OF
`PREVAILING
`
`The references addressed below each provide the teaching believed by the
`
`
`
`Examiner to be missing from the prior art and variously anticipate or render
`
`obvious the claimed subject matter. It should be understood that rejections may be
`
`premised on alternative combinations of these same references.
`
`A.
`
`Claims 1, 2, 25, 28, and 50-57 Are Anticipated by Schilit
`under 35 U.S.C. § 102(e)
`
`U.S. Patent No. 6,670,968 to Schilit et al. (“Schilit,” Ex. 1003) was not
`
`considered during the original prosecution of the ‘481 patent, nor is it cumulative
`
`of any prior art considered by the Examiner. Schilit was filed July 10, 2000 and
`
`issued December 30, 2003. The effective filing date of the ‘481 patent is May 3,
`
`2001. Therefore, Schilit is available as prior art against all claims of the ‘481
`
`patent under 35 U.S.C. § 102(e). The following claim chart demonstrates, on a
`
`
`
`16
`
`

`

`
`limitation-by-limitation basis, how claims 1, 2, 25, 28, and 50-57 of the ‘481 patent
`
`are anticipated by Schilit under 35 U.S.C. § 102(e). (See Ex. 1007 at ¶ 75).
`
`US 6,925,481 Claim
`Language
`1. A method of
`enabling data access and
`manipulation from a
`pervasive device,
`comprising steps of:
`
`receiving a data access
`request from a pervasive
`device;
`
`Correspondence to Schilit
`Schilit discloses a system and method for enabling data
`access and manipulation from a pervasive device by
`providing a Web browser that requests, accesses, and displays
`Web page content, along with selectable hyper-links from the
`requested Web page:
`A Web browser provides the ability to separate
`content and hyper-links from a Web page and
`provides a list of the links for viewing on a
`mobile device display screen enabling more
`effective Web page navigating using the limited
`mobile device display. … Further, once a link is
`selected using the mobile device, a services portal
`link is provided to the mobile device display to
`provide selection of services to be performed on
`the selected link, such as faxing or printing. (Ex.
`1003 at Abstract).
`(See also Ex. 1007 at ¶ 37).
`Schilit discloses a Web Browser, called “m-link,” which
`accesses a server to retrieve a document as identified by a
`user-selected URL.
`The present invention provides a Web Browser,
`referred to herein as “m-link”, which converts
`HTML documents for displaying on a mobile
`display. The m-link program accesses a server to
`retrieve a document as identified by a user-
`selected URL. (Ex. 1003 at 5:30-34).
`As shown in Fig. 7, reproduced below, the m-link browser
`receives a data access request from a pervasive device (shown
`as element 11). (Id. at Fig. 7).
`
`
`
`17
`
`

`

`
`
`
`
`
`
`data;
`
`
`
`
`(Seee also Ex. 1007 at ¶ 337).
`
`
`
`
`
`
`obtaining the requessted Thee m-link brrowser of SSchilit acceesses a webb server 122
`
`
`
`(shoown in Figg. 7, above)) to obtain
`
`
`the documment requesst by
`
`
`
`the user of thee pervasivee device.
`
`
`M-link bbrowser 100 accesses
`
`
`a server 122 to retrievve
`
`
`
`
`
`a documment as iddentified bby the usser selecteed
`
`URL. Thhe URL is
`
`
`
`used to iddentify a doocument oon
`
`
`
`server, suuch as servver 14. (EEx. 1003 aat
`
`another
`11:1-4).
`
`
`Reqquested data
`
`to
`
`
`
`is obbtained anand returnned
`thhe
`
`
`
`
`pervvasive deevice in aan un-commpressed
`
`format bby
`
`
`
`
`seleecting the ddisclosed rreading linkk.
`
`The reaading link
`
`
`
`allows thhe user too view thhe
`content
`
`
`
`
`of the linkk line by liine in a linnear fashioon
`
`
`using thee PCS phoone displayy. (Id. at 8::65-67).
`
`
`
`
`
`(Seee also Ex. 1007 at ¶ 337).
`
`
`
`Thee m-link brrowser alsoo determin
`
`
`es and creaates a list oof
`
`
`
`
`
`
`“s

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