hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.