Content for TR 23.700-88 Word version: 18.0.0
6 Solutions p. 16
6.0 Mapping of Solutions to Key Issues p. 16
6.0A Solution #0A: 5GC architecture enhancements to support PIN p. 16
6.0A.1 Description p. 16
6.0A.2 Procedures p. 17
6.0A.2.1 5GC architecture enhancements to support PIN p. 17
6.0A.2.2 Additional Reference points p. 17
6.0A.2.3 Additional Network Functions and Entities p. 18
6.0A.2.4 Personal IoT Network Architecture p. 18
6.0A.3 Impacts on services, entities and interfaces p. 19
6.0B Solution #0B: Architecture alternative B p. 19
6.0B.1 Description p. 19
6.0B.2 Procedures p. 19
6.0B.3 Impacts on Existing Nodes and Functionality p. 22
6.0C Solution #0C: Architecture alternative C p. 22
6.0C.1 Description p. 22
6.0C.2 Procedures p. 23
6.0C.2.1 Overview of architecture p. 23
6.0C.2.2 Deployment and use case example p. 25
6.0C.2.3 Implementation examples without impact on PEMC p. 27
6.0C.2.4 Control plane of PIN p. 28
6.0C.2.4.1 PINE - PEMC (Pin1) p. 28
6.0C.2.4.2 PINE - PEGC (Pin2) p. 29
6.0C.2.4.3 PEMC - PINMF (Pin3) p. 29
6.0C.2.4.4 PEGC - PINMF (Pin4) p. 30
6.0C.2.4.5 PEMC - PEGC (Pin5) p. 31
6.0C.2.5 User plane of PIN p. 32
6.0C.2.6 Architecture reference model p. 33
6.0C.2.7 Reference points p. 34
6.0C.2.8 Network Functions and entities p. 34
6.0C.3 Impacts on Existing Nodes and Functionality p. 35
6.0D Solution #0D: Personal IoT Networks Architecture in 5GS p. 35
6.0D.1 Description p. 35
6.0D.2 Procedures p. 35
6.0D.2.1 Architecture of Personal IoT Networks in 5GS p. 35
6.0D.2.2 Reference points p. 36
6.0D.2.3 Network Functions and entities p. 36
6.0D.3 Impacts on Existing Nodes and Functionality p. 37
6.0E Solution#0E: PIN architecture p. 37
6.0E.1 Description p. 37
6.0E.2 Procedures p. 38
6.0E.2.1 Architecture of Personal IoT Networks in 5GS p. 38
6.0E.2.2 Reference points p. 38
6.0E.2.3 Network Functions and entities p. 38
6.0E.3 Impacts on Existing Nodes and Functionality p. 39
6.1 Solution #1: PIN and PIN element discovery and selection p. 39
6.1.1 Description p. 39
6.1.2 Procedures p. 39
6.1.2.1 PIN discovery and selection p. 39
6.1.2.2 Discoverability by other PIN elements p. 41
6.1.2.3 Discovery and selection of PEGC p. 42
6.1.3 Impacts on Existing Nodes and Functionality p. 43
6.2 Solution #2: PIN and PINE discovery and selection p. 43
6.2.1 Description p. 43
6.2.1.1 General p. 43
6.2.1.2 Functional description p. 44
6.2.2 Procedures p. 45
6.2.3 Impacts on services, entities and interfaces p. 45
6.3 Solution #3: Solution for PIN and PIN Elements discovery and selection p. 45
6.3.1 Description p. 45
6.3.2 Procedures p. 46
6.3.3 Impacts on Existing Nodes and Functionality p. 47
6.4A Solution #4A: PIN and PIN Element discovery by A PINE p. 47
6.4A.1 Description p. 47
6.4A.2 Procedures p. 47
6.4A.3 Impacts on Existing Nodes and Functionality p. 48
6.4B Solution #4B: PIN Elements with Gateway Capabilities (PEGC) discovery and selection by PEMC p. 48
6.4B.1 Description p. 48
6.4B.1.1 Introduction p. 48
6.4B.1.2 Functional Description p. 48
6.4B.2 Procedures p. 49
6.4B.3 Impacts on Existing Nodes and Functionality p. 49
6.5 Solution #5: Solution for authorization and management of PIN and PIN Elements p. 50
6.5.1 Description p. 50
6.5.1.0 General p. 50
6.5.1.1 Registration management of PEMC, PEGC and PINE p. 50
6.5.1.2 Management of PIN and PINE Elements p. 51
6.5.2 Procedures p. 51
6.5.2.1 PIN Elements registration and PIN management p. 51
6.5.2.2 PINE visiting to 5GC via PEGC p. 53
6.5.3 Impacts on Existing Nodes and Functionality p. 54
6.6 Solution #6: Management of PIN and PIN Elements p. 54
6.6.1 Description p. 54
6.6.2 Procedures p. 55
6.6.3 Impacts on services, entities, and interfaces p. 58
6.7 Solution #7: PIN Management and Communication p. 58
6.7.1 Description p. 58
6.7.2 Procedures p. 59
6.7.3 Impacts on services, entities and interfaces p. 63
6.8 Solution #8: Management of PIN and PIN Elements p. 64
6.8.1 Description p. 64
6.8.2 Procedures p. 66
6.8.2.1 Management of PIN without PINE/PEGC addition/removal p. 66
6.8.2.1.1 Registration of PEMC and registration of PINMF p. 66
6.8.2.1.2 Create a PIN p. 67
6.8.2.1.3 Update a PIN p. 68
6.8.2.1.4 Delete a PIN p. 68
6.8.2.1.5 Query PIN list information p. 69
6.8.2.1.6 Query PIN information p. 69
6.8.2.2 Management of PEGC and PINE p. 70
6.8.2.2.1 Registration of PINE p. 70
6.8.2.2.2 Registration of PEGC p. 71
6.8.2.2.3 Query device list information p. 74
6.8.2.2.4 Add/Update/Remove PINEs for a PIN p. 74
6.8.2.2.5 Add/Update/Remove PEGCs for a PIN p. 76
6.8.2.3 Management of association between PEGC and PINE p. 77
6.8.2.3.1 Create/Remove association between PEGC and PINE p. 77
6.8.2.3.2 Activate association p. 79
6.8.2.3.3 Deactivate association p. 80
6.8.2.4 Activate/Deactivate a PIN p. 81
6.8.3 Impacts on Existing Nodes and Functionality p. 81
6.9 Solution #9: PIN management and PINE management p. 82
6.9.1 Description p. 82
6.9.2 Procedures p. 83
6.9.2.1 PIN management p. 83
6.9.2.1.1 An authorized UE (PEMC) to create a PIN p. 83
6.9.2.1.2 PIN creation from 3rd party p. 84
6.9.2.1.3 PIN deleting triggered by UDM p. 85
6.9.2.2 PINE management p. 86
6.9.3 Impacts on Existing Nodes and Functionality p. 87
6.10 Solution #10: Management of PIN and PIN Elements p. 88
6.10.1 Description p. 88
6.10.1.1 General p. 88
6.10.1.2 Functional description p. 88
6.10.2 Procedures p. 89
6.10.2.1 PEMC Triggered Service Request to Update PIN_List Procedure p. 89
6.10.2.2 Network Triggered Service Request to Update PIN Policies Procedure p. 90
6.10.3 Impacts on services, entities and interfaces p. 91
6.11 Solution #11: Differentiated QoS between a PINE and 5GS when a PEGC is used for the relay p. 91
6.11.1 Description p. 91
6.11.1.1 Introduction p. 91
6.11.1.2 Solution principles p. 92
6.11.2 Procedures p. 92
6.11.3 Impacts on Existing Nodes and Functionality p. 93
6.12 Solution #12: Communication of PIN p. 93
6.12.1 Description p. 93
6.12.2 Procedures p. 94
6.12.2.1 Management of relay path p. 94
6.12.2.2 Mobile termination procedure for PINE p. 97
6.12.2.3 Support credential provisioning for PINE p. 99
6.12.3 Impacts on Existing Nodes and Functionality p. 100
6.13 Solution #13: Communication of PIN p. 101
6.13.1 Description p. 101
6.13.1.1 Communication between PINE and 5GS via PEGC p. 101
6.13.1.2 Communication between PIN elements within PIN p. 102
6.13.2 Procedures p. 103
6.13.3 Impacts on services, entities and interfaces p. 104
6.14 Solution #14: Discover PIN and PIN element via direct discovery p. 104
6.14.1 Description p. 104
6.14.2 Procedures p. 105
6.14.2.1 Procedures for policy and parameters provisioning for PIN p. 105
6.14.2.2 Procedures for PIN and PIN Element discovery p. 105
6.14.3 Impacts on services, entities and interfaces p. 106
6.15 Solution #15: Discovery of PIN/PINE Services via 5GC p. 106
6.15.1 Description p. 106
6.15.2 Procedures p. 106
6.15.2.1 PINE discovery via 5GC p. 106
6.15.2.2 Local PINE discovery p. 108
6.15.2.3 PIN discovery p. 108
6.15.3 Impacts on Existing Nodes and Functionality p. 109
6.16 Solution #16: Policy and QoS differentiation for PINE traffic relayed by PEGC and 5GS p. 109
6.16.1 Description p. 109
6.16.2 Procedures p. 110
6.16.3 Impacts on services, entities and interfaces p. 110
6.17 Solution #17: PIN Communication by local routing in 5GC p. 110
6.17.1 Description p. 110
6.17.2 Procedures p. 113
6.17.3 Impacts on Existing Nodes and Functionality p. 114
6.18 Solution #18: Delay budget between PINE and PEGC p. 114
6.18.1 Description p. 114
6.18.2 Procedures p. 115
6.18.3 Impacts on Existing Nodes and Functionality p. 116
6.19 Solution #19: QoS handling for PINE communication with 5GC via PEGC p. 117
6.19.1 Description p. 117
6.19.2 Procedures p. 117
6.19.2.1 Procedures for policy and parameters provisioning for PEGC p. 117
6.19.2.2 Procedures for QoS handling of PINE communication with 5GC via PEGC p. 118
6.19.3 Impacts on services, entities and interfaces p. 119
6.20 Solution #20: PIN communication using multiple PEGCs p. 119
6.20.1 Description p. 119
6.20.2 Procedures p. 121
6.20.3 Impacts on services, entities, and interfaces p. 122
6.21 Solution #21: Authorization of a PINE for PIN Access p. 122
6.21.1 Description p. 122
6.21.2 Procedures p. 123
6.21.3 Impacts on Existing Nodes and Functionality p. 124
6.22 Solution #22: PIN Authorization p. 124
6.22.1 Description p. 124
6.22.2 Procedures p. 126
6.22.2.1 Authorisation for PINE to PINE Communication authorisation Procedure p. 126
6.22.2.2 Authorisation for PINE accessing 5G communication via PEGC p. 127
6.22.3 Impacts on services, entities and interfaces p. 127
6.23 Solution #23: Policy provisioning framework for PIN p. 128
6.23.1 Description p. 128
6.23.2 Procedures p. 128
6.23.2.1 PIN Establishment with pre-provisioned PIN Policies p. 129
6.23.2.2 PIN establishment with dynamic Policy updates p. 130
6.23.2.3 PEMC initiated dynamic Policy retrieval p. 131
6.23.3 Impacts on Existing Nodes and Functionality p. 131
6.24 Solution #24: PIN Policy and Parameters Provisioning using the UE Configuration Update Procedure p. 132
6.24.1 Description p. 132
6.24.2 Procedures p. 132
6.24.2.1 General p. 132
6.24.2.2 Policy and parameters for PIN p. 132
6.24.3 Impacts on Existing Nodes and Functionality p. 133
6.25 Solution #25: Policy and Parameter provisioning for PIN p. 133
6.25.1 Description p. 133
6.25.2 Procedures p. 135
6.25.2.1 Registration with PIN_Capability and PIN_List Procedure p. 135
6.25.2.2 PEMC Triggered Service Request to Update PIN_List Procedure p. 136
6.25.2.3 Network Triggered Service Request to Update PIN Policies Procedure p. 137
6.25.3 Impacts on services, entities and interfaces p. 137
6.26 Solution #26: Solution for parameter provisioning of PIN subscription data p. 138
6.26.1 Description p. 138
6.26.2 Procedures p. 139
6.26.3 Impacts on services, entities and interfaces p. 140
6.27 Solution #27: Management for identification for PIN and PINE p. 141
6.27.1 Description p. 141
6.27.2 Procedures p. 141
6.27.2.1 Allocation for PINE identifier p. 141
6.27.2.1.1 New PINE identifier allocation when joining the PIN p. 141
6.27.2.1.2 New PINE identifier allocation when moving to new PEGC within same PIN p. 142
6.27.2.2 Allocation for PIN identifier p. 142
6.27.3 Impacts on Existing Nodes and Functionality p. 142
