hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
3.1 Terms
|
For the purposes of the present document, the terms given in 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 TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
4 Performance metrics
|
Editor’s note: This section is to capture the definition of performance metrics for the evaluation, and if agreed, the targeted KPI values
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
5 Measurements
|
Editor’s note: This section is to include the definitions of measurement metrics, and measurement quantization except for the related evaluation results.
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
6 Performance evaluation
|
Editor’s note: This section is to summarize the evaluation assumptions for UAV sensing per RAN1 agreements. Details in Annex A.
Editor’s note: This section is to summarize on evaluation results for UAV sensing per RAN1 agreements. Details in Annex B.
- It includes the evaluation results based on NR waveform and DL NR reference signal
- Depending on RAN1 discussions, it can also include other results based on other waveform and reference signals
- It includes the evaluation results considering measurement quantization.
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
7 Network architecture
|
Editor’s note: This section is to capture the study outcome of network architecture. Applicability to gNB bistatic sensing may be considered as part of this network architecture without additional architecture impacts. No inter-gNB coordination will be studied.
|
4a21e104e9ac01766cb54297bc56539a
|
38.765
|
8 RAN-CN procedures and signalling
|
Editor’s note: This section is to capture the study outcome of procedures and signaling aspects between RAN and CN for gNB-based monostatic sensing.
X Conclusions
Editor’s note: TBA.
Annex <A>: Evaluation assumptions
Editor’s note: This annex is to include the agreed evaluation assumptions for UAV sensing per RAN1 agreements, which complements Clause 6.
- It includes the evaluation assumptions based on NR waveform and DL NR reference signal
- Depending on RAN1 discussions, it can also include other assumptions based on other waveforms and reference signals
Annex <B>: Evaluation results
Editor’s note: This annex is to include the detailed evaluation results for UAV sensing per RAN1 agreements, which complements Clause 6.
Annex <X>: Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-10
RAN1 #122-bis
R1-2507422
TR Skeleton
0.0.1
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
1 Scope
|
The present document covers the Radio Access Architecture and Interface aspects of the study item “Study on 6G Radio” [2].
2 Time Lines
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
2.1 Expected Output and Time scale
|
New specifications {One line per specification. Create/delete lines as needed}
Type
TS/TR number
Title
For info
at TSG#
For approval at TSG#
Remarks
External TR
38.9XX
Study on 6G Radio
TSG#115
TSG#116
This TR is led by RAN
TR editor: Kumagai, Shinya, NTT DOCOMO, shinya.kumagai.yw@nttdocomo.com
Note: The pCR(s) to this TR will be provided by RAN WGs at the end of the SI.
Internal TR
38.8XX
Study on 6G Radio RAN1 aspects
TSG#114
TSG#115
This TR is led by RAN1
TR editor: Kumagai, Shinya, NTT DOCOMO, shinya.kumagai.yw@nttdocomo.com
Internal TR
38.8XX
Study on 6G Radio RAN2 aspects
TSG#115
TSG#116
This TR is led by RAN2
TR editor: Chai, Li, China Mobile, chaili@chinamobile.com
Internal TR
38.8XX
Study on 6G Radio RAN3 aspects
TSG#115
TSG#116
This TR is led by RAN3
TR editor: Kulakov, Alexey, Vodafone, Alexey.Kulakov1@vodafone.com
Internal TR
38.8XX
Study on 6G Radio RAN4 aspects
TSG#115
TSG#116
This TR is led by RAN4
TR editor: Schumacher, Joseph, AT&T, jq304t@att.com
Editor’s note: TSG#115: March 2027, TSG#116 June 2027
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
2.2 Interim Milestone
|
TSG#112 (June/2026):
RAN3 to provide interim study results to allow TSGs to make a decision on:
• RAN-CN interface: P2P vs SBI
• RAN internal interfaces: CU-DU split, CP-UP split.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
3 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 RP-252912: “New SID: Study on 6G Radio”
[3] 3GPP TR 38.914: “Study on 6G Scenarios and Requirements”
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
4 Definitions of terms, symbols and abbreviations
| |
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
4.1 Terms
|
For the purposes of the present document, the terms given in 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 TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
4.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
4.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
5 Objectives and requirements
|
Editor’s note: The detailed objectives of the study are:
Single technology framework based on a stand-alone architecture to support the agreed existing and new services, and to satisfy the usage scenarios, requirements, deployment scenarios and design principles with acceptable performance/complexity trade-off, as determined by the RAN requirements in [RP-250810] and [TR38.914], including: [RAN1], [RAN2], [RAN3], [RAN4]
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
5.1 General Principles
|
All requirements of TR 38.914 will serve as the basis for RAN3 architecture design principles.
The 6G architecture shall allow for virtualized and/or cloud-based implementations of 6G RAN functionality. [FFS]
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
5.2 Deployment Scenarios
|
Editor’s note: This section may be used to describe the details/solutions related to deployment scenarios as per 38.914.
The 6G RAN architecture shall strive to support the deployment scenarios defined in TR 38.914.
- FFS on the implications of this requirement on 6G RAN architecture.
- FFS whether all deployment scenarios of TR 38.914 can be supported.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
5.3 Overall RAN Architecture
|
Editor’s note: The logical architecture can be captured here and should include the entire architecture including possible influence from existing and new services.
5.3.1 RAN-CN Functional Split
Editor’s note: The aim of this section is to describe functions split between RAN and CN.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
5.3.2 RAN Functions
|
Editor’s note: The aim of this section is to describe the functions supported in RAN.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6 RAN Architecture and Interfaces
|
Editor’s note: The aim of this section is to describe all aspects related to the Interfaces between RAN and CN.
6.1 RAN-CN Interface
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.1.1 General Principles
|
Editor’s note: The aim of this section is to describe general design principles and requirements for RAN-CN Interface.
The general principles for the specification of the 6G RAN-CN interface are as follows:
- the 6G RAN-CN interface supports the exchange of signalling information between the RAN and CN;
- the 6G RAN-CN interface supports control plane and user plane separation;
- the 6G RAN-CN interface supports future enhancements;
- the 6G RAN-CN interface supports all possible RAN deployment scenarios;
- the 6G RAN-CN interface supports RAN sharing between multiple operators;
- the 6G RAN-CN interface supports the operation of network slicing;
- the 6G RAN-CN interface supports enhanced service awareness in RAN;
- the 6G RAN-CN control plane interface supports reliable signalling transmission;
- the 6G RAN-CN interface is designed with a clear functional split between RAN and CN.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.1.2 RAN-CN Interface Functions
|
RAN-CN control plane interface supports following functions:
- UE context management : The functionality to manage UE context between the RAN and CN;
- Transport of NAS messages: The functionality to transfer NAS messages between the CN and UE, subject to SA2 progress;
- PDU Session Management: The functionality to manage PDU sessions and respective RAN resources, subject to SA2 progress.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.1.3 RAN-CN Interface Options
|
Editor’s note: This chapter includes description of RAN-CN interface options including protocol stacks, considering new and existing services.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.1.4 Evaluation of RAN-CN Interface Options
|
Editor’s note: This chapter includes evaluation and comparison of RAN-CN interface options described in clause 6.1.3.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.2 RAN Internal Interfaces
|
Editor’s Note: This chapter shall comprehensively address study on CU-DU and CP-UP aspects including functional split considering interim milestone TSG#112 (June/2026) to take a decision during TSG#115: March 2027
Editor’s Note: This chapter should also address the interfaces between 6G RAN nodes (equivalent to Xn).
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
6.2.1 General Principles
|
Editor’s note: The aim of this section is to describe general design principles and requirements for RAN Internal Interfaces
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
7 AI/ML for RAN
| |
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
7.1 AI/ML use cases
|
Editor’s note: Identify Use Case(s) of interest (either existing or new) with compelling trade-off between e.g., performance, complexity, etc…
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
7.2 AI/ML framework
| |
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
8 Radio access network procedures
|
Editor’s note: The intention of this section is to describe as a minimum Mobility scenarios. The section might also cover migration options if agreed by the plenary.
8.1 Mobility
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
8.1.1 Intra 6G Mobility
| |
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
8.1.2 Inter-RAT Mobility
|
Editor’s note: This section is to describe inter-RAT mobility, at least between the 6GR and NR.
|
5a00f94c01b7637733cebda7c3d76e93
|
38.760-3
|
8.1.2.1 Mobility between 6GR and 5G NR
|
X Conclusions
Editor’s note: This section is to provide interim study results to allow TSGs to make a decision during TSG#112.
X.1 RAN-CN interface
X.2 RAN internal interfaces
Annex A: Void
Editor’s note: This section is intended to capture considerations related to aspects that fall outside the scope of 3GPP specifications but may nonetheless impact the content or conclusions of this Technical Report (TR).
Annex B (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
Oct 2025
RAN3#129bis
R3-257234
0.1.1
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
1 Scope
|
The present document reports the RAN1 aspects of the study item “Study on 6G Radio” [2].
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
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 RP-251881: “New SID: Study on 6G Radio”.
[3] 3GPP TR 38.914: “Study on 6G Scenarios and Requirements”.
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
3 Definitions of terms, symbols and abbreviations
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
3.1 Terms
|
For the purposes of the present document, the terms given in 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 TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
4 Overview of 6GR air interface
|
Editor’s Note: High level design proposals/principles/target and overall design of 6G air interface
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5 Physical Layer structure for 6GR
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.1 Waveforms
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.2 Frame structure
|
Editor’s Note: Including numerology and frame structure (for all duplex types)
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.3 Channel coding
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.4 Modulations
|
Editor’s Note: joint channel coding and modulation will be captured in this Clause, if any
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.5 Initial access
|
Editor’s Note: including synchronization signal and raster, broadcast signals/channel and physical random access channel, as well as initial access procedure, random access procedures, system information and paging
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.6 Physical layer control, data scheduling and HARQ operation
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.7 MIMO operation
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.8 Duplexing
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.9 6GR spectrum utilization and aggregation
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.10 NTN
|
Editor’s Note: harmonized 6G Radio design for TN and NTN, including their integration
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
5.11 Other physical layer signals, channels and procedures
|
Editor’s Note: including mobility
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
6 Energy efficiency
| |
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
7 AI/ML for 6GR
|
Editor’s Note: including use case identification with compelling trade-off between e.g., performance, complexity, etc…, as well as AI/ML framework: Extensible AI/ML enablers based on the identified Use Case(s), including LCM procedures, Data collection, and data management
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
8 Sensing
|
Editor’s Note: including PHY functions and procedures for sensing technology (e.g., waveform. reference signals, measurement feedback, etc), as well as aspects of integration with communication services
|
50ed6698cfa682aa68e1c53b3fab0666
|
38.760-1
|
9 Performance evaluation
|
Editor’s Note: at least energy efficiency, spectrum efficiency, and coverage compared to 5G NR, as well as sensing performance
Annex <A>: Simulation scenarios and assumptions
Editor’s Note: LLS and SLS assumptions used for evaluations
Annex <B>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-10
RAN1#122bis
R1-2507813
TR Skeleton
0.0.1
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
1 Scope
|
The present document specifies the stage 3 protocol and data model for the Naf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.288 [14], 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
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.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[7] 3GPP TR 21.900: "Technical Specification Group working methods".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11] IETF RFC 9113: "HTTP/2".
[12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13] IETF RFC 9457: "Problem Details for HTTP APIs".
[14] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[15] 3GPP TS 29.552: "5G System; Network Data Analytics signalling flows; Stage 3".
[16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[18] 3GPP TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
[19] IETF RFC 9112: "HTTP/1.1".
[20] IETF RFC 9110: "HTTP Semantics".
[21] IETF RFC 9111: "HTTP Caching".
[22] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
[23] 3GPP TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
3 Definitions, symbols and abbreviations
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions 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 purpose of the present document, the terms and definitions given in clause 3 of 3GPP TS 23.288 [14] also apply, including the ones referencing other specifications.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
3.2 Symbols
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
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].
AF Application Function
AI/ML Artificial Intelligence/Machine Learning
GPSI Generic Public Subscription Identifier
NEF Network Exposure Function
NWDAF Network Data Analytics Function
REST Representational State Transfer
VFL Vertical Federated Learning
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
4 Overview
|
The Application Function Artificial Intelligence/Machine Learning (AI/ML) Services, as defined in 3GPP TS 23.288 [14], are provided by the Application Function (AF).
The following AI/ML services are specified for the AF:
Table 4.1-1: AI/ML Services provided by AF
Service Name
Description
Service Operations
Operation
Semantics
Example Consumer(s)
Naf_VFLTraining
This service is provided by an AF acting as VFL client and enables an NF service consumer to request the AF to participate in VFL model training as VFL client and train a local model.
Subscribe
Subscribe / Notify
NWDAF, NEF
Unsubscribe
Notify
Request
Request / Response
NWDAF, NEF
Naf_VFLInference
This service is provided by AF acting as VFL client and enables an NF service consumer to subscribe/unsubscribe for a VFL inference.
Subscribe
Subscribe / Notify
NWDAF
Unsubscribe
Notify
Request
Request / Response
NWDAF
Naf_Inference
This service is provided by AF acting as VFL server and enables an NF service consumer to subscribe/unsubscribe for a VFL inference.
Subscribe
Subscribe / Notify
NWDAF, NEF
Unsubscribe
Notify
Request
Request / Response
NWDAF, NEF
Naf_Training
This service is provided by AF acting as VFL server and enables an NF service consumer to subscribe/unsubscribe for a VFL training.
Subscribe
Subscribe / Notify
NWDAF, NEF
Unsubscribe
Notify
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5 Services offered by the AF
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.1 Introduction
|
The AF offers to other NFs the following services:
- Naf_VFLTraining;
- Naf_VFLInference;
- Naf_Training;
- Naf_Inference.
Table 5.1-1 summarizes the corresponding APIs defined for this specification.
Table 5.1-1: API Descriptions
Service Name
Clause
Description
OpenAPI Specification File
apiName
Annex
Naf_VFLTraining
5.2
AF VFL Training service
TS29530_Naf_VFLTraining.yaml
naf-vfl-train
A.2
Naf_VFLInference
5.3
AF VFL Inference service
TS29530_Naf_ VFLInference.yaml
naf-vflinference
A.3
Naf_Training
5.4
AF training service
TS29530_Naf_Training.yaml
naf-train
A.4
Naf_Inference
5.5
AF Inference service
TS29530_Naf_Inference.yaml
naf-inference
A.5
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2 Naf_VFLTraining Service
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1 Service Description
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1.1 Overview
|
The Naf_VFLTraining service exposed by the AF acting as VFL client and enables an NF service consumer to:
- request the creation/update of a VFL Training Subscription; and
- receive VFL Training related event(s) reporting.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1.2 Service Architecture
|
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The Network Data Analytics Exposure architecture is defined in 3GPP TS 23.288 [14]. The VFL signalling flows are defined in 3GPP TS 29.552 [15].
The Naf_VFLTraining service is part of the Naf service-based interface exhibited by the trusted Application Function (AF) or untrusted Application Function (AF).
Known consumers of the Naf_VFLTraining service are:
- Network Data Analytics Function (NWDAF) when the AF is trusted.
- Network Exposure Function (NEF) when the AF is untrusted.
Figure 5.2.1.2-1: Reference Architecture for the Naf_VFLTraining service; SBI representation
Figure 5.2.1.2-2: Reference Architecture for the Naf_VFLTraining service: reference point representation
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1.3 Network Functions
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1.3.1 Application Function (AF)
|
The Application Function (AF) acting as VFL client provides VFL training for different analytics events to NF service consumers.
The Application Function (AF) acting as VFL client allows NF service consumers to subscribe to and unsubscribe from VFL training event notifications.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.1.3.2 NF Service Consumers
|
The Network Data Analytics Function (NWDAF) and Network Exposure Function (NEF) support (un)subscription to the notification of different VFL training events.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2 Service Operations
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.1 Introduction
|
The service operations defined for the Naf_VFLTraining service are shown in table 5.2.2.1-1.
Table 5.2.2.1-1: Naf_VFLTraining Service Operations
Service Operation Name
Description
Initiated by
Naf_VFLTraining_Subscribe
This service operation enables the NF service consumer to request the creation/update of a VFL Training Subscription.
e.g., NWDAF, NEF
Naf_VFLTraining_Unsubscribe
This service operation enables the NF service consumer to request the deletion of a VFL Training Subscription.
e.g., NWDAF, NEF
Naf_VFLTraining_Notify
This service operation enables the NF service consumer to receive VFL Training related event(s) reporting.
AF
Editor's Note: The definition of the Naf_VFLTraining_Request service operation is FFS and pending stage 2 progress.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.2 Naf_VFLTraining_Subscribe
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.2.1 General
|
This service operation is used by an NF service consumer to request the creation/update of a VFL Training Subscription at the AF.
The following procedures are supported by the "Naf_VFLTraining_Subscribe" service operation:
- VFL Training Subscription Creation.
- VFL Training Subscription Update.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.2.2 VFL Training Subscription Creation
|
Figure 5.2.2.2.2-1 depicts a scenario where an NF service consumer sends a request to the AF to request the creation of a VFL Training Subscription (see also clause 6.2H of 3GPP°TS°23.288°[14]).
Figure 5.2.2.2.2-1: Procedure for VFL Training Subscription Creation
1. In order to subscribe to VFL Training, the NF service consumer shall send an HTTP POST request to the AF targeting the URI of the "VFL Training Subscriptions" collection resource, with the request body including the VflTrainingSubs data structure.
2a. Upon success, the AF shall respond with an HTTP "201 Created" status code with the response body containing a representation of the created "Individual VFL Training Subscription" resource within the VflTrainingSubs data structure, and an HTTP "Location" header field containing the URI of the created resource.
2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.1.7.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.2.3 VFL Training Subscription Update
|
Figure 5.2.2.2.3-1 depicts a scenario where an NF service consumer sends a request to the AF to request the update of an existing VFL Training Subscription (see also clause 6.2H of 3GPP°TS°23.288°[14]).
Figure 5.2.2.2.3-1: Procedure for VFL Training Subscription Update
1. In order to request the update of an existing VFL Training Subscription, the NF service consumer shall send an HTTP PUT/PATCH request to the AF, targeting the URI of the corresponding "Individual VFL Training Subscription" resource, with the request body including either:
- the updated representation of the resource within the VflTrainingSubs data structure, in case the HTTP PUT method is used; or
- the requested modifications to the resource within the VflTrainingSubsPatch data structure, in case the HTTP PATCH method is used.
2a. Upon success, the AF shall update the targeted "Individual VFL Training Subscription" resource accordingly and respond with either:
- an HTTP "200 OK" status code with the response body containing a representation of the updated "Individual VFL Training Subscription" resource within the VflTrainingSubs data structure; or
- an HTTP "204 No Content" status code.
2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP PUT/PATCH response body, as specified in clause 6.1.7.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.3 Naf_VFLTraining_Unsubscribe
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.3.1 General
|
This service operation is used by an NF service consumer to request the deletion of a VFL Training Subscription at the AF.
The following procedures are supported by the "Naf_VFLTraining_Unsubscribe" service operation:
- VFL Training Subscription Deletion.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.3.2 VFL Training Subscription Deletion
|
Figure 5.2.2.3.2-1 depicts a scenario where an NF service consumer sends a request to the AF to delete an existing VFL Training Subscription (see also clause 6.2H of 3GPP°TS°23.288°[14]).
Figure 5.2.2.3.2-1: Procedure for VFL Training Subscription Deletion
1. In order to request the deletion of an existing VFL Training Subscription, the NF service consumer shall send an HTTP DELETE request to the AF targeting the URI of the corresponding "Individual VFL Training Subscription" resource.
2a. Upon success, the AF shall respond with an HTTP "204 No Content" status code.
2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP DELETE response body, as specified in clause 6.1.7.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.4 Naf_VFLTraining_Notify
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.4.1 General
|
This service operation is used by the AF to notify a previously subscribed service consumer on:
- VFL Training report(s).
The following procedures are supported by the "Naf_VFLTraining_Notify" service operation:
- VFL Training Notification.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.2.2.4.2 VFL Training Notification
|
Figure 5.2.2.4.2-1 depicts a scenario where the AF sends a request to notify a previously subscribed service consumer on VFL Training report(s) (see also clause 6.2H of 3GPP°TS°23.288°[14]).
Figure 5.2.2.4.2-1: Procedure for VFL Training Notification
1. In order to notify a previously subscribed service consumer on VFL Training report(s), the AF shall send an HTTP POST request to the NF service consumer with the request URI set to "{notifUri}", where the "notifUri" variable is set to the value received from the NF service consumer during the creation/update of the corresponding VFL Training Subscription using the procedures defined in clauses 5.2.2.2, and the request body including the VflTrainingNotify data structure.
2a. Upon success, the NF service consumer shall respond to the AF with an HTTP "204 No Content" status code to acknowledge the reception of the notification.
2b. On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the HTTP POST response body, as specified in clause 6.1.7.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3 Naf_VFLInference Service
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1 Service Description
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1.1 Overview
|
The Naf_VFLInference service as defined in 3GPP TS 23.288 [14], is provided by the trusted Application Function (AF) or untrusted Application Function (AF) acting as VFL client.
This service allows the NF service consumers acting as VFL servers:
- to subscribe to and unsubscribe from different VFL inference events;
- to modify VFL inference subscriptions; and
- be notified about events for corresponding VFL inference subscriptions.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1.2 Service Architecture
|
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The Network Data Analytics Exposure architecture is defined in 3GPP TS 23.288 [14]. The VFL signalling flows are defined in 3GPP TS 29.552 [15].
The Naf_VFLInference service is part of the Naf service-based interface exhibited by the trusted Application Function (AF) or untrusted Application Function (AF).
Known consumers of the Naf_VFLInference service are:
- Network Data Analytics Function (NWDAF) when the AF is trusted.
- Network Exposure Function (NEF) when the AF is untrusted.
Figure 5.3.1.2-1: Reference Architecture for the Naf_VFLInference service; SBI representation
Figure 5.3.1.2-2: Reference Architecture for the Naf_VFLinference service: reference point representation
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1.3 Network Functions
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1.3.1 Network Data Analytics Function (AF)
|
The Application Function (AF), provides VFL inference for different analytics events to NF service consumers.
The Application Function (AF) allows NF service consumers to subscribe to and unsubscribe from one-time, periodic notification or notification when a VFL inference event is detected.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.1.3.2 NF Service Consumers
|
The Network Data Analytics Function (NWDAF) and Network Exposure Function (NEF) support (un)subscription to the notification of different VFL inference events.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2 Service Operations
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.1 Introduction
|
Table 5.3.2.1-1: Operations of the Naf_VFLInference service
Service operation name
Description
Initiated by
Naf_VFLInference_Subscribe
This service operation is used by an NF service consumer to request AF VFL client(s) to subscribe to VFL inference events.
NF service consumer (NWDAF,NEF)
Naf_VFLInference_Unsubscribe
This service operation is used by an NF service consumer to unsubscribe to VFL inference event notifications.
NF service consumer (NWDAF,NEF)
Naf_VFLInference_Notify
This service operation is used by the AF to notify the VFL inference results to the NF service consumer instance which has subscribed to the event report service.
AF
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.2 Naf_VFLInference_Subscribe service operation
| |
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.2.1 General
|
The Naf_VFLInference_Subscribe service operation is used by an NF service consumer to request AF VFL client(s) to subscribe or update subscription for VFL inference event notifications from the AF acting as VFL client.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.2.2 Subscription for VFL inference event notifications
|
Figure 5.3.2.2.2-1 shows a scenario where the NF service consumer sends a request to the AF to subscribe for VFL inference event notification(s) (as shown in 3GPP TS 23.288 [14]).
Figure 5.3.2.2.2-1: NF service consumer subscribes to VFL inference notifications
The NF service consumer shall invoke the Naf_VFLInference_Subscribe service operation to request AF VFL client(s) to subscribe to VFL inference event notification(s). The NF service consumer shall send an HTTP POST request with "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions" as Resource URI representing the "AF VFL Inference Subscriptions", as shown in figure 5.3.2.2.2-1, step 1, to create a subscription for an "Individual AF VFL Inference Subscription" according to the information in message body.
The VflInferSub data structure provided in the request body shall include:
- an URI where to receive the requested notifications as the "notifUri" attribute;
- a notification correlation identifier assigned by the NF service consumer for the requested notifications as "notifCorrId" attribute; and
- a description of the subscribed analytics event(s) as the "vflInferAnaSubs" attribute.
and may include:
- the VFL reporting information as the "reportingReqs" attribute; and
- the required conditions to apply VFL inference as the "vflInferReq" attribute;
Upon the reception of an HTTP POST request with: "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions" as Resource URI and VflInferSub data structure as request body, the AF shall create a new subscription and store the subscription.
If the AF created an "Individual AF VFL Inference Subscription" resource, the AF shall respond with "201 Created" with the message body containing a representation of the created subscription, as shown in figure 5.3.2.2.2-1, step 2. The AF shall include a Location HTTP header field. The Location header field shall contain the URI of the created subscription i.e. "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions/{subscriptionId}".
If the immediate reporting indication is applicable during the event subscription considering the "reportingReqs" attribute in the VflInferSub and VflInferAnaSub data structures, the AF shall include the intermediate VFL inference results of the subscribed events, if available, as the "vflInferResults" attribute in the HTTP POST response.
If any error occurs when processing the HTTP POST request, the AF shall send an HTTP error response as specified in clause 6.2.7.
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.2.3 Update subscription for event notifications
|
Figure 5.3.2.2.3-1 shows a scenario that the NF service consumer sends an HTTP PUT request to the AF to modify an existing VFL inference subscription (as shown in 3GPP TS 23.288 [14]).
Figure 5.3.2.2.3-1: Modification of VFL inference events subscription information using HTTP PUT
The NF service consumer shall invoke the Naf_VFLInference_Subscribe service operation to modify an existing VFL inference subscription. The NF service consumer shall send an HTTP PUT request with: "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions/{subscriptionId}" as Resource URI, where "{subscriptionId}" is the subscriptionId of the existing VFL inference subscription to be modified, to update an "Individual VFL Inference Subscription" according to the information in the message body. The VflInferSub data structure provided in the request body shall include the same contents as described in clause 5.3.2.2.2.
Upon receipt of an HTTP PUT request with: "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions/{subscriptionId}" as Resource URI and VflInferSub data type as request body, if the request is successfully processed and accepted, the AF shall:
- modify the concerned subscription; and
- store the subscription.
If the AF successfully processed and accepted the received HTTP PUT request, the AF shall update an "Individual VFL Inference Subscription" resource, and shall respond with:
- HTTP "204 No Content" response (as shown in figure 5.3.2.2.3-1, step 2a); or
- HTTP "200 OK" response (as shown in figure 5.3.2.2.3-1, step 2b) with a response body containing a representation of the updated subscription in the VflInferSub data type.
If the immediate reporting indication is applicable during the event subscription update considering the "reportingReqs" attribute in the VflInferSub and VflInferAnaSub data structures, the AF shall include the reports of the subscribed events, if available, as the "vflInferResults" attribute in the HTTP PUT response.
If any error occurs when processing the HTTP PUT request, the AF shall send an HTTP error response as specified in clause 6.2.7.
If the AF determines that the received HTTP PUT request needs to be redirected, the AF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4].
|
acdaeadefeb6c305deefa350bb6aac72
|
29.530
|
5.3.2.2.4 Partial update subscription for event notifications
|
Figure 5.3.2.2.4-1 shows a scenario that the NF service consumer sends an HTTP PATCH request to the AF to partial modify an existing VFL inference subscription (as shown in 3GPP TS 23.288 [14]).
Figure 5.3.2.2.4-1: Partial modification of VFL inference subscription information using HTTP PATCH
The NF service consumer shall invoke the Naf_VFLInference_Subscribe service operation to partial modify an existing VFL inference subscription. The NF service consumer shall send an HTTP PATCH request with: "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions/{subscriptionId}" as Resource URI, where "{subscriptionId}" is the subscriptionId of the existing VFL inference subscription to be modified, to update an "Individual VFL Inference Subscription" according to the information in the message body.
Upon receipt of an HTTP PATCH request with: "{apiRoot}/naf-vflinference/<apiVersion>/subscriptions/{subscriptionId}" as Resource URI and VflInferSubPatch data type as request body, if the request is successfully processed and accepted, the AF shall:
- partial modify the concerned subscription; and
- store the subscription.
If the AF successfully processed and accepted the received HTTP PATCH request, the AF shall partially update an "Individual VFL Inference Subscription" resource, and shall respond with:
- HTTP "204 No Content" response (as shown in figure 5.3.2.2.4-1, step 2a); or
- HTTP "200 OK" response (as shown in figure 5.3.2.2.4-1, step 2b) with a response body containing a representation of the updated subscription in the VflInferSub data type.
If the immediate reporting indication is applicable during the event subscription update considering the "reportingReqs" attribute within the in the VflInferSub and VflInferAnaSub data structures on the event subscription or the event subscription update, the AF shall include the reports of the subscribed events, if available, as the "vflInferResults" attribute in the HTTP PATCH response.
If any error occurs when processing the HTTP PATCH request, the AF shall send an HTTP error response as specified in clause 6.2.7.
If the AF determines that the received HTTP PATCH request needs to be redirected, the AF shall send an HTTP redirect response as specified in clause 6.10.9 of 3GPP TS 29.500 [4].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.