Content for TR 23.700-48 Word version: 18.0.0
5 Key issues p. 14
5.1 KI#1: Accessing EHE in a VPLMN when roaming p. 14
5.2 KI#2: Fast and efficient network exposure improvements p. 15
5.2.1 Description p. 15
5.2.2 Use cases and scenarios p. 16
5.3 KI#3: Policies for finer granular sets of UEs p. 16
5.4 KI#4: Influencing UPF and EAS (re)location for collections of UEs p. 17
5.5 KI#5: GSMA OPG impacts and improvements for EHE operated by separate party p. 18
5.6 KI#6: Avoiding UE to switch away from EC PDU Session p. 19
5.7 KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI p. 20
6 Solutions p. 20
6.0 Solution-Key issue matrix p. 20
6.1 Solution 01 (KI#1): EAS discovery in Home Routed roaming scenario p. 22
6.1.1 Description p. 22
6.1.2 Procedures p. 23
6.1.2.1 EAS discovery when HPLMN has the knowledge of EAS deployment information in VPLMN p. 23
6.1.2.2 EAS discovery when HPLMN does not have the knowledge of EAS deployment information in VPLMN p. 24
6.1.3 Impacts on services, entities and interfaces p. 25
6.2 Solution 02 (KI#1): Session Breakout in Visited PLMN p. 26
6.2.1 Description p. 26
6.2.2 Procedure p. 27
6.2.3 Impacts on services, entities and interfaces p. 28
6.3 Solution 03 (KI#1): EAS (re)discovery procedure in roaming scenario p. 29
6.3.1 Description p. 29
6.3.2 Procedures p. 29
6.3.2.1 EAS discovery procedure in roaming scenario p. 29
6.3.2.2 EAS rediscovery procedure in roaming scenario p. 32
6.3.3 Impacts on existing entities and interfaces p. 32
6.4 Solution 04 (KI#1): Support EAS (re-)discovery in VPLMN via HR PDU Session p. 33
6.4.1 Description p. 33
6.4.2 Procedures p. 33
6.4.2.1 EAS discovery p. 33
6.4.2.2 EAS re-discovery p. 36
6.4.3 Impacts on services, entities and interfaces p. 37
6.5 Solution 05 (KI#1): Accessing V-EHE via HR PDU Session p. 39
6.5.1 Description p. 39
6.5.2 Procedures p. 40
6.5.2.1 EAS discovery p. 40
6.5.2.2 EAS re-discovery p. 41
6.5.3 Impacts on services, entities and interfaces p. 41
6.6 Solution 06 (KI#1): URSP solution to support roamers access to EHE in a VPLMN p. 42
6.6.1 Description p. 42
6.6.2 Procedures p. 43
6.6.3 Impacts on Existing Nodes and Functionality p. 43
6.7 Solution 07 (KI#1): Using URSP Rules to Establish an LBO PDU Session p. 43
6.7.1 Description p. 43
6.7.1.1 General p. 43
6.7.1.2 Procedure p. 44
6.7.2 Impacts on services, entities and interfaces p. 44
6.8 Solution 08 (KI#1): V-ECS Discovery during Steering of Roaming p. 45
6.8.1 Description p. 45
6.8.1.1 General p. 45
6.8.1.2 Procedure p. 45
6.8.2 Impacts on services, entities and interfaces p. 47
6.9 Solution 09 (KI#1): PDU Session configuration from EASDF p. 47
6.9.1 Description p. 47
6.9.2 Procedures p. 47
6.9.3 Impacts on services, entities and interfaces p. 49
6.10 Solution 10 (KI#1): LBO PDU Session establishment using PLMN criteria in RSD p. 49
6.10.1 Description p. 49
6.10.2 Procedure p. 50
6.10.3 Impacts on services, entities and interfaces p. 50
6.11 Solution 11 (KI#2): Exposure of Network Congestion p. 51
6.11.0 General p. 51
6.11.1 Procedure p. 51
6.11.2 Impacts on services, entities and interfaces p. 53
6.12 Solution 12 (KI#2): Efficient exposure of RAN information p. 54
6.12.1 Key Issue mapping p. 54
6.12.2 Description p. 54
6.12.3 Procedures p. 55
6.12.4 Impacts on services, entities and interfaces p. 57
6.13 Solution 13 (KI#2): Fast and efficient network exposure improvements p. 58
6.13.1 Introduction p. 58
6.13.2 Functional Description p. 58
6.13.3 Procedures p. 58
6.13.4 Impacts on services, entities and interfaces p. 60
6.14 Solution 14 (KI#4): Group Management p. 60
6.14.1 Introduction p. 60
6.14.2 Functional Description p. 60
6.14.3 Procedures p. 62
6.14.4 Impacts on services, entities and interfaces p. 64
6.15 Solution 15 (KI#4): Selection of common DNAI p. 64
6.15.1 Introduction p. 64
6.15.2 Functional Description p. 65
6.15.3 Procedures p. 65
6.15.3.1 General p. 65
6.15.3.2 Selection of the common DNAI p. 67
6.15.3.3 EAS selection and re-selection using ECS option, preconfigured p. 68
6.15.3.4 EAS selection and re-selection using ECS option, dynamic invoke of SCMF p. 69
6.15.3.5 EAS selection and re-selection via application layer p. 71
6.15.4 Impacts on services, entities and interfaces p. 72
6.16 Solution 16 (KI#4): Selecting the same EAS/DNAI for collection of UEs p. 72
6.16.1 Description p. 72
6.16.2 Procedures p. 73
6.16.3 Impacts on services, entities and interfaces p. 75
6.17 Solution 17 (KI#4): Application layer EAS selection for collections of UEs p. 75
6.17.1 Introduction p. 75
6.17.2 Functional Description p. 75
6.17.3 Procedures p. 76
6.17.4 Impacts on services, entities and interfaces p. 77
6.18 Solution 18 (KI#4): Discovery of the same EAS for collections of UEs p. 77
6.18.1 Description p. 77
6.18.2 Procedures p. 78
6.18.2.1 EASDF-related procedure p. 78
6.18.2.2 Direct DNS response to UE p. 80
6.18.2.3 EAS Discovery Procedure with Local DNS Server/Resolver p. 81
6.18.3 Impacts on services, entities and interfaces p. 81
6.19 Solution 19 (KI#4): Influencing UPF and EAS (re)location for collections of UEs p. 82
6.19.1 Introduction p. 82
6.19.2 Functional Description p. 82
6.19.3 Procedure p. 82
6.19.3.1 AF provisioning ad-hoc group information p. 82
6.19.3.2 Group members served by same SMF p. 83
6.19.4 Impacts on services, entities and interfaces p. 84
6.20 Solution 20 (KI#5): Global EASDF p. 84
6.20.1 Description p. 84
6.20.2 Procedures p. 85
6.20.2.1 Global EASDF p. 85
6.20.3 Impacts on services, entities and interfaces p. 86
6.21 Solution 21 (KI#5): EAS Deployment information differentiated by PLMN ID p. 86
6.21.1 Introduction p. 86
6.21.2 Functional Description p. 86
6.21.3 Procedures p. 86
6.21.4 Impacts on services, entities and interfaces p. 86
6.22 Solution 22 (KI#5): EAS discovery for Edge Node Sharing p. 87
6.22.1 Introduction p. 87
6.22.2 Functional description p. 87
6.22.2.0 Option 0: SMF configuration p. 87
6.22.2.1 Option 1: Shared EASDF p. 87
6.22.2.2 Option 2: Per-PLMN EASDFs p. 88
6.22.3 Procedures p. 90
6.22.3.0 Option 0: SMF configuration p. 90
6.22.3.1 Option 1: Shared EASDF p. 90
6.22.3.2 Option 2: Per-PLMN EASDFs p. 92
6.22.4 Impact on existing entities and interfaces p. 94
6.23 Solution 23 (KI#5): Improvements for EHE operated by separate party p. 94
6.24 Solution 24 (KI#1): Reuse Option D after UL-CL Insertion p. 96
6.24.1 Description p. 96
6.24.2 Procedure p. 97
6.24.3 Impacts on services, entities, and interfaces p. 97
6.25 Solution 25 (KI#1): EAS discovery in VPLMN via V-EASDF for a HR PDU Session p. 98
6.25.1 High level description p. 98
6.25.2 Procedures p. 99
6.25.2.1 PDU Session establishment and EAS discovery p. 99
6.25.2.2 EAS rediscovery due to UE or application mobility p. 101
6.25.3 Impacts on services, entities and interfaces p. 102
6.26 Solution 26 (KI#1): SM Policy for HR Session Breakout in VPLMN p. 103
6.26.1 Description p. 103
6.26.2 Procedures p. 104
6.26.2.1 Option 1: Indirect interaction between V-PCF and H-PCF p. 104
6.26.2.2 Option 2: Direct interaction between V-PCF and H-PCF p. 105
6.26.3 Impacts on existing entities and interfaces p. 106
6.27 Solution 27 (KI#1): EAS discovery with dynamic setup of a LBO PDU Session p. 107
6.27.1 High level description p. 107
6.27.2 Procedures p. 108
6.27.3 Impacts on services, entities and interfaces p. 109
6.28 Solution 28 (KI#1): Support edge computing in Roaming p. 109
6.28.1 Description p. 109
6.28.1.1 General p. 109
6.28.1.2 ECS configuration information Configuration Information configuration in UE p. 110
6.28.2 Procedures p. 110
6.28.2.1 UE registers in VPLMN and URSP rules updated timely p. 110
6.28.2.2 UE registers in VPLMN and URSP rules are not updated timely p. 111
6.28.2.3 HR session to support Edge computing p. 111
6.28.2.4 When UE moving into VPLMN and the original EC-session are impacted p. 113
6.28.3 Impacts on services, entities and interfaces p. 113
6.29 Solution 29 (KI#3): Use of Internal Group ID and constraints in EDI p. 114
6.30 Solution 30 (KI#3): Policies referring to "Allowed services" and/or "Subscriber categories" p. 115
6.30.1 Description p. 115
6.30.2 Procedures p. 116
6.30.3 Impacts on Existing Nodes and Functionality p. 117
6.31 Solution 31 (KI#3): Providing traffic offload policy for a set of UEs with service information p. 118
6.31.1 Description p. 118
6.31.2 Procedures p. 118
6.31.3 Impacts on services, entities and interfaces p. 120
6.32 Solution 32 (KI#3): Offload policy for finer granular set of UEs p. 121
6.32.1 Description p. 121
6.32.2 Procedures p. 121
6.32.3 Impacts on services, entities and interfaces p. 122
6.33 Solution 33 (KI#3): AF requests offload policy for sets of UEs p. 122
6.33.1 Description p. 122
6.33.2 Procedures p. 123
6.33.3 Impacts on services, entities and interfaces p. 123
6.34 Solution 34 (KI#4): Selecting the same EAS/DNAI for collection of UEs p. 123
6.34.1 Description p. 123
6.34.2 Procedure p. 125
6.34.3 Impacts on services, entities and interfaces p. 126
6.35 Solution 35 (KI#4): Providing dedicated (re)location information as traffic routing information p. 126
6.35.1 Description p. 126
6.35.2 Procedures p. 127
6.35.3 Impacts on services, entities and interfaces p. 130
6.36 Solution 36 (KI#4): Providing dedicated (re)location information as EAS Deployment information p. 130
6.36.1 Description p. 130
6.36.2 Procedures p. 131
6.36.3 Impacts on services, entities and interfaces p. 133
6.37 Solution 37 (KI#4): (Re)location of same EAS and coordination across UEs p. 134
6.37.1 Introduction p. 134
6.37.2 Functional Description p. 134
6.37.3 Solution Details p. 134
6.37.3.1 EAS (re)location to the ad hoc group member UEs p. 134
6.37.3.2 Updating EAS ID in the Group Info p. 135
6.37.3.3 Collection of UEs based on 5GC criteria p. 136
6.37.4 Impacts on services, entities and interfaces p. 136
6.38 Solution 38 (KI#5): EAS Discovery for EHE shared with other PLMN p. 136
6.38.1 Description p. 136
6.38.2 Procedures p. 137
6.38.2.1 Option1 - NEF-based EDI provision to serving Operator p. 137
6.38.2.2 Option2 - EWBI/AF-based EDI provision to serving Operator p. 138
6.38.3 Impacts on services, entities and interfaces p. 139
6.39 Solution 39 (KI#1, KI#5): Support EAS relocation of inter-PLMN p. 139
6.39.1 Description p. 139
6.39.2 Procedures p. 141
6.39.2.1 EAS relocation from VPLMN to HPLMN (KI#1) p. 141
6.39.2.2 EAS relocation from HPLMN to VPLMN (KI#1) p. 142
6.39.2.3 EAS relocation between operators via N6 (KI #5) p. 143
6.39.3 Impacts on services, entities and interfaces p. 144
6.40 Solution 40 (KI#5): EAS discovery for shared EHE p. 145
6.40.1 Introduction p. 145
6.40.2 Functional description p. 145
6.40.3 Procedures p. 147
6.40.4 Impacts on existing entities and interfaces p. 148
6.41 Solution 41 (KI#6): Controlling non-3GPP access of EC traffic via URSP and ATSSS p. 148
6.41.1 High level description p. 148
6.41.2 Procedures p. 149
6.41.3 Impacts on services, entities and interfaces p. 150
6.42 Solution 42 (KI#6): Network-guided EC traffic switching p. 151
6.42.1 General p. 151
6.42.1.1 Introduction p. 151
6.42.1.2 Description p. 151
6.42.1.3 WLAN offload guided by the network p. 151
6.42.2 Procedures p. 152
6.42.3 Impacts to existing nodes p. 153
6.43 Solution 43 (KI#6): Network-based solution for keeping EC traffic on 3GPP Access p. 153
6.43.1 Description p. 153
6.43.2 Procedures p. 154
6.43.2.1 Network sides rejects EC-PDU Sessions handover from 3GPP Access to non-3GPP Access p. 154
6.43.2.2 UE decides PDU Session handover according to NWDAF analytics p. 154
6.43.4 Impacts on services, entities and interfaces p. 156
6.44 Solution 44 (KI#6): EAS traffic switching avoidance p. 156
6.44.1 Description p. 156
6.44.2 Procedures p. 157
6.44.3 Impacts on existing entities and interfaces p. 158
6.45 Solution 45 (KI#1, KI#6): Application selected PDU Session p. 158
6.45.1 Description p. 158
6.45.2 Procedures p. 159
6.45.3 Impacts on services, entities and interfaces p. 159
6.46 Solution 46 (KI#6): Avoid UE switching on-going EC traffic away from 3GPP access p. 159
6.46.1 Description p. 159
6.46.2 Procedure p. 159
6.46.3 Impacts on services, entities and interfaces p. 160
6.47 Solution 47 (KI#6): Avoiding Switch Away Based on an SMF Indication p. 161
6.47.1 Description p. 161
6.47.1.1 General p. 161
6.47.1.2 Procedure p. 161
6.47.2 Impacts on services, entities and interfaces p. 162
6.48 Solution 48 (KI#6): Avoiding Switch Away Based on an Indication in the URSP p. 163
6.48.1 Description p. 163
6.48.1.1 General p. 163
6.48.1.2 Procedure p. 163
6.48.2 Impacts on services, entities and interfaces p. 163
6.49 Solution 49 (KI#6): URSP based solution to avoid UE to switch away from Edge PDU Session p. 163
6.49.1 Introduction p. 163
6.49.2 Functional Description p. 164
6.49.3 Procedure p. 164
6.49.4 Impacts on services, entities and interfaces p. 165
6.50 Solution 50 (KI#7): Obtain and maintain mapping table between IP address/IP range with DNAI p. 165
6.50.1 Key Issue mapping p. 165
6.50.2 Description p. 165
6.50.3 Procedures p. 166
6.50.4 Impacts on existing entities and interfaces p. 166
6.51 Solution 51 (KI#7): EDI holding the IP address to DNAI mapping p. 166
6.51.1 High level description p. 166
6.51.2 High level procedures p. 167
6.51.3 Impacts on services, entities and interfaces p. 168
6.52 Solution 52 (KI#7): AF obtaining target DNAI provided by NEF p. 168
6.52.1 Description p. 168
6.52.2 Procedure p. 169
6.52.3 Impacts on services, entities and interfaces p. 169
6.53 Solution 53 (KI#1): EDC-based EAS discovery for HR PDU Session with Session Breakout p. 170
6.53.1 High level description p. 170
6.53.2 Procedures p. 170
6.53.3 Impacts on services, entities and interfaces p. 172
6.54 Solution 54 (KI#4): PCF controlling common DNAI p. 173
6.54.1 Description p. 173
6.54.2 Procedure p. 173
6.54.3 Impacts on Existing Nodes and Functionality p. 173
6.55 Solution 55 (KI#5): Access the shared EAS via N9 tunnel p. 173
6.55.1 Description p. 173
6.55.2 Procedure p. 174
6.55.2.1 Determine target DNAI in PLMN A according to EAS IP address p. 174
6.55.2.2 SMF recovers or obtain the mapping table to determine the target DNAI p. 174
6.55.2.3 EAS discovery procedure and access the shared EAS via N9 tunnel p. 175
6.55.3 Impacts on services, entities and interfaces p. 177
7 Evaluation p. 177
7.1 Evaluation for KI#1: Accessing EHE in a VPLMN when roaming p. 177
7.1.1 Evaluation for scenario 1 (via LBO PDU Session) p. 177
7.1.2 Evaluation for scenario 2 (via HR PDU Session) p. 179
7.1.3 Evaluation for ECS address delivery aspects p. 181
7.2 Evaluation for KI#2: Fast and efficient network exposure improvements p. 183
7.3 Evaluation for KI#3: Policies for finer granular sets of UEs p. 183
7.4 Evaluation for KI#4: Influencing UPF and EAS (re)location for collections of UEs p. 184
7.5 Evaluation for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party p. 186
7.6 Evaluation for KI#6: Avoiding UE to switch away from EC PDU Session p. 187
7.7 Evaluation for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI p. 189
8 Conclusions p. 190
8.1 Conclusion for KI#1: Accessing EHE in a VPLMN when roaming p. 190
8.1.1 Conclusion for scenario 1 (via LBO PDU Session) p. 190
8.1.2 Conclusion for scenario 2 (via HR PDU Session) p. 190
8.1.3 Conclusion for ECS Address Configuration Information delivery p. 191
8.2 Conclusion for KI#2: Fast and efficient network exposure improvements p. 192
8.3 Conclusion for KI#3: Policies for finer granular sets of UEs p. 192
8.4 Conclusion for KI#4: Influencing UPF and EAS (re)location for collections of UEs p. 193
8.5 Conclusion for KI#5: GSMA OPG impacts and improvements for EHE operated by separate party p. 194
8.6 Conclusion for KI#6: Avoiding UE to switch away from EC PDU Session p. 195
8.7 Conclusion for KI#7: Obtain and maintain mapping table between IP address/IP range with DNAI p. 195
$ Change history p. 196
