hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9 Solution 2A
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.1 Solution description
Solution 2A exploits downlink signals from one or more satellites to estimate UE position using DL-TDOA, similar to GNSS but relying on existing NR signals (e.g., SSB/CSI-RS/PRS).
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.4 Performance evaluation
For the evaluation of DL-only UE-based positioning method, using DL-TDOA, the following evaluation assumptions and parameters are being considered. Table 7.1.9-1: Evaluation assumptions and parameters for the evaluation of DL-only UE-based positioning method Parameter Description/Value Satellite Orbit As per RAN1#...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.5 Signaling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.9.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10 Solution 2B
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.1 Solution description
Solution 2B proposes that the UE performs multiple random access attempts, each using different time and frequency pre-compensation values derived from alternative reference points within its uncertainty region. It is expected that the random access preamble of at least one attempt falls within the gNB’s detection win...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.5 Signalling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.10.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11 Solution 2C
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.1 Solution description
Solution 2C suggests that the network broadcast explicit time information (timestamps) that UEs can use to calibrate their local clocks. By receiving a “current network time” via SIB or another broadcast control message, a GNSS-less UE can compare it to its own clock to reduce offset and drift. In effect, this replicat...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.5 Signalling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.11.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12 Solution 2D
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.1 Solution description
Solution 2D has the network provide a common timing and frequency reference—such as a reference location, a common Timing Advance (TA), and/or a Doppler offset—that UEs use to pre-compensate their uplink. Rather than depending on each UE’s unknown actual position, all UEs align to a shared assumed reference (e.g., the ...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.5 Signalling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.12.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13 Solution 2E
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.1 Solution description
Solution 2E allows the UE to use its last valid GNSS fix, even if it is outdated, to perform PRACH time and frequency pre-compensation when GNSS is no longer available. Rather than blocking access once GNSS accuracy deteriorates, the UE continues using its most recent position/time information and tolerates the resulti...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.5 Signaling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.13.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14 Solution 2F
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.1 Solution description
Solution 2F proposes that the UE uses existing downlink signals (e.g., SSB, CSI-RS) to self-calibrate its time and frequency prior to PRACH. The UE locks its oscillator to the downlink carrier to reduce frequency offset and can leverage the timing/phase of the received signals to refine its internal timing. No explicit...
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.5 Signalling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.14.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15 Solution 3
Editor’s note – This section will be updated in the next revision
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.1 Solution description
Solution 3 uses implementation-specific receiver techniques without requiring any changes to the standard. As a result, the gNB can detect preambles arriving anywhere within an extended correlation window using a straightforward detection algorithm.
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.2 Relevant scenario
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.3 Specification Impact
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.4 Performance evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.5 Signaling overhead
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.6 Complexity evaluation
321ab524014ad8f3b834b73b9102f8f0
38.742
7.1.15.7 Coexistence with legacy UEs
321ab524014ad8f3b834b73b9102f8f0
38.742
7.2 Candidate solutions for RRC connected mode
321ab524014ad8f3b834b73b9102f8f0
38.742
7.2.1 Evaluation of solutions
321ab524014ad8f3b834b73b9102f8f0
38.742
8 Conclusions and recommendations
Annex <F> (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2025-11 RAN1#123 R1-2508479 TR skeleton for study on GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation 0.0.1 2026-02 RAN1#124 R1-26017...
92904afb872b798c877d70a5d955b6f5
38.763
1 Scope
The present document is a technical report for Over-the-Air (OTA) test methods for NR NTN above 10GHz. This TR targets to define a full set of OTA test methods to cover different NTN UE types of operation above 10GHz.
92904afb872b798c877d70a5d955b6f5
38.763
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. -...
92904afb872b798c877d70a5d955b6f5
38.763
3 Definitions of terms, symbols and abbreviations
92904afb872b798c877d70a5d955b6f5
38.763
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. Definition format (Normal) <defined term>: <definition>. Fixed VSAT: VSAT used in FSS s...
92904afb872b798c877d70a5d955b6f5
38.763
3.2 Symbols
For the purposes of the present document, the following symbols apply: Symbol format (EW) <symbol> <Explanation>
92904afb872b798c877d70a5d955b6f5
38.763
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. Abbreviation format (EW) EIRP Equivalent Isotropically Radiated...
92904afb872b798c877d70a5d955b6f5
38.763
4 General
92904afb872b798c877d70a5d955b6f5
38.763
4.1 Device types
<Editor’s note: Detailed structure of the subclause is TBD. > The test methods developed in this specification target to cover the required device types to meet requirements of 3GPP TS 38.101-5[2] above 10GHz. The test methods development will first focus on VSAT with VSAT and antenna dimensions 65 cm x 65 cm x 15 c...
92904afb872b798c877d70a5d955b6f5
38.763
4.2 Testing configuration
<Editor’s note: Detailed structure of the subclause is TBD. >
92904afb872b798c877d70a5d955b6f5
38.763
4.3 Testing bands
<Editor’s note: Detailed structure of the subclause is TBD. > The frequency ranges in which NTN satellite can operate according to this version of the specification are identified as described in Table 4.3-1. Table 4.3-1: Definition of NTN frequency ranges Frequency range designation Corresponding frequency range ...
92904afb872b798c877d70a5d955b6f5
38.763
5 Performance metrics
<Editor’s note: This clause is not new metric, but just general explanation of performance metric for RF/RRM/Demod, which is highly related to test method and procedure>
92904afb872b798c877d70a5d955b6f5
38.763
5.1 General definition of UE RF metrics
<Editor’s note: Detailed structure of the subclause is TBD. Including at least EIRP, EIS, TRP, TRS>
92904afb872b798c877d70a5d955b6f5
38.763
5.2 General definition of UE RRM metrics
<Editor’s note: Detailed structure of the subclause is TBD. >
92904afb872b798c877d70a5d955b6f5
38.763
5.3 General definition of UE Demodulation metrics
<Editor’s note: Detailed structure of the subclause is TBD. >
92904afb872b798c877d70a5d955b6f5
38.763
6 NTN UE positioning guidelines
<Editor’s note: Detailed structure of the subclause is TBD. >
92904afb872b798c877d70a5d955b6f5
38.763
6.1 Free space
92904afb872b798c877d70a5d955b6f5
38.763
7 UE RF testing methodologies
92904afb872b798c877d70a5d955b6f5
38.763
7.1 General
The testing methodologies will adopt black-box as baseline, and white-box may be considered in the future. All the RF testing assumes that the VSAT beam direction can be controlled to a specific direction (azimuth and elevation) with reference to a declared VSAT antenna coordinate system and remains there. How to enab...
92904afb872b798c877d70a5d955b6f5
38.763
7.2 Applicability of different test methods
<Editor’s note: general applicability of different test methods for each RF requirements> RAN4 agreed to select IFF method as baseline for VSAT NTN testing.
92904afb872b798c877d70a5d955b6f5
38.763
7.3 Indirect far field (IFF)
<Editor’s note: need sub-clauses,> 7.4 other <Editor’s note: need sub-clauses,>
92904afb872b798c877d70a5d955b6f5
38.763
8 UE RRM testing methodologies
92904afb872b798c877d70a5d955b6f5
38.763
8.1 General
92904afb872b798c877d70a5d955b6f5
38.763
8.2 Applicability of different test methods
<Editor’s note: general applicability of different test methods for each RF requirements. Other methods can be further added, if needed>
92904afb872b798c877d70a5d955b6f5
38.763
8.2 Indirect far field (IFF)
<Editor’s note: need sub-clauses,>
92904afb872b798c877d70a5d955b6f5
38.763
9 UE demodulation testing methodologies
92904afb872b798c877d70a5d955b6f5
38.763
9.1 General
92904afb872b798c877d70a5d955b6f5
38.763
9.2 Measurement setup
<Editor’s note: test setup. >
92904afb872b798c877d70a5d955b6f5
38.763
9.3 Test metrics and procedure
<Editor’s note: need sub-clauses > Annex A: UE coordinate system Annex B: Estimation of Measurement uncertainty <Editor’s note: Detailed structure of the subclause is TBD. > B.1 General B.2 MU assessment for UE RF testing B.3 MU assessment for UE RRM testing B.4 MU assessment for UE Demodulation te...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
1 Scope
The present document specifies the stage 2 of Integrated Sensing and Communication in 5G system, including architecture and function enhancements, end to end service operations and procedures based on the requirements documented in TS 22.137 [2], only focusing on aerial object (e.g., drone) detection and tracking use c...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
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. -...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
3 Definitions and abbreviations
0ab65e75fc1089aa73e560eaf8cd0098
23.137
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. Sensing Service Consumer: The entity that requests and consumes Sensing Result. NOTE: I...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
3.2 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]. SenE Sensing Entity SenF Sensing Function <ABBREVIATION> <Expa...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4 Architecture model and concepts
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.1 General concept
The sensing architecture is based on the 5GS architecture defined in TS 23.501 [3]. The 5GS architecture for Sensing Service is supported by 5GC NFs and NG-RAN, which supports sensing services in addition to communication services. In the 5GC, this involves the introduction of a new NF, i.e. the Sensing Function (SenF)...
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.2 Architecture
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.3 Reference points
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.4 Service-based interfaces
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.5 Functional entities
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.6 Protocol stacks
0ab65e75fc1089aa73e560eaf8cd0098
23.137
4.6.1 Protocol stack for sensing control signalling