Content for TR 23.700-01 Word version: 19.0.0
6 Architecture for satellite access enabled 3GPP services and application enablers
7 Solutions
8 Deployment scenarios
9 Business Relationships
10 Overall evaluation
11 Conclusions
A Information related to Satellite access support for MC Service
$ Change history
6 Architecture for satellite access enabled 3GPP services and application enablers p. 16
6.1 Option#1: MC architecture over satellite access p. 16
6.2 Option#2: EDGEAPP over Satellite connectivity p. 17
6.2.1 Application enablement architecture and deployment models p. 17
6.2.2 Functional Elements p. 17
6.2.3 Reference Points p. 17
6.3 Option#3: SEAL over Satellite connectivity p. 17
7 Solutions p. 18
7.0 Mapping of solutions to key issues p. 18
7.1 Solutions for Mission Critical p. 18
7.2 Solutions for Application Enablers p. 19
7.2.1 Solution #AE1: Satellite edge computing p. 19
7.2.1.1 Solution description p. 19
7.2.1.1.1 General p. 19
7.2.1.1.2 Further consideration for service provisioning p. 20
7.2.1.1.3 EAS discovery for EAS on board satellite p. 20
7.2.1.1.4 Service provisioning for EES on board satellite p. 21
7.2.1.2 Architecture Impacts p. 21
7.2.1.3 Corresponding APIs p. 21
7.2.1.4 Solution evaluation p. 23
7.2.2 Solution #AE2: Enhancement for on board EES(s) and service provisioning p. 23
7.2.2.1 Solution description p. 23
7.2.2.1.1 General p. 23
7.2.2.2 Architecture Impacts p. 25
7.2.2.3 Corresponding APIs p. 25
7.2.2.4 Solution evaluation p. 28
7.2.3 Solution #AE3: Support discontinuous coverage for satellite access p. 28
7.2.3.1 Solution description p. 28
7.2.3.1.1 Procedure of SEAL Server generating Satellite coverage availability and unavailability period information p. 29
7.2.3.1.2 Procedure for AS handling UE unavailability period information p. 30
7.2.3.2 Architecture Impacts p. 31
7.2.3.3 Corresponding APIs p. 31
7.2.3.4 Solution evaluation p. 31
7.2.4 Solution #AE4: Application enablers provisioning and expose the satellite S&F events information p. 31
7.2.4.1 Solution description p. 31
7.2.4.1.1 Deployment model p. 31
7.2.4.1.2 Procedure of SEAL Server exposing the S&F status to the VAL server p. 32
7.2.4.2 Architecture Impacts p. 36
7.2.4.3 Corresponding APIs p. 36
7.2.4.4 Solution evaluation p. 36
7.2.5 Solution #AE5: Satellite edge computing considering EAS onboard p. 37
7.2.5.1 Solution description p. 37
7.2.5.1.1 General p. 37
7.2.5.2 Architecture Impacts p. 38
7.2.5.3 Corresponding APIs p. 38
7.2.5.4 Solution evaluation p. 38
7.2.6 Solution #AE6: Enhancing store and forward mechanism of MSGin5G service p. 39
7.2.6.1 Solution description p. 39
7.2.6.1.1 Enhancement to MSGin5G Store and Forward procedure p. 39
7.2.6.1.2 Procedure for MSGin5G client to update the store and forward parameters p. 40
7.2.6.1.3 Procedure for MSGin5G client to discard the stored message p. 40
7.2.6.1.4 Enhancement to MSGin5G UE Registration p. 41
7.2.6.2 Architecture Impacts p. 41
7.2.6.3 Corresponding APIs p. 41
7.2.6.4 Solution evaluation p. 42
7.2.7 Solution #AE7: Satellite edge computing considering EAS onboard p. 43
7.2.7.1 Solution description p. 43
7.2.7.1.1 General p. 43
7.2.7.2 Architecture Impacts p. 44
7.2.7.3 Corresponding APIs p. 44
7.2.7.4 Solution evaluation p. 44
7.2.8 Solution #AE8: Leveraging S&F events information at application enablement p. 44
7.2.8.1 Solution description p. 44
7.2.8.1.1 AS subscribing to S&F events information with EPC p. 45
7.2.8.1.2 S&F data delivery handling at AS p. 46
7.2.8.2 Architecture Impacts p. 46
7.2.8.3 Corresponding APIs p. 46
7.2.8.4 Solution evaluation p. 47
7.2.9 Solution #AEx: Analytics related to UE RAT connectivity p. 47
7.2.9.1 Solution description p. 47
7.2.9.2 Architecture Impacts p. 48
7.2.9.3 Corresponding APIs p. 49
7.2.9.3.1 General p. 49
7.2.9.3.2 UE RAT Connectivity analytics subscription request p. 49
7.2.9.3.3 UE RAT Connectivity analytics subscription response p. 49
7.2.9.3.4 UE RAT Connectivity data request p. 49
7.2.9.3.5 UE RAT Connectivity data response p. 50
7.2.9.3.6 UE RAT Connectivity analytics notification p. 50
7.2.9.4 Solution evaluation p. 50
8 Deployment scenarios p. 51
8.1 General p. 51
8.2 Deployment model p. 51
9 Business Relationships p. 51
9.1 EDGEAPP deployment with satellite connectivity p. 51
9.2 SEAL deployment with satellite connectivity p. 51
10 Overall evaluation p. 52
10.1 Architecture evaluations for Mission Critical p. 52
10.2 Key issue evaluations for Mission Critical p. 52
10.2.1 Key issue #4: p. 52
10.2.2 Key issue #8: p. 53
10.3 Architecture evaluations for Application Enablers p. 53
10.4 Key issue evaluations for Application Enablers p. 53
10.4.1 Key issue #1: p. 53
10.4.2 Key issue #2: p. 53
10.4.3 Key issue #3: p. 53
10.4.4 Key issue #5: p. 54
10.4.5 Key issue #6: p. 54
10.4.6 Key issue #7: p. 54
11 Conclusions p. 54
11.1 General conclusions p. 54
11.2 Conclusions for Mission Critical p. 54
11.2.1 General conclusions for MC services over NTN p. 54
11.2.2 Conclusions of key issue #4 p. 55
11.2.3 Conclusions of key issue #8 p. 55
11.3 Conclusions for Application Enablers p. 55
A Information related to Satellite access support for MC Service p. 57
$ Change history p. 61
