throbber
Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 1 of 18
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`Case No. 6:20-cv-00272-ADA
`
`DECLARATION OF
`DANIJELA CABRIC, PH.D.
`
`VOIP-PAL.COM, INC.,
`Plaintiff,
`
` v.
`AMAZON.COM, INC.;
`AMAZON.COM SERVICES LLC; and
`AMAZON WEB SERVICES, INC.
`
` Defendants.
`
`I, Dr. Danijela Cabric, declare as follows:
`
`I.
`
`INTRODUCTION
`
`1.
`
`I have personal knowledge of the facts contained in this declaration and, if
`
`called as a witness, I could and would competently testify to those facts. I have been retained
`
`by Voip-PAL.Com Inc. (“Voip-PAL”) as an expert in the fields of computer science, computer
`
`communications, and related technologies. I am being compensated at my normal consulting
`
`rate. My compensation does not depend on and in no way affects the substance of my
`
`statements in this Declaration.
`
`II. QUALIFICATIONS
`
`2.
`
`My technical qualifications are as follows. I hold a Ph.D. in Electrical
`
`Engineering in 2007 from the University of California, Berkley in Berkeley, CA, for research
`
`on the topic of “Cognitive Radios: System Design Perspective,” under the supervision of Dr.
`
`Robert W. Brodersen. Previous to that, I received a M.S. in Electrical Engineering in 2001
`
`from the University of California, Los Angeles (“UCLA”), based on a thesis entitled,
`
`“Characterization of a Fast Frequency-Hopped FSK Testbed through Simulations and Field
`
`Trials.”
`
`1
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 2 of 18
`
`3.
`
`I am a Full Professor of Electrical Engineering at University of California, Los
`
`Angeles. I have been a full, tenured professor in the Department of Electrical Engineering at
`
`UCLA since 2018. My research interests include digital communications and wireless system
`
`design. I am aware of the knowledge that a person of ordinary skill in the art would have had
`
`at the time the invention was made.
`
`4.
`
`I have taught undergraduate and graduate courses at UCLA and at UC Berkeley.
`
`For example, I have taught the following undergraduate courses at UCLA: Signals and System,
`
`Digital Signal Processing, Logic Design for Digital Systems, Circuit Analysis I, Digital
`
`Electronic Circuits. I have also taught graduate courses at UCLA including Estimation and
`
`Detection, Digital Communications, Wireless Communication System Design, Modeling and
`
`Implementation. Further, I developed a new graduate-level course titled: Special Topics in
`
`Circuits and Embedded Systems: Wireless Communications System Design. At UC Berkeley,
`
`I taught the undergraduate course Probability and Random Processes and was a graduate-level
`
`course consultant for the course VLSI Signal Processing.
`
`5.
`
`I am a Fellow of the Institute of Electrical and Electronics Engineers (IEEE) and
`
`have also been recognized by the IEEE as a ComSoc Distinguished Lecturer from 2018-2020.
`
`In 2020, I received the Best paper Award at the 4th ACM Workshop on Millimeter-Wave
`
`Networks and Sensing Systems, and the year before, in 2019, I received the Best paper Award
`
`at the IEEE International Conference on Communications, Networking, and Computing. I am
`
`the author or co-author of five books or chapters, 70 journal publications, eight magazine
`
`articles, 126 conference papers, 17 invited papers, 1 patent and 2 patent applications. I have
`
`also been invited to speak at about 62 talks, panels, keynotes, or tutorials. I am the author or
`
`co-author of over 250 technical publications in the areas of communications, communications
`
`signal processing, networking, embedded systems and integrated circuits.
`
`2
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 3 of 18
`
`6.
`
`I have also been hired by several technology companies as a consultant,
`
`including Amazon, Inc., Perceptronics Solutions, LocatorX, Intellectual Ventures, and
`
`Specom, Inc. I have also served on the Board of Advisors for MaxLinear, Inc.
`
`7.
`
`I have provided a copy of my curriculum vitae as an attachment to this
`
`declaration as Exhibit A. My Curriculum Vitae provides a more detailed description of my
`
`qualifications, experience, publications, awards and patents, as well as a list of cases in which I
`
`have testified at trial, hearing, or by deposition within the last four years.
`
`III.TASK
`
`8.
`
`I have been asked to provide testimony regarding the understanding of a person
`
`of ordinary skill in the art (“POSITA”) at the time of invention regarding the technology
`
`disclosed and claimed in VoIP-Pal’s patents in general, and the 10,218,606 patent (“the ’606
`
`Patent”) in particular. Among other things, I have provided comments distinguishing between
`
`Claim 1 of the ’606 patent and Claim 1 of U.S. Patent No. 9,826,002 B2 (“the ’002 Patent”); I
`
`have distinguished also between Claim 1 of the ’606 Patent and the conventional practices of
`
`historical switchboard operators; and I have explained how a POSITA would know how to
`
`perform the invention.
`
` I have identified unconventional technical advantages and
`
`improvements which arise from the claims of the ’606 Patent.
`
`9.
`
`This declaration is not the first time I have provided testimony for VoIP-Pal. I
`
`provided an expert report in USPTO ex parte Re-examination Control. No. 90/019,124 in
`
`regarding U.S. Patent No. 10,218,606. While I am not a lawyer, in making the statements
`
`contained in this declaration, I have relied on my education in Electrical Engineering, my
`
`professional experience, the ’606 patent and its history. In forming my opinions for this
`
`Declaration, I have adopted the perspective of a POSITA as of the priority date of these
`
`patents, which I am defining as follows: a POSITA would be someone with an undergraduate
`
`degree in either Computer Science, Computer Engineering, Electrical Engineering, or a related
`3
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 4 of 18
`
`discipline, and would likely have about 2 years of experience in system-level development, but
`
`a greater degree of professional experience could serve to replace some formal education and a
`
`higher degree of education could replace some professional experience. Based on my
`
`education and experience, I believe I would qualify as at least a skilled person in the field of
`
`the invention (“POSITA”) both now and as of the patent’s priority date.
`
`IV.DISCUSSION OF VOIP-PAL PATENTS
`
`A.
`
`10.
`
`Claim 1 of the ’606 Patent is distinct from Claim 1 of the ’002 Patent.
`
`I have been asked to compare Claim 1 of the ’606 Patent and Claim 1 of the
`
`’002 Patent and indicate whether a POSITA would perceive that they are directed to the same
`
`concept. In my opinion, while both claims are the field of communications and share some
`
`similarities, they are not directed to the same concept. Also, I was asked to answer the
`
`question of whether Claim 1 of the ’606 Patent is directed to the idea of routing a call based on
`
`participant characteristics (specifically, identity). In my opinion, it is factually inaccurate and
`
`inconsistent with the specification and claims to characterize Claim 1 as being directed to
`
`routing a call based on participant characteristics (specifically, identity). Third, I was asked to
`
`explain whether any technical advantages arise from the distinct concept contained in Claim 1.
`
`I will begin my analysis by focusing on differences between Claim 1 of each of the ’606 and
`
`’002 Patents.
`
`11.
`
`To begin with, Claim 1 of the ’606 Patent is focused on the association of each
`
`system user or subscriber (“participant”) with a specific element of a communication system’s
`
`infrastructure. The preamble states, the “first and second participant devices being associated
`
`with first and second network elements of the communication system, respectively.” This is
`
`important because, later in the claim, the routing decision is undertaken based on whether the
`
`first and second participant devices are associated with the “same” network element or not.
`
`For example, the claim recites, “processing the new second participant identifier, using the at
`4
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 5 of 18
`
`least one processor, to determine whether the second network element is the same as the first
`
`network element.” Nothing in claim 1 of the ’002 Patent corresponds to this step, which
`
`instead recites “classifying the communication, based on the new second participant identifier,
`
`as a system communication or an external network communication.” It is a misinterpretation
`
`of the claims and misunderstanding of the patent specification to equate these two steps. In
`
`particular, it is an error to equate the step of “when the second network element is determined
`
`not to be the same as the first network element…” (in the ’606 Patent) with the step of “when
`
`the communication is classified as an external network communication…” (in the ’002 Patent).
`
`The step of “when the second network element is determined not to be the same as the first
`
`network element…” (in the ’606 Patent) does not require classifying a communication as an
`
`“external network communication”. Quite to the contrary, Claim 1 of the ’606 Patent, if
`
`properly understood, assumes that when specific scenarios are tested for in the claim
`
`language—whether the network elements are the “same” or are “not the same”—this relates to
`
`communications within the system itself; it does not relate to a decision to route the
`
`communication outside of the system to an external network (or external communication
`
`system) through a gateway. An external network, such as is recited in Claim 1 would be
`
`outside of the system network in Claim 1.
`
`12.
`
`A POSITA would interpret Claim 1 in part based on other claims and in light of
`
`the specification as a whole. For example, a POSITA would read Claim 1 in view of
`
`dependent Claim 14, which indicates that the action of producing a routing message identifying
`
`a gateway to an external communication system is mutually exclusive with the two scenarios
`
`described in Claim 1 of the ‘’606 Patent, as described above (i.e., whether the network element
`
`is the “same” or not). Claim 14 expressly recites: “receiving a third participant identifier
`
`associated with a third participant device, wherein the third participant device is not
`
`associated with either the first network element or the second network element; and
`5
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 6 of 18
`
`producing a routing message identifying a gateway to an external communication system that
`
`is not controlled by the system operator, using the at least one processor, to cause a further
`
`communication to be established to the third participant device” [emphasis added]. Clearly,
`
`the scenario in which the network elements are found “not to be the same” does not correspond
`
`to an “external network communication.” To assert otherwise, is to misinterpret the claim. A
`
`POSITA’s claim construction of Claim 1 would be informed, in part, by Claim 14, which
`
`indicates that a communication through a “gateway” to an “external” system occurs when there
`
`is no association of the callee with either the first or second “network elements”. Thus, Claim
`
`1 of the ’606 Patent is directed to a completely different decision and action than Claim 1 of
`
`the ’002 Patent.
`
`13.
`
`Other dependent claims in the ’606 Patent are consistent with the above-
`
`mentioned interpretation. Claim 15 depends from dependent Claim 14 and from independent
`
`Claim 1, and recites that the “external communication system” includes a public switched
`
`telephone network (PSTN) communication system. Claim 45 is a dependent claim that is
`
`similar to Claim 14, discussed above, and indicates that routing to an external communication
`
`system is something that is distinct from routing via the first or second network element,
`
`except that the claim is directed to an apparatus.
`
`14.
`
`Furthermore, the specification provides illustrative examples of preferred
`
`embodiments which are consistent with the above interpretation. The specification describes
`
`examples of calls between subscribers that are associated with the same node or with a
`
`different node.
`
`Id., e.g., 25:61-28:44 (how to route calls between subscribers that are
`
`associated with the same node); and 21:10-23:49 (how to route calls between subscribers that
`
`are associated with respective different nodes). These two scenarios are clearly distinguished
`
`in the specification from a third scenario, namely, that the callee is a non-subscriber, is not
`
`associated with any node in the system, and thus calls must be made through a “gateway” to
`6
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 7 of 18
`
`the subscriber, for example, to a PSTN.
`
`Id. at 23:50-25:60. This mode of communication is
`
`distinct from the above-mentioned two scenarios and is described separately.
`
`15.
`
`In view of the foregoing, a POSITA would infer that Claim 1 of the ’606 Patent
`
`and Claim 1 of the ’002 Patent are directed to distinct types of routing, where the former,
`
`unlike the latter, selectively and transparently allows subscribers to communicate with each
`
`other within a communication system, without leaving through a gateway to an external
`
`communication system, regardless of which network element within the system a subscriber
`
`uses for communication services.
`
`16.
`
`Furthermore, the routing in Claim 1 of the ’606 Patent is not based merely on
`
`participant characteristics (specifically, identity). Instead, Claim 1 indicates that the second
`
`participant (callee identifier, whether taken by itself, or together with the first participant
`
`(caller) identifier, is insufficient to route a communication. Claim 1 recites that the system
`
`stores configuration information that is specific to the first participant is used (“first participant
`
`profile”) and that this user-specific system configuration is used to process the second
`
`participant (callee) identifier. See id., Claim 1 (e.g., “produce a new second participant
`
`identifier based on at least one match between the second participant identifier and the at least
`
`one first participant attribute”). Thus, different first participants with differently configured
`
`settings in their profile (different “first participant attributes”) can have a different outcome for
`
`this step. The use of user-specific configuration information allows user-specific handling of
`
`callee identifiers in the specification; for example, a caller can define a manner of dialing
`
`phone numbers that the caller prefers by setting attributes in the profile appropriately.
`
`Id.
`
`Compare Figs. 11 and 12: the Calgary subscriber can dial international phone numbers using
`
`an IDD prefix of “011” whereas the London subscriber will instead use an IDD prefix of “00”.
`
`These settings are entirely configurable and allow the system to be flexible enough to handle
`
`the diverse needs of subscribers over large geographical areas or even on different continents.
`7
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 8 of 18
`
`17.
`
`Claim 1 of the ’606 Patent (as also illustrated in the specification by example)
`
`indicates that there are other system configuration settings that affect the routing decision,
`
`namely, configuration information that associated subscribers with particular “network
`
`elements” (or nodes). The claim evaluates the new second participant identifier as part of
`
`identifying which “network element” the called party is associated with. By way of example,
`
`in the specification, the aforesaid profiles of the Calgary and London subscribers illustrate that
`
`the former subscriber’s profile is associated with a different “domain” (identifies a different
`
`“network element”) than the latter’s. Id., Fig. 11 (“Domain” is “sp.yvr.digifonica.com”); Fig.
`
`12 (“Domain” is “sp.lhr.digifonica.com”). Moreover the specification provides disclosure of
`
`including a node identifier into a username associated with each subscriber and using a
`
`database to determine which usernames (or a portion of the username, such as a prefix) are
`
`mapped to which IP address or fully qualified domain name of a node. Id., Figs. 17 and 18.
`
`These system databases thus contain configuration information about how subscribers are
`
`distributed over geographically distributed nodes, each serving a respective set of subscribers.
`
`Id. at 13:20-67. Thus, knowing participants’ characteristics (their identity, e.g., phone number)
`
`is not enough to route a call. What is needed is system configuration information, both about
`
`user-specific attributes that affect how each caller’s calls are handled, but also system
`
`configuration information about which callers are “associated with” which network elements or
`
`nodes. The patent discloses setting up such configuration information when registering a
`
`subscriber. Id. at 15:48-67.
`
`18.
`
`A POSITA would see these differences with respect to Claim 1 of the ’002
`
`Patent also reflected in other claims of the ’606 Patent. Claim 23 indicates that which address
`
`(i.e., “first IP network address” or “second IP network address”) is used for establishing the
`
`communication depends on which network element a subscriber device is associated with.
`
`Claim 24 recites, in part, “wherein the first and second communication nodes are operably
`8
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 9 of 18
`
`configured to provide communications services to communication devices associated with first
`
`and second geographical areas, respectively”. This reflects the concept that nodes are
`
`responsible for providing services associated with geographical areas and that subscriber
`
`devices are associated with respect geographical areas, which is a system configuration setting.
`
`Id. at 13:20-40. As Claim 24 further recites, this can be combined with allocating a node for
`
`“load sharing” for at least some geographical areas and the associated subscriber devices.
`
`Notably, Claim 27 recites, “determine a network element with which the second participant
`
`device is associated based on a geographical area associated with the second participant
`
`identifier and to identify the network element with which the second participant device is
`
`associated in the routing message” [emphasis added]. Again, this concept is clearly absent
`
`from Claim 1 of the ’002 Patent, which does not recite the concept of assigning different
`
`subscribers to different nodes or network elements within the system for communication
`
`services. Furthermore, the stored system configuration information that enables determination
`
`of which device is associated with which network element makes improvements possible over
`
`the prior art by providing flexibility to assign subscribers to nodes (or “network elements”) in a
`
`way that will preserve the availability and resilience of the system over a wide geographic area.
`
`Id. at 1:53-59.
`
`19.
`
`Claim 1 and other claims of the ’606 Patent thus include a system architecture
`
`which is suitable for solving the problems of serving a large number of geographically
`
`dispersed subscribers. As described in the specification, a node may provide services to most
`
`of a continent or part of a continent, to provide communication services for subscribers in a
`
`particular wide geographical area.
`
`Id. at 13:20-40. And yet, routing does not depend on the
`
`characteristics of the caller or callee (e.g., the callee phone number). Indeed, as described
`
`herein, the phone number (or other identifier) can be decoupled form the area in which the
`
`subscriber lives. It can also be decoupled from elements of the infrastructure such that new
`9
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 10 of 18
`
`nodes and network elements can be added, and system configuration settings, to scalably
`
`handle providing services to any number of subscribers seamlessly and transparently. An
`
`improvement of prior art methods is that subscribers can place calls without being concerned
`
`about any changes in the underlying infrastructure. The ability to also allocate load sharing
`
`duties to some nodes routing to destinations further enables the scalability and availability of
`
`services.
`
`20.
`
`Unlike Claim 1 of the ’002 Patent, which does not recite a method of associated
`
`different subscribers with different nodes or network elements and then determining how to
`
`route to them, the claimed method describe a specific method and system designed to use
`
`system configuration information to transparently route communications between a plurality of
`
`geographically dispersed subscribers that rely for services on respective network elements of
`
`this distributed communication system.
`
`From my experience, I am unaware of any
`
`conventional communication system that provided these features in the manner recited in the
`
`claims, therefore in my view, the specific invention in Claim 1 of the ’606 Patent is not
`
`conventional, routine or well-understood. It is also unconventional relative to how historical
`
`switchboard operators performed their duties, as I will further describe below.
`
`B.
`
`21.
`
`A skilled person would understand how to perform the claimed invention.
`
`I have been asked to consider whether a POSITA would have understood how
`
`to perform the invention recited in Claim 1 of the ’606 patent.
`
`22.
`
`A POSITA’s understanding would be based on their general knowledge in light
`
`of the intrinsic evidence, which includes the patent specification, claims, and file history. I
`
`understand that while such intrinsic evidence is preferred, a POSITA could also rely on
`
`extrinsic evidence such as technical documentation known in the field of the invention to
`
`understand the patent and interpret its claims. In my view, the functions described by Claim 1
`
`of the ’606 Patent would have been readily understood by a POSITA at the time of invention.
`10
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 11 of 18
`
`While the claims contain some broad language, they exclude communication systems which do
`
`not contain the recited combination of elements. The claims do not, to my knowledge,
`
`describe any conventional, well-known or well-understood technologies or processes, whether
`
`implemented by an apparatus, system, or technological method, nor do they describe any well-
`
`known human-implemented processes such as historical switchboard operators, who did not
`
`follow anything like the method recited in the claims, as I will further explain below. Claim 1
`
`is reproduced at 37:30-38:3 of U.S. Patent No. 10,218,606 (“the ’606 Patent”).
`
`23.
`
`For example, the illustrative embodiments in the ‘606 Patent’s specification
`
`would enable a POSITA to understand and practice the claims. Claim 1 recites, in part, a
`
`method that “produce[s] a new second participant identifier,” but that is not all; the claim also
`
`requires “processing the second participant identifier and the at least one first participant
`
`attribute, using the at least one processor, to produce a new second participant identifier based
`
`on at least one match between the second participant identifier and the at least one first
`
`participant attribute” [emphasis added].
`
`Id. The ‘606 patent specification discloses specific
`
`examples of how to compare portions of the second participant identifier with first participant
`
`attributes to translate a dialed number from one format to another format (see, e.g. ‘606 Patent
`
`at Fig. 8B; 20:33-58). A POSITA would appreciate that the examples disclosed in the
`
`specification constitute exemplary steps and would have no difficulty in understanding the
`
`claim element of processing “based on at least one match” as a concrete limitation for “how”
`
`the processing is achieved (see, e.g. ‘606 Patent at Fig. 8B; 20:33-60; 22:3-23:22). This recited
`
`feature distinguishes the claimed invention from methods and systems that do not rely on “first
`
`participant attributes,” which, Claim 1 states, are identified in a “first participant profile.” For
`
`example, switchboard operators did not use a stored “profile,” nor did they identify “attributes”
`
`based on that profile, nor did they “match” the called party’s identifier against such “attributes”
`
`(which were not needed) as part of their decision-making in how they acted upon a caller’s
`11
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 12 of 18
`
`instructions. The specification also has various other examples of how to perform a match, and
`
`this would further inform the POSITA as to various types of matching methods.
`
`Id., 17:27,
`
`24:10-11, 26:16-26, 27:18-21. More generally, the concept of comparing stored values in
`
`order to generate a match is something that a POSITA would understand based on their
`
`knowledge and experience, in light of the specification. The profile attributes being matched
`
`could be retrieved from a “memory” that stores them (as recited in Claim 1), such as a RAM,
`
`EEPROM or database, to take a few examples. Thus, it would be within the ordinary skill of a
`
`POSITA to know how to implement a mechanism to produce a new second participant
`
`identifier. This feature of the claims does not require an explanation of “how”.
`
`24.
`
`As another source of information, the POSITA could look to embodiments
`
`recited in the dependent claims, which describe how to implement features recited in the
`
`independent claims. For example, Claims 11 and 12 recite, in part: “wherein processing the
`
`second participant identifier comprises locating the new second participant identifier in a
`
`database based on the second participant identifier”. Id. at 39:6-18. A POSITA would
`
`understand that locating the new second participant identifier in a database as an example of
`
`how a new second participant identifier could be produced.
`
`25.
`
`To take another example, Claim 1 recites a step involving processing “the new
`
`second participant identifier [to] determine whether the second network element is the same as
`
`the first network element.” Again, it is clear that a POSITA would have no difficulty
`
`understanding “how” these claimed steps are performed in view of the intrinsic and extrinsic
`
`evidence. For example, the specification of the ‘606 Patent discloses specific steps in which a
`
`comparison is made between the first and second participant usernames (see, e.g. ‘606 Patent at
`
`Fig. 8A, 8B; 21:11-29; 25:62-26:7). The specification also discloses that the usernames (or a
`
`portion of the username, such as a prefix) can be mapped to an IP address or fully qualified
`
`domain name of a node.
`
`Id., 21:30-46, FIGS. 17 and 18. A POSITA would appreciate that
`12
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 13 of 18
`
`database records that associated subscribers (e.g., the Calgary subscriber in FIG. 18) with
`
`particular node addresses, could be a source for making a comparison, and determining
`
`whether the calling party was associated with the same node as the called party. It will be
`
`appreciated that this is just one example of an implementation. In addition to using node table
`
`records, a POSITA would know other methods and data structures for storing information that
`
`associated subscribers with nodes, such as binary trees. Therefore, it would be well within the
`
`ordinary skill of a POSITA to know “how” to implement a mechanism to produce a new
`
`second participant identifier.
`
`26.
`
`In addition to the foregoing, the specification’s disclosure of how node
`
`addresses can be mapped to usernames (see, e.g., 21:30-46), illuminates also the fact that this
`
`database is available and can be searched by the routing algorithm (e.g., FIGS. 8A-8D) and
`
`provides a useful example of a way of determining how the “first” or “second” network
`
`addresses of suitable “network element(s)” can be generated in Claim 1. More generally, the
`
`specification provides a detailed of illustrative examples and implementations of routing intra-
`
`and inter- node communications. Id., e.g., 25:61-28:44 (how to route calls between subscribers
`
`that are associated with the same node); and 21:10-23:49 (how to route calls between
`
`subscribers that are associated with respective different nodes). The specification would enable
`
`a POSITA to practice Claim 1, although it will be appreciated that other implementations,
`
`consistent with the claims, could be used by the POSITA, too.
`
`27.
`
`Claims 19 and 24 state that the underlying communication system may provide
`
`a “node” in “geographical proximity” to at least one network element “to provide load
`
`sharing.” In my view, how to do this would be readily understandable to a POSITA in light of
`
`general knowledge and the specification. The concept of load sharing is a term of art in the
`
`field of network communication that a POSITA would know and therefore would understand
`
`generally how to implement. In addition, the specification illustratively describes setting up a
`13
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 14 of 18
`
`distributed architecture of nodes that provides communication services to respective
`
`geographical areas and indicates that a node could be setup to provide load sharing in a
`
`particular service region if needed.
`
`Id. at 13:20-47; compare 1:52. A POSITA would also
`
`have access to technical literature on methods of performing load sharing, which could be
`
`implemented in the context of this architecture. Therefore, a POSITA’s general knowledge in
`
`light of the specification would be enough to understand how to add load sharing as claimed.
`
`28.
`
`In summary, a POSITA would understand and know how to perform the
`
`invention in Claim 1 and other claims in the context of general knowledge, the specification,
`
`and the other claims.
`
`C.
`
`29.
`
`Historical switchboard operators and processes are not analogous.
`
`I have been asked whether historical switchboard operators, performed the
`
`same, or a substantially the same (i.e., analogous), process as the one described in Claim 1, and
`
`also, whether it is correct to say that a switchboard operator would have directed a call based
`
`on where a caller was located. In my opinion, the answer is “no” to both questions, as
`
`explained below.
`
`30.
`
`As already explained above, the claim recites limitations that had no counterpart
`
`or analog in the processes for switchboard operators. To the best of my knowledge, in contrast
`
`to the language recited in Claim 1, switchboard operators did not require access to a stored
`
`caller “profile,” nor did they need to identify caller “attributes” based on any such profile, nor
`
`did they “match” any such attributes from a “profile” (which as explained above, didn’t exist)
`
`with a “second participant identifier” (e.g., the name of the called party). Instead, they simply
`
`acted upon the instructions given by plugging in a wire associated with the incoming call into
`
`the appropriate switchboard connection.
`
`31.
`
`Additionally, while it is true that the operator of a first switchboard might call
`
`upon a second switchboard operator at a remote location to help route the call, this sequence of
`14
`
`Doc ID: 4b8b58f5714da74387122b78b86ed8d60292e0d1
`
`

`

`Case 6:20-cv-00272-ADA Document 106-3 Filed 12/13/23 Page 15 of 18
`
`steps differs from Claim 1, as well. Notably, involving a second operator/switchboard required
`
`two routing decisions: one, by the first switchboard operator (i.e., to decide that the call could
`
`not be routed on the same switchboard); and then, once the first operator successfully
`
`connected to the second operator’s switchboard, the second operator needed to make a second
`
`decision (i.e., to route the call to the called party). This multi-step process involving two
`
`operators and switchboards required at least two “routing” decisions, taken in a particular
`
`sequence. However, Claim 1 does not require two separate decisions, nor does it require that
`
`two routing decisions be taken in a particular sequence. Instead, Claim 1 decides whether the
`
`second participant is associated with the same element or a differen

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