throbber
Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 1 of 51
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`FLYPSI, INC. (D/B/A FLYP),
`
`
`
`
`
`Plaintiff,
`
`vs.
`
`GOOGLE LLC,
`
`Civil Action No. 6:22-cv-31-ADA
`
`JURY TRIAL DEMANDED
`
`PUBLIC VERSION
`
`Defendant.
`
`
`
`SECOND AMENDED COMPLAINT FOR PATENT INFRINGEMENT
`
`Plaintiff Flypsi, Inc. files this Second Amended Complaint for Patent Infringement against
`
`Google LLC and alleges as follows:
`
`THE PARTIES
`
`1.
`
`Plaintiff Flypsi, Inc. (“Flyp”) is a Delaware corporation with its principal place of
`
`business at 2040 Bedford Road, Suite 100, Bedford, Texas 76021.
`
`2.
`
`Defendant Google LLC (“Google”) is a Delaware limited liability company that
`
`maintains an established places of business at 100 Congress Ave., 901 E. Fifth St. and 500 W.
`
`Second St., Austin, Texas 78701, among other locations. Google may be served with process
`
`through its registered agent, the Corporation Service Company dba CSC – Lawyers Incorporating
`
`Service Company at 211 East 7th Street, Suite 620, Austin, Texas 78701. Google is registered to
`
`do business in the State of Texas and has been since at least November 17, 2006.
`
` 1
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 2 of 51
`
`
`
`JURISDICTION AND VENUE
`
`3.
`
`This is an action arising under the patent laws of the United States, 35 U.S.C. § 271.
`
`This Court has subject matter jurisdiction under 28 U.S.C. §§ 1331 and 1338(a).
`
`4.
`
`Venue is proper in this judicial district under 28 U.S.C. § 1400(b) because
`
`Defendant has committed acts of infringement and has a regular and established place of business
`
`in this District as set forth below.
`
`5.
`
`Google maintains an office in Austin, Texas, and touts that it has “proudly called
`
`Texas home for more than a decade with offices in Austin and Dallas, and a data center in
`
`Midlothian—a $600M investment.” (See https://economicimpact.google.com/state/tx/). Google
`
`employs over 1,700 Texans full-time (the majority in Austin), has connected with 1.43 million
`
`Texas businesses, and touts $26.45 billion in economic activity within Texas. (Id.)
`
`6.
`
`Google’s Austin office opened in 2007 and now has more than 1,500 employees in
`
`Central Texas, including 800 engineering employees based in Austin and the broader Austin area.
`
`(See https:// www. statesman. com/story/business/2021/08/13/austin-google-exec-companys-
`
`future-really-bright-in-city-tx/5488231001/). Google is excited to see the company’s Austin
`
`operations grow into one of Google’s largest hubs, as it will shortly occupy all of a new 35-story
`
`tower being built at 601 W. Second St. in Austin. (Id.) The 750,000 square feet of office space at
`
`601 W. Second St. will expand on the 550,000 square feet already owned by Google in downtown
`
`Austin at its three locations: 100 Congress Ave., 901 E. Fifth St. and 500 W. Second St. (see
`
`https://www.kvue.com/article/money/economy/boomtown-2040/google-austin-texas-real-estate-
`
`report/269-2ce6e60e-e8c3-46f5-aca6-864175e67950).
`
` 2
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 3 of 51
`
`
`
`7.
`
`In addition to its downtown Austin office space, Google operates a Google Fiber
`
`Space at 701 S. Lamar Blvd in Austin. Via its website and this Google Fiber Space, Google markets
`
`and sells Google Fiber throughout the Austin area (see https:// fiber. google. com/cities/austin/).
`
`In addition to Internet service, Google Fiber includes Google Fiber Phone, which is powered by
`
`the accused Google Voice. (See https: //fiber.google.com/phone/ (“Google Fiber Phone is just like
`
`a typical home phone, except your phone service is delivered over the Internet, and it’s powered
`
`by Google Voice. Use your current home phone number, choose a new one, or use your existing
`
`Google Voice number.”)) Google’s established places of business in this District are thus
`
`marketing, selling, and deriving revenue directly from the functionality accused of infringement
`
`in this case.
`
`8.
`
`In addition to the approximately 1,500 employees, including 800 engineers,
`
`employed in Austin, Google’s Careers website currently lists 442 jobs available in the Austin area
`
`related to both Google and Google Fiber (see https://careers.google.com/jobs/results/?company=
`
`Google&company=Google%20Fiber&distance=50&hl=en&location=Austin,%20TX,
`
`%20USA&q=). Upon information and belief, Google’s in-house legal department also has
`
`substantial presence in Austin, Texas. Google’s Careers website includes a job posting for
`
`“Litigation Counsel, Patent Litigation” with the option to work in Austin. (See id.)
`
`9.
`
`In addition to its Austin presence, Google also maintains a $600 million data center
`
`in Midlothian, Texas. (https:// www. google. com/about/datacenters/locations/midlothian/).
`
`According to Google, its data centers “are really the engine of the internet” and that data “in Texas
`
`or the surrounding areas” will be processed through the Midlothian data center. (https: //www.
`
`dallasnews.com/business/real-estate/2019/06/14/google-s-massive-600m-data-center-takes-
`
` 3
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 4 of 51
`
`
`
`shape-in-ellis-county-as-tech-giant-ups-texas-presence/). Google’s 375-acre data center
`
`in
`
`Midlothian is approximately 70 miles from the Waco courthouse.
`
`10.
`
`This Court has personal jurisdiction over Google. Google has continuous and
`
`systematic business contacts with the State of Texas (as set forth in ¶¶ 5–9 above, which are
`
`incorporated herein). In addition, Google conducts its business extensively throughout Texas and
`
`derives substantial revenue from Texas, by shipping, distributing, offering for sale, selling, and
`
`advertising (including the provision of an interactive web page) its products and/or services in the
`
`State of Texas and the Western District of Texas. Google has purposefully and voluntarily placed
`
`in the stream of commerce one or more products and/or services that practice the Asserted Patents
`
`(as set forth in ¶¶ 24–28 below) with the intention and expectation that they will be purchased and
`
`used by consumers in the Western District of Texas.
`
`BACKGROUND
`
`The Flyp Inventions
`
`11.
`
`Long before the COVID-19 pandemic, the explosion of Internet-connected mobile
`
`devices changed the way many, even most, in the United States communicate with their family,
`
`friends, and work colleagues. Throughout the 2010s and continuing into the 2020s, personal and
`
`professional communication coalesced around the smartphone. While some chose to segregate
`
`their personal and professional communication with multiple devices, that solution was both
`
`financially and physically cumbersome. Rather, a technological need arose to segregate such
`
`communications within a single device and to manage multiple numbers in a clean, centralized
`
`environment. And within this field, there was a particular need for a device that would maintain
`
`caller identification (“caller ID”) and properly identify a call as originating from the secondary
`
` 4
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 5 of 51
`
`
`
`phone number of the caller with multiple numbers, rather than a conference line number or a
`
`randomly generated number.
`
`12.
`
`Flyp invented a technological solution that fulfills this technological need in a
`
`particular, inventive way. Flyp owns a patent portfolio directed to innovations that claim a
`
`particular way of setting up and connecting telephone calls, and delivering information related to
`
`such telephone calls using an Internet Protocol (IP) or other data channel, while delivering the
`
`voice portion of the call in accordance with telecom voice channel delivery standards. As opposed
`
`to the standard mobile phone that is connected to a single phone number, Flyp’s patented systems
`
`and methods enable a particular way for mobile-phone users to create and own multiple phone
`
`numbers on a single mobile device while maintaining the integrity of caller-identification
`
`functions. Thus, from a single mobile phone utilizing Flyp’s app (and patented methods), users
`
`can add new phone numbers and control various streams of outbound and inbound calls to those
`
`numbers. Users can select the area code of their choice for local calling in the United States and
`
`create alternative and dedicated numbers for business, social activities, shopping, dating, and any
`
`other aspect of life.
`
`13.
`
`This invention is unlike and constituted a technological advance over other methods
`
`for using alternative phone numbers. Many of those methods utilized call forwarding or call
`
`conferencing solutions—rather than connecting the call at the switch. In these solutions, caller ID
`
`was not maintained, and the recipient caller ID would appear to the one receiving the call as a
`
`conference line number or randomly generated number—rather than properly identifying the call
`
`as originating from the secondary phone number of the caller with multiple numbers. The need for
`
`alternative numbers that identified calls as originating from the secondary phone number was a
`
` 5
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 6 of 51
`
`
`
`long-felt need and unique technological problem that the invention provides a particular way of
`
`solving, thereby improving the functionality of the phones beyond the mere advantages of
`
`implementing phone technology using computers. This is also a feature that cannot be
`
`implemented manually.
`
`14.
`
`This need to segregate communications within a single device and to manage
`
`multiple numbers in a centralized environment was reinforced during the sudden and rapid shift to
`
`a “work from anywhere” ethos brought on by the COVID-19 pandemic. The pandemic reinforced
`
`the essential role that the Internet and our Internet-connected mobile devices occupy in day-to-day
`
`work and life. That is particularly true regarding cloud-based telephone service. Indeed, amid the
`
`COVID-19 crisis, the global market for cloud telephony service, estimated at $13.5 billion in the
`
`year 2020, is projected to reach a revised size of $40 billion by 2027, growing at a compound
`
`annual growth rate of 16.8% over the period 2020–2027. (See “$13.5 Billion Worldwide Cloud
`
`Telephony Service Industry to 2027 – Impact of COVID-19 on the Market,” Research & Markets,
`
`https://www.globenewswire.com/en/news-release/2020/10/14/2108292/28124/en/13-5-Billion-
`
`Worldwide-Cloud-Telephony-Service-Industry-to-2027-Impact-of-COVID-19-on-the-Market.
`
`html).
`
`15.
`
`But for rampant infringement of its patented technology, Flyp would be well-
`
`positioned to play a role in this growing market. Simply put, Flyp has developed a unique and
`
`inventive technology that enables a particular way for a user to gain access to an additional,
`
`alternative phone number on his or her mobile devices—as opposed to the single carrier-assigned
`
`number on a mobile device. Second numbers, or even third, fourth, or fifth numbers, allow users
`
`to manage different work streams on a single device in a manner that was not well understood,
`
` 6
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 7 of 51
`
`
`
`conventional, or routine within the prior art, as evidenced by the limited number of references
`
`originally cited during examination of the Asserted Patents by the United States Patent and
`
`Trademark Office.
`
`Google Voice
`
`16.
`
`In addition to its more well-known web-searching and hosting services, Google
`
`operates Google Voice. Google Voice is an application published by Google for iOS and Android
`
`that allows a user to add a second phone number to his or her smartphone.
`
`17.
`
`Although Google Voice was launched in 2009, it was revamped significantly in
`
`2017 (after the priority date of the Asserted Patents).
`
`18.
`
`At the time of its 2009 launch, Google Voice was described by the industry as a
`
`call-forwarding solution—“Google Voice is an internet-based service that gives your contacts one
`
`voice number and forwards it to multiple phones.” (See https://www.lifewire.com/what-is-google-
`
`voice-1616888.). For inbound calls, Google Voice did not display any indication of what number
`
`was receiving the call. (See Google Voice – Taking calls, March 11, 2009, available at
`
`https://www.youtube.com/watch?v=vDo6hkgoYXo). In addition, Google Voice
`
`leveraged
`
`multiple third-party providers for call routing using Google Voice. (See https: //www. fcc. gov/
`
`wcb/archives/googleletter.pdf).
`
`19.
`
`From 2012 until early 2017, Google made no major revisions to Google Voice.
`
`Instead, according to industry observers, Google let Google Voice languish in disrepair for five
`
`years.
`
`(See
`
`https://gizmodo.com/five-years-later-google-finally-remembers-google-voice-
`
`1791532022 (“Unfortunately, over the years, Google let the nifty little voice service fall into
`
` 7
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 8 of 51
`
`
`
`relative disrepair—until today, that is. For the first time in five—yes, five—years, Google Voice
`
`is getting a major UI update.”)
`
`20.
`
`The patent application that led to Flyp’s first patent (the ’770 Patent) published in
`
`January 2015,1 and months later in March 2015 Flyp’s mobile application launched on the Google
`
`Play Store. Not long after these events, Google Ventures—Google’s venture capital fund—asked
`
`for the opportunity to learn more about Flyp under the auspices of offering funding. The Google
`
`Ventures team included key contributors to Google Voice: Craig Walker, Wesley Chan, and Rich
`
`Miner, the co-founder of Android and a purported co-inventor of Google Voice technology.2
`
`21.
`
`Rich Miner3 arranged a meeting with Peter Rinfret from Flyp for November 12,
`
`2015. To prepare for that meeting, Mr. Miner conferred with Google Voice’s co-founder, Craig
`
`Walker. At the meeting between Google Ventures and Flyp, Mr. Rinfret provided a presentation
`
`to Mr. Miner about Flyp and its technologies, including discussing the flaws and shortcomings in
`
`Google’s existing Google Voice product along with the proprietary technologies that Flyp had
`
`developed to overcome them. The presentation also referenced Flyp’s efforts to seek patent
`
`protection for its technology in three separate instances.4 Mr. Rinfret explained to Mr. Miner that
`
`Flyp had sought patent protection for its proprietary technologies and provided an overview of
`
`
`
`1 U.S. Patent App. No. 2015/0024718 was published on January 22, 2015.
`2 See https://googleblog.blogspot.com/2009/03/googles-newest-venture.html; https://om.co/gigaom/ google-voice-co-
`founder-quits-joins-google-ventures; https://www.wsj.com/articles/BL-VCDB-5994; https://www.theverge.com/
`2014/3/6/5474902/rich-miner-google-ventures-profile; and U.S. Patent Publ. 2011/0026468.
`3 In November 2015, Mr. Miner was an employee of Google Ventures. Prior to the filing of this lawsuit, however, Mr.
`Miner became an employee of Google LLC in March 2021.
`4 See Ex. A (Flyp Presentation as maintained in Google’s files and produced as GOOG-FLYP-00004073 (Confidential
`– Attorneys Eyes Only)), at 15, 16, and 17 (Filed Under Seal).
`
` 8
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 9 of 51
`
`
`
`Flyp’s pending patent applications. In addition, the presentation showed and Mr. Rinfret explained
`
`that Flyp’s pending patent applications had been accepted into the United States Patent and
`
`Trademark Office’s “Patent Prosecution Highway (PPH) – Fast Track Examination of
`
`Applications,” and would be considered on an expedited basis. Mr. Miner asked for, and received,
`
`a copy of the presentation from Mr. Rinfret.
`
`22.
`
`After the meeting, Mr. Miner conferred with the Google Ventures team about what
`
`he had learned from Mr. Rinfret. Google Ventures did not offer funding to Flyp. Shortly thereafter,
`
`however, Google incorporated many of the solutions that Mr. Rinfret discussed during the meeting
`
`into its own Google Voice product. On information and belief, Mr. Miner and the Google Voice
`
`team took no affirmative steps to monitor Flyp’s patent filings (including Flyp’s fast-tracked patent
`
`application) following that meeting. On information and belief, Google was nonetheless aware of
`
`each of Flyp’s patents shortly after each issued as they were analyzed and incorporated into
`
`patents.google.com, a website owned and operated by Google LLC. Prior to the filing of this
`
`lawsuit, each asserted patent was available on patents.google.com.
`
`23.
`
`A little more than one year later, in January 2017, Google updated Google Voice.
`
`In addition to user-interface improvement, the revised Google Voice employed new call
`
`mechanisms that infringe Flyp’s Asserted Patents, including new methods for outbound and
`
`inbound call routing.
`
`THE ASSERTED PATENTS
`
`24.
`
`U.S. Patent No. 9,667,770, entitled “Telephone Network System and Method” (the
`
`“’770 Patent”), was duly and legally issued to inventors Ivan Zhidov, Peter Rinfret, and Sunir
`
` 9
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 10 of 51
`
`
`
`Kochhar on May 30, 2017. Flyp owns by assignment the entire right, title, and interest in the ʼ770
`
`Patent and is entitled to sue for past and future infringement.
`
`25.
`
`U.S. Patent No. 10,051,105, entitled “Telephone Network System and Method”
`
`(the “’105 Patent”), was duly and legally issued to inventors Ivan Zhidov, Peter Rinfret, and Sunir
`
`Kochhar on August 14, 2018. Flyp owns by assignment the entire right, title, and interest in the
`
`ʼ105 Patent and is entitled to sue for past and future infringement.
`
`26.
`
`U.S. Patent No. 10,334,094, entitled “Telephone Network System and Method”
`
`(the “’094 Patent”), was duly and legally issued to inventors Ivan Zhidov, Peter Rinfret, and Sunir
`
`Kochhar on June 25, 2019. Flyp owns by assignment the entire right, title, and interest in the ʼ094
`
`Patent and is entitled to sue for past and future infringement.
`
`27.
`
`U.S. Patent No. 11,012,554, entitled “Telephone Network System and Metho[d]”
`
`(the “’554 Patent”), was duly and legally issued to inventors Ivan Zhidov, Peter Rinfret, and Sunir
`
`Kochhar on May 18, 2021. Flyp owns by assignment the entire right, title, and interest in the ʼ554
`
`Patent and is entitled to sue for past and future infringement.
`
`28.
`
`U.S. Patent No. 11,218,585, entitled “Telephone Network System and Method”
`
`(the “’585 Patent”), was duly and legally issued to inventors Ivan Zhidov, Peter Rinfret, and Sunir
`
`Kochhar on January 4, 2022. Flyp owns by assignment the entire right, title, and interest in the
`
`ʼ585 Patent and is entitled to sue for past and future infringement.
`
`Count I: Claim for Patent Infringement of the ʼ770 Patent
`
`29.
`
`Flyp repeats and realleges the allegations in paragraphs 1–28 as if fully set forth
`
`herein.
`
`
`
`
`
`10
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 11 of 51
`
`
`
`30.
`
`Google has infringed the ’770 Patent by making, using, selling, offering for sale, or
`
`importing into the United States, or by intending that others make, use, import into, offer for sale,
`
`or sell in the United States, products and/or methods covered by one or more claims of the ’770
`
`Patent, including, but not limited to, Google’s app-based telephone feature known as Google Voice
`
`(including Google Voice and Google Telephony Platform, on server and client sides). In addition,
`
`since at least the filing of Flyp’s Original Complaint in this action, Google has contributed to the
`
`infringement of and/or induced infringement of the ’770 Patent by making, using, selling, offering
`
`for sale, or importing into the United States, or by intending that others make, use, import into,
`
`offer for sale, or sell in the United States, products and/or methods covered by one or more claims
`
`of the ’770 Patent, including, but not limited to, Google Voice (including Google Voice and
`
`Google Telephony Platform, on server and client sides).
`
`31.
`
`Google Voice infringes at least claims 1–6 of the ’770 Patent. Google makes, uses,
`
`sells, offers for sale, imports, exports, supplies, or distributes Google Voice within the United
`
`States and thus directly infringes the ʼ770 Patent.
`
`32.
`
`Upon information and belief, Google indirectly infringes the ʼ770 Patent by
`
`(1) inducing infringement by others, such as resellers, partners, and end-user customers in this
`
`District and throughout the United States with knowledge or willful blindness that the induced acts
`
`would constitute infringement, and (2) contributing to infringement by others, such as resellers,
`
`partners, and end-user customers. Upon information and belief, direct infringement is (1) the result
`
`of activities performed by resellers, partners, and end-user customers of Google Voice, who
`
`perform each step of the claimed invention as directed by Google, or (2) the result of activities
`
`performed by resellers, partners, and end-user customers of Google Voice—including placing
`
`
`
`
`11
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 12 of 51
`
`
`
`outbound calls and receiving inbound calls—in a normal and customary way that infringes the
`
`ʼ770 Patent, that has no substantial non-infringing uses, that is known by Google, and that
`
`constitutes a material part of the invention of the ’770 Patent.
`
`33.
`
`Google had knowledge of Flyp and its patent applications, including the fast-track
`
`application that was eventually issued as the ’770 Patent, at least as early as November 12, 2015.
`
`On that date, Mr. Miner met with Flyp to discuss Flyp’s technology, business, and patent filings.
`
`In response to a request from Mr. Miner, Flyp transmitted a copy of the presentation given to Mr.
`
`Miner at that meeting days later on November 16, 2015, which included a summary of Flyp’s
`
`technology and disclosed that Flyp had filed patent applications related to its technology. Mr.
`
`Miner rejoined Google as an employee in March 2021. On information and belief, Mr. Miner and
`
`the Google Voice team took no steps to monitor Flyp’s patent filings following Mr. Miner’s
`
`meeting with Flyp.
`
`34.
`
`Nonetheless, Google itself was aware of the ’770 Patent shortly after its issuance.
`
`On information and belief, the ’770 Patent was analyzed and incorporated into patents.google.com
`
`shortly after its issuance. For years prior to the filing of this lawsuit, the ’770 Patent was available
`
`on patents.google.com, a website owned and operated by Google LLC.
`
`35.
`
`At the very least, Google received actual notice of the ʼ770 Patent at least as early
`
`as the filing of the Original Complaint in this action.
`
`36.
`
`By engaging in the conduct described herein, Google has injured Flyp and is thus
`
`liable for infringement of the ’770 Patent, pursuant to 35 U.S.C. § 271. Google has committed
`
`these acts of infringement without license or authorization.
`
`
`
`12
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 13 of 51
`
`
`
`37.
`
`As a result of Google’s infringement of the ’770 Patent, Flyp has suffered monetary
`
`damages and is entitled to a monetary judgment in an amount adequate to compensate for Google’s
`
`past infringement, together with interests and costs. In addition, Google’s infringement is causing
`
`irreparable harm and monetary damage to Flyp and will continue to do so unless and until Google
`
`is enjoined by the Court.
`
`38.
`
`Google’s infringement of the ’770 Patent has been and continues to be deliberate
`
`and willful, and, therefore, this is an exceptional case warranting an award of enhanced damages
`
`for up to three times the actual damages awarded and attorneys’ fees to Flyp pursuant to 35 U.S.C.
`
`§§ 284–285.
`
`39.
`
`Google Voice provides a method of providing telephone service comprising:
`
`associating a secondary telephone number with a primary telephone number in at least one
`
`computer memory device, the primary telephone number being assigned to a handset, including as
`
`demonstrated in the exemplary text below:
`
`
`
`
`
`
`
`13
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 14 of 51
`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 14 of 51
`
`Sign up for Voice and get your number
`
`1. On your computer, go to voice.google.com B .
`
`2. Sign in to your Google Account.
`
`3. After reviewing the Terms of Service and Privacy Policy, tap Continue.
`
`4. Search by city or area code for a number. Voice doesn't offer 1-800 numbers.
`
`*
`
`|f there aren't any numbers available in the area you want, try somewhere nearby.
`
`5. Next to the numberyou want, click Select. Follow the instructions.
`
`After setting up Voice, you can link another phone number. Learn more about setting up phones.
`
`Change your device's number
`Important: Google Voice uses your linked numberto makecalls if an internet connection isnt
`available. If you didn't link your device's number during sign-up, you can link it later.
`
`before linking. 6. Tap Save.
`
`
`
`
`
`1. Open the Voice app t®.
`
`2. In the top left, tap Menu = > Settings.
`
`3. Under “Account,' tap Devices and numbers.
`
`4. Under "This device," tap Change device number.
`
`5. Choose one of these options:
`
`* Your device's number:Voice links to your mobile device.
`* No number: Voiceisn't linked to a device number.
`
`* New linked number: Voice links to a new numberyou enter. Google Voice verifies the number
`
`
`
`14
`14
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 15 of 51
`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 15 of 51
`
`
`
`Google Cloud
`
`Google has been in telephonyfor 12 years
`
`jf
`
`Vy)
`
`ja
`
`Calls via Google Cloud
`100+ countries, 100+ carriers, 100+ peering points, 188
`minutes/yr, 308 messages/yr.
`
`Already know andlove Voice
`Since 2009,milllionsof users haverelied on Voice to
`keepin touchwith friends,
`family, and colleagues.
`
`|aa Paar
`
`behind the scenesvoiceis part of a
`GS
`muchlarger telephony platform that
`
`#GoogleCloudNext
`Using Google Voice to managebusinesslines
`1,188 views * Nov5, 2021
`
`=+ SAVE
`
`25
`
`GD vIslikE > SHARE
`
`S DOWNLOAD
`
`=+ SAVE
`
`Google Workspace @
`640K subscribers
`
`Google Cloud
`
`aa
`Even moreavailability
`
`—
`Urea Reyna aa
`
`easily allowyou to switch to the most
`reliable connection.
`
`whenyou add anotherlinked phone number
`like that of your mobile device
`
`ci
`
`Pm
`
`Plo
`
`4)
`
`315/1405
`
`Using Google Voice to managebusinesslines
`1,188 views + Nov 5, 2021
`
`Google Workspace @
`640K subscribers
`
`25
`
`GD DISLIKE
`
`A> SHARE
`
`sb DOWNLOAD
`
`
`
`15
`15
`
`
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 16 of 51
`
`
`
`
`
`40.
`
`Google Voice provides a method of providing telephone service comprising:
`
`acquiring first digital information from the handset over at least one data channel, the first digital
`
`information indicating primary call processing rules for handling calls directed to the primary
`
`telephone number, and storing the primary call processing rules in the at least one computer
`
`memory device, and acquiring second digital information from the handset over the at least one
`
`data channel, the second digital information indicating secondary call processing rules for handling
`
`calls directed to the secondary telephone number, and storing the secondary call processing rules
`
`in the at least one computer memory device, including as demonstrated in the exemplary text
`
`below:
`
`
`
`
`
`16
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 17 of 51
`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 17 of 51
`
`Set up your phone to make & receive Google
`Voice calls
`Your Google Voice numberlets you make andreceive calls at voice.google.com or on the Google Voice app.
`You canalso link phone numbers you wantto forward calls to if you don't want to answerwith Google Voice.
`Whencall forwardingis set up,calls to your Google Voice numberwill ring yourlinked phones.
`
`
`
`Add a numberto place & receivecalls & texts
`1. Open the Voice app &®.
`2. In the topleft, tap Menu = > Settings.
`3. Under "Account," tap Devices and numbers.
`4. Tap New linked number.
`5. Enter the phone numbertolink.
`6. Google Voice sends youa verification code.
`* To verify a mobile number: Tap Send code. Google Voice sends the codein a text message.
`* To verify a landline number: Tap Verify by phone > Call. Google Voice calls the phone numberand gives
`the code.
`
`4. Under "My devices," turn off any devices you don't wantto get calls on.
`
`7. Enter the code > tap Verify.
`
`Tips:
`
`+ You canlink up to 6 numbers.You can't link a numberthat's already linked to a Google Voice number.
`* Calls to your Google Voice numberalso ring on your linked number.
`
`Change whereyou get calls
`
`1. Open the Voice app &®.
`
`2. In the topleft, tap Menu = > Settings.
`
`3. Under"Calls," tap Incomingcalls.
`
`
`
`
`
`
`
`17
`17
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 18 of 51
`
`
`
`
`
`41.
`
`Google Voice provides a method of providing telephone service comprising:
`
`receiving an incoming call over at least one voice channel at a switch, the switch being associated
`
`with a bridge telephone number such that calls directed to the bridge telephone number are
`
`automatically routed to the switch, the incoming call being directed to a handset-associated
`
`telephone number, the handset-associated telephone number being the primary telephone number
`
`or the secondary telephone number, including as demonstrated in the exemplary text above.
`
`42.
`
`Google Voice provides a method of providing telephone service comprising: based
`
`on the primary call processing rules or the secondary call processing rules provides transmitting
`
`pre-call information to the handset over the at least one data channel the pre-call information
`
`including the bridge telephone number and the handset-associated telephone number, such that the
`
`handset is capable of displaying the handset-associated telephone number to a user and, based on
`
`
`
`18
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 19 of 51
`
`
`
`user input, accepting the incoming call by connecting with the switch over the at least one voice
`
`channel using the bridge telephone number, including as demonstrated in the exemplary text above
`
`and below:
`
`
`
`
`
`Count II: Claim for Patent Infringement of the ʼ105 Patent
`
`43.
`
`Flyp repeats and realleges the allegations in paragraphs 1–42 as if fully set forth
`
`herein.
`
`44.
`
`Google has infringed the ’105 Patent by making, using, selling, offering for sale, or
`
`importing into the United States, or by intending that others make, use, import into, offer for sale,
`
`or sell in the United States, products and/or methods covered by one or more claims of the ’105
`
`Patent, including, but not limited to, Google’s app-based telephone feature known as Google Voice
`
`(including Google Voice and Google Telephony Platform, on server and client sides). In addition,
`
`
`
`19
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 105 Filed 03/29/23 Page 20 of 51
`
`
`
`since at least the filing of Flyp’s Original Complaint in this action, Google has contributed to the
`
`infringement of and/or induced infringement of the ’105 Patent by making, using, selling, offering
`
`for sale, or importing into the United States, or by intending that others make, use, import into,
`
`offer for sale, or sell in the United States, products and/or methods covered by one or more claims
`
`of the ’105 Patent, including, but not limited to, Google Voice (including Google Voice and
`
`Google Telephony Platform, on server and client sides).
`
`45.
`
`Google Voice infringes at least claims 1–11 of the ’105 Patent. Google makes, uses,
`
`sells, offers for sale, imports, exports, supplies, or distributes Google Voice within the United
`
`States and thus directly infringes the ʼ105 Patent.
`
`46.
`
`Upon information and belief, Google indirectly infringes the ʼ105 Patent by
`
`(1) inducing infringement by others, such as resellers, partners, and end-user customers in this
`
`District and throughout the United States with knowledge or willful blindness that the induced acts
`
`would constitute infringement, and (2) contributing to infringement by others, such as resellers,
`
`partners, and end-user customers. Upon information and belief, direct infringement is (1) the result
`
`of activities performed by resellers, partners, and end-user customers of Google Voice, who
`
`perform each step of the claimed invention as directed by Google, or (2) the result of activities
`
`performed by resellers, partners, and end-user customers of Google Voice—including placing of
`
`outbound calls and the receiving of inbound calls—in a normal and cu

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