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

TR 33.790
Study on the Security support for the next generation Real Time Communication services Phase 2

V19.1.0 (Wzip)  2025/09  … p.
Rapporteur:
Dr. Tsiatsis, Vlasios
Ericsson LM

full Table of Contents for  TR 33.790  Word version:  19.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 8
2References  p. 8
3Definitions of terms, symbols and abbreviations  p. 9
3.1Terms  p. 9
3.2Symbols  p. 9
3.3Abbreviations  p. 9
4Assumptions  p. 10
4.1General  p. 10
4.2Architectural Assumptions and Principles  p. 10
5Key issues  p. 10
5.1Key issue #1: Third party specific user identities  p. 10
5.1.1Key issue details  p. 10
5.1.2Threats  p. 10
5.1.3Potential security requirements  p. 11
5.2Key issue #2: Security of IMS based Avatar Communication  p. 11
5.2.1Key issue details  p. 11
5.2.2Threats  p. 11
5.2.3Potential security requirements  p. 11
5.3Key Issue #3: Security and privacy aspects of IMS DC capability exposure  p. 12
5.3.1Key issue details  p. 12
5.3.2Security threats  p. 12
5.3.3Potential security requirements  p. 12
6Solutions  p. 13
6.0Mapping between key issues and solutions  p. 13
6.1Solution #1: Signing/verification of third party ID information  p. 13
6.1.1Introduction  p. 13
6.1.2Solution details  p. 13
6.1.3Evaluation  p. 15
6.2Solution #2: Security of 3rd party specific identities  p. 15
6.2.1Introduction  p. 15
6.2.2Solution details  p. 15
6.2.2.1Solution Description  p. 15
6.2.2.2How the Originating IMS network invokes the signing on behalf of 3rd party (SIP trunk)  p. 18
6.2.2.3How the Originating IMS network invokes the signing on behalf of 3rd party (Single SIP registration)  p. 20
6.2.3Evaluation  p. 21
6.3Solution #3: Support of Third Party specific User Identities in IMS using STIR/SHAKEN  p. 21
6.3.1Introduction  p. 21
6.3.2Solution detail  p. 23
6.3.3Evaluation  p. 25
6.4Solution #4: SHAKEN based third-party specific user identities  p. 25
6.4.1Introduction  p. 25
6.4.2Solution details  p. 25
6.4.2.1General procedures  p. 25
6.4.2.2Alternative authorisation procedure  p. 27
6.4.3Evaluation  p. 27
6.5Solution #5: Securing the IMS based avatar communication  p. 27
6.5.1Introduction  p. 27
6.5.2Solution details  p. 27
6.5.2.0General  p. 27
6.5.2.1Network centric procedure  p. 28
6.5.2.2Sending UE centric procedure  p. 29
6.5.2.3Receiving UE centric procedure  p. 30
6.5.3Evaluation  p. 31
6.6Solution #6: Solution for secure IMS based avatar communication  p. 31
6.6.1Introduction  p. 31
6.6.2Solution details  p. 32
6.6.2.1Network centric IMS avatar call flow  p. 32
6.6.2.2Sending UE centric IMS avatar call flow  p. 33
6.6.2.3Receiving UE centric IMS avatar call flow  p. 34
6.6.2.4UE1 attestation  p. 35
6.6.3Evaluation  p. 35
6.7Solution #7: Protect IMS DC based Avatar Communication  p. 35
6.7.1Introduction  p. 35
6.7.2Solution details  p. 36
6.7.2.0General  p. 36
6.7.2.1Procedure to protect IMS DC based Avatar Communication (Network based Rendering)  p. 36
6.7.2.2Procedure to protect IMS DC based Avatar Communication (UE-A based Rendering)  p. 39
6.7.2.3Procedure to protect IMS DC based Avatar Communication (UE-B based Rendering)  p. 40
6.7.3Evaluation  p. 40
6.8Solution #8: Security for IMS based Avatar Communication  p. 41
6.8.1Introduction  p. 41
6.8.2Solution details  p. 41
6.8.3Evaluation  p. 45
6.9Solution #9: Secure IMS DC capability exposure  p. 45
6.9.1Introduction  p. 45
6.9.2Solution details  p. 45
6.9.2.0General  p. 45
6.9.2.1Procedure of DC AS authorization for DC event subscription  p. 45
6.9.2.2Procedure of DC AS authorization for data channel session control  p. 46
6.9.3Evaluation  p. 47
6.10Solution #10: User aware IMS DC capability exposure  p. 48
6.10.1Introduction  p. 48
6.10.2Solution details  p. 48
6.10.3Evaluation  p. 48
6.11Solution #11: IMS (DC) capability exposure security based on existing specification  p. 48
6.11.1Introduction  p. 48
6.11.2Solution details  p. 48
6.11.2.1General  p. 48
6.11.2.2IMS event exposure security  p. 48
6.11.2.3IMS DC session control exposure security  p. 51
6.11.3Evaluation  p. 51
6.12Solution #12: Solution for secure IMS based avatar communication using STIR/SHAKEN  p. 52
6.12.1Introduction  p. 52
6.12.2Solution details  p. 52
6.12.2.1Network centric IMS avatar call flow  p. 52
6.12.2.2Sending UE centric IMS avatar call flow  p. 53
6.12.2.3Receiving UE centric IMS avatar call flow  p. 54
6.12.3Evaluation  p. 54
6.13Solution #13: IMS avatar communication security based on existing specification  p. 55
6.13.1Introduction  p. 55
6.13.2Solution details  p. 55
6.13.2.1General  p. 55
6.13.2.2Security for the Sending UE centric procedure  p. 55
6.13.2.3Security for the Receiving UE centric procedure  p. 56
6.13.2.4Security for the Network centric procedure  p. 58
6.13.3Evaluation  p. 58
7Conclusions  p. 59
7.1Conclusions for Key Issue #1: Third party specific user identities  p. 59
7.2Conclusions for Key Issue #2: Security of IMS based Avatar Communication  p. 59
7.3Conclusions for Key Issue #3: Security and privacy aspects of IMS DC capability exposure  p. 60
$Change history  p. 57

Up   Top