throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`ZTE (USA) Inc.,
`Petitioner,
`
`
`
`v.
`
`
`
`Papst Licensing Gmbh & Co. KG,
`Patent Owner.
`
`
`
`Case No. To Be Assigned
`Patent No. 9,189,437 B2
`
`
`
`DECLARATION OF KEVIN C. ALMEROTH IN SUPPORT OF
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 9,189,437
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.100 et seq.
`
`SMRH:480610066.3
`
`
`
`
`-1-
`
`
`
`
`
`ZTE (USA) 1010, Page 1
`
`

`
`
`
`I, Kevin C. Almeroth, hereby declare and state as follows:
`
`1.
`
`I have been retained as a technical consultant on behalf of
`
`Petitioner ZTE (USA) Inc. I understand that the petition in the present
`
`proceeding also names ZTE (USA) Inc. and ZTE Corporation as the real
`
`parties-in-interest. I have no financial interest in, or affiliation with, the Petitioner,
`
`real parties-in-interest, or the patent owner, which I understand to be Papst
`
`Licensing GmbH & Co. KG. My compensation does not depend upon the
`
`outcome of, or my testimony in, the present inter partes review or any litigation
`
`proceedings.
`
`2.
`
`I understand that the application leading to U.S. Patent
`
`No. 9,189,437 (“the ʼ437 patent”) was Application No. 11/467,092, which was
`
`filed on August 24, 2006. The ʼ437 Patent is part of a long chain of continuing
`
`applications, which purport to claim priority back to PCT/EP98/01187 (filed on
`
`March 3, 1998) and German application DE 197 08 755 (filed on March 4, 1997).
`
`I understand, however, that the patentee failed to perfect its claim of priority
`
`though all of the intervening applications. In particular, while U.S. Application
`
`No. 11/078,778 was filed as a continuation of U.S. Application No. 10/219,105, it
`
`failed to claim priority to the earlier-filed U.S. Application No. 09/331,002. For
`
`purposes of my opinions in this declaration, I assume the time of the purported
`
`invention to be no earlier than August 15, 2002 (the filing date of the ’105
`
`SMRH:480610066.3
`
`
`
`
`-2-
`
`
`
`
`
`ZTE (USA) 1010, Page 2
`
`

`
`Application).
`
`
`
`I.
`
`BACKGROUND AND QUALIFICATIONS
`I hold three degrees from the Georgia Institute of Technology:
`3.
`
`(1) a Bachelor of Science degree in Information and Computer Science
`
`(with minors in Economics, Technical Communication, American Literature)
`
`earned in June, 1992; (2) a Master of Science degree in Computer Science
`
`(with specialization in Networking and Systems) earned in June, 1994; and (3) a
`
`Doctor of Philosophy (Ph.D.) degree in Computer Science (Dissertation Title:
`
`Networking and System Support for the Efficient, Scalable Delivery of Services
`
`in Interactive Multimedia System, minor in Telecommunications Public Policy)
`
`earned in June, 1997. During my education, I have taken a wide variety of
`
`courses as demonstrated by my minor. My undergraduate degree also included a
`
`number of courses are more typical of a degree in electrical engineering
`
`including digital logic, signal processing, and telecommunications theory.
`
`4.
`
`One of the major themes of my research has been the delivery
`
`of multimedia content and data between computing devices and users. In my
`
`research I have looked at large-scale content delivery systems and the use of
`
`servers located in a variety of geographic locations to provide scalable delivery to
`
`hundreds, even thousands, of users simultaneously. I have also looked at smaller-
`
`scale content delivery systems
`
`in which content,
`
`including
`
`interactive
`
`SMRH:480610066.3
`
`
`
`
`-3-
`
`
`
`
`
`ZTE (USA) 1010, Page 3
`
`

`
`communication like voice and video data, is exchanged between computers and
`
`portable computing devices. As a broad theme, my work has examined how to
`
`exchange content more efficiently across computer networks, including the devices
`
`that switch and route data traffic. More specific topics include the scalable
`
`delivery of content to many users, mobile computing, satellite networking,
`
`delivering content to mobile devices, and network support for data delivery in
`
`wireless network.
`
`5.
`
`Beginning in 1992, when I started graduate school, the first
`
`focus of my research was on the provision of interactive functions (VCR-style
`
`functions like pause, rewind, and fast-forward) for near video-on-demand systems
`
`in cable systems, in particular, how to aggregate requests for movies at a cable
`
`head-end and then how to satisfy a multitude of requests using one audio/video
`
`stream broadcast to multiple receivers simultaneously. Continued evolution of this
`
`research has resulted in the development of new techniques to scalably deliver on-
`
`demand content, including audio, video, web documents, and other types of data,
`
`through the Internet and over other types of networks, including over cable
`
`systems, broadband telephone lines, and satellite links.
`
`6.
`
`An important component of my research from the very
`
`beginning has been investigating the challenges of communicating multimedia
`
`content between computers and across networks. Although the early Internet was
`
`SMRH:480610066.3
`
`
`
`
`-4-
`
`
`
`
`
`ZTE (USA) 1010, Page 4
`
`

`
`designed mostly for text-based non-real time applications, the interest in sharing
`
`multimedia content quickly developed. Multimedia-based applications ranged
`
`from downloading content to a device to streaming multimedia content to be
`
`instantly used. One of the challenges was that multimedia content is typically
`
`larger than text-only content but there are also opportunities to use different
`
`delivery techniques since multimedia content is more resilient to errors. I have
`
`worked on a variety of research problems and used a number of systems that were
`
`developed to deliver multimedia content to users.
`
`7.
`
`In 1994, I began to research issues associated with the
`
`development and deployment of a one-to-many communication facility (called
`
`“multicast”) in the Internet (first deployed as the Multicast Backbone, a virtual
`
`overlay network supporting one-to-many communications). Some of my more
`
`recent research endeavors have looked at how to use the scalability offered by
`
`multicast to provide streaming media support for complex applications like
`
`distance learning, distributed collaboration, distributed games, and large-scale
`
`wireless communications. Multicast has also been used as the delivery mechanism
`
`in systems that perform local filtering (i.e., sending the same content to a large
`
`number of users and allowing them to filter locally content in which they are not
`
`interested).
`
`SMRH:480610066.3
`
`
`
`
`-5-
`
`
`
`
`
`ZTE (USA) 1010, Page 5
`
`

`
`8.
`
`Starting in 1997, I worked on a project to integrate the
`
`streaming media capabilities of the Internet together with the interactivity of the
`
`web. I developed a project called the Interactive Multimedia Jukebox (IMJ).
`
`Users would visit a web page and select content to view. The content would then
`
`be scheduled on one of a number of channels, including delivery to students in
`
`Georgia Tech dorms delivered via the campus cable plant. The content of each
`
`channel was delivered using multicast communication.
`
`9.
`
`In the IMJ, the number of channels varied depending on the
`
`capabilities of the server including the available bandwidth of its connection to the
`
`Internet. If one of the channels was idle, the requesting user would be able to
`
`watch their selection immediately. If all channels were streaming previously
`
`selected content, the user’s selection would be queued on the channel with the
`
`shortest wait time. In the meantime, the user would see what content was currently
`
`playing on other channels, and because of the use of multicast, would be able to
`
`join one of the existing channels and watch the content at the point it was currently
`
`being transmitted.
`
`10. The IMJ service combined the interactivity of the web with the
`
`streaming capabilities of the Internet to create a jukebox-like service. It supported
`
`true Video-on-Demand when capacity allowed, but scaled to any number of users
`
`based on queuing requested programs. As part of the project, we obtained
`
`SMRH:480610066.3
`
`
`
`
`-6-
`
`
`
`
`
`ZTE (USA) 1010, Page 6
`
`

`
`permission from Turner Broadcasting to transmit cartoons and other short-subject
`
`content. We also attempted to connect the IMJ into the Georgia Tech campus
`
`cable television network so that students in their dorms could use the web to
`
`request content and then view that content on one of the campus’s public access
`
`channels.
`
`11. More recently, I have also studied issues concerning how users
`
`choose content, especially when considering the price of that content. My research
`
`has examined how dynamic content pricing can be used to control system load. By
`
`raising prices when systems start to become overloaded (i.e., when all available
`
`resources are fully utilized) and reducing prices when system capacity is readily
`
`available, users’ capacity to pay as well as their willingness can be used as factors
`
`in stabilizing the response time of a system. This capability is particularly useful
`
`in systems where content is downloaded or streamed to users on-demand.
`
`12. As a parallel research theme, starting in 1997, I began
`
`researching issues related to wireless devices. In particular, I was interested in
`
`showing how to provide greater communication capability to “lightweight
`
`devices,” i.e., small form-factor, resource-constrained (e.g., CPU, memory,
`
`networking, and power) devices.
`
`13. Starting in 1998, I published several papers on my work to
`
`develop a flexible, lightweight, battery-aware network protocol stack. The
`
`SMRH:480610066.3
`
`
`
`
`-7-
`
`
`
`
`
`ZTE (USA) 1010, Page 7
`
`

`
`lightweight protocols we envisioned were similar in nature to protocols like
`
`Universal Plug and Play (UPnP) and Digital Living Network Alliance (DLNA).
`
`14. From this initial work, I have made wireless networking—
`
`including ad hoc and mesh networks and wireless devices—one of the major
`
`themes of my research. One topic includes developing applications for mobile
`
`devices, for example, virally exchanging and tracking “coupons” through
`
`“opportunistic contact” (i.e., communication with other devices coming into
`
`communication range with a user). Other topics include building network
`
`communication among a set of mobile devices unaided by any other kind of
`
`network infrastructure. Yet another theme is monitoring wireless networks, in
`
`particular different variants of IEEE 802.11 compliant networks, to (1) understand
`
`the operation of the various protocols used in real-world deployments, (2) use these
`
`measurements to characterize use of the networks and identify protocol limitations
`
`and weaknesses, and (3) propose and evaluate solutions to these problems.
`
`15. Protecting networks, including their operation and content, has
`
`been an underlying theme of my research almost since the beginning. Starting in
`
`2000, I have also been involved in several projects that specifically address
`
`security, network protection, and firewalls. After significant background work, a
`
`team on which I was a member successfully submitted a $4.3M grant proposal to
`
`the Army Research Office (ARO) at the Department of Defense to propose and
`
`SMRH:480610066.3
`
`
`
`
`-8-
`
`
`
`
`
`ZTE (USA) 1010, Page 8
`
`

`
`develop a high-speed intrusion detection system. Once the grant was awarded, we
`
`spent several years developing and meeting the milestones of the project. I have
`
`also used firewalls in developing techniques for the classroom to ensure that
`
`students are not distracted by online content.
`
`16. As an important component of my research program, I have
`
`been involved in the development of academic research into available technology
`
`in the market place. One aspect of this work is my involvement in the Internet
`
`Engineering Task Force (IETF) including many content delivery-related working
`
`groups like the Audio Video Transport (AVT) group, the MBone Deployment
`
`(MBONED) group, Source Specific Multicast (SSM) group, the Inter-Domain
`
`Multicast Routing (IDMR) group, the Reliable Multicast Transport (RMT) group,
`
`the Protocol Independent Multicast (PIM) group, etc. I have also served as a
`
`member of
`
`the Multicast Directorate (MADDOGS), which oversaw
`
`the
`
`standardization of all things related to multicast in the IETF. Finally, I was the
`
`Chair of the Internet2 Multicast Working Group for seven years.
`
`17.
`
`I am an author or co-author of nearly 200 technical papers,
`
`published software systems, IETF Internet Drafts and IETF Request for Comments
`
`(RFCs).
`
`18. My involvement in the research community extends to
`
`leadership positions for several journals and conferences. I am the co-chair of the
`
`SMRH:480610066.3
`
`
`
`
`-9-
`
`
`
`
`
`ZTE (USA) 1010, Page 9
`
`

`
`Steering Committee for the ACM Network and System Support for Digital Audio
`
`and Video (NOSSDAV) workshop and on the Steering Committees for the
`
`International Conference on Network Protocols (ICNP), ACM Sigcomm
`
`Workshop on Challenged Networks (CHANTS), and IEEE Global Internet (GI)
`
`Symposium. I have served or am serving on the editorial boards of IEEE/ACM
`
`Transactions on Networking, IEEE Transactions on Mobile Computing, IEEE
`
`Transactions on Networks and System Management, IEEE Network, ACM
`
`Computers in Entertainment, AACE Journal of Interactive Learning Research
`
`(JILR), and ACM Computer Communications Review.
`
`19.
`
`I have co-chaired a number of conferences and workshops
`
`including the IEEE International Conference on Network Protocols (ICNP), ACM
`
`International Conference on Next Generation Communication (CoNext), IEEE
`
`Conference on Sensor, Mesh and Ad Hoc Communications and Networks
`
`(SECON), International Conference on Communication Systems and Networks
`
`(COMSNETS),
`
`IFIP/IEEE
`
`International Conference on Management of
`
`Multimedia Networks and Services (MMNS), the International Workshop On
`
`Wireless Network Measurement (WiNMee), ACM Sigcomm Workshop on
`
`Challenged Networks (CHANTS), the Network Group Communication (NGC)
`
`workshop, and the Global Internet Symposium; and I have been on the program
`
`committee of numerous conferences.
`
`SMRH:480610066.3
`
`
`
`
`-10-
`
`
`
`
`
`ZTE (USA) 1010, Page 10
`
`

`
`20. Furthermore, in the courses I teach, the class spends significant
`
`time covering all aspects of the Internet including each of the layers of the Open
`
`System Interconnect (OSI) protocol stack commonly used in the Internet. These
`
`layers include the physical and data link layers and their handling of signal
`
`modulation, error control, and data transmission. I also teach DOCSIS, DSL, and
`
`other standardized protocols for communicating across a variety of physical media
`
`including cable systems, telephone lines, wireless, and high-speed Local Area
`
`Networks (LANs). I teach the configuration and operation of switches, routers,
`
`and gateways including routing and forwarding and the numerous respective
`
`protocols as they are standardized and used throughout the Internet. Topics
`
`include a wide variety of standardized Internet protocols at the Network Layer
`
`(Layer 3), Transport Layer (Layer 4), and above.
`
`21.
`
`In addition, I co-founded a technology company called Santa
`
`Barbara Labs that was working under a sub-contract from the U.S. Air Force to
`
`develop very accurate emulation systems for the military’s next generation
`
`internetwork. Santa Barbara Labs’ focus was in developing an emulation platform
`
`to test the performance characteristics of the network architecture in the variety of
`
`environments in which it was expected to operate, and in particular, for network
`
`services including IPv6, multicast, Quality of Service (QoS), satellite-based
`
`communication, and security. Applications for this emulation program included
`
`SMRH:480610066.3
`
`
`
`
`-11-
`
`
`
`
`
`ZTE (USA) 1010, Page 11
`
`

`
`communication of a variety of multimedia-based services. Within this testing
`
`infrastructure, we used a wide range of switches and routers.
`
`22.
`
`In addition to having co-founded a technology company myself,
`
`I have worked for, consulted with, and collaborated with companies such as IBM,
`
`Hitachi Telecom, Digital Fountain, RealNetworks, Intel Research, Cisco Systems,
`
`and Lockheed Martin.
`
`23.
`
`I am a Member of the Association of Computing Machinery
`
`(ACM) and a Fellow of the Institute of Electrical and Electronics Engineers
`
`(IEEE).
`
`24. Further details about my background, qualifications, and
`
`experience are included in my curriculum vitae (“CV”) submitted herewith as Ex.
`
`1011, which I provided from my own files.
`
`II. OVERVIEW OF THE ʼ437 PATENT
`
`25. The ’437 Patent describes an “interface device” intended to
`
`eliminate the need for specialized device drivers. When the interface device of the
`
`alleged invention is connected to a host, it responds to the host’s request for
`
`identification by “simulat[ing], both in terms of hardware and software, the way in
`
`which a conventional input/output device functions, preferably that of a hard disk
`
`drive,” for which the host system already has a working driver. Ex. 1001, at 4:17-
`
`20 (emphasis added). When the host communicates with the interface device to
`
`SMRH:480610066.3
`
`
`
`
`-12-
`
`
`
`
`
`
`
`ZTE (USA) 1010, Page 12
`
`

`
`request data from or control the operation of the data device, the host uses its own
`
`customary device driver, and the interface device translates the communications
`
`into a form understandable by the connected data device. Id. at 3:29-4:41. The
`
`interface device of the ʼ437 Patent thus does not require a “specially designed
`
`driver” to permit a connected peripheral device to communicate with a host
`
`computer. Id. at 4:25-26. “Communication between the host device and the
`
`devices attached to the multi-purpose interface … essentially takes place by means
`
`of the specific driver software for the multipurpose interface ….” Id. at 3:59-62.
`
`III. LEVEL OF ORDINARY SKILL
`
`26.
`
`I understand that patent claims must be interpreted by a person
`
`of ordinary skill in the art (“POSITA”) at the time of invention. For the purpose of
`
`this proceeding, I have been informed to evaluate the level of ordinary skill in the
`
`art as of August 15, 2002 (the filing date of the ’105 Application). Based on the
`
`disclosure of the ʼ437 patent, a POSITA at the relevant time would have had at least
`
`a four-year undergraduate degree in electrical engineering, computer science,
`
`computer engineering, or related field of study, or equivalent experience, and at
`
`least two years of experience in studying or developing computer interfaces or
`
`peripherals and storage-related software. In my opinion, a POSITA would also be
`
`familiar with operating systems (e.g., MS-DOS, Windows, Unix), their associated
`
`file systems (e.g., FAT, UFS, FFS), device drivers for computer components and
`
`SMRH:480610066.3
`
`
`
`
`-13-
`
`
`
`
`
`
`
`ZTE (USA) 1010, Page 13
`
`

`
`peripherals (e.g., mass storage device drivers), and communication interfaces (e.g.,
`
`SCSI, USB, PCMCIA). This description is approximate, and a higher level of
`
`education or skill might make up for less experience, and vice-versa.
`
`27. Based on my experience, I have an understanding of the
`
`capabilities of a POSITA. Furthermore, I possessed those capabilities myself at
`
`least as of August 15, 2002.
`
`IV. ANALYSIS
`“input/output (i/o) port” (claim 1)
`A.
`
`28.
`
`In my opinion, as of August 15, 2002, a POSITA would have
`
`understood the following structures disclosed in PCT No. WO 98/39710 (“the PCT
`
`Publication”), attached as Exhibit 1004 (Certified English translation) to be
`
`examples of an input/output (i/o) port: (1) a 50-pin SCSI connector with a SCSI
`
`interface, (2) a 25-pin sub-D connector with an Enhance Parallel Port (EPP), and
`
`(3) a 25-pin connector with a digital input/output.
`
`B.
`
`“a sensor … designed to generate the analog data” (claim 16)
`
`29.
`
`In my opinion, as of August 15, 2002, a POSITA would have
`
`understood an electronic measuring device such as a multimeter, as disclosed in
`
`PCT No. WO 98/39710 (“the PCT Publication”) attached as Exhibit 1004
`
`(Certified English translation), to be an example of a sensor designed to generate
`
`and transmit data.
`
`SMRH:480610066.3
`
`
`
`
`-14-
`
`
`
`
`
`ZTE (USA) 1010, Page 14
`
`

`
`C.
`
`“at least one file of … data” (claim 1)
`
`30.
`
`In my opinion, as of August 15, 2002, a POSITA would have
`
`understood that a buffer, such as data buffer disclosed in PCT No. WO 98/39710
`
`(“the PCT Publication”), attached as Exhibit 1004 (Certified English translation),
`
`to store data in one or more files.
`
`“a cable” (claim 15)
`
`D.
`In my opinion, as of August 15, 2002, a POSITA would have understood that host
`
`line 11 disclosed in PCT No. WO 98/39710 (“the PCT Publication”), attached as
`
`Exhibits 1004 (Certified English translation) at Fig. 1 and on pages 8 and 9, could
`
`be a cable. The following connectors, disclosed in PCT No. WO 98/39710 (“the
`
`PCT Publication”), attached as Exhibit 1004 (Certified English translation), are
`
`designed to be used to with a cable to physically connect a device to acomputing
`
`device: (1) a 50-pin SCSI connector, (2) a 25-pin sub-D connector,
`
`
`
`
`
`SMRH:480610066.3
`
`
`
`
`-15-
`
`
`
`
`
`ZTE (USA) 1010, Page 15
`
`

`
`and (3) a 25-pin connector.
`
`I hereby declare that all statements made herein of my own knowledge are
`
`true and that all statements made on information and belief are believed to be
`
`true; and further that these statements were made with the knowledge that
`
`willful false statements and the like so made are punishable by fine or
`
`imprisonment, or both, under Section 1001 of Title 18 of the United States
`
`Code.
`
`Executed on this 17th day of January, 2017, in Santa Barbara, California.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SMRH:480610066.3
`
`
`
`
`-16-
`
`
`
`
`
`ZTE (USA) 1010, Page 16

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