throbber

`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`APPLE INC., FACEBOOK, INC., and WHATSAPP, INC.,
`Petitioner
`
`v.
`
`UNILOC USA, INC. and UNILOC LUXEMBOURG S.A.
`Patent Owner
`
`
`
`Case IPR2017-002221
`Patent 8,243,723
`
`
`
`
`DECLARATION OF LEONARD J. FORYS, PH.D.
`IN SUPPORT OF PETITIONER APPLE INC.’S
`REPLY TO PATENT OWNER RESPONSE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Mail Stop “PATENT BOARD”
`Patent Trial and Appeal Board
`U.S. Patent & Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`1 Facebook, Inc. and WhatsApp, Inc., who filed a petition in IPR2017-01635, have
`been joined as petitioners in this proceeding.
`
`
`
`
`
`Apple Ex. 1028
`Apple v. Uniloc
`IPR2017-00222
`
`

`

`
`
`
`TABLE OF CONTENTS
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`
`Introduction ......................................................................................................... 1
`I.
`II. Response to Uniloc’s Patent Owner Response and Mr. Easttom’s Declaration 5
`A. The term “list” means a list of “one or more nodes.” ..................................... 5
`B. Vuori’s SVM watcher is user-facing, therefore Vuori teaches or suggests
`“transmitting a signal to a client including a list of the recorded connectivity
`status…” ................................................................................................................. 8
`III. Conclusion .....................................................................................................16
`
`
`
`
`
`
`- i -
`
`

`

`
`
`I.
`
`Introduction
`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`I, Dr. Leonard J. Forys, declare as follows:
`
`1.
`
`This declaration supplements my declaration (Ex. 1003) submitted
`
`with Apple’s Petition in IPR2017-00222. For the sake of brevity, I rely on and
`
`confirm the facts and opinions contained in my Declaration dated November 14,
`
`2016 – Ex. 1003. My qualifications and background information can be found in
`
`my original Declaration. (Ex. 1003 ¶¶1-2, 6-53.)
`
`2.
`
`I am making this declaration to respond to certain arguments raised by
`
`Uniloc USA Inc. and Uniloc Luxembourg S.A., (“Uniloc” or “PO”) in its Patent
`
`Owner Response (“POR”) and the declaration of William C. Easttom II (Ex.
`
`2001) submitted therewith. In view of Uniloc’s and Mr. Easttom’s arguments, it is
`
`still my opinion that all of the claim elements in the ’723 patent are taught or
`
`suggested by Vuori alone or in combination with Malik and the other prior art
`
`references presented in the Grounds of the Petition. In my opinion, Uniloc’s
`
`arguments rely on overly narrow interpretations of the claim elements, inaccurate
`
`explanations of the prior art references, and unfounded concerns about the
`
`combinations of prior art references that inflate potential “detriments” and ignore
`
`an artisan’s understanding of design tradeoffs. My opinions are set forth below.
`
`
`
`
`
`
`
`- 1 -
`
`

`

`
`
`
`
`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`In preparing this declaration, I have reviewed and am familiar with the
`
`3.
`
`following documents:
`
`Exhibit
`
`Description
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`Rojas, U.S. Patent No. 8,243,723 (earliest priority date December 18,
`2003; filed March 4, 2009; issued August 14, 2012).
`
`File History for U.S. Patent No. 8,243,723.
`
`Declaration of Leonard J. Forys, Ph.D.
`
`Curriculum Vitae of Leonard J. Forys, Ph.D.
`
`Vuori, U.S. Patent Application Publication No. 2002/0146097 (filed
`July 23, 2001, published October 10, 2002).
`
`SMSS, Universal Mobile Telecommunications System (UTMS);
`Technical realization of the Short Message Service (SMS) (3G TS
`23.040 version 3.5.0 Release 1999) (published on August 16, 2000).
`
`Holtzberg, U.S. Patent No. 6,625,261 (filed December 20, 2000,
`issued September 23, 2003).
`
`Väänänen, U.S. Patent No. 7,218,919 (filed August 8, 2001, issued
`May 15, 2007).
`
`Dahod et al., U.S. Patent Application Publication No. 2004/0022208
`(filed on August 1, 2002, published February 5, 2004).
`
`Hogan et al., U.S. Patent No. 5,619,554 (filed June 8, 1994, issued
`April 8, 1997).
`
`Logan et al., U.S. Patent No. 5,732,216 (filed October 2, 1996, issued
`March 24, 1998).
`
`Peersman et al., The Global System for Mobile Communications
`Short Message Service, IEEE Personal Communications (June 2000).
`
`- 2 -
`
`

`

`Exhibit
`
`1013
`
`1014
`
`1015
`
`1016
`
`1017
`
`1018
`
`1019
`
`1020
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`
`
`
`
`
`
`
`
`Description
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`SMS Forum, SMPP v3.4 Protocol Implementation guide for GSM /
`UMTS, Version 1.0 (May 30, 2002).
`
`Clarke et al., Experiments with packet switching of voice traffic, IEE
`Proceedings G - Electronic Circuits and Systems, Vol.130, Pt. G, No.
`4, pp. 105-13 (August 1983).
`
`Oouchi et al., Study on Appropriate Voice Data Length of IP Packets
`for VoIP Network Adjustment, Proceedings of the IEEE Global
`Telecommunications Conference (GLOBECOM) 2002, V. 2, Taipei,
`Taiwan, 2002, pp. 1618–1622.
`
`Lotito et al., U.S. Patent No. 4,625,081 (filed November 30, 1982,
`issued November 25, 1986).
`
`Pershan, U.S. Patent No. 5,260,986 (filed April 23, 1991, issued
`November 9, 1993).
`
`Old Version of AOL Instant Messenger 2.1 Download, retrieved
`from http://www.oldapps.com/aim.php?old_aim=4#screenshots.
`
`Malik, Patent Publication No. 2003/0219104 (filed August 19, 2002,
`published November 27, 2003).
`
`Staack et al., WO Patent Publication No. 02/07396 (filed July 13,
`2000, published January 24, 2002).
`
`Lerner et al., U.S. Patent No. 6,192,395 (filed December 17, 1999,
`issued February 20, 2001).
`Stubbs, WO Patent Publication No. 99/63773 (filed June 3, 1999,
`published December 9, 1999).
`Abburi, U.S. Patent Application Publication No. 2003/0147512 (filed
`on February 1, 2002, published August 7, 2003).
`File History for U.S. Patent No. 7,535,890.
`
`Day et al., A Model for Presence and Instant Messaging, Network
`Working Group, RFC 2778, pp. 1-17 (February 2000).
`
`- 3 -
`
`

`

`
`
`
`
`
`
`
`
`Description
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`International Telecommunication Union, General Aspects of Digital
`Transmission Systems, Terminal Equipments, Pulse Code
`Modulation (PCM) of Voice Frequencies, ITU-T Recommendation
`G.711., pp. 1-10 (ITU 1993).
`
`Gayomali, C., “The text message turns 20: A brief history of SMS,”
`The Week, December 3, 2012, retrieved from
`http://www.theweek.com/articles/469869/text-message-turns-20-
`brief-history-sms.
`
`Deposition transcript of William C. Easttom, II
`
`Declaration of William C. Easttom II
`
`Deposition of Dr. Leonard J. Forys (September 13, 2017)
`
`Description
`
`Petition for Inter-Partes Review of U.S. Patent No. 8,243,723
`
`Uniloc’s Patent Owner Preliminary Response
`
`Decision – Institution of Inter Partes Review
`
`Uniloc’s Patent Owner Response
`
`Exhibit
`
`1026
`
`1027
`
`1029
`
`2001
`
`2002
`
`
`Paper
`
`2
`
`6
`
`7
`
`11
`
`
`4.
`
`To the best of my knowledge, the above Exhibits are true and accurate
`
`copies of what they purport to be. An expert in the field would reasonably rely on
`
`them to formulate opinions such as those set forth in this declaration.
`
`5.
`
`I continue to be compensated for my work in this proceeding. My
`
`compensation in no way depends upon the outcome of this proceeding.
`
`- 4 -
`
`

`

`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`
`II. Response to Uniloc’s Patent Owner Response and Mr. Easttom’s
`Declaration
`
`6.
`
`I address certain portions of Uniloc’s POR and Mr. Easttom’s
`
`Declaration below. Failure to address any statement or argument presented by
`
`Uniloc or Mr. Easttom should not be viewed as an acquiescence to or agreement
`
`with that statement or argument.
`
`A. The term “list” means a list of “one or more nodes.”
`As I mentioned in my original Declaration, I have applied the plain
`7.
`
`and ordinary meaning of the claim terms as understood to a POSITA at the time of
`
`invention. (Ex. 1003, ¶101.) Uniloc’s attempt to limit the term “list,” as recited in
`
`claim 1, to “more than one,” is inconsistent with the plain and ordinary meaning
`
`of the term “list.” In fact, Uniloc’s proposed definition is well outside what a
`
`POSITA would have understood the term to mean in light of the specification.
`
`Further, Mr. Easttom’s analysis, hinges on the faulty construction, which is
`
`divorced from the plain and ordinary meaning of the terms at issue.
`
`8.
`
`The recited “list” includes the recorded connectivity status of one or
`
`more nodes. The Board stated:
`
`Patent Owner’s argument appears to take an overly narrow view of
`the term to mean that the ‘list of the recorded connectivity status’
`must include the connectivity status of more than one node. Patent
`Owner cites no factual support in the record for its argument that the
`scope of the term excludes a singular value. Furthermore, based on
`
`
`
`- 5 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`our review of the ’723 patent, the specification seems to contradict
`Patent Owner’s argument.
`
`(Institution Decision, 17-18, emphasis added.)
`
`9.
`
`Based on the ’723 specification, the term “list” must include the
`
`connectivity status of “one or more nodes.”
`
`10. Uniloc argues that “[a] plain reading of the claim language itself …
`
`unambiguously resolves this issue” and that without the “modifying phrase ‘one
`
`or more’… the transmitted ‘list’ must have the recorded connectivity status for
`
`multiple ‘nodes’” (POR, 8-9.) This fails to take into account that the ’723 patent
`
`specification consistently refers to a list as having “one or more” items: “a list of
`
`one or more IVM recipients” (’723 patent, 8:52-56 and 16:61-63) and “[t]he IVM
`
`client 208 displays a list of one or more IVM recipients on its display 216,
`
`provided and stored by the local IVM server 202” (Institution Decision, citing
`
`’723 patent, 7:61-63). So a POSITA would have understood that a “list” in this
`
`patent, under its broadest reasonable interpretation (BRI), encompasses “one or
`
`more” items.
`
`11.
`
`In addition to being overly narrow, Uniloc’s analysis is incomplete.
`
`For example, Uniloc argues that the omission of the modifying phrase “one or
`
`more” confirms that “the transmitted ‘list’ must have the recorded connectivity
`
`status for multiple ‘nodes.’” (POR, 9.) Uniloc’s analysis fails to identify other
`
`
`
`- 6 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`modifying phrases that are also omitted from the claim. For example, if the ’723
`
`patent inventor truly intended the transmitted list to include the recorded
`
`connectivity status for “multiple nodes,” as Uniloc argues, notably missing from
`
`the claim language are phrases including “more than one” or “a plurality of...”
`
`12. Because under the Patent Owner’s argument the claim is ambiguous
`
`and does not define the term “list” with a modifying phrase, the term must be
`
`interpreted according to its BRI in light of the specification.
`
`13. Uniloc further argues that, “[v]iewing Claim 1 as a whole further
`
`confirms that the phrase ‘one or more’ was explicitly recited when the intent was
`
`to encompass both the singular and plural form of a term.” (POR, p. 8.) Uniloc’s
`
`analysis is, again, incomplete. Looking at claim 1 as a whole, and even just the
`
`limitation as a whole, reveals that the claim recites the phase “a list of the
`
`connectivity status of each of the nodes in the sub-set.” The term sub-set is not
`
`defined by the ’723 patent, but a POSITA would have understood that the term
`
`sub-set means a smaller part of larger set. That is, a POSITA would have
`
`understood that the “sub-set of nodes” could be a single node. In such a case, the
`
`list of “the connectivity status of each of the nodes in the sub-set” could
`
`reasonably include only one node, because the sub-set contains only one node.
`
`Thus, under BRI the term “list” must include the connectivity status of “one or
`
`more nodes.” The Uniloc position would not consider a network composed of
`
`
`
`- 7 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`only two subscribers as being within the scope of the claims. However, nothing in
`
`the ‘723 patent prohibits such a situation.
`
`14. Finally, Uniloc provides that “[i]t is significant that ‘nodes’ is recited
`
`in the plural in the phrase ‘each of the nodes in the sub-set.’ Use of the plural form
`
`of ‘nodes’ in that context confirms the ‘list’ must record the connectivity status of
`
`more than one node.” (POR, 8.) Yet the specification refers to a list as having
`
`“one or more” items – and in each case the “one or more” items are identified in
`
`plural form. Thus, Uniloc’s argument falls short because the recitation of nodes
`
`(in plural form) is consistent with the ’723 patent’s disclosure of a “list of one or
`
`more” items (in plural form).
`
`15.
`
`In view of the foregoing, the term “list” encompasses “one or more.”
`
`B. Vuori’s SVM watcher is user-facing, therefore Vuori teaches or
`suggests “transmitting a signal to a client including a list of the
`recorded connectivity status…”
`
`16. Mr. Easttom argued that Vuori’s “SVM watcher 256 is not a user-
`
`facing ‘client’ and thus does render obvious the claimed ‘transmitting’ step.”
`
`(POR, 12; Ex. 2001, ¶29.) But Vuori’s SVM watcher is user-facing and does
`
`distribute connectivity status on a line to the user. The directional arrows of
`
`Vuori’s Figure 7 are not dispositive, Vuori expressly
`
`teaches two-way
`
`communication. Vuori teaches that a user interacts with the system using an
`
`SVM watcher UA, suggesting two-way communication. Vuori further teaches that
`
`
`
`- 8 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`“[a] user agent is purely coupling between a principal and some core entity of
`
`the system” including the SVM watcher 256. The term coupling, as applied in
`
`Vuori, indicates that the SVM watcher is coupled to the user agent, suggesting
`
`that the SVM watcher is indeed user-facing. The presence status is distributed so
`
`that it can be “interpretable by programs or by persons,” suggesting a person
`
`may view and thus interpret shared presence status information. Vuori’s
`
`description of a buddy list is evidence that the SVM watcher is user-facing
`
`because the sender determines whether the intended recipient is available by
`
`means of a presence service. Each of the foregoing reasons is evidence that
`
`Uniloc’s arguments fall short.
`
`17. Uniloc appears to argue that the arrows of Figure 7 indicate that the
`
`presence information is distributed only to the SVM watcher 256 and is not
`
`distributed to a “‘user agent’ or ‘UA’ device (276, 278) of either end user.” (POR,
`
`12.) Uniloc’s reliance on the “directional communication arrows in Figure 7” fails
`
`to consider Vuori’s entire disclosure. A POSITA would have understood that the
`
`direction of the arrows illustrated in the Figure are not dispositive and do not
`
`exemplify the only embodiments described in Vuori.
`
`18. Vuori’s SVM watcher is further illustrated in Figure 8.
`
`
`
`- 9 -
`
`

`

`
`
`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`
`“As shown in FIG. 8, according to an adaptation of RFC 2778, there
`are two kinds of SVM watchers, called SVM fetchers 258 and SVM
`subscribers 260. An SVM fetcher 258 simply requests the current
`value of some SVM presentity's presence information from the
`presence service 248. In contrast, an SVM subscriber 260 requests
`notification from the SVM presence service 248 of (future) changes in
`some SVM presentity's presence information. A special kind of SVM
`fetcher is one that fetches SVM presence information on a regular
`basis. This is called an SVM poller 262.”
`
`(Vuori, [0044], emphasis added.) As is known in the art, “requesting,” “fetching,”
`
`and “polling” are done by sending messages from a device 258 (SVM Watcher) to
`
`device 248 (SVM presence service), thus in the opposite direction from the
`
`indicated arrow in Figure 7. Thus, because Vuori’s SVM watchers are capable of
`
`requesting, fetching, and polling information, it suggests two-way communication
`
`and/or data transfer. That is the plain and ordinary meaning of the term “interact.”
`
`And the SVM watcher’s requesting, fetching, and polling information show that
`
`the arrows of Figure 7 are not dispositive, as Mr. Easttom seems to suggest.
`
`
`
`- 10 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`19. Figure 7 shows each user agent is associated with a principal. As
`
`described in Vuori, the term “principal” refers to “people, groups and/or software
`
`in the ‘real world’ outside of the system that use the system as a means of
`
`coordination and communication.… A principal interacts with the system via one
`
`of several user agents (UAs) such as shown in FIGS. 7 and 9.” (Vuori, [0046].)
`
`Vuori therefore suggests that when a principal interacts with the system via a user
`
`agent, he/she is engaging in a two-way communication and/or data transfer –
`
`because that is the plain and ordinary meaning of the term “interact.” Thus, a
`
`POSITA would have understood that the described interaction indicates that the
`
`SVM watchers are user-facing because data, including connectivity information,
`
`may be distributed to and from the user agents via the described interaction.
`
`20. Vuori further teaches that “[a] user agent is purely coupling between a
`
`principal and some core entity of the system (SVM inbox 274, SVM sender 272,
`
`SVM presentity 254, SVM watcher 256). It will therefore be understood that the
`
`simple examples shown in RFC 2778 are applicable to the SVM service of the
`
`present invention.” (Vuori, [0046].) The term coupling, as applied in Vuori,
`
`indicates that the SVM watcher is “coupled” to the user agent. When two entities
`
`are coupled, as the user agent and SVM watcher 256, a POSITA would
`
`understand that the disclosed coupling suggests a two-way communication
`
`
`
`- 11 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`between the user agent and SVM watcher 256. Thus, Vuori teaches or suggests
`
`that the SVM watcher is indeed user-facing.
`
`21. Evidence that the SVM watcher is indeed user-facing, and that Mr.
`
`Easttom’s conclusions are misguided, can be found in Vuori’s description of the
`
`term “status.” For example, Vuori teaches that each “element comprises a status
`
`marker 298, 300 (which might convey information such as on-line/off-
`
`line/busy/away/do not disturb).… Status can be interpretable by programs or by
`
`persons and can consist of single or multiple values as spelled out in the IETF
`
`model of RFC 2778.” (Vuori, [0047], emphasis added.) For status information to
`
`be interpretable by a person, the status information must be transmitted to a device
`
`capable of, e.g., displaying the information (or otherwise informing them) for the
`
`person to see. Thus, Vuori discloses or suggests that the status (i.e. connectivity)
`
`information is available to a person and that the SVM watcher is user-facing.
`
`22. The term “buddy list” was a well-known term in the art. Vuori
`
`describes the term buddy list in the context of a sender determining whether or not
`
`the potential recipient is available to receive a message. (See Vuori [0035]).
`
`Specifically, “the sender first determines whether the intended recipient is
`
`available by means of a presence service and the intended recipient has
`
`effectively acquiesced to availability by previously joining a ‘buddy list’ or
`
`otherwise subscribing to the service.” The first thing to note is that the term
`
`
`
`- 12 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`“buddy list” is in quotations which suggest that it is a term of art. The applicant
`
`provides “joining a ‘buddy list’” as an example for subscribing to a presence
`
`service. Vuori’s presence service
`
`tracks presence
`
`information
`
`including
`
`information such as whether a user is on-line/off-line/busy/away/do not disturb.
`
`(Vuori, [0047].) So a sender is able to determine whether an intended recipient is
`
`available because the recipient has acquiesced to availability by previously joining
`
`a buddy list. That is, the connectivity information of a potential recipient
`
`connected to the network is distributed to the sender. (Vuori, [0035] and [0047].)
`
`23. Vuori additionally teaches:
`
`An SVM presence service 248 serves to accept SVM presence
`information e.g. on a line 250, store it, and distribute it, e.g., on a
`line 252. An SVM presentity 254 is a client that provides the presence
`information on the line 250 to be stored and distributed. Another set
`of clients called SVM watchers such as an SVM watcher 256 in FIG.
`7, receives SVM presence information on the line 252 from the SVM
`presence service 248.
`
`(Id., [0043], emphasis added.)
`
`24. Again, according to Vuori, when a user joins a buddy list, he/she
`
`acquiesces in their availability information being shared with others, using, for
`
`example, Vuori’s presence service. Thus, a user’s availability is stored and
`
`distributed to the clients associated with the buddy list that the potential recipient
`
`has joined. A POSITA would have understood that by joining a “buddy list,” a
`
`
`
`- 13 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`user allows his/her presence information (i.e. connectivity) to be transmitted to all
`
`of the nodes associated with the buddy lists he/she has joined. (Ex. 2002, Forys
`
`Deposition, 73:7-11.) That is, the “buddy list” is not a list belonging to the
`
`recipient, but rather it belongs to the sender who is able to see which recipients are
`
`available.
`
`25. A POSITA would have understood that Vuori’s SVM watcher is user-
`
`facing and that Vuori teaches distributing the presence information because, as the
`
`Board agreed, “[d]istributing connectivity information ‘on a line’ means to
`
`distribute the information to other users connected to the network,” as recited in
`
`claim 1. (Institution Decision, 17-18.)
`
`26. Even if the Board determines that the term “list” requires connectivity
`
`status of more than one node, a POSITA would have understood that Vuori still
`
`teaches the “transmitting” feature of claim 1, including a “list of the recorded
`
`connectivity status for each of the nodes in the sub-set corresponding to the
`
`client.” For example, Vuori determines the availability of one or more recipients,
`
`and “[t]he user 10 then uses the menu key to select one or more intended
`
`recipients…” (Vuori, [0033].) And “[t]he SVM is then sent to an SVM service
`
`center. This could be a short message service (SMS) service center which
`
`determines the availability of the one or more intended recipients.” (Vuori,
`
`[0034].) To the extent Uniloc or Mr. Easttom may argue that the short message
`
`
`
`- 14 -
`
`

`

`
`
`
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`service center is different than, or does not include, Vuori’s presence service, a
`
`POSITA would apply the foregoing teachings (i.e., determining the availability of
`
`one or more intended recipients) to the presence service.
`
`
`
`
`
`
`
`- 15 -
`
`

`

`
`
`III. Conclusion
`In signing this declaration, I recognize that the declaration will be
`27.
`
`Case IPR2017-00222
`U.S. Pat. No. 8,243,723
`
`
`
`
`filed as evidence in a contested case before the Patent Trial and Appeal Board of
`
`the United States Patent and Trademark Office. I also recognize that I may be
`
`subject to cross-examination in the case and that cross-examination will take place
`
`within the United States. If cross-examination is required of me, I will appear for
`
`cross-examination within the United States during the time allotted for cross-
`
`examination.
`
`28.
`
`I hereby declare that all statements made herein of my own
`
`knowledge are true and that all statements made on information and belief are
`
`believed to be true; and further that these statements were made with the
`
`knowledge that willful false statements and the like so made are punishable by
`
`fine or imprisonment, or both, under Section 1001 of Title 18 of the United States
`
`Code.
`
`Executed this 18th day of December, 2017.
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`______________________________
`
`
`
`Leonard J. Forys, Ph.D.
`
`- 16 -
`
`

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