hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.1.1 Key Issue #1: DMFW Capabilities
| The DMFW should support the following capabilities:
• Data lifecycle management
• Data collection: the capability to collect data which includes:
◦ Existing management data : Performance Measurements (PM), Key Performance Indicators (KPI), Fault/Alarm data, Configuration Management (CM) related dat... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.2 Data and Knowledge Management
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.2.1 Key Issue #1: Knowledge/semantic representation and management
| 6G management system should understand meaning and relationships of data, in addition to processing syntactic data by making semantics more explicit. Knowledge representations should be used for 6G network management.
Knowledge requires data, the modelling of Knowledge and data should be related.
6G management syste... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.2.2 Key Issue #2: Data management – Concepts and terminology
| This key issue is about a common concept and terminology for data modelling and data management. A common concept and terminology ensures consistent and clear specifications, thus helping to increase the interoperability of solutions from different vendors. It also makes the process of writing standards more efficient ... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.3 Management Agent
| There are three types of agent:
1. Agent external to 3GPP system, e.g., 3rd party application Agent
2. Management Agent within 3GPP management system
3. Agent in 3GPP network
Clause 7.3.2 focuses on the concept of management agent within 3GPP management system.
Editor’s Note: Use of “Management Agent” in bullet 2... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.3.1 Key Issue #1 Concept of agent in management domain
| Management Agent: an entity that operates autonomously to achieve a specific goal for service and network management and orchestration. Management Agent may be intent driven, task driven, adaptive, capable of continuously learning, reasoning, decision-making and able to adapt its behaviours based on the changing condit... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.4 Energy Saving and Energy Efficiency
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.4.1 Key Issue #1: Energy efficiency management architectural framework
| The 6G management system should support the following Energy Saving (ES) and Energy Efficiency (EE) management scenarios. This includes the MnS capabilities that need to be studied to be supported in 6G to enable the support of the same set of capabilities as in 5G, while allowing extensions for 6G.
1) A Centralized ... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.5.1 Key Issue #1: Improvements to LCM based on NF Deployments
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.5.1.1 Description
| SA5 has conducted a study on LCM of NF Deployments in Rel-19. The scope of the study did not include the impact of NF Deployments on higher layer use cases like Sub-Network, Network Slice Subnets.
As part of the normative work in Rel-20, the 5GA WID ( SP-251697 [6]) for NF Deployment LCM has created tasks to specify ... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.5.1.2 Potential Requirements
| MREQ-CMO-1: 3GPP management system should support LCM of Network Slice Subnets for NF Deployments.
MREQ-CMO-2: 3GPP management system should support LCM of Sub-Network for NF Deployments.
Editor’s note: It is FFS if more requirements need to be specified. This is dependent on the progress of the 5GA Rel-20 normative ... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 8 Solutions
| Editor's note: This clause will contain potential solutions related to the Key Issues in clause 7. The Mapping table in the Annex A will reflect the relation between potential Key Issues and solutions.
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 8.1 Potential Solution #1: <title>
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 8.2 Potential Solution #2: <title>
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 9 Conclusions and Recommendations
| Editor's note: This clause will contain conclusions and recommendations for the Key Issues identified in clause 7.
Annex A:
Management Scenarios, Key Issues, and Solutions Mapping
A.1 Mapping between Management Scenarios and Key Issues
Table A.2-1: Mapping of Key Issues to Management Scenarios
Key Issues
Manage... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 1 Scope
| This technical report addresses the study of GNSS (Global Navigation Satellite System) resilient operation in NR-NTN (Non-Terrestrial Networks), targeting Release 20 enhancements. The objective is to evaluate and define solutions to ensure NR-NTN functionality in scenarios where GNSS is temporarily unavailable while ma... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 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.
-... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 3 Definitions of terms, symbols and abbreviations
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 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].
Feeder link: Wireless link between NTN Gateway and satellite.
Geostationary Earth orbit: Circular ... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 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].
CSI-RS Channel State Information-Reference Signal
DL-TDOA Downlink Time D... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 4 Background and motivation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 4.1 Review of previous NR-NTN releases
| UEs compatible with Rel-17/18/19 and supporting NTN access are expected to be equipped with GNSS (Global Navigation Satellite System) [5, TS 38.300]. According to [5, TS 38.300], NTN UE shall not perform uplink transmission (e.g., PRACH preamble, PUSCH) if the UE does not have a valid GNSS position. Indeed, NTN UE shou... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 4.2 Motivation for GNSS-resilient NR-NTN operation
| GNSS availability is therefore essential for Rel-19 NTN access due to its necessity for physical layer operation. Additionally, GNSS availability may be useful for higher layer procedures such as location-based conditional handovers. In practice, however, GNSS information in the UE may be temporarily unavailable or ava... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 4.3 Study objectives
| The primary objective of this study is to investigate GNSS-resilient operation of NR-NTN (New Radio - Non-Terrestrial Networks) systems, addressing the challenges posed by potential GNSS unavailability or degradation. This study will assess the impact of GNSS limitations on both initial access and connected mode proced... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 5 Assumptions and study parameters
| This section outlines the key assumptions and study parameters that underpinned the evaluation process. These assumptions define the operational context and constraints within which the evaluation was conducted. The parameters detailed below cover aspects such as network configuration, UE capabilities, and environmenta... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6 Evaluation of impacts of GNSS temporary unavailability
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.1 Methodology
| To evaluate GNSS-resilient operation on the uplink time and frequency synchronization in initial access, the adopted methodology assesses the differential one-way delay/timing offset and one-way Doppler/frequency offset within a defined uncertainty area (UA), reflecting the degraded GNSS positioning accuracy during una... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2 Calculation of differential delay and Doppler
| For the calculation of one-way differential delay and one-way differential Doppler, the following geometry model is considered. For the variables in the equations, refer to Figure 2.
Editor’s note – This section will be updated in the next revision to provide explicit definitions of all variables used in the equations... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.1 Differential delay calculation results
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.1.1 Differential one-way delay
| The following tables provide differential one-way delay (DOWTO) values obtained from multiple sources. All results assume a UE altitude of 0 km, and UE altitude uncertainty is not taken into account. The results are provided for two main types of location uncertainty areas and two geometrical configurations. In Case A,... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.1.2 Differential round-trip delay
| As outlined earlier, for uplink performance evaluation, twice the DOWTO value is considered, accounting for the round-trip delay impact on UL timing accuracy. The following Tables provide the round trip delay for different uncertainty areas.
Table 6-7 and Table 6-2 provide the differential round trip delay values for ... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.2 Differential Doppler calculation results
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.2.1 Differential DL one-way Doppler
| The following tables summarize differential downlink one-way Doppler/frequency offset (DOWFO) values compiled from multiple sources; the results assume a UE altitude of 0 km and a UE speed of 3 km/h, do not consider Earth rotation, and do not account for UE altitude uncertainty. The results are categorized by two prima... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.2.2 Differential uplink Doppler
| The differential uplink Doppler/frequency offset shall be calculated by scaling the DL one-way differential Doppler/frequency offset with a factor equal to 2* / . Here, and denote the uplink and downlink carrier frequencies, respectively. Thus,
Differential UL Doppler/frequency offset = 2* / × (DL one-way different... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.2.3 Calculation results summary
| Editor’s note – This section will be updated in the next revision, add a paragraph introducing the results summary tables.
Table 6-27: Differential round trip delay and Differential Doppler in UL | Set1- parameters
Orbit
Frequency Band
UA diameter (km)
Elevation (°)
Differential round-trip delay (in µs)
Differe... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.3 Impact on initial access
| The performance evaluation of existing PRACH formats is based on an analytical method that compares scenario-specific differential delay and Doppler values against the established PRACH tolerance limits for timing and frequency error. This analytical method is summarized as follows: For each PRACH format and configurat... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.3.1 Differential RTD limits for PRACH preamble formats
| For PRACH performance evaluation of existing PRACH preamble formats using analytical characterization, PRACH RTD tolerance is considered exceeded for unrestricted set if:
min (, Sequence duration) Differential RTD
In this criterion, is the cyclic prefix duration; is as specified in Tables 6.3.3.1-5, 6.3.3.1-6, ... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.3.2 Differential doppler shift limits for PRACH preamble formats
| For PRACH performance evaluation of existing PRACH preamble formats using analytical characterization, Doppler shift tolerance is deemed exceeded when the scaled UL differential Doppler/frequency offset surpasses the tolerance associated with the selected preamble set, that is:
Scaling factor*(DL Differential Doppler... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.3.3 NR PRACH performance evaluation
| The results of differential round-trip delay and uplink differential Doppler versus the maximum allowed PRACH tolerances is provided in Table 6-34 through Table 6-39. Interpretation applied: negative values indicate margin (tolerance met); positive values indicate gap (tolerance exceeded). A PRACH option is considered ... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 6.4 Impact on connected mode
| To evaluate the impact of GNSS-resilient operation on NR-NTN UEs in RRC Connected mode, the signalling overhead associated with timing and frequency adjustment is assessed under a common set of assumptions.
The analysis follows the satellite orbit and satellite parameter configurations given in section 5, and focus o... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7 Evaluation of solutions for GNSS resilient NR-NTN
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1 Candidate solutions for initial access
| To support GNSS-resilient NR-NTN operation, especially for initial access in the presence of large time and frequency uncertainties, a set of candidate solutions is considered with the objective of increasing PRACH robustness and/or reducing the associated uncertainty. The following solution candidates span enhancement... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1 Solution 1A
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.1 Solution description
| Solution 1A enables a UE to transmit multiple PRACH preambles using multiple random access occasions. Within each random access occasion, the UE transmits a PRACH preamble with existing PRACH format with time/frequency pre-compensation derived from an assumed reference location. Across the random access occasions with... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.5 Signalling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.1.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2 Solution 1B
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.1 Solution description
| Solution 1B suggests defining restricted PRACH preamble sets that are specifically optimized for NTN. By constraining the Zadoff–Chu sequence configurations (for example, using larger zero-correlation zones), this approach seeks to enhance robustness against Doppler and frequency offsets, at the expense of reducing the... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.5 Signalling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.2.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3 Solution 1C
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.1 Solution description
| Solution 1C proposes a multi-step Random Access Response procedure. The UE sends a single PRACH preamble, and once it is detected, the gNB issues multiple Timing Advance (TA) and/or Frequency Advance (FA) commands within Msg2 (RAR) or through multiple RAR messages. The UE then transmits Msg3 several times, each using a... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.5 Signalling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.3.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4 Solution 1D
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.1 Solution description
| Solution 1D proposes enhancing the random access procedure by introducing additional fields in Msg2 (RAR) and/or Msg4 to refine time and frequency alignment after preamble detection. These may include an extended-range or higher-resolution Timing Advance (TA), an explicit frequency adjustment command for Doppler compen... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.5 Signalling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.4.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5 Solution 1E
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.1 Solution description
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.5 Signalling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.5.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6 Solution 1F
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.1 Solution description
| Solution 1F proposes that the network broadcast a Timing Advance (TA) margin to UEs and apply Random Access Occasion (RO) masking. UEs then transmit PRACH with an additional timing offset (the margin) after performing initial TA pre-compensation, while the network deactivates certain PRACH occasions additionally to cre... |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.5 Signaling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.6.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7 Solution 1G
| Editor’s note – This section will be updated in the next revision
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.1 Solution description
| Solution 1G proposes dynamically adapting existing PRACH configurations for GNSS-resilient operation of a quasi-Earth fixed cell by selecting formats and parameters that better tolerate large delay and/or Doppler depending on the elevation angle.
|
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.2 Relevant scenario
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.3 Specification Impact
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.4 Performance evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.5 Signaling overhead
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.6 Complexity evaluation
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.7.7 Coexistence with legacy UEs
| |
321ab524014ad8f3b834b73b9102f8f0 | 38.742 | 7.1.8 Void
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.