Abstract
In this paper, we study the stability region of the two-user broadcast channel (BC) with bursty data arrivals and security constraints. It is assumed that one of the receivers has a secrecy constraint, i.e., its packets need to be kept secret from the other receiver, which is defined based on signal to interference noise ratio. The receiver with secrecy constraint has full-duplex capability to send a jamming signal for improving its service rate. The stability region of the two-user BC with secrecy constraint is characterized for the general decoding case. Then, assuming two different decoding schemes, the respective stability regions are derived. The full-duplex operation of receiver results in self-interference, and the effect of imperfect self-interference cancelation on the stability region is also investigated. The stability region of the BC with a secrecy constraint, where the receivers do not have full duplex capability can be obtained as a special case of the results derived in this paper. In addition, the paper considers the problem of maximizing the saturated throughput of the queue for which there is no secrecy constraint under minimum service guarantees for the other queue. The results provide new insights on the effect of the secrecy constraint on the stability region of the BC. It is found that the stability region with secrecy constraint is sensitive to the degree of self-interference cancelation.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: IEEE Transactions on Information Forensics and Security
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.