Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.880  Word version:  15.1.0

Top   Top   Up   Prev   Next
1…   4…   7…   8…

 

7  Potential security solutionsp. 40

7.1  Generalp. 40

7.2  Cross-service security solutionsp. 40

7.2.1  Solution #1.1 : KMS Discovery and redirectionp. 40

7.2.2  Solution #1.2 : Distribution of key material to protect signalling between the MCX Server and the MCX clientp. 48

7.2.3  Solution #1.3 : Adding KMS security domain details to configuration datap. 52

7.2.4  Solution #1.4 : Encryption of entire XML signalling contentp. 54

7.2.5  Solution #1.5 : Signalling Proxyp. 55

7.2.6  Solution #1.6 : Authentication of a sensitive signalling request (EAR)p. 60

7.2.7  Solution #1.7 : EAR authorisationp. 62

7.3  Security solutions for the Common Functional Architecture (MC_ARCH)p. 69

7.4  Security solutions to enhance push-to-talk (eMCPTT)p. 69

7.4.1  Solution #3.1 : New bearer specific key for MBMS subchannel control message protectionp. 69

7.4.2  Solution #3.2 : MKFC based protection for MBMS subchannel control messagesp. 71

7.4.3  Solution #3.3 : New server specific key for MBMS subchannel control message protectionp. 72

7.4.4  Solution #3.4 : Key management for Temporary Group Call - regroup callp. 74

7.4.5  Solution #3.5 : Concealment of group identifiers using group specific pseudonymsp. 76

7.4.6  Solution #3.6 : Concealment of group identifiers using session specific pseudonymsp. 78

7.4.7  Solution #3.7 : Key management for First-to-answer callp. 80

7.5  Security solutions for data (MCData)p. 83

7.5.1  Solution #4.1 : SDS key distribution through signalling channelp. 83

7.5.2  Solution #4.2 : SDS key distribution alongside messagesp. 84

7.5.3  Solution #4.3 : MCData SDS protectionp. 86

7.5.4  Solution #4.4 : MCData SDS/FD signalling and payload protectionp. 89

7.5.5  Solution #4.5 : MCData Key managementp. 92

7.5.6  Solution #4.6 : MCData key distributionp. 93

7.6  Security solutions for video (MCVideo)p. 94

7.7  Security solutions for migration and interconnect (MCSMI)p. 95

7.8  Security solutions for interworking between LTE and non-LTE systems (MCCI)p. 97

7.8.1  Solution #7.1: MC Security Gateway (SeGy) acts as a single MC clientp. 97

7.8.2  Solution #7.2: MC Security Gateway (SeGy) acts as many MC clientsp. 98

7.8.3  Solution #7.3: MC Security Gateway (SeGy) acts as many migrated MC clientsp. 99

7.8.4  Solution #7.4: MC Security Gateway (SeGy) acts as an external MC Domainp. 100

7.8.5  Solution #7.5: MC Security Gateway (SeGy) acts as a single user in an external MC Domainp. 101

7.8.6  Solution #7.6: Interworking security data management using MCData SDS when security data is home to non-3GPP system.p. 102

7.8.7  Solution #7.7: Interworking security data management using SIP MESSAGE message when security data is home to non-3GPP system.p. 103


Up   Top   ToC