Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 1 of 42 PageID #: 1135
`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 1 of 42 PageID #: 1135
`
`
`
`
`EXHIBIT A
`EXHIBIT A
`
`
`
`
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 2 of 42 PageID #: 1136
`
`Case No. 2:17-cv-00513-JRG
`(Lead Case)
`
`JURY TRIAL DEMANDED
`
`Case No. 2:17-CV-00517-JRG
`(Consolidated Case)
`
`JURY TRIAL DEMANDED
`
`AGIS SOFTWARE DEVELOPMENT
`LLC,
`
`
`
`v.
`
`HUAWEI DEVICE USA INC., HUAWEI
`DEVICE CO., LTD. AND HUAWEI
`DEVICE (DONGGUAN) CO., LTD.,
`
`
`
`Plaintiff,
`
`Defendants.
`
`
`
`
`
`
`
`v.
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`
`AGIS SOFTWARE DEVELOPMENT,
`LLC,
`
`
`
`
`
`ZTE CORPORATION, ZTE (USA) INC.,
`AND ZTE (TX), INC.,
`
`
`
`
`Plaintiff,
`
`Defendants.
`
`
`
`
`ZTE (USA) INC.’S AND ZTE (TX) INC.’S OBJECTIONS AND RESPONSES TO
`PLAINTIFF’S FIRST SET OF COMMON INTERROGATORIES (NOS. 1-10)
`
`Pursuant to Rules 26 and 33 of the Federal Rules of Civil Procedure, Defendants ZTE
`
`(USA) Inc. and ZTE (TX) Inc. (“ZTA” and “ZTX” respectively, and collectively “ZTE”)1
`
`hereby serve their objections and responses to Plaintiff AGIS Software Development LLC
`
`(“Plaintiff’s”) First Set of Common Interrogatories (1-10) to ZTE.
`
`
`1 Defendant ZTE Corporation (“ZTE Corp.”) has not yet been served or appeared in this matter.
`
`1
`
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 3 of 42 PageID #: 1137
`
`These responses are made solely for the purposes of Civil Action no. 2:17-cv-00517
`
`captioned above (referred to herein as the “Action”)2. The following responses are based on
`
`ZTE’s present state of recollection, knowledge, and belief. The responses are at all time subject
`
`to additional or different information that discovery may disclose and, while based on the present
`
`state of recollection, are subject to such refreshing of recollection and such knowledge or facts as
`
`may result from further investigation by ZTE or its attorneys and/or further discovery from
`
`Plaintiff and/or third parties. ZTE reserves the right to supplement these responses.
`
`ZTE’s objections and responses are made without in any way waiving or intending to
`
`waive, but to the contrary, are intended to preserve:
`
`1.
`
`All questions as to the competency, relevancy, materiality, privilege, and
`
`admissibility as evidence for any purpose of the response or subject matter thereof, in this Action
`
`or any subsequent proceeding associated with this Action or any other matter;
`
`2.
`
`The right to object on any ground to the use of said responses, or the subject
`
`matter thereof, in any subsequent proceeding with this Action or any other action; and
`
`3.
`
`The right to object on any ground at any time to the other requests or other
`
`discovery procedures involving or relating to the subject matter of these interrogatories.
`
`GENERAL OBJECTIONS
`
`
`
`The following general objections apply to each and every interrogatory contained in
`
`Plaintiff’s interrogatories, including its definitions and instructions, and each of the general
`
`objections is incorporated by reference into the specific objections to each interrogatory,
`
`regardless of whether the specific objections overlap or repeat the general objection.
`
`1.
`
`ZTE objects to Plaintiff’s definitions and instructions to the extent they are
`
`unreasonably vague, overly broad, repetitious, unduly burdensome, or seek to impose any
`
`2 Unless indicated otherwise, all docket citations will reference the ZTE case.
`
`2
`
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 4 of 42 PageID #: 1138
`
`obligations beyond those imposed by the applicable rules and law, including the Federal Rules of
`
`Civil Procedure, the Local Rules of this Court, the Docket Control Order, and the Discovery
`
`Order.3
`
`2.
`
`ZTE objects to the interrogatories to the extent that they seek documents and
`
`information subject to (a) attorney-client privilege, (b) work product immunity, (c) joint defense
`
`privilege, (d) common interest privilege, or (e) any other applicable privilege, immunity, or
`
`protection. ZTE does not intend to provide such information or produce such privileged or
`
`protected documents or things, and the inadvertent production of such is not to be deemed a
`
`waiver of any privilege. ZTE expressly reserves the right to object to the introduction at trial or
`
`any other use of such documents or things that may be inadvertently disclosed. An objection
`
`based on the attorney-client privilege and/or the work product doctrine shall not be construed as
`
`a representation that information called for in the interrogatory exists or existed. Such objections
`
`indicate only that the interrogatories are of such a scope as to embrace subject matter protected
`
`by the attorney-client privilege, the work product doctrine, or other protection or privilege.
`
`3.
`
`ZTE objects to the interrogatories to the extent that they seek documents,
`
`information, and things (a) not relevant to the subject matter of this investigation, (b) not
`
`proportional to the needs of the case, considering the importance of the issues at stake in the
`
`action, the amount in controversy, the parties’ relative access to relevant information, the
`
`parties’ resources, the importance of the discovery in resolving the issues, and whether the
`
`burden or expense of the proposed discovery outweighs its likely benefit, or (c) otherwise not
`
`within the scope of relevant discovery.
`
`4.
`
`ZTE objects to the interrogatories to the extent that they seek to impose an
`
`
`3 ZTE will follow the Docket Control Order and Discovery Orders entered in 2:17-cv-00514
`(Dkt. Nos. 38 and 39) until new ones are entered in the lead case 2:17-cv-00513.
`
`3
`
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 5 of 42 PageID #: 1139
`
`improper or undue burden on ZTE, or duties and responsibilities greater than those imposed by
`
`the Federal Rules of Civil Procedure, and the Local Rules. ZTE objects to the interrogatories to
`
`the extent they seek information or documents and things that do not exist or are beyond ZTE’s
`
`possession, custody, or control. ZTE further objects to the interrogatories and to the definitions
`
`and instructions therein to the extent they seek documents, information, and things from
`
`corporate parents, subsidiaries, affiliates, divisions or joint ventures that are not within the
`
`possession, custody or control of ZTE.
`
`5.
`
`ZTE objects to the interrogatories to the extent they seek information
`
`or documents and things that are subject to a claim of confidentiality from a third
`
`party.
`
`6.
`
`ZTE’s responses or failure to object to any of Plaintiff’s Definitions or
`
`Instructions are not intended to be, and shall not be, construed as admissions as to the meaning
`
`of words or phrases at issue in the action, and shall have no binding effect on ZTE in this or in
`
`any other proceeding.
`
`7.
`
`ZTE’s responses and objections are for discovery purposes only, and are not
`
`to be construed as limiting or reflecting Plaintiff’s positions in this case regarding claim
`
`construction.
`
`8.
`
`ZTE’s agreement to respond to these interrogatories shall not be deemed as
`
`an admission regarding the relevance of the interrogatory nor is it intended to waive any right
`
`to object the admissibility of such at trial.
`
`9.
`
`ZTE have not yet completed their investigation, collection of information,
`
`discovery, and analysis relating to this action. The following responses are based on
`
`information known and available to ZTE at this time. Discovery in this litigation is ongoing.
`
`
`
`
`4
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 6 of 42 PageID #: 1140
`
`ZTE reserve the right to amend, supplement, or otherwise change their response to these
`
`interrogatories should any additional information become available to them. ZTE also reserve
`
`the right to produce additional evidence at trial.
`
`10.
`
`ZTE, i.e. ZTA and ZTX, object to Plaintiff’s definition of “ZTE,” “You,”
`
`“Your,” and “Defendants.” As addressed above ZTE Corp. has not yet been served or appeared
`
`in this matter, and is thus not a party subject to 30(b)(6) discovery. ZTE further objects to
`
`Plaintiff’s definition of “ZTE,” “You,” “Your,” and “Defendants” on the ground that these
`
`definitions (i) are vague, overly broad, and unduly burdensome; (ii) seek information that is not
`
`relevant to any claims or defenses of any party and/or is not reasonably calculated to lead to the
`
`discovery of admissible evidence with respect to any such claim or defense; (iii) seek
`
`information that ZTE cannot reasonably be expected to be aware of or have knowledge of; and
`
`(iv) to the extent they seek information from persons or legal entities that ZTE neither employs
`
`not controls.
`
`11.
`
`ZTE objects to Plaintiff’s definition of “ZTE Accused Products” to the extent it
`
`is directed at devices beyond the scope of the Complaint in this action and beyond the time
`
`period relevant to this case. ZTE objects to any discovery beyond the scope of any right
`
`Plaintiff may have to recover damages for infringement. ZTE further objects to Plaintiff’s
`
`definition of “ZTE Accused Products” on the grounds that it is vague, overly broad, and unduly
`
`burdensome, especially to the extent that the definition is unlimited in time and encompasses
`
`systems or products not made, used, sold, offered for sale, or imported by ZTE. ZTE further
`
`objects to the definition to the extent that it includes products alleged of infringing patents that
`
`are not asserted in this case. ZTE also objects to the definition to the extent it attempts to
`
`characterize the asserted patents or ay patent claim terms. Claim construction and expert
`
`
`
`
`5
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 7 of 42 PageID #: 1141
`
`discovery has not yet occurred in this case, and ZTE reserves its rights to provide expert
`
`testimony and claim construction positions in accordance with this Court’s Local Patent Rules,
`
`Docket Control Order, and any other applicable rules or orders. ZTE also objects to this
`
`definition to the extent it implies that any ZTE system or product practices any claim of any
`
`Asserted Patents; ZTE specifically denies any alleged acts of infringement. ZTE also objects to
`
`this definition to the extent it implies that any accused ZTE products are interchangeable or
`
`representative of any others for the purposes of this case. In responding to Plaintiff’s
`
`Interrogatories, ZTE will limit its responses to products and systems identified in Plaintiff’s
`
`Complaint (Dkt. No. 1), Amended Complaint (Dkt. No. 32), and Infringement Contentions,
`
`including any court-approved supplements or amendments thereto, and reasonably related
`
`products, without conceding that any such products are representative or share any similar
`
`characteristics for the purposes of Plaintiff’s burden of establishing infringement.
`
`12.
`
`ZTE objects to Plaintiff’s definition of “This Action.” ZTE are not Defendants
`
`in AGIS Software Development LLC v. Huawei Device USA Inc., et al., 2:17-cv-00513-JRG
`
`(E.D. Tex.).
`
`13.
`
`ZTE objects to Plaintiff’s definition of “documents” as vague, overly broad, and
`
`unduly burdensome. ZTE further objects to this definition to the extent it exceeds the scope of
`
`the parties’ agreed Discovery or E-Discovery Orders.4
`
`14.
`
`ZTE objects to Plaintiff’s definition of “communications” as vague, overly
`
`broad, and unduly burdensome. ZTE further objects to this definition to the extent it exceeds
`
`the scope of the parties’ agreed Discovery or E-Discovery Orders.
`
`
`4 To be proposed respectively on April 9, 2018 and April 23, 2018. See AGIS Software
`Development LLC v. Huawei Device USA Inc., et al., 2:17-cv-00513-JRG (Dkt. No. 101) (E.D.
`Tex.).
`
`
`
`6
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 8 of 42 PageID #: 1142
`
`15.
`
`ZTE objects to Plaintiff’s definition of “things” as vague, overly broad, and
`
`unduly burdensome. ZTE further objects to this definition to the extent it exceeds the scope of
`
`the parties’ agreed Discovery or E-Discovery Orders.
`
`16.
`
`ZTE objects to Plaintiff’s definition of “persons” as vague, overly broad, and
`
`unduly burdensome, and to the extent it seeks information outside of ZTE’s possession,
`
`custody, or control and not proportional to the needs of the case. ZTE further objects to this
`
`definition to the extent it exceeds the scope of the parties’ agreed Discovery or E-Discovery
`
`Orders.
`
`17.
`
`ZTE objects to Plaintiff’s definition of “identify” as vague, overly broad, and
`
`unduly burdensome, and to the extent it seeks information outside of ZTE’s possession,
`
`custody, or control and not proportional to the needs of the case. Where applicable, ZTE will
`
`provide detail sufficient to ascertain the identity of the person, place, or thing sought, if that
`
`detail is within ZTE’s possession, custody, or control.
`
`18.
`
`ZTE objects to Plaintiff’s definition of “describe” as vague, overly broad, and
`
`unduly burdensome, and to the extent it seeks information outside of ZTE’s possession,
`
`custody, or control and not proportional to the needs of the case, especially as it seeks the
`
`identity of “all” persons or documents.
`
`19.
`
`ZTE objects to the definition of the terms “relate,” “reflecting,” and
`
`“concerning” as being vague, overly broad, unduly burdensome, and as seeking information
`
`not in ZTE’s possession, custody, or control. ZTE will identify individuals by name, and
`
`documents by Bates number, where applicable.
`
`
`
`
`
`
`
`
`
`
`7
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 9 of 42 PageID #: 1143
`
`SPECIFIC OBJECTIONS AND RESPONSES
`
`
`
`INTERROGATORY NO. 1
`
`
`
`Identify all ZTE Accused Products sold to customers and made available for purchase
`by customers in the United States from January 2011 to the present, providing at least the
`following information: (i) the internal and external name(s) and model number(s) of the ZTE
`Accused Products; (ii) each Entity to whom the ZTE Accused Products were offered for sale or
`sold, and the supplier of each ZTE Accused Product and components thereof, as well as an
`identification of which components are supplied by each supplier.
`
`RESPONSE TO INTERROGATORY NO. 1:
`
`
`In addition to the General Objections stated above, ZTE objects to this interrogatory on
`
`the basis that it includes at least four (4) distinct interrogatories. ZTE further objects to this
`
`interrogatory to the extent it is vague, ambiguous, overly broad, and unduly burdensome because
`
`the terms “all” and “each,” as used in this interrogatory, are not clear and potentially encompass
`
`an unreasonably board range of topics or calls for information that is not relevant or proportional
`
`to the needs of this case. ZTE additionally objects to this interrogatory to the extent it calls for a
`
`legal conclusion. Further, ZTE objects to this interrogatory because the terms “purchase,”
`
`“internal,” “external,” “model,” “offered,” “sale,” “sold,” “supplier,” and “components” are
`
`vague, ambiguous, overly broad, and undefined. ZTE also expressly incorporates its General
`
`Objection to Plaintiff’s definition of “Accused Products.” ZTE also objects to this interrogatory to
`
`the extent it seeks information which ZTE is under a duty to third parties not to disclose. ZTE
`
`further objects to this interrogatory to the extent it requests that ZTE provide customer
`
`information that is not relevant or proportional to the needs of this case; ZTE will not provide
`
`personal information about each of its customers.
`
`Subject to the foregoing general and specific objections, ZTE responds as follows:
`
`
`
`
`8
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 10 of 42 PageID #: 1144
`
`ZTE produced documents that detail technical aspects of the Accused Products and their
`
`operation, and directs Plaintiff to those documents at the following bates numbers pursuant to
`
`Rule 33(d):
`
`ZTE-AGIS-00000001 - ZTE-AGIS-00000011; ZTE-AGIS-00000012 - ZTE-AGIS-00000015;
`ZTE-AGIS-00000016 - ZTE-AGIS-00000020; ZTE-AGIS-00000021 - ZTE-AGIS-00000026;
`ZTE-AGIS-00000027 - ZTE-AGIS-00000032; ZTE-AGIS-00000033 - ZTE-AGIS-00000035;
`ZTE-AGIS-00000036 - ZTE-AGIS-00000038; ZTE-AGIS-00000039 - ZTE-AGIS-00000042;
`ZTE-AGIS-00000043 - ZTE-AGIS-00000045; ZTE-AGIS-00000046 - ZTE-AGIS-00000194;
`ZTE-AGIS-00000195 - ZTE-AGIS-00000266; ZTE-AGIS-00000267 - ZTE-AGIS-00000351;
`ZTE-AGIS-00000352 - ZTE-AGIS-00000364; ZTE-AGIS-00000365 - ZTE-AGIS-00000367;
`ZTE-AGIS-00000368 - ZTE-AGIS-00000371; ZTE-AGIS-00000372 - ZTE-AGIS-00000373;
`ZTE-AGIS-00000374 - ZTE-AGIS-00000377; ZTE-AGIS-00000378 - ZTE-AGIS-00000419;
`ZTE-AGIS-00000420 - ZTE-AGIS-00000425; ZTE-AGIS-00000426 - ZTE-AGIS-00000428;
`ZTE-AGIS-00000429 - ZTE-AGIS-00000430; ZTE-AGIS-00000431 - ZTE-AGIS-00000435;
`ZTE-AGIS-00000436 - ZTE-AGIS-00000438; ZTE-AGIS-00000439 - ZTE-AGIS-00000441;
`ZTE-AGIS-00000442 - ZTE-AGIS-00000443; ZTE-AGIS-00000444 - ZTE-AGIS-00000444;
`ZTE-AGIS-00000445 - ZTE-AGIS-00000490; ZTE-AGIS-00000491 - ZTE-AGIS-00000493;
`ZTE-AGIS-00000494 - ZTE-AGIS-00000496; ZTE-AGIS-00000497 - ZTE-AGIS-00000498;
`ZTE-AGIS-00000499 - ZTE-AGIS-00000548; ZTE-AGIS-00000549 - ZTE-AGIS-00000682;
`ZTE-AGIS-00000683 - ZTE-AGIS-00000691; ZTE-AGIS-00000692 - ZTE-AGIS-00000694;
`ZTE-AGIS-00000695 - ZTE-AGIS-00000697; ZTE-AGIS-00000698 - ZTE-AGIS-00000701;
`ZTE-AGIS-00000702 - ZTE-AGIS-00000703; ZTE-AGIS-00000704 - ZTE-AGIS-00000709;
`ZTE-AGIS-00000710 - ZTE-AGIS-00000810; ZTE-AGIS-00000811 - ZTE-AGIS-00000813;
`ZTE-AGIS-00000814 - ZTE-AGIS-00000817; ZTE-AGIS-00000818 - ZTE-AGIS-00000820;
`ZTE-AGIS-00000821 - ZTE-AGIS-00000837; ZTE-AGIS-00000838 - ZTE-AGIS-00001010;
`ZTE-AGIS-00001011 - ZTE-AGIS-00001013; ZTE-AGIS-00001014 - ZTE-AGIS-00001016;
`ZTE-AGIS-00001017 - ZTE-AGIS-00001018; ZTE-AGIS-00001019 - ZTE-AGIS-00001022;
`ZTE-AGIS-00001023 - ZTE-AGIS-00001027; ZTE-AGIS-00001028 - ZTE-AGIS-00001031;
`ZTE-AGIS-00001032 - ZTE-AGIS-00001133; ZTE-AGIS-00001134 - ZTE-AGIS-00001183;
`ZTE-AGIS-00001184 - ZTE-AGIS-00001188; ZTE-AGIS-00001189 - ZTE-AGIS-00001192;
`ZTE-AGIS-00001193 - ZTE-AGIS-00001197; ZTE-AGIS-00001198 - ZTE-AGIS-00001372;
`ZTE-AGIS-00001373 - ZTE-AGIS-00001550; ZTE-AGIS-00001551 - ZTE-AGIS-00001556;
`ZTE-AGIS-00001557 - ZTE-AGIS-00001559; ZTE-AGIS-00001560 - ZTE-AGIS-00001562;
`ZTE-AGIS-00001563 - ZTE-AGIS-00001565; ZTE-AGIS-00001566 - ZTE-AGIS-00001567;
`ZTE-AGIS-00001568 - ZTE-AGIS-00001571; ZTE-AGIS-00001572 - ZTE-AGIS-00001581;
`ZTE-AGIS-00001582 - ZTE-AGIS-00001586; ZTE-AGIS-00001587 - ZTE-AGIS-00001590;
`ZTE-AGIS-00001591 - ZTE-AGIS-00001594; ZTE-AGIS-00001595 - ZTE-AGIS-00001771;
`ZTE-AGIS-00001772 - ZTE-AGIS-00001795; ZTE-AGIS-00001796 - ZTE-AGIS-00001851;
`ZTE-AGIS-00001852 - ZTE-AGIS-00001855; ZTE-AGIS-00001856 - ZTE-AGIS-00001861;
`ZTE-AGIS-00001862 - ZTE-AGIS-00001868; ZTE-AGIS-00001869 - ZTE-AGIS-00001880;
`ZTE-AGIS-00001881 - ZTE-AGIS-00002040; ZTE-AGIS-00002041 - ZTE-AGIS-00002044;
`ZTE-AGIS-00002045 - ZTE-AGIS-00002049; ZTE-AGIS-00002050 - ZTE-AGIS-00002056;
`ZTE-AGIS-00002057 - ZTE-AGIS-00002119; ZTE-AGIS-00002120 - ZTE-AGIS-00002129;
`
`
`
`
`9
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 11 of 42 PageID #: 1145
`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 11 of 42 PageID #: 1145
`
`ZTE-AGIS-00002130 - ZTE-AGIS-00002139; ZTE-AGIS-00002140 - ZTE-AGIS-00002155;
`ZTE-AGIS-00002130 - ZTE-AGIS-00002139; ZTE-AGIS-00002140 - ZTE-AGIS-00002155;
`ZTE-AGIS-00002156 - ZTE-AGIS-00002159; ZTE-AGIS-00002160 - ZTE-AGIS-00002161;
`ZTE-AGIS-00002156 - ZTE-AGIS-00002159; ZTE-AGIS-00002160 - ZTE-AGIS-00002161;
`ZTE-AGIS-00002162 - ZTE-AGIS-00002166; ZTE-AGIS-00002167 - ZTE-AGIS-00002318;
`ZTE-AGIS-00002162 - ZTE-AGIS-00002166; ZTE-AGIS-00002167 - ZTE-AGIS-00002318;
`ZTE-AGIS-00002319 - ZTE-AGIS-00002327; ZTE-AGIS-00002328 - ZTE-AGIS-00002333;
`ZTE-AGIS-00002319 - ZTE-AGIS-00002327; ZTE-AGIS-00002328 - ZTE-AGIS-00002333;
`ZTE-AGIS-00002334 - ZTE-AGIS-00002338; ZTE-AGIS-00002339 - ZTE-AGIS-00002342;
`ZTE-AGIS-00002334 - ZTE-AGIS-00002338; ZTE-AGIS-00002339 - ZTE-AGIS-00002342;
`ZTE-AGIS-00002343 - ZTE-AGIS-00002346; ZTE-AGIS-00002347 - ZTE-AGIS-00002519;
`ZTE-AGIS-00002343 - ZTE-AGIS-00002346; ZTE-AGIS-00002347 - ZTE-AGIS-00002519;
`ZTE-AGIS-00002520 - ZTE-AGIS-00002575; ZTE-AGIS-00002576 - ZTE-AGIS-00003093;
`ZTE-AGIS-00002520 - ZTE-AGIS-00002575; ZTE-AGIS-00002576 - ZTE-AGIS-00003093;
`ZTE-AGIS-00003094 - ZTE-AGIS-00003097; ZTE-AGIS-00003098 - ZTE-AGIS-00003253;
`ZTE-AGIS-00003094 - ZTE-AGIS-00003097; ZTE-AGIS-00003098 - ZTE-AGIS-00003253;
`ZTE-AGIS-00003254 - ZTE-AGIS-00003255; ZTE-AGIS-00003256 - ZTE-AGIS-00003311;
`ZTE-AGIS-00003254 - ZTE-AGIS-00003255; ZTE-AGIS-00003256 - ZTE-AGIS-00003311;
`ZTE-AGIS-00003312 - ZTE-AGIS-00003313; ZTE-AGIS-00003314 - ZTE-AGIS-00003317;
`ZTE-AGIS-00003312 - ZTE-AGIS-00003313; ZTE-AGIS-00003314 - ZTE-AGIS-00003317;
`ZTE-AGIS-00003318 - ZTE-AGIS-00003321; ZTE-AGIS-00003322 - ZTE-AGIS-00003325;
`ZTE-AGIS-00003318 - ZTE-AGIS-00003321; ZTE-AGIS-00003322 - ZTE-AGIS-00003325;
`ZTE-AGIS-00003326 - ZTE-AGIS-00003360; ZTE-AGIS-00003361 - ZTE-AGIS-00003531;
`ZTE-AGIS-00003326 - ZTE-AGIS-00003360; ZTE-AGIS-00003361 - ZTE-AGIS-00003531;
`ZTE-AGIS-00003532 - ZTE-AGIS-00003535; ZTE-AGIS-00003536 - ZTE-AGIS-00003538;
`ZTE-AGIS-00003532 - ZTE-AGIS-00003535; ZTE-AGIS-00003536 - ZTE-AGIS-00003538;
`ZTE-AGIS-00003539 - ZTE-AGIS-00003709; ZTE-AGIS-00003710 - ZTE-AGIS-00003725;
`ZTE-AGIS-00003539 - ZTE-AGIS-00003709; ZTE-AGIS-00003710 - ZTE-AGIS-00003725;
`ZTE-AGIS-00003726 - ZTE-AGIS-00003738; ZTE-AGIS-00003739 - ZTE-AGIS-00003912;
`ZTE-AGIS-00003726 - ZTE-AGIS-00003738; ZTE-AGIS-00003739 - ZTE-AGIS-00003912;
`ZTE-AGIS-00003913 - ZTE-AGIS-00004078; ZTE-AGIS-00004079 - ZTE-AGIS-00004080;
`ZTE-AGIS-00003913 - ZTE-AGIS-00004078; ZTE-AGIS-00004079 - ZTE-AGIS-00004080;
`ZTE-AGIS-00004081 - ZTE-AGIS-00004084; ZTE-AGIS-00004085 - ZTE-AGIS-00004089;
`ZTE-AGIS-00004081 - ZTE-AGIS-00004084; ZTE-AGIS-00004085 - ZTE-AGIS-00004089;
`ZTE-AGIS-00004090 - ZTE-AGIS-00004162; ZTE-AGIS-00004163 - ZTE-AGIS-00004264;
`ZTE-AGIS-00004090 - ZTE-AGIS-00004162; ZTE-AGIS-00004163 - ZTE-AGIS-00004264;
`ZTE-AGIS-00004265 - ZTE-AGIS-00004268; ZTE-AGIS-00004269 - ZTE-AGIS-00004274;
`ZTE-AGIS-00004265 - ZTE-AGIS-00004268; ZTE-AGIS-00004269 - ZTE-AGIS-00004274;
`ZTE-AGIS-00004275 - ZTE-AGIS-00004281; ZTE-AGIS-00004282 - ZTE-AGIS-00004286;
`ZTE-AGIS-00004275 - ZTE-AGIS-00004281; ZTE-AGIS-00004282 - ZTE-AGIS-00004286;
`ZTE-AGIS-00004287 - ZTE-AGIS-00004460; ZTE-AGIS-00004461 - ZTE-AGIS-00004464;
`ZTE-AGIS-00004287 - ZTE-AGIS-00004460; ZTE-AGIS-00004461 - ZTE-AGIS-00004464;
`ZTE-AGIS-00004465 - ZTE-AGIS-00004467; ZTE-AGIS-00004468 - ZTE-AGIS-00004471;
`ZTE-AGIS-00004465 - ZTE-AGIS-00004467; ZTE-AGIS-00004468 - ZTE-AGIS-00004471;
`ZTE-AGIS-00004472 - ZTE-AGIS-00004474; ZTE-AGIS-00004475 - ZTE-AGIS-00004626;
`ZTE-AGIS-00004472 - ZTE-AGIS-00004474; ZTE-AGIS-00004475 - ZTE-AGIS-00004626;
`ZTE-AGIS-00004627 - ZTE-AGIS-00004658; ZTE-AGIS-00004659 - ZTE-AGIS-00004820;
`ZTE-AGIS-00004627 - ZTE-AGIS-00004658; ZTE-AGIS-00004659 - ZTE-AGIS-00004820;
`ZTE-AGIS-00004821 - ZTE-AGIS-00004824; ZTE-AGIS-00004825 - ZTE-AGIS-00004829;
`ZTE-AGIS-00004821 - ZTE-AGIS-00004824; ZTE-AGIS-00004825 - ZTE-AGIS-00004829;
`ZTE-AGIS-00004830 - ZTE-AGIS-00004906; ZTE-AGIS-00004907 - ZTE-AGIS-00004910;
`ZTE-AGIS-00004830 - ZTE-AGIS-00004906; ZTE-AGIS-00004907 - ZTE-AGIS-00004910;
`ZTE-AGIS-00004911 - ZTE-AGIS-00004915; ZTE-AGIS-00004916 - ZTE-AGIS-00004920;
`ZTE-AGIS-00004911 - ZTE-AGIS-00004915; ZTE-AGIS-00004916 - ZTE-AGIS-00004920;
`ZTE-AGIS-00004921 - ZTE-AGIS-00004924; ZTE-AGIS-00004925 - ZTE-AGIS-00004925;
`ZTE-AGIS-00004921 - ZTE-AGIS-00004924; ZTE-AGIS-00004925 - ZTE-AGIS-00004925;
`ZTE-AGIS-00004926 - ZTE-AGIS-00004998; ZTE-AGIS-00004999 - ZTE-AGIS-00005004;
`ZTE-AGIS-00004926 - ZTE-AGIS-00004998; ZTE-AGIS-00004999 - ZTE-AGIS-00005004;
`ZTE-AGIS-00005005 - ZTE-AGIS-00005009; ZTE-AGIS-00005010 - ZTE-AGIS-00005013;
`ZTE-AGIS-OOOOSOOS - ZTE-AGIS-00005009; ZTE-AGIS-OOOOSOIO - ZTE-AGIS-00005013;
`ZTE-AGIS-00005014 - ZTE-AGIS-00005185; ZTE-AGIS-00005186 - ZTE-AGIS-00005270;
`ZTE-AGIS-00005014 - ZTE-AGIS-00005185; ZTE-AGIS-00005186 - ZTE-AGIS-00005270;
`ZTE-AGIS-00005271 - ZTE-AGIS-00005368; ZTE-AGIS-00005369 - ZTE-AGIS-00005470;
`ZTE-AGIS-00005271 - ZTE-AGIS-00005368; ZTE-AGIS-00005369 - ZTE-AGIS-00005470;
`ZTE-AGIS-00005471 - ZTE-AGIS-00005553; ZTE-AGIS-00005554 - ZTE-AGIS-00005644;
`ZTE-AGIS-00005471 - ZTE-AGIS-00005553; ZTE-AGIS-00005554 - ZTE-AGIS-00005644;
`ZTE-AGIS-00005645 - ZTE-AGIS-00005676; ZTE-AGIS-00005677 - ZTE-AGIS-00005683;
`ZTE-AGIS-00005645 - ZTE-AGIS-00005676; ZTE-AGIS-00005677 - ZTE-AGIS-00005683;
`ZTE-AGIS-00005684 - ZTE-AGIS-00005686; ZTE-AGIS-00005687 - ZTE-AGIS-00005688;
`ZTE-AGIS-00005684 - ZTE-AGIS-00005686; ZTE-AGIS-00005687 - ZTE-AGIS-00005688;
`ZTE-AGIS-00005689 - ZTE-AGIS-00005721; ZTE-AGIS-00005722 - ZTE-AGIS-00005722;
`ZTE-AGIS-00005689 - ZTE-AGIS-00005721; ZTE-AGIS-00005722 - ZTE-AGIS-00005722;
`ZTE-AGIS-00005723 - ZTE-AGIS-00005726; ZTE-AGIS-00005727 - ZTE-AGIS-00005731;
`ZTE-AGIS-00005723 - ZTE-AGIS-00005726; ZTE-AGIS-00005727 - ZTE-AGIS-00005731;
`ZTE-AGIS-00005732 - ZTE-AGIS-00005788; ZTE-AGIS-00005789 - ZTE-AGIS-00005791;
`ZTE-AGIS-00005732 - ZTE-AGIS-00005788; ZTE-AGIS-00005789 - ZTE-AGIS-00005791;
`ZTE-AGIS-00005792 - ZTE-AGIS-00005798; ZTE-AGIS-00005799 - ZTE-AGIS-00005801;
`ZTE-AGIS-00005792 - ZTE-AGIS-00005798; ZTE-AGIS-00005799 - ZTE-AGIS-00005801;
`ZTE-AGIS-00005802 - ZTE-AGIS-00005803; ZTE-AGIS-00005804 - ZTE-AGIS-00005805;
`ZTE-AGIS-00005802 - ZTE-AGIS-00005803; ZTE-AGIS-00005804 - ZTE-AGIS-00005805;
`ZTE-AGIS-00005806 - ZTE-AGIS-00005853; ZTE-AGIS-00005854 - ZTE-AGIS-00005856;
`ZTE-AGIS-00005806 - ZTE-AGIS-00005853; ZTE-AGIS-00005854 - ZTE-AGIS-00005856;
`ZTE-AGIS-00005857 - ZTE-AGIS-00005859; ZTE-AGIS-00005860 - ZTE-AGIS-00005862;
`ZTE-AGIS-00005857 - ZTE-AGIS-00005859; ZTE-AGIS-00005860 - ZTE-AGIS-00005862;
`ZTE-AGIS-00005863 - ZTE-AGIS-00005866; ZTE-AGIS-00005867 - ZTE-AGIS-00005868;
`ZTE-AGIS-00005863 - ZTE-AGIS-00005866; ZTE-AGIS-00005867 - ZTE-AGIS-00005868;
`ZTE-AGIS-00005869 - ZTE-AGIS-00005871; ZTE-AGIS-00005872 - ZTE-AGIS-00005874;
`ZTE-AGIS-00005869 - ZTE-AGIS-00005871; ZTE-AGIS-00005872 - ZTE-AGIS-00005874;
`ZTE-AGIS-00005875 - ZTE-AGIS-00005878; ZTE-AGIS-00005879 - ZTE-AGIS-00006028;
`ZTE-AGIS-00005875 - ZTE-AGIS-00005878; ZTE-AGIS-00005879 - ZTE-AGIS-00006028;
`ZTE-AGIS-00006029 - ZTE-AGIS-00006192; ZTE-AGIS-00006193 - ZTE-AGIS-00006198;
`ZTE-AGIS-00006029 - ZTE-AGIS-00006192; ZTE-AGIS-00006193 - ZTE-AGIS-00006198;
`
`
`
`
`10
`10
`
`

`

`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 12 of 42 PageID #: 1146
`Case 2:17-cv-00517-JRG Document 83-1 Filed 09/24/18 Page 12 of 42 PageID #: 1146
`
`ZTE-AGIS-00006199 - ZTE-AGIS-00006209; ZTE-AGIS-00006210 - ZTE-AGIS-00006212;
`ZTE-AGIS-00006199 - ZTE-AGIS-00006209; ZTE-AGIS-00006210 - ZTE-AGIS-00006212;
`ZTE-AGIS-00006213 - ZTE-AGIS-00006215; ZTE-AGIS-00006216 - ZTE-AGIS-00006217;
`ZTE-AGIS-00006213 - ZTE-AGIS-00006215; ZTE-AGIS-00006216 - ZTE-AGIS-00006217;
`ZTE-AGIS-00006218 - ZTE-AGIS-00006307; ZTE-AGIS-00006308 - ZTE-AGIS-00006397;
`ZTE-AGIS-00006218 - ZTE-AGIS-00006307; ZTE-AGIS-00006308 - ZTE-AGIS-00006397;
`ZTE-AGIS-00006398 - ZTE-AGIS-00006401; ZTE-AGIS-00006402 - ZTE-AGIS-00006406;
`ZTE-AGIS-00006398 - ZTE-AGIS-00006401; ZTE-AGIS-00006402 - ZTE-AGIS-00006406;
`ZTE-AGIS-00006407 - ZTE-AGIS-00006488; ZTE-AGIS-00006489 - ZTE-AGIS-00006492;
`ZTE-AGIS-00006407 - ZTE-AGIS-00006488; ZTE-AGIS-00006489 - ZTE-AGIS-00006492;
`ZTE-AGIS-00006493 - ZTE-AGIS-00006495; ZTE-AGIS-00006496 - ZTE-AGIS-00006577;
`ZTE-AGIS-00006493 - ZTE-AGIS-00006495; ZTE-AGIS-00006496 - ZTE-AGIS-00006577;
`ZTE-AGIS-00006578 - ZTE-AGIS-00006581; ZTE-AGIS-00006582 - ZTE-AGIS-00006585;
`ZTE-AGIS-00006578 - ZTE-AGIS-00006581; ZTE-AGIS-00006582 - ZTE-AGIS-00006585;
`ZTE-AGIS-00006586 - ZTE-AGIS-00006589; ZTE-AGIS-00006590 - ZTE-AGIS-00006688;
`ZTE-AGIS-00006586 - ZTE-AGIS-00006589; ZTE-AGIS-00006590 - ZTE-AGIS-00006688;
`ZTE-AGIS-00006689 - ZTE-AGIS-00006731; ZTE-AGIS-00006732 - ZTE-AGIS-00006735;
`ZTE-AGIS-00006689 - ZTE-AGIS-00006731; ZTE-AGIS-00006732 - ZTE-AGIS-00006735;
`ZTE-AGIS-00006736 - ZTE-AGIS-00006740; ZTE-AGIS-00006741 - ZTE-AGIS-00006744;
`ZTE-AGIS-00006736 - ZTE-AGIS-00006740; ZTE-AGIS-00006741 - ZTE-AGIS-00006744;
`ZTE-AGIS-00006745 - ZTE-AGIS-00006802; ZTE-AGIS-00006803 - ZTE-AGIS-00006805;
`ZTE-AGIS-00006745 - ZTE-AGIS-00006802; ZTE-AGIS-00006803 - ZTE-AGIS-00006805;
`ZTE-AGIS-00006806 - ZTE-AGIS-00006807; ZTE-AGIS-00006808 - ZTE-AGIS-00006811;
`ZTE-AGIS-00006806 - ZTE-AGIS-00006807; ZTE-AGIS-00006808 - ZTE-AGIS-00006811;
`ZTE-AGIS-00006812 - ZTE-AGIS-00006816; ZTE-AGIS-00006817 - ZTE-AGIS-00006820;
`ZTE-AGIS-00006812 - ZTE-AGIS-00006816; ZTE-AGIS-00006817 - ZTE-AGIS-00006820;
`ZTE-AGIS-00006821 - ZTE-AGIS-00006821; ZTE-AGIS-00006822 - ZTE-AGIS-00006879;
`ZTE-AGIS-00006821 - ZTE-AGIS-00006821; ZTE-AGIS-00006822 - ZTE-AGIS-00006879;
`ZTE-AGIS-00006880 - ZTE-AGIS-00006883; ZTE-AGIS-00006884 - ZTE-AGIS-00006886;
`ZTE-AGIS-00006880 - ZTE-AGIS-00006883; ZTE-AGIS-00006884 - ZTE-AGIS-00006886;
`ZTE-AGIS-00006887 - ZTE-AGIS-00006954; ZTE-AGIS-00006955 - ZTE-AGIS-00006958;
`ZTE-AGIS-00006887 - ZTE-AGIS-00006954; ZTE-AGIS-00006955 - ZTE-AGIS-00006958;
`ZTE-AGIS-00006959 - ZTE-AGIS-00006961; ZTE-AGIS-00006962 - ZTE-AGIS-00006965;
`ZTE-AGIS-00006959 - ZTE-AGIS-00006961; ZTE-AGIS-00006962 - ZTE-AGIS-00006965;
`ZTE-AGIS-00006966 - ZTE-AGIS-00006967; ZTE-AGIS-00006968 - ZTE-AGIS-00007063;
`ZTE-AGIS-00006966 - ZTE-AGIS-00006967; ZTE-AGIS-00006968 - ZTE-AGIS-00007063;
`ZTE-AGIS-00007064 - ZTE-AGIS-00007099; ZTE-AGIS-00007100 - ZTE-AGIS-00007161;
`ZTE-AGIS-00007064 - ZTE-AGIS-00007099; ZTE-AGIS-00007100 - ZTE-AGIS-00007161;
`ZTE-AGIS-00007162 - ZTE-AGIS-00007163; ZTE-AGIS-00007164 - ZTE-AGIS-00007212;
`ZTE-AGIS-00007162 - ZTE-AGIS-00007163; ZTE-AGIS-00007164 - ZTE-AGIS-00007212;
`ZTE-AGIS-00007213 - ZTE-AGIS-00007240; ZTE-AGIS-00007241 - ZTE-AGIS-00007243;
`ZTE-AGIS-00007213 - ZTE-AGIS-00007240; ZTE-AGIS-00007241 - ZTE-AGIS-00007243;
`ZTE-AGIS-00007244 - ZTE-AGIS-00007246; ZTE-AGIS-00007247 - ZTE-AGIS-00007314;
`ZTE-AGIS-00007244 - ZTE-AGIS-00007246; ZTE-AGIS-00007247 - ZTE-AGIS-00007314;
`ZTE-AGIS-00007315 - ZTE-AGIS-00007315; ZTE-AGIS-00007316 - ZTE-AGIS-00007385;
`ZTE-AGIS-00007315 - ZTE-AGIS-00007315; ZTE-AGIS-00007316 - ZTE-AGIS-00007385;
`ZTE-AGIS-00007386 - ZTE-AGIS-00007389; ZTE-AGIS-00007390 - ZTE-AGIS-00007393;
`ZTE-AGIS-00007386 - ZTE-AGIS-00007389; ZTE-AGIS-00007390 - ZTE-AGIS-00007393;
`ZTE-AGIS-00007394 - ZTE-AGIS-00007397; ZTE-AGIS-00007398 - ZTE-AGIS-00007398;
`ZTE-AGIS-00007394 - ZTE-AGIS-00007397; ZTE-AGIS-00007398 - ZTE-AGIS-00007398;
`ZTE-AGIS-00007399 - ZTE-AGIS-00007544; ZTE-AGIS-00007545 - ZTE-AGIS-00007547;
`ZTE-AGIS-00007399 - ZTE-AGIS-00007544; ZTE-AGIS-00007545 - ZTE-AGIS-00007547;
`ZTE-AGIS-00007548 - ZTE-AGIS-00007550; ZTE-AGIS-00007551 - ZTE-AGIS-00007552;
`ZTE-AGIS-00007548 - ZTE-AGIS-00007550; ZTE-AGIS-00007551 - ZTE-AGIS-00007552;
`ZTE-AGIS-00007553 - ZTE-AGIS-00007572; ZTE-AGIS-00007573 - ZTE-AGIS-00007755;
`ZTE-AGIS-00007553 - ZTE-AGIS-00007572; ZTE-AGIS-00007573 - ZTE-AGIS-00007755;
`ZTE-AGIS-00007756 - ZTE-AGIS-00007758; ZTE-AGIS-00007759 - ZTE-AGIS-00007761;
`ZTE-AGIS-00007756 - ZTE-AGIS-00007758; ZTE-AGIS-00007759 - ZTE-AGIS-00007761;
`ZTE-AGIS-00007762 - ZTE-AGIS-00007763; ZTE-AGIS-00007764 - ZTE-AGIS-00007785;
`ZTE-AGIS-00007762 - ZTE-AGIS-00007763; ZTE-AGIS-00007764 - ZTE-AGIS-00007785;
`ZTE-AGIS-00007786 - ZTE-AGIS-00007789; ZTE-AGIS-00007790 - ZTE-AGIS-00007963;
`ZTE-AGIS-00007786 - ZTE-AGIS-00007789; ZTE-AGIS-00007790 - ZTE-AGIS-00007963;
`ZTE-AGIS-00007964 - ZTE-AGIS-00007966; ZTE-AGIS-00007967 - ZTE-AGIS-00007968;
`ZTE-AGIS-00007964 - ZTE-AGIS-00007966; ZTE-AGIS-00007967 - ZTE-AGIS-00007968;
`ZTE-AGIS-00007969 - ZTE-AGIS-00008008; ZTE-AGIS-00008009 - ZTE-AGIS-00008037;
`ZTE-AGIS-00007969 - ZTE-AGIS-00008008; ZTE-AGIS-00008009 - ZTE-AGIS-00008037;
`ZTE-AGIS-00008038 - ZTE-AGIS-00008040; ZTE-AGIS-00008041 - ZTE-AGIS-00008044;
`ZTE-AGIS-00008038 - ZTE-AGIS-00008040; ZTE-AGIS-00008041 - ZTE-AGIS-00008044;
`ZTE-AGIS-0000804