Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 33.856
Study on Security aspects of
Single Radio Voice Continuity
from 5G to UTRAN

V16.1.0 (Wzip)  2019/06  16 p.
Rapporteur:
Dr. Gao, Feng
China Unicom

full Table of Contents for  TR 33.856  Word version:  16.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 5
1Scope  p. 6
2References  p. 6
3Definitions and abbreviations  p. 6
3.1Definitions  p. 6
3.2Abbreviations  p. 6
4Overview  p. 6
5Key issues  p. 7
5.1Key Issue #1: Achieving backward security of key derivation during SRVCC from 5G to UTRAN CS  p. 7
5.1.1Key issue details  p. 7
5.1.2Security threats  p. 7
5.1.3Potential Security requirements  p. 7
5.2Key Issue #2: Security of IMS Emergency Session Handling  p. 7
5.2.1Key issue details  p. 7
5.2.2Security threats  p. 7
5.2.3Potential Security requirements  p. 8
5.3Key Issue #3: Protecting the SRVCC capability  p. 8
5.3.1Key issue details  p. 8
5.3.2Security threats  p. 8
5.3.3Potential Security requirements  p. 8
5.4Key Issue #4: 5G UE returning from 3G SRVCC to E-UTRA or NR  p. 8
5.4.1Key issue details  p. 8
5.4.2Security threats  p. 8
5.4.3Potential Security requirements  p. 8
6Solutions  p. 9
6.1Solution #1.1: Key derivation during SRVCC from 5G to UTRAN CS without direct interface between AMF and MSC server  p. 9
6.1.1Introduction  p. 9
6.1.2Solution details  p. 9
6.1.3Impacts on existing nodes and functionality  p. 10
6.1.4Evaluation  p. 10
6.2Solution #1.2: Key derivation during SRVCC from 5G to UTRAN CS with direct interface between AMF and MSC server  p. 10
6.2.1Introduction  p. 10
6.2.2Solution details  p. 11
6.2.3Impacts on existing nodes and functionality  p. 11
6.2.4Evaluation  p. 12
6.3Solution #2: Emergency session in SRVCC from 5G to UTRAN CS  p. 12
6.3.1Introduction  p. 12
6.3.2Solution details  p. 12
6.3.3Impacts on existing nodes and functionality  p. 12
6.3.4Evaluation  p. 12
6.4Solution #3: Protecting the SRVCC capability  p. 12
6.4.1Introduction  p. 12
6.4.2Solution details  p. 13
6.4.3Impacts on existing nodes and functionality  p. 13
6.4.4Evaluation  p. 13
6.5Solution #4: Return from UTRAN to E-UTRAN or NR  p. 13
6.5.1Introduction  p. 13
6.5.2Solution details  p. 13
6.5.3Impacts on existing nodes and functionality  p. 13
6.5.4Evaluation  p. 13
7Conclusions  p. 14
$Change History  p. 16

Up   Top