Add files using upload-large-folder tool

README.md

@@ -0,0 +1,69 @@
+---
+language:
+  - en
+license: other
+license_name: 3gpp
+license_link: https://www.3gpp.org/specifications-technologies/legal-matters
+tags:
+  - telecommunications
+  - 3gpp
+  - 5g
+  - nr
+  - lte
+  - mobile
+  - standards
+  - specifications
+  - release-18
+pretty_name: 3GPP Release 18 Specifications
+---
+
+# 3GPP Release 18 Specifications
+
+549 3GPP Release 18 technical specifications converted from DOCX to Markdown
+using the Datalab API, with all extracted figures.
+
+## Repository Structure
+
+```
+original/                     Source DOCX from 3GPP
+  21900-i10.docx
+  38331-i00.docx
+  ...
+
+gsma/                         Datalab conversion output
+  {series}/
+    {spec_id}/
+      raw.md                  Full markdown
+      {hash}_img.jpg          Extracted figures
+      ...
+```
+
+## Usage
+
+Each spec is a self-contained folder with its markdown and images:
+
+```
+gsma/38_series/38331/
+  raw.md                      3GPP TS 38.331 (RRC protocol specification)
+  64662465..._img.jpg         5G logo
+  5fb340ad..._img.jpg         3GPP logo
+  2cf38963..._img.jpg         UE state machine diagram
+  ... (67 images total)
+```
+
+Images in `raw.md` use relative paths, so they resolve when the folder is kept together.
+
+## Stats
+
+| Metric | Value |
+|--------|-------|
+| Specifications | 549 (422 TS, 127 TR) |
+| Total text | 287M characters |
+| Extracted figures | 16,147 |
+| Source DOCX | 553 files |
+| Series | 14 (21 through 38) |
+
+## License
+
+3GPP specifications are subject to 3GPP intellectual property rights policy.
+See [3GPP Legal Matters](https://www.3gpp.org/specifications-technologies/legal-matters).

gsma/37_series/37114/raw.md

@@ -0,0 +1,979 @@
+
+
+# 3GPP TS 37.114 V18.0.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC) (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                 |           |
+|-----------------------------------------------------------------|-----------|
+| Foreword .....                                                  | 5         |
+| 1 Scope.....                                                    | 7         |
+| 2 References.....                                               | 7         |
+| 3 Definitions, symbols and abbreviations .....                  | 9         |
+| 3.1 Definitions.....                                            | 9         |
+| 3.2 Symbols.....                                                | 11        |
+| 3.3 Abbreviations .....                                         | 11        |
+| 4 Test conditions .....                                         | 12        |
+| 4.1 Exclusion bands.....                                        | 13        |
+| 4.1.1 Transmitter exclusion band .....                          | 13        |
+| 4.1.2 Receiver exclusion band.....                              | 13        |
+| 4.2 Arrangements for establishing a communication link.....     | 14        |
+| 4.3 Narrow band responses on receivers.....                     | 14        |
+| 4.4 BS test configurations .....                                | 14        |
+| 4.5 Manufacturer declarations.....                              | 18        |
+| 5 Performance assessment .....                                  | 18        |
+| 5.1 General .....                                               | 18        |
+| 5.2 Assessment of performance in Downlink .....                 | 19        |
+| 5.3 Assessment of performance in Uplink .....                   | 19        |
+| 6 Performance criteria.....                                     | 19        |
+| 7 Applicability overview.....                                   | 20        |
+| 7.1 Emission.....                                               | 20        |
+| 7.2 Immunity .....                                              | 20        |
+| 8 Emission.....                                                 | 20        |
+| 8.1 Test configurations.....                                    | 20        |
+| 8.2 Radiated emission from base station.....                    | 21        |
+| 8.2.1 Radiated emission, hybrid AAS BS .....                    | 21        |
+| 8.2.2 Radiated emission, OTA AAS BS.....                        | 21        |
+| 8.3 Conducted emissions, DC power input/output port .....       | 22        |
+| 8.4 Conducted emissions, AC mains power input/output port.....  | 22        |
+| 8.5 Harmonic current emissions (AC mains input port) .....      | 22        |
+| 8.6 Voltage fluctuations and flicker (AC mains input port)..... | 22        |
+| 8.7 Conducted emissions, telecommunication ports .....          | 22        |
+| 9 Immunity .....                                                | 23        |
+| 9.1 Test configurations.....                                    | 23        |
+| 9.2 RF electromagnetic field (80 MHz - 6000 MHz).....           | 24        |
+| 9.2.1 RF electromagnetic field, hybrid AAS BS .....             | 24        |
+| 9.2.2 RF electromagnetic field, OTA AAS BS .....                | 24        |
+| 9.3 Electrostatic discharge.....                                | 25        |
+| 9.4 Fast transients common mode.....                            | 25        |
+| 9.5 RF common mode (0.15 MHz - 80 MHz).....                     | 26        |
+| 9.6 Voltage dips and interruptions .....                        | 26        |
+| 9.7 Surges, common and differential mode.....                   | 26        |
+| <b>Annex A (normative): Simplified immunity testing.....</b>    | <b>27</b> |
+| A.1 Applicability.....                                          | 27        |
+| A.2 Capability Sets for simplified immunity testing .....       | 27        |
+| <b>Annex B (informative): Change history .....</b>              | <b>28</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document covers the assessment of UTRA TDD, UTRA FDD, E-UTRA, NR and Multi-Standard Radio (MSR) Active Antenna Systems Base Stations in respect of Electromagnetic Compatibility (EMC).
+
+NOTE 1: Whenever the AAS BS in *single RAT UTRA operation*, or AAS BS in *MSR operation* using UTRA is referred in this specification, UTRA TDD and UTRA FDD shall be considered, unless otherwise stated.
+
+NOTE 2: For NR, scope of this specification is limited to *BS type 1-H* and *BS type 1-O*. For EMC requirements of the MSR BS for *BS type 1-C*, refer to TS 37.113 [4].
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- Active Antenna System Base Station for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3],
+- Active Antenna System Base Station for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of 3TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10].
+
+Technical requirements related to the TAB connector are not included in the present document. These are found in the relevant product standards [2, 3, 10].
+
+The present document does not cover ancillary equipment requirements, where ancillary equipment is not incorporated in the radio equipment and can be assessed on a stand-alone basis, as declared by the manufacturer. Ancillary equipment EMC requirements are still applicable to the AAS BS and are covered by other EMC specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30].
+
+The present document does not specify test conditions, performance assessment and performance criteria for the Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* as defined in TS 36.113 [6], or for AAS BS in *MSR operation* using E-UTRA as defined in TS 37.113 [4].
+
+The present document does not specify test conditions, performance assessment and performance criteria for Band 46 operation as it is not supported by AAS BS.
+
+The scope of the present document is twofold:
+
+- Requirement, procedures and values of a *hybrid AAS BS* with *TAB connectors* for every transceiver unit at the *transceiver array boundary* (TAB), subject to conducted requirements,
+
+NOTE 3: *hybrid AAS BS* in the single RAT NR operation is equivalent to *BS type 1-H* defined in NR BS specification TS 38.104 [31].
+
+- Requirements, procedures and values of an OTA AAS BS without *TAB connectors* and relying in the radiated interface, subject to radiated requirements.
+
+NOTE 4: OTA AAS BS in the single RAT NR operation is equivalent to *BS type 1-O* defined in NR BS specification TS 38.104 [31].
+
+The electromagnetic environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [7] and IEC 61000-6-3 [8].
+
+The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence.
+
+# 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 TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception".
+- [3] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing".
+- [4] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [5] 3GPP TS 25.113: "Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [6] 3GPP TS 36.113: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [7] IEC 61000-6-1: 2016: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity standard for residential, commercial and light-industrial environments".
+- [8] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for residential, commercial and light-industrial environments".
+- [9] Void.
+- [10] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing".
+- [11] IEC 61000-3-2: 2014: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current  $\leq 16$  A per phase)".
+- [12] IEC 61000-3-3: 2013: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems, for equipment with rated current  $\leq 16$  A per phase and not subject to conditional connection".
+- [13] IEC 61000-3-11: 2017 "Electromagnetic compatibility (EMC) - Part 3-11: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems - Equipment with rated current  $\leq 75$  A and subject to conditional connection".
+- [14] IEC 61000-3-12: 2011: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage systems with input current  $>16$  A and  $\leq 75$  A per phase".
+- [15] IEC 61000-4-2: 2008: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test".
+- [16] IEC 61000-4-3: 2006+AMD1:2007+AMD2:2010: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test".
+- [17] IEC 61000-4-4: 2012: "Electromagnetic compatibility (EMC) – Part 4-4: Testing and measurement techniques – Electrical fast transient/burst immunity test".
+- [18] IEC 61000-4-5: 2014+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test".
+- [19] IEC 61000-4-6: 2013: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio-frequency fields".
+
+- [20] IEC 61000-4-11: 2004+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests".
+- [21] ETSI EN 301 489-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements".
+- [22] Void
+- [23] Void
+- [24] ITU-R SM.329-10: "Unwanted emissions in the spurious domain".
+- [25] ETSI EN 301 489-50, v2.1.0: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for Cellular Communication Base Station (BS), repeater and ancillary equipment; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU".
+- [26] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [27] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [28] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [29] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements".
+- [30] 3GPP TS 38.113: "NR; Base Station (BS) ElectroMagnetic Compatibility (EMC)".
+- [31] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
+- [32] Void
+- [33] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception".
+- [34] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements".
+- [35] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 37.113 [4] 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] or TS 37.113 [4].
+
+NOTE: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are printed in their entirety.
+
+**active antenna system base station:** BS system which combines an *antenna array* with a transceiver unit array and a *radio distribution network*.
+
+**antenna array:** group of radiating elements characterized by the geometry and the properties of the *array elements*.
+
+**antenna port:** RF interface at the *transceiver array boundary*, specifically the *TAB connectors*.
+
+**BS type 1-H:** NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB.
+
+**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB.
+
+**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set*.
+
+**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)*, including any of UTRA, E-UTRA and/or NR operation as single RAT or multi-RAT based on TS 37.104 [33] (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier.
+
+**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band.
+
+**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+**OTA AAS BS:** AAS BS which has  $\geq 8$  *transceiver units* for E-UTRA or MSR and  $\geq 4$  *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*.
+
+**OTA requirements set:** complete set of OTA requirements applied to an OTA AAS BS.
+
+**port:** particular interface of EUT used for EMC requirements testing purposes.
+
+NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port.
+
+EXAMPLE 1: Examples of ports for *hybrid AAS BS* are as presented in figure 3.1-1:
+
+![Diagram of a hybrid AAS BS showing various ports.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port".
+
+Diagram of a hybrid AAS BS showing various ports.
+
+**Figure 3.1-1: Examples of ports for *hybrid AAS BS***
+
+EXAMPLE 2: Examples of ports for OTA AAS BS (i.e. with no antenna ports) are as presented in figure 3.1-2:
+
+![Diagram of an OTA AAS BS showing various ports, with no antenna port.](2a0f333f04f8e672bebf288c511c1db5_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" inside a larger outer box. Above the outer box is the label "Enclosure Port". To the left of the outer box, three lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". To the right of the outer box, two lines extend from the "Apparatus" box to the outer box, labeled from top to bottom: "Signal/control port" and "Telecommunication port". There is no "Antenna port" shown on the right side.
+
+Diagram of an OTA AAS BS showing various ports, with no antenna port.
+
+**Figure 3.1-2: Examples of ports for OTA AAS BS**
+
+**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply.
+
+**radio distribution network:** linear passive network which distributes the RF power generated by the transceiver unit array to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the transceiver unit array.
+
+NOTE: In the case when the active transceiver units are physically integrated with the *array elements* of the *antenna array*, the *radio distribution network* is a one-to-one mapping.
+
+**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation.
+
+**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the operating band (see manufacturer's declaration D6.12 in TS 37.145-1 [3] and/or D9.25 in TS 37.145-2 [10]).
+
+**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *OTA AAS BS* (i.e. half sphere around the EUT's radiating direction).
+
+**TAB connector:** *transceiver array boundary* connector.
+
+**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna.
+
+**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters.
+
+**telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks.
+
+NOTE: ETSI EN 301 489-1 [21] calls *telecommunication port* as the "wired network port".
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                                 |                                                                                                                                                   |
+|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| $BW_{\text{Channel}}$           | Channel bandwidth                                                                                                                                 |
+| $f_{\text{offset}}$             | Frequency offset used for discovering narrowband response for receivers                                                                           |
+| $F_{\text{UL\_high}}$           | The highest frequency of the uplink operating band                                                                                                |
+| $F_{\text{UL\_low}}$            | The lowest frequency of the uplink operating band                                                                                                 |
+| $\Delta f_{\text{OOB}}$         | Maximum offset of the out-of-band boundary from the uplink operating band edge                                                                    |
+| $\Delta f_{\text{R exclusion}}$ | Maximum offset of the Radiated Immunity exclusion band from the uplink operating band edge for test without <i>spatial exclusion zone</i> applied |
+
+## 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].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| AAS    | Active Antenna System                           |
+| AAS BS | AAS Base Station                                |
+| CSA    | Capability Set supported by the AAS BS          |
+| EMC    | ElectroMagnetic Compatibility                   |
+| EUT    | Equipment Under Test                            |
+| FR1    | Frequency Range 1                               |
+| MSR    | Multi-Standard Radio                            |
+| NB-IoT | Narrowband – Internet of Things                 |
+| NR     | New Radio                                       |
+| RCSA   | Radiated Capability Set supported by the AAS BS |
+
+|     |                             |
+|-----|-----------------------------|
+| RDN | Radio Distribution Network  |
+| RF  | Radio Frequency             |
+| RIB | Radiated Interface Boundary |
+| TAB | Transceiver Array Boundary  |
+
+# 4 Test conditions
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.145-1 [3], or TS 37.145-2 [10]. The test conditions shall be recorded in the test report.
+
+For an AAS BS supporting more than one RAT (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests shall be performed with RATs activated according to the test configurations in subclause 4.4. Tests shall be performed relating to each type of port and RIB, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test.
+
+For AAS BS supporting single RAT operation only (see D6.12 in TS 37.145-1 [3], or D9.25 in TS 37.145-2 [10]), tests relating to the *antenna port(s)* and RIBs shall be performed for each supported RAT.
+
+For AAS BS capable of multi-band operation (see D6.13 in TS 37.145-1 [3], or D9.15 in TS 37.145-2 [10]), the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the respective test configurations in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4], or TS 38.113 [30]. Tests shall be performed relating to each type of port and RIB, and all RATs per band shall be assessed during the tests.
+
+Requirements apply only for the declared operating band(s) (see manufacturer's declaration D6.1 in TS 37.145-1 [3], or D9.4 in TS 37.145-2 [10]), and corresponding Band Categories as per CSA (see D6.12 in TS 37.145-1 [3]) and/or RCSA capability sets (see D9.25 in TS 37.145-2 [10]).
+
+The manufacturer shall declare the supported capability set(s) according to TS 37.145-1 [3] and TS 37.145-2 [10]. Tests performed on an AAS BS according to a declared capability set(s) cover all single RAT and multi-RAT configurations included in the declared capability set. Exception can be made for immunity testing based on declaration DEMC.1, DEMC.2, DEMC.3, and DEMC.4 (see table 4.5-1), as detailed in annex A.
+
+NOTE 1: *TAB connector* capability sets (CSA) for *hybrid AAS BS* are defined in TS 37.145-1 [3] and declared in D6.12 declaration.
+
+NOTE 2: Radiated capability sets (RCSA) for *hybrid AAS BS* and OTA AAS BS are defined in TS 37.145-2 [10] and declared by D9.25 declaration.
+
+Where the *hybrid AAS BS* has multiple *TAB connectors* which are declared to be equivalent then it is sufficient to perform EMC tests on a single representative *TAB connector*. For the definition of the *TAB connector* equivalence declaration (D6.70), refer to TS 37.145-1 [3].
+
+EMC test shall not be performed with the AAS BS *antenna array* radiating, all *TAB connectors* shall be disconnected from the *radio distribution network* (RDN)/antenna array as specified in TS 37.105 [2] and terminated in an appropriate load impedance. For the description of the general AAS BS radio architecture and relations between the RDN/*antenna array* and the Transceiver Array Boundary, refer to TS 37.105 [2].
+
+Depending on RAT capability sets supported by the AAS BS, the following test conditions shall be referred and applied for the BS test configurations:
+
+- For AAS BS in *single RAT UTRA operation* the test conditions from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation* the test conditions from TS 36.113 [6] apply.
+- For AAS BS in single RAT NR operation the test conditions from TS 38.113 [30] apply.
+- For AAS BS in *MSR operation* the test conditions from TS 37.113 [4] apply.
+
+Whenever ports are considered for the emissions and immunity testing in the referred TS 25.113 [5], TS 36.113 [6] and TS 37.113 [4] specifications, special considerations shall be taken to test conditions specification for OTA AAS BS due to lack of *antenna ports*.
+
+NOTE 3: The receiver exclusion bands defined in E-UTRA and MSR specifications for Band 46 operation are not applicable for AAS BS, as the Band 46 operation is not supported by AAS BS.
+
+NOTE 4: The NB-IoT operation is not supported by AAS BS.
+
+## 4.1 Exclusion bands
+
+### 4.1.1 Transmitter exclusion band
+
+The *transmitter exclusion band* for BS is the frequency range over which no tests of radiated immunity of a transmitter are made. The *transmitter exclusion band* only applies to OTA AAS BS.
+
+The *transmitter exclusion band* is defined as:
+
+$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$
+
+Where:
+
+The value of  $\Delta f_{OBUE}$ ,  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* for NR, E-UTRA, UTRA in TS 37.105 [2].
+
+NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply.
+
+### 4.1.2 Receiver exclusion band
+
+An exclusion band is a band of frequencies over which no tests of radiated immunity are made.
+
+In case the *spatial exclusion* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is used during the EMC RI testing, the receiver exclusion band for OTA AAS BS is defined as:
+
+$$F_{UL,low} - \Delta f_{OOB} < f < F_{UL,high} + \Delta f_{OOB}$$
+
+Where:
+
+- Values of  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* in TS 37.104 [33].
+- The values of  $\Delta f_{OOB}$  are defined in table 4.1.2-1.
+
+**Table 4.1.2-1: Maximum  $\Delta f_{OOB}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>                             | $\Delta f_{OOB}$ (MHz) |
+|-------------------------------------------------------------------|------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$                   | 20                     |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low} \leq 900 \text{ MHz}$ | 60                     |
+
+In case the *spatial exclusion zone* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is not used during the EMC RI testing, the receiver exclusion band for OTA AAS BS and *BS type I-O* is defined as:
+
+$$F_{UL,low} - \Delta f_{RIexclusion} < f < F_{UL,high} + \Delta f_{RIexclusion}$$
+
+Where the values of  $\Delta f_{RIexclusion}$  are defined in table 4.1.2-2.
+
+**Table 4.1.2-2: Maximum  $\Delta f_{RIexclusion}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>           | $\Delta f_{RIexclusion}$ (MHz) |
+|-------------------------------------------------|--------------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 60                             |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low}$    | 200                            |
+
+For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by AAS BS.
+
+NOTE 1: The receiver exclusion bands do not apply for SDL bands.
+
+NOTE 2: Void
+
+## 4.2 Arrangements for establishing a communication link
+
+Depending on RAT capability sets supported by the AAS BS, the following arrangements for establishing a communication link shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the arrangements for establishing a communication link from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the arrangements for establishing a communication link from TS 36.113 [6] apply.
+- For AAS BS in MSR operation, the arrangements for establishing a communication link from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for establishing a communication link from TS 38.113 [30] apply.
+
+## 4.3 Narrow band responses on receivers
+
+Depending on RAT capability sets supported by the AAS BS, the following narrow band responses on receivers shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the narrow band responses on receivers from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the narrow band responses on receivers from TS 36.113 [6] apply.
+- For AAS BS in MSR operation the arrangements for narrow band responses on receivers from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for narrow band responses on receivers from TS 38.113 [30] apply.
+
+## 4.4 BS test configurations
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- AAS BS for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3]. In this case, the EMC test configuration are listed in tables 4.4-1, 4.4-3, 4.4-5, 4.4-7, 4.4-9, 4.4-11 respectively.
+- AAS BS for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10]. In this case, the EMC test configuration are listed in table 4.4-2, 4.4-4, 4.4-6, 4.4-8, 4.4-10, 4.4-12 respectively.
+
+The test configurations apply according to the declared RAT capability sets (i.e. CSA as declared in D6.12 in TS 37.145-1 [3], or RCSA as declared in D9.25 in TS 37.145-2 [10]) of the AAS BS and the Band Category of the declared operating band (i.e. BC1, BC2 or BC3).
+
+The AAS BS test configurations are defined as ATCx in TS 37.145-1 [3] and ATCRx in TS 37.145-2 [10], clause 4.11.
+
+- For AAS BS declared to be capable of contiguous operation only (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), the test configuration(s) in tables 4.4-1, 4.4-2 and 4.4-3, 4.4-4 denoted by a "C" shall be used for testing.
+- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacture's declaration D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used.
+
+- For AAS BS declared to be capable of contiguous and non-contiguous operation (see D6.14 in TS 37.145-1 [3], or D9.28 in TS 37.145-2 [10]), and where the parameters in the manufacturer's D6.15 in TS 37.145-1 [3] or D9.29 in TS 37.145-2 [10] are not identical for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing.
+
+For AAS BS where signals from supported RATs are processed in common active components (see DEMC.2 and DEMC.4 in table 4.5-1), it is sufficient to consider a reduced set of CSs for immunity testing, as described in Annex A.
+
+For immunity tests:
+
+- The communication link for the RAT(s) listed in the table shall be established according to subclause 4.2.
+- Tests for ports relating to the RAT(s) supported shall be performed according to subclause 4.1.
+
+**Table 4.4-1: Test configuration applicability to requirements and capability sets for TAB connectors supporting MSR operation**
+
+| TAB connector test case | UTRA + E-UTRA (CSA3)                                  |                                                       |          | E-UTRA + NR (CSA3A)                                 |                                                     |                                               | UTRA + E-UTRA + NR (CSA3B)                 |
+|-------------------------|-------------------------------------------------------|-------------------------------------------------------|----------|-----------------------------------------------------|-----------------------------------------------------|-----------------------------------------------|--------------------------------------------|
+|                         | BC1                                                   | BC2                                                   | BC3      | BC1                                                 | BC2                                                 | BC3                                           | BC1,BC2                                    |
+| Emission tests          | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3b | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC: ANTC6<br>C/NC: ATC6,<br>ANTC6 | C: ATC8<br>CNC: ANTC8<br>C/NC: ANTC8, ATC8 |
+| Immunity tests          | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3a<br>CNC:<br>ANTC3<br>C/NC:<br>ATC3a,<br>ANTC3 | C: ATC3b | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC:<br>ANTC6<br>C/NC:<br>ATC6,<br>ANTC6 | C: ATC6<br>CNC: ANTC6<br>C/NC: ATC6,<br>ANTC6 | C: ATC8<br>CNC: ANTC8<br>C/NC: ANTC8, ATC8 |
+
+**Table 4.4-2: Test configuration applicability to requirements and capability sets for AAS BS supporting MSR operation**
+
+| Test case      | UTRA + E-UTRA (RCSA 3)                                    |                                                           |     | E-UTRA + NR (RCSA 3A)                                   |                                                         |                                                   | UTRA + E-UTRA + NR (RCSA 3B)                   |
+|----------------|-----------------------------------------------------------|-----------------------------------------------------------|-----|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------|------------------------------------------------|
+|                | BC1                                                       | BC2                                                       | BC3 | BC1                                                     | BC2                                                     | BC3                                               | BC1,BC2                                        |
+| Emission tests | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | N/A | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC: ANTCR7<br>C/NC: ATCR7,<br>ANTCR7 | C: ATCR9<br>CNC: ANTCR9<br>C/NC: ATCR9, ANTCR9 |
+| Immunity tests | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | C: ATCR3a<br>CNC:<br>ANTCR3<br>C/NC:<br>ATCR3a,<br>ANTCR3 | N/A | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC:<br>ANTCR7<br>C/NC:<br>ATCR7,<br>ANTCR7 | C: ATCR7<br>CNC: ANTCR7<br>C/NC: ATCR7,<br>ANTCR7 | C: ATCR9<br>CNC: ANTCR9<br>C/NC: ATCR9, ANTCR9 |
+
+**Table 4.4-3: Test configuration applicability to requirements and capability sets for TAB connectors supporting one RAT only MSR operation**
+
+| Capability set          | UTRA (MC) capable BS (CSA1)                       |                                                   |          | E-UTRA (MC) capable BS (CSA2)                |                                              |                                                 |
+|-------------------------|---------------------------------------------------|---------------------------------------------------|----------|----------------------------------------------|----------------------------------------------|-------------------------------------------------|
+| TAB connector test case | BC1                                               | BC2                                               | BC3      | BC1                                          | BC2                                          | BC3                                             |
+| Emission tests          | C: ATC1a<br>CNC: ANTC1a<br>C/NC: ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2    |
+| Immunity tests          | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a<br>CNC: ANTC2<br>C/NC: ATC2a,<br>ANTC2 |
+
+**Table 4.4-4: Test configuration applicability to requirements and capability sets for operating bands supporting one RAT only MSR operation**
+
+| Capability set | UTRA (MC) capable BS (RCSA1)                                |                                                             |     | E-UTRA (MC) capable BS (RCSA2)                         |                                                        |                                                        |
+|----------------|-------------------------------------------------------------|-------------------------------------------------------------|-----|--------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|
+| Test case      | BC1                                                         | BC2                                                         | BC3 | BC1                                                    | BC2                                                    | BC3                                                    |
+| Emission tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+| Immunity tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+
+**Table 4.4-5: Test configurations for a TAB connector supporting single-RAT UTRA operation**
+
+| TAB connector test case | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C capable only | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC capable TAB connector (CSA4) C capable only |
+|-------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| Emission tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+| Immunity tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+
+**Table 4.4-6: Test configurations for an AAS BS supporting single-RAT UTRA operation**
+
+| Test case      | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C capable only | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC AAS BS operating band (RCSA4) C capable only |
+|----------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
+| Emission tests | ATC1a                                                                       | ANTC1                                                                                                   | ATC1a, ANTC1                                                                                            | N/A                                                                 |
+| Immunity tests | ATCR1a                                                                      | ANTCR1                                                                                                  | ATCR1a, ANTCR1                                                                                          | N/A                                                                 |
+
+**Table 4.4-7: Test configurations for a *TAB connector* supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| <i>TAB connector</i> test case | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C capable only | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with identical parameters (CNC) | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with different parameters (CNC) |
+|--------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
+| Emission tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+| Immunity tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+
+**Table 4.4-8: Test configurations for an AAS BS supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| Test case      | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C capable only | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with identical parameters | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with different parameters |
+|----------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| Emission tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+| Immunity tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+
+**Table 4.4-9: Test configuration for *multi-band TAB connectors* supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |       |
+|--------------------------------|----------------------------|-------|
+|                                | BC1/BC2                    | BC3   |
+| Emission tests                 | ATC5b                      | ATC5b |
+| Immunity tests                 | ATC5b                      | ATC5b |
+
+**Table 4.4-10: Test configuration for AAS BS operating bands containing beams with multi-band dependencies supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |        |
+|--------------------------------|----------------------------|--------|
+|                                | BC1/BC2                    | BC3    |
+| Emission tests                 | ATCR5b                     | ATCR5b |
+| Immunity tests                 | ATCR5b                     | ATCR5b |
+
+**Table 4.4-11: Test configuration for *multi-band TAB connectors* supporting Single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                 | UTRA TDD CSA4         | E-UTRA Test CSA5               |
+|--------------------------------|-------------------------------|-----------------------|--------------------------------|
+| Emission test                  | ATC1a/ANTC1 (note 1)<br>ATC5b | ATC1b (note 2), ATC5a | ATC2a/ANTC2 (note 3),<br>ATC5b |
+| Immunity test                  | ATC5b                         | ATC5a                 | ATC5b                          |
+
+NOTE 1: ATC1a and/or ANTC1 shall be applied in each supported operating band according to table 4.4-3a.  
+NOTE 2: ATC1b shall be applied in each supported operating band according to table 4.4-3a.  
+NOTE 3: ATC2 and/or ANTC2 shall be applied in each supported operating band according to table 4.4-4a.
+
+**Table 4.4-12: Test configuration for AAS BS operating bands with multi-band dependencies supporting single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                    | UTRA TDD CSA4 | E-UTRA Test CSA5                  |
+|--------------------------------|----------------------------------|---------------|-----------------------------------|
+| Emission test                  | ATCR1a/ANTCR1 (note 1)<br>ATCR5b | N/A           | ATCR2a/ANTCR2 (note 2),<br>ATCR5b |
+| Immunity test                  | ATCR5b                           | N/A           | ATCR5b                            |
+
+NOTE 1: ATCR1a and/or ANTCR1 shall be applied in each supported operating band according to table 4.4-3b.  
+NOTE 2: ATCR2 and/or ANTCR2 shall be applied in each supported operating band according to table 4.4-4b.
+
+## 4.5 Manufacturer declarations
+
+The following EMC-specific manufacturer's declarations listed in table 4.5-1 are required to be provided by the manufacturer for AAS BS requirements testing.
+
+NOTE: The below listed manufacturer's declarations are supplementary to declarations covered in TS 37.145-1 [3], and in TS 37.145-2 [10].
+
+**Table 4.5-1: EMC-specific manufacturer declarations**
+
+| Declaration identifier                           | Declaration                                         | Description                                                                                                                                                                                                                                                                                                               |
+|--------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DEMC.1<br>(NOTE)                                 | Ports intended to be used with cables less than 3 m | Declaration of any port(s) intended to be used with cables less than 3 m.                                                                                                                                                                                                                                                 |
+| DEMC.2                                           | Common and/or RAT-specific active RF components     | Declaration of common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS or other BS supporting more than one RAT.                                                                                                                                                           |
+| DEMC.3                                           | Common and/or band-specific active RF components    | Declaration of common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation.                                                                                                                                                                       |
+| DEMC.4<br>(NOTE)                                 | RAT dependencies for simplified immunity testing    | Declaration of RAT dependencies for simplified immunity testing. For the case where BS employs common active RF components (DEMC.2), declare RATs which are handled per operating band in common active components in the radio digital unit. Declared per supported operating band (in case supported by multiple RATs). |
+| NOTE: This manufacturer declaration is optional. |                                                     |                                                                                                                                                                                                                                                                                                                           |
+
+# 5 Performance assessment
+
+## 5.1 General
+
+The following information shall be recorded in or annexed to the test report:
+
+- the primary functions of the radio equipment to be tested during and after the EMC testing;
+- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment;
+- the method to be used to verify that a communications link is established and maintained;
+- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress;
+- the ancillary equipment to be combined with the radio equipment for testing (where applicable);
+- the information about ancillary equipment intended to be used with the radio equipment;
+- information about the common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS supporting more than one RAT; (see declaration DEMC.2);
+- information about the common and/or band-specific active RF components and other HW blocks for a communication link in AAS BS capable of multi-band operation; (see declaration DEMC.3);
+- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+A communication link used by more than one tested RAT or more than one tested operating band, shall be assessed on all tested RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance assessment the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+## 5.2 Assessment of performance in Downlink
+
+In the immunity tests, the output of the transmitter shall be connected (via port for hybrid AAS BS, or via RIB for OTA AAS BS) to test equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following:
+
+- BLER assessment in TS 25.102 [26] in case of UTRA TDD
+- BLER assessment in TS 25.101 [27] in case of UTRA FDD
+- Throughput assessment in TS 36.101 [28] in case of E-UTRA
+- Throughput assessment in TS 38.101-4 [34] in case of NR
+
+The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing.
+
+## 5.3 Assessment of performance in Uplink
+
+In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following:
+
+- The value of the throughput shall be monitored in case of E-UTRA or in case of NR
+- The value of the BLER shall be monitored in case of UTRA FDD or in case of UTRA TDD
+
+# --- 6 Performance criteria
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for UTRA TDD, UTRA FDD, E-UTRA, or NR. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report.
+
+Depending on RAT capability sets supported by the AAS BS, the following performance criteria for continuous or for transient phenomena shall be referred and applied:
+
+- For AAS BS in *single RAT UTRA operation*, the performance criteria from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the performance criteria from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the performance criteria from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the performance criteria from TS 38.113 [30] apply.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance criteria the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+Table 7.1-1: Emission requirements applicability
+
+| Phenomenon                       | Application                | Equipment test requirement                 | Reference subclause in the present document | Reference standard                              |
+|----------------------------------|----------------------------|--------------------------------------------|---------------------------------------------|-------------------------------------------------|
+|                                  |                            | BS equipment                               |                                             |                                                 |
+| Radiated emission                | Enclosure                  | applicable for <i>hybrid AAS BS</i> (Note) | 8.2.1                                       | ITU-R SM.329 [24]                               |
+| Conducted emission               | DC power input/output port | applicable                                 | 8.3                                         | CISPR 32 [29]                                   |
+| Conducted emission               | AC mains input/output port | applicable                                 | 8.4                                         | CISPR 32 [29]                                   |
+| Conducted emission               | Telecommunication port     | applicable                                 | 8.5                                         | CISPR 32 [29]                                   |
+| Harmonic current emissions       | AC mains input port        | applicable                                 | 8.6                                         | IEC 61000-3-2 [11]<br>or<br>IEC 61000-3-12 [14] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                                 | 8.7                                         | IEC 61000-3-3 [12]<br>or<br>IEC 61000-3-11 [13] |
+
+NOTE: The EMC radiated emissions requirements for the OTA AAS BS are covered by the RF radiated emissions requirement in TS 37.105 [2], conforming to the TS 37.145-2 [10].
+
+## 7.2 Immunity
+
+Table 7.2-1: Immunity requirements applicability
+
+| Phenomenon                               | Application                                                               | Equipment test requirement | Reference subclause in the present document | Reference standard  |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------------------------------|---------------------|
+|                                          |                                                                           | BS equipment               |                                             |                     |
+| RF electromagnetic field (80 – 6000 MHz) | Enclosure                                                                 | applicable                 | 9.2                                         | IEC 61000-4-3 [16]  |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | 9.3                                         | IEC 61000-4-2 [15]  |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.4                                         | IEC 61000-4-4 [17]  |
+| RF common mode 0.15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.5                                         | IEC 61000-4-6 [19]  |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | 9.6                                         | IEC 61000-4-11 [20] |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | 9.7                                         | IEC 61000-4-5 [18]  |
+
+# 8 Emission
+
+## 8.1 Test configurations
+
+This subclause defines the configurations for emission tests as follows:
+
+- The equipment shall be tested under normal test conditions as specified in the functional standards;
+
+- The test configuration shall be as close to normal intended use as possible;
+- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- The test conditions, test configuration and mode of operation shall be recorded in the test report;
+- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS without Radio Frequency (RF) input/output ports but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power;
+- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- The test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.2 Radiated emission from base station
+
+### 8.2.1 Radiated emission, hybrid AAS BS
+
+This test is applicable to *hybrid AAS BS*. This test shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+Depending on RAT capability sets supported by the *hybrid AAS BS*, the following radiated emission requirements apply:
+
+- For *hybrid AAS BS* in *single RAT UTRA operation*, the base stations radiated emission requirements from TS 25.113 [5] apply.
+- For *hybrid AAS BS* in *single RAT E-UTRA operation* the base stations radiated emission requirements from TS 36.113 [6] apply.
+- For *hybrid AAS BS* in *MSR operation*, the base stations radiated emission requirements from TS 37.113 [4] apply.
+- For *hybrid AAS BS* in *single RAT NR operation*, the *BS type I-H* radiated emission requirements from TS 38.113 [30] apply.
+
+### 8.2.2 Radiated emission, OTA AAS BS
+
+This test is applicable to OTA AAS BS. This test shall be performed on a representative configuration of the OTA AAS BS.
+
+For OTA AAS BS, the radiated emission requirement is covered by RF radiated spurious emission requirement in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10].
+
+- NOTE: As the EMC radiated emissions of the OTA AAS BS cannot be distinguished between the intended emissions (nor to any spurious emissions related to these intentional transmissions) a single radiated emissions requirement is used for the OTA AAS BS.
+
+## 8.3 Conducted emissions, DC power input/output port
+
+This test is applicable to equipment which may have DC cables longer than 3 m.
+
+If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.4.
+
+This test shall be performed on a representative configuration of the radio equipment.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the DC power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the DC power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the DC power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the DC power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.4 Conducted emissions, AC mains power input/output port
+
+This test is applicable to equipment powered by the AC mains.
+
+This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT.
+
+This test shall be performed on a representative configuration of the radio equipment.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the AC mains power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the AC mains power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.5 Harmonic current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [11] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [14] applies.
+
+## 8.6 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [12] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-11 [13] applies.
+
+## 8.7 Conducted emissions, telecommunication ports
+
+This test is applicable for radio equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment.
+
+The test method and limits shall be in accordance with CISPR 32 [29], as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# --- 9 Immunity
+
+## 9.1 Test configurations
+
+This subclause defines the configurations for immunity tests as follows:
+
+- The equipment shall be tested under normal test conditions as specified in the functional standards;
+- During test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link;
+- The test configuration shall be as close to normal intended use as possible;
+- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- The test conditions, test configuration and mode of operation shall be recorded in the test report;
+- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup capable to reduce the power to a level sufficient for establishing and maintaining the communication link;
+- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- Immunity tests on the entire AAS BS shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub interface (e.g. with an RNC/EPC simulator) and evaluating the BLER/throughput (see figures 9.1-1 and 9.1-2);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub interface. BLER/throughput evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the radio interface or S1/Iub interface. In case of looping is used care have to be taken that the BLER/throughput information doesn't change due to looping;
+- For AAS BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all tested RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each tested RAT and/or operating band
+
+![Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-1: Communication link set up for *hybrid AAS BS* immunity measurement**
+
+![Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.](d9c0a780cd22626253dab4aa41699e2f_img.jpg)
+
+Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement**
+
+## 9.2 RF electromagnetic field (80 MHz - 6000 MHz)
+
+### 9.2.1 RF electromagnetic field, hybrid AAS BS
+
+This test assesses the ability of radio equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. This test is applicable to *hybrid AAS BS* and shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+The test method and levels shall be in accordance with IEC 61000-4-3 [16] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. The use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+### 9.2.2 RF electromagnetic field, OTA AAS BS
+
+This test assesses the ability of radio equipment operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. The OTA AAS BS includes an antenna which is an intentional radiator and does not form part of the EMC enclosure, application of RF electromagnetic fields in these directions may damage the BS receivers unintentionally.
+
+In the operational range of angles of the OTA AAS BS antenna receivers are protected by the RF blocking requirements defined in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10] and are not part of the EMC RF electromagnetic field immunity requirement.
+
+In the range of angles except the operational range of angles of the OTA AAS BS antenna (i.e. except for the half sphere around the DUT radiating direction as depicted on figure 9.2.2-1) and for the frequency range above 690 MHz (according to ETSI EN 301 489-50 [25]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the OTA AAS BS, as depicted on figure 9.2.2-1.
+
+When no spatial exclusion is implemented the use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.
+
+**Figure 9.2.2-1 EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS (horizontal plane depicted) with the spatial exclusion zone applied**
+
+Depending on RAT capability sets supported by the OTA AAS BS, the following RF electromagnetic field requirements apply over the range of angles covered by the EMC RF electromagnetic field immunity requirement:
+
+- For OTA AAS BS in *single RAT UTRA operation*, the RF electromagnetic field immunity requirements from TS 25.113 [5] apply.
+- For OTA AAS BS in *single RAT E-UTRA operation*, the RF electromagnetic field immunity requirements from TS 36.113 [6] apply.
+- For OTA AAS BS in *MSR operation*, the RF electromagnetic field immunity requirements from TS 37.113 [4] apply.
+- For OTA AAS BS in *single RAT NR operation*, the *BS type I-O* requirements for the RF electromagnetic field immunity from TS 38.113 [30] apply.
+
+## 9.3 Electrostatic discharge
+
+This test assesses the ability of radio equipment to operate as intended in the event of an electrostatic discharge.
+
+The test shall be performed on a representative configuration of the radio equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-2 [15] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.4 Fast transients common mode
+
+The test shall be performed on AC mains power input ports.
+
+This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.5-1) that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-4 [17] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.5 RF common mode (0.15 MHz - 80 MHz)
+
+The test shall be performed on AC mains power input/output ports.
+
+This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares in DEMC.1 (see table 4.5-1) that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-6 [19] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [19].
+
+## 9.6 Voltage dips and interruptions
+
+These tests assess the ability of radio equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-11 [20] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.7 Surges, common and differential mode
+
+These tests assess the ability of radio equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+The tests shall be performed on AC mains power input ports.
+
+This test shall be additionally performed on telecommunication ports.
+
+These tests shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-5 [18] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# Annex A (normative): Simplified immunity testing
+
+## A.1 Applicability
+
+Simplified immunity testing applies, per operating band, only to the BS which satisfies both of the following conditions:
+
+- Radio unit employs common active RF components for supported RATs, as described in DEMC.2.
+- Radio digital unit employs common active components for supported RATs, as described in DEMC.4.
+
+NOTE: If the above condition is not met, all applicable test configurations in clause 4.4 apply for testing.
+
+## A.2 Capability Sets for simplified immunity testing
+
+The set of RATs which are considered sufficient for the immunity testing purposes depends on the BS hardware capabilities declared by the manufacturer in DEMC.4.
+
+The following RAT combinations were identified as candidates for the immunity testing reductions:
+
+- For AAS BS declared to support E-UTRA and UTRA, UTRA does not have to be configured.
+- For AAS BS declared to support NR and UTRA, UTRA does not have to be configured.
+
+The above RAT combinations were further translated into the Capability Sets in tables below.
+
+For single-band AAS BS, the sufficient CSs in tables A.2-1 and A.2-2 may be considered, instead of the CSs in tables 4.4-1 and 4.4-2, respectively.
+
+The test configurations (TCx) are associated to the sufficient CSs according to tables 4.4-1 and 4.4-2.
+
+Example: BS declared to support CS9 (corresponding to TC9) in table A.2-2, will be tested using TC8 (corresponding to CS8).
+
+**Table A.2-1: Declared and sufficient CSs for testing**
+
+| Declared Capability Set   | UTRA + E-UTRA (CSA3)          | E-UTRA + NR (CSA3A) | UTRA + E-UTRA + NR (CSA3B) |
+|---------------------------|-------------------------------|---------------------|----------------------------|
+| Sufficient CS for testing | E-UTRA (MC) capable BS (CSA2) | E-UTRA + NR (CSA3A) | E-UTRA + NR (CSA3A)        |
+
+**Table A.2-2: Declared and sufficient CSs for testing**
+
+| Declared Capability Set   | UTRA + E-UTRA (RCSA 3)         | E-UTRA + NR (RCSA 3A) | UTRA + E-UTRA + NR (RCSA 3B) |
+|---------------------------|--------------------------------|-----------------------|------------------------------|
+| Sufficient CS for testing | E-UTRA (MC) capable BS (RCSA2) | E-UTRA + NR (RCSA 3A) | E-UTRA + NR (RCSA 3A)        |
+
+For multi-band multi-RAT capable MSR BS, the rationale described above applies for each band.
+
+# Annex B (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                  |               |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------|---------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                  | New version   |
+| 2016-02        | RAN4#78 | R4-161123 |      |     |     | First version of TS                                                                              | 0.1.0         |
+| 2016-03        | RAN#71  | RP-160401 |      |     |     | Presented to RAN for approval.<br>Editorial corrections recommended by ETSI editHelp             | 1.0.0         |
+| 2016-03        | RP-71   |           |      |     |     | TR approved by RAN plenary                                                                       | 13.0.0        |
+| 2016/06        | RP-72   | RP-161142 | 0002 | 1   | F   | Clarification in EMC environmental conditions references                                         | 13.1.0        |
+| 2017/03        | RP-75   | RP-170586 | 0004 | -   | F   | CR to TS 37.114: Clarification of the EMC specification's scope                                  | 13.2.0        |
+| 2017-03        | RP-75   | -         | -    | -   | -   | Update to Rel-14 version (MCC)                                                                   | 14.0.0        |
+| 2017/06        | RP-76   | RP-171306 | 0009 |     | A   | CR to TS 37.114: Isolation of Band 46 and NB-IoT from the AAS BS specification                   | 14.1.0        |
+| 2017-12        | RAN#78  | RP-172599 | 0059 | 1   | B   | Big CR to TS 37.114: eAAS EMC specification, v15.0.0                                             | 15.0.0        |
+| 2018-03        | RAN#79  | RP-180282 | 0064 |     | F   | CR to TS37.114                                                                                   | 15.1.0        |
+| 2018-06        | RAN#80  | RP-181075 | 0067 | 1   | B   | CR to TS 37.114: NR introduction into AAS EMC specification                                      | 15.2.0        |
+| 2018-12        | RAN#82  | RP-182362 | 0071 | 2   | B   | CR to TS 37.114: Clarification on Exclusion Bands for Radiated Immunity Test in FR2              | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0073 | 1   | F   | CR to TS 37.114: additional inputs for introduction of NR to the AAS EMC specification           | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0074 |     | F   | CR to TS 37.114: RAT-specific AAS BS operation terminology corrections                           | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0075 | 1   | B   | CR to TS 37.114: Consideration of the narrowband responses and communication link                | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0076 |     | F   | CR to TS 37.114: clarification on CSA and RCSA capability sets                                   | 15.3.0        |
+| 2019-03        | RAN#83  | RP-190401 | 0077 | 1   | B   | Draft CR to TS 37.114 Exclusion Bands for Radiated                                               | 15.4.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0078 | 1   | F   | CR to TS 37.114: Updates for Rx exclusion zone size and terminology for EMC RI testing purposes  | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0080 | 1   | F   | CR to TS 37.114 subclause 4.2                                                                    | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0084 |     | F   | CR to 37.114 Subsections index in Section 4.1                                                    | 15.5.0        |
+| 2019-09        | RAN#85  | RP-192019 | 0085 |     | F   | CR to TS 37.114 Correction on CISPR 16-1-1 for DC conducted Emission(clause 2 and subclause 7.1) | 15.6.0        |
+| 2019-09        | RAN#85  | RP-192053 | 0087 | 1   | F   | CR to 37.114 Editorial Corrections                                                               | 15.6.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0093 |     | F   | CR to TS 37.114 Correction on definitions subclause 3.1                                          | 15.7.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0094 |     | F   | CR to TS 37.114 Correction on notes in subclause 7.1                                             | 15.7.0        |
+| 2020-03        | RAN#87  | RP-200393 | 0095 | 1   | F   | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1)                     | 15.8.0        |
+| 2020-06        | RAN#88  | RP-201005 | 0096 |     | F   | CR to TS 37.114: internal TR reference corrections, Rel-15                                       | 15.9.0        |
+| 2020-06        | RAN#88  | RP-200984 | 0097 | 1   | F   | [R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2)      | 15.9.0        |
+| 2020-06        | RAN#88  | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                                   | <b>16.0.0</b> |
+
+| Change history |         |           |      |     |     |                                                                |             |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                | New version |
+| 2022-03        | SA#95   |           |      |     |     | Update to Rel-17 version (MCC)                                 | 17.0.0      |
+| 2023-03        | RAN#99  | RP-230502 | 0100 |     | F   | CR to TS 37.114 AAS BS test configuration R15                  | 17.1.0      |
+| 2023-03        | RAN#99  | RP-230505 | 0106 |     | F   | TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity | 17.1.0      |
+
+| Change history |         |           |      |     |     |                                                                                                                   |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                   | New version |
+| 2023-12        | RAN#102 | RP-233360 | 0108 | 1   | F   | [AAS_BS_LTE_UTRA-Core, TE118] CR to TS 37.114: framework for the EMC-specific manufacturer's declarations, Rel-18 | 18.0.0      |
+| 2023-12        | RAN#102 | RP-233364 | 0109 | 1   | B   | CR to TS 37.114: Implementation of AAS BS testing simplifications, Rel-18                                         | 18.0.0      |

gsma/37_series/37480/raw.md

@@ -0,0 +1,431 @@
+
+
+# 3GPP TS 37.480 V18.0.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E1 general aspects and principles (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                              |           |
+|--------------------------------------------------------------|-----------|
+| Foreword .....                                               | 4         |
+| 1 Scope.....                                                 | 5         |
+| 2 References.....                                            | 5         |
+| 3 Definitions and abbreviations .....                        | 5         |
+| 3.1 Definitions.....                                         | 5         |
+| 3.2 Abbreviations .....                                      | 6         |
+| 4 General aspects .....                                      | 6         |
+| 4.1 E1 interface general principles.....                     | 6         |
+| 4.2 E1 interface specification objectives.....               | 7         |
+| 5 Functions of the E1 interface .....                        | 7         |
+| 5.1 General .....                                            | 7         |
+| 5.1.1 E1 interface management function.....                  | 7         |
+| 5.1.2 E1 bearer context management function .....            | 7         |
+| 5.1.3 Trace function.....                                    | 8         |
+| 5.1.4 Load management function .....                         | 8         |
+| 5.1.5 Measurement results transfer function .....            | 8         |
+| 5.1.6 Support for IAB .....                                  | 8         |
+| 5.1.7 E1 bearer context management function for NR MBS.....  | 9         |
+| 5.2 TEIDs allocation .....                                   | 9         |
+| 6 Procedures of the E1 interface .....                       | 9         |
+| 6.1 Interface Management procedures .....                    | 9         |
+| 6.2 Bearer Context Management procedures .....               | 9         |
+| 6.3 UE Tracing procedures.....                               | 10        |
+| 6.4 Load management procedures.....                          | 10        |
+| 6.5 Measurement results transfer procedures.....             | 10        |
+| 6.6 IAB procedures .....                                     | 10        |
+| 6.7 NR MBS procedures .....                                  | 10        |
+| 7 E1 interface protocol structure.....                       | 11        |
+| 8 Other E1 interface specifications .....                    | 11        |
+| 8.1 E1 interface: layer 1 (3GPP TS 37.481).....              | 11        |
+| 8.2 E1 interface: signalling transport (3GPP TS 37.482)..... | 11        |
+| 8.3 E1 interface: E1AP specification (3GPP TS 37.483).....   | 12        |
+| <b>Annex A (informative): Change history.....</b>            | <b>13</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document is an introduction to the 3GPP TS 37.48x series of technical specifications that define the E1 interface. The E1 interface provides means for interconnecting a gNB-CU-CP and a gNB-CU-UP of a gNB-CU within an NG-RAN, or for interconnecting a gNB-CU-CP and a gNB-CU-UP of an en-gNB within an E-UTRAN, or for interconnecting an eNB-CP and an eNB-UP of an eNB within an E-UTRAN, or for interconnecting an ng-eNB-CU-CP and an ng-eNB-CU-UP of an ng-eNB-CU within an NG-RAN.
+
+# 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 TS 38.401: "NG-RAN; Architecture Description".
+- [3] 3GPP TS 37.481: "E1 layer 1".
+- [4] 3GPP TS 37.482: "E1 signalling transport".
+- [5] 3GPP TS 37.483: "E1 Application Protocol (E1AP)".
+- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+- [7] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
+- [8] 3GPP TS 37.470: "W1 interface; General aspects and principles".
+- [9] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description".
+- [10] 3GPP TS 23.247: "5G multicast-broadcast services; Stage 2".
+
+# 3 Definitions and abbreviations
+
+## 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].
+
+**eNB-CP:** as defined in TS 36.401 [9].
+
+**eNB-UP:** as defined in TS 36.401 [9].
+
+**en-gNB:** as defined in TS 37.340 [7].
+
+**gNB-CU:** as defined in TS 38.401 [2].
+
+**gNB-CU-CP:** as defined in TS 38.401 [2].
+
+**gNB-CU-UP:** as defined in TS 38.401 [2].
+
+**gNB-DU:** as defined in TS 38.401 [2].
+
+**gNB:** as defined in TS 38.300 [6].
+
+**IAB:** as defined in TS 38.300 [6].
+
+**ng-eNB-CU:** as defined in TS 37.470 [8].
+
+**ng-eNB-CU-CP:** as defined in TS 38.401 [2].
+
+**ng-eNB-CU-UP:** as defined in TS 38.401 [2].
+
+**ng-eNB-DU:** as defined in TS 37.470 [8].
+
+## 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].
+
+|        |                                           |
+|--------|-------------------------------------------|
+| DL     | Downlink                                  |
+| DRB    | Data Radio Bearer                         |
+| E1AP   | E1 Application Protocol                   |
+| IP     | Internet Protocol                         |
+| MBS    | Multicast/Broadcast Service               |
+| MT-SDT | Mobile Terminated Small Data Transmission |
+| PTP    | Point to Point                            |
+| PTM    | Point to Multipoint                       |
+| SCTP   | Stream Control Transmission Protocol      |
+| TNL    | Transport Network Layer                   |
+
+# --- 4 General aspects
+
+This clause captures the E1 interface principles and characteristics.
+
+**Note:** The principles, functions and procedures specified in this specification also apply to the case where E1AP is used between an ng-eNB-CU-CP and an ng-eNB-CU-UP or between an eNB-CP and an eNB-UP, unless stated otherwise.
+
+## 4.1 E1 interface general principles
+
+The general principles for the specification of the E1 interface are as follows:
+
+- the E1 interface is open;
+- the E1 interface supports the exchange of signalling information between the endpoints;
+- from a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP, or between an ng-eNB-CU-CP and an ng-eNB-CU-UP, or between an eNB-CP and an eNB-UP.
+
+**NOTE 1:** A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints.
+
+- the E1 interface separates Radio Network Layer and Transport Network Layer;
+- the E1 interface enables exchange of UE associated information and non-UE associated information;
+- the E1 interface is future proof to fulfil different new requirements, support of new services and new functions.
+
+## 4.2 E1 interface specification objectives
+
+The E1 interface specifications facilitate the following:
+
+- inter-connection of a gNB-CU-CP and a gNB-CU-UP supplied by different manufacturers.
+- inter-connection of an ng-eNB-CU-CP and an ng-eNB-CU-UP supplied by different manufacturers.
+- inter-connection of an eNB-CP and an eNB-UP supplied by different manufacturers.
+
+# --- 5 Functions of the E1 interface
+
+## 5.1 General
+
+The following clauses describe the functions supported over E1.
+
+### 5.1.1 E1 interface management function
+
+The error indication function is used by the gNB-CU-UP or gNB-CU-CP to indicate to the gNB-CU-CP or gNB-CU-UP that an error has occurred.
+
+The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-CU-UP and the gNB-CU-CP.
+
+The E1 setup function allows to exchange application level data needed for the gNB-CU-UP and gNB-CU-CP to interoperate correctly on the E1 interface. The E1 setup is initiated by both the gNB-CU-UP and gNB-CU-CP.
+
+The gNB-CU-UP Configuration Update and gNB-CU-CP Configuration Update functions allow to update application level configuration data needed between the gNB-CU-CP and the gNB-CU-UP to interoperate correctly over the E1 interface.
+
+The E1 setup and gNB-CU-UP Configuration Update functions allow to inform NR CGI(s), ECGI(s), S-NSSAI(s), PLMN-ID(s), QoS information and NID(s) supported by the gNB-CU-UP.
+
+The E1 setup and gNB-CU-UP Configuration Update functions allow the gNB-CU-UP to signal its capacity information to the gNB-CU-CP.
+
+The E1 gNB-CU-UP Status Indication function allows to inform the overloaded or non-overloaded status over the E1 interface.
+
+### 5.1.2 E1 bearer context management function
+
+The establishment of the E1 bearer context is initiated by the gNB-CU-CP and accepted or rejected by the gNB-CU-UP based on admission control criteria (e.g., resource not available).
+
+The modification of the E1 bearer context can be initiated by either gNB-CU-CP or gNB-CU-UP. The receiving node can accept or indicate failure to carry out the modification request. The E1 bearer context management function also supports the release of the bearer context previously established in the gNB-CU-UP. The release of the bearer context is triggered by the gNB-CU-CP either directly or following a request received from the gNB-CU-UP.
+
+This function is used to setup and modify the QoS-flow to DRB mapping configuration. The gNB-CU-CP decides flow-to-DRB mapping and provides the generated SDAP and PDCP configuration to the gNB-CU-UP. The gNB-CU-CP also decides the Reflective QoS flow to DRB mapping. The function is also used to send to the gNB-CU-UP the alternative QoS Parameters Sets when available for a QoS flow. For each PDU Session Resource to be setup or modified, the S-NSSAI, shall be provided in the E1 bearer context setup procedure and may be provided in the E1 bearer context modification procedure by gNB-CU-CP to the gNB-CU-UP.
+
+This function is also used to setup and modify the EPS bearer/E-RAB to DRB mapping configuration for the case of eNB-CP and eNB-UP separation. The eNB-CP decides EPS bearer/E-RAB-to-DRB mapping and provides the E-UTRAN/NR PDCP configuration to the eNB-UP.
+
+This function is also used for the gNB-CU-UP to report the MT-SDT data size to the gNB-CU-CP.
+
+This function is used for the gNB-CU-CP to send the security information to the gNB-CU-UP.
+
+This function is used for the gNB-CU-CP to send to the gNB-CU-UP transport layer information to be used for data forwarding e.g., during handovers.
+
+This function is used for the gNB-CU-CP to send the parameters for header compression for certain traffic types e.g., IP, Ethernet to the gNB-CU-UP.
+
+This function is used for the gNB-CU-CP to send the uplink data compression parameters to the gNB-CU-UP for certain data radio bearer(s).
+
+This function is used for the gNB-CU-UP to notify the event of DL data arrival detection to the gNB-CU-CP. With this function, the gNB-CU-UP requests gNB-CU-CP to trigger paging procedure over F1 or Xn to support RRC Inactive state. RRC Inactive state is not supported when this function is used between an eNB-CP and an eNB-UP.
+
+This function is used for the gNB-CU-UP to notify the gNB-CU-CP that a DL packet including a QFI value not configured by the gNB-CU-CP or an UL packet including a QFI value in the SDAP header of the default DRB not configured by the gNB-CU-CP is received for the first time. The gNB-CU-CP can take further action if needed.
+
+This function is used for the gNB-CU-UP to notify the gNB-CU-CP during the SDT procedure that the received DL SDT data crossed the data size threshold. The gNB-CU-CP can take further action if needed.
+
+This function is used for the gNB-CU-UP to notify the event of user inactivity to the gNB-CU-CP. With this function, the gNB-CU-UP indicates that the inactivity timer associated with a bearer, a PDU session or a UE expires, or that user data is received for the bearer, the PDU session or the UE whose inactivity timer has expired. The gNB-CU-CP consolidates all the serving gNB-CU-UPs for the UE and takes further action.
+
+This function is used for the gNB-CU-UP to report data volume to the gNB-CU-CP.
+
+This function is used for the gNB-CU-CP to notify the suspension and resumption of bearer contexts to the gNB-CU-UP. Suspension and resumption of bearer contexts are not applicable to eNB-CP/eNB-UP and ng-eNB-CU-CP/ng-eNB-CU-UP.
+
+This function also allows to support CA based packet duplication as described in TS 38.300 [6], i.e. one data radio bearer should be configured with at least two GTP-U tunnels between gNB-CU-UP and a gNB-DU.
+
+This function is used to support the enhanced mobility operations as described in TS 38.300 [6] in the gNB-CU-UP.
+
+### 5.1.3 Trace function
+
+The Trace function provides means to control trace sessions for a UE over E1 interface.
+
+### 5.1.4 Load management function
+
+The load management function allows an gNB-CU-CP to request the reporting of load measurements to gNB-DU and is used by gNB-CU-UP to report the result of measurements admitted by gNB-CU-UP.
+
+### 5.1.5 Measurement results transfer function
+
+The measurement results transfer is used by the gNB-CU-CP to transfer UE associated measurement results to the gNB-CU-UP.
+
+### 5.1.6 Support for IAB
+
+Note: IAB is an NR feature, and this function is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation.
+
+This function is used to update the DL/UL F1-U GTP-U tunnels for an IAB network, and allow the gNB-CU-CP to send the security key info to the gNB-CU-UP for the protection of the F1-U interface with IAB-DU.
+
+### 5.1.7 E1 bearer context management function for NR MBS
+
+The E1 bearer context management function for NR MBS consists of two sub-sets for functions, one for NR MBS broadcast, one for NR MBS multicast.
+
+Both sets follow the principles of the E1 bearer context management functions, with the following differences.
+
+- E1 NR MBS procedure concerns a single MBS Session Resource only.
+- E1 NR MBS procedures concern the control of MRB resources in gNB-CU-UP.
+- E1 NR MBS procedures do not control security information, as for NR MBS, PDCP does not apply security as specified in TS 38.300 [6].
+- QoS flow to MRB mapping is determined by the gNB-CU-CP or, in case of shared NR-U terminations, the gNB-CU-UP may be notified about the QoS flow to MRB mapping already determined in the bearer context for the shared NR-U termination. The gNB-CU-CP may inform the gNB-CU-UP whether it is contended with the already determined mapping decision.
+
+NOTE: Not all QoS flow parameters are applicable for NR MBS, as specified in TS 23.247 [10].
+
+- Data volume reporting is not applicable for NR MBS.
+- CA based packet duplication is not applicable for NR MBS.
+
+## 5.2 TEIDs allocation
+
+The gNB-CU-UP is responsible for the allocation of the F1-U UL GTP TEID for each data radio bearer.
+
+The gNB-CU-UP is responsible for the allocation of the S1-U DL GTP TEID for each E-RAB and the NG-U DL GTP TEID for each PDU Session.
+
+The gNB-CU-UP is responsible for the allocation of the X2-U DL/UL GTP TEID or the Xn-U DL/UL GTP TEID for each data radio bearer.
+
+# --- 6 Procedures of the E1 interface
+
+## 6.1 Interface Management procedures
+
+The E1 interface management procedures are listed below:
+
+- Reset procedure
+- Error Indication procedure
+- gNB-CU-UP E1 Setup procedure
+- gNB-CU-CP E1 Setup procedure
+- gNB-CU-UP Configuration Update procedure
+- gNB-CU-CP Configuration Update procedure
+- E1 Release procedure
+- gNB-CU-UP Status Indication procedure
+
+## 6.2 Bearer Context Management procedures
+
+The E1 bearer management procedures are listed below:
+
+- Bearer Context Setup procedure
+- Bearer Context Release Request (gNB-CU-UP initiated) procedure
+- Bearer Context Release (gNB-CU-CP initiated) procedure
+- Bearer Context Modification (gNB-CU-CP initiated) procedure
+- Bearer Context Modification Required (gNB-CU-UP initiated) procedure
+- DL Data Notification procedure
+- Bearer Context Inactivity Notification procedure
+- Data Usage Report procedure
+- MR-DC Data Usage Report procedure
+
+## 6.3 UE Tracing procedures
+
+The following procedures are used to trace the UE:
+
+- Trace Start procedure
+- Deactivate Trace procedure
+- Cell Traffic Trace procedure
+
+## 6.4 Load management procedures
+
+The load management procedures are listed as below:
+
+- Resource Status Reporting Initiation procedure
+- Resource Status Reporting procedure
+
+## 6.5 Measurement results transfer procedures
+
+The measurement results transfer procedures are listed as below:
+
+- gNB-CU-CP Measurement Results Information
+
+## 6.6 IAB procedures
+
+Note: IAB is an NR feature, and this procedure is not applicable to eNB CP-UP separation and ng-eNB CP-UP separation.
+
+The IAB procedures are listed as below:
+
+- IAB UP TNL Address Update procedure
+- IAB PSK Notification procedure
+
+## 6.7 NR MBS procedures
+
+The E1 MBS procedures are listed below:
+
+- Broadcast E1AP MBS procedures
+- BC Bearer Context Setup
+
+- BC Bearer Context Modification (gNB-CU-CP initiated)
+- BC Bearer Context Modification (gNB-CU-UP initiated)
+- BC Bearer Context Release (gNB-CU-CP initiated)
+- BC Bearer Context Release (gNB-CU-UP initiated)
+- Multicast E1AP MBS procedures
+  - MC Bearer Context Setup
+  - MC Bearer Context Modification (gNB-CU-CP initiated)
+  - MC Bearer Context Modification (gNB-CU-UP initiated)
+  - MC Bearer Context Release (gNB-CU-CP initiated)
+  - MC Bearer Context Release (gNB-CU-UP initiated)
+  - MC Bearer Notification
+
+# 7 E1 interface protocol structure
+
+Figure 7.1-1 shows the protocol structure for E1. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as E1AP (E1 Application Protocol).
+
+![Diagram of E1 interface protocol structure showing Control Plane and User Plane layers.](5e92d9e8e9ce204e405bff2367f88176_img.jpg)
+
+The diagram illustrates the protocol stack for the E1 interface. It is divided into two main sections: the Control Plane and the User Plane. The Control Plane contains the E1-AP (E1 Application Protocol) block. The User Plane consists of a stack of four layers: SCTP (Stream Control Transmission Protocol), IP (Internet Protocol), Data link layer, and Physical layer. The E1-AP block is connected to the SCTP block via a horizontal line with an oval symbol, representing a protocol data unit (PDU) or a connection point. The SCTP block is part of the Transport Network Layer, which also includes the IP, Data link layer, and Physical layer blocks. The Radio Network Layer is shown above the E1-AP block, indicating its position in the overall network architecture.
+
+Diagram of E1 interface protocol structure showing Control Plane and User Plane layers.
+
+Figure 7.1-1: Interface protocol structure for E1
+
+# 8 Other E1 interface specifications
+
+This clause contains the description of the other related 3GPP specifications.
+
+## 8.1 E1 interface: layer 1 (3GPP TS 37.481)
+
+3GPP TS 37.481 [3] specifies the physical layer technologies that may be used to support the E1 interface.
+
+## 8.2 E1 interface: signalling transport (3GPP TS 37.482)
+
+3GPP TS 37.482 [4] specifies the signalling bearers for the E1AP for the E1 interface.
+
+## 8.3 E1 interface: E1AP specification (3GPP TS 37.483)
+
+3GPP TS 37.483 [5] specifies the E1AP protocol for radio network control plane signalling over the E1 interface.
+
+# Annex A (informative): Change history
+
+| Change history |             |           |      |     |     |                                                                                                                                                                                            |             |
+|----------------|-------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting     | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                            | New version |
+| 2022-01        | R3#114bis-e | R3-220846 |      |     |     | Text transferred from TS 38.460 v16.4.0 and references updated to 37.48x series                                                                                                            | 0.0.1       |
+| 2022-02        | R3#115-e    | R3-221646 |      |     |     | Changes from Rel-17 WI "LTE_NR_arch_evo_enh-Core" incorporated and change history updated.                                                                                                 | 0.1.0       |
+| 2022-03        | R3#115-e    | R3-222579 |      |     |     | Agreements from Rel-17 WI "LTE_NR_arch_evo_enh-Core" at RAN3#115-e incorporated.                                                                                                           | 0.1.1       |
+| 2022-03        | R3#115-e    | R3-222973 |      |     |     | Change history updated                                                                                                                                                                     | 0.2.0       |
+| 2022-03        | RAN#95-e    | RP-220795 |      |     |     | Version submitted for approval in RAN#95-e                                                                                                                                                 | 1.0.0       |
+| 2022-03        | RAN#95-e    | R3-220848 |      |     |     | Agreed Rel-16/17 CRs from other WIs are merged.<br>Including REL-16 38.460 changes of R3-221224 of RP-220276, and REL-17 38.460 changes of R3-222614 of RP-220234, R3-222929 of RP-220224. | 1.1.0       |
+| 2022-03        | SA#95-e     |           |      |     |     | Promotion to Release 17 without technical change                                                                                                                                           | 17.0.0      |
+| 2022-06        | RAN#96      | RP-221145 | 0001 | -   | D   | E1 TS 37.480 Editorial corrections                                                                                                                                                         | 17.1.0      |
+| 2022-06        | RAN#96      | RP-221134 | 0002 | -   | F   | Corrections on E1 bearer context management function for NR MBS                                                                                                                            | 17.1.0      |
+| 2023-12        | RAN#102     | RP-233849 | 0005 | 2   | F   | Correction on Temp no data and DL data arrival for Activate Multicast Session                                                                                                              | 17.2.0      |
+| 2023-12        | RAN#102     | RP-233820 | 0003 | 5   | B   | Introduction on MT-SDT                                                                                                                                                                     | 18.0.0      |

gsma/37_series/37877/raw.md

@@ -0,0 +1,329 @@
+
+
+# 3GPP TR 37.877 V18.0.0 (2023-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching; (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                      |           |
+|------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                       | 4         |
+| 1 Scope.....                                                                                         | 6         |
+| 2 References.....                                                                                    | 6         |
+| 3 Definitions of terms, symbols and abbreviations.....                                               | 6         |
+| 3.1 Terms.....                                                                                       | 6         |
+| 3.2 Symbols.....                                                                                     | 6         |
+| 3.3 Abbreviations .....                                                                              | 6         |
+| 4 Background .....                                                                                   | 7         |
+| 4.1 TR Maintenance .....                                                                             | 7         |
+| 5 Specific Band Combinations.....                                                                    | 7         |
+| 5.1 NR band combinations.....                                                                        | 7         |
+| 5.1.1 CA_n1-n5-n78.....                                                                              | 7         |
+| 5.1.1.1 Configurations .....                                                                         | 7         |
+| 5.1.1.2 Technical analysis.....                                                                      | 7         |
+| 5.1.1.3 Conclusion .....                                                                             | 7         |
+| 5.1.2 CA_n3-n5-n78.....                                                                              | 8         |
+| 5.1.2.1 Configurations .....                                                                         | 8         |
+| 5.1.2.2 Technical analysis.....                                                                      | 8         |
+| 5.1.2.3 Conclusion .....                                                                             | 8         |
+| 6 Release Independent Requirements .....                                                             | 8         |
+| 6.1 Inter-band CA.....                                                                               | 8         |
+| 6.2 Inter-band EN-DC .....                                                                           | 9         |
+| <b>Annex A (informative): Common UE RF requirements .....</b>                                        | <b>9</b>  |
+| A.1 Common UE RF requirements for Inter-band EN-DC with tx switching.....                            | 9         |
+| A.2 Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1 ..... | 10        |
+| <b>Annex B (informative): Change history .....</b>                                                   | <b>11</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document is a technical report for WI “Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink” under Rel-18 time frame. The purpose is to gather the relevant background information and studies in order to address the band combinations requested for mandating no DL interruption to conduct dynamic Tx switching in uplink listed in Table 1-1.
+
+**Table 1-1: Band combinations requested for mandating no DL interruption**
+
+| Configuration | Uplink configuration |
+|---------------|----------------------|
+| CA n1-n5-n78  | CA n1-n78, CA n5-n78 |
+| CA n3-n5-n78  | CA n3-n78, CA n5-n78 |
+
+# 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] TS38.101-1, NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone
+- [3] 3GPP TS 38.133: "NR; Requirements for support of radio resource management".
+- [4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios".
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 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].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+## 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].
+
+# 4 Background
+
+At 3GPP RAN#96 meeting, a new basket Work Item “Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink” was approved. The objectives are as following,
+
+For the core part:
+
+- Discuss and specify inter-band uplink CA and EN-DC combinations for which DL interruption is not allowed when dynamic switching between two uplink carriers is conducted.
+  - 1) Based on the requested band combinations from operators, analyze if it is feasible to specify no DL interruption in RAN4 specification.
+  - 2) Based on the feasibility analysis for specific combination, decide to introduce no DL interruption in RAN4 specification.
+
+For the performance part:
+
+- For 2CC 1Tx-2Tx switching, the mandating of no DL interruption for new band combinations is release independent from Rel-16.
+- For 3CC 1Tx-2Tx switching and 2CC or 3CC 2Tx-2Tx switching, the mandating of no DL interruption for new band combinations is release independent from Rel-17.
+
+The present document is the technical report for this basket Work Item.
+
+## 4.1 TR Maintenance
+
+A single company is responsible for introducing all approved TPs in the current TR, i.e. TR editor. However, it is the responsibility of the contact person of each band/band combination to ensure that the TPs related to the band/band combination have been implemented.
+
+# 5 Specific Band Combinations
+
+## 5.1 NR band combinations
+
+### 5.1.1 CA\_n1-n5-n78
+
+#### 5.1.1.1 Configurations
+
+**Table 5.1.1.1-1: CA configuration for mandating no DL interruption**
+
+| Configuration | Uplink configuration |
+|---------------|----------------------|
+| CA_n1-n5-n78  | CA_n1-n78, CA_n5-n78 |
+
+#### 5.1.1.2 Technical analysis
+
+For CA\_n1-n78 and CA\_n5-n78, no DL interruption allowed has been specified as mandated in 38101-1, which means switching from n1/n5 to n78 has no impact to n1/n5 downlink. Thus there is no DL interruption for CA\_n1-n5-n78 with CA\_n1-n78 or CA\_n5-n78 uplink configuration when conducting dynamic Tx switching.
+
+#### 5.1.1.3 Conclusion
+
+No DL interruption for CA\_n1-n5-n78 with CA\_n1-n78 or CA\_n5-n78 uplink configuration is mandated.
+
+**Table 5.1.1.3-1: Inter-band CA operating bands involving FR1 (three bands)**
+
+| NR CA Band                                                                                                                                  | NR Band<br>(Table 5.2-1) | DL interruption<br>allowed (Note 3) |
+|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------------------|
+| CA_n1-n5-n78                                                                                                                                | n1, n5, n78              | No for CA_n1-n78,<br>CA_n5-n78      |
+| NOTE 4: Applicable when dynamic Tx switching is conducted. The DL interruption requirement is specified in clause 8.2.2.2.10 of 38.133 [3]. |                          |                                     |
+
+### 5.1.2 CA\_n3-n5-n78
+
+#### 5.1.2.1 Configurations
+
+**Table 5.1.2.1-1: CA configuration for mandating no DL interruption**
+
+| Configuration | Uplink configuration |
+|---------------|----------------------|
+| CA_n3-n5-n78  | CA_n3-n78, CA_n5-n78 |
+
+#### 5.1.2.2 Technical analysis
+
+For CA\_n3-n78 and CA\_n5-n78, no DL interruption allowed has been specified as mandated in 38.101-1, which means switching from n3/n5 to n78 has no impact to n3/n5 downlink. Thus there is no DL interruption for CA\_n3-n5-n78 with CA\_n3-n78 or CA\_n5-n78 uplink configuration when conducting dynamic Tx switching.
+
+#### 5.1.2.3 Conclusion
+
+No DL interruption for CA\_n3-n5-n78 with CA\_n3-n78 or CA\_n5-n78 uplink configuration is mandated.
+
+**Table 5.1.2.3-1: Inter-band CA operating bands involving FR1 (three bands)**
+
+| NR CA Band                                                                                                                                  | NR Band<br>(Table 5.2-1) | DL interruption<br>allowed (Note 3) |
+|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------------------|
+| CA_n3-n5-n78                                                                                                                                | n3, n5, n78              | No for CA_n3-n78,<br>CA_n5-n78      |
+| NOTE 4: Applicable when dynamic Tx switching is conducted. The DL interruption requirement is specified in clause 8.2.2.2.10 of 38.133 [3]. |                          |                                     |
+
+# 6 Release Independent Requirements
+
+The mandating of no DL interruption requirement belongs to the feature of inter-band CA or EN-DC with tx switching. Thus to specify the release independent requirement shall involve the feature of tx switching. The specific requirements need to be fulfilled include downlink interruption requirement, mandating no DL interruption requirement and time mask requirements as specified in the 38.133 [3] and 38.101-1 [2]. Because RRM downlink interruption requirement is referred when specifying mandating no DL interruption in 38.101-1, only UE RF requirements are listed in the last column of the table in the clause 6.1 and 6.2, which are the requirements to be fulfilled by inter-band CA or EN-DC to support tx switching feature.
+
+## 6.1 Inter-band CA
+
+Requirements for a Rel-16 UE for additional NR inter-band CA configurations within FR1 compared to TS 38.101-1 of Rel-16 [2] are introduced via this clause.
+
+Requirements for a Rel-17 UE for additional NR inter-band CA configurations within FR1 compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause.
+
+Table 6.1-1: NR inter-band CA within FR1
+
+| Feature                                                           | DL/UL | Maximum number of bands | number of CCs | CA BW Classes | Duplex-mode      | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) |
+|-------------------------------------------------------------------|-------|-------------------------|---------------|---------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------|
+| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL    | 2                       | 2             | A             | TDD, FDD and TDD | Rel-16                   | Table A.2-1                                                                                       |
+| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL    | 2                       | 3             | A, B, C       | TDD, FDD and TDD | Rel-17                   | Table A.2-1                                                                                       |
+| Inter-band CA configurations with 2Tx-2Tx switching within NR FR1 | UL    | 2                       | 2             | A             | TDD, FDD and TDD | Rel-17                   | Table A.2-1                                                                                       |
+|                                                                   |       | 2                       | 3             | A, B, C       |                  |                          |                                                                                                   |
+
+## 6.2 Inter-band EN-DC
+
+Requirements for a Rel-16 UE for additional EN-DC inter-band configurations within FR1 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause.
+
+Table 6.2-1: EN-DC inter-band configurations without SUL within FR1
+
+| Feature                                 | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode      | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) |
+|-----------------------------------------|-------|--------------------------------|------------------------------|----------------------------|--------------------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------|
+| Inter-band EN-DC with 1Tx-2Tx switching | UL    | 1                              | 1                            | 1                          | 1                        | TDD, FDD and TDD | Rel-16                   | Table A.1-1                                                                                       |
+
+# Annex A (informative): Common UE RF requirements
+
+## A.1 Common UE RF requirements for Inter-band EN-DC with tx switching
+
+The requirements and test cases listed in Table A.1-1 are specified in in REL-16 version of TS 38.101-3 [4].
+
+Table A.1-1: Common UE RF requirements for Inter-band EN-DC with tx switching
+
+| Clause | Description                                                     |
+|--------|-----------------------------------------------------------------|
+| 5.5B.4 | Configuration for Inter-band EN-DC within FR1                   |
+| 6.3B.4 | Output power dynamics for switching between two uplink carriers |
+
+## A.2 Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1
+
+The requirements and test cases listed in Table A.2-1 are specified in Rel-16 version of TS 38.101-1 [2].
+
+The requirements and test cases listed in Table A.2-1 are specified in Rel-17 version of TS 38.101-1 [2].
+
+**Table A.2-1: Common UE RF requirements for Inter-band CA configurations with tx switching within NR FR1**
+
+| Clause   | Description                                 |
+|----------|---------------------------------------------|
+| 5.2A.2   | Operating bands for inter-band CA           |
+| 6.3A.3.3 | Transmit ON/OFF time mask for inter-band CA |
+
+# Annex B (informative): Change history
+
+| Change history |                |            |    |     |     |                                                                                                                                                                      |             |
+|----------------|----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting        | TDoc       | CR | Rev | Cat | Subject/Comment                                                                                                                                                      | New version |
+| 2022-08        | RAN4 #104-e    | R4-2212699 |    |     |     | TR skeleton                                                                                                                                                          | 0.0.1       |
+| 2022-10        | RAN4#104-bis-e | R4-2216097 |    |     |     | Implement the following TPs from RAN4#104-bis-e:<br>R4-2216096, TP to 37.877 DL interruption clarification for CA_n1-n5-n78 at dynamic Tx switching, China Telecom   | 0.1.0       |
+| 2022-11        | RAN4#105       | R4-2218608 |    |     |     | Implement the following TPs from RAN4#105:<br>R4-2218607, TP to 37.877 DL interruption clarification for CA_n3-n5-n78 at dynamic Tx switching, China Telecom         | 0.2.0       |
+| 2023-04        | RAN4#106bis-e  | R4-2305155 |    |     |     | Implement the following TPs from RAN4#106bis-e:<br>R4-2306549, TP to TR 37.877: Release independence on mandating no DL interruption for Tx Switching, China Telecom | 0.3.0       |
+| 2023-12        | RAN#102        | RP-23xxxx  |    |     |     | Editorial change and change history update                                                                                                                           | 1.0.0       |
+
+| Change history |         |      |    |     |     |                                                        |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2023-12        | RAN#102 |      |    |     |     | Approved by plenary – Rel-18 spec under change control | 18.0.0      |

gsma/37_series/37878/raw.md

@@ -0,0 +1,597 @@
+
+
+# 3GPP TR 37.878 V18.0.0 (2023-12)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. At the bottom, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|         |                                                                        |           |
+|---------|------------------------------------------------------------------------|-----------|
+| 1       | Scope.....                                                             | 5         |
+| 2       | References.....                                                        | 5         |
+| 3       | Definitions, symbols and abbreviations .....                           | 6         |
+| 3.1     | Definitions.....                                                       | 6         |
+| 3.2     | Symbols.....                                                           | 6         |
+| 3.3     | Abbreviations .....                                                    | 6         |
+| 4       | Background .....                                                       | 6         |
+| 4.1     | Justification .....                                                    | 6         |
+| 4.2     | Objective .....                                                        | 6         |
+| 5       | Void.....                                                              | 7         |
+| 6       | Con-current operation between one Uu band and one PC5 band .....       | 7         |
+| 6.1     | Con-current operation between one LTE Uu band and one NR PC5 band..... | 7         |
+| 6.1.1   | V2X_34A_n47A.....                                                      | 7         |
+| 6.1.1.1 | Operating bands for V2X_34A_n47A.....                                  | 7         |
+| 6.1.1.2 | Channel bandwidths per operating band for V2X_34A_n47A .....           | 8         |
+| 6.1.1.3 | UE co-existence studies .....                                          | 8         |
+| 6.1.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                   | 8         |
+| 6.2     | Con-current operation between one NR Uu band and one NR PC5 band ..... | 8         |
+| 6.2.1   | V2X_n34A-n47A .....                                                    | 8         |
+| 6.2.1.1 | Operating bands for V2X_n34A-n47A.....                                 | 8         |
+| 6.2.1.2 | Channel bandwidths per operating band for V2X_n34A-n47A .....          | 9         |
+| 6.2.1.3 | Coexistence studies.....                                               | 10        |
+| 6.2.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                   | 13        |
+| 6.2.2   | V2X_n3A-n47A .....                                                     | 13        |
+| 6.2.2.1 | Operating bands for V2X_n3A-n47A.....                                  | 13        |
+| 6.2.2.2 | Channel bandwidths per operating band for V2X_n3A-n47A .....           | 14        |
+| 6.2.2.3 | UE co-existence studies .....                                          | 14        |
+| 6.2.2.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                   | 16        |
+| 6.3     | Con-current operation between one NR Uu band and one LTE PC5 band..... | 16        |
+| 6.3.1   | V2X_n34A_47A.....                                                      | 16        |
+| 6.3.1.1 | Operating bands for V2X_n34A_47A.....                                  | 16        |
+| 6.3.1.2 | Channel bandwidths per operating band for V2X_n34A_47A .....           | 17        |
+| 6.3.1.3 | UE co-existence studies .....                                          | 17        |
+| 6.3.1.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                   | 17        |
+| 6.3.2   | V2X_n3A_47A.....                                                       | 17        |
+| 6.3.2.1 | Operating bands for V2X_n3A_47A.....                                   | 17        |
+| 6.3.2.2 | Channel bandwidths per operating band for V2X_n3A_47A .....            | 18        |
+| 6.3.2.3 | UE co-existence studies .....                                          | 18        |
+| 6.3.2.4 | MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                   | 18        |
+| 7       | Void.....                                                              | 18        |
+|         | <b>Annex A: Change history .....</b>                                   | <b>19</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document is the Technical Report on TR on band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band in Release 18.
+
+The purpose of the present document is to study the extension of the band combinations for V2X service to grow the NR V2X ecosystem. Operators propose new band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band. Whether to specify con-current operation of LTE/NR CA/DC band combinations and V2X band depends on requests in Rel-18. Specifically, the self-desensitization problem of con-current operation band combinations will be analysed including harmonics, IMD problem, etc.. Also the candidate solutions will be studied to solve the self-desensitization problem.
+
+**Table 1-1: Release 18 NR V2X band combinations**
+
+| V2X Band combination | REL independent from |
+|----------------------|----------------------|
+| V2X_n3-n47           | Rel-16               |
+| V2X_n34-n47          | Rel-16               |
+| V2X_n3_47            | Rel-16               |
+| V2X_n34_47           | Rel-16               |
+| V2X_34_n47           | Rel-16               |
+
+Note: All band combinations in table 1-1 that are release independent from Rel-16 are optional
+
+# 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] RP-221879: " New WID: Rel-18 band combinations for concurrent operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band ".
+- [3] 3GPP TR 38.886 V16.3.0: " V2X Services based on NR; User Equipment (UE) radio transmission and reception".
+- [4] 3GPP TR 38.785 V17.0.0: " User Equipment (UE) radio transmission and reception for enhanced NR sidelink".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions 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].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                   |                                                                                                                |
+|-------------------|----------------------------------------------------------------------------------------------------------------|
+| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for CA or DC operation, for serving cell $c$ .         |
+| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for CA or DC operation, for serving cell $c$ |
+
+## 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].
+
+|         |                                   |
+|---------|-----------------------------------|
+| CA      | Carrier Aggregation               |
+| CC      | Component Carrier                 |
+| DC      | Dual Connectivity                 |
+| ITS     | Intelligent Transportation System |
+| MSD     | Maximum Sensitivity Degradation   |
+| REFSENS | Reference Sensitivity             |
+
+# 4 Background
+
+## 4.1 Justification
+
+3GPP has completed the Release 17 work item on NR V2X including RAN4 minimum requirements and frequency bands for V2X operation. The current specification considers an set of frequency bands for PC5 interface and requirement frame work for con-current operation between Uu bands and V2X bands as part of Release 17 work.
+
+However, in order to further enhance the V2X ecosystem, it is necessary to set up a basket WI to introduce more band combinations on con-current operation of Uu bands and V2X bands in Release 18.
+
+## 4.2 Objective
+
+The objective of this work item is to specify band specific RF requirements for the following scenarios with maximum two simultaneous transmission bands within FR1:
+
+- Con-current operation between NR Uu band and NR PC5 band.
+- Con-current operation between LTE Uu band and NR PC5 band.
+- Con-current operation between NR Uu band and LTE PC5 band.
+- Whether to specify con-current operation of LTE/NR CA/DC band combinations + PC5 V2X band depending on requests in Rel-18.
+  - If there is such request the denotation on the combination definition need to be discussed at first.
+
+- Analyse con-current operation band combinations that have self-desensitization due to following reasons:
+  - TX Harmonic and/or inter modulation overlap of receive band
+  - TX signal overlap of receiver harmonic frequency
+  - TX frequency being in close proximity of one of the receive bands
+  - Any other identified reasons
+- For the combination where self-desensitization exists, specify at least needed
+  - $\Delta T_{IB}$  and  $\Delta R_{IB}$
+  - Reference sensitivity excerpts
+  - UL/SL RB restrictions for REFSENS test
+- Add conformance testing in RAN5 specifications (to follow at a later stage)
+
+of all REL-18 V2X con-current operation band combinations that fall into the category defined by the WI title.
+
+An overview of these V2X con-current operation band combinations is provided in the attached Excel.
+
+NOTE: Only power class 3 (PC3) is considered in this work item.
+
+# 5 Void
+
+# 6 Con-current operation between one Uu band and one PC5 band
+
+## 6.1 Con-current operation between one LTE Uu band and one NR PC5 band
+
+### 6.1.1 V2X\_34A\_n47A
+
+#### 6.1.1.1 Operating bands for V2X\_34A\_n47A
+
+The operating bands for V2X\_34A\_n47A are specified in table 6.1.1.1-1.
+
+**Table 6.1.1.1-1: Inter-band con-current V2X operating bands for V2X\_34A\_n47A**
+
+| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band         |   |                      | Downlink (DL) band       |   |                      | Duplex Mode |  |
+|-------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--|
+|                               |                            |           | BS receive / UE transmit |   |                      | BS transmit / UE receive |   |                      |             |  |
+|                               |                            |           | F <sub>UL_low</sub>      | – | F <sub>UL_high</sub> | F <sub>DL_low</sub>      | – | F <sub>DL_high</sub> |             |  |
+| V2X_34A_n47A                  | 34                         | Uu        | 2010 MHz                 | – | 2025 MHz             | 2010 MHz                 | – | 2025 MHz             | TDD         |  |
+|                               | n47                        | PC5       | 5855 MHz                 | – | 5925 MHz             | 5855 MHz                 | – | 5925 MHz             | HD          |  |
+
+#### 6.1.1.2 Channel bandwidths per operating band for V2X\_34A\_n47A
+
+The channel bandwidths per operating band for V2X\_34A\_n47A are specified in table 6.1.1.2-1.
+
+**Table 6.1.1.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_34A\_n47A**
+
+| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set |
+|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------|
+| V2X_34A_n47A                 | 34                         | 15      | 5, 10, 15               | 55                                 | 0                         |
+|                              | n47                        | 15      | 10, 20, 30, 40          |                                    |                           |
+|                              |                            | 30      | 10, 20, 30, 40          |                                    |                           |
+|                              |                            | 60      | 10, 20, 30, 40          |                                    |                           |
+
+#### 6.1.1.3 UE co-existence studies
+
+The UE co-existence studies specified for V2X\_n34A-n47A in clause 6.2.1.3 are applicable to V2X\_34A\_n47A since band 34 and band n34 have the same frequency range.
+
+#### 6.1.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+**Table 6.1.1.4-1:  $\Delta T_{IB,c}$  for inter-band con-current V2X operation (two bands)**
+
+| V2X con-current band Combination | E-UTRA or V2X Operating Band | $\Delta T_{IB,c}$ [dB] |
+|----------------------------------|------------------------------|------------------------|
+| V2X_34A_n47A                     | 34                           | 0.0                    |
+
+**Table 6.1.1.4-2:  $\Delta R_{IB,c}$  for inter-band con-current V2X operation (two bands)**
+
+| V2X inter-band con-current band Combination | E-UTRA Band | $\Delta R_{IB,c}$ [dB] |
+|---------------------------------------------|-------------|------------------------|
+| V2X_34A_n47A                                | 34          | 0.0                    |
+
+## 6.2 Con-current operation between one NR Uu band and one NR PC5 band
+
+### 6.2.1 V2X\_n34A-n47A
+
+#### 6.2.1.1 Operating bands for V2X\_n34A-n47A
+
+The operating bands for V2X\_n34A-n47A are specified in table 6.2.1.1-1.
+
+Table 6.2.1.1-1: Inter-band concurrent V2X operating bands for V2X\_n34A-n47A
+
+| V2X concurrent configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band         |   |                      | Downlink (DL) band       |   |                      | Duplex Mode |  |
+|------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--|
+|                              |                            |           | BS receive / UE transmit |   |                      | BS transmit / UE receive |   |                      |             |  |
+|                              |                            |           | F <sub>UL_low</sub>      | – | F <sub>UL_high</sub> | F <sub>DL_low</sub>      | – | F <sub>DL_high</sub> |             |  |
+| V2X_n34A-n47A                | n34                        | Uu        | 2010 MHz                 | – | 2025 MHz             | 2010 MHz                 | – | 2025 MHz             | TDD         |  |
+|                              | n47                        | PC5       | 5855 MHz                 | – | 5925 MHz             | 5855 MHz                 | – | 5925 MHz             | HD          |  |
+
+#### 6.2.1.2 Channel bandwidths per operating band for V2X\_n34A-n47A
+
+The channel bandwidths per operating band for V2X\_n34A-n47A are specified in table 6.2.1.2-1.
+
+**Table 6.2.1.2-1: V2X inter-band concurrent configurations and bandwidth combination sets for V2X\_n34A-n47A**
+
+| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set |
+|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------|
+| V2X_n34A_n47A                | n34                        | 15      | 5, 10, 15               | 55                                 | 0                         |
+|                              |                            | 30      | 10, 15                  |                                    |                           |
+|                              |                            | 60      | 10, 15                  |                                    |                           |
+|                              | n47                        | 15      | 10, 20, 30, 40          |                                    |                           |
+|                              |                            | 30      | 10, 20, 30, 40          |                                    |                           |
+|                              |                            | 60      | 10, 20, 30, 40          |                                    |                           |
+
+#### 6.2.1.3 Coexistence studies
+
+The harmonics analysis for V2X\_n34A-n47A is specified in table 6.2.1.3-1. Up to 4th harmonics of band n34 are provided since the frequency range of the 5<sup>th</sup> harmonics is much higher than 5.9GHz. The harmonics of band n47 are not listed as the harmonics distributed in the frequency range much higher than 5.9GHz have no impact on GNSS and ISM bands.
+
+**Table 6.2.1.3-1: Harmonics analysis for V2X\_n34A-n47A**
+
+| Operating Band                       | Band n34       |          | Band n47  |           |         |
+|--------------------------------------|----------------|----------|-----------|-----------|---------|
+|                                      | UE UL carriers | fx_low   | fx_high   | fy_low    | fy_high |
+| UL frequency (MHz)                   |                | 2010     | 2025      | 5855      | 5925    |
+| 2nd harmonics frequency limits       |                | 2*fx_low | 2*fx_high | No effect |         |
+| 2nd harmonics frequency limits (MHz) |                | 4020     | 4050      |           |         |
+| 3rd harmonics frequency limits       |                | 3*fx_low | 3*fx_high | No effect |         |
+| 3rd harmonics frequency limits (MHz) |                | 6030     | 6075      |           |         |
+| 4th harmonics frequency limits       |                | 4*fx_low | 4*fx_high | No effect |         |
+| 4th harmonics frequency limits (MHz) |                | 8040     | 8100      |           |         |
+
+The IMD analysis for V2X\_n34A-n47A is specified in table 6.2.1.3-2. Up to the 5<sup>th</sup> order IMDs of band n34 and band n47 are provided. Based on the IMD analysis, it is observed that no IMD products fall into the associated bands.
+
+**Table 6.2.1.3-2: IMD analysis for V2X\_n34A-n47A**
+
+| Operating Band                                   | Band 34              |                       | Band n47             |                       |
+|--------------------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UE UL carriers                                   | fx_low               | fx_high               | fy_low               | fy_high               |
+| UL frequency (MHz)                               | 2010                 | 2025                  | 5855                 | 5925                  |
+| 2 <sup>nd</sup> harmonics frequency limits       | 2*fx_low             | 2*fx_high             | 2* fy_low            | 2* fy_high            |
+| 2 <sup>nd</sup> harmonics frequency limits (MHz) | 4020                 | 4050                  | 11710                | 11850                 |
+| 3 <sup>rd</sup> harmonics frequency limits       | 3*fx_low             | 3*fx_high             | 3* fy_low            | 3* fy_high            |
+| 3 <sup>rd</sup> harmonics frequency limits (MHz) | 6030                 | 6075                  | 17565                | 17775                 |
+| Two tone 2 <sup>nd</sup> order IMD products      | fy_low – fx_high     | fy_high – fx_low      | fy_low + fx_low      | fy_high + fx_high     |
+| IMD frequency limits (MHz)                       | 3830                 | 3915                  | 7865                 | 7950                  |
+| Two-tone 3 <sup>rd</sup> order IMD products      | 2*fx_low – fy_high   | 2*fx_high – fy_low    | 2*fy_low – fx_high   | 2*fy_high – fx_low    |
+| IMD frequency limits (MHz)                       | 1905                 | 1805                  | 9685                 | 9840                  |
+| Two-tone 3 <sup>rd</sup> order IMD products      | 2*fx_low + fy_low    | 2*fx_high + fy_high   | 2*fy_low + fx_low    | 2*fy_high + fx_high   |
+| IMD frequency limits (MHz)                       | 9875                 | 9975                  | 13720                | 13875                 |
+| Two-tone 4 <sup>th</sup> order IMD products      | 3*fx_low – fy_high   | 3*fx_high – fy_low    | 3*fy_low – fx_high   | 3*fy_high – fx_low    |
+| IMD frequency limits (MHz)                       | 105                  | 220                   | 15540                | 15765                 |
+| Two-tone 4 <sup>th</sup> order IMD products      | 3*fx_low + fy_low    | 3*fx_high + fy_high   | 3*fy_low + fx_low    | 3*fy_high + fx_high   |
+| IMD frequency limits (MHz)                       | 11885                | 12000                 | 19575                | 19800                 |
+| Two-tone 4 <sup>th</sup> order IMD products      | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low  | 2*fy_low + 2*fy_low  | 2*fx_high + 2*fy_high |
+| IMD frequency limits (MHz)                       | 7830                 | 7660                  | 15730                | 15900                 |
+| Two-tone 5 <sup>th</sup> order IMD products      | fx_low – 4*fy_high   | fx_high – 4*fy_low    | fy_low – 4*fx_high   | fy_high – 4*fx_low    |
+| IMD frequency limits (MHz)                       | 21690                | 21395                 | 2245                 | 2115                  |
+| Two-tone 5 <sup>th</sup> order IMD products      | fx_low + 4*fy_low    | fx_high + 4*fy_high   | fy_low + 4*fx_low    | fy_high + 4*fx_high   |
+| IMD frequency limits (MHz)                       | 25430                | 25725                 | 13895                | 14025                 |
+| Two-tone 5 <sup>th</sup> order IMD products      | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low  | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low  |
+| IMD frequency limits (MHz)                       | 13755                | 13515                 | 5635                 | 5820                  |
+| Two-tone 5 <sup>th</sup> order IMD products      | 2*fx_low + 3*fy_low  | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low  | 2*fy_high + 3*fx_high |
+
+|                            |       |       |       |       |
+|----------------------------|-------|-------|-------|-------|
+| IMD frequency limits (MHz) | 21585 | 21825 | 17740 | 17925 |
+|----------------------------|-------|-------|-------|-------|
+
+The harmonics and intermodulation products should be evaluated when V2X inter-band concurrent operating UE coexists with other systems such as GNSS and ISM. The harmonics and IMD analysis of V2X\_n34A-n47A for GNSS and ISM bands is shown in table 6.2.1.3-3. Based on the analysis for GNSS and ISM bands, band n47 has an impact on the ISM band (5GHz).
+
+**Table 6.2.1.3-3: Harmonic and IMDs analysis of V2X\_n34A-n47A UE for GNSS and ISM bands**
+
+| Victim Systems    | Frequency range [MHz] |   |        | Impact | Regions   | Comments                      |
+|-------------------|-----------------------|---|--------|--------|-----------|-------------------------------|
+| COMPASS (Beidou)  | 1559                  | - | 1591   | No     |           |                               |
+| Galileo           | 1559                  | - | 1591   | No     |           |                               |
+| GLONASS           | 1591                  | - | 1610   | No     |           |                               |
+| GPS               | 1563                  | - | 1587   | No     |           |                               |
+| ISM band (2.4GHz) | 2400                  | - | 2483.5 | No     | US/Europe |                               |
+|                   | 2400                  | - | 2494   | No     | Asia      |                               |
+| ISM band (5GHz)   | 5150                  | - | 5925   | Yes    | US        | 5 <sup>th</sup> IMD, Band n47 |
+|                   | 5150                  | - | 5350   | Yes    | Europe    |                               |
+|                   | 5470                  | - | 5725   | Yes    |           | 5 <sup>th</sup> IMD           |
+|                   | 5150                  | - | 5825   | Yes    | Asia      | 5 <sup>th</sup> IMD           |
+
+#### 6.2.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+**Table 6.2.1.4-1:  $\Delta T_{IB,c}$  for inter-band concurrent V2X operation (two bands)**
+
+| V2X concurrent band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] |
+|---------------------------------|-------------------|------------------------|
+| V2X_n34A-n47A                   | n34               | 0.0                    |
+
+**Table 6.2.1.4-2:  $\Delta R_{IB,c}$  for inter-band concurrent V2X operation (two bands)**
+
+| V2X inter-band concurrent band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] |
+|--------------------------------------------|-------------------|------------------------|
+| V2X_n34A-n47A                              | n34               | 0.0                    |
+
+### 6.2.2 V2X\_n3A-n47A
+
+#### 6.2.2.1 Operating bands for V2X\_n3A-n47A
+
+The operating bands for V2X\_n3A-n47A are specified in table 6.2.2.1-1.
+
+Table 6.2.2.1-1: Inter-band concurrent V2X operating bands for V2X\_n3A-n47A
+
+| V2X concurrent configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band         |   |                      | Downlink (DL) band       |   |                      | Duplex Mode |  |
+|------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--|
+|                              |                            |           | BS receive / UE transmit |   |                      | BS transmit / UE receive |   |                      |             |  |
+|                              |                            |           | F <sub>UL_low</sub>      | – | F <sub>UL_high</sub> | F <sub>DL_low</sub>      | – | F <sub>DL_high</sub> |             |  |
+| V2X_n3A-n47A                 | n3                         | Uu        | 1710 MHz                 | – | 1785 MHz             | 1805 MHz                 | – | 1880 MHz             | FDD         |  |
+|                              | n47                        | PC5       | 5855 MHz                 | – | 5925 MHz             | 5855 MHz                 | – | 5925 MHz             | HD          |  |
+
+#### 6.2.2.2 Channel bandwidths per operating band for V2X\_n3A-n47A
+
+The channel bandwidths per operating band for V2X\_n3A-n47A are specified in table 6.2.2.2-1.
+
+Table 6.2.2.2-1: V2X inter-band concurrent configurations and bandwidth combination sets for V2X\_n3A-n47A
+
+| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz)               | Maximum aggregated bandwidth [MHz] | Bandwidth combination set |
+|------------------------------|----------------------------|---------|---------------------------------------|------------------------------------|---------------------------|
+| V2X_n3A-n47A                 | n3                         | 15      | 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 | 90                                 | 0                         |
+|                              |                            | 30      | 10, 15, 20, 25, 30, 35, 40, 45, 50    |                                    |                           |
+|                              |                            | 60      | 10, 15, 20, 25, 30, 35, 40, 45, 50    |                                    |                           |
+|                              | n47                        | 15      | 10, 20, 30, 40                        |                                    |                           |
+|                              |                            | 30      | 10, 20, 30, 40                        |                                    |                           |
+|                              |                            | 60      | 10, 20, 30, 40                        |                                    |                           |
+
+#### 6.2.2.3 UE co-existence studies
+
+The harmonics analysis for V2X\_n3A-n47A is specified in table 6.2.2.3-1. Up to the 3<sup>rd</sup> harmonics of band 3 are provided since the frequency range of the 4<sup>th</sup> harmonics is higher than 5.9GHz. The harmonics of band n47 are not listed as the harmonics distributed in the frequency range much higher than 5.9GHz have no impact on GNSS and ISM bands. Based on the harmonics analysis, it is observed that the 3<sup>rd</sup> harmonics of band 3 have no impact on band n47.
+
+Table 6.2.2.3-1: Harmonics analysis for V2X\_n3A-n47A
+
+| Operating Band                       | Band 3   |           | Band n47  |         |
+|--------------------------------------|----------|-----------|-----------|---------|
+| UE UL carriers                       | fx_low   | fx_high   | fy_low    | fy_high |
+| UL frequency (MHz)                   | 1710     | 1785      | 5855      | 5925    |
+| 2nd harmonics frequency limits       | 2*fx_low | 2*fx_high | No effect |         |
+| 2nd harmonics frequency limits (MHz) | 3420     | 3570      |           |         |
+| 3rd harmonics frequency limits       | 3*fx_low | 3*fx_high | No effect |         |
+| 3rd harmonics frequency limits (MHz) | 5130     | 5355      |           |         |
+
+The IMD analysis for V2X\_n3A-n47A is specified in table 6.2.2.3-2. Up to the 5<sup>th</sup> order IMDs of band 3 and band n47 are provided. Based on the IMD analysis, it is observed that no IMD products fall into the associated bands. So there is no IMD issue caused by the band combination.
+
+Table 6.2.2.3-2: IMD analysis for V2X\_n3A-n47A
+
+| Operating Band                                   | Band 3         |                      | Band n47              |                      |                       |
+|--------------------------------------------------|----------------|----------------------|-----------------------|----------------------|-----------------------|
+|                                                  | UE UL carriers | fx_low               | fx_high               | fy_low               | fy_high               |
+| UL frequency (MHz)                               |                | 1710                 | 1785                  | 5855                 | 5925                  |
+| 2 <sup>nd</sup> harmonics frequency limits       |                | 2*fx_low             | 2*fx_high             | 2* fy_low            | 2* fy_high            |
+| 2 <sup>nd</sup> harmonics frequency limits (MHz) |                | 3420                 | 3570                  | 11710                | 11850                 |
+| 3 <sup>rd</sup> harmonics frequency limits       |                | 3*fx_low             | 3*fx_high             | 3* fy_low            | 3* fy_high            |
+| 3 <sup>rd</sup> harmonics frequency limits (MHz) |                | 5130                 | 5355                  | 17565                | 17775                 |
+| Two tone 2 <sup>nd</sup> order IMD products      |                | fy_low – fx_high     | fy_high – fx_low      | fy_low + fx_low      | fy_high + fx_high     |
+| IMD frequency limits (MHz)                       |                | 4070                 | 4215                  | 7565                 | 7710                  |
+| Two-tone 3 <sup>rd</sup> order IMD products      |                | 2*fx_low – fy_high   | 2*fx_high – fy_low    | 2*fy_low – fx_high   | 2*fy_high – fx_low    |
+| IMD frequency limits (MHz)                       |                | 2505                 | 2285                  | 9925                 | 10140                 |
+| Two-tone 3 <sup>rd</sup> order IMD products      |                | 2*fx_low + fy_low    | 2*fx_high + fy_high   | 2*fy_low + fx_low    | 2*fy_high + fx_high   |
+| IMD frequency limits (MHz)                       |                | 9275                 | 9425                  | 13420                | 13635                 |
+| Two-tone 4 <sup>th</sup> order IMD products      |                | 3*fx_low – fy_high   | 3*fx_high – fy_low    | 3*fy_low – fx_high   | 3*fy_high – fx_low    |
+| IMD frequency limits (MHz)                       |                | 795                  | 500                   | 15780                | 16065                 |
+| Two-tone 4 <sup>th</sup> order IMD products      |                | 3*fx_low + fy_low    | 3*fx_high + fy_high   | 3*fy_low + fx_low    | 3*fy_high + fx_high   |
+| IMD frequency limits (MHz)                       |                | 10985                | 11280                 | 19275                | 19560                 |
+| Two-tone 4 <sup>th</sup> order IMD products      |                | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low  | 2*fx_low + 2*fy_low  | 2*fx_high + 2*fy_high |
+| IMD frequency limits (MHz)                       |                | 8430                 | 8140                  | 15130                | 15420                 |
+| Two-tone 5 <sup>th</sup> order IMD products      |                | fx_low – 4*fy_high   | fx_high – 4*fy_low    | fy_low – 4*fx_high   | fy_high – 4*fx_low    |
+| IMD frequency limits (MHz)                       |                | 21990                | 21635                 | 1285                 | 915                   |
+| Two-tone 5 <sup>th</sup> order IMD products      |                | fx_low + 4*fy_low    | fx_high + 4*fy_high   | fy_low + 4*fx_low    | fy_high + 4*fx_high   |
+| IMD frequency limits (MHz)                       |                | 25130                | 25485                 | 12695                | 13065                 |
+| Two-tone 5 <sup>th</sup> order IMD products      |                | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low  | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low  |
+| IMD frequency limits (MHz)                       |                | 14355                | 13995                 | 6355                 | 6720                  |
+| Two-tone 5 <sup>th</sup> order IMD products      |                | 2*fx_low + 3*fy_low  | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low  | 2*fy_high + 3*fx_high |
+| IMD frequency limits (MHz)                       |                | 20985                | 21345                 | 16840                | 17205                 |
+
+The harmonics and intermodulation products should be evaluated when V2X inter-band concurrent operating UE coexists with other systems such as GNSS and ISM. The harmonics and IMD analysis of V2X\_n3A-n47A for GNSS and ISM bands is shown in table 6.2.2.3-3. Based on the analysis for GNSS and ISM bands, band n47 and the 3<sup>rd</sup> harmonics of band 3 have an impact on the ISM band (5GHZ).
+
+Table 6.2.2.3-3: Harmonic and IMDs analysis of V2X\_n3A-n47A UE for GNSS and ISM bands
+
+| Victim Systems    | Frequency range [MHz] |   |        | Impact | Regions   | Comments                                         |
+|-------------------|-----------------------|---|--------|--------|-----------|--------------------------------------------------|
+| COMPASS (Beidou)  | 1559                  | - | 1591   | No     |           |                                                  |
+| Galileo           | 1559                  | - | 1591   | No     |           |                                                  |
+| GLONASS           | 1591                  | - | 1610   | No     |           |                                                  |
+| GPS               | 1563                  | - | 1587   | No     |           |                                                  |
+| ISM band (2.4GHz) | 2400                  | - | 2483.5 | No     | US/Europe |                                                  |
+|                   | 2400                  | - | 2494   | No     | Asia      |                                                  |
+| ISM band (5GHz)   | 5150                  | - | 5925   | Yes    | US        | Band n47 and 3 <sup>rd</sup> harmonics of band 3 |
+|                   | 5150                  | - | 5350   | Yes    | Europe    | 3 <sup>rd</sup> harmonics of band 3              |
+|                   | 5470                  | - | 5725   | Yes    |           |                                                  |
+|                   | 5150                  | - | 5825   | Yes    | Asia      | 3 <sup>rd</sup> harmonics of band 3              |
+
+#### 6.2.2.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+Table 6.2.2.4-1:  $\Delta T_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] |
+|----------------------------------|-------------------|------------------------|
+| V2X_n3A-n47A                     | n3                | 0.0                    |
+
+Table 6.2.2.4-2:  $\Delta R_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] |
+|---------------------------------------------|-------------------|------------------------|
+| V2X_n3A-n47A                                | n3                | 0.0                    |
+
+## 6.3 Con-current operation between one NR Uu band and one LTE PC5 band
+
+### 6.3.1 V2X\_n34A\_47A
+
+#### 6.3.1.1 Operating bands for V2X\_n34A\_47A
+
+The operating bands for V2X\_n34A\_47A are specified in table 6.3.1.1-1.
+
+Table 6.3.1.1-1: Inter-band con-current V2X operating bands for V2X\_n34A\_47A
+
+| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band         |   |                | Downlink (DL) band       |   |                | Duplex Mode |  |
+|-------------------------------|----------------------------|-----------|--------------------------|---|----------------|--------------------------|---|----------------|-------------|--|
+|                               |                            |           | BS receive / UE transmit |   |                | BS transmit / UE receive |   |                |             |  |
+|                               |                            |           | $F_{UL\_low}$            | – | $F_{UL\_high}$ | $F_{DL\_low}$            | – | $F_{DL\_high}$ |             |  |
+| V2X_n34A_47A                  | n34                        | Uu        | 2010 MHz                 | – | 2025 MHz       | 2010 MHz                 | – | 2025 MHz       | TDD         |  |
+|                               | 47                         | PC5       | 5855 MHz                 | – | 5925 MHz       | 5855 MHz                 | – | 5925 MHz       | HD          |  |
+
+#### 6.3.1.2 Channel bandwidths per operating band for V2X\_n34A\_47A
+
+The channel bandwidths per operating band for V2X\_n34A\_47A are specified in table 6.3.1.2-1.
+
+Table 6.3.1.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_n34A\_47A
+
+| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz) | Maximum aggregated bandwidth [MHz] | Bandwidth combination set |
+|------------------------------|----------------------------|---------|-------------------------|------------------------------------|---------------------------|
+| V2X_n34A_47A                 | n34                        | 15      | 5, 10, 15               | 35                                 | 0                         |
+|                              |                            | 30      | 10, 15                  |                                    |                           |
+|                              |                            | 60      | 10, 15                  |                                    |                           |
+|                              | 47                         | 15      | 10, 20                  | 35                                 |                           |
+
+#### 6.3.1.3 UE co-existence studies
+
+The UE co-existence studies specified for V2X\_n34A-n47A in clause 6.2.1.3 are applicable to V2X\_n34A\_47A since band 47 and band n47 have the same frequency range.
+
+#### 6.3.1.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+Table 6.3.1.4-1:  $\Delta T_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] |
+|----------------------------------|-------------------|------------------------|
+| V2X_n34A_47A                     | n34               | 0.0                    |
+
+Table 6.3.1.4-2:  $\Delta R_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] |
+|---------------------------------------------|-------------------|------------------------|
+| V2X_n34A_47A                                | n34               | 0.0                    |
+
+### 6.3.2 V2X\_n3A\_47A
+
+#### 6.3.2.1 Operating bands for V2X\_n3A\_47A
+
+The operating bands for V2X\_n3A\_47A are specified in table 6.3.2.1-1.
+
+Table 6.3.2.1-1: Inter-band con-current V2X operating bands for V2X\_n3A\_47A
+
+| V2X con-current configuration | E-UTRA / NR Operating Band | Interface | Uplink (UL) band         |   |                      | Downlink (DL) band       |   |                      | Duplex Mode |  |
+|-------------------------------|----------------------------|-----------|--------------------------|---|----------------------|--------------------------|---|----------------------|-------------|--|
+|                               |                            |           | BS receive / UE transmit |   |                      | BS transmit / UE receive |   |                      |             |  |
+|                               |                            |           | F <sub>UL_low</sub>      | – | F <sub>UL_high</sub> | F <sub>DL_low</sub>      | – | F <sub>DL_high</sub> |             |  |
+| V2X_n3A_47A                   | n3                         | Uu        | 1710 MHz                 | – | 1785 MHz             | 1805 MHz                 | – | 1880 MHz             | FDD         |  |
+|                               | 47                         | PC5       | 5855 MHz                 | – | 5925 MHz             | 5855 MHz                 | – | 5925 MHz             | HD          |  |
+
+#### 6.3.2.2 Channel bandwidths per operating band for V2X\_n3A\_47A
+
+The channel bandwidths per operating band for V2X\_n3A\_47A are specified in table 6.3.2.2-1.
+
+Table 6.3.2.2-1: V2X inter-band con-current configurations and bandwidth combination sets for V2X\_n3A\_47A
+
+| V2X inter-band Configuration | E-UTRA / NR operating Band | SCS kHz | Channel bandwidth (MHz)               | Maximum aggregated bandwidth [MHz] | Bandwidth combination set |
+|------------------------------|----------------------------|---------|---------------------------------------|------------------------------------|---------------------------|
+| V2X_n3A_47A                  | n3                         | 15      | 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 | 70                                 | 0                         |
+|                              |                            | 30      | 10, 15, 20, 25, 30, 35, 40, 45, 50    |                                    |                           |
+|                              |                            | 60      | 10, 15, 20, 25, 30, 35, 40, 45, 50    |                                    |                           |
+|                              | 47                         | 15      | 10, 20                                |                                    |                           |
+
+#### 6.3.2.3 UE co-existence studies
+
+The UE co-existence studies specified for V2X\_n3A-n47A in clause 6.2.2.3 are applicable to V2X\_n3A\_47A since band 47 and band n47 have the same frequency range.
+
+#### 6.3.2.4 MSD, $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+Table 6.3.2.4-1:  $\Delta T_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X con-current band Combination | NR Operating Band | $\Delta T_{IB,c}$ [dB] |
+|----------------------------------|-------------------|------------------------|
+| V2X_n3A_47A                      | n3                | 0.0                    |
+
+Table 6.3.2.4-2:  $\Delta R_{IB,c}$  for inter-band con-current V2X operation (two bands)
+
+| V2X inter-band con-current band Combination | NR Operating Band | $\Delta R_{IB,c}$ [dB] |
+|---------------------------------------------|-------------------|------------------------|
+| V2X_n3A_47A                                 | n3                | 0.0                    |
+
+# Annex A: Change history
+
+| Change history |                |            |    |     |     |                                                                                                                                                                        |             |
+|----------------|----------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting        | TDoc       | CR | Rev | Cat | Subject/Comment                                                                                                                                                        | New version |
+| 2022-08        | RAN4 #104e     | R4-2214902 |    |     |     | Create the TR skeleton                                                                                                                                                 | 0.0.1       |
+| 2022-10        | RAN4 #104bis-e | R4-2217812 |    |     |     | Capture the following approved TPs:<br>R4-2217114 TP for V2X_n34A-n47A_V2X_34A-n47A_V2X_n34A-47A<br>R4-2217115 TP on coexistence study of V2X_n3A-n47A and V2X_n3A_47A | 0.1.0       |
+| 2022-11        | RAN4 #105      | R4-2218442 |    |     |     | Capture the following approved TP:<br>R4-2218198 TP updates for TR37.878                                                                                               | 0.2.0       |
+| 2023-12        | RAN#102        | RP-234066  |    |     |     | Presented to TSG RAN for approval (specification v1.0.0).                                                                                                              | 1.0.0       |
+
+| Change history |         |      |    |     |     |                                                        |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2023-12        | RAN#102 |      |    |     |     | Approved by plenary – Rel-18 spec under change control | 18.0.0      |