Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 33.825 Word version: 16.0.1

1… 5…

5 Key issues p. 8

5.1 Key Issue #1: Security for redundant transmission p. 8

5.1.1 Key issue details p. 8

5.1.2 Security threats p. 9

5.1.3 Potential Security requirements p. 9

5.2 Key issue #2: Support of security for high reliability by redundant data transmission in user plane p. 9

5.2.1 Key issue details p. 9

5.2.2 Security threats p. 10

5.2.3 Potential security requirements p. 10

5.3 Key Issue #3: UP security policy handling for multiple PDU sessions established for redundant data transmission p. 10

5.3.1 Key issue details p. 10

5.3.2 Security threats p. 11

5.3.3 Potential security requirements p. 11

5.4 Key Issue #4: Security policy for URLLC service p. 11

5.4.1 Key issue details p. 11

5.4.2 Security threats p. 11

5.4.3 Potential Security requirements p. 12

5.5 Key Issue #5: Security aspect of low latency handover procedure p. 12

5.5.1 Key issue details p. 12

5.5.2 Security threats p. 12

5.5.3 Potential Security requirements p. 12

5.6 Key Issue #6: Retaining AS security keys for redundant data transmission in user plane p. 12

5.6.1 Key issue details p. 12

5.6.2 Security threats p. 13

5.6.3 Potential security requirements p. 13

5.7 Key Issue #7: QoS monitoring protection p. 13

5.7.1 Key issue details p. 13

5.7.2 Security threats p. 13

5.7.3 Potential Security requirements p. 13

5.8 Key Issue #8: Acceleration of authentication and key agreement procedure for low latency p. 13

5.8.1 Key issue details p. 13

5.8.2 Security threats p. 13

5.8.3 Potential Security requirements p. 13

5.9 Key Issue #9: Security aspect of low latency Re-authentication procedure p. 14

5.9.1 Key issue details p. 14

5.9.2 Security threats p. 14

5.9.3 Potential security requirements p. 14

5.10 Key Issue #10: UP security performance for low latency p. 14

5.10.1 Key issue details p. 14

5.10.2 Security threats p. 14

5.10.3 Potential Security requirements p. 14

6 Candidate Solutions p. 15

6.1 Solution #1: Security solution for handling UP security policy for multiple PDU sessions for redundant data transmission p. 15

6.1.1 Introduction p. 15

6.1.2 Solution details p. 15

6.1.3 Evaluation p. 16

6.2 Solution #2: Retaining AS security keys for redundant data transmission in user plane p. 16

6.2.1 Introduction p. 16

6.2.2 Solution details p. 16

6.2.3 Evaluation p. 16

6.3 Solution #3: Security policy handling for redundant data transmission p. 16

6.3.1 Introduction p. 16

6.3.2 Solution details p. 17

6.3.3 Evaluation p. 18

6.4 Solution #4: Security support for N3 tunnel redundancy p. 18

6.4.1 Introduction p. 18

6.4.2 Solution details p. 18

6.4.3 Evaluation p. 19

6.5 Solution #5: Security for redundant data transmission p. 19

6.5.1 Introduction p. 19

6.5.2 Solution details p. 19

6.5.3 Evaluation p. 20

6.7 Solution #7: Security for redundant data transmission using Dual Connectivity p. 21

6.7.1 Introduction p. 21

6.7.2 Solution details p. 22

6.7.3 Evaluation p. 23

6.8 Solution #8: Handling of UP security activation status and selection of SN in Dual Connectivity p. 24

6.8.1 Introduction p. 24

6.8.2 Solution details p. 24

6.8.3 Evaluation p. 26

7 Conclusions p. 26

7.1 Key Issue #1: Security for redundant transmission p. 27

7.2 Key Issue #2: Support of security for high reliability by redundant data transmission in user plane p. 27

7.3 Key Issue #3: UP security policy handling for multiple PDU sessions established for redundant data transmission p. 28

7.4 Key Issue #4: Security policy for URLLC service p. 28

7.6 Key Issue #6: Retaining AS security keys for redundant data transmission in user plane p. 28

7.8 Key Issue #8: Acceleration of authentication and key agreement procedure for low latency p. 28

$ Change History p. 29