hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
5966a28ef4ebbf4af83a9cfb3cde5e38 | 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.
|
5966a28ef4ebbf4af83a9cfb3cde5e38 | 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.
|
5966a28ef4ebbf4af83a9cfb3cde5e38 | 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
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
Editor's note: The content of this clause is TBD, pending study progress.
A.1.2 Work Task 1.2
A.1.2.1 Network Sharing in the 6G system
Study on how to support network sharing in 6G, including the following aspects:
- How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G.
Editor's note: It is FFS whether other aspects of network sharing in 6G can be added in this clause.
A.1.2.2 Scope on Network Slicing
The scope of the network slicing work task includes:
1. Study the overall design and functionalities of the network slicing in 6G assuming the network slicing in 5GS as starting point for discussions including the following:
a. Identify and address any areas of possible improvement and simplification of network slicing.
b. Identify and address any improvements of the application traffic mapping to network slice(s)/user plane connection(s).
NOTE 1: Coordination between bullet 1b and the WT 1.2.x on Policy is expected.
2. Study impacts of the network slicing in 6G on the interworking and migration.
NOTE 2: Impacts to RAN are possible and coordination with RAN WGs is expected.
A.1.2.3 WT FWA Scope
Study support for Fixed Wireless Access in 6G:
1) Analyse issues encountered in 5G deployments to efficiently support FWA and determine requirements to be taken by other WT 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.
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
|
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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".
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 3 Definitions of terms, symbols and abbreviations
| |
b54bc2e105df66934b818307212e2783 | 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
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
b54bc2e105df66934b818307212e2783 | 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>
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 4 Key issues
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 4.1 Key Issue #1: AIML model storage and deployed on satellite
| |
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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).
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 4.2 Key Issue #2: Satellite based AIML service maintenance while losing connection with terrestrial network
| |
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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).
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 4.3 Key Issue #3: Support satellite selection in data delivery
| |
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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
|
b54bc2e105df66934b818307212e2783 | 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.).
|
b54bc2e105df66934b818307212e2783 | 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
|
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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
|
b54bc2e105df66934b818307212e2783 | 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.
|
b54bc2e105df66934b818307212e2783 | 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).
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5 Solutions
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.1 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
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.2 Solution #1: Support of application satellite coverage availability information (ASCAI) analysis
| |
b54bc2e105df66934b818307212e2783 | 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 analysis related to the application satellite coverage 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).
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.2.1.1 Procedure of Satellite related information subscription request
| Figure 5.2.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.2.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 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 analyse 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 predict 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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.2.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.2.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.2.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3 Solution #2: Support of QoS analysis for services over satellite access
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3.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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3.1.1 Procedure of QoS analysis for services over satellite access
| Figure 5.3.1.2-1 illustrates the high-level procedure of QoS analysis for services over satellite access.
Pre-condition:
- The following NFs (e.g., ADAES, SEAL) are all deployed on the ground.
- The target UE is accessing the satellite.
Figure 5.3.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 network (i.e., NWDAF), 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 analyse 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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.3.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4 Solution #3: Location management service via satellite access
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4.0 General description
| Figure 5.4.0-1, illustrates the deployment of location enabler on-board satellite for assisting location management service.
Figure 5.4.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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4.1 Solution description
| Figure 5.4.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.4.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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4.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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4.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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 5.4.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.
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.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 6 Deployment scenarios
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 6.1 General
| This clause will provide a general description of the deployment scenarios.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 7 Business Relationships
| Provide a description of the involved business relationships.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 8 Overall evaluation
| This clause will provide evaluation of different solutions.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 9 Conclusions
| |
b54bc2e105df66934b818307212e2783 | 23.700-02 | 9.1 General conclusions
| This clause will provide general conclusions for the study.
|
b54bc2e105df66934b818307212e2783 | 23.700-02 | 9.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-09
SA6#68
S6-253656
Skeleton for TR 23.700-02
0.0.0
2025-09
SA6#68
S6-253655
Key Issue on AIML model storage and deployment on satellite
0.1.0
2025-09
SA6#68
S6-253657
Key Issue on Satellite based AIML service maintenance while losing connection with terrestrial network
0.1.0
2025-09
SA6#68
S6-253660
Key Issue on Support satellite switch selection in data delivery
0.1.0
2025-09
SA6#68
S6-253722
New KI on efficient content delivery over satellite access
0.1.0
2025-09
SA6#68
S6-253732
Pseudo-CR KI on location service via satellite access
0.1.0
2025-09
SA6#68
S6-253755
New KI on improving service performance over satellite access utilizing AI capabilities
0.1.0
2025-10
SA6#69
S6-254605
New Solution on support of satellite related information utilizing AI analysis
0.2.0
2025-10
SA6#69
S6-254606
New Solution for support of QoS analysis for services over satellite access
0.2.0
2025-10
SA6#69
S6-254607
Pseudo-CR Solution for location service via satellite access
0.2.0
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 1 Scope
| The present document is a technical report which identifies potential enhancements to application enablement services by utilizing Sensing results and proposes architectural requirements, key issues, and solutions for the potential application enablement architecture enhancements.
The study takes into consideration the existing SEAL architecture specified in 3GPP TS 23.434 [2] to investigate how to support the potential enhanced application enablement services by utilizing Sensing results.
Furthermore, the study also provides recommendations for the normative work.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 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 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3] 3GPP TS 22.137, "Service requirements for Integrated Sensing and Communication; Stage 1".
[4] 3GPP TS 23.255, "Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows;".
[5] 3GPP TS 23.286, "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows; "
[6] 3GPP TR 22.837: "Feasibility Study on Integrated Sensing and Communication (Release 19)".
[7] 3GPP TR 23.700-14: "Study on Integrated Sensing and Communication (Release 20)".
[8] 3GPP TS 23.437: "Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and Spatial anchors".
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 3 Definitions of terms, symbols and abbreviations
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 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].
For the purposes of the present document, the terms given in 3GPP TS 22.137 [3] apply.
Sensing result
For the purposes of the present document, the terms given in 3GPP TS TS 23.255 [4] apply.
UAS Service Supplier (USS)
UAV
For the purposes of the present document, the terms given in 3GPP TS TS 23.286 [5] apply.
V2X service
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 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].
SEAL Service Enabler Architecture Layer for Verticals
UAE UAS Application Enabler
UAS Uncrewed Aerial System
UAV Uncrewed Aerial Vehicle
USS UAS Service Supplier
V2X Vehicle-to-Everything
VAE V2X Application Enabler
VAL Vertical Application Layer
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4 Key issues
| 4.1 Key issue #1: Application enablement architecture enhancements to support utilization and exposure of sensing results
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.1.1 Description
| 3GPP TR 22.837[6] and TS 22.137[3] specify a set of service requirements about sensing which may have potential impacts on the application enabler layer.
- Subject to operator’s policy, the 5G network shall be able to provide secure means to report sensing results to a trusted third-party requesting information about a target object when specific requested conditions are met;
- Subject to operator’s policy and regulation, the 5G system shall be able to provide secure means for a trusted third-party to receive sensing results with contextual information;
- Subject to user’s consent, regulation and operator’s policy, the 5G network may provide secure means to expose to a trusted third-party the combined sensing result derived from the joint processing of the 3GPP sensing data and non-3GPP sensing data.
- Subject to operator’s policy, the 5G network may provide secure means for the operator to expose information towards trusted third-party on whether a given sensing service is available and the estimated quality of the given service for a certain geographic area and time.
A vertical application may provide the application enabler layer with specific information defining the conditions for the situation of interest. When such conditions are met, the application enabler layer shall be able to provide the vertical application with a report together with the relevant information.
The information required to define the situation of interest may include, but is not limited to, basic parameters such as a specific geographical area, state information, or conditions (e.g., speed, distance). Furthermore, depending on the requirements of the vertical application, more detailed and complex conditional information may be specified, such as indicators of a disaster in a specific area, tracking of the movement of a target UE over a defined time period together with environmental status information around the UE, or detection of unauthorized UE entry into a specific area, etc.
Thus, in 5G wireless sensing each vertical application may specify a single sensing service requirement (e.g. object detection) or a combination of multiple requirements (e.g. detect-and-avoid, no-transmit zone enforcement), and request them to the application enabler layer. Therefore, the application enabler layer shall be able to handle these application requirements, and shall dynamically provide the necessary capabilities to fulfil sensing requirements.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.1.2 Open Issues
| Based on the above analysis, the following aspects need to be addressed in the application enabler layer:
1. Whether and how to enhance the application enablement architecture and related functions to support the mapping of sensing service requirements of vertical applications.
2. Whether and how the existing exposure mechanisms (e.g., subscription, notification, etc) defined in the SEAL architecture and functions are sufficient to meet vertical application requirements.
3. Whether and how to process the collected sensing results (e.g., sensing exposure from the core network), to generate application enabler layer enhanced sensing results, and to expose them to vertical applications.
4. Whether and how to resolve conflicts in sensing service requirements among different vertical applications or under resource limitations.
5. Whether new application enabler architecture is needed to support the above functions.
Note that applications-specific aspects (e.g., UAV, V2X, Metaverse, etc) will be covered in separate KIs.
4.2 Key issue #2: Enhance UAV service utilizing sensing results
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.2.1 Description
| 3GPP TS 22.137 [3] has specified sensing service requirements about UAVs. Such as "The 5G system shall be able to provide sensing service to detect, and/or track one or more objects (e.g., UAVs, birds) and the environment around the object(s). "
In Rel-19, the application enabler (i.e. UAE) has been developed to support UAS which specified in 3GPP TS 23.255 [4] in which communications between UAVs, monitoring of UAV location deviation and reporting of UAV events have been studied. Especially for Detect And Avoid (DAA) service, which is to detect the potential collision between UAVs, is a key service of UAS to accomplish the safe and efficient UAV management. However, the DAA service depends on the PC5 communication, and the current situation is that the PC5 communication is not large-scale commercially used in UAV industry and even some UAVs are not equipped with 3GPP UE modules (e.g. USIM).
Furthermore, according to clause 7.8 of 3GPP TS 23.255 [4], an UAE service of tracking dynamic UAVs in an application defined area relative to a host UAV is specified. For this service, the UAE layer needs to provide the dynamic information (i.e. other UAVs’ location information) to the application layer and/or the host UAV. Currently, this service is performed by invoking location management service in SEAL layer. The location management service localizes an UAV only when the UE is equipped an UE module (e.g. USIM), and it is impossible to obtain the location information of an UAV without such UE module.
In addition, it is essential to manage UAV flight in No Drone Zone. This requires that once UAVs enter No Drone Zone, the intrusion can be detected, triggering notification immediately, e.g., sending warning to the UAV controller or UTM.
In fact, sensing results can be utilized to assist in detecting UAV, tracking UAV and avoiding the collision when there is any object during UAV trajectory or when UAV is entering a No Drone Zone, especially when the UAV is without the UE module. So, it would make sense to study how to utilize related sensing results to support the DAA, UAV trajectory tracking services, UAV flight management in No Drone Zone.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.2.2 Open Issues
| Based on the above analysis, the following open issues need to be studied:
- How to enhance the UAS application enabler to support enhanced trajectory tracking for UAVs utilizing the sensing results.
- How to enhance the UAS application enabler to support enhanced DAA service/functionalities for UAVs utilizing the sensing results.
- How to enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results.
4.3 Key issue #3: Key issue on use of sensing results for spatial maps
4.3.1 Description
This KI aims to study how to use sensing results to manage object information in spatial maps. Objects in spatial maps can be stationary or mobile. As a result, tracking mobile objects within spatial maps can be more efficient with the use of sensing technology. A sensing service can be triggered to generate sensing results for an area of interest in a spatial map and the sensing results can be used to determine and identify objects within the spatial map. As an object moves, sensing results can be used to track the object and allow a spatial map server the ability to keep the spatial map current. The information obtained from sensing results for the spatial map can then be exposed to third-party consumers.
In Rel-19, the processed sensor data is stored at VAL layer (e.g., in database at VAL layer) and the SEAL SM server gets access to such database to create a spatial map via application specific way which is out of scope.
4.3.2 Open Issues
The key issue will study:
1. Whether and how the enabler layer can use sensing results for determining the presence of objects (e.g. humans, animals, and vehicles) within an area of interest in a spatial map.
2. Whether and how the enabler layer can associate a sensing result with an object within a spatial map.
3. Whether and how the enabler layer can localize objects and detect object movements within a spatial map from sensing results.
4. How the enabler layer can support SM server with creating SM.
NOTE: In Rel-20, exposure of sensing results (with or without the sensing contextual information) to support sensing services will be provided by 3GPP core network to enabler layer.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.4 Key issue #4: utilizing sensing results for HD map in V2X
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.4.1 Description
| According to application layer support for Vehicle-to-Everything (V2X) services specified in 3GPP TS 23.286 [5], the V2X application specific server can be responsible for managing HD maps and providing the HD map information to the V2X application specific client on V2X UE. As per a proximity range set by the application layer, the VAE layer support providing the dynamic information (i.e. location information) required for HD maps management to the V2X application specific server. During this procedure, VAE needs to invoke location management service to get dynamic UEs list and further obtain their location. However, in current transportation system, there are many traditional vehicles which may be not equipped with UE module, or GNSS module, so it is difficult to localize their location by location management service provided by SEAL. Moreover, the environment information around vehicle (e.g., pedestrian/animal objects) also is important for safe operation, but there is no an efficient method to obtain those information.
According to the sensing service requirement specified in 3GPP TS 22.137 [3], the 5G system shall be able to provide sensing service to detect, and/or track one or more objects and the environment around the object(s). This service could be used to enhance HD map service to provide the location information of traditional vehicles and environment information around host vehicle to improve system safety.
Hence, it would make sense to study how to utilize sensing results for HD map in V2X.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 4.4.2 Open issues
| Based on the above analysis, the following open issue need to be studied:
1. How to enhance VAE layer to provide enhanced HD map including traditional vehicles information with considering sensing results.
2. How to enhance VAE layer to provide enhanced HD map including environment information (e.g. pedestrian/animal objects, etc) with considering sensing results.
4.x Key issue #x: <Title>
4.x.1 Description
This clause provides a description of the key issue.
4.x.2 Open Issue
This clause provides the open issue(s) of the key issue.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 5 Architectural Requirements and Assumptions
| This clause provides the architectural requirements and assumptions.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6 Solutions
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.1 Mapping of solutions to key issues
| Table 6.1-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
Sol #1
x
Sol #2
x
Sol #3
x
Sol #4
x
Sol #5
x
Sol #6
x
Sol #7
x
Sol #8
x
Sol #9
x
Sol #10
x
Sol #11
x
Sol #...
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2 Solution #1: Functional Architecture to Support Sensing Application Relevant Services
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1 Solution Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.0 General
| There are some common requirements from difference sensing application relevant services, for example, sensing data/result collection, sensing result aggregation, sensing result exposure. Enhancements to the application enablement layer architecture are needed to introduce common functionalities to fulfil these comment requirements.
The following clauses specify generic functional model of SEAL Sensing Enabler for support application relevant sensing services.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.1 Functional Model
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.1.1 General
| The functional architecture enhancement for the SEAL Sensing Enabler is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe an architecture enhancement which addresses the support for sensing aspects for vertical applications.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.1.2 Network Functional Model
|
Figure 6.2.1.1.2-1: Network functional model
Figure 6.2.1.1.2-1 illustrates the network functional model with SEAL Sensing Enabler. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. The SEAL functional entity with sensing enabler function on the server is grouped into SEAL Sensing Enabler server. The SEAL Sensing Enabler server consists of a common set of services and reference points. The SEAL Sensing Enabler server offers its services to the vertical application layer (VAL), VAE/UAE, and other SEAL servers.
NOTE: In this release, the SEAL sensing client is not used for sensing data collection.
Editor’s Note: Whether the SEAL sensing client is needed and the usage of it are FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.2 Functional Entities Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.2.1 General
| The SEAL Sensing Enabler functional entities with sensing application relevant service functions are described in the following subclauses.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.2.2 SEAL Sensing Enabler client
| The SEAL Sensing Enabler client interacts with the SEAL Sensing Enabler server.
NOTE: In this release, the SEAL sensing client is not used for sensing data collection.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.2.3 SEAL Sensing Enabler server
| The SEAL Sensing Enabler server functional entity provides for sensing application relevant services supported within the vertical application layer.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.3 Reference Points Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.1.3.1 General
| The reference points for the functional model for sensing application relevant service are described in the following subclauses.
Editor’s Note: The description of reference points is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.2.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.3 Solution #2: Support the sensing results exposure based on the sensing subscription request
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.3.1 Solution description
| This solution aims to address the issues identified in Key Issue 1 and provides a possible procedure to perform the sensing results exposure.
Editor's note: This solution is built on functional architecture described in solution X for key issue 1. The sensing capabilities in the enabler layer may be provided by a separate SEAL sensing server or directly by the specific SEAL/VAL enabler server. The decision on whether a separate SEAL sensing server is needed will be based on the evaluation of the solutions and FFS.
In this solution, after acquiring the sensing requirements from the sensing service consumer, a Sensing enabler server will send sensing request to a 5GC NF(e.g.,NEF). After it receives the sensing results from the 5GC NF, it determines whether the sensing requirements (e.g. the required accuracy of sensing result) are met, if not, it may further select other sensing service supplier(s) to acquire more sensing results, then it may generate enhanced sensing results based on the received sensing results from the 5GC NF and other sensing service supplier(s) and expose them to the sensing service consumer.
In this solution, the sensing service supplier which can provide sensing results can be another 5GC NF or vertical application server.
Editor's note: Whether the sensing service supplier can be 3rd party AF is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.3.2 Procedures
| The high-level procedure of sensing service exposure is shown in Figure 6.3.2-1.
Pre-conditions:
1. The Sensing enabler server has acquired sensing capability information of one or more Sensing Service Supplier(s).
Figure 6.3.2-1: Sensing service exposure procedure
1. The VAL Server/Client acting as sensing consumer performs sensing service subscription procedure by sending sensing service subscription request and receiving sensing service subscription response. During the sensing service subscription procedure, the Sensing enabler server can acquire the sensing requirements of the VAL Server/Client such as Sensing Service Area of interest, Sensing target object type, Accuracy requirements, QoS requirements and so on.
2. Sensing enabler server sends sensing request to 5GC NF(e.g.,NEF) and receives sensing response.
Editor's note: The parameters in the sensing request and response are FFS and should be determined based on SA2’s progress.
3. Sensing enabler server receives sensing results from 5GC NF(e.g.,NEF) and determine whether the sensing requirements are met.
4. If the sensing requirements are met, skip to step 8, if not, the Sensing enabler server selects other Sensing Service Supplier(s) according to the sensing capability information of Sensing Service Supplier(s) and sensing requirement as received in step1 (e.g. by matching sensing capability information of Sensing Service Supplier to the sensing subscription parameters received from the sensing consumer).
5. The Sensing enabler server sends sensing request to each selected Sensing Service Supplier and receives sensing response. Different Sensing Service Supplier may be given different sensing request parameters.
Editor's note: The parameters in the sensing request and response are FFS.
6. Each Sensing Service Supplier sends sensing results to the Sensing enabler server based on the sensing request parameters respectively.
7. The Sensing enabler server further generate enhanced sensing results(e.g.,with higher accuracy) based on the received sensing results from the 5GC NF and other Sensing Service Supplier(s).
8. The Sensing enabler server sends the (enhanced) sensing results to the VAL Server/Client.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.3.3 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.4 Solution #3: Support of exposure of sensing results
| This solution addresses the KI#1.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.4.1 Procedure of exposure of sensing results
| This solution proposes a new enabler (i.e., Sensing Enabler Server) to support the exposure of sensing results to the consumers (e.g., VAL server). The Sensing Enabler server may interact with other SEAL enabler to get the value-added sensing results.
Figure 6.4.1-1 illustrates the high-level procedure of exposure of sensing results.
Figure 6.4.1-1: Procedure of exposure of sensing results
1. The VAL server sends a sensing service request to the Sensing Enabler server, including the service type (e.g., UAV detection, dynamic HD map, Vehicle tracking, etc.), service ID, sensing target object information (e.g., UAV ID, UE ID, Vehicle ID), sensing service requirements for the target object (e.g., the target area, sensing accuracy, sensing resolution, max sensing service latency, etc.), the reporting conditions (e.g., periodic reporting or event-triggered reporting), the time duration for the sensing, etc.
2. The Sensing Enabler server checks whether the VAL server is authorized to invoke such request, may be based on e.g. the pre-configurations or operator policies.
3. If the request is authorized, the SM server may invoke the sensing related service request to the 3GPP CN and obtain the sensing results from the 3GPP CN.
Editor’s note: The exposure of sensing results from 3GPP CN depends on SA2’s progress. What will be exposed to the consumers is FFS.
4. The Sensing Enabler server may interact with other SEAL enablers (e.g., SEALDD, ADAES) to get more sensing results (e.g., the transmission latency, sensing accuracy analysis) utilizing the obtained sensing results from the 3GPP CN, in case the 3GPP core network will not provide.
- The Sensing Enabler server may interact with ADAES to get the e.g., sensing accuracy analysis and the prediction analysis for the target object utilizing the obtained sensing results from the 3GPP CN;
- The Sensing Enabler server may interact with SEALDD to get the e.g., the transmission latency for the target object utilizing the obtained sensing results from the 3GPP CN.
Editor’s note: How the ADAES and SEALDD support the sensing related functionalities are FFS.
5. The Sensing Enabler may analyse and aggregate the sensing results obtained in step 3 and step 4 to generate the value-added sensing results (e.g. the statistic results in a location/time/direction/height granularity), and then expose to the VAL server if the results can fulfil the requested sensing service requirements.
6. The Sensing Enabler sends the value-added sensing results to the VAL server via sensing service response message, including all of target objects and the value-added sensing information.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.4.2 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.5 Solution #4: Enhancements of UAV services utilizing the sensing results
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.5.1 Solution description
| This solution addresses the KI#2.
The following high-level solution principles apply to this solution:
- A high-level procedure for sensing request and exposure is proposed with a new Sensing enabler in the application enablement layer.
- The solution assumes the 3GPP core network will expose the sensing results related to UAVs to the AF (e.g., VAL server).
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.5.1.1 Procedure of detecting UAVs utilizing sensing results
| Figure 6.5.1.1-1 illustrates the high-level procedure of detecting UAVs utilizing sensing results.
Pre-condition:
- The following Sensing enabler is a new enabler that implements the sensing functions in the application enablement layer.
Figure 6.5.1.1-1: Procedure of detecting UAVs utilizing sensing results
2. The VAL server sends a UAV detect request to the UAE to detect the UAVs in a certain area, including the service type (i.e., UAV detection, invalid UAV detection ), service ID, sensing service requirements for the detected UAVs (e.g., location accuracy, velocity, latency, sensing resolution, etc.), the target area, the reporting conditions (e.g., periodic reporting or event-triggered reporting), the reporting time intervals if the request is periodic, time duration, optional tracked object information (e.g., UAV ID, flight trajectory) if the object needs to be tracked, etc.
3. The UAE checks whether the VAL server is authorized to invoke such request based on e.g. the pre-configurations or the operator policies.
4. If the request is authorized, the UAE sends the UAV related sensing results request to the sensing enabler to ask for the UAV related sensing results.
4. The sensing enabler may invoke the sensing related service request to the 3GPP CN and obtain the sensing results from the 3GPP CN via NEF if the SM server is an untrusted AF or interact with the SF entity in 5GC directly as a trusted AF.
Editor’s note: The exposure of sensing results from 3GPP CN depends on SA2’s progress. What will be exposed to the consumers is FFS.
5. Upon received the exposure from network layer, the sensing enabler may determine the detected UAVs that entering the target area and then the sensing enabler may interact with LMS to track the detected UAVs and obtain the location trajectory (including the velocity, direction, altitude, etc.) for them in the requested time duration.
Editor’s note: How the LMS tracks the detected UAVs that without UE modules is FFS.
6. The sensing enabler aggregates and combines the sensing results obtained in step 4 and step 5 to determine all of UAVs entering the target area as well as their flight trajectories, and then the sensing enabler compares the detected UAV flight trajectory with requested flight trajectory included in Step 1 to identify if the UAVs entering the target area are invalid or not.
7. The sensing enabler notifies the UAE for the UAV related sensing results, including all UAVs entering the target area and the invalid UAVs that not allowed entering the target area.
8. The UAE sends the analysed sensing results to the VAL server via UAV detect response message, including all UAVs entering the target area and the invalid UAVs that not allowed entering the target area.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.5.2 Architecture Impacts
| This solution proposes a new sensing enabler to support the sensing service.
For the new architecture for the sensing enabler, pls check the solution for the KI#1.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.5.3 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6 Solution #5: sensing based tracking dynamic UAVs
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6.1 Solution description
| This solution intends to solve the first open issue of key issue #2. This solution is to enhance tracking dynamice UAV service by utilizing sensing results.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6.2 Procedures
| This feature utilizes the following procedures:
- Step 1: UAS Application Specific Server or the host UAV subscription for host UAV’s dynamic information with UAE server.
- Step 2: UAE server tracking host UAV’s UE location with support from SEAL’s location management server.
- Step 3: UAE server management of dynamic area for sensing
- Step 4: UAE server obtaining dynamic information from sensing results
- Step 5: UAE server notification of host UAV’s dynamic information to the UAS Application Specific Server and/or to the host UAV.
Note: Step 1 and Step 2 are same to the exisiting procedures defined in clause 7.8.2.1 in 3GPP TS 23.255 [4]. Step 5 is enhanced to inclucde UVA dynamic information obtained by sensing results based on the procedure in 7.8.2.4 in 3GPP TS 23.255 [4].
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6.2.1 Subscription for host UAV dynamic information
| This procedure intends to obtain the host UAV dynamice information, the procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] is reused.
6.6.2.2 UAE server management of dynamice area for sensing
Figure 6.6.2.2-1 describes the procedure for management of dynamic area for sensing.
Pre-condition:
- UAE server 1 has received an updated location of the host UAV as per procedure specified in 3GPP TS 23.434 [5].
Figure 6.6.2.2-1: Management of dynamic area for sensing
1. Dynamice area for sensing creation/update is triggered (e.g. notified of the UE location of host UAV or notified a location update) via the step 4 in clause 7.8.2.1 in 3GPP TS 23.255 [4] for the UAV ID of the host UAV.
2. UAE server 1 determines the dynamice area for sensing based on the location of host UAV and the proximity range defined by application by its implementation.
6.6.2.3 UAE server obtaining dynamic information from sensing results
Figure 6.6.2.3-1 describes the procedure of obtaining dynamice information from sensing results.
Pre-condition:
- UAE server 1 is configured with NEF information of their supported region of operation.
Figure 6.6.2.3-1: Obtaining dynamic information from sensing results
1. The UAE server 1 determines the NEF(s) operating in the dynamice area for sensing.
2. The UAE server 1 request and obtain sensing results from 5GC.
3. The UAE server 1 obtain dynamic information of UAVs by considering all sensing results from 5GC.
Editor Note: the detail of how to request and obtain sensing results from 5GC depends on SA2.
6.6.2.4 Notification of host UAV dynamic information
Pre-conditions:
- UAS Application Specific Server has performed subscription as per procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] with UAE server 1.
- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3 in 3GPP TS 23.255 [4].
Figure 6.6.2.4: Notification for host UAV dynamic information
1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UAS Application Specific Server and/or to the subscribed UAE client of the host UAV). The UAE server can aggregate the dynamic information obtained by sensing and other methods. The notification includes the aggregated information of all the objects in the application defined proximity range of the host UAV and the location of the host UAV.
2. The UAS Application Specific Server or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client.
Editor note: How to define objects in the notification message is FFS. It may be associated to an UAV identity or not.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6.2.3 UAE server obtaining dynamic information from sensing results
| Figure 6.6.2.3-1 describes the procedure of obtaining dynamic information from sensing results.
Pre-condition:
- UAE server 1 is configured with NEF information of their supported region of operation.
Figure 6.6.2.3-1: Obtaining dynamic information from sensing results
1. The UAE server 1 determines the NEF(s) operating in the dynamic area for sensing.
2. The UAE server 1 request and obtain sensing results from 5GC.
3. The UAE server 1 obtain dynamic information of UAVs by considering all sensing results from 5GC.
Editor's Note: the detail of how to request and obtain sensing results from 5GC depends on SA2.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.