Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.843  Word version:  15.1.0

Top   Top   Up   Prev   None
1…   5…

 

5  Key issues

5.1  Key Issue #1: Authorization for indirect 3GPP communication

5.2  Key Issue #2: Authentication of eRemote-UE via eRelay-UE

5.3  Key Issue #3: IMSI Privacy of eRemote-UEWord‑p. 10

5.4  Key Issues #4: DiscoveryWord‑p. 11

5.5  Key Issues #5: Security of CP between eRemote-UE and networkWord‑p. 12

5.6  Key Issue #6: Security of Service Continuity

5.7  Key Issues #7: Authentication of eRemote-UE during Setting Up Indirect 3GPP CommunicationWord‑p. 15

5.8  Key Issue #8: Authentication of eRelay-UE

5.9  Key Issue #9: User Plane protection between eRemote-UE and eNB

6  Solutions

6.1  Solution #1: Authentication of eRemote-UE via eRelay-UE

6.2  Solution #2: eRemote-UE Authentication with MITM detectionWord‑p. 17

6.3  Solution #3: Authentication of eRelay-UE

6.4  Solution #4: Solution of Authorization for Indirect 3GPP Communication

6.5  Solution #5: Protection of the UP between eRemote-UE and eRelay-UE

6.6  Solution #6: Solution for protection of CP between eRemote-UE and Network

6.7  Solution #7: Solution of IMSI privacy for attach via eRelay-UE

6.8  Solution #8: eRelay Discovery

6.9  Solution #9: Path Switch of direct to indirect 3GPP Communication and vice versa

6.10  Solution #10: Handover of eRemote-UE from one eRelay to anotherWord‑p. 27

6.11  Solution #11: Handover of eRelay-UE

6.12  Solution #12: Enhancement of Setting Up Connection between eRemote-UE and eRelay-UE

6.13  Solution #13: Security Parameters Configuration on eRemote-UE during Dynamic Trust Relationship Establishment

7  Conclusions

$  Change HistoryWord‑p. 35


Up   Top