hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.8.1 Description | Satellite access may be valuable for Mission Critical communication, especially in remote areas and during disaster relief scenarios. Participants connected via satellite access may be crucial in Mission Critical group communications. Still, it should be considered that it is likely that Mission Critical group communic... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.8.2 Open issues | The following aspects need to be studied:
- What is the actual impact of satellite access to the KPIs for Mission Critical communication?
- Whether and how participants of group communications can be informed about reduced KPIs due to one or more participants being connected via satellite. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 5 Architecture requirements | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 5.1 General architecture requirements | [AR-5.1-a] The architecture shall support deployment of application enablers and services over satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 5.2 Mission Critical service architecture requirements | [AR-5.2-a] The architecture shall support deployments to obtain MC services over satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 5.3 EDGEAPP architecture requirements | [AR-5.3-a] The EDGEAPP shall support satellite connectivity enabled with deployment of EDGEAPP architecture components onboard satellite.
[AR-5.3-b] The EDGEAPP shall support satellite connectivity enabled with multiple deployment options of EDGEAPP architecture components onboard satellite.
[AR-5.3-c] The EDGEAPP shal... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 5.4 SEAL functional requirements | [AR-5.4-a] The SEAL architecture shall leverage satellite connectivity.
[AR-5.4-b] The SEAL architecture shall support satellite coverage availability information during discontinuous coverage of satellite connectivity.
[AR-5.4-c] The SEAL architecture shall support UE unavailability information during discontinuous co... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6 Architecture for satellite access enabled 3GPP services and application enablers | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.1 Option#1: MC architecture over satellite access | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.1.1 Application architecture | The architecture and functional model defined in 3GPP TS 23.289 [23.289] is reused to achieve MC services over NTN. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.1.2 Functional Elements | No additional functional elements is needed to be defined in order to enable MC services over NTN. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.1.3 Reference Points | No additional reference point is needed to be defined in order to enable MC services over NTN. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.2 Option#2: EDGEAPP over Satellite connectivity | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.2.1 Application enablement architecture and deployment models | The EDGEAPP architecture as defined in 3GPP TS 23.558 [10] is reused to enhance EDGEAPP procedures such as service provisioning, EAS discovery during satellite connectivity as per Solution #AE1, Solution #AE2, Solution #AE5 and Solution AE#7. There are no architectural impacts to EDGEAPP architecture defined in 3GPP TS... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.2.2 Functional Elements | Editor's Note: The functional elements corresponding to the architecture will be presented in this clause. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.2.3 Reference Points | Editor's Note: The reference points corresponding to the architecture will be presented in this clause. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.3 Option#3: SEAL over Satellite connectivity | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.3.1 Application enablement architecture and deployment models | The SEAL architecture as defined in 3GPP TS 23.434 [8] is reused to enhance SEAL procedures in Configuration management, Network resource management, SEALDD, to support discontinuous coverage, S&F operation during satellite connectivity as per Solution #AE3, Solution #AE4, Solution #AE6 and Solution AE#8. There are no ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.3.2 Functional Elements | Editor's Note: The functional elements corresponding to the architecture will be presented in this clause. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 6.3.3 Reference Points | Editor's Note: The reference points corresponding to the architecture will be presented in this clause. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7 Solutions | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.0 Mapping of solutions to key issues | Table 7.0-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI#5
KI#6
KI#7
KI#8
Mission Critical Services
Sol #MC1
x
Sol #MC2
Application Enablers
Sol #AE1
x
x
Sol #AE2
x
Sol #AE3
x
Sol #AE4
x
Sol #AE5
x
x
Sol #AE6
x
Sol #AE7
x
x
Sol #AE8
x
Sol#AE9
x |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1 Solutions for Mission Critical | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1.1 Solution #MC1: MC group members NTN connection information | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1.1.1 Solution description | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1.1.1.1 General | This solution looks into how to inform MC group participants of one or more MC service users participating in the group communication being connected via NTN. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1.1.1.2 Enhance the dynamic data associated with a group | Clause 10.1.5.5 in 3GPP TS 23.280 [18] discusses the dynamic data associated to a group, such as the status, i.e., the indication of potential emergency or in-peril status of the group, the affiliation status of each MC service ID in the group, ongoing group calls. These dynamic data is known to the MC service server a... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.1.1.2 Solution evaluation | The solution described provides a promising approach to inform the participants of a group communication of possible MC service users being connected via NTN. The solution can be further enhanced, and potential procedures can be investigated during the normative work. Other potential solutions may be considered as well... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2 Solutions for Application Enablers | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1 Solution #AE1: Satellite edge computing | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.1 Solution description | Editor's Note: This clause will describe the solution. Each solution should clearly describe which of the key issues it covers and how. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.1.1 General | Figure 7.2.1.1.1-1: satellite EDN deployment
In this deployment option, ECS is deployed on ground. The UE can be on the ground/sea or in the air (e.g. drone). The UPF to access satellite EDN is deployed on satellite, EAS and EES are deployed in one or more satellites. RAN (e.g. gNB) can either be deployed on ground/sea... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.1.2 Further consideration for service provisioning | An external server responsible for providing satellite availability information for each satellite based on real-time satellite orbit information (e.g. eccentricity, inclination, true anomaly) may exist (e.g. see 3GPP TS 23.501 [5], Annex Q). During service provisioning, the EEC can provide needed satellite capability ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.1.3 EAS discovery for EAS on board satellite | Unlike EAS discovery procedures EAS(s) on the ground, the EAS discovery for EAS(s) on board the satellite could be mobile depending on the satellite they are deployed on: GEO, MEO, or LEO. For GEO satellites, since the satellites are stationary relative to the Earth's surface, the EAS is also static. However, for MEO a... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.1.4 Service provisioning for EES on board satellite | Similar to EAS on board a MEO or LEO satellite, the EES will also be mobile when the EES is also on board a MEO or LEO satellite. Therefore considering the trajectory of the EES is important for efficient service provisioning for selecting EDN matched with movement of the AC hosting UE during the AC’s operation schedul... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.2 Architecture Impacts | This solution has no architecture impacts to EDGEAPP. Under the existing EDGEAPP architecture, the service provisioning procedure is enhanced to support different cases in service continuity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.3 Corresponding APIs | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.3.1 EAS Profile, EES Profile and AC Profile for discovery and service provisioning | According to clause 7.2.1.1.3 EAS discovery for EAS onboard satellite and clause 7.2.1.1.4 Service provisioning for EES on board satellite, the following change is needed in 3GPP TS 23.558 [10].
NOTE: The Trajectory ID of the EAS(s) and the EES(s) on the same satellite is identical.
- 3GPP TS 23.558 [10] Clause 8.2.4 E... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.1.4 Solution evaluation | This solution is for KI#2 and addresses the open issue about deployment option for EDGEAPP and related enhancements to the EDGEAPP procedures including service provisioning and EAS discovery. The solution does not impact the architecture entity in EDGEAPP.
The solution proposes ECS is deployed on ground while EAS and E... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2 Solution #AE2: Enhancement for on board EES(s) and service provisioning | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2.1 Solution description | This solution proposes to address the following open issues in KI#5,
- How the EES(s) are placed on board the Satellite.
- Whether and how the service provisioning is impacted.
It is proposed to add the Satellite assistant information in the EES profile to indicating the EES(s) are placed on board the satellite, so th... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2.1.1 General | When EES is deployed in the satellite, it is proposed to add the Satellite assistant information in the EES Profile to indicating the EES is deployed on-board. The Satellite assistant information could be the satellite ephemeris information(e.g., time slot and spatial location). So that the ECS could obtain the EES’s S... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2.2 Architecture Impacts | This solution has no architecture impacts to EDGEAPP. Under the existing EDGEAPP architecture, the service provisioning procedure is enhanced to support different cases in service continuity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2.3 Corresponding APIs | EDN configuration information in the Service provisioning response needs to be changed as follows.
Table 8.3.3.3.3-2: EDN configuration information
Information element
Status
Description
EDN connection information (NOTE 1)
M
Information required by the UE to establish connection with the EDN.
> DNN/APN
M
Data Network N... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.2.4 Solution evaluation | This solution is for KI#5 and addresses the open issue about deployment option for EDGEAPP and related enhancements to the EDGEAPP service provisioning. The solution does not required new architecture entity in EDGEAPP.
The solution proposes ECS is deployed on ground while EAS and EES are deployed on satellite. In this... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3 Solution #AE3: Support discontinuous coverage for satellite access | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.1 Solution description | This solution addresses the KI#3: Satellite access with discontinuous coverage.
This solution shows how the application enabler obtaining the satellite related information (e.g., ephemeris) from the satellites, retrieving unavailability period for UE with satellite access then exposing to the VAL UE and the VAL server.... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.1.1 Procedure of SEAL Server generating Satellite coverage availability and unavailability period information | Pre-condition:
- SEAL Client has registered on SEAL server.
- The VAL server asks SEAL Server to provide VAL UE’s information (e.g. location data) periodically.
- The SEAL server is aware of the VAL UE’s location information.
Figure 7.2.3.1.1-1: Procedure of SEAL Server generating Satellite coverage availability and un... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.1.2 Procedure for AS handling UE unavailability period information | Pre-condition:
- Satellite coverage availability information (SCAI) is not yet configured on the UE or not supported by the UE.
- 5GC is aware of SCAI and UE location.
Figure 7.2.3.1.2-1: Procedure for AS handling UE unavailability period information
1. UE does not support SCAI provisioning or UE has not received SCAI ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.2 Architecture Impacts | This solution has no architecture impacts to the existing SEAL server (i.e. Configuration management and SEALDD server) when serving the IoT applications.
Under the existing SEAL architecture, the SEAL Configuration management and SEALDD procedures are enhanced to support satellite discontinuous coverage. E.g., the pro... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.3 Corresponding APIs | Editor's note: This clause provides the corresponding APIs for supporting the solution. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.3.4 Solution evaluation | This solution is for KI#3 and addresses the open issue on how SEAL can obtain the satellite coverage availability information (SCAI) and retrieve unavailability period then provide it to the UE and VAL Server. In this solution the SEAL server (i.e. Configuration management SEALDD server) retrieves the UE unavailability... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4 Solution #AE4: Application enablers provisioning and expose the satellite S&F events information | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.1 Solution description | This solution addresses the KI#7: Usage of S&F events information for the application enablement. It mainly focuses on the following open issues.
- What is the S&F events information that can be utilized by the application enablers?
- Whether and how the S&F Satellite operation information can be exposed to the 3rd par... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.1.1 Deployment model | Figure 7.2.4.1.1-1: Deployment for satellite S&F operation for IoT services
For this solution, the SEAL server serving the IoT service is assumed to be deployed on the ground. The VAL server is deployed on the ground. The UE can be on the ground/sea or in the air (e.g. drone). The PGW-U to access the SEAL server is dep... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.1.2 Procedure of SEAL Server exposing the S&F status to the VAL server | Pre-condition:
- The SEAL client, the SEAL server and the VAL server all are deployed on the ground.
- The UPF/PGW-U in the 3GPP CN is deployed on the satellite.
Figure 7.2.4.1.2-1: Procedure of SEAL Server exposing the S&F status to the VAL server
1. The VAL server sends UE S&F status events subscription requests to t... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.2 Architecture Impacts | This solution has no architecture impacts to SEAL. Under the existing SEAL architecture, the SEAL NRM for control plane, SEALDD sever for user plane procedures are enhanced to support S&F functionality during satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.3 Corresponding APIs | Editor's note: This clause provides the corresponding APIs for supporting the solution. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.4.4 Solution evaluation | This solution is for KI#7 and addresses the open issue about enabling SEAL architecture to obtain and expose the S&F related information and to leverage that information for optimised application enablement behaviour. The solution does not required new architecture entity in SEAL.
This solution proposes how SEAL server... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5 Solution #AE5: Satellite edge computing considering EAS onboard | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.1 Solution description | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.1.1 General | Figure 7.2.5.1.1-1: EAS onboard satellite deployment
In this deployment option, ECS and EES are deployed on ground. The UE can be on the ground/sea or in the air (e.g. drone). The UPF to access EAS is deployed on satellite. RAN (e.g. gB) can either be deployed on ground/sea (e.g. in a ship) and connected to satellite U... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.2 Architecture Impacts | This solution has no architecture impacts to EDGEAPP. Under the existing EDGEAPP architecture, the EAS discovery procedure is enhanced to support different cases in discontinuous coverage. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.3 Corresponding APIs | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.3.1 EAS Profile enhancement for EAS onboard | According to clause 7.2.1.1.3 EAS discovery for EAS onboard satellite the following change is needed in TS 23.558 [10].
- 3GPP TS 23.558 [10] Clause 8.2.4 EAS Profile EAS mobility on board LEO or MEO Satellite
3GPP TS 23.558 [10] Table 8.2.4-1: EAS Profile
Information element
Status
Description
EASID
M
The identifier o... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.5.4 Solution evaluation | This solution is for KI#2 to addresses the open issue about deployment option for EDGEAPP and related enhancements to the EDGEAPP procedures including service provisioning and EAS discovery. The solution does not required new architecture entity in EDGEAPP.
The solution proposes ECS and EES are deployed on ground while... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6 Solution #AE6: Enhancing store and forward mechanism of MSGin5G service | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.1 Solution description | As specified in clause 8.3.6 (of 3GPP TS 23.554 [14]), SA6 defined MSGin5G service supports application enabler level store and forward mechanism. As per the defined mechanism, the MSGin5G server stores the message if recipient UE is not available. Further, as specified in KI #7, SA2 is studying S&F events like expecte... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.1.2 Enhancement to MSGin5G Store and Forward procedure | Following enhancement are done in clause 8.3.6 of 3GPP TS 23.554 [14]:
- The MSGin5G server subscribes to receive S&F events:
- If the recipient MSGin5G Client knows that satellite connection may be used, e.g. based on the configuration, it may include the satellite connection used indicator in its registration request... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.1.2 Procedure for MSGin5G client to update the store and forward parameters | Figure 7.2.6.1.2-1 shows the procedure for MSGin5G client to update the store and forward parameters.
Pre-conditions:
1. The MSGin5G Client has originated a message to a recipient UE and it is stored to the MSGin5G Server as the recipient UE is not available (as specified in clause 8.3.6 of 3GPP TS 23.554 [14]).
2. Use... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.1.3 Procedure for MSGin5G client to discard the stored message | Figure 7.2.6.1.3-1 shows the procedure for MSGin5G client to discard the stored messages.
Pre-conditions:
1. The MSGin5G Client has originated a message to a recipient UE and it is stored to the MSGin5G Server as the recipient UE is not available (as specified in clause 8.3.6 of 3GPP TS 23.554 [14]).
2. User has receiv... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.1.4 Enhancement to MSGin5G UE Registration | If the recipient MSGin5G Client knows that satellite connection may be used, e.g. based on the configuration, it may include the satellite connection used indicator in its registration request. This indicator is included in the MSGin5G Client Communication Availability specified in Table 8.2.1-3 of 3GPP TS 23.554 [14].... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.2 Architecture Impacts | No architecture impact is identified for MSGin5G architecture as defined in 3GPP TS 23.554 [14]. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.3 Corresponding APIs | Table 7.2.6.3-1 specifies information elements for MSGin5G update stored message parameter request message.
Table 7.2.6.3-1: MSGin5G update stored message parameter request
Information element
Status
Description
Originating UE Service ID/AS Service ID
M
The service identity of the sending MSGin5G Client or the sending ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.6.4 Solution evaluation | This solution addresses key issue #7 by utilizing store and forward events from SA2, and deciding whether to update the stored and forward parameters or the MSGin5G message or discard the stored message. Solution #AE6 will not be considered for KI #7 in normative phase due to SA2 only support S&F for EPC in Rel-19. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7 Solution #AE7: Satellite edge computing considering EAS onboard | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7.1 Solution description | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7.1.1 General | Figure 7.2.7.1.1-1: EAS and EES onboard satellite deployment
In this deployment option, ECS is deployed on ground. The UE can be on the ground/sea or in the air (e.g. drone). The UPF to access satellite EDN is deployed on satellite, EAS and EES are deployed in one or more satellites. EASs and their registered EES are d... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7.2 Architecture Impacts | This solution has no architecture impacts to EDGEAPP. Under the existing EDGEAPP architecture, the service provisioning and EAS discovery procedures are enhanced to support different cases in discontinuous coverage. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7.3 Corresponding APIs | 7.2.7.3.1 EES Profile enhancement for EES onboard
According to clause 7.2.7.1 service provisioning for EES onboard satellite the following change is needed in 3GPP TS 23.558 [10].
3GPP TS 23.558 [10] Clause 8.2.6 EES Profile EES mobility on board LEO or MEO Satellite
3GPP TS 23.558 [10] Table 8.2.6-1: EES Profile
Infor... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.7.4 Solution evaluation | This solution is for KI#2 to addresses the open issue about deployment option for EDGEAPP and related enhancements to the EDGEAPP procedures including service provisioning and EAS discovery. The solution does not required new architecture entity in EDGEAPP.
The solution proposes ECS is deployed on ground while EES and ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8 Solution #AE8: Leveraging S&F events information at application enablement | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.1 Solution description | This solution maps to KI#7. This solution is about leveraging S&F events information at the application enablement for the optimized service delivery. In this scenario, AS (e.g. SEAL server) is considered to be deployed on the ground and UPF onboard the satellite as shown in Figure 7.2.8.1-1.
Figure 7.2.8.1-1: Deployme... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.1.1 AS subscribing to S&F events information with EPC | Figure 7.2.8.1.1-1: Procedure for AS subscribing to S&F events information with EPC
1. AS (e.g. SEAL server) sends subscribe S&F information request to EPC (e.g. SCEF) e.g. for getting feeder link and service link availability information, expected data delivery time.
NOTE: The request may include UE information if AS ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.1.2 S&F data delivery handling at AS | Pre-condition: AS (SEAL server) has subscription to S&F information with EPC as described in 7.2.8.1.1
Figure 7.2.8.1.2-1: Procedure for S&F data delivery handling at AS (e.g. SEAL server)
1. VAL server sends send data request to AS (e.g. SEAL server) including the target UE/user and service identity information.
2. AS... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.2 Architecture Impacts | This solution has no architecture impacts to SEAL. Under the existing SEAL architecture, the SEALDD procedures are enhanced to support S&F functionality during satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.3 Corresponding APIs | Editor's note: This clause provides the corresponding APIs for supporting the solution. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.8.4 Solution evaluation | This solution is for KI#7 and addresses the open issue about enabling SEAL architecture to obtain and expose the S&F related information and to leverage that information for optimised application enablement behaviour. The solution does not required new architecture entity in SEAL.
This solution proposes how SEAL server... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9 Solution #AEx: Analytics related to UE RAT connectivity | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.1 Solution description | This solution addresses the open issues listed as part of the key issue 1 which are related to identifying the new analytics required to be supported for satellite access. It introduces a new analytics type which needs to be supported by the ADAE (Application Data Analytics Enablement) server. It proposes the procedure... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.1.1 Procedure on UE RAT connectivity analytics | Figure 7.2.9.1.1-1 illustrates the procedure support the UE RAT connectivity analytics.
Figure 7.2.9.1.1-1: Procedure of ADAE Server supporting UE RAT connectivity analytics
1. The analytics consumer (e.g.VAL server) makes a subscription request to ADAE server for UE RAT connectivity prediction/stats, including an anal... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.2 Architecture Impacts | This solution has no architecture impacts to ADAE or any other SEAL services. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3 Corresponding APIs | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.1 General | The following information flows are specified for UE RAT connectivity analytics. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.2 UE RAT Connectivity analytics subscription request | Table 7.2.9.3.2-1 describes information elements for the UE RAT connectivity analytics subscription request from the VAL server / Consumer to the ADAE server.
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server.
Analytics ID
M
The identifier of the UE RAT connectivity analytics event... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.3 UE RAT Connectivity analytics subscription response | Table 7.2.9.3.3-1 describes information elements for the UE RAT connectivity analytics subscription response from the ADAE server to the VAL server /Analytics Consumer.
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement) |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.4 UE RAT Connectivity data request | Table 7.2.9.3.4-1 describes information elements for the UE RAT connectivity data request from the ADAE server to the A-ADRF.
Information element
Status
Description
ADAE server ID
M
The identifier of the ADAE server
Analytics ID
M
The identifier of the analytics event i.e. UE RAT connectivity analytics
List of VAL UE I... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.5 UE RAT Connectivity data response | Table 7.2.9.3.5-1 describes information elements for the UE RAT connectivity data response from the A-ADRF to the ADAE server.
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event.
List of VAL UE IDs and addresses
M
The VAL UE(s) identifiers and IP address(es) for which the analyt... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.3.6 UE RAT Connectivity analytics notification | Table 7.2.9.3.5-1 describes information elements for the UE RAT connectivity analytics notification from the A-ADRF to the ADAE server.
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event (UE RAT connectivity)
Analytics Output
M
The predictive or statistical parameter, which can ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 7.2.9.4 Solution evaluation | Editor's note: This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
This solution is for KI#1 and addresses the open issues about the new analytics required to be supported for satellite access. This solution does not impact the arc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.