Content for TR 23.700-98 Word version: 18.1.0
7 Solutions p. 47
7.0 Mapping of solutions to key issues p. 47
7.1 Solution #1: Service provisioning via push notification p. 49
7.1.1 Architecture enhancements p. 49
7.1.2 Solution description p. 49
7.1.2.1 General p. 49
7.1.2.2 Procedure p. 49
7.1.3 Solution evaluation p. 50
7.2 Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection p. 51
7.2.1 Architecture enhancements p. 51
7.2.2 Solution description p. 51
7.2.3 Solution evaluation p. 52
7.3 Solution #3: Service provisioning triggering via SMS over NAS p. 52
7.3.1 Architecture enhancements p. 52
7.3.2 Solution description p. 52
7.3.2.1 General p. 52
7.3.2.2 Procedure p. 52
7.3.3 Solution evaluation p. 54
7.4 Solution #4: ECS discovery through serving ECS to support edge services across ECSPs p. 54
7.4.1 Architecture enhancements p. 54
7.4.2 Solution description p. 54
7.4.2.1 General p. 54
7.4.2.2 Procedure p. 55
7.4.3 Solution evaluation p. 56
7.5 Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs p. 56
7.5.1 Architecture enhancements p. 56
7.5.2 Solution description p. 57
7.5.2.1 General p. 57
7.5.2.2 Procedure p. 57
7.5.3 Solution evaluation p. 59
7.6 Solution #6: ACR update in service continuity planning p. 59
7.6.1 Architecture enhancements p. 59
7.6.2 Solution description p. 59
7.6.3 Solution evaluation p. 62
7.7 Solution #7: EES monitors UE mobility for service continuity planning p. 62
7.7.1 Architecture enhancements p. 62
7.7.2 Solution description p. 62
7.7.2.1 General p. 62
7.7.2.2 Procedure p. 62
7.7.3 Solution evaluation p. 64
7.8 Solution #8: EAS Service API enablement using CAPIF p. 64
7.8.1 Architecture enhancements p. 64
7.8.2 Solution description p. 65
7.8.2.1 General p. 65
7.8.2.2 CAPIF operations in Edge Enabler Layer p. 65
7.8.2.3 Service KPIs in CAPIF for EAS Service APIs p. 67
7.8.3 Solution evaluation p. 71
7.9 Solution #9: Application traffic influence trigger from EAS p. 71
7.9.1 Architecture enhancements p. 71
7.9.2 Solution description p. 71
7.9.2.1 General p. 71
7.9.2.2 Procedure p. 71
7.10 Solution #10: low power mode support p. 72
7.10.1 Architecture enhancements p. 72
7.10.2 Solution description p. 72
7.10.2.1 General p. 72
7.10.2.2 Procedure p. 73
7.11 Solution #11: A deployment option for alignment with ETSI MEC using CAPIF p. 74
7.11.1 Architecture enhancements p. 74
7.11.2 Solution description p. 74
7.11.2.1 General p. 74
7.11.2.2 Procedure p. 75
7.11.3 Solution evaluation p. 75
7.12 Solution #12: Service continuity planning permission p. 75
7.12.1 Architecture enhancements p. 75
7.12.2 Solution description p. 76
7.12.2.1 General p. 76
7.12.2.2 Procedure p. 76
7.12.3 Solution evaluation p. 77
7.13 Solution #13: Update ECS configuration information p. 77
7.13.1 Architecture enhancements p. 77
7.13.2 Solution description p. 77
7.13.3 Solution evaluation p. 78
7.14 Solution #14: V-ECS Discovery via the H-ECS p. 78
7.14.1 Architecture enhancements p. 78
7.14.2 Solution description p. 78
7.14.2.1 General p. 78
7.14.2.2 Procedure p. 78
7.14.3 Solution evaluation p. 81
7.15 Solution #15: Initial EAS selection declaration p. 81
7.15.1 Architecture enhancements p. 81
7.15.2 Solution description p. 81
7.15.3 Solution evaluation p. 83
7.16 Solution #16: EAS discovery for different users p. 83
7.16.1 Architecture enhancements p. 83
7.16.2 Solution description p. 83
7.16.2.1 General p. 83
7.16.2.2 Procedure p. 83
7.16.3 Solution evaluation p. 83
7.17 Solution #17: Traffic influence for initial EAS discovery p. 84
7.17.1 Architecture enhancements p. 84
7.17.2 Solution description p. 84
7.17.2.1 General p. 84
7.17.2.2 Procedure p. 84
7.17.3 Solution evaluation p. 84
7.18 Solution #18: Constraint device in EDGEAPP p. 85
7.18.1 Architecture enhancements p. 85
7.18.2 Solution description p. 85
7.18.3 Solution evaluation p. 86
7.19 Solution #19: EES determines the selected ACR scenario p. 87
7.19.1 Architecture enhancements p. 87
7.19.2 Solution description p. 87
7.19.2.1 General p. 87
7.19.2.2 Procedure p. 87
7.19.3 Solution evaluation p. 88
7.20 Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server p. 88
7.20.1 Architecture enhancements p. 88
7.20.2 Solution description p. 88
7.20.2.1 General p. 88
7.20.2.2 Notification delivery over a direct Notification Channel Procedure p. 88
7.20.2.3 Notification delivery using a Push Server Procedure (indirect Notification Channel) p. 90
7.20.3 Solution evaluation p. 92
7.21 Solution #21: Prediction expiration time for service continuity planning enhancement p. 92
7.21.1 Architecture enhancements p. 92
7.21.2 Solution description p. 92
7.21.2.1 General p. 92
7.21.2.2 Procedure p. 93
7.21.3 Solution evaluation p. 94
7.22 Solution #22: Support simultaneous EAS connectivity in ACR p. 94
7.22.1 Architecture enhancements p. 94
7.22.2 Solution description p. 94
7.22.3 Solution evaluation p. 97
7.23 Solution #23: UE identification with NAT p. 97
7.23.1 Architecture enhancements p. 97
7.23.2 Solution description p. 97
7.23.2.1 General p. 97
7.23.2.2 Procedure p. 98
7.23.3 Solution evaluation p. 99
7.24 Solution #24: ACR between EAS and CAS with CES p. 100
7.24.1 Architecture enhancements p. 100
7.24.2 Solution description p. 100
7.24.2.0 General p. 100
7.24.2.1 ACR Scenarios p. 101
7.24.3 Solution evaluation p. 101
7.25 Solution #25: ACR between EAS and CAS without CES p. 101
7.25.1 Architecture enhancements p. 101
7.25.2 Solution description p. 101
7.25.2.1 General p. 101
7.25.2.2 Procedure p. 101
7.25.2.2.1 Updated 3GPP TS 23.558 clause 8.8.2.2 Initiation by EEC using regular EAS Discovery p. 101
7.25.2.2.2 Updated 3GPP TS 23.558 clause 8.8.2.3 EEC executed ACR via S-EES p. 103
7.25.2.2.3 Updated 3GPP TS 23.558 clause 8.8.2.4 S-EAS decided ACR scenario p. 105
7.25.2.2.4 Updated 3GPP TS 23.558 clause 8.8.2.5 S-EES executed ACR p. 107
7.25.2.2.5 EEC initiated ACR p. 109
7.25.2.2.6 CAS initiated ACR p. 109
7.25.3 Solution evaluation p. 112
7.26 Solution #26: Bundled EASs p. 112
7.26.1 Architecture enhancements p. 112
7.26.2 Solution description p. 112
7.26.2.1 General p. 112
7.26.2.2 Handling of EAS bundle information by the EEC p. 116
7.26.2.3 Handling of EAS bundle information and EAS bundle requirements by the EES p. 116
7.26.2.4 Handling of EAS bundle information by the ECS p. 116
7.26.2.5 Handling of EAS bundle when the bundle EAS are registered on the multiple EESs in the same EDN p. 117
8.2.6 EES Profile p. 121
7.26.3 Solution evaluation p. 122
7.27 Solution #27: Enabling AC Association Aware services by selecting common EASs p. 123
7.27.1 Architecture enhancements p. 123
7.27.2 Solution description p. 123
7.27.2.1 General p. 123
7.27.2.2 New Information Elements p. 123
7.27.2.3 Enhancements to existing Information Elements p. 125
7.27.2.4 Enhancements to Service Provisioning for determining common EES p. 127
7.27.2.4.1 Using the "assumed common EES" option (option i) p. 127
7.27.2.4.2 Determining common EES with CAAR (option ii) p. 127
7.27.2.5 Enhancements to EAS Discovery for determining common EAS p. 128
7.27.2.6 Enhancements to ACR p. 128
7.27.2.7 Other procedural enhancements p. 129
7.27.2.8 New procedures p. 130
7.27.3 Solution evaluation p. 130
7.28 Solution #28: Common EAS discovery using EAS selection information p. 131
7.28.1 Architecture enhancements p. 131
7.28.2 Solution description p. 131
7.28.2.1 General p. 131
7.28.2.2 Procedure p. 131
7.28.3 Solution evaluation p. 133
7.29 Solution #29: Discovery of a common EAS p. 133
7.29.1 Architecture enhancements p. 133
7.29.2 Solution description p. 134
7.29.2.1 General p. 134
7.29.2.2 Procedure p. 135
7.29.2.3 Enhanced Service provisioning request p. 137
7.29.2.4 Enhanced EAS discovery filters p. 137
7.29.2.5 New Group profile common information element p. 139
7.29.2.6 Enhanced EDN configuration information p. 139
7.29.3 Solution evaluation p. 140
7.30 Solution #30: Common EAS selection p. 141
7.30.1 Architecture enhancements p. 141
7.30.2 Solution description p. 141
7.30.3 Solution evaluation p. 143
7.31 Solution #31: Discover common EAS p. 143
7.31.1 Architecture enhancements p. 143
7.31.2 Solution description p. 143
7.31.2.1 General p. 143
7.31.2.2 Procedure for EEC(s) connected to different EES(s) p. 144
7.31.2.3 Procedure for EEC(s) connected to same EES p. 146
7.31.2.4 Procedure for Edge enabler layer support for common EAS announcement p. 148
7.31.2.5 Enhancements to 3GPP TS 23.558 Table 8.2.2-1 AC Profile p. 149
7.31.2.6 Enhancements to 3GPP TS 23.558 8.3.3.2.2 p. 149
7.31.3 Solution evaluation p. 150
7.32 Solution #32: Dynamic EAS instantiation triggering and notification p. 150
7.32.1 Architecture enhancements p. 150
7.32.2 Solution description p. 150
7.32.2.1 General p. 150
7.32.2.2 Dynamic EAS instantiation triggering and notification procedures p. 151
7.32.3 Solution evaluation p. 152
7.33 Solution #33: Support for EEC Discovery of EAS(es) before instantiation p. 153
7.33.1 Architecture enhancements p. 153
7.33.2 Solution description p. 153
7.33.2.1 General p. 153
7.33.2.2 Procedure p. 153
7.33.3 Solution evaluation p. 155
7.34 Solution #34: EDGE-5 APIs p. 156
7.34.1 Architecture enhancements p. 156
7.34.2 Solution description p. 156
7.34.2.1 General p. 156
7.34.2.2 Procedure p. 156
7.34.2.2.1 General p. 156
7.34.2.2.2 AC registration request p. 156
7.34.2.2.3 EAS discovery request p. 157
7.34.2.2.4 ACR request p. 158
7.34.2.2.5 AC subscription request p. 159
7.34.2.2.6 AC notification p. 160
7.34.3 Solution evaluation p. 161
7.35 Solution #35: EEC selected ACR scenarios p. 161
7.35.1 Architecture enhancements p. 161
7.35.2 Solution description p. 161
7.35.2.1 General p. 161
7.35.2.2 Procedure p. 161
7.35.3 Solution evaluation p. 163
7.36 Solution #36: Alignment of EDGEAPP and ETSI MEC p. 163
7.36.1 Architecture enhancements p. 163
7.36.2 Solution description p. 163
7.36.2.1 General p. 163
7.36.2.2 Alignment of EAS registration and MEC application registration p. 163
7.36.2.3 Alignment of EDGE-9 and Mp3 p. 166
7.36.3 Solution evaluation p. 166
7.37 Solution #37: ACR request trigger timing p. 166
7.37.1 Architecture enhancements p. 166
7.37.2 Solution description p. 166
7.37.3 Solution evaluation p. 169
7.38 Solution #38: ACR coordination p. 169
7.38.1 Architecture enhancements p. 169
7.38.2 Solution description p. 169
7.38.2.1 General p. 169
7.38.2.2 Procedure p. 169
7.38.3 Solution evaluation p. 171
7.39 Solution #39: EAS selection synchronization at registration p. 171
7.39.1 Architecture enhancements p. 171
7.39.2 Solution description p. 171
7.39.2.1 General p. 171
7.39.2.2 Procedure p. 171
7.39.3 Solution evaluation p. 176
7.40 Solution #40: EAS instantiation status provisioned by ECS p. 176
7.40.1 Architecture enhancements p. 176
7.40.2 Solution description p. 176
7.40.2.1 General p. 176
7.40.2.2 Procedure p. 176
7.40.3 Solution evaluation p. 178
7.41 Solution #41: Interaction with ADAES for edge load analytics p. 179
7.41.1 Architecture enhancements p. 179
7.41.2 Solution description p. 179
7.41.2.1 General p. 179
7.41.2.2 Procedure p. 179
7.41.3 Solution evaluation p. 180
7.42 Solution #42: EAS selection and instantiation in EES p. 180
7.42.1 Architecture enhancements p. 180
7.42.2 Solution description p. 180
7.42.3 Solution evaluation p. 181
7.43 Solution #43: EAS discovery for Edge node sharing p. 182
7.43.1 Architecture enhancements p. 182
7.43.2 Solution description p. 182
7.43.2.1 General p. 182
7.43.2.2 Publish/unpublish and fetch application p. 182
7.43.2.3 EAS discovery without published application info p. 184
7.43.2.4 EAS discovery with published application info p. 185
7.43.3 Solution evaluation p. 187
7.44 Solution #44: EAS discovery for Edge node sharing p. 187
7.44.1 Architecture enhancements p. 187
7.44.2 Solution description p. 187
7.44.2.1 General p. 187
7.44.2.2 Publish/unpublish and fetch application p. 187
7.44.2.3 EAS discovery for edge node sharing Procedure p. 190
7.44.2.4 Get list of all registered EAS from partner OP p. 191
7.44.3 Solution evaluation p. 191
7.45 Solution #45: EAS discovery in Edge Node sharing scenario p. 192
7.45.1 Architecture enhancements p. 192
7.45.2 Solution description p. 192
7.45.2.1 General p. 192
7.45.2.2 EAS discovery Procedure p. 192
7.45.2.3 T-EAS discovery Procedure p. 193
7.45.3 Solution evaluation p. 194
7.46 Solution #46: EEC selected ACR scenario for EAS bundles p. 194
7.46.1 Architecture enhancements p. 194
7.46.2 Solution description p. 195
7.46.2.1 General p. 195
7.46.2.2 Procedure p. 195
7.46.3 Solution evaluation p. 197
7.47 Solution #47: EES determines the selected ACR scenario for EAS bundles p. 197
7.47.1 Architecture enhancements p. 197
7.47.2 Solution description p. 197
7.47.2.1 General p. 197
7.47.2.2 Procedure p. 197
7.47.3 Solution evaluation p. 199
7.48 Solution #48: Edge server set and edge service set p. 199
7.48.1 Architecture enhancements p. 199
7.48.2 Solution description p. 199
7.48.2.1 General p. 199
7.48.2.2 Reliability support with Sets p. 199
7.48.2.3 EES binding update p. 201
7.48.2.4 Context Transfer procedure p. 201
7.48.3 Solution evaluation p. 202
7.49 Solution #49: ACR for EAS composition p. 202
7.49.1 Architecture enhancements p. 202
7.49.2 Solution description p. 202
7.49.3 Solution evaluation p. 202
7.50 Solution #50: Enhanced ECS for federation of services p. 202
7.50.1 Architecture enhancements p. 202
7.50.2 Solution description p. 202
7.51 Solution #51: EEC sharing UE Mobility requirement p. 206
7.51.1 Architecture enhancements p. 206
7.51.2 Solution description p. 206
7.51.3 Solution evaluation p. 206
7.52 Solution #52: EES policy differentiation p. 206
7.52.1 Architecture enhancements p. 206
7.52.2 Solution description p. 207
7.52.3 Solution evaluation p. 208
7.53 Solution #53: Support for EAS synchronization p. 208
7.53.1 Architecture enhancements p. 208
7.53.2 Solution description p. 209
7.53.3 Solution evaluation p. 210
7.54 Solution #54: EEL assist the application layer to determine the common EAS p. 210
7.54.1 Architecture enhancements p. 210
7.54.2 Solution description p. 210
7.54.2.1 General p. 210
7.54.2.2 Procedure p. 210
7.54.3 Solution evaluation p. 211
7.55 Solution #55: Non-roaming UE location invocation p. 211
7.55.1 Architecture enhancements p. 211
7.55.2 Solution description p. 211
7.55.3 Solution evaluation p. 213
