throbber

`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`________________
`
`INTEL CORP., CAVIUM, INC., and
`WISTRON CORPORATION,
`
`Petitioners,
`
`v.
`
`ALACRITECH INC.,
`
`Patent Owner
`________________
`
`Case IPR2017-014061
`U.S. Patent 7,673,072
`________________
`
`
`
`DECLARATION OF KEVIN ALMEROTH, PH.D. IN SUPPORT OF
`
`PATENT OWNER’S REPLY IN SUPPORT OF CONTINGENT MOTION
`
`TO AMEND UNDER TO 37 C.F.R. § 42.121
`
`
`
`
`1 Wistron Corporation, which filed a Petition in Case IPR2018-00329, has been joined as a
`
`petitioner in this proceeding.
`
`
`
`
`
`Alacritech Exhibit 2305
`
`

`

`
`
`I.
`
`INTRODUCTION
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`1.
`
`I have been retained on behalf of Alacritech, Inc. (“Alacritech,”
`
`“Patent Owner,” OR “PO”) for the above-captioned inter partes review (IPR)
`
`proceeding. I understand that this proceeding was filed by Intel Corporation
`
`(“Intel”) (and joined by Cavium, Inc. (“Cavium”)) and involves U.S. Patent No.
`
`7,673,072 (“the ‘072 patent”). The ‘072 patent is currently assigned to
`
`Alacritech. I have been retained to provide my opinions in support of PO’s
`
`Reply In Support of Its Contingent Motion to Amend Under 37 C.F.R. § 42.121.
`
`I am being compensated for my time at the rate of $600 per hour. I have no
`
`interest in the outcome of this proceeding.
`
`2.
`
`In preparing this declaration, I have reviewed and am familiar with
`
`the following prior art references:
`
`• U.S. Patent No. 5,768,618 (“Erickson”) (Ex.
`1005);
`
`• Andrew S. Tanenbaum, Computer Networks, 3rd
`ed (1996) (“Tanenbaum96”) (Ex. 1006).
`
`3.
`
`I have also considered all other materials cited and discussed herein,
`
`including all other materials cited and discussed in Intel’s Petition for Inter
`
`Partes Review of U.S. Patent No. 7,673,072 (Case IPR2017-01406) and its
`
`Opposition to PO’s Motion to Amend, along with PO’s Preliminary Response
`
`Pursuant to 35 U.S.C. § 313 and 37 C.F.R. § 42.107, and Corrected Patent
`
`Owner’s Response Pursuant to 35 U.S.C. § 313 and 37 C.F.R. § 42.107. I
`
`
`
`
`
`Alacritech, Page 1
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`incorporate by reference herein my opinions and explanation regarding the
`
`overview of the above prior art and reasons why they do not invalidate the
`
`challenged claims of the ‘072 patent as were presented in my prior declaration,
`
`Ex. 2026.
`
`4.
`
`The ‘072 patent describes a novel system for accelerating network
`
`processing. In particular, the ’072 patent discloses a system with “a specialized
`
`microprocessor designed for processing network communications, avoiding the
`
`delays and pitfalls of conventional software layer processing, such as repeated
`
`copying and interrupts to the CPU,” and “freeing the host CPU from most
`
`protocol processing and allowing improvements in other task.” Ex. 1001 at 5:44-
`
`47, 7:47-49.
`
`5.
`
`The ‘072 patent explains that, at the time of the invention,
`
`communications networks were growing “increasingly popular and
`
`the
`
`information communicated thereby [becoming] increasingly complex and
`
`copious” creating increased network protocol processing such that “a large
`
`fraction of the processing power of a host CPU may be devoted to controlling
`
`protocol processes, diminishing the ability of that CPU to perform other tasks.”
`
`Ex. 1001, 5:5-11.
`
`6.
`
`The ‘072 patent explains that the then-existing standard protocol
`
`processing involved too many data moves (id. at 35:1-27), too much processing
`
`
`
`
`
`Alacritech, Page 2
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`by the CPU (id. at 35:29-36:3), too many interrupts (id. at 36:4-34), and
`
`inefficient use of the peripheral component interconnect (“PCI”) bus (id. at
`
`36:36-61).
`
`7.
`
`The ’072 patent solves these problems with a specialized network
`
`interface device (i.e., the INIC) that is capable of performing certain processing
`
`normally handled by the host CPU. Ex. 1001 at 7:41-55.
`
`8.
`
`Despite industry skepticism, the ‘072 inventors came up with the
`
`claimed arrangement, which allows for enhanced network and system
`
`performance, a stark reduction or elimination of unnecessary processing by the
`
`host CPU, faster data throughput, increased system stability, and an overall better
`
`user experience. Instead of using an unspecified processor on a network card to
`
`carry out some protocol software, the ‘072 patent discloses “a specialized
`
`microprocessor designed for processing network communications.” Ex. 1001,
`
`5:44-47. This specialized microprocessor, residing in an intelligent network
`
`interface card (INIC), is described, for example, in Fig. 13 and corresponding
`
`embodiments described in the patent.
`
`9.
`
`The statements made herein are based on my own knowledge and
`
`opinion. This Declaration represents only the opinions I have formed to date. I
`
`may consider additional documents as they become available or other documents
`
`
`
`
`
`Alacritech, Page 3
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`that are necessary to form my opinions. I reserve the right to revise, supplement,
`
`or amend my opinions based on new information and on my continuing analysis.
`
`II. QUALIFICATIONS
`
`10. My qualifications can be found in my Curriculum Vitae, which
`
`includes a complete list of my publications. Ex. 2027.
`
`11.
`
`I am currently a Professor in the Department of Computer Science at
`
`the University of California, Santa Barbara. I also hold an appointment and am a
`
`founding member of the Computer Engineering (CE) Program at UCSB. I am
`
`also a founding member of the Media Arts and Technology (MAT) Program, and
`
`the Technology Management Program (TMP) at UCSB. I also served as the
`
`Associate Director of the Center for Information Technology and Society (CITS)
`
`at UCSB from 1999 to 2012. I have been a faculty member at UCSB since July
`
`1997.
`
`12.
`
`I hold three degrees from the Georgia Institute of Technology: (1) a
`
`Bachelor of Science degree in Information and Computer Science (with minors in
`
`Economics, Technical Communication, and 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.
`
`
`
`
`
`Alacritech, Page 4
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`13. 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, or even thousands, of users simultaneously. I have also looked at
`
`smaller-scale content delivery systems in which content, including interactive
`
`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 of my work
`
`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 and sensor networks.
`
`14. Beginning in 1992, at the time I started graduate school, the initial
`
`focus of my research was the provision of interactive functions (e.g., 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 to broadcast to multiple receivers simultaneously. Continued
`
`evolution of this research has resulted in the development of new techniques to
`
`
`
`
`
`Alacritech, Page 5
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`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.
`
`15. 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
`
`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 for 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 because 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.
`
`16.
`
`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 communication). 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,
`
`
`
`
`
`Alacritech, Page 6
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`distributed
`
`collaboration, distributed games,
`
`and
`
`large-scale wireless
`
`communication. 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).
`
`17. 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.
`
`18.
`
`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
`
`
`
`
`
`Alacritech, Page 7
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`be able to join one of the existing channels and watch the content at the point it
`
`was currently being transmitted.
`
`19. 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 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.
`
`20. 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 on-demand to users.
`
`
`
`
`
`Alacritech, Page 8
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`21. As a parallel research theme, starting in 1997, I began researching
`
`issues related to wireless devices and sensors. 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. Starting by at least 2004, I researched
`
`techniques to wirelessly disseminate information, for example, advertisements
`
`between users using ad hoc networks. In the system, called Coupons, an
`
`incentive scheme is used to encourage users to relay information, including
`
`advertisements, to other nearby users.
`
`22. Starting in 1998, I published several papers on my work to develop a
`
`flexible, lightweight, battery-aware network protocol stack. The lightweight
`
`protocols we envisioned were similar in nature to protocols like Universal Plug
`
`and Play (UPnP) and Digital Living Network Alliance (DLNA).
`
`23. From this initial work, I have made wireless networking—including
`
`ad hoc, 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
`
`
`
`
`
`Alacritech, Page 9
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`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.
`
`24. 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
`
`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.
`
`25. 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
`
`
`
`
`
`Alacritech, Page 10
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`(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.
`
`26.
`
`I am an author or co-author of approximately 200 technical papers,
`
`published software systems, IETF Internet Drafts and IETF Request for
`
`Comments (RFCs). A list of these papers is included in my CV, which is Exhibit
`
`2027.
`
`27. My involvement in the research community extends to leadership
`
`positions for several journals and conferences. I am the co-chair of the 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
`
`
`
`
`
`Alacritech, Page 11
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`Computers in Entertainment, AACE Journal of Interactive Learning Research
`
`(JILR), and ACM Computer Communications Review.
`
`28. 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.
`
`29.
`
`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
`
`
`
`
`
`Alacritech, Page 12
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`network services including IPv6, multicast, Quality of Service (QoS), satellite-
`
`based communication, and security. Applications for this emulation program
`
`included communication of a variety of multimedia-based services.
`
`30.
`
`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.
`
`31.
`
`I am a Member of the Association of Computing Machinery (ACM)
`
`and a Fellow of the Institute of Electrical and Electronics Engineers (IEEE).
`
`32. Additional details about my employment history, fields of expertise,
`
`and publications are further included in my curriculum vitae, attached as Exhibit
`
`2027.
`
`33. From my education, teaching, and consulting experience, I am
`
`familiar with networking protocols in general and in particular the TCP/IP
`
`protocol. I am also familiar with TCP offload engines (sometime referred to as
`
`TOE) that offload the processing of the entire TCP/IP stack to the network
`
`controller. I am also familiar with the technologies sometimes referred to as
`
`Large Segmentation Offload (LSO) and Receive Side Coalescing (RSC).
`
`
`
`
`
`Alacritech, Page 13
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`III. LEGAL AND OTHER UNDERSTANDINGS
`
`34.
`
`I incorporate herein by reference my legal understandings referenced
`
`in the previous declaration I submitted in this proceeding in support of PO. See
`
`Ex. 2026.
`
`35.
`
`I understand that PO, by way of its Contingent Motion to Amend
`
`seeks to substitute proposed claims 22-42 for original 1-21, should the Board find
`
`any challenged claims unpatentable.
`
` See Contingent Motion
`
`(listing
`
`amendments).
`
`36.
`
`I understand that Petitioners have challenged the patentability of the
`
`amendments proposed by PO. I also understand that Intel relies on the expert
`
`declarations of Dr. Robert Horst (Exs. 1003, 1210) in support of its challenge to
`
`the patentability of PO’s amendments.
`
`37. Accordingly, I have been asked to provide certain opinions
`
`regarding the patentability of the proposed amendments to the ‘072 patent that
`
`Intel has challenged. Specifically, I have been asked to provide my opinions
`
`regarding whether the proposed amendments (i) are not indefinite, (ii) are not
`
`obvious over Erickson in combination with Tanenbaum96; (iii) find sufficient
`
`written description support in prior applications; and (iv) expand the scope of the
`
`claims of the ‘072 patent.
`
`
`
`
`
`Alacritech, Page 14
`
`

`

`
`
`38.
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`I incorporate herein by reference my prior opinions and explanations
`
`of the background of the technology disclosed in the ‘072 patent, as well as the
`
`overview of the ‘072 patent, its claims and prosecution history. See Ex. 2026.
`
`39. As explained in more detail below, it is my opinion that the
`
`proposed amendments challenged by Intel do not expand claim scope, are fully
`
`supported by the specification and original claims of the ‘072 patent as well as
`
`the prior applications, are not indefinite, and are valid as they are not obvious in
`
`view of Erickson in combination with Tanenbaum96.
`
`40. My opinions in this declaration are not exhaustive of my opinions on
`
`the patentability of the challenged claims of the ‘072 patent. Therefore, the fact
`
`that I may not address a particular point should not be understood to indicate any
`
`opinion on my part that the any claim or limitation fails to comply with any
`
`patentability requirement.
`
`IV. OVERVIEW OF THE PRIOR ART
`
`A. U.S. Patent No. 5,768,618 (“Erickson”)
`
`41. Erickson (a reference already considered by the PTO) discloses an
`
`input/output (I/O) device connected to a computer to facilitate fast I/O data
`
`transfers. Ex. 1005 at Abstract. An address space for the I/O device is created in
`
`the virtual memory of the computer, wherein the address space comprises virtual
`
`registers that are used to directly control the I/O device. Control registers and/or
`
`memory of the I/O device are mapped into the virtual address space, and the
`
`
`
`
`
`Alacritech, Page 15
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`virtual address space is backed by control registers and/or memory on the I/O
`
`device. When the I/O device detects writes to the address space, a pre-defined
`
`sequence of actions can be triggered in the I/O device by programming specified
`
`values into the data written into the mapped virtual address space. Id.
`
`42. Figure 7 of Erickson shows a UDP datagram header “template” that
`
`resides in the I/O adapter’s memory. (Id. at 7:39-46.) A user provides the starting
`
`address and length for the user data in its virtual address space, and then “spanks”
`
`a GO register to trigger execution of a predetermined script. Id. The script causes
`
`a UDP datagram to be created by accessing the user data, computing a counter
`
`value for the datagram, computing a UDP checksum over both the UDP header
`
`and user data, and computing an IP checksum. Id. at 8:10-26. The completed
`
`UDP datagram is then transmitted over the network. Id. at 7:45-47. Erickson
`
`does not address or suggest segmenting or dividing a block of user data from
`
`source memory into a number of transmittable segments because the network
`
`adapter only possesses “a very limited knowledge of the user process’ virtual
`
`address space, probably only knowing how to map virtual-to-physical for a very
`
`limited range, maybe as small as a single page.” Id. at 8:16-20. Consequently,
`
`Erickson is also silent as to the network adapter then prepending packet headers
`
`to each of these divided segments.
`
`
`
`
`
`Alacritech, Page 16
`
`

`

`
`
`43.
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`In addition, while TCP/IP is mentioned in passing (“[t]ypes of
`
`protocols include, but are not limited to, TCP/IP, UDP/IP, BYNET lightweight
`
`datagrams, deliberate shared memory, active message handler, SCSI, and File
`
`Channel”), all the described examples and embodiments in Erickson use UDP,
`
`not TCP. Id. at 5:47-51. There is no discussion or explanation within Erickson of
`
`how to implement any of the processes described in Erickson with TCP.
`
`B.
`
`Computer
`Tanenbaum,
`(“Tanenbaum96”
`
`Networks,
`
`3rd
`
`ed.
`
`(1996)
`
`44. Tanenbaum96 was also considered by the PTO during prosecution.
`
`Tanenbaum96 is the third edition of a textbook relating to “Computer Networks.”
`
`45. Petitioner cites only a few pages from Tanenbaum96—i.e., the
`
`portion of Tanenbaum that discusses “fast path” host CPU processing of the TCP
`
`protocol. Ex. 1006 at 584. Specifically, Tanenbaum96 describes “fast” TPDU
`
`(Transport Protocol Data Unit) processing. Ex. 1006 at 583-86. On the sending
`
`side, Tanenbaum96 notes that “[i]n the normal case, the headers of consecutive
`
`data TPDUs are almost the same.” Id. at 583. In view of this observation, a
`
`“prototype header” is defined. Id. In order to construct a packet for transmission,
`
`at the TCP layer, the TCP prototype header is copied into the output buffer, the
`
`sequence number is filled in, the TCP checksum is computed, and the sequence
`
`number is incremented in memory. Id. at 584. Then, the TCP header and data is
`
`handed “to a special IP procedure” at the IP layer, where the IP prototype header
`
`
`
`
`
`Alacritech, Page 17
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`is copied into the output buffer, the “Identification” field is inserted, and the IP
`
`checksum is computed. Id. The packet is then ready for transmission. This fast
`
`path processing is introduced to improve the network performance. Id. at 583.
`
`However, this proposal is fundamentally different from the ‘072 patent in that it
`
`is a software proposal, without altering the location where any of the processing
`
`occurs (e.g., on the host or on the interface device) and particularly without
`
`disclosing an interface device capable of dividing the data into segments.
`
`Nowhere in the cited passage does Tanenbaum discuss dividing the TPDU data
`
`into segments, let alone doing so on a separate piece of network hardware.
`
`46.
`
`Indeed, Tanenbaum96 teaches away from performing any TCP/IP
`
`protocol processing on anything other than the host CPU. Tanenbaum96 is aware
`
`of the possibility of a transport entity being on a network interface card Id. at
`
`498; however, it teaches away from doing so. Id. at 588-89.
`
`47. Accordingly, Tanenbaum96 identifies myriad difficulties with
`
`implementing TCP header bypass in a chip separate from the host CPU and
`
`advises against attempting such an implementation. These difficulties are
`
`precisely the issues that were solved by the invention of the ‘072 patent. At the
`
`very least, Tanenbaum96 teaches that integration of transport entity functions in
`
`the NIC is complicated and non-trivial, but does not provide any insight or
`
`suggestion of how the complications may be overcome. Instead, Tanenbaum96
`
`
`
`
`
`Alacritech, Page 18
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`suggests a “Fast TPDU Processing” method that is implemented and performed
`
`on the host—precisely the opposite of the ‘072 invention.
`
`V. THE PROPOSED AMENDMENTS ARE NOT INDEFINITE
`
`48.
`
`I understand that Intel asserts that the proposed amended claims are
`
`indefinite, I disagree. In my opinion, a POSA would have no difficulty
`
`understanding the meaning and scope of the amended claim language.
`
`49.
`
`In particular, I understand that Intel claims that substitute claims 22-
`
`29 are indefinite because it is unclear what the limitation of “the context
`
`information” refers to, as “it is not previously mentioned” in substitute claim 22.
`
`In my opinion, Petitioner’s argument is mistaken.
`
`50. The relevant portions of substitute claim 22 provide as follows:
`
`establishing, at a host computer, a transport layer connection,
` including creating a context
`that
`includes a media access
`control (MAC) layer address, an Internet Protocol (IP) address and
`Transmission Control Protocol (TCP) state information protocol
`header information for the connection;
`
`
`transferring the context protocol header information to an interface device;
`
`transferring data from the network host to the interface device, after
`transferring the context protocol header information to the interface device;
`
`
`51. As noted, the first amendment to original claim 1 narrows the claim
`
`by disclosing the “context” must include three elements: “a media access control
`
`(MAC) layer address, an Internet Protocol (IP) address and Transmission Control
`
`Protocol (TCP) state information.”
`
`
`
`
`
`Alacritech, Page 19
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`52. The next amendment provides
`
`the “context
`
`information”
`
`is
`
`transferred to an interface device. Rather than being indefinite, to a POSA, the
`
`plain meaning of the claim language establishes that “context information” refers
`
`to the three itemized elements of the claimed “context.”
`
`53.
`
`I understand that Intel also argues that substitute claims 26-42 are
`
`indefinite. I disagree.
`
`54. Substitute clam 36 provides for a method comprising “establishing,
`
`at a computer, a Transmission Control Protocol (TCP) connection corresponding
`
`to a context that includes status information and Internet Protocol (IP) addresses
`
`and TCP ports a media access control (MAC) layer address for the connection.”
`
`55.
`
`I understand Petitioner contends substitute claim 36 is “nonsensical”
`
`and indefinite because “[i]t is unclear whether PO meant to say ‘or a media
`
`access control...’ or ‘and a media access control...’ or something else entirely.”
`
`Opp., 10. As claims 37-42 depend upon claim 36, Petitioner alleges they are
`
`likewise invalid. Id. In my opinion, Petitioner is wrong.
`
`56. To a POSA, substitute claim 30’s claim language demonstrates
`
`substitute claim 36’s addition (“a media access control (MAC) layer address”) is
`
`a necessary requirement as substitute claim 30 requires the same elements for
`
`“context”: “a media access control (MAC) layer address,” “Internet Protocol (IP)
`
`addresses” and “TCP” status information.
`
`
`
`
`
`Alacritech, Page 20
`
`

`

`
`
`
`
` Case No. IPR2017-01406
`U.S. Patent No. 7,237,072
`
`VI. THE PROPOSED AMENDED CLAIMS ARE NOT OBVIOUS IN
`VIEW OF ERICKSON IN COMBINATION WITH TANENBAUM96
`
`57.
`
`I understand Petitioner contends that the amended claims are
`
`obvious in view of Erickson in combination with Tanenbaum96. I disagree.
`
`58. As I opined in my prior declaration (which I expressly incorporate
`
`herein by reference), a POSA would never have combined Erickson and
`
`Tanenbaum in the manner suggested by Petitioner.
`
`59. To begin with, Tanenbaum96 expressly teaches away from the
`
`combination. And, other factors, including significant differences between the
`
`protocols (Tanenbaum96 uses TCP/IP while Erickson uses UDP) further weigh
`
`against this combination.
`
`60. Secondary considerations weigh against Petition

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