2017
DOI: 10.1007/s11277-017-4771-5
|View full text |Cite
|
Sign up to set email alerts
|

Bitstream-Oriented Protection for the H.264/Scalable Video Coding (SVC)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 8 publications
0
3
0
Order By: Relevance
“…Terefore, VPS, SPS, and PPS are also not appropriate for video encryption. Ting et al utilized the bitstream of video coding layer (VCL) data [31]. Te NALU bodies of I slices are encrypted by the AES block cipher and those of B/P slices are encrypted with the CBC-mode XOR algorithm.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Terefore, VPS, SPS, and PPS are also not appropriate for video encryption. Ting et al utilized the bitstream of video coding layer (VCL) data [31]. Te NALU bodies of I slices are encrypted by the AES block cipher and those of B/P slices are encrypted with the CBC-mode XOR algorithm.…”
Section: Related Workmentioning
confidence: 99%
“…Terefore, compared with VEAs before compression coding, VEAs based on compression coding are more efcient and more appropriate for real-time video protection. Tese VEAs are roughly divided into two categories: (1) encryption through video coding and (2) encryption after video coding [24][25][26][27][28][29][30][31][32]. Category (1) is embedded into one of the steps of the video coding standard, mostly before entropy coding.…”
Section: Introductionmentioning
confidence: 99%
“…Meanwhile, it performed a series operation of analysis, extraction, encryption, and encoding on the H.264 bitstream, so it can be classified as the BOE method. References [3,18,23] proposed a similar encryption method for H.264 bitstream, which retained the 'header' information of the H.264 bitstream and encrypted the rest of the data. When the type of 'header' is revised as unspecific, the encrypted bitstream will be bypassed without decoding to maintain format compatibility.…”
Section: Introductionmentioning
confidence: 99%