Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.807  Word version:  16.0.1

Top   Top   Up   Prev   None
1…   5…

 

5  Key issuesp. 9

5.1  Key Issue #1: security of 5G-RGp. 9

5.2  Key Issue #2: FN-RG authentication and authorizationp. 10

5.3  Key Issue #3: Transport security for the interfaces between W-5GAN and 5GCp. 10

5.4  Key Issue #4: Security for the interface between 5G-RG and W-5GANp. 11

5.5  Key Issue #5: Registration and NAS transport for trusted non-3GPP accessp. 11

5.6  Key Issue #6: Access to 5GC from WLAN UEs that do not support NASp. 11

5.7  Key Issue #7: Authentication of 5G capable UE behind a RGp. 12

5.8  Key Issue #8: User plane data handling for 5G capable UE behind a RGp. 12

5.9  Key Issue #9: User plane security for 5G-RG or FN-RG to 5GCp. 13

5.10  Key Issue #10: NAS termination in Trusted WLAN Interworking Function (TWIF)p. 13

5.11  Key Issue #11: NAS termination for FN-RGp. 14

5.12  Key Issue #12: Protection of Line Idp. 14

5.13  Key Issue 13: Mobility between TNAPs within the Trusted Non-3GPP Access Network (TNAN)p. 15

5.14  Key Issue #14: Mobility between TNGFs within the Trusted Non-3GPP Access Network (TNAN)p. 15

5.15  Key Issue #15: N3GPP Key Separationp. 16

5.16  Key Issue #16: Missing SUCI-to-SUPI mapping for the FN-RGp. 17

6  Solutionsp. 17

6.1  Solution #1: Solution for trusted non-3GPP accessp. 17

6.2  Solution #2: 5GC-capable UEs behind 5G-RG/FN-RG using N3GPP-access solutionsp. 21

6.3  Solution #3: 5G-RG connecting to 5GC via W-5GANp. 22

6.4  Solution #4: FN-RG registration to 5GCp. 23

6.5  Solution #5: 5G-RG connecting to 5GC via NG-RAN (FWA)p. 24

6.6  Solution #6: Solution for 5GC access from WLAN UEs that do not support NASp. 25

6.7  Solution #7: Key separation for untrusted and trusted accessp. 28

6.8  Solution #8: Transport security for the interfaces between W-5GAN and 5GCp. 29

6.9  Solution #9: Solution on Line ID protectionp. 30

7  Conclusionsp. 30

$  Change Historyp. 33


Up   Top