hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 1 Scope
| The present document is intended to capture the output of study item for "Study on Integrated Sensing And Communication (ISAC) for NR" [2]. CP-OFDM is considered as baseline waveform. The purpose of this TR is to document the following investigations for NR ISAC.
- Performance evaluation of gNB-based mono-static sens... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 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.
-... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 3 Definitions of terms, symbols and abbreviations
| |
a42d942a68c46b17b4d16e1f71329da3 | 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.
|
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a42d942a68c46b17b4d16e1f71329da3 | 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].
CPI Coherent Processing Interval
STX Sensing Transmitter
SRX Sensing Rec... |
a42d942a68c46b17b4d16e1f71329da3 | 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
|
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 4.1 Definitions of performance metrics
| In the evaluation of NR ISAC, the following performance metrics are considered:
- Horizontal/vertical positioning accuracy is defined as the absolute value of the difference between the estimated horizontal/vertical position and the corresponding true position of a sensing target.
NOTE: There should be only one est... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 4.2 Performance objectives
| The following performance objectives are adopted for the evaluation of UAV use case with gNB-based monostatic sensing.
Table 4.2-1: Performance objectives
Performance metrics
Values
Missed detection Probability
5%
False Alarm Probability Type 1
5%
False Alarm Probability Type 2
5%
Horizontal Positioning Accur... |
a42d942a68c46b17b4d16e1f71329da3 | 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.
From physical layer perspective, the following measurements that may be reported from RAN are identified in the study of NR ISAC.
- Level A: Raw data per Tx anten... |
a42d942a68c46b17b4d16e1f71329da3 | 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 ... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 6.1 Evaluation methodologies
| The following general procedure for performance evaluation of NR ISAC is provided.
1) Simulation parameter configuration
2) Sensing scenario generation, including the deployment of sensing Tx/Rx (STXs/SRXs)
3) Dropping N target(s), where N is equal to 0 or larger than 0
4) Channel generation and STX/SRX determina... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 6.2 Evaluation Assumptions
| The evaluation assumptions for the evaluation of UAV use case with gNB-based monostatic sensing are provided in Annex A. In order to define the sensing resource ratio used in the evaluation of NR ISAC, three kinds of resources are defined
- Type_1: Resources that are used for sensing signal transmission
- Type_2: Par... |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 6.3 Performance evaluation results
| |
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 6.3.1 Baseline configuration 1
| [Editor’s note] this section is to capture observations on results for baseline configuration 1
|
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 6.3.2 Baseline configuration 2
| [Editor’s note] this section is to capture observations on results for baseline configuration 2
6.3.3 [Configuration x]
[Editor’s note] this section is to capture observations on results for other configurations if agreed. This section may be split to one or more sections.
|
a42d942a68c46b17b4d16e1f71329da3 | 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.
|
a42d942a68c46b17b4d16e1f71329da3 | 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.
|
a42d942a68c46b17b4d16e1f71329da3 | 38.765 | 9 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 discussion... |
d8a2582e68c28448160ac2de7acb3004 | 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
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 2.1 Expected Output and Time scale
| New specifications
Type
TS/TR number
Title
For info
at TSG#
For approval at TSG#
Remarks
External TR
38.960
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 en... |
d8a2582e68c28448160ac2de7acb3004 | 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.
|
d8a2582e68c28448160ac2de7acb3004 | 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.
-... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 4 Definitions of terms, symbols and abbreviations
| |
d8a2582e68c28448160ac2de7acb3004 | 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.
Standalone 6G RAN: refers... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 4.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
d8a2582e68c28448160ac2de7acb3004 | 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].
6GR 6G Radio
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5 Objectives and requirements
| 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 ... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.1 General Principles
| All requirements of TR 38.914 will serve as the basis for RAN3 architecture design principles.
NOTE 1: If needed, RAN3 will check with relevant working groups on issues concerning security and data privacy.
The 6G RAN architecture and interfaces shall allow for different implementations, e.g. virtualized, cloud-based... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.2 Deployment Scenarios
| |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.2.1 General
| 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 3... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.2.2 Shared RAN deployment
| 6GR should support shared RAN deployments, including support of multiple participating operators. A shared RAN should be able to efficiently interoperate with a non-shared RAN. Mobility and service continuity between the non-shared RAN and the shared RAN shall be supported.
Figure 5.2.x-1: Shared RAN deployment
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.3 Overall RAN Architecture
| Editor’s Note: Figure 5.3-1 and title aim at providing a single framework based on a stand-alone architecture for existing and new services, taking into account legacy communication services, and is subject to study progress including new services.
The names of the logical nodes and the interfaces are FFS.
The 6G RAN... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 5.3.2 RAN Functions
| The aim of this section is to describe the functions supported in RAN.
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6 RAN Architecture and Interfaces
| The aim of this section is to describe all aspects related to the Interfaces between RAN and CN.
6.1 RAN-CN Interface
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.1.1 General Principles
| 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 s... |
d8a2582e68c28448160ac2de7acb3004 | 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 ... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.1.3 RAN-CN Interface Options
| This chapter includes description of RAN-CN interface options including protocol stacks, considering new and existing services.
6.1.3.1 RAN-CN Control Plane
Editor’s Note: The encoding (e.g., ASN.1) for control plane interface options below is FFS.
6.1.3.1.1 Point to Point (P2P)
A RAN-CN P2P interface refers to app... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.1.3.2 RAN-CN User Plane
| Editor’s Note 1: The aim of this section is to describe the user plane protocol stack for the RAN-CN interface.
Editor’s Note 2: On hold waiting for CT4 input.
The user plane interface between the 6G RAN and CN for 6G is based on a point-to-point tunnel.
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.1.4 Evaluation of RAN-CN Interface Options
| This chapter includes evaluation and comparison of RAN-CN interface options described in clause 6.1.3.1
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.2 RAN Internal Interfaces
| 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
This chapter should also address the interfaces between 6G RAN nodes (equivalent to Xn).
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.2.1 General Principles
| The aim of this section is to describe general design principles and requirements for RAN Internal Interfaces
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 6.2.2 Disaggregated RAN Architecture
| RAN3 acknowledges that there are benefits of HLS:
- RAN3 will list benefits
The main areas of study (as a starting point) RAN3 is going to address within this study item for HLS are:
- UE context handling between CU and DU
- F1-U interface optimizations (e.g. flow control)
NOTE: Additional areas of study are FFS.
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 7 AI/ML for RAN
| |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 7.1 High-level principles
| The following high-level principles apply for the 6G RAN AI/ML study:
- The study focuses on AI/ML functionality and corresponding input/output/feedback data.
- The study focuses on data needed at the Model Training function. The aspects of how the Model Training function uses this data to train a model are out of RA... |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 7.2 AI/ML use cases
| Identify Use Case(s) of interest (either existing or new) with compelling trade-off between e.g., performance, complexity, etc…
Editor’s Note: Focus on clarifying the areas where AI/ML can be applied, the scenario description and the problem statement.
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 7.3 AI/ML framework
| |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 8 Radio access network procedures
| 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
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 8.1.1 Intra 6G Mobility
| |
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 8.1.2 Inter-RAT Mobility
| This section is to describe inter-RAT mobility, at least between the 6GR and NR.
|
d8a2582e68c28448160ac2de7acb3004 | 38.760-3 | 8.1.2.1 Mobility between 6GR and 5G NR
| X Conclusions
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
This section is intended to capture considerations related to aspects that fall outside the scope of 3GPP specifications but may nonethele... |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 1 Scope
| The present document reports the RAN1 aspects of the study item “Study on 6G Radio” [2].
|
8e813a83597c9d6f04fe2bcb430572a3 | 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.
-... |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 3 Definitions of terms, symbols and abbreviations
| |
8e813a83597c9d6f04fe2bcb430572a3 | 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.
|
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
8e813a83597c9d6f04fe2bcb430572a3 | 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>
|
8e813a83597c9d6f04fe2bcb430572a3 | 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
|
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5 Physical Layer structure for 6GR
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.1 Waveforms
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.2 Frame structure
| Editor’s Note: Including numerology and frame structure (for all duplex types)
|
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.3 Channel coding
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.4 Modulations
| Editor’s Note: joint channel coding and modulation will be captured in this Clause, if any
|
8e813a83597c9d6f04fe2bcb430572a3 | 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
|
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.6 Physical layer control, data scheduling and HARQ operation
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.7 MIMO operation
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.8 Duplexing
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.9 Spectrum utilization and aggregation
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.10 NTN
| Editor’s Note: harmonized 6G Radio design for TN and NTN, including their integration can be captured in another section. Aspects unique to NTN, if any, can be captured in this section.
|
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 5.11 Other physical layer signals, channels and procedures
| |
8e813a83597c9d6f04fe2bcb430572a3 | 38.760-1 | 6 Energy efficiency
| |
8e813a83597c9d6f04fe2bcb430572a3 | 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
|
8e813a83597c9d6f04fe2bcb430572a3 | 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
|
8e813a83597c9d6f04fe2bcb430572a3 | 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
... |
21583c06c9a14c098fd1bd4da409262a | 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 2... |
21583c06c9a14c098fd1bd4da409262a | 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.
-... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 3 Definitions, symbols and abbreviations
| |
21583c06c9a14c098fd1bd4da409262a | 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 ... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 3.2 Symbols
| |
21583c06c9a14c098fd1bd4da409262a | 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 L... |
21583c06c9a14c098fd1bd4da409262a | 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
Operat... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5 Services offered by the AF
| |
21583c06c9a14c098fd1bd4da409262a | 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... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2 Naf_VFLTraining Service
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.1 Service Description
| |
21583c06c9a14c098fd1bd4da409262a | 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.
|
21583c06c9a14c098fd1bd4da409262a | 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 Funct... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.1.3 Network Functions
| |
21583c06c9a14c098fd1bd4da409262a | 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.
|
21583c06c9a14c098fd1bd4da409262a | 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.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.2 Service Operations
| |
21583c06c9a14c098fd1bd4da409262a | 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 ... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.2.2 Naf_VFLTraining_Subscribe
| |
21583c06c9a14c098fd1bd4da409262a | 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.
|
21583c06c9a14c098fd1bd4da409262a | 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 ser... |
21583c06c9a14c098fd1bd4da409262a | 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 exis... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.2.3 Naf_VFLTraining_Unsubscribe
| |
21583c06c9a14c098fd1bd4da409262a | 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.
|
21583c06c9a14c098fd1bd4da409262a | 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 Tr... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 5.2.2.4 Naf_VFLTraining_Notify
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.