hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.8 Solution #8: EAS instantiation enhancement to satisfy E2E KPI requirements for XR application | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.8.1 Architecture Impacts | This solution is presented based on the existing EDGEAPP architecture in 3GPP TS 23.558 [11]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.8.2 Solution description | 7.8.2.1 General
This solution proposes that the enablement layer (i.e. EES) can determine the required computing ability requirements of EAS instantiation and/or the required QoS information. By interacting with management system and 5GC, the E2E KPI application requirements of XR application can be guaranteed.
In this... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.8.3 Solution evaluation | This solution addresses the all open issues in key issue #7, the EDGEAPP as enablement layer is enhanced for EAS instantiation to optimize the E2E KPI performance for XR service. The EES triggers the ECSP management system to instantiate the EAS by using the MnS API as in clause 8.12 of 3GPP TS 23.558. This solution wi... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.9 Solution #9: Support performance analytics for tethered UEs | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.9.1 Architecture Impacts | This solution requires the following architecture enhancements:
- ADAES needs to introduce a new service for collecting measurements, monitoring and providing analytics for tethered UEs.
- XRApp server (at SEALDD server or a separate XR enabler) acts as a consumer of ADAES to consume analytics on the VAL session perfor... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.9.2 Solution description | The solution provides a mechanism for analyzing the delay for application layer segments within an end-to-end XR application service segment, and in particular the link between the XRApp Client (e.g., SEALDD client) at the Tethered Device, and the 3GPP UE. Based on this analysis, the mechanism includes the derivation o... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.9.3 Solution evaluation | This solution provides a mechanism for monitoring performance of a tethered UE session with the server and providing analytics on the performance attributes (e.g. RTT). This solution requires enhancement in ADAES to support such new capability. Also, some steps of this solution may be impact depending on whether the XR... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.10 Solution #10: EDN selection based on predicted network connectivity | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.10.1 Architecture Impacts | This solution is based on architecture of EDGEAPP as described in 3GPP TS 23.558 [11]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.10.2 Solution description | 7.10.2.1 General
In service provisioning stage, the UE network connectivity towards EDN is not yet established. This solution improves service provisioning procedure in EDGEAPP, the ECS can obtain the predicted Application session's network connectivity then the ECS can proceed with identifying EES and corresponding ED... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.10.3 Solution evaluation | This solution addresses KI#6 to support XR application server selection to further reduce service latency in a scenario depicted in figure 4.6.1. Function related to how to obtain predicted application session connectivity information needs further evaluation. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.11 Solution #11: Support the tethered UE based on PINAPP | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.11.1 Architecture Impacts | As discussed in TR 26.806 [8], there are three types of tethered UE, Tethered Standalone AR Glasses, Tethered Display AR Glasses, and Tethered AR Glasses with 5G Relay. To focus more on the interaction with applications, the architecture of the application enablement layer can be divided into the following two types ba... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.11.2 Solution description | With the above architecture discussion, there are two ways to do the tethering link measurement. One is SEALDD and VAL coordination measurement based on PIN, the other is the SEALDD measurement based on PIN. The SEALDD and VAL coordination measurement is based on assumption that there is business agreement between the ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.11.3 Solution evaluation | This solution addresses KI#5 by to utilizing PINAPP to do the tethered device discovery, the SEALDD to do the traffic transmission and measurement (including tethered device link). For SEALDD and VAL coordination measurement, the SEALDD client on the 3GPP UE interacts with XR client on the tethered UE to do the measure... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.12 Solution #12: XR application server deployment enhancement | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.12.1 Architecture Impacts | This solution is presented based on the existing EDGEAPP architecture in 3GPP TS 23.558 [11]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.12.2 Solution description | 7.12.2.1 General
This solution proposes that the enabler layer determines the EAS (e.g. XR application) which can provide service with minimum N6 latency, using such mechanism, the E2E KPI requirement of XR application can be satisfied.
In this solution, to avoid the UPF and EAS are not close to each other (e.g. not in... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.12.3 Solution evaluation | Solution#12 provide feasible solution for further minimum N6 latency for XR application to address Key issue#6. The EAS discovery procedure is enhance to select the EAS with minimum N6 latency.
This solution has dependency on SA2 thus further evaluation is required based on the progress on SA2. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.13 Solution #13: XR EAS selection based on N6 delay measurement | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.13.1 Architecture Impacts | This solution is based on architecture of EDGEAPP as described in 3GPP TS 23.558 [11]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.13.2 Solution description | 7.13.2.1 General
In EAS discovery procedure, the EES sends N6 delay measurement request to 5GC and obtains the N6 delay of each pair of discovered XR EAS and UPF for the DNAI of the XR EAS if SA2 can expose N6 delay information to EES.
Editor's note: whether the N6 delay request indicator is needed for EAS discovery or... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.13.3 Solution evaluation | This solution addresses KI#6 to support XR EAS selection based on the measurement of N6 delay of XR EAS(s) and UPF(s) performed by 5GC.
Editor's note: Whether the solution can be concluded and whether the solution can be in normative phase depends on whether SA2 expose N6 delay information to AF. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.14 Solution #14: Support UE to UE communication in different modes via SEALDD | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.14.1 Architecture Impacts | This solution is based on architecture of SEALDD as described in 3GPP TS 23.433 [6] with additional inter-SEALDD client reference point.
Figure 7.14.1-1: SEALDD architecture with on-network and off-network
VAL UE 1 and VAL UE 2 have on-network connectivity, and both VAL UEs can directly communication with each other vi... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.14.2 Solution description | 7.14.2.1 General
When two VAL UEs need to communicate with each other for exchanging gaming/interactive data in XR service, they can use servers in the DN as data relay or communicate with each other directly.
NOTE 1: This solution is only applicable for the XR transmission scenario without involvement of VAL server. A... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.14.3 Information flows | Table 7.14.3-1 describes the new information elements to be added to the SEALDD policy configuration request in 3GPP TS 23.433 [6] Table 9.10.3.1-1 in order to support UE-to-UE communication flows and policy.
Table 7.14.3.1-1: SEALDD policy configuration request
Information element
Status
Description
XR traffic flows
M... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.14.4 Solution evaluation | This solution addresses KI#3 to support:
- How the application enablement layer can be enhanced to support usage of direct communication between 5G connected AR/VR devices.
- Whether and how the application enablement layer can be enhanced to make coordination (e.g., the connection redundancy) between network-based com... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.15 Solution #15: Application enablement layer capabilities usage to support the user group level QoS guarantee | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.15.1 Architecture Impacts | No architecture impact identified. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.15.2 Solution description | Figure 7.15.2-1 illustrates the procedure to support the user group level QoS guarantee. The user group level QoS guarantee provides different QoS for different users in single XR service.
Pre-conditions:
1. The SEALDD server acts as NSaaS provider, and is authorized to get network slice related information and capabil... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.15.3 Solution evaluation | This solution addresses KI#4, the user group level QoS guarantee is provided based on the interaction with NSCE server and 5GC. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.16 Solution #16: XR Application enablement client capability information procedure | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.16.1 Architecture Impacts | This solution describes XR Application enablement client capability information procedure. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.16.2 Solution description | This solution is targeting Key issue #4: Application enablement layer capabilities usage to support the XR services. The SEALDD server and client support XR App functionality. There is a heterogeneity in the VR device ecosystem. As per the [22], the device constraints plays a big role in optimizing the VR data delivery... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.17 Solution #17: Application Enablement Layer AIML Capabilities for Supporting XR Services | The application enablement layer capabilities of the AIML Enablement server (in 3GPP TR 23.700-82 [25] and 3GPP TS 23.482 [28]) can be considered to use for supporting XR services. For example, AI/ML may be required for image/object recognition (as listed in the description part of KI#4), image/video processing, etc. U... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.17.2 Procedure | Pre-conditions:
- The AIMLE Server is known by the consumer and the SEALDD Server.
- The AI/ML services provided by the AIMLE Server is allowed to exposure to the consumer and the SEALDD Server.
- The consumer decides XR service which requires split image/video processing (distribute image/video processing tasks to mul... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.17.3 Information flows | 7.17.3.1 General
The following information flows are specified for adaptive XR data delivery/distribution request based on clause 7.17.2.
7.17.3.2 Supporting Adaptive XR data delivery/distribution request
Table 7.17.3.2-1 describes the information flow from the consumer (e.g. VAL Server) as a request or update request ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.17.4 Solution evaluation | This solution addresses KI#4 and introduces procedure on utilize of the application enablement layer AIML capabilities provided to support XR services, for the following aspects:
- Whether and how the identified application enablement capabilities could be utilized to jointly support the XR service.
- Whether and how t... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 8 Business Relationships | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 8.1 General | The business relationships outlined in 3GPP TS 23.434 and 3GPP TS 23.433[6] remain applicable, with the following modifications:
- the XR service provider acting as the VAL service provider;
- the XRAPP service provider acting as the SEAL/SEALDD service provider. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9 Overall evaluation | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.1 General | All the key issues and solutions specified in this technical report are listed in Table 9.1-1. It includes the mapping of the key issues to the solutions. It also lists the dependencies on other enablement framework.
Table 9.1-1: Key issue and solutions
Key issues
Solution
Dependency on other application enablement cap... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.2 Architecture evaluation | As discussed in clause 9.1, most solutions have dependencies on other application enablement capabilities.
- 7 solutions are based on SEALDD capability and Potential SEALDD architecture enhancement is needed (based on conclusion of KI#5);
- 3 solutions has impact on the EDGEAPP, no architecture impact;
- 1 solution is ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3 Solution evaluation | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.1 Key Issue #1 solutions evaluation | Key issue #1 studies which KPI could be measured and exposed to VAL. There are three solutions addressing the related issues. Solution #4, solution #5 and Solution #6 identify different KPIs using different identification.
Regarding the KPI to be measured:
- Solution #4 improves the SEALDD client for the crossflow RTT ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.2 Key issue #2 solutions evaluation | The open issue of KI#2 include:
- Whether and how to support the E2E multi-modal communication flows between application clients and application servers within the application enablement layer?
- Whether and how to support the interaction between the application enablement layer and 5G CN to manage E2E multi-modal comm... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.3 Key issue #3 solutions evaluation | Key issue#3 studies how to make coordination between network-based communication(on-network communication) and direct communication (off-network communication) between AR/VR devices for AR/VR services communication. Solution #X proposes to coordinate on-network communication and off-network communication by switching t... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.4 Key Issue #4 solutions evaluation | The open issue of KI#4 include:
- Whether and how the identified application enablement capabilities could be utilized to jointly support the XR service.
- Whether and how the application enablement architecture could support the XR service taking advantage of the identified application enablement capabilities.
Solutio... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.5 Key Issue #5 solutions evaluation | Key issue #5 studies how to identify and measure the traffic flows from the tethered devices behind the UE. There are three solutions addressing the related issues: solution #4, solution #9 and solution #11.
- Solution #4 proposes that the SEALDD client on the tethering device to measures the QoS between the SEALDD cli... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.6 Key Issue #6 solutions evaluation | Key issue #6 studies the XR EAS selection enhancement for reducing service latency. There are three solutions addressing the related issues: solution #10, solution #12 and solution #13.
- Solution #10 proposes that the ECS may obtain predicted application session connectivity information if application session connecti... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.7 Key Issue #7 solutions evaluation | The open issue of KI#7 includes:
- How to support the E2E KPI optimization to meet real-time XR service requirements, taking the processing delay of XR application server into account, e.g. considering the potential enhancements to EDGEAPP in XR application server discovery or instantiation.
- What available informatio... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 9.3.8 Key issue #8 solutions evaluation | The open issue of KI#8 include:
- Whether and how SEALDD or other application enabler may be enhanced to facilitate XR communication flows between application clients and application servers involved in the same application service in relation to PDU set (e.g., support for PDU set handling, QoS measurement)?
In the exi... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10 Conclusions | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.1 General conclusions | XR related transmission services are supported based on existing SEALDD architecture with the enhancement identified in clause 6.1.3. CAPIF architecture is utilized to facilitate the SEAL service discovery and invocation for XR application. Specific service enhancements are concluded in the following clauses. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.2 Conclusions of key issue #1 | Solution #4, solution#5 and solution #6 can be modified and adopted into normative work with the following principles:
- Solution #4 can be used to measure and expose crossflow QoS measurement.
- Both solution#5 and #6 can be used to measure the transmission delay, while solution #6 can also be used to measure and expo... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.3 Conclusions of key issue #2 | Solution#1, solution#2, solution #3, solution #5and solution #6 can be considered for normative work (with modifications as needed) with the following principles:
- Solution #1 can be used to configure the SEALDD policy to SEALDD server to support multi-modal XR application.
- For the negotiation on the SEALDD-Uu conne... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.4 Conclusions of key issue #3 | Solution#14 can be considered into normative work to support the coordination between network-based communication (on-network communication) and direct communication (off-network communication).
NOTE 1: If SA2 provided services can support UE-to-UE communication analytics will be further re-visited in the normative wor... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.5 Conclusions of key issue #4 | For the aspect of service discovery and invocation for XR application in key issue #4, the existing CAPIF mechanism can be utilized to support the XR service by invoking the northbound API exposed by the application enablement (e.g. SEAL, EDGEAPP) or the northbound API exposed by 5GS.
The NSCE provided network slice re... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.6 Conclusions of key issue #5 | It is agreed to adopted the following principles in the normative work:
- The PINAPP is utilized to do the tethered device discovery and management.
- The SEALDD is enhanced to do the tethered link measurement.
- The ADAES is enhanced to support performance analytics for tethered devices. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.7 Conclusions of key issue #6 | To enhance the XR EAS selection for reducing service latency, the potential utilization of application session connectivity information and N6 delay measurement information will depend on the progress of SA2's work, this KI is not further studied in this release. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.8 Conclusions of key issue #7 | Solution#8 can be considered into normative work to support the E2E KPI optimization for XR service. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 10.9 Conclusions of key issue #8 | Solution#4 can be considered for normative work with the following principles: - Solution #4 can be used to measure and expose crossflow QoS measurement for XR flows including PDU set. - For the target flow identification, traffic descriptor could be used to uniquely identifies the flow while the exact information elem... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 1 Scope | The scope of this Technical Report is to study the following aspects of 5GS/EPS integrating of satellite component in Release 19, including:
- Regenerative payload generic architecture:
- Impact to 5GS and EPS to support gNB/eNB onboard the satellite.
- Store and Forward Satellite operation for delay tolerant services:... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 3 Definitions of terms and abbreviations | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.401 [5] and TS 23.501 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Serving satellite: a satellite providing the satellite access to a ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
ISL Inter-Satellite Link
NTN Non-Terrestrial Network
S&F Store and Forward
... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 4 Architectural Assumptions and Principles | The following architecture assumptions are applied to the study:
- The 5GC architecture for satellite access for NR as defined in TS 23.501 [2] is used as a baseline.
- The EPC architecture for satellite access for IoT as defined in TS 23.401 [5] and the architecture enhancements to facilitate communications with packe... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5 Key Issues | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.1 Key Issue #1: Support of Regenerative-based satellite access | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.1.1 Description | The deployment of an eNB or an gNB on a satellite for regenerative based satellite access for LEO/MEO deployment is to be studied. The aspects to be studied include:
- Identify and study whether there is any impact on 5GS and EPS to support an gNB/eNB embedded on a satellite:
- any impact of RAN nodes changing for any ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.2 Key Issue #2: Support of Store and Forward Satellite operation | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.2.1 Description | S&F Satellite operation is especially suited for the delivery of delay-tolerant/non-real-time satellite services (i.e. CIoT/MTC, SMS). To support S&F Satellite operation for such services, it is proposed to study the following items:
- If applicable, what are the minimum necessary set of core network elements/network f... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.3 Key Issue #3: Support of UE-satellite-UE communication | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 5.3.1 Description | UE-satellite-UE communication refers to the communication between UEs under the coverage of one or more serving satellites without the user plane traffic going through the ground network.
It is expected that a link to the ground, via ISL to another satellite with a link to a ground gateway, or via multiple other satell... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6 Solutions | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
1
2
3
1
X
2
X
3
X
4
X
5
X
6
X
7
X
8
X
9
X
10
X
11
X
12
X
13
X
14
X
15
X
16
X
17
X
18
X
19
X
20
X
21
X
22
X
23
X
24
X
25
X
26
X
27
X
28
X
29
X
30
X
31
X
32
X
33
X
34
X
35
X
36
X
37
X
38
X
39
X
40
X
41
X
42
X
X
43
X
44
X
45
X |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.1 Solution #1: N2/S1 disconnection for satellites leaving an area served by a CN | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.1.1 Description | This is a solution addressing Key Issue #1.
The solution assumes that an eNB/gNB is on-board the satellite, and the EPC/5GC is on ground.
When a LEO satellite with an on-board eNB/gNB leaves an area served by a certain core network, there is no use of the N2/S1 interface anymore. It may even be that the satellite has n... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.1.2 Procedures | Figure 6.1.2-1: Release of N2/S1 interface
1. The gNB/eNB knows, based on its ephemeris and configuration, that it is about to stop serving a certain 5GC/EPC area and it is about to lose the connectivity to the 5GC/EPC via a ground connection.
Before triggering a disconnect of the N2/S1 interface, it is assumed that th... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.1.3 Impacts to Services, Entities and Interfaces | NG-RAN and E-UTRAN:
- Support for detecting when satellite is about to stop serving (and/or lose ground connectivity to) a given AMF/MME and trigger N2/S1 disconnect to release the N2/S1 connection.
MME/AMF:
- Support for N2/S1 procedure to release N2/S1 connection and delete corresponding context. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2 Solution #2 for KI#1: Mobility optimization for Regenerative-based satellite access | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.1 Description | This is a candidate solution for Key Issue #1: Support of Regenerative-based satellite access considering the following aspects:
- How does the RAN node connect to an AMF on the ground, including what information will be exchanged between RAN and CN?
- How to efficiently manage N2 connections due to the RAN node's move... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.1.1 TAI/CGI report over N2/S1-AP interface | In existing procedures, the RAN node initiates the NG/S1 Setup procedure to report the Supported TA List to the AMF/MME. However, RAN node mobility will lead to continuous change of the TAs supported by the RAN node, and then cause frequent message exchange between RAN nodes on board and the core network on the ground ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.1.2 TNL Connection Suspending over N2/S1-AP interface | RAN node mobility, in case RAN nodes are boarded on satellite and the CN on the ground, will cause much frequent disconnection and re-connection of TNL over the N2/S1-AP interface of an AMF/MME. When the SCTP endpoint detects the path failure based on heartbeat time out, it will close the SCTP association and delete th... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.1.3 Paging | RAN mobility will also cause the change of RAN nodes serving a TA(s), thus for paging an UE in a TA(s), the AMF needs to know which RAN node should page the UE over the air interface. As this solution doesn't require the RAN node onboard to continuously report the Supported TA list, the AMF has to rely on satellite eph... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.1 Connecting a RAN node on-board to the CN on the ground | Figure 6.2.2.1-1: Connecting a RAN node on-board to the CN on the ground
1. If the on-board RAN node initiates the NG/S1 Setup procedure, the RAN node sends the NG SETUP REQUEST message as specified in clause 9.2.6.1 of TS 38.413 [12] to the AMF or the S1 SETUP REQUEST message as specified in clause 9.1.8.4 of TS 36.41... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.2 Information Exchanging between RAN node and CN | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.2.1 RAN node Configuration for Supported TA list report | Figure 6.2.2.2.1-1: RAN node Configuration for Supported TA list report
Compared to the existing ANF/MME configuration update procedure, the differences are as follows:
1. AMF/MME CONFIGURATION UPDATE message may include:
a) Request Supported TA List indicator.
2. AMF/MME CONFIGURATION ACKNOWLEDGE message may include:
... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.2.2 Reporting Supported TA list to the CN on the ground | Figure 6.2.2.2.2-1: Reporting Supported TA list to the CN on the ground
1. If the on-board RAN node will not be able to provide services to any TA in the TA list last provided to the AMF/MME, the on-board RAN node may initiate the RAN/ENB Configuration Update procedure to update the supported TA list by sending a RAN C... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.3 TNL management over N2/S1-MME interface | Figure 6.2.2.2-2: Disconnecting and Reconnecting a RAN node with the CN on the ground
1. If the on-board RAN node is about to disconnect the feeder link towards the AMF/MME in the PLMN, the on-board RAN node should initiate the RAN/ENB Configuration Update procedure to inform the AMF/MME to store the context of the NG/... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.2.4 Paging | If the network needs to signal (e.g. N1 signalling to UE, Mobile-terminated SMS, User Plane connection activation for PDU Session(s) to deliver mobile terminating user data) with a UE, the Network Triggered Service Request procedure is triggered by SMSF, PCF, LMF, GMLC, NEF, AMF or UDM, the SMF (and UPF, if applicable)... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.2.3 Impacts on services, entities and interfaces | The solution impacts the following network functions:
- MME/AMF supports to be configured with ephemeris information of all on-board (ng-)eNB by O&M;
- MME/AMF and RAN support to suspend the TNL between the RAN node and the CN;
- MME/AMF and RAN support to resume the TNL between the RAN node and the CN;
- MME/AMF suppo... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.3 Solution #3: Support for suspend and resume of NG interface | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.3.1 Key Issue mapping | This solution addresses the scenarios mentioned in the KI#1. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.3.2 Functional Description | This solution follows following basic principles and assumptions:
Figure 6.3.2-1
1. The gNB is in the payload of the satellite.
2. When the feeder link becomes available, the gNB sends NG SETUP REQUEST message including feeder link available time i.e. gNB available time to the AMF.
3. The AMF stores the feeder link ava... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.3.4 Impacts on existing services, entities and interfaces | gNB, NTN GW,and AMF needs to implement the suspend and resume \NG connection.
eNB, NTN GW and MME needs to implement the suspend and resume S1 connection. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.