hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 2 Study whether and how to improve NF/NF service resiliency, scalability, efficiency and load balancing, compared with 5G.
| NOTE: This WT covers generic aspects for SBA framework. The study of other WTs can also result in potential enhancements on the SBA framework and will be studied as part of respective WTs.
A.1.2.1 Network Sharing in the 6G system
Study on how to support network sharing in 6G, including the following aspects:
- How t... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.3 Key Issue #3: Support of Network Slicing in the 6G system
| This Key Issue aims to study the support of Network Slicing in the 6G system, including the following aspects:
1. Study the overall design and functionalities of the network slicing in 6G assuming the network slicing in 5GS as starting point for discussions including the following:
a) Identify and address any areas o... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.4 Key Issue #4: User Plane Architecture
| In order to support 6G user plane for a diverse set of applications and traffic patterns, the following are studied taking the 5GS user plane framework as a starting point for discussion:
1. Whether and how to enhance CP-UP functional split and interaction for better multi-vendor interoperability.
2. Whether and how... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.5 Key Issue #5: QoS Framework for 6G
| This key issue is based on the WT#1.2 on the QoS Framework for 6G. This KI includes following aspects:
1. Investigate whether and what new functionality in 6G QoS framework is required considering, the emerging new traffic characteristics and application needs, e.g. AI/ML application traffic.
NOTE 1: Which working gr... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.6 Key Issue #6: Policy and charging control framework
| To support the Policy and charging control in 6GS, the policy and charging control framework defined in 5G for policies (i.e., SM Policy, UE Policy, AM Policy) is considered as starting point for discussion, the following aspects are to be studied:
1. Whether and how to simplify the policy and charging control framew... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.7 Key Issue #7: Network Exposure
| This key issue is to study whether and how to support a common network exposure framework in 6G. The capabilities that are exposed via the framework fall into one of two categories.
1. The first category is new capabilities. New capabilities refer to capabilities that are not exposed in the 5G network. This category o... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.8 Key Issue #8: Network Sharing in the 6G system
| Study on how to support network sharing in 6G, including the following aspects:
1) How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.9 Key Issue #9: Localized Service Access
| The scope of localized service access is to study the overall architecture design and enablers for localized service access in 6G, which consists of the following:
1. Whether and how to support localized service access provided via PLMN, and study how to perform authorization and authentication of UE for localized ser... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.10 Key Issue #10: FWA / Fixed Wireless Access
| The key issue aims to:
1) Analyse issues encountered in 5G deployments to efficiently support FWA and determine requirements to be taken by other KIs for 6G. The result of this analysis will serve as the basis for architectural requirements to relevant Key Issues related with WT 1.1 and WT 1.2.
NOTE: As the result of... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.11 Key Issue #11: Support of non-3GPP access
| NOTE 1: The UE can access the 6G CN via non-3GPP access even if there is no 3GPP access available.
NOTE 2: Coordination with SA3 for authentication aspects will be needed for this KI.
NOTE 3: The dependency/interaction of non-3GPP access and 3GPP access should be minimized.
For non-3GPP access:
1. Study how to supp... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.12 Key Issue #12: Voice Services for 6G
| This Key Issue will investigate how to support voice services for the 6G system (referring to the mechanisms used in 5GS to support voice services as the starting point for discussion) – the following aspects will be studied:
1. How the 6GS natively supports IMS based voice over the 6G access network, including how a ... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.13 Key Issue #13: Emergency Voice Services for 6G
| This key issue will investigate how to support emergency voice services over the 6G system using the capabilities defined for voice service in Key Issue 12.
Additionally, this key issue will study:
1. The functionality required in the UE and the 6G system to enable emergency voice service for 6GS.
2. The functionali... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.14 Key Issue #14: Location Services for 6G
| This Key Issue will investigate how to support location service in 6G – the following aspects will be studied:
1. The architecture to support location services in 6GS.
2. How to support regulatory location services for emergency voice service in 6GS.
3. How to support location service exposure.
NOTE 1: The focus in... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.15 Key Issue #15: Messaging Services for 6G
| For messaging service in 6G this Key Issue will study:
1. How to support short message services (SMS) in 6GS as per the service requirements specified in TS 22.101 [8], TS 22.261 [9], TS 22.105 [10]
NOTE: For SMS to Emergency centre support it is assumed that the outcome of 5G-Advanced Rel-20 study will be adopted al... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.16 Key Issue #16: Other Essential/Regulatory Services for 6G
| This Key Issue will study the following services:
1. How to support Multimedia Priority Services (MPS) in 6GS.
2. How to provide priority treatment to access control, signalling and media packets delivery for Mission Critical Services (MCX Services) in 6GS.
NOTE 1: It is assumed that 6GS will support Public Warning ... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.17 Key Issue #17: Migration and Interworking
| This key issue studies how to support migration and interworking, including:
1. How to support migration to 6GS
2. How to support interworking with 5GS
3. Whether and how to support interworking with EPS
NOTE 1: Whether to support interworking with EPS will depend on SA1 requirement.
4. How to support interworking... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.18 Key Issue #18: AI for 6G architecture
| Study how to support and enable use of AI in 6G (e.g. AI agent, AI framework).
NOTE 1: The term AI agent refers to the general concept of agents autonomously performing tasks on behalf of users, systems, and/or applications. As the SA1 work is still in progress, adapting the definition of AI agent from SA1 and the us... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.19 Key Issue #19: 6G Network for AI
| This key issue is based on the WT#3.2 about the 6G network for AI.
NOTE 1: The term AI agent refers to the general concept of agents autonomously performing tasks on behalf of users, systems, and/or applications. As the SA1 work is still in progress, adapting the definition of AI agent from SA1 and the use of the ter... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.20 Key Issue #20: Integrated Sensing and Communication
| Study the integration of Sensing and Communication over 3GPP access, covering RAN node and UE operating as 3GPP Sensing Entities in the different sensing modes in alignment with TSG RAN, and considering multiple sources of sensing data.
The following aspects will be studied:
1) Architecture and functional support fo... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.21 Key Issue #21: 6G data framework in SA2
| NOTE 1: Coordination (as requested by SA plenary LS SP-251261) with SA5 is required. Common functionalities for data handling may be identified between SA2 and SA5 to be coordinated with each other to avoid incompatible or duplicated solutions for data framework.
The Key issue is based on WT#5, which includes the foll... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.22 Key Issue #22: 6G Computing Support
| Study aspects on support of computing for UE, core network and application server in 6G (e.g. coordination among UE, core network and application server, exposure of computing service in the core network, etc.).
In order to support computing, the following aspects need to be studied:
1. Identification of the architec... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.23 Key Issue #23: Support of 6G NTN
| Study how to support 6G RAT for NTN, based on RAN decision, and support service continuity aspects.
NOTE 1: The detailed scope for this KI will be coordinated and aligned with RAN in Q1 2026. A checkpoint is set to Q1 2026 to revisit WT/KI descriptions if needed before discussing solutions.
NOTE 2: This KI has IWK a... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.24 Key Issue #24: Analyse 5GS IoT features and solutions
| This key issue will study how to support cellular IoT enablers in 6G including:
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1 Analyse whether and which 5GS cellular IoT features are applicable to 6G and identify which of these features that should be further studied.
| NOTE 1: Enhancements in 6G to the selected 5GS IoT features are not precluded.
NOTE 2: Features driven by this key issue are expected to be generic and may apply to any UEs in 6G.
NOTE 3: The detailed scope for this key issue will be coordinated and aligned with Massive Communication (IoT) requirements from RAN and ... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 6 Solutions
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 6.0 Mapping of Solutions to Key Issues
| Editor's note: Solutions are documented in separate clauses per Key Issue (see clause 6.X) to structure the solution descriptions and get a reasonable overview when there are many solutions (similar to how TRs for 4G and 5G were structured). A separate mapping table is thus not needed.
Table 6.0-1: Mapping of Solution... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 7 Interim agreements
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 7.1 Agreed Principles
| 7.1.Y Agreed Principles for KI#Y
Editor's note: This clause will include the principles that are agreed as work progresses for the specific KI#Y. This may be populated directly or e.g. also when a topic in Annex B gets resolved and a principle is agreed.
Where there is consensus, interim agreements (e.g. solution pr... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 8 Consolidated 6G architecture interim agreements
| Editor's note: This clause can be used to consolidate system architecture aspects based on the consensus building around solutions proposed in clause 6. Whether to use this clause and how it relates to clause 9 will be determined as the study progresses.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 9 Conclusions
| Editor's note: This clause will capture conclusions for the study.
By consensus interim agreements can become part of the final conclusions of the study.
Annex A:
Work Tasks
A.0 Introduction
Editor's note: This Annex will capture updates to WT scope based on the 6G SID in SP-250806. The plan is to update the St... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1.1 Determine how to fulfil requests from the UEs or AFs when intent is included and, in order to ensure interoperability of intents and supporting system test cases, determine the constraints on the use and expression of intents sent from the UEs and the AFs so that the intents can be processed and interpreted unambig... | |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1.2 Determine how to fulfil requests when intent is not included.
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1.3 In order to enable AI capable entities in 6G CN to dynamically compose parts of procedures to fulfil requests from UEs and AFs, determine the design principles and constraints for the modularisation of the procedures for the 6G CN that will be applicable to the system procedures defined in the normative work. How t... | NOTE 2: An intent refers to expectations including requirements, goals, conditions, guidelines, and constraints, without specifying how to achieve them. What intent means and how to specify intents in SA2 specifications will be determined by the study. Intent is to be specified as a result of this work task.
NOTE 3: W... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1 Study whether and how to optimize NF/NF service registration, discovery and selection for efficient message forwarding compared with 5G.
| |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.81 Key Issue #81: Network Sharing in the 6G system
| Study on how to support network sharing in 6G, including the following aspects:
1) How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
|
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 5.102 Key Issue #102: FWA / Fixed Wireless Access
| The key issue aims to:
1) Analyse issues encountered in 5G deployments to efficiently support FWA and determine requirements to be taken by other WT KIs for 6G. The result of this analysis will serve as the basis for architectural requirements to relevant Key Issues related with WT 1.1 and WT 1.2.
NOTE: As the result... |
f911fc6f2b5a5f998d00bb20b26a3c9a | 23.801-01 | 1 Analyse whether and which 5GS cellular IoT features are applicable to 6G and identify which of these features that should be further studied.
| NOTE 1: Enhancements in 6G to the selected 5GS IoT features are not precluded.
NOTE 2: Features driven by this WT are expected to be generic and may apply to any UEs in 6G.
NOTE 3: The detailed scope for WT#8 will be coordinated and aligned with Massive Communication (IoT) requirements from RAN and SA1. Ambient IoT,... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 1 Scope
| The present document is a technical report capturing the study on enhancement to application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 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.
-... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3 Definitions of terms, symbols and abbreviations
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
ASCAI: Applicat... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4 Key issues
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1 Key Issue #1: AIML model storage and deployed on satellite
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1.1 Description
| In 3GPP's TS 23.482 [8], SA6 defines the architecture of AIML enabling services and related AIML business processes. Existing AIML-enabled services provide different users or third-party entities with services for searching, storing, and calling AIML models by providing a platform. Based on the SA6 process, users can c... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1.2 Open Issues
| This key issue will study:
1. Investigate different deployment options for AIMLAPP when AIML models are deployed on satellite and study whether/how to deploy AIMLE on satellite (e.g. ML repository/ADAES on satellite to perform data processing/interference based on collected remote data).
2. Whether/how to storage AIM... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2 Key Issue #2: Satellite based AIML service maintenance while losing connection with terrestrial network
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2.1 Description
| The relative positions of satellites (such as low-orbit and medium-orbit satellites) other than geosynchronous Earth orbit (GEO) satellites to the AIML service platform on the terrestrial network are constantly changing. Considering the scenario where AIML models are deployed on satellites, there are specific time wind... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2.2 Open Issues
| This key issue will study:
1. Whether and how to support satellite based AIML service management when losing connection with terrestrial network (e.g. When a satellite is supporting AIML service connection or related data collection, the satellite keeps connection with terrestrial network due to exceeding the availabl... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3 Key Issue #3: Support satellite selection in data delivery
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3.1 Description
| When operators deploy some components of the SEALDD architecture on satellites to ensure reliable data transmission via satellite communications, the following scenario may occur: to reduce latency, users initially select low-orbit satellites for satellite data transmission. However, due to the shorter connection time ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3.2 Open Issues
| This key issue will study:
1. When a satellite is handling received message request, whether and how to select proper satellites in the same orbit for data delivery (e.g. selection between satellites to ensure continuity of data transmission to terrestrial network).
2. When data delivery handling is moved to another... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.4.1 Description
| The 3GPP stage-1 spec. TS 22.261 [2] provides the service requirements for the support of efficient content delivery. Emphasizing the video-based services and personal data storage applications, it brings up that the in-network content caching can be provided by an operator, a third-party or both, to improve user exper... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.4.2 Open Issues
| This Key issue is proposed to study the enhancement of the application enablement architecture for the support of efficient content delivery over the satellite access:
- Whether and how to enhance the application enablement architecture layer and/or application enabler (e.g., SEALDD) to support the deployment of conte... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.5.1 Description
| 3GPP TS 23.434 [4] describes Location Management service that offers the location management related capabilities to one or more vertical applications. The location management server is a functional entity that receives and stores user location information and provides user location information to the vertical applicat... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.5.2 Open issues
| To support the location management service with satellite service, the following aspects need to be studied:
- How to support history location data, monitoring location deviation events, periodic verify UE location when the UE is connected via satellite access, during the loss of service link or feeder link?
4.6 Key ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.6.1 Description
| In Rel-19, the normative work on application enablement for satellite enabled 5G services has been specified which including usage of satellite access characteristics for the application enablement, edge computing on satellite, satellite access with discontinuous coverage, impact on MC service and so on. Especially the... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.6.2 Open Issues
| Based on the above analysis, the following open issues need to be studied:
- Whether and how to provide/expose the preferred and/or predicated satellite related information (e.g. satellite/time/area) to the consumers when using the satellite, utilizing the analysis from (e.g. ADAES, ALMLE).
- Whether and how to provi... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5 Solutions
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.0 Mapping of solutions to key issues
| Table 8.1-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI#5
KI#6
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1 Solution #1: Support of application satellite coverage availability information (ASCAI) analysis
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.1 Solution description
| This solution addresses the KI#6.
The VAL server or the UE may act as consumers to subscribe the analysis related to the application satellite coverage availability information (ASCAI) from ADAES. They may ask to analyse the application satellite coverage availability information of the target UE to assist the UE's s... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.1.1 Procedure of Satellite related information subscription request
| Figure 5.1.1.1-1 illustrates the high-level procedure of Satellite related information subscription request.
Pre-condition:
- The following NFs in the application enablement layer (e.g., ADAES, CMS, and LMS) are all deployed on the ground.
Figure 5.1.1.1-1: Procedure of Satellite related information subscription ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.4 Solution evaluation
| This solution addresses the KI#6 to provide the application satellite coverage availability information (ASCAI) analytics when the VAL UE is using the satellite access.
The solution has no impact on the existing architecture. The ADAES can be enhanced to obtain the satellite related information from the SEAL servers ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2 Solution #2: Support of QoS analysis for services over satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.1 Solution description
| This solution addresses the KI#6.
The VAL server or the UE may act as consumers to subscribe the QoS analysis related to the services over satellite access from ADAES. They may ask to provide the preferred or predicted QoS for the requested service over satellite access.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.1.1 Procedure of QoS analysis for services over satellite access
| Figure 5.2.1.2-1 illustrates the high-level procedure of QoS analysis for services over satellite access.
Pre-condition:
- The ADAES, VAL UE, VAL server, 3GPP CN (e.g., NWDAF) are all deployed on the ground.
- The target UE is accessing the satellite.
Figure 5.2.1.1-1: Procedure of QoS analysis for services o... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.4 Solution evaluation
| This solution addresses the KI#6 to support the QoS analysis for the services over the satellite access in the application enablement layer.
The solution has no impacts on the existing architecture. The ADAES can be enhanced to obtain the satellite communication related information for the target UE from the 3GPP cor... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3 Solution #3: Location management service via satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.0 General description
| Figure 5.3.0-1, illustrates the deployment of location enabler on-board satellite for assisting location management service.
Figure 5.3.0-1: Deployment of location enabler on-board satellite for assisting location management service
Basically, in this architecture option, SEAL location management server is deployed... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.1 Solution description
| Figure 5.3.1-1 illustrates the procedure for on-board satellite location management server assisting SEAL location history procedure specified in 3GPP TS 23.434.
Pre-conditions:
1. The location management server on-board satellite is deployed to assist the value-added location information.
Figure 5.3.1-1: Procedur... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.2 Architecture Impacts
| SEAL location management server is expected to be deployed on-board satellite. And the SEAL-E interface LM-E is required to support interaction between LMS on-ground to LMS on-board satellite.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.3 Corresponding APIs
| This solution impacts the SEAL-E interface LM-E with new interactions between LMS on-ground to LMS on-board satellite to support SEAL location history service via satellite access.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.4 Solution evaluation
| This solution provides a proposal to address the open issues listed in key issue#5 by supporting location management service via satellite access. Architecture impacts are identified where location management server is required to be deployed on-board satellite. SEAL-E interface LM-E is required with new interactions b... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4 Solution #4: Enhance SEALDD to support satellite selection in data delivery
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.1 Architecture
| This solution is based on the SEALDD architecture as in 3GPP TS 23.433 [3].
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2 Solution description
| This solution addresses the KI#3, i.e., support satellite selection in data delivery.
Because the KI description states that operators deploy some components of the SEALDD architecture on satellites to ensure reliable data transmission via satellite communications, the solution proposes to deploy the SEALDD servers on... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.1 Procedures
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.1.1 SEALDD enabled transmission with satellite selection support in data delivery
| Figure 5.4.2.1.1-1 illustrates the procedure for the source SEALDD (or S-SEALDD) server to discover and select a target SEALDD (or T-SEALDD) server based on Application Satellite Coverage Availability Information or ASCAI, and then handle the switching of serving satellites along with the context transfer between the S... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.2 Information flows
| The following information flows are based on from the clause of 9.2.3.1 in the 3GPP TS 23.433 [3]. All new changes are in bold.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9.2.3.1 SEALDD enabled regular transmission request
| Table 9.2.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the regular application transmission service.
Table 9.2.3.1-1: SEALDD enabled Regular transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
I... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2 Architecture Impacts
| This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5 Solution #5: Using SEALDD to enhance application enablement layer for efficient content delivery over satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.1 Architecture
| This solution is based on the SEALDD architecture as in 3GPP TS 23.433 [3].
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2 Solution description
| According to the 3GPP TS 23.433 [3], the SEALDD server offers the storage capabilities, which supports the data storage and storage management for VAL client/server, SEALDD client and other SEALDD servers. The VAL client and VAL server may coordinate to determine the usage of the SEALDD storage service. For efficient c... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.1 Procedures
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.1.1 SEALDD enabled transmission for efficient content delivery
| Figure 5.5.2.1.1-1 illustrates the procedure for the SEALDD server to determine the content caching capability of the SEALDD client, establishing the data transmission connection with the SEALDD client for efficient content delivery (or so-named ECD), as well as the SEALDD layer utilizing the satellite services to tran... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2 Information flows
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.1 SEALDD enabled ECDforSatAccess transmission request
| Table 5.5.2.2.1-1 describes the information flow from the VAL server to the SEALDD server to enable the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.1-1: SEALDD enabled ECDforSatAccess transmission request
Information element
Status
Description
VAL server ID
M
Identit... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.2 SEALDD enabled ECDforSatAccess transmission response
| Table 5.5.2.2.2-1 describes the information flow from the SEALDD server to the VAL server to respond to the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.2-1: SEALDD enabled ECDforSatAccess transmission response
Information element
Status
Description
Result
M
Success ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.3 SEALDD enabled ECDforSatAccess transmission notification
| Table 5.5.2.2.3-1 describes the information flow from the SEALDD server to the VAL server to notify the events related to the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.3-1: SEALDD enabled ECDforSatAccess transmission notification
Information element
Status
Description... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2 Architecture Impacts
| This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.