hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.3.1 Following Entities and functionalities are defined based on Solution #14.4
| The 6G GMLC supports the following functions:
- Support Le interface to LCS Client.
- Support privacy check.
- Obtain serving CRF information of target UE from UDM+.
- Get cell ID and TAI of Target UE from the 6G mobility management function when location request is received.
NOTE 1: The 6G mobility management fun... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.3.2 Following Entities and functionalities are defined based on second Solution of #14.5
| - The solution reuses the services provided by the solutions from other key issues, e.g. KI#1, KI#7.
- 6G LMF and 6G GMLC would be used for location service support.
- 6G network exposure function would be used for location service exposure based on conclusion of KI#7.
- The interfaces defined in TS 23.273 [13] for ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.4 Open issues
| Two solutions in this alternative propose different way to avoid AMF between 6G LMF and 6G-RAN/UE.
- Solution of #14.5 proposes to use user plane as only option to send data between 6G LMF and UE, additionally proposes new NLs interface between 6G RAN and 6G LMF to transfer data between those entities.
- Solution of... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15 Solutions to KI#15
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1 Solution variant #15.1: Support for SMS services via 6GS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.0 Topics addressed and High-level Solution Principles
| This solution addresses the following aspects of KI#15:
- 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].
The principles of the solution are as follows:
- 5G Architecture to support SMS over NAS described in TS 23.501 [... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.1.1 SMS over NAS
| Following functionality is required for supporting SMS over NAS in 6G System:
- Support for SMS over NAS transport between UE and AMF (or equivalent for CN for 6G).
- Support for AMF (or equivalent for CN for 6G) determining the SMSF (or equivalent for CN for 6G) for a given UE.
- Support for subscription checking ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.1.2 SMS over IP
| The IP‑SM‑GW acts as an SIP-AS in the IMS domain to provide the protocol interworking for the delivery of the short message between the UE and the Service Centre. All functionalities and interfaces of IP‑SM‑GW are defined in TS 23.204 [16].
NOTE: Adaptations required in IMS to support 6GR and CN for 6G will be studied... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.1.3 Domain selection for UE originating SMS
| To allow for appropriate domain selection for SMS delivery, it should be possible to provision UEs with the following HPLMN operator preferences on how an IMS enabled UE is supposed to handle SMS services:
- SMS is not to be invoked over IP networks: the UE does not attempt to deliver SMS over IP networks. The UE atte... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.1.4 Secure SMS
| SA1 identified security requirements for 6G SMS Services in TR 22.870 [11] clause 5.7.3, including operator-supported sender verification and SMS integrity protection.
NOTE: Coordination with SA3 and CT1 is required to identify the potential impacts to 6G architecture in supporting SMS service with enhanced security ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.2 Procedures
| The procedures for SMS over NAS described in TS 23.502 [3] are reused for 6G SMS over NAS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.15.1.3 Services, Entities and Interfaces
| Existing UE and SMSF (or equivalent for CN for 6G) described in TS 23.501 [2] apply.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.16 Solutions to KI#16
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.17 Solutions to KI#17
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.18 Solutions to KI#18
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19 Solutions to KI#19
| 6.19.0 Mapping of Solution variants to KI#19 bullets
Table 6.19-1: Mapping of Solution variants to KI#19 bullets
Key Issues # 19
Solutions
Bullet#1
Bullet#2
Bullet#3
Bullet#4
Bullet#5
#19.1
X
X
#19.2
X
X
#19.3
X
#19.4
X
#19.5
X
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.0 Mapping of Solution variants to KI#19 bullets
| Table 6.19-1: Mapping of Solution variants to KI#19 bullets
Key Issues # 19
Solutions
Bullet#1
Bullet#2
Bullet#3
Bullet#4
Bullet#5
#19.1
X
X
#19.2
X
X
#19.3
X
#19.4
X
#19.5
X
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1 Solution variant #19.1: 6G CN support the UE AI agent registration, discovery and communication
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.0 Topics addressed and High-level Solution Principles
| This solution variant addresses KI#19, bullet 1 and bullet 2.
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 auth... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2 Solution variant #19.2: UE AI agent registration, discovery and communication within application layer of the operator control domain
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.0 Topics addressed and High-level Solution Principles
| This solution variant addresses KI#19, bullet 1 and bullet 2.
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 auth... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3 Solution variant #19.3: Network Capability Exposure Functionalities to AI agent on AF(s)
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.0 Topics addressed and High-level Solution Principles
| This solution variant focuses on KI#19: 6G Network for AI, and the topic addressed is the following:
3. Study whether and how to enhance network capability exposure functionalities to AI agent on AF(s).
The following are high-level solution principles captured by this solution variant based on the proposals in Soluti... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4 Solution variant #19.4: 6G CN can provide AI services (i.e. AI inferencing and AI training) to applications (AF or in UE)
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.0 Topics addressed and High-level Solution Principles
| This solution variant addresses Bullet#4 of KI#19:
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).
Based on the submitted solutions, the following architectural and high-level principles are extracted to enable the 6G CN to provide netwo... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.5 Solution variant #19.5: 6G System impacts based on the characteristics of AI traffic
| Editor's note: Which working groups will determine the characteristics of AI traffic is subject to TSG SA plenary decision.
Editor's note: This clause will be filled out once characteristics of AI traffic are clarified.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.20 Solutions to KI#20
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.21 Solutions to KI#21
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.22 Solutions to KI#22
| 6.22.0 Solution Category Overview
The solutions for KI#22 are structured as following in Table 6.22.0-1:
Table 6.22.0-1: Solution Category overview
Solution Groups
Addressed bullet #
Solution category for the group
Variants for each category
Referred input paper in Annex C.22
Solution # in TR
1. Architecture ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.22.0 Solution Category Overview
| The solutions for KI#22 are structured as following in Table 6.22.0-1:
Table 6.22.0-1: Solution Category overview
Solution Groups
Addressed bullet #
Solution category for the group
Variants for each category
Referred input paper in Annex C, clause .22
Solution # in TR
1. Architecture Requirements,
1a, 1b
(1)... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.23 Solutions to KI#23
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24 Solutions to KI#24
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1 Solution variant #24.1: Features applicable for 6G IoT solution.
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1.0 Topics addressed and High-level Solution Principles
| This solution addresses KI#24 and specifically provides a list of 5GS IoT features that should be further studied and possible enhanced to support 6G IoT.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1.1 Description
| The 5GS CIoT features can be treated as the start point for the 6G IoT study.
Features driven by this key issue are expected to be generic and may apply to any UEs in 6G.
Based on clause 5.31 "Support for cellular IoT" in TS 23.501 [2], this solution has the following analysis and observations.
Following features a... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.24.1.4 Issues
| The following features need more discussion before agreeing on the applicability for 6G IoT.
- 5.31.6 Reliable Data Service
- 5.31.14 Support of rate control of user data
- 5.31.15 Control Plane Data Transfer Congestion Control
- 5.31.16 Service Gap Control- Reduced Capability signalling.
6.X Solutions to KI#X... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 7 Interim agreements
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 7.1 Agreed Principles
| 7.1.Y Agreed Principles for KI#Y
Editor's note: This clause will include the principles that are agreed as work progresses for the specific KI#Y. This may be populated directly or e.g. also when a topic in Annex B gets resolved and a principle is agreed.
Where there is consensus, interim agreements (e.g. solution pr... |
fcf00dbf2301bc1e78448d06d0e070aa | 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.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 9 Conclusions
| Editor's note: This clause will capture conclusions for the study.
By consensus interim agreements can become part of the final conclusions of the study.
Annex A:
Work Tasks
A.0 Introduction
Editor's note: This Annex will capture updates to WT scope based on the 6G SID in SP-250806. The plan is to update the St... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 1.1 Determine how to fulfil requests from the UEs or AFs when intent is included and, in order to ensure interoperability of intents and supporting system test cases, determine the constraints on the use and expression of intents sent from the UEs and the AFs so that the intents can be processed and interpreted unambig... | |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 1.2 Determine how to fulfil requests when intent is not included.
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 1.3 In order to enable AI capable entities in 6G CN to dynamically compose parts of procedures to fulfil requests from UEs and AFs, determine the design principles and constraints for the modularisation of the procedures for the 6G CN that will be applicable to the system procedures defined in the normative work. How t... | NOTE 2: An intent refers to expectations including requirements, goals, conditions, guidelines, and constraints, without specifying how to achieve them. What intent means and how to specify intents in SA WG2 specifications will be determined by the study. Intent is to be specified as a result of this work task.
NOTE 3... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.5.1 Solution variant #5.1: QoS flow considerations for 6G – Variant 1
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.5.5 Solution variant #5.5: Supporting dynamic QoS requirement by using multiple QoS flows
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.5.7 Solution variant #5.7: Enhanced QoS collaboration based on enhanced control plane signalling functionality
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3 Solution variant #12.3: Compatibility with existing deployed IMS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.1.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.2.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.3.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.19.4.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 7.1 Agreed Principles
| 7.1.Y Agreed Principles for KI#Y
Editor's note: This clause will include the principles that are agreed as work progresses for the specific KI#Y. This may be populated directly or e.g. also when a topic in Annex B gets resolved and a principle is agreed.
Where there is consensus, interim agreements (e.g. solution pr... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 1 Scope
| The present document is a technical report capturing the study on enhancement to application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3 Definitions of terms, symbols and abbreviations
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
ASCAI: Applicat... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4 Key issues
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1 Key Issue #1: AIML model storage and deployed on satellite
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1.1 Description
| In 3GPP's TS 23.482 [8], SA6 defines the architecture of AIML enabling services and related AIML business processes. Existing AIML-enabled services provide different users or third-party entities with services for searching, storing, and calling AIML models by providing a platform. Based on the SA6 process, users can c... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.1.2 Open Issues
| This key issue will study:
1. Investigate different deployment options for AIMLAPP when AIML models are deployed on satellite and study whether/how to deploy AIMLE on satellite (e.g. ML repository/ADAES on satellite to perform data processing/interference based on collected remote data).
2. Whether/how to storage AIM... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2 Key Issue #2: Satellite based AIML service maintenance while losing connection with terrestrial network
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2.1 Description
| The relative positions of satellites (such as low-orbit and medium-orbit satellites) other than geosynchronous Earth orbit (GEO) satellites to the AIML service platform on the terrestrial network are constantly changing. Considering the scenario where AIML models are deployed on satellites, there are specific time wind... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.2.2 Open Issues
| This key issue will study:
1. Whether and how to support satellite based AIML service management when losing connection with terrestrial network (e.g. When a satellite is supporting AIML service connection or related data collection, the satellite keeps connection with terrestrial network due to exceeding the availabl... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3 Key Issue #3: Support satellite selection in data delivery
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3.1 Description
| When operators deploy some components of the SEALDD architecture on satellites to ensure reliable data transmission via satellite communications, the following scenario may occur: to reduce latency, users initially select low-orbit satellites for satellite data transmission. However, due to the shorter connection time ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.3.2 Open Issues
| This key issue will study:
1. When a satellite is handling received message request, whether and how to select proper satellites in the same orbit for data delivery (e.g. selection between satellites to ensure continuity of data transmission to terrestrial network).
2. When data delivery handling is moved to another... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.4.1 Description
| The 3GPP stage-1 spec. TS 22.261 [2] provides the service requirements for the support of efficient content delivery. Emphasizing the video-based services and personal data storage applications, it brings up that the in-network content caching can be provided by an operator, a third-party or both, to improve user exper... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.4.2 Open Issues
| This Key issue is proposed to study the enhancement of the application enablement architecture for the support of efficient content delivery over the satellite access:
- Whether and how to enhance the application enablement architecture layer and/or application enabler (e.g., SEALDD) to support the deployment of conte... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.5.1 Description
| 3GPP TS 23.434 [4] describes Location Management service that offers the location management related capabilities to one or more vertical applications. The location management server is a functional entity that receives and stores user location information and provides user location information to the vertical applicat... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.5.2 Open issues
| To support the location management service with satellite service, the following aspects need to be studied:
- How to support history location data, monitoring location deviation events, periodic verify UE location when the UE is connected via satellite access, during the loss of service link or feeder link?
4.6 Key ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.6.1 Description
| In Rel-19, the normative work on application enablement for satellite enabled 5G services has been specified which including usage of satellite access characteristics for the application enablement, edge computing on satellite, satellite access with discontinuous coverage, impact on MC service and so on. Especially the... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 4.6.2 Open Issues
| Based on the above analysis, the following open issues need to be studied:
- Whether and how to provide/expose the preferred and/or predicated satellite related information (e.g. satellite/time/area) to the consumers when using the satellite, utilizing the analysis from (e.g. ADAES, ALMLE).
- Whether and how to provi... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5 Solutions
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.0 Mapping of solutions to key issues
| Table 8.1-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI#5
KI#6
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1 Solution #1: Support of application satellite coverage availability information (ASCAI) analysis
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.1 Solution description
| This solution addresses the KI#6.
The VAL server or the UE may act as consumers to subscribe the analysis related to the application satellite coverage availability information (ASCAI) from ADAES. They may ask to analyse the application satellite coverage availability information of the target UE to assist the UE's s... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.1.1 Procedure of Satellite related information subscription request
| Figure 5.1.1.1-1 illustrates the high-level procedure of Satellite related information subscription request.
Pre-condition:
- The following NFs in the application enablement layer (e.g., ADAES, CMS, and LMS) are all deployed on the ground.
Figure 5.1.1.1-1: Procedure of Satellite related information subscription ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.