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 23.700-78 Word version: 18.1.0

1… 4…

4 Key issues p. 10

4.1 Key issue #1: PIN Management p. 10

4.2 Key issue #2: PINAPP accesses 5G network by application mechanism p. 11

4.3 Key issue #3: Service switch in PIN p. 11

4.4 Key issue #4: PIN Application Server Discovery p. 11

4.5 Key issue #5: Service continuity p. 12

4.6 Key issue #6: PEMC/PEGC replacement in PIN p. 12

5 Architecture requirements p. 13

5.1 General p. 13

5.2 Requirements p. 13

5.2.1 General requirements p. 13

5.2.1.1 General p. 13

5.2.1.2 Requirements p. 13

5.2.2 PIN Management p. 13

5.2.2.1 General p. 13

5.2.2.2 Requirements p. 13

5.2.3 PIN enable 5GS communication p. 14

5.2.3.1 General p. 14

5.2.3.2 Requirements p. 14

5.2.4 Service Switch p. 14

5.2.4.1 General p. 14

5.2.4.2 Requirements p. 14

5.2.5 Application server discovery p. 14

5.2.5.1 General p. 14

5.2.5.2 Requirements p. 14

5.2.6 Service continuity p. 14

5.2.6.1 General p. 14

5.2.6.2 Requirements p. 15

6 Architecture p. 15

6.1 General p. 15

7 Solutions p. 16

7.1 Mapping of solutions to key issues p. 16

7.2 Solution #1: PINAPP architecture p. 16

7.2.1 Architecture assumption p. 16

7.2.1.1 User accessing services provided by PIN Element from outside the PIN p. 17

7.2.2 Functional elements p. 18

7.2.2.1 PIN element with Management Capabilities (PEMC) p. 18

7.2.2.2 PIN Server p. 18

7.2.2.3 PIN element with Gateway Capabilities (PEGC) p. 19

7.2.2.4 PIN client p. 19

7.2.2.5 Application client p. 19

7.2.3 Reference Points p. 19

7.2.4 Functional Entity Cardinality p. 20

7.2.4.1 PEMC p. 20

7.2.4.2 PEGC p. 20

7.2.4.3 PIN server p. 20

7.2.4.4 PIN client p. 21

7.2.4.5 Application client p. 21

7.2.5 Identities p. 21

7.2.5.1 PIN ID p. 21

7.2.5.2 UE identifier p. 21

7.2.5.3 PIN client ID p. 21

7.2.5.4 Application Client ID p. 21

7.2.5.5 PIN server ID p. 21

7.3 Solution #2: PIN management p. 21

7.3.1 Architecture enhancements p. 21

7.3.2 Solution description p. 21

7.3.2.1 General p. 21

7.3.2.2 Procedures of Creation of PIN p. 22

7.3.2.3 Procedures of Modification of PIN p. 24

7.3.2.3.1 PIN modification triggered by PEMC p. 24

7.3.2.3.2 PIN modification triggered by event of PEGC p. 26

7.3.2.3.3 PEMC replacement triggered by PIN server p. 26

7.3.2.3.4 PEMC replacement triggered internally within the PIN p. 27

7.3.2.3.5 PEGC replacement triggered by PEMC p. 28

7.3.2.3.6 PIN modification triggered by PEGC p. 29

7.3.2.3.7 PIN modification triggered after local PEMC failure p. 31

7.3.2.3.8 PIN management with multiple PEGCs p. 31

7.3.2.3.9 PIN management with multiple PEMCs p. 32

7.3.2.4 Procedures of PIN Profile retrieval p. 33

7.3.3 Solution evaluation p. 34

7.4 Solution #3: Insertion and remove of PIN elements in a PIN p. 34

7.4.1 Architecture enhancements p. 34

7.4.2 Solution description p. 34

7.4.2.1 General p. 34

7.4.2.2 Procedures p. 35

7.4.2.2.1 PIN client requests to join into a PIN p. 35

7.4.2.2.2 The PEMC removes the PIN elements from a PIN p. 36

7.4.2.2.3 The PIN elements decides to leave the PIN p. 37

7.5 Solution #4: PIN delete p. 38

7.5.1 Architecture enhancements p. 38

7.5.2 Solution description p. 38

7.5.2.1 General p. 38

7.5.2.2 Procedures of Delete of PIN p. 38

7.5.2.2.1 PIN delete triggered by PEMC p. 38

7.5.2.2.2 PIN delete triggered by PIN server p. 39

7.5.2.2.3 PIN delete locally by PEMC p. 40

7.6 Solution #5: PIN discovery p. 41

7.6.1 Architecture enhancements p. 41

7.6.2 Solution description p. 41

7.6.2.1 General p. 41

7.6.2.2 Procedures of PIN discovery p. 42

7.6.2.2.1 Procedures of PIN discovery based on PEMC p. 42

7.6.2.2.2 Procedures of PIN discovery with assistance of PIN server via PEGC p. 43

7.7 Solution #6: PIN Profile p. 44

7.7.1 Architecture enhancements p. 44

7.7.2 Solution description p. 44

7.7.2.1 General p. 44

7.7.2.2 PIN Profile in a PIN p. 45

7.7.2.3 Dynamic profile information of a PIN p. 45

7.7.2.4 PIN client profile p. 47

7.7.3 Solution evaluation p. 47

7.8 Solution #7: PIN server discovery p. 48

7.8.1 Architecture enhancements p. 48

7.8.2 Solution description p. 48

7.8.2.1 General p. 48

7.8.2.2 Procedures of PIN server discovery p. 48

7.8.2.2.1 Procedures of PIN server discovery based on receiving PIN server endpoint information p. 48

7.8.2.2.2 Procedures of PIN server discovery via PEGC p. 48

7.8.2.2.3 Procedures of PIN server discovery from PEMC p. 49

7.9 Solution #8: Service switch in a PIN p. 50

7.9.1 Architecture enhancements p. 50

7.9.2 Solution description p. 50

7.9.2.1 General p. 50

7.9.2.2 Procedure p. 50

7.9.2.2.1 Functional entities p. 50

7.9.2.2.2 Procedures of PIN Service Switch p. 50

7.9.3 Solution evaluation p. 52

7.10 Solution #9: PINAPP role change p. 53

7.10.1 Architecture enhancements p. 53

7.10.2 Solution description p. 53

7.10.2.1 General p. 53

7.10.2.2 Procedure p. 53

7.10.3 Solution evaluation p. 54

7.11 Solution #10: Service switch internal PIN p. 54

7.11.1 Architecture assumptions p. 54

7.11.2 Solution description p. 54

7.11.2.1 General p. 54

7.11.2.2 Procedure of service switch internal PIN p. 55

7.11.3 Solution evaluation p. 56

7.12 Solution #11: Application Server Discovery in a PIN p. 56

7.12.1 Architecture enhancements p. 56

7.12.2 Solution description p. 56

7.12.2.1 General p. 56

7.12.2.2 Procedure p. 56

7.12.2.2.1 Functional entities p. 57

7.12.2.2.2 Procedures of PIN Application Server Discovery p. 57

7.12.3 Solution evaluation p. 58

7.13 Solution #12: PEMC registration to PIN server p. 58

7.13.1 Architecture enhancements p. 58

7.13.2 Solution description p. 58

7.13.2.1 General p. 58

7.13.2.2 Procedures of PEMC registration p. 59

7.13.2.3 Procedures of PINE/PEGC registration p. 59

7.14 Solution #13: SEAL enabled PINAPP architecture and PIN management p. 60

7.14.1 Architecture assumption p. 60

7.14.2 PIN creation p. 61

7.14.3 PIN update p. 61

7.14.4 PIN deletion p. 61

7.14.5 PIN discovery and PIN element discovery p. 61

7.15 Solution #14: PIN communication via 5GS p. 61

7.15.1 Architecture enhancements p. 61

7.15.2 Solution description p. 61

7.15.2.1 General p. 61

7.15.2.2 Procedures of PIN communication via 5GS p. 62

7.15.2.3 Procedures of credential provisioning to PINE via 5GS p. 63

7.16 Solution #15: Service continuity p. 65

7.16.1 Architecture enhancements p. 65

7.16.2 Solution description p. 65

7.16.2.1 General p. 65

7.16.2.2 Procedures to support service continuity p. 66

7.16.2.2.1 PEGC relocation p. 66

7.16.2.2.2 Change application layer communication to communication via 5GS, with the support of PIN server p. 67

8 Deployment scenarios p. 76

8.1 General p. 76

9 Overall evaluation p. 76

9.1 Architecture enhancements p. 76

9.2 Key issue evaluations p. 76

9.2.1 General p. 76

9.2.2 Evaluation of key issue #1: PIN Management p. 78

9.2.3 Evaluation of key issue #2: PINAPP accesses 5G network by application mechanism p. 81

9.2.4 Evaluation of key issue #3: Service switch in PIN p. 81

9.2.5 Evaluation of key issue #4: PIN Application Server Discovery p. 83

9.2.6 Evaluation of key issue #5: Service continuity p. 83

9.2.7 Evaluation of key issue #6: PEMC/PEGC replacement in PIN p. 84

9.2.8 Evaluation of PINAPP architecture p. 85

10 Conclusions p. 85

10.1 Conclusion of PIN management of KI#1 p. 85

10.2 Conclusion of KI#2 p. 87

10.3 Conclusion of Service Switch of KI#3 p. 88

$ Change history p. 90