hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 service access, and minimize service interruption during UE mobility, including
a) Whether, how and which aspects (e.g., provisioning, updating, retrieval) for the part of subscription (that is needed for localized service access) can be performed/managed via the NFs present locally in the network providing localized service access.
NOTE 1: Network selection and access control are not to be studied for bullet 1 and bullet 2.
NOTE 2: For the case when localized service access is provided via PLMN, solutions are expected not to introduce additional UE functionality that is specific for localized service access (i.e., anything that requires UE dependency beyond what is needed for general PLMN access).
NOTE 3: Authentication aspects need to be coordinated with SA3
2. Study whether and how to make use of 5G NPN (SNPN and PNI-NPN) for localized service access in 6G.
NOTE 4: Which of the existing features will be supported will be determined during the study.
NOTE 5: Access control principles defined for NPN (SNPN and PNI-NPN) in 5G are assumed to be reused. Network selection principles defined for SNPN are assumed to be re-used, but remit stays within CT1.
NOTE 6: Session and service continuity between PLMN and SNPN using direct interface between PLMN and SNPN is out of scope of this work task.
|
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 this analysis will serve as the basis for architectural requirements to Key Issues related with other Work Tasks, this analysis needs to conclude for June 2026.
|
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 support untrusted non-3GPP access in 6G System architecture.
2. Study how to support service continuity between 3GPP access and non-3GPP access in the above bullet(s).
3. Study how to support Interworking aspects between 5GS and 6GS related to non-3GPP access.
NOTE 4: Coordination with other KIs is needed.
NOTE 5: Solutions to above bullets may support connectivity via non-3GPP access only.
NOTE 6: Solution discussion on Simultaneous connectivity via 3GPP and non-3GPP access with only per flow granularity can only start from SA2#175, but with low priority at SA2#175 if time allows.
For Non/Seamless WLAN Offload:
4. How to support UE policy necessary for Non-Seamless WLAN Offload (NSWO).
|
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 UE supporting 6G RAN selects and connects to 6G network for voice service.
2. Whether and how to update the IMS specification to support an IP-CAN in the 6GS.
3. How to support the voice continuity between 6G RAT and selected 3GPP RATs or between 6G RAT and selected non-3GPP Accesses when 6G RAT supports voice natively.
4. How to support migration to Vo6G.
5. Whether and how to support voice services if they are not provided in the serving 6G Network (Assuming this covers both domain selection and RAT/System selection at the time of the call).
6. How to support the compatibility between 6G CN and the existing deployed IMS with minimum impacts on the existing deployed DIAMETER interfaces (e.g. Rx, Cx, Sh).
NOTE 1: For bullet 6, coordination with CT is required, including to consider whether SA WG2 or CT WG leads the study.
NOTE 2: Support of voice services via 6G NTN need to be coordinated with WT#7 (KI#23).
NOTE 3: Interworking, migration and service continuity aspects need to be coordinated with WT#2 (KI#17). Interworking with 2G/3G and CS (Circuit switch) for voice are not considered in this Key issue.
NOTE 4: The existing IMS architecture is used as a starting point for the study.
NOTE 5: The study will be aligned with RAN and coordinated where needed.
NOTE 6: This Key issue should consider roaming aspects.
|
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 functionality required in the UE and the 6G system to establish emergency session via 6GS for the emergency voice service.
3. How to identify emergency services in 6GS in case of non-UE detectable emergency call, such that the required treatment for an emergency call is applied.
4. How to support a UE in Limited-Service state so that it can establish emergency session via 6GS.
5. Whether and how to support emergency voice services if they are not provided in the serving 6G Network (Assuming this covers both domain selection and RAT/System selection at the time of the call).
|
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 this release of the specifications will be on the required location service capability to support emergency and other regulatory services.
NOTE 2: A unified location service architecture should be pursued (using 5GS as the starting point for discussion), by considering the location service requirement in this KI and from other KI(s) if any.
NOTE 3: Coordination with RAN WG for RAN aspects, SA3 for privacy and user consent aspects and SA5 for OAM and charging aspects will be needed.
|
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 also for 6G.
|
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 System (PWS). Stage 2 capabilities for PWS will be specified by CT.
NOTE 2: The scope will keep alignment with RAN.
|
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 between 6GS and 4G/5G NTN/satellite access that use EPS/5GS.
NOTE 2: Interworking with 2G/3G are not considered in this study. Interworking between 6GS and 5GS is required to work even if the UE has previously registered in 2G, 3G or 4G.
NOTE 3: The detailed migration study scope and migration options will be coordinated and aligned with RAN.
NOTE 4: Additional migration options beyond stand-alone, MRSS and inter-RAT mobility between NR and 6GR, will be studied no earlier than June 2026 in alignment with TSG RAN (if needed).
NOTE 5: It is assumed that interworking for roaming is within the scope of this work task.
NOTE 6: This work task focuses on general interworking procedures. The specific interworking aspects studied in other KIs (if any) need to follow the general interworking procedures.
|
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 use of the term AI agent will be determined as part of the study. AI agent does not imply any specific solution.
The AI for the 6G architecture shall be multi-vendor interoperable, reliable and sustainable.
NOTE 2: It is assumed that operators can decide whether and which AI capabilities and technologies to deploy in their network.
Study whether and how to provide an architecture for AI to fulfil the following:
1. enable the 6G CN to leverage AI capabilities and technologies in the 6G CN (e.g. AI agent), subject to operator policies and configuration and using 6G CN functionalities available in the network:
a) 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 unambiguously by the AI capable entities in the 6G CN, and define the mechanisms required to support these constraints.
b) determine how to fulfil requests when intent is not included.
c) 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 to enable the AI capable entities to compose these procedures in SA2 specifications will be determined by the study.
NOTE 3: 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 key issue.
NOTE 4: Whether to support intents in a 6G CN is up to operator choice. It is assumed it is not required for the MT stack of UE to produce nor understand the intent. The MT stack of UE is assumed to be agnostic to whether or not the network uses 6G CN AI capable entities (e.g. AI agent, AI-enabled NFs) to address UE requests not including intent.
NOTE 5: This should not result in duplicated procedures in 3GPP specifications. It is assumed that the 6G study will still describe 6G system procedures for the 3GPP features, without necessarily requiring AI capabilities.
2. enable closed-loop operations and learning techniques such as reinforcement learning, in 6G CN.
3. enable entities in 6G CN to access network AI capabilities provided by 6G NFs.
4. enable AI capable entities in 6G CN to access trusted external capabilities provided by AF.
NOTE 6: Whether and what external capabilities provided by AF is accessed by AI capable entities will be discussed as part of the study.
5. enable the monitoring of the performance of all AI capable entities in 6G CN.
6. enable the operator to control the network's use of AI capabilities in its 6G CN, i.e. support different operator-configurable levels of autonomy based on operational needs, including the option to use or not use any AI capabilities.
7. support roaming scenarios, e.g. how visited networks using or not using AI technologies can interwork with home network using or not using AI technologies.
8. enable NFs of the 6G CN to have AI/ML capabilities, ML model provisioning, inferencing, training and monitoring.
9. enable the 6G CN AI architecture to ensure interoperability with 5G CN AI architecture if needed, for the purpose of maintaining a consistent service for UEs across 5G and 6G.
NOTE 7: How to process the intent when AI capabilities are not being used is to be studied as part of this key issue.
NOTE 8: Aspects related to SA3, SA5, SA6 will be coordinated with each group respectively during the study.
NOTE 9: Further alignments with SA1 consolidated requirements may be needed.
NOTE 10: This key issue does not cover AI agents in UE, which is covered by KI#19.
NOTE 11: Coordination across the KIs in the 6G study is needed.
NOTE 12: This key issue will not duplicate the work in the scope of KI#1.
|
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 term AI agent will be determined as part of the study. AI agent does not imply any specific solution.
1. Study whether and how to support an AI agent on a UE to discover another AI agent on a different UE via the 6G network(s).
2. Study whether and how to enable communication for AI agents on different UEs via the 6G network(s) e.g., identification and authorization of an AI agent on a UE.
3. Study whether and how to enhance network capability exposure functionalities to AI agent on AF(s).
NOTE 2: Coordination with KI#7 for Network Exposure is required.
NOTE 3: During the study, which aspects will belong to SA2 or SA6, or required coordination with SA6 on the application layer aspects will be discussed, if needed. And coordination with SA3 on security aspects may be needed.
NOTE 4: When AI agent is on the UE, this AI agent is assumed not part of the MT. It is also assumed that this KI is not replacing UE to Core Network interaction, NAS.
NOTE 5: The AI agent in this KI is outside of RAN and Core Network for 6G.
4. Study whether and how the 6G CN can provide AI services (i.e., AI inferencing and AI training) to applications (AF or in UE).
5. Study the potential system impacts based on the characteristics of AI traffic.
NOTE 6: Coordination with KI#5 QoS may be needed.
NOTE 7: System enhancement related to QoS for AI traffic will be handled by KI#5 QoS,
NOTE 8: Which working groups will determine the characteristics of AI traffic is subject to SA plenary (SA#110) decision.
NOTE 9: Coordination with SA3, SA5 and SA6 may be needed on AI inferencing and AI training.
NOTE 10: Coordination with KI#21 and KI#22 may be needed.
NOTE 11: New service charging part may be coordinated with SA5 Charging group.
|
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 for Sensing Service, including:
a) Sensing Service authorization and revocation.
b) Discovery and (re-)selection of Sensing function and Sensing Entities (i.e. RAN nodes, UEs), including sensing modes selection.
c) Configuration parameters and policy provisioning to support sensing service, e.g., to the selected Sensing Entities, Sensing function, etc.
d) Collection and transport of 3GPP sensing related data for sensing result generation.
e) Exposure framework of sensing result to the Sensing service consumer (i.e. AFs, UEs, Core NFs).
NOTE 1: How the Sensing service consumer makes use of the sensing results is not part of this key issue.
2) Whether and how to support Sensing Service in consideration of the mobility of the UE as sensing entity.
3) Whether and how to support providing sensing data, which is not obtained from 3GPP radio signals, to the Sensing Function for sensing result generation.
NOTE 2: This includes sensing data obtained using technologies that are different from 3GPP defined ISAC mechanisms, such as sensing based on IEEE 802.11, camera, sonar, lidar, etc.
NOTE 3: The scope of this KI assumes RAN node and UE operating as Sensing Entities in different sensing modes in alignment with TSG RAN.
NOTE 4: Coordination with other KIs will be needed if identified, e.g., Sensing data aspects with KI#21, architectural aspect with KIs corresponding to WT#1, etc.
NOTE 5: Coordination with RAN WG for RAN aspects, SA3 for privacy and user consent aspects, and SA5 for OAM and charging aspects will be needed. Coordination with SA6 may be needed on aspects to be identified during the study.
NOTE 6: The scope of this KI will be aligned with RAN for 6G in Q1 2026. A checkpoint is set for Q1 2026 to revisit WT/KI descriptions and determine if solutions can be discussed in Q2 2026.
|
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 following aspects:
1. Identify high level use cases (e.g. AIML in the core, UE data collection for UE-sided model training, Sensing) potentially subject to the data framework.
NOTE 2: This identification does not predetermine whether the use cases will ultimately adopt the data framework solutions. The coordination with other WTs for specific use cases is needed.
NOTE 3: The use of the term “data framework” does not imply that all use cases that will be identified need to be supported by the same set of functionalities, procedures, NFs, services and/or use the same data structure/format
2. Study required data framework functionalities to support the identified use cases, e.g:
a) data discovery and data registration
b) data collection and transfer (including configuration of the data source (e.g. about collected data, reporting period and mechanisms to use), transfer of the collected data (including data distribution) )
c) data labelling/metadata handling
d) data processing (e.g. data anonymization, data analysis, data generation, etc.)
e) data storage and retrieval
f) data exposure
The functionalities above may need to consider the quality of data, latency and data volume.
NOTE 4: The bullet 1 and bullet 2 can be studied in parallel, e.g. each solution is expected to include or refer to the corresponding use case(s).
NOTE 5: Coordination with SA5 may be required for charging aspects.
NOTE 6: Consideration on MNO's requirements of visibility and controllability during data handling processes is required.
NOTE 7: The outcome of 5GS studies in R20 and normative work in previous releases on data handling will be considered.
3. Study potential system impacts of user consent, privacy, security and data governance from SA2 architectural and system level perspective for data generated in 6G system corresponding to the use cases and functionalities in aspects 1 and 2.
NOTE 8: Coordination with SA3 is required for user consent, privacy, security and data governance related topics to avoid duplicated or incompatible design. SA2 should study first which use cases and functionalities in aspects 1 and 2 above apply to aspect 3 and then coordinate with SA3. SA2 should consider the output of SA3 before specifying any system procedure on this topic.
|
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 architectural requirements and computing resource(s):
a) Derive architectural requirements for scenario(s) and service requirements defined by SA1 to be enabled by the Computing Service.
b) Whether and how to define the computing resource (e.g., computing resource type and/or status, location of the computing resource, etc.).
NOTE 1: The use cases and the terms of Computing Service and the Service Hosting Environment defined in TR 22.870 [11] can be used as starting point for further refinement during solution development phase. The detailed computing resource type (e.g., software component, hardware component, etc.) can be identified during study phase.
2. Enablement/authorization of computing service to UE or AF.
a) Whether and how to enable Computing Service.
b) Whether and how the operator network may expose the computing resource related information (e.g., its hosting capability (e.g. using compute resources at Service Hosting Environment)) and/or network metrics to AF.
3. Coordination of communication and computing, service continuity and QoS aspects:
a) Whether and how to coordinate (e.g., within or outside the core network) communication (for the traffic transferred over user plane) and computing resource(s) in the Computing Site.
b) Whether and how to identify, collect/monitor, provision the computing resource related information.
c) Whether and how to improve the service experience
d) Whether there is a need to improve QoS to satisfy Computing Service requirements.
e) Whether and how to support service continuity for computing service upon change of computing site and/or user plane function (e.g., due to UE mobility, computing load balancing, AF influence etc.).
4. Discovery and (re-)selection of compute site(s) for the Computing Service:
a) Whether and how to discover and (re-)select Computing Site(s) for the Computing Service.
NOTE 2: Whether and how to utilise and/or enhance Edge Computing mechanisms specified in 5G to address the aspects in the scope of this KI will be discussed in the study phase.
NOTE 3: Which of above aspects should fall into SA5 and/or SA6 scope will be further identified in study phase, coordination with SA5 and SA6 may be needed.
NOTE 4: Potential coordination with other KIs (e.g., KI#1 on service enablement and UE-CN interaction, key issues on QoS, exposure framework and UP aspects, etc.) is needed.
NOTE 5: Computing Site represents the computing resources in a specific location of network topology. The computing site can offer computing services by allocating its computing resources to run application workloads upon demand of a Computing Service consumer. From networking perspective, the Computing Site is located within 6G CN (via e.g. user plane function in 6G) or Data Network (either owned and controlled by the operator or 3rd party).
|
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 aspects that are scoped under WT#2 (KI#17).
NOTE 3: This KI has dependency on mobility aspects that are scoped under WT#1.1 (KI#1).
NOTE 4: This KI has voice aspects that are scoped under KIs corresponding to WT#1.4.
|
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 SA1. Ambient IoT, NB-IoT and non-3GPP access are not in the scope of the key issue.
5.X Key Issue #X: Key Issue Title
|
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 Solutions to Key Issues
Key Issues
Solutions
#P
#Q
#X
#Y
6.X Solutions to KI#X
6.X.Y Solution #X.Y: <Solution Title>
6.X.Y.0 High-level solution Principles
Editor’s note: A description of which KI(s), and which parts of each KI, the solution addresses should be included, in addition to the high-level solution principles.
Editor's note: Where possible similar/overlapping solution proposals should be documented as a single solution in the TR.
Documentation of more than one solution from the same company for the same KI is allowed but it shouldn't be expected that all of them will be documented in the TR.
6.X.Y.1 Description
Editor's note: This clause will describe the solution principles and architecture assumptions for corresponding key issue(s). Further (sub-)clause(s) may be added to capture details.
6.X.Y.2 Procedures
Editor's note: This clause will describe the high-level procedures and information flows for the solution.
6.X.Y.3 Impacts on Services, Entities and Interfaces
Editor's note: This clause captures impacts on existing services, entities and interfaces.
|
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 principles descriptions) should be documented in the TR as soon as possible during a study.
These can be documented in the TR as "7.1.Y Agreed Principles for KI#Y" in the "Interim Agreements" clause. If the interim agreement has impacts on another clause in the TR and if there is consensus, that TR clause can be updated.
|
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 Study Item Description with updated Work Task descriptions from this Annex.
This Annex contains clarifications of Work Task scope, as preparation for Key Issue drafting.
A.0a Mapping between Work Tasks and Key Issues
Editor's note: This clause will capture a table containing WT to KI mapping.
Table A.0a-1: Mapping of Work Tasks to Key Issues
Key Issues
Work Task
#1
#2
#1.2.1
X
#1.2.3
X
-
Work Tasks
Key Issues
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
WT#1.1
X
WT#1.2 SBA
X
WT#1.2 network slicing
X
WT#1.2 user plane
X
WT#1.2 QoS
X
WT#1.2 policy framework
X
WT#1.2 network exposure
X
WT#1.2 network sharing
X
WT#1.2 localized service access
X
WT#1.2 FWA
X
WT#1.3
X
WT#1.4
X
X
X
X
X
WT#2
X
WT#3.1
X
WT#3.2
X
WT#4
X
WT#5
X
WT#6
X
WT#7
X
WT#8
X
A.X Work Task X
Editor's note: Description of Work Task X. Clauses can be used if needed.
A.1 Work Task 1
A.1.1 Work Task 1.1: Study the support for control signalling for 6G System
Editor's note: The content of this clause is TBD, pending study progress.
1. Study the support for control signalling for 6G System, including at least the following:
a. Whether and how to enable the introduction of a new non-access stratum functionality with minimal or no impact to other non-access stratum functionalities.
NOTE 1: It is assumed that WT#1.1 bullet 1a covers 6G System procedures including functionalities such as mobility management, session management, NAS transport and UE NAS identifiers.
NOTE 2: For the above bullet 1a, target would be not to impact other non-access stratum functionalities when introducing new non-access stratum functionalities. If this is not possible, objective is to minimize impact.
2. Study the support for control signalling for 6G System, including at least the following:
a. Whether and how to support generic mechanisms (e.g. service discovery, service authorization, transport mechanism) for UE to Core Network interaction to support operator services.
NOTE 3: This WT#1.1 bullet 2a can include any transport mechanism such as using NAS or UP or new plane. WT1.1 bullet 2a can have dependency on other work tasks e.g. WT#1.1 bullet 1a, WT#3, WT#4, WT#5, WT#6.
NOTE 4: This WT#1.1 covers operator services.
A.1.2 Work Task 1.2
A.1.2.1 SBA framework
The following is work scope for SBA related work task.
|
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 unambiguously by the AI capable entities in the 6G CN, and define the mechanisms required to support these constraints.
| |
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 to enable the AI capable entities to compose these procedures in SA2 specifications will be determined by the study.
| 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: Whether to support intents in a 6G CN is up to operator choice. It is assumed it is not required for the MT stack of UE to produce nor understand the intent. The MT stack of UE is assumed to be agnostic to whether or not the network uses 6G CN AI capable entities (e.g. AI agent, AI-enabled NFs) to address UE requests not including intent.
NOTE 4: This should not result in duplicated procedures in 3GPP specifications. It is assumed that the 6G study will still describe 6G system procedures for the 3GPP features, without necessarily requiring AI capabilities.
2. enable closed-loop operations and learning techniques such as reinforcement learning, in 6G CN.
3. enable entities in 6G CN to access network AI capabilities provided by 6G NFs.
4. enable AI capable entities in 6G CN to access trusted external capabilities provided by AF.
NOTE 5: Whether and what external capabilities provided by AF is accessed by AI capable entities will be discussed as part of the study.
5. enable the monitoring of the performance of all AI capable entities in 6G CN.
6. enable the operator to control the network's use of AI capabilities in its 6G CN, i.e. support different operator-configurable levels of autonomy based on operational needs, including the option to use or not use any AI capabilities.
7. support roaming scenarios, e.g. how visited networks using or not using AI technologies can interwork with home network using or not using AI technologies.
8. enable NFs of the 6G CN to have AI/ML capabilities, ML model provisioning, inferencing, training and monitoring.
9. enable the 6G CN AI architecture to ensure interoperability with 5G CN AI architecture if needed, for the purpose of maintaining a consistent service for UEs across 5G and 6G.
NOTE 6: How to process the intent when AI capabilities are not being used is to be studied as part of this work task.
NOTE 7: Aspects related to SA3, SA5, SA6 will be coordinated with each group respectively during the study.
NOTE 8: Further alignments with SA1 consolidated requirements may be needed.
NOTE 9: This sub work task does not cover AI agents in UE, which is covered by WT3.2.
NOTE 10: Coordination across the WTs in the 6G study is needed.
NOTE 11: This work task will not duplicate the work in the scope of WT#1.1.
A.3.2 WT#3.2 6G Network for AI:
1. Study whether and how to support an AI agent on a UE to discover another AI agent on a different UE via the 6G network(s).
2. Study whether and how to enable communication for AI agents on different UEs via the 6G network(s) e.g., identification and authorization of an AI agent on a UE.
3. Study whether and how to enhance network capability exposure functionalities to AI agent on AF(s).
NOTE 1: Coordination with WT#1.2 for Network Exposure is required.
NOTE 2: During the study, which aspects will belong to SA2 or SA6, or required coordination with SA6 on the application layer aspects will be discussed, if needed. And coordination with SA3 on security aspects may be needed.
NOTE 3: When AI agent is on the UE, this AI agent is assumed not part of the MT. It is also assumed that this WT is not replacing UE to Core Network interaction, NAS.
NOTE 4: The AI agent in WT#3.2 is outside of RAN and Core Network for 6G.
4. Study whether and how the 6G CN can provide AI services (i.e., AI inferencing and AI training) to applications (AF or in UE).
5. Study the potential system impacts based on the characteristics of AI traffic.
NOTE 5: Coordination with WT1.2 QoS may be needed.
NOTE 6: System enhancement related to QoS for AI traffic will be handled by WT1.2 QoS,
NOTE 7: Which working groups will determine the characteristics of AI traffic is subject to SA plenary (SA#110) decision.
NOTE 8: Coordination with SA3, SA5 and SA6 may be needed on AI inferencing and AI training.
NOTE 9: Coordination with WT#5 and WT#6 may be needed.
NOTE 10: New service charging part may be coordinated with SA5 Charging group.
A.4 Work Task 4: 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 for Sensing Service, including:
a. Sensing Service authorization and revocation.
b. Discovery and (re-)selection of Sensing function and Sensing Entities (i.e. RAN nodes, UEs), including sensing modes selection.
c. Configuration parameters and policy provisioning to support sensing service, e.g., to the selected Sensing Entities, Sensing function, etc.
d. Collection and transport of 3GPP sensing related data for sensing result generation.
e. Exposure framework of sensing result to the Sensing service consumer (i.e. AFs, UEs, Core NFs).
NOTE 1: How the Sensing service consumer makes use of the sensing results is not part of this work task.
2. Whether and how to support Sensing Service in consideration of the mobility of the UE as sensing entity.
3. Whether and how to support providing sensing data, which is not obtained from 3GPP radio signals, to the Sensing Function for sensing result generation.
NOTE 2: This includes sensing data obtained using technologies that are different from 3GPP defined ISAC mechanisms, such as sensing based on IEEE 802.11, camera, sonar, lidar, etc.
NOTE 3: The scope of WT#4 assumes RAN node and UE operating as Sensing Entities in different sensing modes in alignment with TSG RAN.
NOTE 4: Coordination with other WTs will be needed if identified, e.g., Sensing data aspects with WT#5, architectural aspect with WT#1, etc.
NOTE 5: Coordination with RAN WG for RAN aspects, SA3 for privacy and user consent aspects, and SA5 for OAM and charging aspects will be needed. Coordination with SA6 may be needed on aspects to be identified during the study.
NOTE 6: The scope of WT#4 will be aligned with RAN for 6G in Q1 2026. A checkpoint is set for Q1 2026 to revisit WT/KI descriptions and determine if solutions can be discussed in Q2 2026.
A.5 Work Task 5: 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 WT includes the following aspects:
1. Identify high level use cases (e.g. AIML in the core, UE data collection for UE-sided model training, Sensing) potentially subject to the data framework.
NOTE 2: This identification does not predetermine whether the use cases will ultimately adopt the data framework solutions. The coordination with other WTs for specific use cases is needed.
NOTE 3: The use of the term “data framework” does not imply that all use cases that will be identified need to be supported by the same set of functionalities, procedures, NFs, services and/or use the same data structure/format.
2. Study required data framework functionalities to support the identified use cases, e.g:
a. data discovery and data registration
b. data collection and transfer (including configuration of the data source (e.g. about collected data, reporting period and mechanisms to use), transfer of the collected data (including data distribution) )
c. data labelling/metadata handling
d. data processing (e.g.data anonymization, data analysis, data generation, etc.)
e. data storage and retrieval
f. data exposure
The functionalities above may need to consider the quality of data, latency and data volume.
NOTE 4: The bullet 1 and bullet 2 can be studied in parallel, e.g. each solution is expected to include or refer to the corresponding use case(s).
NOTE 5: Coordination with SA5 may be required for charging aspects.
NOTE 6: Consideration on MNO’s requirements of visibility and controllability during data handling processes is required.
NOTE 7: The outcome of 5GS studies in R20 and normative work in previous releases on data handling will be considered.
3. Study potential system impacts of user consent, privacy, security and data governance from SA2 architectural and system level perspective for data generated in 6G system corresponding to the use cases and functionalities in aspects 1 and 2.
NOTE 8: Coordination with SA3 is required for user consent, privacy, security and data governance related topics to avoid duplicated or incompatible design. SA2 should study first which use cases and functionalities in aspects 1 and 2 above apply to aspect 3 and then coordinate with SA3. SA2 should consider the output of SA3 before specifying any system procedure on this topic.
A.6 Work Task 6: 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:
WT#6.1: Identification of the architectural requirements and computing resource(s):
a. Derive architectural requirements for scenario(s) and service requirements defined by SA1 to be enabled by the Computing Service.
b. Whether and how to define the computing resource (e.g., computing resource type and/or status, location of the computing resource, etc.).
NOTE 1: The use cases and the terms of Computing Service and the Service Hosting Environment defined in TR22.870 can be used as starting point for further refinement during solution development phase. The detailed computing resource type (e.g., software component, hardware component, etc.) can be identified during study phase.
WT#6.2: Enablement/authorization of computing service to UE or AF.
a. Whether and how to enable Computing Service.
b. Whether and how the operator network may expose the computing resource related information (e.g., its hosting capability (e.g. using compute resources at Service Hosting Environment)) and/or network metrics to AF.
WT#6.3: Coordination of communication and computing, service continuity and QoS aspects:
a. Whether and how to coordinate (e.g., within or outside the core network) communication (for the traffic transferred over user plane) and computing resource(s) in the Computing Site.
b. Whether and how to identify, collect/monitor, provision the computing resource related information.
c. Whether and how to improve the service experience
d. Whether there is a need to improve QoS to satisfy Computing Service requirements.
e. Whether and how to support service continuity for computing service upon change of computing site and/or user plane function (e.g., due to UE mobility, computing load balancing, AF influence etc.).
WT#6.4: Discovery and (re-)selection of compute site(s) for the Computing Service:
a. Whether and how to discover and (re-)select Computing Site(s) for the Computing Service.
NOTE 2: Whether and how to utilise and/or enhance Edge Computing mechanisms specified in 5G to address the aspects in the scope of WT#6 will be discussed in the study phase.
NOTE 3: Which of above aspects should fall into SA5 and/or SA6 scope will be further identified in study phase, coordination with SA5 and SA6 may be needed.
NOTE 4: Potential coordination with other WTs (e.g., WT#1.1 on service enablement and UE-CN interaction, WT#1.2 on QoS, exposure framework and UP aspects, etc.) is needed.
NOTE 5: Computing Site represents the computing resources in a specific location of network topology. The computing site can offer computing services by allocating its computing resources to run application workloads upon demand of a Computing Service consumer. From networking perspective, the Computing Site is located within 6G CN (via e.g. user plane function in 6G) or Data Network (either owned and controlled by the operator or 3rd party).
A.7 Work Task 7: 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 WT#7 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 WT has IWK aspects that are scoped under WT#2.
NOTE 3: This WT has dependency on mobility aspects that are scoped under WT#1.1.
NOTE 4: This WT has voice aspects that are scoped under WT#1.4.
A.8 Work Task 8: Cellular IoT enablers in 6G
Study how to support cellular IoT enablers in 6G including:
|
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 of this analysis will serve as the basis for architectural requirements to Key Issues related with other Work Tasks, this analysis needs to conclude for June 2026.
|
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, NB-IoT and non-3GPP access are not in the scope of the WT.
Annex B:
Topics for further resolution
B.X Topics for further resolution for KI#X
Editor's note: This clause will include the topics for further resolution as work progresses for the specific KI#X. Eventually this clause should only contain topics for further resolution that did not result in agreements (i.e. in agreed principle(s) in a clause 7.1.X) and can either be then marked as not pursued or postponed to a future Release.
Annex C:
Change History
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA2#170
S2-2507937
-
-
-
TR skeleton for FS_6G_ARC
0.0.0
2025-08
SA2#170
-
-
-
-
Documented approved p-CRs at S2#170: S2-2508022, S2-2508034
0.1.0
2025-10
SA2#171
-
-
-
-
Documented approved p-CRs at S2#171: S2-2509788, S2-2509821, S2-2509835
0.2.0
2025-11
SA2#172
-
-
-
-
Documented approved p-CRs at S2#172: S2-2511123, S2-2511142, S2-2511144, S2-2511180, S2-2511196, S2-2511197, S2-2511201, S2-2511212, S2-2511213, S2-2511214, S2-2511215, S2-2511217, S2-2511218, S2-2511240, S2-2511241, S2-2511244, S2-2511245, S2-2511252, S2-2511253, S2-2511254, S2-2511261, S2-2511297
0.3.0
|
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 enablers, and corresponding solutions.
The study is based on the application enablement requirements as defined in 3GPP TS 22.261 [1]. The study is dependent on 3GPP TS 23.501 [2] (5GC architecture for satellite access for NR), 3GPP TS 23.502 [3] (procedures for NR satellite access). The study would consider the impacts and enhancements to the application enablement to align with SA1 and existing SA6 service.
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system".
[3] 3GPP TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[4] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[5] 3GPP TR 23.700-01: "Study on application enablement for Satellite access enabled 5G Services”.
[6] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".
[7] 3GPP TR 23.700-82: “Study on application layer support for AI/ML services.”
[8] 3GPP TS 23.482: “Functional architecture and information flows for AIML Enablement Service”.
[9] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[10] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
|
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: Application Satellite Coverage Availability Information.
|
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 call servers in edge networks or cloud networks, retrieve the required models, and request the server to perform corresponding AIML tasks, such as perception, recognition, reasoning, and federated learning. Although TS 23.700-82 [7] has proposed a variety of ground network use cases for AIML APP, it is worth studying whether the scenario of deploying AIML models on satellites requires enhancements to existing application enablers.
Furthermore, if remote sensing data is collected via satellite and transmitted to AI models on ground networks, the data capacity and speed of transmission will be limited by the satellite's limited bandwidth. Therefore, it is possible to consider deploying AIML models directly on satellites, performing data processing, compression, and inference locally. Ultimately, the compressed remote sensing data and inference results are transmitted to users on the ground via feeder links, thereby reducing data transmission burden and latency.
|
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 AIML models for AIMLE (e.g. Light weight models stored on remote sensing satellite to process collected remote data, Model transmission and sharing between satellites and terrestrial network).
|
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 windows during which the AIML model on the satellite can establish data and signalling communications with the AIML service platform. Outside of these time windows, the AIML model on the satellite loses contact with the terrestrial network. If the time required for the onboard AIML model to collect remote sensing data exceeds the satellite-to-ground network communication window, AIML service continuity must be maintained during the extended period (e.g., 1. Waiting for the satellite to reestablish contact with the ground network and obtain the collected remote sensing data; 2. Switching to another AIML satellite providing remote sensing services and taking over the data and processing results from the original AIML satellite; 3. Maintaining data and signalling communication between the ground network and the AIML satellite via an AIMLE server-to-AIMLE server mechanism).
It is worthwhile to explore ways to ensure onboard AIML service continuity by leveraging inter-satellite handovers and predicting/managing the AIML satellite's available time windows, thereby maintaining user services even after the AIML satellite leaves the available time window. Furthermore, it is worthwhile to investigate interconnection solutions between AIMLE platforms in the ground network. By using a roaming AIMLE platform as a proxy for the original AIMLE platform, a data and signalling communication path could be established between the original AIML satellite, the roaming AIMLE platform, and the original AIMLE platform to ensure user service continuity.
|
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 available time window).
2. Whether and how to maintain and reestablish communication between UE and AIMLE layer while collecting/transmitting remote data via satellite (e.g. predict/manage available time window of satellites related to (based on) AIML data collection and transmission information).
|
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 for users, low-orbit satellites may result in incomplete data transmission before the satellite is no longer within the user's connection range. Therefore, when the low-orbit satellite-assisted enabling layer performs data transmission, it is necessary to consider how to ensure uninterrupted data transmission before the satellite leaves users’ connection range. It is worth studying the need to arrange satellite switching and application context transmission in advance before the available time window of the data transmission auxiliary satellite is exceeded.
|
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 satellite in the same orbit to support continuity of data delivery, whether and how to relocate the context between satellites (e.g. enhancement on application context relocation to support data delivery between satellites).
4.4 Key issue #4: Application enablement layer enhancement for efficient content delivery over satellite access
|
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 experience, reduce backhaul resource usage and utilize radio resource efficiently. The operation of in-network caching includes the location management of the content cache as well as the efficient delivery of content to and from the appropriate content caching applications. The location requirement includes the support of content caching applications in both the network (e.g., AN/access network and CN/core network) and the UE (e.g., terminal equipment, smartphone, etc.).
When the services are extended to accommodate the satellite access, the stage-1 spec. requires, quoted as:
A 5G system with satellite access optimize the delivery of content from a content caching application by taking advantage of satellites in supporting ubiquitous service on very large to global coverages.
This extension suggests three aspects: (1) ubiquitous coverage over a large to global scope implies the support of distributed content caching applications; (2) the distributedness necessitates the cache deployment in AN, CN, and even in UE; and (3) efficient content delivery from application servers with the consideration of satellite access characteristics.
The 3GPP SEAL spec. TS 23.434 [4] references the data delivery enabler, i.e., SEALDD, to ease the diversified data delivery demands for VAL applications. SEALDD offers not only the advanced data delivery capabilities, but also the storage capacities. The SEALDD spec. The 3GPP TS 23.433 [3] clauses 4.6 and 9.5 indicate that the SEALDD server supports the data storage and storage management for VAL client/server, SEALDD client and other SEALDD servers (via the SEALDD-E reference point). The VAL client and VAL server may coordinate to determine the usage of the SEALDD storage service. As we can project, while the content caching service may be leveraged via the storage service as provided by the SEALDD server, the normal deployment locations of SEALDD servers makes the distributedness of content caches less desirable, which posts challenge to the required ubiquitous coverage over a large to global scope for satellite access. In 3GPP TS 23.434 [4] upon describing the NRM handling the satellite S&F services, the clause 21.3.2.2 says a VAL UE may report (via the NRM client on the UE) the maximum data storage quota which indicates the maximum data storage quota per application layer on the UE for all of services. This suggests a content caching application might be deployable on a UE for better distributedness.
3GPP TS 23.434 [4] clause 21, SEAL services over satellite access, implies the satellite footprint or application satellite coverage availability information (ASCAI) can be leveraged for efficient content delivery. It describes a CM (i.e., Configuration Management) server can provide the ASCAI to consumers (e.g., VAL UE, CM client, VAL server, etc.) to guide to minimize the service impact (e.g. indicate when to trigger the UL/DL service flow if the VAL UE is accessing the satellite). The 3GPP TR 23.700-01 [5] indicates that supplying the discontinuous coverage pattern between UEs and AS/AFs to the application layer will help applications design themselves for handling discontinuity accordingly. For instance, if the intermittent connectivity pattern is predicted in advance and then exposed to the application enablement layer, then the application layer could use this information to better schedule content delivery to distributed caching applications (e.g. UEs supporting caching applications may be given precedence during a connectivity available interval, UEs with large caching demand may be better off utilizing longer connectivity interval, etc.).
|
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 content caching applications for efficient content delivery.
- Whether and how to enhance the application enablers (e.g., SEALDD, NRM, etc.) to optimize the content delivery over the satellite connectivity by leveraging the satellite access characteristics (e.g., satellite ephemeris, ASCAI or application satellite coverage availability information, QoS parameters for traffic over the satellite access, etc.).
4.5 Key issue #5: Location management service via satellite access
|
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 application server. The location management server, with the fused location function, may combine/aggregate location information from multiple sources to provide a more accurate UE location. The location management server also supports to report the value-added location information (e.g. monitoring location deviation events, history location data, periodic verify UE location, prediction related to UE location, etc.) to the VAL server.
In a network with satellite access, the Location management service works as expected when both the service link and feeder link are available, and on par with the location management service with terrestrial access. However, when either of them (service link or feeder link) is not available, the Location management service is expected to have interruption that may have direct impact on the behaviour of the application. Particularly, features such as monitoring location deviation events, history location data, periodic verify UE location does not work when such interruption happens.
|
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 issue #6: Improve service performance over satellite access utilizing AI capabilities
|
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 there is a solution which defines a new analytics for the UE RAT connectivity and utilizing the ADAE server to provide a better service experience as specified in 3GPP TS 23.436 [6].
In fact, besides the UE RAT connectivity analysis, the application enabled layer could obtain more satellite related data analysis to optimize the performance of satellite access and satellite communication with the help of AI enablers/capabilities defined in application enablement layer. For example, compared with defined ASCAI (Application Satellite Coverage Availability Information), satellite related data analysis may provide available satellite information to the target UE in a certain area, the time/predicted time at which the target UE is moved in/out of the satellite coverage, the preferred QoS/QoE when using the services over the satellite access, etc. to indicate the UE client on the application or the application server the related satellite information directly. Thus it’s necessary to study how to enhance the satellite based data analysis to improve the service performance in the application enabled layer.
|
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 provide/expose the preferred and/or predicated QoS/QoE for services over satellite access, utilizing analysis from (e.g. ADAES, ALMLE).
|
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 satellite access or to minimize the impact on services (e.g. inform the VAL server in time to pause the downlink data when the target UE is unavailable under the satellite coverage).
|
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 request
1. Consumers (e.g., the VAL server or UE) initiate a satellite communication analysis subscription request to the ADAES, with the analysis ID (i.e. the application satellite coverage availability information), analysis type (statistics or prediction), target UE ID, service ID, target service area, reporting conditions (e.g., periodic reporting or event-triggered reporting), etc.
2. The ADAES checks whether the VAL server is authorized to invoke such request.
3. If the request is authorized, the ADAES enabler sends a satellite communication analysis subscription response to the VAL server.
4a. ADAES may obtain the satellite related information for the target UE from the SEAL servers in the following ways:
- ADAES may obtain the ASCAI related to the target UE from the configuration management server as specified in clause 21.2.2.1 of 3GPP TS 23.434 [4];
- ADAES may retrieve the location information and access type of the target UE from the location management server as specified in clause 9.3.5 of 3GPP TS 23.434 [4].
4b. ADAES may obtain the satellite related information for the target UE from the 3GPP CN in the following ways:
- ADAES may obtain the location information and UE mobility analysis information for the target UE from the 3GPP CN (i.e., NWDAF) as specified in clause 6.7.2 of 3GPP TS 23.288 [9]).
5. The ADAES stores and analyses the received satellite related information based on the satellite communication analysis subscription service request received in step 1. The ADAES may generate the statistical and predicated ASCAI information for the target UE in a specific service area/time point. E.g., the available satellite information for the target UE in a certain area, the predicted time point when the target UE enters/exits the coverage of a certain satellite, or the predicted time periods during which the target UE is available under the coverage of a certain satellite.
NOTE 1: Whether the ADAES provides the predictive satellite related information depends on the prediction parameter is included in Step 1or not.
6a. The ADAES will report the ASCAI analysis (including the statistics and prediction information) to the consumer via the satellite communication analysis notification message. And the consumers may take actions to minimize the service impact if there is. For example, the VAL server may promptly adjust the downlink data polices (e.g., pending the downlink data) based on the time points when the UE is unavailable under the satellite coverage.
6b. The ADAES may generate the corresponding data polices based on the analysed satellite related information and sends these data polices to the consumer directly. These data polices below only apply when the target UE is unavailable under the satellite coverage:
- Reject forwarding the data for new uplink and downlink data;
- Pending forwarding the data and cache for new uplink and downlink data;
- Forwarding the data according to priority for existing uplink and downlink data.
NOTE 2: The priority for the forwarding polices may be set according to the service QoS/QoE, user levels, operator policies, pre-configurations, etc.
NOTE 3: It’s up to the ADAES to decide which step (6a or 6b) is performed.
|
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 or 3GPP core network, generate the ASCAI analytics (including the statistics and prediction information) and then report them to the consumers (VAL UE or VAL server).
Besides, the ADAES can generate the corresponding data polices based on the analysed satellite related information to guide the consumers how to operate the traffic data to minimize the service impacts.
|
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 over satellite access
1. Consumers (e.g., the VAL server or UE) initiate a satellite communication analysis subscription request to the ADAES, with the analysis ID (i.e. QoS for the satellite communication), analysis type (statistics or prediction), target UE ID, service ID, target service area, reporting conditions (e.g., periodic reporting or event-triggered reporting), service QoS parameters, etc.
NOTE 1: The definition of QoS can refer to the clause 5.7 of 3GPP TS 23.501 [10].
2. The ADAES checks whether the VAL server is authorized to invoke such request.
3. If the request is authorized, the ADAES enabler sends a satellite communication analysis subscription response to the VAL server.
4. ADAES may obtain the satellite communication related information for the target UE from the 3GPP CN (i.e., NWDAF, via NEF), including the location information, RAT type (i.e. satellite), UE mobility analysis information, the DN performance and QoS analysis information (such as the time delay, the traffic data flow and the uplink/downlink QoS parameters when the UE accesses via satellite access) as specified in clause 6.14 and clause 6.23 of 3GPP TS 23.288 [9]).
5. Upon receiving the satellite communication related information for the target UE from step 4, the ADAES stores and analyses these information based on the service request received in step 1 to generate the performance or service quality (i.e., QoS) statistics and prediction related to satellite access. E.g., the ADAES may provide the preferred satellite and the preferred satellite type (such as GEO, MEO, LEO) when the UE is using the satellite access to meet the requested QoS requirements, or the recommended/predicated QoS parameters for the specific service when the UE is accessing the dedicated satellite.
6. The ADAES will report the QoS analysis related to satellite communication, including preferred and prediction information (e.g. the preferred satellite and satellite type, recommended/predicated QoS parameters), to the consumer via satellite communication analysis notification message. And the consumers may take actions to minimize the service impact if there is. For example, when the target UE is accessing the GEO satellite, the VAL server may decrease the service QoS (e.g., latency), etc.
NOTE 2: The actions from the consumer to minimize the service impact are out of scope of this specification.
|
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 core network and generate the preferred or predicted QoS analysis (e.g. the preferred satellite and satellite type, recommended/predicated QoS parameters, etc.) for the requested services over the satellite access.
NOTE: Whether the procedure 5.1.1.1 of Sol#1 and the procedure 5.2.1.1 of Sol#2 can be combined or not will be discussed in normative phase.
|
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 on-board satellite (GEO, MEO, or LEO) to complement and for continuity of the location management service, especially when the feeder link is not available and S&F is supported.
In this deployment option, location management server is deployed both on ground and on-board satellite. The UE can be on the ground/sea or in the air (e.g. drone). The UPF to access on-board location management server is deployed on one or more satellites. RAN (e.g. gNB) can either be deployed on ground/sea (e.g. in a ship) and connected to satellite UPF or be deployed on regenerative satellite. The 5GS control plane functions (e.g. AMF, SMF) are deployed on the ground and/or on satellite, which is not depicted in the figure for simplicity. UPF is deployed on ground to access the location management server on the ground, and the UE can reach the location management server on ground or via space. The on-board location management server can be mobile depending on the satellite they are deployed on: GEO, MEO, or LEO.
The location management server, with the fused location function, may combine/aggregate location information from multiple sources including the location determined on-board satellite to provide a more accurate UE location. The location management server on-board satellite also assists to report the value-added location information (e.g. monitoring location deviation events, history location data, periodic verify UE location, prediction related to UE location, etc.) to the VAL server via satellite access.
|
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: Procedure for on-board satellite LMS assisted SEAL location history service
1. Location tracing configuration from VAL server to the location management server (on-ground) as described in 3GPP TS 23.434 clause 9.3.21.1.
2. The location management server (on-ground) sends a location tracing configuration request to the location management server (on-board satellite) to configure the location tracing service while the feeder link is available. The location tracing configuration request may contain the geographical area for history location tracing, events/conditions for triggering the location history report, location QoS, the identities for the UE and service, the time till when the SEAL LM needs to store the location history data and the required positioning method(s) , etc.
Editor's note: How the target satellite to configure the location tracing service is determined is FFS.
3. The location management server (on-board satellite) checks whether the location tracing configuration request is authorized and available to serve. If the request is available, the location management server (on-board satellite) stores the configuration received in step 2. If the request includes multiple UEs, the location management server creates and stores the contexts for each UE.
4. The location management server (on-board satellite) sends the location tracing configuration responses to the location management server (on-ground).
5. When the feeder link is not available, the location management server (on-board satellite) has obtained and stored the UE location data from multiple sources (e.g. UE, gNB/GMLC onboard, 3rd party), periodically based on the event triggers or conditions received in the request of step 2.
6. Once the feeder link is available, the location management server (on-board satellite) forwards the stored UE location data towards the location management server (on-ground).
NOTE: The interactions between the location management server (on-board satellite) and location management server (on-ground) are supported by LM-E reference point as described in 3GPP TS 23.434 clause 9.2.5.6.
|
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 between LMS on-ground to LMS on-board satellite to support SEAL location history service via satellite access.
Editor's note: It is FFS to evaluate further on the impact made by this solution to the use case.
|
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-board satellites to achieve the large to global range of service coverage. Low-Earth-Orbit (or LEO) satellites are utilized to reduce the transmission latency. However, thanks to the lower altitude of LEOs, and also depending on the minimum elevation angles, the coverage range of LEO on Earth is limited. This will result in the shorter connection time for on-ground users via LEO-based satellite access.
For example, assuming a LEO satellite orbits at the 500 km altitude, which makes the orbital period be roughly 95 minutes. With a reasonable choice of the minimum elevation angle (e.g., 30 degree), a specific spot on Earth could access the satellite approximately for 7 minutes once within the coverage of the satellite. Accordingly, in some scenarios, incomplete data transmission via a LEO satellite might be experienced before the satellite moves aways and no longer resides within users’ connection range. Therefore, when the LEO satellite-assisted enabling layer performs data transmission, it is necessary to consider how to ensure uninterrupted data transmission and strive for service continuity.
With SEALDD servers on-board LEO satellites, the solution enhances the SEALDD enabled data transmission service with the dynamic discovery and selection of (target) SEALDD server based on the application satellite coverage availability information (i.e., ASCAI). Once the target SEALDD server (on-board another satellite) is selected, the enhanced procedure handles the switching of serving satellites along with the context transfer of the SEALDD servers deployed on-board the satellites.
In the solution, SEALDD clients on VAL UEs are on the ground.
|
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 SEALDD servers.
Pre-condition:
- SEALDD servers are deployed on-board satellites and SEALDD clients are on the ground.
- The VAL server discovers and selects the S-SEALDD server by CAPIF functions.
- The S-SEALDD server has gotten the ASCAI by leveraging the procedures like in the TS 23.434 [4] clause 21.2.2.
- The existence and impact of the Inter-Satellite Links (or ISLs) that provide the transmission connectivity between satellites are out of the scope of the solution.
Figure 5.4.2.1.1-1: SEALDD enabled transmission with satellite selection support in data delivery
1. The VAL server sends a Sdd_RegularTransmission request to the SEALDD server#1 (S-SEALDD), as specified in 3GPP TS 23.433 [3] clause 9.2.2.2. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), and optionally, the duration of the data connection. The S-SEALDD server is selected with the consideration of ASCAI.
2. Upon receiving the request, the SEALDD server#1 performs an authorization check. If authorization is successful, the SEALDD server sends a response to the VAL server.
3. The regular data transmission connection is established according to TS 23.433 [3] clause 9.2.2.2. The S-SEALDD server transmits data received from VAL server to SEALDD client.
4. The VAL server uses the ASCAI and the duration of the data connection to determine whether the current connection can maintain the service continuity for data transmission, before the serving satellite (i.e., Sat#1 for SEALDD server#1) moves away from the VAL UE’s connection range. The current S-SEALDD server (on Sat#1) will continue the data connection if no service interruption is expected. If the duration of the data connection will lead to service interruption due to the moving away of the Sat#1, the VAL server triggers the decision process of the service continuity for the data transmission connection.
NOTE 1: When the ASCAI is utilized to discover a list of the target SEALDD servers, the VAL UE’s information (e.g., location data) may be considered for the discovery. The SEAL location management server can provide the VAL UE information.
NOTE 2: The VAL server can get the ASCAI by leveraging the procedures like in the TS 23.434 [4] clause 21.2.2.2.
5. The S-SEALDD server (SEALDD server#1) performs candidate SEALDD servers discovery by using EEL, as specified in TS 23.433 [3] clause 9.4. The discovery can utilize various discovery filter (or query filters), with the consideration of ASCAI in the query filter.
NOTE 3: The discovered candidate SEALDD servers must be on different serving satellites from the S-SEALDD server’s serving satellite (i.e., Sat#1), since SEALDD servers on-board the same satellite will have the same ASCAI that cannot address the data connection interruption issue
6. Once the available target SEALDD servers are discovered, the S-SEALDD server can select the T-SEALDD server (i.e., SEALDD server #2) based on the coverage range, the coverage duration, or local configuration.
7. The SEALDD context transfer procedure is performed between the S-SEALDD server and the T-SEALDD server, as specified in TS 23.433 [3] clause 9.6.2.1. Both SEALDD servers on-board different satellites interact via the reference point SEALDD-E to transfer data content and exchange information for SEALDD service provisioning, control, reporting etc., as specified in TS 23.433 [3] clause 7.4.5.
After the SEALDD context transfer procedure, the SEALDD client on VAL UE connects to the new T-SEALDD server (i.e., SEALDD server#2) to continue the data transmission connection.
|
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
Identity of the VAL service
Identity
O
Identifier of specific UE or VAL user
SEALDD-S connection information
M
Address information (e.g., IP address and/or port, URL) of the VAL server to receive the traffic from the SEALDD server
QoS information
O
QoS information provided by VAL server
Duration of data connection
O
The total time a data transmission connection expects to last
VAL server’s total bandwidth limit
O
(See NOTE)
The total bandwidth limit of VAL server, including UL/DL
VAL users’ bandwidth limit
O
(See NOTE)
The bandwidth limits (i.e. minimum bandwidth requirement and maximum bandwidth limit) for VAL users, including UL/DL
NOTE: These IEs are used for the SEALDD enabled bandwidth control for different VAL users.
|
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 content delivery with satellite access, while the in-network content caching service may be provided by the SEALDD server, the normal deployment locations of SEALDD servers, i.e., closer to VAL servers, will make the distributed requirement of content cache less achievable. This impacts the desired ubiquitous coverage for satellite access.
In TS 23.434 [4] upon describing the NRM handling the satellite S&F services, the clause 21.3.2.2 says a VAL UE may report (via the NRM client on the UE) the maximum data storage quota which indicates the maximum data storage quota per application layer on the UE for all of services. This suggests a content caching application might be deployable on the VAL UE for better distribution. This part of the solution proposes to enhance the architecture of the SEALDD enabler by providing the data storage capability in SEALDD client(s). The SEALDD client (in VAL UE) is deployed on-ground for satellite access.
The 3GPP TS 23.434 [4] clause 21, SEAL services over satellite access, implies the satellite footprint or application satellite coverage availability information (ASCAI) can be leveraged for efficient content delivery. For example, applications leveraging the discontinuous coverage pattern between UEs and AS/AFs can help applications design themselves for handling discontinuity accordingly. For instance, if the intermittent connectivity pattern is predicted in advance and then exposed to the application enablement layer, then the application layer could use this information to better schedule content delivery to distributed content cache in VAL UE (e.g. VAL UEs supporting content caching applications may be given precedence during a connectivity available period, UEs with large caching capacity may be better off utilizing longer connectivity interval, etc.). This part of the solution supplements the previous SEALDD layer architecture enhancement proposal by leveraging the satellite access characteristics for efficient content delivery.
|
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 transmit contents between the VAL client and VAL server for better global service coverage.
Pre-condition:
- The VAL server discovers and selects the SEALDD server by CAPIF functions.
- VAL servers, VAL clients and SEALDD servers are deployed on the ground.
Figure 5.5.2.1.1-1: SEALDD enabled data transmission for efficient content delivery via satellite services
1. The VAL server decides to use SEALDD service to enable efficient content delivery (ECD) for data transmission and allocates address/port as SEALDD-S Data transmission connection information for receiving the data packets from SEALDD server. The VAL server sends Sdd_ECDforSatAccessTransmission request to the SEALDD server discovered by CAPIF. The service request includes UE ID/address, VAL server ID, VAL service ID, SEALDD-S Data transmission connection information of the VAL server side, ECD for satellite access requirement (e.g., indication, max cache capacity, etc.).
2. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, SEALDD server allocates the SEALDD-S data transmission connection information (e.g., address/port) of the SEALDD server side to receive the application data packets from the VAL server to be delivered to the VAL UE. The SEALDD server responds with a Sdd_ECDforSatAccessTransmission response.
NOTE 1: The SEALDD-S data transmission connection information of the SEALDD server side is optional, if the SEALDD server uses the downlink pull mode to fetch the application data from the address provided by the VAL server in step 1, and uses the uplink push mode to send the application data to the address provided by VAL server.
3. If the SEALDD server receives from the VAL server the ECD for satellite access indication, the SEALDD server may invoke the SEAL NRM service to enquire the content caching capability and the data storage capacity from the VAL UE. A procedure like the TS 23.434 [4] clause 21.3.2.2 could be utilized. The NRM client on a VAL UE can report the content caching capability and maximum data storage quota per application layer on the VAL UE for all of services to the NRM server, which then sends to the SEALDD server.
NOTE 2: While the procedure in TS 23.434 [4] clause 21.3.2.2 is about VAL UE reporting information from NRM client to NRM server, the procedure for NRM server to enquire and collect the VAL UE information from the NRM client makes no significant difference.
4. If the received ECD indication shows the support of ECD in VAL UE, the SEALDD server and the SEALDD client enable the ECD for satellite access data transmission. Based on the ECD for satellite access requirement received from the VAL server or local configuration, the SEALDD server requires the SEALDD client to set up the content caching service and allocate content cache with provided content storage capacity.
NOTE 3: Whether a VAL UE can support the ECD and accordingly store received contents is subject to the regulatory requirements and operator’s policy.
5. The VAL server sends downlink application data to the SEALDD server which delivers it further to the VAL UE with the efficient content delivery or ECD.
NOTE 4: Based on implementation, the SEALDD server can calculate the available capacity of the content cache in the VAL UE and adjust the volume of the DL transmission data to the SEALDD client accordingly.
NOTE 5: The SEALDD server may receive the DL application data from the VAL server before the ECD is enabled in SEALDD client, during which the SEALDD server may store the application data locally.
6. The SEALDD server controls the efficient downlink application data delivery to the SEALDD client based on the application satellite coverage availability information (or ASCAI).
NOTE 6: The SEALDD server can leverage the procedures like in the 3GPP TS 23.434 [4] clause 21.2.2 to get the application satellite coverage availability information (or ASCAI).
7. The SEALDD server sends the DL data to the SEALDD client in VAL UE via the 3GPP network.
NOTE 7: The SEALDD enabled regular data transmission procedure in the 3GPP TS 23.433[3] clause 9.2.2.2 can be leveraged for the data transmission.
8. The SEALDD client receives the DL data and save it into the content cache. Later, the VAL UE distributes the cached contents to other VAL UEs/VAL clients based on the settings of the content cache applications.
NOTE 8: When contents are received and cached in the VAL UE, the VAL UE can distribute the contents via the refence point SEALDD-PC5. The 3GPP TS 23.433[3] clause 7.2 illustrates the architecture for SEALDD enabler service to support VAL UE-to-VAL UE communication. However, how a VAL UE/VAL client distributes the cached contents is implementation specific that is out of the scope of the document.
9. Optionally, the SEALDD server may send Sdd_ECDforSatAcessTransmission notification to the VAL server to influence the DL application data transmission from the VAL server, e.g., if the content cache at the VAL UE is near its capacity, if the VAL UE connection status changes thanks to the variation of satellite connectivity, or if the DL data transmission from the VAL server needs to be adjusted.
|
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
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
Identity
M
Identifier of specific UE or VAL user
SEALDD-S endpoint information
M
Address/port and/or URL of the VAL server to receive the application packets from the SEALDD server.
ECD requirement
O
ECD requirement for satellite access (e.g., support indication, max storage size).
DL data delivery status subscription indication
O
Indicates the VAL server expected to receive the DL delivery status notification
|
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 or failure.
SEALDD-S endpoint information
O
Address/port and/or URL of the SEALDD server to receive the packets from the VAL server for application traffic transfer
Cause
O
(see NOTE)
Indicates the reason for the failure, e.g. SEALDD policy mismatch, ECD not support.
NOTE: The IE is only present if the Result is failure.
|
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
Event ID
O
(see NOTE)
Identifies event SEALDD client connection status for DL ECD e.g., reachable, unreachable, cache near capacity.
Identity
M
Identifier of VAL UE or VAL user.
VAL service ID
O
Identity of the VAL service.
DL data delivery instructions
O
(see NOTE)
Indicates the instructions to the VAL server regarding the DL efficient data delivery
> Adjust DL data volume
O
Indicates adjusting DL data volume with suggested data volume
> Pause DL ECD
O
Indicates pausing DL ECD due to e.g., cache near capacity
> Resume DL ECD
O
Indicates enforcing DL ECD due to e.g., more capacity available
NOTE: Either Event ID IE or the DL data delivery instruction ID is present.
|
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.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
5.x Solution #x: <title>
Provide a suitable title for the solution.
5.x.1 Solution description
This clause will describe the solution. Each solution should clearly describe which of the key issues it covers and how.
5.x.2 Architecture Impacts
This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
5.x.3 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
5.x.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 | 6 Deployment scenarios
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 6.1 General
| This clause will provide a general description of the deployment scenarios.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 7 Business Relationships
| Provide a description of the involved business relationships.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 8 Overall evaluation
| This clause will provide evaluation of different solutions.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9 Conclusions
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9.1 General conclusions
| This clause will provide general conclusions for the study.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.