Skip to main navigation Skip to search Skip to main content

Strong Converse for Hypothesis Testing Against Independence over a Two-Hop Network

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

By proving a strong converse, we strengthen the weak converse result by Salehkalaibar, Wigger and Wang (2017) concerning hypothesis testing against independence over a two-hop network with communication constraints. Our proof follows by judiciously combining two recently proposed techniques for proving strong converse theorems, namely the strong converse technique via reverse hypercontractivity by Liu, van Handel, and Verdú (2017) and the strong converse technique by Tyagi and Watanabe (2018), in which the authors used a change-of-measure technique and replaced hard Markov constraints with soft information costs. The techniques used in our paper can also be applied to prove strong converse theorems for other multiterminal hypothesis testing against independence problems.

Original languageEnglish
Title of host publication2019 IEEE International Symposium on Information Theory, ISIT 2019 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages1994-1998
Number of pages5
ISBN (Electronic)9781538692912
DOIs
StatePublished - Jul 2019
Externally publishedYes
Event2019 IEEE International Symposium on Information Theory, ISIT 2019 - Paris, France
Duration: 7 Jul 201912 Jul 2019

Publication series

NameIEEE International Symposium on Information Theory - Proceedings
Volume2019-July
ISSN (Print)2157-8095

Conference

Conference2019 IEEE International Symposium on Information Theory, ISIT 2019
Country/TerritoryFrance
CityParis
Period7/07/1912/07/19

Keywords

  • Hypothesis testing with communication constraints
  • Relay
  • Strong converse
  • Testing against independence
  • Two-hop network

Fingerprint

Dive into the research topics of 'Strong Converse for Hypothesis Testing Against Independence over a Two-Hop Network'. Together they form a unique fingerprint.

Cite this