throbber
Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 1 of 19
`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 1 of 19
`
`Exhibit 1
`Exhibit 1
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 2 of 19
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`CIVIL ACTION NO. 6:21-cv-665-ADA
`
`
`
`VOIP-PAL.COM, INC.
`
`Plaintiff,
`
`v.
`
`META PLATFORMS, INC., and
`WHATSAPP, INC.
`
`Defendants.
`
`
`VOIP-PAL.COM, INC.
`
`
`Plaintiff,
`
`
`CIVIL ACTION NO. 6:21-cv-667-ADA
`
`
`
`CIVIL ACTION NO. 6:21-cv-668-ADA
`
`
`
`v.
`
`
`GOOGLE LLC,
`
`
`Defendant.
`
`
`
`VOIP-PAL.COM, INC.
`Plaintiff,
`
`v.
`AMAZON.COM, INC.;
`AMAZON.COM SERVICES LLC; and
`AMAZON WEB SERVICES, INC.,
`Defendants.
`
`
`
`
`
`
`
`
`1
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 3 of 19
`
`
`CIVIL ACTION NO. 6:21-cv-672-ADA
`
`
`
`CIVIL ACTION NO. 6:21-cv-674-ADA
`
`
`
`VOIP-PAL.COM, INC.
`
`Plaintiff,
`
`v.
`
`VERIZON COMMUNICATIONS, INC.;
`CELLCO PARTNERSHIP d/b/a VERIZON
`WIRELESS;
`VERIZON SERVICES, CORP.; and
`VERIZON BUSINESS NETWORK
`SERVICES, INC.,
`
`Defendants.
`
`
`VOIP-PAL.COM, INC.
`
`Plaintiff,
`
`v.
`
`T-MOBILE US, INC.; and
`T-MOBILE USA, INC.
`
`Defendants.
`
`
`
`PLAINTIFF VOIP-PAL.COM, INC.’S PROPOSED CLAIM CONSTRUCTIONS
`
`Under the parties’ Proposed Scheduling Order (Case No. 6:21-cv-665-ADA, Dkt. No. 30),
`Plaintiff VoIP-Pal.com, Inc. (“VoIP-Pal”) provides its proposed claim constructions, to the extent
`that any of these claim terms require construction. These are the terms and phrases among the
`asserted claims that VoIP-Pal contends might be in need of construction. By listing any given term
`or phrase, VoIP-Pal does not agree that that term or phrase actually should be construed, only that it
`might deserve construction. Otherwise, VoIP-Pal presently contends that the claims receive their
`plain and ordinary meaning as understood by a person having ordinary skill in the art in the field of
`the invention, in light of the intrinsic record. VoIP-Pal reserves the right to contend that no particular
`explanatory construction is needed for these or any other terms or phrases. VoIP-Pal specifically
`reserves the right to submit proposed jury instructions that present no specific explanation of any
`
`
`
`
`
`2
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 4 of 19
`
`given term or phrase, but that ask the jury to apply the plain meaning as understood by a person of
`ordinary skill. Likewise, VoIP-Pal reserves the right to contend that additional terms or phrases
`might be in need of construction, such as after review and consideration of Defendants’ disclosure.
`VoIP-Pal also reserves the right to contend that additional terms or phrases identified by Defendants
`in the related cases might be in need of construction.
`To the extent the claim terms, phrases, or clauses set forth in this disclosure include particular
`terms, phrases, or clauses appropriate to be construed separately, such terms, phrases, or clauses are
`deemed to be part of this disclosed list. Similarly, to the extent that it is appropriate to construe
`terms, phrases, or clauses listed in this disclosure in the context of additional claim language, such
`additional language is deemed to be part of this disclosure.
`VoIP-Pal’s investigation is ongoing. Accordingly, VoIP-Pal reserves the right to supplement
`and/or amend its disclosure, including but not limited to identifying additional terms in response to
`Defendants’ disclosure and proposing additional or alternative constructions, as discovery proceeds,
`and as additional information becomes available.
`
`
`Term
`
`Proposed Construction
`
`Patent(s)/Claim(s)
`
`“Access server”
`
`Plain and ordinary meaning
`
`“Access code request message” Plain and ordinary meaning
`
`“Access code reply message”
`
`Plain and ordinary meaning
`
`’234 patent claims 1, 11, 19, 20,
`21, 25, 28
`
`’721 patent claims 1, 16, 20, 34,
`38, 39, 46, 49, 50
`
`’234 patent claims 1, 10, 11, 19,
`20, 21, 28, 40, 46, 62, 72
`
`’721 patent claims 1, 16, 20, 34,
`38, 39, 49, 50, 51, 77, 103, 104
`
`’234 patent claims 1, 11, 19, 20,
`43, 45, 46, 61, 62, 75
`
`’721 patent claims 1, 16, 20, 34,
`38, 46, 49, 50, 51, 77, 103, 124
`
`
`
`
`
`3
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 5 of 19
`
`“routing controller”
`
`One or more devices that
`produce messages to setup
`communication between callers
`and callees
`
`“roaming”
`
`Plain and ordinary meaning
`
`“callee identifier”
`
`Plain and ordinary meaning
`
`“access code”
`
`Plain and ordinary meaning
`
`“pool of access codes”
`
`Plain and ordinary meaning
`
`’234 patent claims 10, 19, 32,
`62, 64
`
`’721 patent claims 15, 16, 34,
`49, 51, 77, 103, 109, 110, 124
`
`’234 patent, claims 1, 19, 28,
`30, 46, 62
`
`’721 patent, claims 34, 49
`
`’234 patent, claims 1, 11, 20,
`25, 28, 30, 46, 62
`
`’234 patent, claims 1, 10, 11,
`19, 20, 21, 25, 28, 30, 31, 32,
`33, 38, 40, 43, 45, 46, 47, 48,
`54, 61, 62, 64, 65, 70, 72, 75
`
`’721 patent, claims 1, 14, 16,
`20, 34, 38, 39, 46, 49, 50, 51,
`57, 63, 77, 103, 104, 109, 110,
`124, 130, 135, 138, 139, 140
`
`’234 patent, claims 1, 11, 20,
`30, 38, 46, 54, 57, 62, 70
`
`’721 patent, claims 63, 109
`
`“local call”
`
`Plain and ordinary meaning
`
`’234 patent, claims 1, 11, 20
`
`“receiv[ing] an access code
`reply message from the access
`server”
`
`“initiat[ing] a call [with the
`mobile telephone]
`using said access code to
`identify the callee”
`
`“means for receiving, from a
`user of the mobile telephone, a
`callee identifier”
`
`
`
`
`
`Plain and ordinary meaning
`
`’234 patent, claims 1, 11, 20
`
`’721 patent, claims 1, 20, 38
`
`Plain and ordinary meaning
`
`’234 patent, claims 1, 11, 20
`
`’234 patent, claim 11
`
`Function: “receiving, from a
`user of the mobile telephone, a
`callee identifier”
`
`Corresponding structure:
`Mobile wireless device 12
`having a microprocessor 52
`4
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 6 of 19
`
`’234 patent, claim 11
`
`’721 patent, claim 20
`
`’234 patent, claim 11
`
`’721 patent, claim 20
`
`programmed to implement the
`algorithm illustrated in FIG. 3,
`which includes block 104
`labeled “Obtain callee
`identified.” The telephone 12
`includes an I/O port (56) and
`dialing function (62, 64). See
`FIG. 2.
`
`Function: “transmitting an
`access code request message to
`an access server”
`
`Corresponding structure:
`Mobile wireless device 12
`having a microprocessor 52
`programmed to implement the
`algorithm illustrated in FIG. 3,
`which includes block 106
`labeled “Transmit access code
`request message to access
`server.” The wireless device 12
`includes I/O port(s) 56 capable
`of acting as an interface to
`external networks (70, 72, 15,
`16). See FIG. 2.
`
`Function: “receiving an access
`code reply message from the
`access server in response to
`[said/the] access code request
`message”
`
`Corresponding structure:
`Mobile wireless device 12
`having a microprocessor 52
`programmed to implement the
`algorithm illustrated in FIG. 3,
`which includes block 130
`labeled “Receive access code
`reply message from access
`server.” The wireless device 12
`includes I/O port(s) 56 capable
`of acting as an interface to
`external networks (70, 72, 15,
`16). See FIG. 2.
`5
`
`“means for transmitting an
`access code request message to
`an access server”
`
`“means for receiving an access
`code reply message from the
`access server in response to
`[said/the] access code request
`message”
`
`
`
`
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 7 of 19
`
`
`
`Function: “initiating a call
`using said access code to
`identify the callee”
`
`Corresponding structure:
`Mobile wireless device 12
`having a microprocessor 52
`programmed to implement the
`algorithm illustrated in FIG. 3,
`which includes block 149
`labeled “Initiate voice/video
`call using access code.” The
`wireless device 12 includes I/O
`port(s) 56 capable of acting as
`an interface to external
`networks (70, 72, 15, 16). See
`FIG. 2.
`
`Function: “receiving from the
`mobile telephone [said/an]
`access code request message”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7,
`which includes block 196
`labeled “Obtain an access
`code.” The access server 14
`includes one or more I/O ports
`156 which can provide
`interfaces to external networks
`162 or internal components 164
`of the communication network.
`See FIG. 6.
`
`Function: “communicating
`with [said/the] routing
`controller to obtain from
`[said/the] routing controller
`[said/the] access code”
`
`Corresponding structure: See
`6
`
`’234 patent, claim 11
`
`’234 patent, claims 19, 46
`
`’234 patent, claim 19
`
`’721 patent, claim 34
`
`“means for initiating a call
`using said access code to
`identify the callee”
`
`“means for receiving from the
`mobile telephone [said/an]
`access code request message”
`
`“means for communicating with
`[said/the] routing controller to
`obtain from [said/the] routing
`controller [said/the] access
`code”
`
`
`
`
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 8 of 19
`
`“means for transmitting
`[said/an/the] access code reply
`message including [said/the]
`access code to the [mobile
`telephone/wireless apparatus]”
`
`’234 patent, claims 19, 46
`
`’721 patent, claims 34, 77
`
`FIGS. 6 and 7. Access server
`14 having a microprocessor
`152, performs a process
`including “Obtain an access
`code” 196. Routing Controller
`30 has a microprocessor 232 in
`communication with I/O
`interface 236 and access server
`interface 242 for
`communicating with access
`server 14, as illustrated in FIG.
`8. In some embodiments, the
`routing controller is part of or
`integrated with the access
`server; see col. 17 lines 19-30.
`See also col. 14, lines 30-54.
`
`Function: “transmitting
`[said/an/the] access code reply
`message including [said/the]
`access code to the [mobile
`telephone/wireless apparatus]”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7,
`which includes block 198
`labeled “Transmit access code
`reply message.” The access
`server 14 includes one or more
`I/O ports 156 providing
`interfaces to external networks
`162 or internal components 164
`of the communication network.
`See FIG. 6. In some
`embodiments, the routing
`controller is part of or
`integrated with the access
`server; see col. 17 lines 19-30.
`
`“transmit[ting] [a/an/said]
`[access code] reply message
`including [said/the] access code
`to the [mobile
`
`Plain and ordinary meaning
`
`’234 patent, claims 19, 30, 46
`
`’721 patent, claims 77, 103, 130
`
`
`
`
`
`7
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 9 of 19
`
`telephone/wireless device]”
`“access code . . . useable by the
`mobile telephone to initiate a
`call to the callee”
`“means for producing an access
`code”
`
`“means for selecting said access
`code from a pool of access
`codes”
`
`
`
`
`
`Plain and ordinary meaning
`
`’234 patent, claims 30, 46, 62
`
`’234 patent, claim 46
`
`’234 patent, claim 46
`
`Function: “producing an access
`code”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7,
`which includes block 196
`labeled “Obtain an access
`code.” The access server 14
`includes one or more I/O ports
`156 which can provide an
`interface for communicating
`with a routing controller (164).
`See FIG. 6. In some
`embodiments, the routing
`controller is part of or
`integrated with the access
`server; see col. 17 lines 19-30.
`Various embodiments of a
`routing controller 30 producing
`an access code are disclosed at
`col. 15, line 7 to col. 22 line 60,
`for example.
`
`Function: “selecting said
`access code from a pool of
`access codes”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7
`or an equivalent algorithm,
`which includes block 196
`labeled “Obtain an access
`code.” Alternatively, various
`embodiments of a routing
`controller 30 producing an
`access code are disclosed at col.
`8
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 10 of 19
`
`15, line 7 to col. 22 line 60, for
`example. In some
`embodiments, the routing
`controller is part of or
`integrated with the access
`server; see col. 17 lines 19-30.
`
`Plain and ordinary meaning
`
`Plain and ordinary meaning
`
`“cause an access code reply
`message including said access
`code to be transmitted to the
`mobile telephone”
`“destination node identifier”
`
`“location identifier identifying a
`geographical location”
`
`Plain and ordinary meaning
`
`“gateway”
`
`Plain and ordinary meaning
`
`’234 patent, claim 62
`
`’721 patent, claims 1, 20, 38,
`50, 51, 77, 103, 130, 136
`
`’721 patent, claims 1, 20, 38,
`50, 51, 77, 103
`
`’721 patent, claims 1, 20, 38,
`51, 77, 103, 133
`
`“caus[ing] the wireless device
`to use the access code . . . to
`[initiate/establish]
`communications
`[from/between] the wireless
`device [to/and] the destination
`node”
`“means for receiving from a
`user of the wireless apparatus a
`destination node identifier”
`
`“means for causing the wireless
`apparatus to establish
`communications with the
`
`
`
`
`
`Plain and ordinary meaning
`
`’721 patent, claims 1, 50
`
`Function: “receiving from a
`user of the wireless apparatus a
`destination node identifier”
`
`Corresponding structure:
`Mobile wireless apparatus 12
`having a microprocessor 52
`programmed to implement the
`algorithm illustrated in FIG. 3,
`which includes block 104
`labeled “Obtain callee
`identifier.” The apparatus 12
`includes an I/O port (56) and
`dialing function (62, 64). See
`FIG. 2.
`
`Function: “causing the wireless
`apparatus to establish
`communications with the
`9
`
`’721 patent, claim 20
`
`’721 patent, claim 20
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 11 of 19
`
`’721 patent, claim 20
`
`’721 patent, claims 34, 77
`
`destination node through the
`communications channel
`identified by the access code”
`
`“causing the wireless apparatus
`to establish communications
`with the destination node
`through the communications
`channel identified by the access
`code”
`“means for receiving from the
`wireless [apparatus/device]
`[the/an] access code request
`message”
`
`
`
`
`
`destination node through the
`communications channel
`identified by the access code”
`
`Corresponding structure:
`Mobile telephone 12 having a
`microprocessor 52 programmed
`to implement the algorithm
`illustrated in FIG. 3, which
`includes block 149 labeled
`“Initiate voice/video call using
`access code.” The apparatus 12
`includes an I/O port (56) for
`communication. See FIG. 2.
`
`Plain and ordinary meaning
`
`Function: “receiving from the
`wireless [apparatus/device]
`[the/an] access code request
`message”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7,
`labeled “Receive Access Code
`Request Message 192”, which
`includes block 196 labeled
`“Obtain an access code.” The
`access server 14 includes one or
`more I/O ports 156 which can
`provide interfaces to external
`networks 162 and/or internal
`components of the
`communication network (164).
`See FIG. 6. In some
`embodiments, the routing
`controller is part of or
`integrated with the access
`server; see col. 17 lines 19-30.
`10
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 12 of 19
`
`
`Plain and ordinary meaning
`
`’721 patent, claim 38
`
`Plain and ordinary meaning
`
`’721 patent, claim 50
`
`Plain and ordinary meaning
`
`’721 patent, claims 51, 77, 103,
`130, 138
`
`Plain and ordinary meaning
`
`’721 patent, claim 51
`
`Plain and ordinary meaning
`
`’721 patent, claim 51
`
`Function: “causing a routing
`controller to produce an access
`code”
`
`Corresponding structure:
`Access server 14 having a
`microprocessor 152
`programmed to implement the
`algorithm illustrated in FIG. 7,
`which includes block 196
`labeled “Obtain an access
`code.” In some embodiments,
`the routing controller is part of
`or integrated with the access
`server; see col. 17 lines 19-30.
`
`Plain and ordinary meaning
`
`’721 patent, claim 77
`
`’721 patent, claims 77, 103, 130
`
`“initiate communications from
`the wireless apparatus . . . using
`the access code”
`“cause the wireless device to
`receive an access code reply
`message comprising an access
`code”
`“access code is useable by the
`wireless device to initiate [the]
`communications with the
`destination node through the
`[communications channel/IP
`network communication
`device]”
`“transmitting, to the wireless
`device, an access code reply
`message including the access
`code”
`“cause the wireless device to
`use the access code to initiate
`communications with the
`destination node”
`“means for causing a routing
`controller to produce an access
`code”
`
`“[access code/second Internet
`Protocol (IP) address] . . . is
`used by the wireless device to
`initiate communications”
`
`
`Dated: February 22, 2022
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`11
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 13 of 19
`
`
`
`
`
`
`
`/s/Lewis E. Hudnell, III
`Lewis E. Hudnell, III
`lewis@hudnelllaw.com
`Nicolas S. Gikkas
`nick@gikkaslaw.com
`Hudnell Law Group P.C.
`800 W. El Camino Real Suite 180
`Mountain View, California 94040
`T: 650.564.3698
`F: 347.772.3034
`
`ATTORNEYS FOR PLAINTIFF
`VOIP-PAL.COM, INC.
`
`
`
`
`
`
`
`
`12
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 14 of 19
`
`
`
`CERTIFICATE OF SERVICE
`
`I certify that I have caused PLAINTIFF VOIP-PAL.COM, INC.’S PROPOSED CLAIM
`CONSTRUCTIONS to be served on February 22, 2022 via electronic mail upon the following
`counsel of record:
`
`
`
`
`
`13
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 15 of 19
`
`
`
`Michael E. Jones
`State Bar No. 10929400
`mikejones@potterminton.com
`POTTER MINTON
`110 N. College Ave., Suite 500
`Tyler, Texas 75702
`Tel: (903) 597-8311
`Fax: (903) 593-0846 (Facsimile)
`
`Ellisen Shelton Turner
`ellisen.turner@kirkland.com
`Joshua Popik Glucoft
`josh.glucoft@kirkland.com
`KIRKLAND & ELLIS LLP
`2049 Century Park East, Suite 3700
`Los Angeles, CA 90067
`Tel: (310) 552-4220
`Fax: (310) 552-5900
`
`Kristina R. Cary
`Massachusetts BBO No. 688759
`kristina.cary@kirkland.com
`KIRKLAND & ELLIS LLP
`200 Clarendon Street
`Boston, MA 02116
`Tel: (617) 385-7500
`Fax: (617) 385-7501
`
`ATTORNEYS FOR DEFENDANTS
`FACEBOOK, INC. AND WHATSAPP,
`INC.
`
`
`
`
`
`14
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 16 of 19
`
`Paige Arnette Amstutz
`State Bar No.: 00796136
`pamstutz@scottdoug.com
`SCOTT, DOUGLASS & MCCONNICO,
`LLP
`303 Colorado Street, Suite 2400
`Austin, TX 78701
`Telephone: (512) 495-6300
`Facsimile: (512) 495-6399
`
`Robert W. Unikel
`robertunikel@paulhastings.com
`Matthew Lind
`matthewlind@paulhastings.com
`PAUL HASTINGS LLP
`71 South Wacker Drive, 45th Floor
`Chicago, IL 60606
`Telephone: (312) 499-6000
`Facsimile: (312) 499-6100
`
`Robert R. Laurenzi
`robertlaurenzi@paulhastings.com
`PAUL HASTINGS LLP
`200 Park Avenue
`New York, NY 10166
`Telephone: (212) 318-6000
`Facsimile: (212) 319-4090
`
`Ariell N. Bratton
`ariellbratton@paulhastings.com
`Cole D. Malmberg
`colemalmberg@paulhastings.com
`PAUL HASTINGS LLP
`4747 Executive Drive, 12th Floor
`San Diego, CA 92121
`Telephone: (858) 458-3000
`Facsimile: (858) 458-3005
`
`ATTORNEYS FOR DEFENDANT
`GOOGLE LLC
`
`
`
`15
`
`
`
`
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 17 of 19
`
`M. Craig Tyler, Bar No. 00794762
`CTyler@perkinscoie.com
`Perkins Coie LLP
`500 W 2nd St, Suite 1900
`Austin, TX 78701-4687
`Tel. No. 737.256.6113
`Fax No. 737.256.6300
`
`Daniel T. Shvodian
`dshvodian@perkinscoie.com
`Perkins Coie LLP
`3150 Porter Drive
`Palo Alto, CA 94304-1212
`Tel No. 650.838.4300
`Fax No. 650.838.4350
`
`Attorneys for Defendants
`AMAZON.COM, INC.;
`AMAZON.COM, SERVICES LLC;
`AND
`AMAZON WEB SERVICES, INC.
`
`
`
`16
`
`
`
`
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 18 of 19
`
`J. Mark Mann
`State Bar No. 12926150
`mark@themannfirm.com
`MANN | TINDEL | THOMPSON
`201 E. Howard Street
`Henderson, TX 75654
`(903) 657-8540
`(903) 657-6003 (fax)
`
`Frank C. Cimino, Jr.
`Megan S. Woodworth
`VENABLE LLP
`600 Massachusetts Avenue, NW
`Washington, DC 20001
`(202) 344-4569
`FCCimino@Venable.com
`MSWoodworth@Venable.com
`
`William Hector
`VENABLE LLP
`101 California Street
`Suite 3800
`San Francisco, CA 94111
`(415) 653-3750
`WAHector@Venable.com
`
`ATTORNEYS FOR DEFENDANTS
`VERIZON COMMUNICATIONS
`INC., CELLCO PARTNERSHIP
`D/B/A VERIZON WIRELESS,
`VERIZON SERVICES CORP., AND
`VERIZON BUSINESS NETWORK
`SERVICES LLC
`
`
`
`17
`
`
`
`
`
`

`

`Case 3:21-cv-09773-JD Document 58-2 Filed 02/23/23 Page 19 of 19
`
`
`
`Amanda Tessar, Colorado Bar #33173
`ATessar@perkinscoie.com
`PERKINS COIE LLP
`1900 Sixteenth Street, Suite 1400
`Denver, Colorado 80202-5255
`
`Martin E. Gilmore
`MGilmore@perkinscoie.com
`PERKINS COIE LLP
`500 W 2nd St 1900
`Austin, Texas 78701
`
`Melissa Richards Smith
`Texas Bar No. 24001351
`melissa@gillamsmithlaw.com
`GILLAM AND SMITH, L.L.P.
`303 South Washington Avenue
`Marshall, TX 75670
`(903)934-8450
`Fax: (903)934-9257
`
`ATTORNEYS FOR DEFENDANTS T-
`MOBILE US, INC. AND T MOBILE
`USA, INC.
`
`
`
`
`By: /s/Lewis E. Hudnell, III
`Lewis E. Hudnell, III
`
`
`18
`
`
`
`
`
`
`
`
`
`
`

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