hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.1 General | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2 Measurement quantities | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.1 UE originated measurements | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2 L2 measurement quantities | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2.0 General | The following measurements are to be introduced to NR:
- Received Random Access Preambles
- Number of users for RRC_CONNECTED
- Number of users for RRC_INACTIVE
For the following measurements, SA5 defined measurements are to be used instead of measurements defined in TS 36.314 [8]:
- 4.1.1 PRB usage
- 4.1.4 Packet Dela... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2.1 L2 measurements in TS 28.552 | RAN2 and RAN3 have analysed SA5 requirements for "Performance measurements for gNB" defined in TS 28.552 [4], and came to the following conclusion:
Table 6.2.2.1-1: Analysis on performance measurements for gNB in TS 28.552
Clause
Title
Use case description
Views from RAN2 and RAN3
5.1.1
Performance measurements valid f... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2.2 RAN part of packet delay measurement | Packet delay includes RAN part of delay and CN part of delay. This study only covers RAN part of the packet delay.
The RAN part of DL and UL packet delay is measured by gNB and UE at DRB level, respectively. In reporting to TCE, the delay may be provided to QoS flow level by gNB with the assumption that all QoS flows m... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2.2.1 UL packet delay measurement | Figure 6.2.2.2.1-1: RAN part of UL delay
As shown in figure 6.2.2.2.1-1, RAN part (T2-T1) of the UL delay is defined as the delay from packet entering the UE's PDCP upper SAP to leaving gNB's PDCP upper SAP. It can be separated into D1 and D2:
- D1 is the PDCP queuing delay in the UE, including the delay from packet ar... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.2.2.2 DL packet delay measurement | RAN part of the DL delay is measured by gNB by DRB level. For arrival of packets the reference point is PDCP upper SAP. For successful reception the reference point is MAC lower SAP. It includes average delay in DL (e.g. average delay in CU-UP, average delay on F1-U and average delay DL in gNB-DU)*. The delay may be co... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.3 L1 measurement quantities (e.g. Timing Advance in RAR) | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.2.4 Sensor data for UE orientation/altitude to log in addition to location | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.3 Events and faults | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.3.1 RLF and access failure information | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6.4 Conclusion | The feasibility of L2 measurements in TS 28.552 have been checked in TR 37.816. The following feasible L2 measurements are recommended to be supported in NR in context of RAN-centric data collection:
- PRB usage
- Packet Delay
- Data loss
- Scheduled IP Throughput
- Scheduled IP Throughput for MDT
- Data Volume
- Distr... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 7 Conclusion | RAN3 conclusions
The following SON features are recommended by RAN3 to be specified in normative phase:
- Capacity and Coverage Optimization
- PCI Selection
- Mobility Optimization
- Load Sharing and Load Balancing Optimization
- RACH Optimization
- Energy Saving
Recommendations for each feature are described in the de... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 1 Scope | The present document is intended to capture findings produced in the context of the study on optimizations of UE radio capability signalling.
The study is expected to proceed as follows:
- Study the size of UE Radio Capability signaling
- Study mechanisms to optimise the UE Radio Capability signalling over the air whil... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 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.
- Fo... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 3 Definitions, symbols and abbreviations | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 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].
example: text used to clarify abstract rules by applying them literally. |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 4 Void | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 5 UE Radio Capability Signaling Size Analysis | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 5.1 UE Radio Capability size estimation | For LTE, the primary overhead introduced by Rel-15 parameters is FeatureSetsEUTRA-r15. The theoretical overhead of FeatureSetsEUTRA-r15 can exceed 10 kbytes.
In practical deployment, the size of featureSetsEUTRA-r15 is variable depending on the number of DL/UL feature sets per band and the number of DL/UL feature sets ... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 5.2 Limitations on different interfaces | The estimated theoretical maximum size of UE radio capabilities is extremely large. The estimated practical size of UE radio capabilities can be reduced, and the estimated size of "several tens of kilo-octets" appears to be valid.
For RAN interfaces, the size limitation of PDCP PDU is 9000 bytes for NR and 8188 bytes L... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 5.3 Analysis | It is hard for the size of UE radio capabilities to respect the limitation of Uu interface both for NR and LTE, and it can even exceed the limitation of GTP based interfaces.
The issue of exceeding the size limitation exists mainly for:
1) UE radio capabilities reporting via Uu interface in NR scenario and LTE scenario... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6 UE Radio Capability Signaling Optimizations | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1 Solutions using UE capability Identity | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1 UE capability Identity | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.1 Description | This section describes the use of a UE capability identity, i.e. a short value that can be used as a representation of all or part of the UE capability.
RAN2 preference is for a single capability identity covering all capability containers (i.e. UE-NR-Capability, UE-EUTRA-Capability, and UE-MRDC-Capability), as opposed... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.2 Signalling for transfer of UE capability identity | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.2.1 Approach 1: Transfer via RRC signalling | The transfer of UE capability in RRC signalling is shown in Figure 6.1.1.2.1-1. The UE sends a UE capability ID in an RRC message, which could be either the RRCSetupComplete message or the UECapabilityInformation message. The subsequent handling of the UE capability ID is discussed in subclause 6.1.1.3. In this alter... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.2.2 Approach 2: Transfer via NAS signalling | The transfer of UE capability in NAS signalling is shown in Figure 6.1.1.2.2-1.The UE sends a UE capability ID to the CN using a NAS message before the CN sends the Initial Context Setup Request to the NG-RAN. The subsequent handling of the UE capability ID is discussed in subclause 6.1.1.3. In this alternative, the U... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3 Interaction between NG-RAN and CN for management of UE capability identity | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3.1 Summary of approaches | After the UE capability ID is transferred from the UE to either the NG-RAN or the CN, an entity in the network is responsible for mapping the ID to the UE capability set.
If the ID is first provided to the NG-RAN (e.g. by RRC signalling as described in subclause 6.1.1.2.1), there are three alternatives: The mapping of ... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3.2 Approach 1: Mapping stored at NG-RAN only | If the mapping is stored at the NG-RAN only, no capability-related interaction with the CN is required and the capability exchange can proceed as shown in Figure 6.1.1.3.2-1.
Figure 6.1.1.3.2-1: NG-RAN identification of UE capability without CN interaction
In the procedure of Figure 6.1.1.3.2-1, step 1 may involve eith... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3.3 Approach 2: Mapping stored at CN only | If the mapping is stored at the CN only, the capability exchange can proceed as shown in Figure 6.1.1.3.3-1.
Figure 6.1.1.3.3-1: CN identification of UE capability and delivery to NG-RAN
In the procedure of Figure 6.1.1.3.3-1, step 1 may involve either RRC signalling (as in subclause 6.1.1.2.1, with subsequent transfer... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3.4 Approach 3: Mapping stored at CN and NG-RAN, using NAS signalling | If the mapping is stored at the CN and the NG-RAN and the transfer of the UE capability ID uses NAS signalling, the capability exchange can proceed as shown in Figure 6.1.1.3.4-1.
Figure 6.1.1.3.4-1: NG-RAN and CN identification of UE capability (with NAS signalling)
In the procedure of Figure 6.1.1.3.4-1, if the CN is... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.1.3.5 Approach 4: Mapping stored at CN and NG-RAN, using RRC signalling | If the mapping is stored at the CN and the NG-RAN and the transfer of the UE capability ID uses RRC signalling, the capability exchange can proceed as shown in Figure 6.1.1.3.5-1.
Figure 6.1.1.3.5-1: NG-RAN and CN identification of UE capability (with RRC signalling)
In the procedure of Figure 6.1.1.3.5-1, if the NG-RA... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.2 UE capability Identity combined with other means | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.2.1 Solution using Hash-based Identification of UE radio capabilities | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.2.1.1 Description | On HASH-based ID's as described in solution #3 in 23.743[3], RAN2 has identified that, to create a hash-Capability ID the UE needs to do this assuming some specific capability information. It is not obvious what capability information the UE would have the hash operate on to create the ID. Further, there are aspects re... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.2.2 UE Capability ID with delta set of UE Radio Capabilities | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.1.2.2.1 Description | On 'delta signalling' as described in solution #9 in 23.743[3], RAN2 understands that all the impacts of 'delta signalling' (i.e. some additional capability information alongside the capability ID) would be within the RAN2 specifications and therefore it should be RAN2 decision to conclude on support of this feature. R... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2 Solutions using other means | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1 Segmentation of capabilities | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1.1 Description | This section describes the segmentation approach to transfer UE capabilities. If the capability size is over 9000 bytes for NR and 8188 bytes for LTE, then capabilities are segmented into smaller pieces. |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1.2 Signalling for transfer of UE capabilities in segments | A signalling diagram to transfer capabilities in segments is shown in Figure 6.2.1.2-1. In the first step, the eNB/gNB requests capabilities. The UE constructs capabilities and segments the capabilities to the pieces not exceeding the maximum PDCP SDU size. Segments are transmitted to the network by the lower layers. O... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1.3 Segmentation structure | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1.3.1 Segmentation at RRC level | In the segmentation of UE capabilities in the RRC level, for each segment, a type (e.g. notLastSegment, lastSegment) as well as a segment number is added. The RRC segmentation can be done in different ways as described below.
Option 1: "hard" split RRC Segmentation:
This approach is similar to ETWS/CMAS in LTE and NR. ... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.1.3.2 Segmentation at PDCP level | On the Transmitting side,
1. PDCP segments the huge RRC message (i.e. RRC PDU) into multiple PDCP SDUs;
2. The size of each PDCP SDU does not exceed 9000bytes for NR or 8188 bytes for LTE;
3. The last PDCP SDU is tagged with end-marker in the corresponding PDCP PDU header.
Figure 6.2.1.3.2-1: Illustration of UE capabil... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 6.2.2 Uplink Capability Signalling Compression (UCSC) | UCSC is a technique to minimize the redundancy in the UE capability information sent by the UE to the network. The NG-RAN informs the UE whether it supports compression in the capability enquiry. Depending on the UE capability to support compression, the UE responds with compressed or uncompressed capability informatio... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 7 Conclusion | |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 7.1 Solutions using UE capability Identity | Based on the study, RAN2 recommends that UE capability Identity transfer via NAS signalling, in section 6.1.1.2.2, is introduced in the normative phase. In addition, UE capability ID in UECapabilityInformation message should also be supported (only after AS security is activated).
RAN2 also concludes that it is possibl... |
d735229c4aeaadc75c90b63fa4f4e6ff | 37.873 | 7.2 Solutions using other means | RAN2 recommends that RRC level segmentation with hard split to be specified in any follow on WI.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2018-10
RAN2 #103bis
R2-1813777
-
-
-
Skeleton TR
0.0.1
2019-03
RAN2 #105
R2-1902690
TR 37.873 v0.1.0 as agreed by RAN2 in emai... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 1 Scope | The present document is the Technical Report for the Work Item on Integrated Access and Backhaul for NR. The present document captures the background and the decisions on IAB requirements. |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 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.
- Fo... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 3 Definitions of terms, symbols and abbreviations | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 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].
IAB type 1-H: IAB-MT and IAB-DU operating at FR1 with a requirement set holding requiremen... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
The composite antenna array pattern in dB
The array element pattern in dB
BeW The Beam width in
BeWϕ The Beam width in ϕ |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 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].
EMC Electromagnetic Compatibility
ESD Electrostatic discharge
IAB... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4 General aspect | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.1 Relation with other core specification | IAB (Integrated Access and backhaul) node is a RAN node that supports wireless access to Ues and wirelessly backhauls the access traffic. Direct application of only Base station RF requirements is not appropriate enabler for both the wireless backhaul and wireless access and thus a new TS spec 38.174[8] will be specifi... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.2 RF Requirements reference points | The requirement reference points for BS is defined as below:
Table 4.2-1: BS requirement sets
BS type / Requirement set
BS Description
Additional information
1-H
A BS operating at FR1 with a requirement set holding requirements defined at the TAB and OTA requirements defined at RIB.
The requirement set is like the one ... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.3 IAB classification | IAB-MT classification and IAB-DU classification will be defined separately.
For IAB-DU the classification will be the same as NR BS classification in TS 38.104 [2] to support Wide Area IAB-DU, Medium Range IAB-DU and Local Area IAB-DU with the same deployment scenarios for each class as for BS. The same criteria and ex... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.4 Void | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.5 IAB architecture | The logical architecture (considering the RF interfaces) of the IAB is as follows:
Figure 4.5-1: Logical IAB functions showing RF interfaces
In the RF specification these logical functions have been separated into the HW entities the IAB-DU and the IAB-MT IAB-DU. The HW entities may be implemented in the same radio har... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.6 IAB test efficiency optimization | In case the same RF implementation is used for both IAB-MT and IAB-DU, it would be inefficient to test separately both IAB-MT and IAB-DU. Therefore, test efficiency optimization rules were defined.
For test efficiency optimization to apply, manufacturer needs to declare usage of same RF hardware, and in addition to tha... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 4.7 Void | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 5 Operating band and channel arrangement | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 5.1 General | The Frequency range definitions for IAB will be the same as for the NR BS in TS 38.104 [2]. |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 5.2 Operating bands | Operating bands will be added to the IAB specification as they are approved, no bands are precluded at this stage and can be added based on consensus. Currently the FR1 bands shown in table 5.2-1 and all Rel-15 FR2 bands shown in table 5.2-2 are to be included in the IAB specification.
Table 5.2-1: NR operating bands i... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 5.3 Channel bandwidth | Channel bandwidth covers definitions on the transmission bandwidth configuration, minimum guard band, RB alignment and channel bandwidth per operating band. For the transmission bandwidth configuration and minimum guard band, existing NR definition for BS and UE for each frequency range is the same. And they should be ... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 5.4 Channel arrangement | Channel arrangement includes channel spacing, channel raster and sync raster. The introduction of IAB node should be transparent to UE from IAB-DU perspective. And it is not expected to impact on existing fundamental NR design on global channel raster and sync raster as well. Hence the channel raster, channel raster an... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6 Co-existence study | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.1 System layout and scenario | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.1.1 Layout for co-existence study | For Layout 1 considered in IAB co-existence study the details are provided in Table 6.1.1-1 and figure 6.1.1-1 as below.
Figure 6.1.1-1: Layout 1
Table 6.1.1-1: Parameters for Layout 1
Parameters
Values and remarks
Layout for nodes
IAB network: Two layer
Macro layer: Hex. Grid (3 sector) (all macro BSs are IAB-donors)
... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.1.2 Scenarios for co-existence study | There are two scenarios considered in co-existence study as shown in table 6.1.2-1.
Table 6.1.2-1: IAB co-existence scenarios
Scenario
Details
Scenario 1
In case of TDM operation the following mapping of IAB node transmission/reception to a TDD pattern (DL/UL/F resources) is assumed:
IAB DU transmission / IAB MT recept... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.1.3 Co-location | An IAB node is capable of transmitting in the DL (IAB-DU) or the UL (IAB-MT). When acting as an IAB-MT there are 2 possible co-location interference scenarios between the IAB-MT and a BS.
- Aggressor IAB-MT transmitting in UL, victim BS receiving in UL
- Aggressor BS transmitting in DL, victim IAB-MT receiving in DL
Fo... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2 Simulation assumption | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.1 Propagation model | RAN4 study on IAB co-existence reuse the pathloss model between parent/donor IAB node DU and child IAB node MT agreed in RAN1 in TR 38.874.
The path loss for links between the IAB-node and candidate serving IAB-nodes/donors is determined based on N independent large-scale channel realizations (taking into account LOS/N... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.2 Antenna configuration | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.2.1 General | Since some parameters required by the array antenna model are not independent, arbitrary parameter values are not supported. If parameters are selected arbitrary the model will produce incorrect gain characteristics.
We define arrays using the number of columns, rows, the separation between them as well as the definiti... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.2.2 FR1 | The FR1 antenna is defined as:
Table 6.2.2.2-1 FR1 IAB antenna model for macro scenario
Parameter
Values
Composite Array radiation pattern in Db
the steering matrix components are given by
the weighting factor is given by
Antenna element vertical radiation pattern (Db)
Antenna element horizontal radiation pattern (Db)
... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.2.3 FR2 | The FR2 BS antenna is defined as:
Table 6.2.2.3-1. FR2 IAB antenna model for macro scenario
Parameter
Values
Composite Array radiation pattern in Db
the steering matrix components are given by
the weighting factor is given by
Antenna element vertical radiation pattern (Db)
Antenna element horizontal radiation pattern (... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.2.3 Other simulation assumption | The remaining simulation assumptions such as link level assumption, system level assumption, and simulation methodology are captured in this clause.
Table 6.2.3-1: Link level assumptions
Parameter
Details
Target SNR
IAB node-MT:
SNR target: 22dB [upper limit of approx curve]
γ = 1
Legacy NR UE:
SNR target: 15 dB
γ = 1
... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.3 Simulation result | Simulation result provided for IAB co-existence study is summarized in Annex A. |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 6.4 Void | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7 Conducted transmitter characteristics | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.1 General | Conducted transmitter characteristics were defined for IAB-MT type 1-H and IAB-DU type 1-H. Requirements were agreed not to be defined for type 1-C, as type 1-H can also support only one TAB connector. Another reason is that, the IAB expects directional antennas, therefore, only AAS types were considered. The general p... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.2 IAB output power | IAB output power limits are defined for each IAB-DU and IAB-MT class. For each class the rated power per carrier at TAB connector and sum of rated power per carrier over all TAB connectors need to be aligned with specified limits.
For IAB-DU the limits are exactly the same as defined for NR BS type 1-H.
For IAB-MT only... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.3 Output power dynamics | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.3.1 Power control | The power control requirements are not defined to the wide area IAB-MT, as the tolerances for power control are large compared to the minimum requirement for dynamic range.
For the local area IAB-MT, the absolute power tolerance was not defined as the dynamic range defined for the local area IAB-MT is not large enough ... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.4 Transmit ON/OFF power | Transmit ON/OFF power requirements include two parts: transmitter off power and transmitter transient period. For IAB-DU, it's straightforward to reuse BS's both requirements because IAB-DU behaviour is the same as BS.
For IAB-MT, reusing BS or UE requirements for both OFF power and transient period are the candidates.... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.5 Transmitted signal quality | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.5.1 IAB-DU transmitted signal quality | As the IAB-DU behavior is very similar with BS, all of the transmitted signal quality requirements can be imported from BS. Therefore, the frequency error, modulation quality and time alignment error requirements in clause 6.5.1, 6.5.2, 6.5.3 for BS type 1-H in TS 38.104 [2] apply to IAB-DU type 1-H. |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.5.2 IAB-MT transmitted signal quality | |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.5.2.1 Frequency error | As IAB-MT function is more like a UE, UE frequency error correction can be a reference. When BS transmits DL signal to UE, UE does frequency error correction algorithm to make sure UE follows BS with a relative low residual frequency error.The residual frequency error after compensation should be less than one percent ... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.5.2.2 Error Vector Magnitude | EVM performance is the SNR performance of the transmitted signal. In order to have the same link performance, IAB-MT output signal quality should have the same performance as UE then guarantee the link quality. UE requirements are reused by IAB-MT EVM requirements. The difference is that BPSK EVM requirement is removed... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.6 Unwanted emissions | Unwanted emissions cover the definitions and requirements for OOB boundary, occupied bandwidth, ACLR including also absolute ACLR, OBUE, and spurious emissions.
For IAB-DU type 1-H all unwanted emissions requirements, except for the protection of the BS receiver of own or different BS, are the same as specified for NR ... |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 7.7 Transmitter intermodulation | For conducted transmitter intermodulation, it is agreed to reuse the base station framework for both IAB-DU and IAB-MT. |
5d80416bb8e462e97be7acb8f332ff7e | 38.809 | 8 Conducted receiver characteristics |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.