Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.733  Word version:  15.1.0

Top   Top   Up   Prev   None
1…   4…

 

4  Architectural considerationsp. 9

5  Key issuesp. 12

6  Solutionsp. 15

6.1  Solutions to Key Issue 1p. 15

6.1.1  Solution 1: Subscription based authorisationp. 15

6.1.2  Solution 2: Authorisation of eRelay-UE and eRemote-UEp. 16

6.1.3  Solution 3: Authorisation for Indirect 3GPP Communication via MMEp. 20

6.1.4  Solution 4: Dynamic Trust relationship establishment using ProSe function/PC3p. 24

6.1.4B  Solution 4B: Dynamic Trust relationship establishment for MME based authorisationp. 26

6.1.5  Solution 5: Independent UE Authentication and Authorisation for Indirect 3GPP Communication via MMEp. 28

6.1.6  Solution 6: Simplified authorisation of eRelay-UE and eRemote-UEp. 31

6.2  Solutions to Key Issue 2p. 35

6.3  Solutions to Key Issue 3p. 39

6.4  Solutions to Key Issue 4p. 42

6.5  Solutions to Key Issue 5p. 42

6.5.1  Solution 1: NAS Based Service Continuity Solutionp. 42

6.5.2  Solution 2: AS based Service Continuity Solutionp. 47

6.5.3  Solution 3: Switching between direct and indirect communicationp. 54

6.5.4  Solution 4: Simplified NAS Based Service Continuity Solutionp. 56

6.5.5  Solution 5: Handover of eRelay-UE with eRemote-UE(s) having an active indirect connectionp. 61

6.6  Solutions to Key Issue 6p. 64

7  Overall evaluationp. 72

8  Conclusionsp. 76

A  Combined Solution 1p. 77

B  Solution based on L3 Relay architecturep. 79

$  Change Historyp. 81


Up   Top