`Case 6:24-cv-00298-DC-DTG Document1-4 Filed 05/30/24 Page 1 of 59
`
`EXHIBIT 4
`EXHIBIT 4
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 2 of 59
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`VOIP-PAL.COM, INC.
`Plaintiff,
`
`v.
`T-MOBILE USA, INC.;
`Defendant.
`
`CIVIL ACTION NO. : 6:24-cv-298
`
`JURY TRIAL DEMANDED
`
`DECLARATION OF DANIJELA CABRIC, PH.D.
`
`I, Dr. Danijela Cabric, declare as follows:
`
`I.
`
`INTRODUCTION
`
`1.
`
`I have personal knowledge of the facts contained in this declaration and I could
`
`competently testify to those facts as a witness. In preparing this Declaration, I have reviewed the
`
`following, as well as the other documents discussed herein:
`
`a. U.S. Patent No. 8,542,815 (“the ’815 Patent”) and its file history;
`
`b. U.S. Patent No. 9,179,005 (“the ’005 Patent”) and its file history;
`
`c. U.S. Patent No. 10,218,606 (“the ’606 Patent”) and its file history.
`
`2.
`
`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 consulting rate of $500 per hour. My compensation is not dependent on and
`
`in no way affects the substance of my Declaration. I have no financial interest in VoIP-Pal or in
`
`VoIP-Pal’s patents.
`
`1
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 3 of 59
`
`II.
`
`QUALIFICATIONS
`
`3.
`
`My technical qualifications are as follows. I hold a Ph.D. in Electrical Engineering
`
`in 2007 from the University of California, Berkeley 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.”
`
`4.
`
`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.
`
`5.
`
`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.
`
`6.
`
`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
`
`2
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 4 of 59
`
`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 at least 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.
`
`7.
`
`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.
`
`8.
`
`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
`
`9.
`
`I have been asked to review the VoIP-Pal patents listed above and provide context
`
`regarding the understanding of these patents of a person of ordinary skill in the art (“POSITA”) at
`
`the time of invention. I have also been asked to provide some background information and
`
`comparisons to other communication systems, including an assessment of what inventive concepts
`
`claimed in the VoIP-Pal patents would not have been well-known, routine or conventional to the
`
`POSITA.
`
`10.
`
`Based on my review of the above-mentioned patents and my background and
`
`experience in the field of computer science, it is my opinion that one of ordinary skill in the art as
`
`of the priority date would be someone with an undergraduate degree in either Computer Science,
`
`Computer Engineering, Electrical Engineering, or a closely related discipline. Furthermore, I
`
`3
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 5 of 59
`
`believe that such a person would also have 2 years of experience in system-level software
`
`development. In my opinion a greater degree of professional experience could serve to replace
`
`some degree of formal education. I also believe that some greater degree of formal education
`
`could serve to replace some degree of professional work experience.
`
`A.
`
`11.
`
`Background of the Technology of the Patents
`
`The earliest telephone systems to receive public use within the United States
`
`involved a telephone directly connected to a switchboard that had a human operator. The operator
`
`was signaled when the portion was lifted from the hook. A caller would then identify the person
`
`they wished to call to the operator. If the callee was connected to the same telephone switch board,
`
`the operator would physically pull out a cable associated with the caller’s phone and plug the cable
`
`into a socket associated with the callee’s telephone. If the callee was associated with a different
`
`switchboard, the operator would connect the caller to an appropriate switchboard with a different
`
`human operator. This arrangement was error prone (e.g., operators would often connect the wrong
`
`party) and limited the number of possible telephones because of the physical limits of switchboards
`
`and cables to be pulled. This basic system developed into the traditional analog telephone service,
`
`also called the Plain Old Telephone Service (“POTS”), in which there was a dedicated, point-to-
`
`point electrical connection between the caller and callee.
`
`12.
`
`Rotary dialing eventually was introduced, beginning at around the turn of the 20th
`
`century, where a rotary disk was marked with numbers from zero to nine. A caller would spin the
`
`wheel and a mechanical device in the telephone would cause a sequence of electrical pulses to be
`
`sent to the network corresponding to the digit dialed, for example, four pulses would be sent for
`
`the number four. Rather than speaking to a human operator, an electric device would count the
`
`pulses and begin to route a call once an appropriate and valid sequence of digits was dialed by the
`
`4
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 6 of 59
`
`caller. This advancement improved reliability of call routing and reduced the time required to
`
`initiate a call but there was still a dedicated, point-to-point electrical connection between the caller
`
`and the callee. As multiple companies began to provide telephone services and the number of
`
`customers increased, a caller could be a customer of one telephone company and the callee could
`
`be a customer of another. To address this problem, trunk lines were used to connect one company
`
`to another.
`
`13.
`
`Eventually, as the number of companies continued to increase and telephone
`
`services spread over much larger geographic areas, the notion of a Public Switched Telephone
`
`Network (“PSTN”) emerged. Dedicated wires were used to connect a caller and callee and were
`
`“circuit-switched” to connect these two participants. The PSTN developed gradually into the
`
`middle of the 20th century, still built around rotary dialing and circuit-switched, analog POTS
`
`connections to individual telephones. A circuit-switched network assigns dedicated resources,
`
`such as switch settings and specific wires, to connect a caller to a callee. While the call is ongoing,
`
`these resources cannot be used for any other communications.
`
`14.
`
`The next important advancement for consumer telephone service, introduced
`
`broadly during the second half of the 20th century, was the introduction of push-button telephones.
`
`The rotary dial was replaced by a matrix of buttons, each labeled with a digit from zero through
`
`nine along with the additions of ‘*’ and ‘#’. The underlying signaling technology was dual-tone
`
`multiple-frequency (“DTMF”) and involved two different audible tones being sent simultaneously
`
`from the telephone into the telephone network. A receiver within the network decoded these tones
`
`and formed them into a sequence of digits indicating the number of the callee.
`
`15.
`
`Around this time a scheme for international telephone addressing was introduced,
`
`with a numeric protocol for identifying one country from another and providing country-specific
`
`5
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 7 of 59
`
`routing within the destination country. The E.164 standard now documents how telephone
`
`numbers can be uniquely identified. Local rules govern how to dial a telephone number to cause
`
`a telephone call to be routed. While many advances, such as DTMF dialing and automated
`
`international routing, may have been originally introduced via ad hoc methods, eventually they
`
`required multiple parties (companies and governments) to agree on standards to enable wide-
`
`spread reliable use and inter-operability among different physical communications networks.
`
`Even with these advances, the systems still relied on circuit-switched technology that dedicated
`
`resources between callers and callees during the call.
`
`16.
`
`The move to take human operators out of the loop, with the introduction of rotary
`
`dialing, combined with the fast increase in demand for telephone services throughout the 20th
`
`century, resulted in the development of automated telephone switches. These switches originally
`
`supported analog voice calls initiated via rotary dialing and dedicated ports as well as physical
`
`wires for each circuit-switched call. Eventually analog voice services were replaced within the
`
`network with digital voice. Digital voice is communicated using a sequence of chunks (or packets)
`
`of data. This advancement allowed the physical resources to be shared among multiple calls over
`
`short bursts of time. For example, a physical wire can move a packet for one call at a specific
`
`instance in time and then move a packet for a totally different call subsequently, only to later return
`
`to transfer a new packet for the original call. This advance is called packet-switched
`
`communications and provided an important increase in network reliability and efficiency while
`
`driving down the cost. However, in most situations throughout the 20th century (and often still
`
`today), the connection to the end user’s physical telephone is analog. The conversion between
`
`analog and digital encoding is commonly done at the point where the PSTN network switch
`
`connects to the POTS handset, for example, at a Class-5 telephone switch, which connects the
`
`6
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 8 of 59
`
`POTS handset to the PSTN at the service provider’s central office. Various signaling protocols
`
`were used to setup calls through switches at PSTN central offices or exchanges including in-band
`
`signaling, which was superseded by out-of-band signaling (e.g., “Signaling System 7” or “SS7”).
`
`17.
`
`The Internet became important to consumers, via broad deployment, during the late
`
`1980’s and early 1990’s. Eventually available bandwidth and reliability increased to the point
`
`where pioneers began to experiment with techniques to carry voice communications over the
`
`Internet. These early efforts then began to focus on techniques called Voice Over Internet Protocol
`
`(VoIP) and session initiation protocol (SIP). VoIP provided a consistent set of protocols and
`
`mechanisms for moving digital voice packets between two callers using the Internet rather than
`
`existing PSTN networks. For example, SIP provided a mechanism for establishing and terminating
`
`these calls between users of a VoIP service. Furthermore, a callee could register with a VoIP
`
`service so that an identifier (such as their name, email address or a nickname) could be associated
`
`with the computer to which they were logged in. Eventually VoIP services expanded to provide
`
`interoperability with the existing PSTN services. For example, the company Skype began to allow
`
`a user to call a PSTN number using a feature marketed as “Skype out”. However, the user was
`
`required to explicitly classify the call as a PSTN call by specifying a real physical telephone
`
`number. In this case the VoIP system included a gateway between the VoIP network and the PSTN
`
`network in order to route to the PSTN telephone. Calls placed to a proprietary non-PSTN user
`
`identifier, such as an email or nickname, however, remained within the VoIP network and were
`
`not routed to the PSTN network and did not connect to a POTS telephone.
`
`18.
`
`The advent of VoIP technology allowed customers to physically move their
`
`telephones from one location to another, even from one continent to another, with no fundamental
`
`change in its operation from the point of view of a caller once a connection to the Internet was
`
`7
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 9 of 59
`
`established. However, the integration of network equipment to route between different types of
`
`networks using VoIP, for example from a VoIP caller in Europe to a PSTN callee in the United
`
`States, introduced a number of new complications. The VoIP service needed to be able to
`
`distinguish between callees within the VoIP network and those outside of it and thus required
`
`different methods for identifying callees and routing to them depending on whether the callees
`
`were within or outside the VoIP network. One way to identify callees on the VoIP network was
`
`to use a predefined proprietary user identifier such as an email or nickname. The VoIP service
`
`provider also needed to interpret dialed PSTN numbers in order to correctly route calls to a PSTN
`
`callee. A VoIP caller had to use different types of callee identifier depending on whether or not
`
`the destination (callee) was within the VoIP network or not. The caller’s choice of the type of
`
`callee identifier thus explicitly specified the destination network.
`
`19.
`
`Starting from about the 1960’s, some organizations desired to take greater control
`
`over their telephony network and thus created a privately controlled network by using a private
`
`branch exchange (PBX), which was a kind of private switch that allowed them to assign their own
`
`internal phone numbers or “extensions” to their users (for example, short three- or four-digit
`
`numbers for convenient dialing) and also to control calls over their internal network without
`
`recourse to the public switch telephone network (PSTN). Keeping internal calls on their internal
`
`network also allowed these organization to avoid some of the expense of using an external network
`
`such as the PSTN. As networks migrated to Voice-over-IP (VoIP), some of these PBXs began to
`
`support VoIP protocols over a packet switched network. However, the typical method of operation
`
`required the user to dial a special code to signal to the PBX when a PSTN number was being
`
`dialed, which would be sent to the PSTN. For example, it was typical to require the user to “dial
`
`9” to send a call over an outside line to the PSTN, whereas other dialed numbers were interpreted
`
`8
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 10 of 59
`
`as internal and were routed internally provided that they identified a valid extension. Again, the
`
`user manually specified the selection of the network on which the call should be routed by their
`
`manner of dialing (e.g., by dialing ‘9’). Inwardly bound calls from the PSTN were typically passed
`
`through a receptionist connected to the PBX. Some PBX systems had Direct Inward Dialing (DID)
`
`features to allow incoming calls to be routed directly to a specific extension or phone within the
`
`organization’s Private Branch Exchange (PBX) system, bypassing the receptionist. Organizations
`
`purchased telephone numbers from a PSTN telephone company and assigned them to individual
`
`PBX extensions within the company. The first DID service for PBXs in the U.S. appears to have
`
`been developed by AT&T starting in the 1960s, nowadays typically delivered on a Primary Rate
`
`Interface (PRI) circuit. The use of DID lines on PBX systems benefited organizations for several
`
`reasons: it allowed callers to reach specific extensions directly, without the need for a receptionist
`
`or interactive voice response system; it allowed existing and new PSTN phone numbers to be
`
`assigned to particular local extensions by the PBX administrator; it allowed a large number of local
`
`extensions to share a smaller number of physical PSTN lines, with only some extensions having
`
`dedicated PSTN phone numbers. Typically, an organization that operated its own PBX would buy
`
`a block of PSTN numbers from a PSTN service provider (e.g., AT&T) such that if any of those
`
`numbers were dialed, they were forwarded by AT&T to the PBX, which in turn, would distribute
`
`the call to the appropriate extension based on the PBX configuration. This enabled the direct
`
`inward dialing of calls from the PSTN to PBX users. Conventionally, however, outgoing calls
`
`from PBX users to PSTN numbers were signaled by the PBX users dialing a certain prefix (e.g.,
`
`“9”), thus PBX users specified routing over the PSTN by dialing this prefix. By way of
`
`background, direct inward dial numbers and lines (DIDs) were sometimes referred to as “Direct-
`
`9
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 11 of 59
`
`in-Dial numbers”, “DID lines”, “Direct Dial-in numbers”, “DDI numbers,” “DDI lines”, or private
`
`direct dialing numbers, for example.
`
`20.
`
`Digifonica’s advancements over the prior art. The above-described history and
`
`technical background serves to provide important context for understanding and recognizing the
`
`benefits of the technology disclosed and claimed in the asserted VoIP-Pal patents, which were
`
`formerly assigned to a predecessor-in-title company, namely, Digifonica. At a high level, VoIP-
`
`Pal’s ’815 and ’005 Patents describe and claim improved methods of routing and interoperability
`
`as between a private network and the PSTN and included inventive concepts that were not well-
`
`understood, routine or conventional in the prior art, as will be further described and explained
`
`below. VoIP-Pal’s ’606 Patent is focused mostly on improved methods for routing within an
`
`interconnected communication network comprising multiple nodes or network elements. I will
`
`begin by discussing the ’815 and ’005 Patents, and then will discuss the ’606 Patent.
`
`B.
`
`21.
`
`Discussion of the ’815 and ’005 Patents
`
`Claim 14 of the ’815 Patent. By way of example, Claim 14 of the ’815 Patent
`
`provides improvements and inventive concepts that go beyond Claim 1. Claim 14 recites, “The
`
`process of claim 7 further comprising, causing a database of records to be searched to locate a
`
`Direct-Inward-Dial (DID) bank table record associating a public telephone number with said
`
`reformatted callee identifier and if said DID bank table record is found, classifying the call as a
`
`private network call and if a DID bank table record is not found classifying the call as a public
`
`network call.” Claim 7 of the ’815 Patent recites, in turn, “The process of claim 1 further
`
`comprising formatting said callee identifier into a pre-defined digit format to produce a re-
`
`formatted callee identifier.” In view of the patent specification and the claims, a POSITA would
`
`understand Claim 7 as disclosing that a callee identifier can be transformed to a callee identifier in
`
`10
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 12 of 59
`
`a format recognizable by the system for DID searching (Claim 14) and subsequent use in routing
`
`(Claim 1). While some preferred embodiments of a reformatting technique are discussed in the
`
`’815 Patent with reference to Figure 8B, a POSITA would appreciate that other methods could be
`
`used to generate an identifier that the system can use to identify a route to the callee. This is
`
`discussed in further detail below.
`
`22. More particularly, Claim 14 of the ’815 Patent recites causing a database of records
`
`to be searched to locate a DID bank table record associating a public telephone number with the
`
`callee identifier. A public telephone number or DID number would be one that is recognizable as
`
`a PSTN compatible number, for example, a number compatible with the E.164 standard for PSTN
`
`telephone numbers. As a POSITA would understand, such a number would, for example, typically
`
`include a country code (CC), a national destination code (NDC) or area code, and a subscriber
`
`number (SN). See id., 19:4-18, 22:34-44. A DID number or “public number”, as recited in the
`
`claim, could include PSTN-based geographical indications helpful for routing to PSTN locations.
`
`For example, a PSTN number could include “44” as a country code (to represent the United
`
`Kingdom) or “1” (to represent the U.S./Canada) , for example, and an area code such as “604” or
`
`“778” to represent areas associated with Vancouver, Canada. See ’815 Patent at 18:32-37, Figures
`
`9, 10 and 12. When expressed in a human-readable form, an E.164 formatted number typically
`
`looks like this: +[Country Code][National Destination Code][Subscriber Number]. For example,
`
`a number in London might be formatted as +44 20 1234 5678, where “44” is the country code for
`
`the UK, “20” is the NDC for London, and “1234 5678” is the subscriber number. A POSITA
`
`would understand that the E.164 format is exemplary and that not all parts of the string may be
`
`necessary to represent a PSTN number if the format is understood. For example, a “+” is not
`
`necessary if it is understood that the first digit or digits of a number represent a country code (e.g.,
`
`11
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 13 of 59
`
`the leading “1” in item 283 in Fig. 14 is a code representing Canada/US). See id., Figs. 13-14 and
`
`19:15-18. In some contexts, a PSTN number may be represented in shorter form, for example, by
`
`omitting features such as the country code when a “local” PSTN number is being called. See id.,
`
`21:65-22:6. As another example, the same local PSTN number might alternatively be dialed in a
`
`national style by prepending a national dialing digit. See id., 21:33-37. Similarly, a POSITA
`
`would recognize that public numbers could be represented by a variety of different DID database
`
`formats, so long as they were consistent and recognizable; for example, a country code could be
`
`omitted or implicit from a DID record in some internal system representations of a PSTN number
`
`(e.g., the system might be configured to assume that a 10-digit phone number is located in
`
`Canada/U.S., which nevertheless would be associated with a specific user on the PSTN network).
`
`Id., 19:4-10, 22:44-48. In other words, a POSITA would understand that there are many ways to
`
`represent a public number. The E.164 format is not the only format for specifying public numbers,
`
`nor does it mandate how to validly dial a telephone number, which can vary in different locations.
`
`A POSITA would recognize from Claim 14 that the claimed system associates public numbers
`
`with “direct-inward-dial” (DID) records, which indicates the ability to receive calls from the PSTN
`
`(which is how a “DID” has been conventionally defined). However, a POSITA would recognize
`
`that Claim 14 indicates that a DID information database is searched for subscriber-initiated
`
`outgoing calls, not just direct inward calls from PSTN telephones incoming from non-subscribers
`
`(e.g., via a gateway).
`
`23.
`
`Claim 14 includes an unconventional inventive concept: using a DID database to
`
`configurably remap public callee identifiers from both private and public network sources to route
`
`calls to a private network node or PSTN gateway. As discussed above, a DID number was
`
`typically used in PBXs to route inward-bound calls from the PSTN to a specific “extension” of the
`
`12
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 14 of 59
`
`PBX (whereas calls between PBX users were made by dialing shorter PBX extension numbers).
`
`Similarly, the patent specification would indicate to a POSITA that stored DID information is
`
`“associated with the user on the PSTN network”, meaning that PSTN callers could call into the
`
`system based on the DID information that would be associated with a system subscriber upon
`
`registration, for example. See id., 19:4-10. Notably, Claim 14 recites a database mechanism for
`
`associating public (PSTN) numbers with user devices and integrating the routing of
`
`communications to a specific subscriber (associated with a DID entry) both from other subscribers
`
`(i.e., subscribers of the private network who are calling the specific subscriber from the private
`
`network) and from non-subscribers who are calling the specific subscriber from the PSTN (e.g.,
`
`via a gateway). Locating DID information for the called subscriber in the DID database is how
`
`the call is classified as a private network call (compare “classifying” in Claims 1 and 14), which
`
`is used for “producing a private network routing message for receipt by a call controller” to effect
`
`the routing of the communication to “an address, on the private network, associated with the
`
`callee” (Claim 1). In summary, DID-based calls from both private network subscribers and non-
`
`subscribers are routed to the called subscriber over the private network.
`
`24.
`
`A POSITA would recognize that DIDs were conventionally used for direct inward
`
`dialing in PBXs. Similarly, in the context of the patent, the POSITA would recognize that a DID
`
`would setup calls from the PSTN such as through a third party invite. Id., 16:56-62, 17:11-15.
`
`However, the scenario in Claim 14 points to some unconventional differences. In Claim 14, the
`
`application of DID information effectively merges the aforesaid routing of communications from
`
`public network sources (i.e., direct inward dialed calls from the PSTN) with those from private
`
`network sources (i.e., DID-based calls from other subscribers of the private network) to route to
`
`the called subscriber. However, for calling subscribers, the same DID database information is
`
`13
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 15 of 59
`
`used to classify the call as to which network to use for subsequent routing (private or public).
`
`Compare Claims 1 and 14. In cases where a search of the DID database located DID information
`
`associated with the callee identifier received from the caller’s device, the availability of that
`
`information is how the call is classified as a “private network call” to produce a “private network
`
`routing message.” The absence of related DID information in the DID database is how it is
`
`determined that the call should not be placed on the private network, i.e., it is how the call is
`
`classified as a “public network call” to produce a “public network routing message,” to effect the
`
`appropriate routing with a call controller. Id. In both cases, the calling subscriber does not specify
`
`which network (public or private) to use for routing the call, and indeed, does not need to know
`
`this because of the use of DID information. In contrast, conventional PBXs used DIDs for
`
`incoming PSTN calls but outgoing calls from behind the PBX were made without using a DID by
`
`the caller explicitly selecting which network to use (the PBX’s private network or the PSTN) by
`
`the manner of placing the call. If the caller dialed a special code such as “9”, subsequent digits
`
`were interpreted as (and sent to) the PSTN via the PBX. However, calls within the PBX internal
`
`network were placed by dialing extension numbers which were different than the PSTN numbers
`
`represented by the DIDs. The DID number of the called subscriber was not used for classifying
`
`or routing the dialed call. Indeed, the DID number would not normally even be dialed by the caller
`
`unless the caller was calling from outside the PBX (e.g., from a mobile phone or home phone),
`
`that is, from a distinct external communication system.
`
`25.
`
`Furthermore, in PBX systems, it was not practical to dial the PSTN number
`
`represented by the DID number directly on the PBX since the leading digits of the DID number
`
`could overlap with and interfere with the dialing of private numbers (i.e., extensions) defined by
`
`the PBX operator. For example, consider a scenario in which a first subscriber wanted to call a
`
`14
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 16 of 59
`
`second subscriber having a DID with a “604” area code (see Fig. 14, item 274 of the ’815 Patent:
`
`“1 604 867 5309”). If the first subscriber was calling from within Vancouver, they might interpret
`
`the number as a local number (“604” is a typical Vancouver area code), and if so, they might want
`
`to dial “604-867-5309” (if 10-digit dialing was the local PSTN dialing convention), but this would
`
`potentially conflict with the dialing of PBX extension numbers starting with these digits (e.g.,
`
`“6048”). However, if the local convention was 7-digit dialing, the caller might wish to dial “867-
`
`5309”, which would conflict with dialing PBX extensions starting with those digits (such as
`
`“8675”).
`
`26.
`
`Another problem is that a conventional PBX was unable to interpret and follow
`
`changing local dialing conventions without interference with its existing private extension
`
`numbers. Whenever PSTN dialing conventions changed, if the PBX user tried to directly dial
`
`PSTN numbers according to the new convention, it would create a new set of conflicts. For
`
`example, Vancouver switched from 7-digit dialing to 10-digit dialing in 2001, and the rest of
`
`British Columbia switched in 2008. See: < https://www.cbc.ca/news/canada/vancouver-gets-10-
`
`digit-dialing-1.275934>
`
`and <https://www.canada.ca/en/news/archive/2007/06/new-dialing-
`
`come-british-columbia.html>. As a further problem, PBX users from outside the local area
`
`associated with “604” could try to dial “1-604-867-5309” (which includes a “1” national dialing
`
`digit for long-distance calls), but that could interfere with still other kinds of local extensions. To
`
`avoid such problems, PBXs required the use of a special code (e.g., dial “9”) to signal the caller’s
`
`intention to dial a PSTN number, which was then routed to the PSTN. Nor was dialing DIDs
`
`desirable since PBX users dialed short extension numbers to reach other PBX users. In summary,
`
`trying to dial DID numbers on a PBX system would not work reliably or was impractical. A
`
`POSITA would recognize that DID numbers in traditional PBXs were for the use of callers outside
`
`15
`
`
`
`
`Case 6:24-cv-00298-DC-DTG Document 1-4 Filed 05/30/24 Page 17 of 59
`
`the PBX, whereas in the ’815 and ’005 Patents, a system is disclosed in which DID-bas