Add files using upload-large-folder tool

marked/Rel-17/25_series/25111/raw.md

@@ -0,0 +1,625 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                             |    |
+|---------------------------------------------|----|
+| Foreword .....                              | 4  |
+| Introduction .....                          | 5  |
+| 1 Scope.....                                | 6  |
+| 2 References.....                           | 6  |
+| 3 Definitions and abbreviations .....       | 6  |
+| 3.1 Definitions.....                        | 6  |
+| 3.2 Abbreviations .....                     | 6  |
+| 4 General.....                              | 7  |
+| 4.1 Main concepts .....                     | 7  |
+| 4.2 LMU Classes.....                        | 7  |
+| 4.3 U-TDOA architecture.....                | 7  |
+| 5 LMU radio characteristics.....            | 8  |
+| 5.1 Frequency bands.....                    | 8  |
+| 5.2 Channel arrangement.....                | 8  |
+| 5.3 Reference sensitivity level .....       | 9  |
+| 5.4 Dynamic range .....                     | 9  |
+| 5.5 Adjacent Channel Selectivity (ACS)..... | 9  |
+| 5.6 Blocking characteristics .....          | 9  |
+| 5.7 Intermodulation characteristics .....   | 13 |
+| 5.8 Spurious emissions.....                 | 14 |
+| 6 LMU measurement requirements.....         | 15 |
+| 6.1 General .....                           | 15 |
+| 6.2 RRC States supported.....               | 15 |
+| 6.3 Maximum response times.....             | 15 |
+| 6.4 Nominal time accuracy.....              | 15 |
+| 6.5 Multipath scenarios .....               | 16 |
+| 6.6 Moving scenario.....                    | 16 |
+| 6.7 Cross correlation .....                 | 16 |
+| Annex A (informative): Change history.....  | 17 |
+
+# --- Foreword
+
+This Technical Specification 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.
+
+# --- Introduction
+
+In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3<sup>rd</sup> Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management.
+
+Also, the fact that the specifications are/will be implemented by industry almost in parallel with the writing of them requires strict and fast procedures for handling of changes to the specifications.
+
+It is very important that the changes that are brought into the standard, from the past, at present and in the future, are well documented and controlled, so that technical consistency and backwards tracing are ensured.
+
+The 3GPP TSGs, and their sub-groups together with the Support Team are responsible for the technical content and consistency of the specifications whilst the Support Team alone is responsible for the proper management of the entire documentation, including specifications, meeting documents, administrative information and information exchange with other bodies.
+
+# --- 1 Scope
+
+The present document establishes the Location Measurement Unit (LMU) minimum RF characteristics of the FDD mode of UTRA.
+
+# --- 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 TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [2] 3GPP TS 45.004: "Modulation".
+- [3] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)".
+- [4] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios".
+- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [5] 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 [5].
+
+**Mean power:** When applied to a W-CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot unless otherwise stated.
+
+NOTE: The roll-off factor  $\alpha$  is defined in clause 6.8.1 of [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [5] 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 [5].
+
+|        |                                              |
+|--------|----------------------------------------------|
+| ACS    | Adjacent Channel Selectivity                 |
+| BS     | Base Station                                 |
+| BER    | Bit Error Ratio                              |
+| BLER   | Block Error Ratio                            |
+| CW     | Continuous Wave (unmodulated signal)         |
+| DL     | Down Link (forward link)                     |
+| FDD    | Frequency Division Duplexing                 |
+| GSM    | Global System for Mobile Communications      |
+| LMU    | Location Measurement Unit                    |
+| UARFCN | UTRA Absolute Radio Frequency Channel Number |
+| UE     | User Equipment                               |
+| UL     | Up Link (reverse link)                       |
+
+|        |                                        |
+|--------|----------------------------------------|
+| U-TDOA | Uplink Time Difference Of Arrival      |
+| WCDMA  | Wideband Code Division Multiple Access |
+
+# --- 4 General
+
+## 4.1 Main concepts
+
+The LMU is either located as a separate unit in an existing network or typically located at Node B or BTS sites. Therefore the LMU radio requirements assume that the isolation between the LMU and any other network to be protected is to be at least 30dB.
+
+The communication link between LMU and Stand-Alone SMLC is not a radio interface over the air. Requirements in this document therefore do not cover the situation when the LMU is transmitting over the air on this interface between LMU and Stand-Alone SMLC.
+
+## 4.2 LMU Classes
+
+The requirements in this specification apply to Wide Area LMUs and Medium Range LMUs.
+
+Wide Area LMUs are characterised by requirements derived from Macro Cell scenarios with an LMU to UE minimum coupling loss equal to 70 dB.
+
+Medium Range LMUs are characterised by requirements derived from Micro Cell scenarios with an LMU to UE minimum coupling loss equal to 53 dB.
+
+For Pico Cell scenarios, the location of the BS provides sufficient accuracy; therefore, a Local Area LMUs class is not specified.
+
+## 4.3 U-TDOA architecture
+
+A sample architecture is shown in Figure 3.1 depicting the LMU's relationship with other network elements. The LMU is typically located at the Node B. The LMUs communicate with the SMLC that distributes UTDOA reference data from the reference LMU to other cooperating LMUs when performing UE positioning.
+
+![Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with two Node Bs, two RNCs, a Stand-Alone SMLC, an MSC, and an SGSN. Node Bs are connected to RNCs via Iub interfaces. RNCs are connected to the Stand-Alone SMLC via Iupc interfaces. The Stand-Alone SMLC is connected to the MSC and SGSN via Iupc interfaces. LMUs are connected to the Stand-Alone SMLC. A vertical arrow on the left indicates that LMUs are typically located at Node B.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+```
+
+graph TD
+    NodeB1[Node B] -- Iub --> RNC1[RNC]
+    NodeB2[Node B] -- Iub --> RNC2[RNC]
+    RNC1 -- Iupc --> SMLC[Stand-Alone SMLC]
+    RNC2 -- Iupc --> SMLC
+    SMLC -- Iupc --> MSC[MSC]
+    SMLC -- Iupc --> SGSN[SGSN]
+    LMU1[LMU] --> SMLC
+    LMU2[LMU] --> SMLC
+    LMU3[LMU] --> SMLC
+    LMU4[LMU] --> SMLC
+    LMU5[LMU] --> SMLC
+    LMU6[LMU] --> SMLC
+    LMU7[LMU] --> SMLC
+    LMU8[LMU] --> SMLC
+    LMU9[LMU] --> SMLC
+    LMU10[LMU] --> SMLC
+    LMU11[LMU] --> SMLC
+    LMU12[LMU] --> SMLC
+    LMU13[LMU] --> SMLC
+    LMU14[LMU] --> SMLC
+    LMU15[LMU] --> SMLC
+    LMU16[LMU] --> SMLC
+    LMU17[LMU] --> SMLC
+    LMU18[LMU] --> SMLC
+    LMU19[LMU] --> SMLC
+    LMU20[LMU] --> SMLC
+    LMU21[LMU] --> SMLC
+    LMU22[LMU] --> SMLC
+    LMU23[LMU] --> SMLC
+    LMU24[LMU] --> SMLC
+    LMU25[LMU] --> SMLC
+    LMU26[LMU] --> SMLC
+    LMU27[LMU] --> SMLC
+    LMU28[LMU] --> SMLC
+    LMU29[LMU] --> SMLC
+    LMU30[LMU] --> SMLC
+    LMU31[LMU] --> SMLC
+    LMU32[LMU] --> SMLC
+    LMU33[LMU] --> SMLC
+    LMU34[LMU] --> SMLC
+    LMU35[LMU] --> SMLC
+    LMU36[LMU] --> SMLC
+    LMU37[LMU] --> SMLC
+    LMU38[LMU] --> SMLC
+    LMU39[LMU] --> SMLC
+    LMU40[LMU] --> SMLC
+    LMU41[LMU] --> SMLC
+    LMU42[LMU] --> SMLC
+    LMU43[LMU] --> SMLC
+    LMU44[LMU] --> SMLC
+    LMU45[LMU] --> SMLC
+    LMU46[LMU] --> SMLC
+    LMU47[LMU] --> SMLC
+    LMU48[LMU] --> SMLC
+    LMU49[LMU] --> SMLC
+    LMU50[LMU] --> SMLC
+    LMU51[LMU] --> SMLC
+    LMU52[LMU] --> SMLC
+    LMU53[LMU] --> SMLC
+    LMU54[LMU] --> SMLC
+    LMU55[LMU] --> SMLC
+    LMU56[LMU] --> SMLC
+    LMU57[LMU] --> SMLC
+    LMU58[LMU] --> SMLC
+    LMU59[LMU] --> SMLC
+    LMU60[LMU] --> SMLC
+    LMU61[LMU] --> SMLC
+    LMU62[LMU] --> SMLC
+    LMU63[LMU] --> SMLC
+    LMU64[LMU] --> SMLC
+    LMU65[LMU] --> SMLC
+    LMU66[LMU] --> SMLC
+    LMU67[LMU] --> SMLC
+    LMU68[LMU] --> SMLC
+    LMU69[LMU] --> SMLC
+    LMU70[LMU] --> SMLC
+    LMU71[LMU] --> SMLC
+    LMU72[LMU] --> SMLC
+    LMU73[LMU] --> SMLC
+    LMU74[LMU] --> SMLC
+    LMU75[LMU] --> SMLC
+    LMU76[LMU] --> SMLC
+    LMU77[LMU] --> SMLC
+    LMU78[LMU] --> SMLC
+    LMU79[LMU] --> SMLC
+    LMU80[LMU] --> SMLC
+    LMU81[LMU] --> SMLC
+    LMU82[LMU] --> SMLC
+    LMU83[LMU] --> SMLC
+    LMU84[LMU] --> SMLC
+    LMU85[LMU] --> SMLC
+    LMU86[LMU] --> SMLC
+    LMU87[LMU] --> SMLC
+    LMU88[LMU] --> SMLC
+    LMU89[LMU] --> SMLC
+    LMU90[LMU] --> SMLC
+    LMU91[LMU] --> SMLC
+    LMU92[LMU] --> SMLC
+    LMU93[LMU] --> SMLC
+    LMU94[LMU] --> SMLC
+    LMU95[LMU] --> SMLC
+    LMU96[LMU] --> SMLC
+    LMU97[LMU] --> SMLC
+    LMU98[LMU] --> SMLC
+    LMU99[LMU] --> SMLC
+    LMU100[LMU] --> SMLC
+  
+```
+
+Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with two Node Bs, two RNCs, a Stand-Alone SMLC, an MSC, and an SGSN. Node Bs are connected to RNCs via Iub interfaces. RNCs are connected to the Stand-Alone SMLC via Iupc interfaces. The Stand-Alone SMLC is connected to the MSC and SGSN via Iupc interfaces. LMUs are connected to the Stand-Alone SMLC. A vertical arrow on the left indicates that LMUs are typically located at Node B.
+
+Figure 3.1: Example of UTDOA deployment
+
+# 5 LMU radio characteristics
+
+An LMU performs BS receiver functions to obtain reference data for use at a cooperating LMU. The following clause describes the required LMU radio characteristics when performing these functions.
+
+## 5.1 Frequency bands
+
+- a) The LMU is designed to operate in the following bands:
+
+Table 4.1: Frequency bands
+
+| Operating Band | UL Frequencies<br>UE transmit, LMU receive |
+|----------------|--------------------------------------------|
+| I              | 1920 – 1980 MHz                            |
+| II             | 1850 -1910 MHz                             |
+| III            | 1710-1785 MHz                              |
+| IV             | 1710-1755 MHz                              |
+| V              | 824 – 849MHz                               |
+| VI             | 830-840 MHz                                |
+| VII            | 2500 – 2570 MHz                            |
+| VIII           | 880 – 915 MHz                              |
+| IX             | 1749.9 – 1784.9 MHz                        |
+| X              | 1710-1770 MHz                              |
+
+- b) Deployment in other frequency bands is not precluded
+
+## 5.2 Channel arrangement
+
+The channel arrangement shall be as specified in Section 5.4 of [1].
+
+## 5.3 Reference sensitivity level
+
+Using the reference measurement channel specification in TS 25.104 Annex A [1], the reference sensitivity level and performance of the LMU shall be as specified in Table 4.2.
+
+**Table 4.2: LMU reference sensitivity levels**
+
+| LMU Class        | Reference measurement channel data rate | LMU sensitivity level (dBm) | BER                        |
+|------------------|-----------------------------------------|-----------------------------|----------------------------|
+| Wide Area LMU    | 12.2 kbps                               | -121                        | BER shall not exceed 0.001 |
+| Medium Range LMU | 12.2 kbps                               | -111                        | BER shall not exceed 0.001 |
+
+## 5.4 Dynamic range
+
+Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel.
+
+The BER shall not exceed 0.001 for the parameters specified in Table 4.3.
+
+**Table 4.3: Dynamic range**
+
+| Parameter                               | Level Wide Area LMU | Level Medium Range LMU | Unit         |
+|-----------------------------------------|---------------------|------------------------|--------------|
+| Reference measurement channel data rate | 12.2                | 12.2                   | kbps         |
+| Wanted signal mean power                | -91                 | -81                    | dBm          |
+| Interfering AWGN signal                 | -73                 | -63                    | dBm/3.84 MHz |
+
+## 5.5 Adjacent Channel Selectivity (ACS)
+
+Adjacent channel selectivity (ACS) is a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the LMU receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s).
+
+The interference signal is offset from the wanted signal by the frequency offset Fuw. The interference signal shall be a W-CDMA signal as specified in Annex C of TS 25.104 [1].
+
+The BER shall not exceed 0.001 for the parameters specified in Table 4.4.
+
+**Table 4.4: LMU Adjacent channel selectivity**
+
+| Parameter                     | Level Wide Area LMU | Level Medium Range LMU | Unit |
+|-------------------------------|---------------------|------------------------|------|
+| Data rate                     | 12.2                | 12.2                   | kbps |
+| Wanted signal mean power      | -115                | -105                   | dBm  |
+| Interfering signal mean power | -52                 | -42                    | dBm  |
+| Fuw offset (Modulated)        | 5                   | 5                      | MHz  |
+
+## 5.6 Blocking characteristics
+
+The blocking characteristics are a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The performance as specified in Table 4.5-4.10 shall be met with a wanted and an interfering signal coupled to the LMU antenna input using the following parameters for the blocking and narrowband blocking requirements:
+
+**Table 4.5: Blocking performance requirement for Wide Area LMU**
+
+| Operating Band | Center Frequency of Interfering Signal       | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| I              | 1920 – 1980 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1900 – 1920 MHz<br>1980 – 2000 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -1900 MHz<br>2000 MHz – 12750 MHz      | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| II             | 1850 – 1910 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1830 – 1850 MHz<br>1910 – 1930 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1830 MHz<br>1930 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| III            | 1710 – 1785 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1785 – 1805 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1805 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| IV             | 1710 – 1755 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1755 – 1775 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1775 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| V              | 824-849 MHz                                  | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 804-824 MHz<br>849-869 MHz                   | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 804 MHz<br>869 MHz – 12750 MHz       | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VI             | 810 – 830 MHz<br>840 – 860 MHz               | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 810 MHz<br>860 MHz – 12750 MHz       | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VII            | 2500 – 2570 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 2480 – 2500 MHz<br>2570 – 2590 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -2480 MHz<br>2590 MHz – 12750 MHz      | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| VIII           | 880 – 915 MHz                                | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 860 – 880 MHz<br>915 – 925 MHz               | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -860 MHz<br>925 MHz – 12750 MHz        | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| IX             | 1749.9 – 1784.9 MHz                          | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1729.9 – 1749.9 MHz<br>1784.9 – 1804.9 MHz   | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1729.9 MHz<br>1804.9 MHz – 12750 MHz | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+| X              | 1710 – 1770 MHz                              | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1770 – 1790 MHz           | -40 dBm                       | -115 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1790 MHz – 12750 MHz     | -15 dBm                       | -115 dBm                 | —                                    | CW carrier                 |
+
+NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1]
+
+**Table 4.6: Blocking performance requirement for the Medium range LMU**
+
+| Operating Band | Center Frequency of Interfering Signal       | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| I              | 1920 – 1980 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1900 – 1920 MHz<br>1980 – 2000 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -1900 MHz<br>2000 MHz – 12750 MHz      | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| II             | 1850 – 1910 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1830 – 1850 MHz<br>1910 – 1930 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1830 MHz<br>1930 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| III            | 1710 – 1785 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1785 – 1805 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1805 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| IV             | 1710 – 1755 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1755 – 1775 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1775 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| V              | 824-849 MHz                                  | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 804-824 MHz<br>849-869 MHz                   | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 804 MHz<br>869 MHz – 12750 MHz       | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| VI             | 810 – 830 MHz<br>840 – 860 MHz               | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 810 MHz<br>860 MHz – 12750 MHz       | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| VII            | 2500 – 2570 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 2480 – 2500 MHz<br>2570 – 2590 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -2480 MHz<br>2590 MHz – 12750 MHz      | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| VIII           | 880 – 915 MHz                                | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 860 – 880 MHz<br>915 – 925 MHz               | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz -860 MHz<br>925 MHz – 12750 MHz        | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| IX             | 1749.9 – 1784.9 MHz                          | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1729.9 – 1749.9 MHz<br>1784.9 – 1804.9 MHz   | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1729.9 MHz<br>1804.9 MHz – 12750 MHz | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+| X              | 1710 – 1770 MHz                              | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1690 – 1710 MHz<br>1770 – 1790 MHz           | -35 dBm                       | -105 dBm                 | 10 MHz                               | WCDMA signal *             |
+|                | 1 MHz – 1690 MHz<br>1790 MHz – 12750 MHz     | -15 dBm                       | -105 dBm                 | —                                    | CW carrier                 |
+
+NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1]
+
+**Table 4.7: Blocking performance requirement (narrowband) for the Wide Area LMU**
+
+| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| II             | 1850 – 1910 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| III            | 1710 – 1785 MHz                        | - 47 dBm                      | -115 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| IV             | 1710 – 1755 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| V              | 824 – 849 MHz                          | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| VIII           | 880 – 915 MHz                          | - 47 dBm                      | -115 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| X              | 1710 – 1770 MHz                        | - 47 dBm                      | -115 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+
+NOTE \*: GMSK modulation as defined in TS 45.004 [2].
+
+**Table 4.8: Narrowband blocking performance requirement for the Medium Range LMU**
+
+| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| II             | 1850 – 1910 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| III            | 1710 – 1785 MHz                        | - 42 dBm                      | -105 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| IV             | 1710 – 1755 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| V              | 824 – 849 MHz                          | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+| VIII           | 880 – 915 MHz                          | - 42 dBm                      | -105 dBm                 | 2.8 MHz                              | GMSK modulated*            |
+| X              | 1710 – 1770 MHz                        | - 42 dBm                      | -105 dBm                 | 2.7 MHz                              | GMSK modulated*            |
+
+NOTE \*: GMSK modulation as defined in TS 45.004 [2].
+
+Additional blocking requirements shall be applied for the protection of the LMU receiver in the presence of GSM900, DCS1800, PCS1900, GSM850, UTRA TDD, and UTRA FDD in bands I to X.
+
+**Table 4.9: Additional blocking performance requirement for Wide Area LMU.**
+
+| Co-located BS type    | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Macro GSM900          | 921 – 960 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro DCS1800         | 1805 – 1880 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro PCS1900         | 1930 – 1990 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| Macro GSM850          | 869 – 894 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band I    | 2110 – 2170 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band II   | 1930 – 1990 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band III  | 1805 – 1880 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band IV   | 2110 – 2155 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band V    | 869 – 894 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VI   | 875 – 885 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VII  | 2620 – 2690 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band VIII | 925 – 960 MHz                          | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band IX   | 1844.9 – 1879.9 MHz                    | +16 dBm                       | -115 dBm                 | CW carrier                 |
+| WA UTRA-FDD Band X    | 2110 – 2170 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+
+**Table 4.10: Additional blocking performance requirements for the LMU**
+
+| Co-located BS type    | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Micro GSM900          | 921 – 960 MHz                          | -3 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro DCS1800         | 1805 – 1880 MHz                        | +5 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro PCS1900         | 1930 – 1990 MHz                        | +5 dBm                        | -105 dBm                 | CW carrier                 |
+| Micro GSM850          | 869 – 894 MHz                          | -3 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band I    | 2110 – 2170 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band II   | 1930 – 1990 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band III  | 1805 – 1880 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band IV   | 2110 – 2155 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band V    | 869 – 894 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VI   | 875 – 885 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VII  | 2620 – 2690 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band VIII | 925 – 960 MHz                          | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band IX   | 1844.9 – 1879.9 MHz                    | +8 dBm                        | -105 dBm                 | CW carrier                 |
+| MR UTRA-FDD Band X    | 2110 – 2170 MHz                        | +8 dBm                        | -105 dBm                 | CW carrier                 |
+
+An additional blocking requirement may be applied for the protection of the LMU receivers when UTRA TDD is co-located with an LMU.
+
+The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-BS minimum coupling loss.
+
+However, there are certain site-engineering solutions that can be used in these cases. These techniques are addressed in TR 25.942 [4].
+
+For an LMU, the static reference performance as specified in clause 5.3 should be met with a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 4.11.
+
+**Table 4.11: Blocking performance requirement for a Wide Area LMU when co-located with UTRA TDD BS in other bands.**
+
+| Co-located BS type | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal |
+|--------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------|
+| Wide Area TDD      | 2585 – 2620 MHz                        | +16 dBm                       | -115 dBm                 | CW carrier                 |
+
+## 5.7 Intermodulation characteristics
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal.
+
+The static reference performance as specified in clause 5.3 shall be met for a LMU when the following signals are coupled to LMU antenna input:
+
+- A wanted signal at the assigned channel frequency with a mean power of -115 dBm.
+- Two interfering signals with the following parameters.
+
+**Table 4.12: Intermodulation performance requirement (Wide Area LMU)**
+
+| Operating band | Interfering Signal mean power                                                         | Offset | Type of Interfering Signal |
+|----------------|---------------------------------------------------------------------------------------|--------|----------------------------|
+| All bands      | - 48 dBm                                                                              | 10 MHz | CW signal                  |
+|                | - 48 dBm                                                                              | 20 MHz | WCDMA signal *             |
+| Note*:         | The characteristics of the W-CDMA interference signal are specified in Annex C of [1] |        |                            |
+
+**Table 4.13: Narrowband intermodulation performance requirement (Wide Area LMU)**
+
+| Operating band                    | Interfering Signal mean power | Offset  | Type of Interfering Signal |
+|-----------------------------------|-------------------------------|---------|----------------------------|
+| II, III, IV, V, VIII, X           | - 47 dBm                      | 3.5 MHz | CW signal                  |
+|                                   | - 47 dBm                      | 5.9 MHz | GMSK modulated*            |
+| * GMSK as defined in TS45.004 [2] |                               |         |                            |
+
+The static reference performance as specified in clause 5.3 shall be met for a Medium Range LMU when the following signals are coupled to LMU antenna input:
+
+- A wanted signal at the assigned channel frequency with a mean power of -105 dBm.
+- Two interfering signals with the following parameters.
+
+**Table 4.14: Intermodulation performance requirement (Medium Range LMU)**
+
+| Operating band                                                                               | Interfering Signal mean power | Offset | Type of Interfering Signal |
+|----------------------------------------------------------------------------------------------|-------------------------------|--------|----------------------------|
+| All bands                                                                                    | - 44 dBm                      | 10 MHz | CW signal                  |
+|                                                                                              | - 44 dBm                      | 20 MHz | WCDMA signal *             |
+| Note*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] |                               |        |                            |
+
+**Table 4.15: Narrowband intermodulation performance requirement (Medium Range LMU)**
+
+| Operating band                    | Interfering Signal mean power | Offset  | Type of Interfering Signal |
+|-----------------------------------|-------------------------------|---------|----------------------------|
+| II, III, IV, V, VIII, X           | - 43 dBm                      | 3.5 MHz | CW signal                  |
+|                                   | - 43 dBm                      | 5.9 MHz | GMSK modulated*            |
+| * GMSK as defined in TS45.004 [2] |                               |         |                            |
+
+## 5.8 Spurious emissions
+
+The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the LMU antenna connector.
+
+The power of any spurious emission shall not exceed:
+
+**Table 4.16: General LMU spurious emission requirement**
+
+| Band              | Maximum level | Measurement Bandwidth | Note                                                                                                                                                |
+|-------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| 30MHz – 1 GHz     | -57 dBm       | 100 kHz               |                                                                                                                                                     |
+| 1 GHz – 12.75 GHz | -47 dBm       | 1 MHz                 | With the exception of frequencies between 12.5 MHz below the first carrier frequency and 12.5 MHz above the last carrier frequency used by the LMU. |
+
+In addition the following requirements shall be applied for the protection of UE, MS, and Node B, BS of the same and other systems, where the power of any spurious emission shall not exceed the limits:
+
+**Table 4.17: Additional LMU Spurious emissions limits**
+
+| Operating Band | Band                | Maximum level | Measurement Bandwidth | Note |
+|----------------|---------------------|---------------|-----------------------|------|
+| I              | 1920 – 1980 MHz     | -78 dBm       | 3.84 MHz              |      |
+| II             | 1850 – 1910 MHz     | -78 dBm       | 3.84 MHz              |      |
+| III            | 1710 – 1785 MHz     | -78 dBm       | 3.84 MHz              |      |
+| IV             | 1710 – 1755 MHz     | -78 dBm       | 3.84 MHz              |      |
+| V              | 824 – 849 MHz       | -78 dBm       | 3.84 MHz              |      |
+| VI             | 815 – 850 MHz       | -78 dBm       | 3.84 MHz              |      |
+| VII            | 2500 – 2570 MHz     | -78 dBm       | 3.84 MHz              |      |
+| VIII           | 880 – 915 MHz       | -78 dBm       | 3.84 MHz              |      |
+| IX             | 1749.9 – 1784.9 MHz | -78 dBm       | 3.84 MHz              |      |
+| X              | 1710 – 1770 MHz     | -78 dBm       | 3.84 MHz              |      |
+
+In addition, the requirement in Table 4.18 may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed.
+
+**Table 4.18: Additional spurious emission requirements for the TDD bands**
+
+| Operating Band | Band                               | Maximum level | Measurement Bandwidth | Note                    |
+|----------------|------------------------------------|---------------|-----------------------|-------------------------|
+| I              | 1900 – 1920 MHz<br>2010 – 2025 MHz | -78 dBm       | 3.84 MHz              | Not applicable in Japan |
+|                | 2010 – 2025 MHz                    | -52 dBm       | 1MHz                  | Applicable in Japan     |
+| VI, IX         | 2010 – 2025 MHz                    | -52 dBm       | 1MHz                  |                         |
+
+# 6 LMU measurement requirements
+
+## 6.1 General
+
+All tests at specified detection levels require that the LMU detection threshold be set such that the false alarm rate is at or below 5 % when no signal is present (noise only).
+
+## 6.2 RRC States supported
+
+UTDOA positioning technique does work in CELL\_DCH and CELL\_FACH state, not in URA\_PCH nor CELL\_PCH state.
+
+## 6.3 Maximum response times
+
+- 1) The maximum time for a Master LMU to establish a reference signal shall be, after the data capture has started, less than 5 seconds.
+- 2) The maximum time for the distribution of the reference signal to another LMU involved in the positioning shall be less than 3 seconds.
+- 3) The maximum time of detection of the time of arrival in an LMU given the reference signal shall be less than 15 seconds.
+
+## 6.4 Nominal time accuracy
+
+Nominal Time Accuracy requirement verifies the difference between the detected time of arrival and the real time of arrival.
+
+In an AWGN environment with no fading or multi-paths, the standard deviation of the timing error of the LMU shall be less than 30 ns when the signal presence is correctly detected.
+
+## 6.5 Multipath scenarios
+
+The purpose of the test case is to verify the LMU receiver's performance in multipath.
+
+For the 12.2 kbps reference measurement channel specified in 3GPP TS 25.104 Annex A [1], and with Rx diversity (using both diversity paths), the LMU shall be capable of detecting the earliest path, for at least 90 % of the location attempts, at the levels in Table 5.1.
+
+Nominal time accuracy for multipath fading scenarios includes an additional chip duration of 260 nanoseconds over that in Section 5.4.
+
+**Table 5.1: Multipath detection level**
+
+| Propagation condition   | Detection level: Signal to Noise level in (dB) | Note   |
+|-------------------------|------------------------------------------------|--------|
+| Static (AWGN)           | -51.2 dB                                       | NOTE 1 |
+| Multipath fading Case 1 | -47.2dB                                        | NOTE 2 |
+| Multipath fading Case 2 | - 43.8 dB                                      | NOTE 2 |
+| Multipath fading Case 3 | - 41.9 dB                                      | NOTE 2 |
+| Multipath fading Case 4 | - 39.8 dB                                      | NOTE 2 |
+
+NOTE 1: Static propagation condition is described in 3GPP TS 25.104 Annex B.1 [1].
+
+NOTE 2: Multipath-fading case 1-4 is described in 3GPP TS 25.104 Annex B.2 [1].
+
+## 6.6 Moving scenario
+
+The purpose of the test case is to verify the LMU receiver's performance to Doppler shift.
+
+In an AWGN environment with no fading or multi-paths, and at a speed of 250km/h, the detectability of the LMU shall be degraded by no more than 1.5 dB.
+
+## 6.7 Cross correlation
+
+The ability of the LMU to detect a weak terminal signal in the presence of a strong other terminal is covered in Section 5.5 when the other terminal interference is modelled as AWGN.
+

marked/Rel-17/25_series/25113/raw.md

@@ -0,0 +1,1191 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                 |    |
+|---------------------------------------------------------------------------------|----|
+| Foreword .....                                                                  | 5  |
+| 1 Scope.....                                                                    | 6  |
+| 2 References.....                                                               | 6  |
+| 3 Definitions, symbols and abbreviations.....                                   | 7  |
+| 3.1 Definitions .....                                                           | 8  |
+| 3.2 Symbols .....                                                               | 9  |
+| 3.3 Abbreviations .....                                                         | 9  |
+| 4 Test conditions .....                                                         | 10 |
+| 4.1 General .....                                                               | 10 |
+| 4.2 Arrangements for establishing a communication link.....                     | 10 |
+| 4.2.1 Multiple enclosure BS solution.....                                       | 10 |
+| 4.3 Narrow band responses on receivers .....                                    | 11 |
+| 4.3.1 FDD and 3,84 Mcps TDD option .....                                        | 11 |
+| 4.3.2 1,28 Mcps TDD option .....                                                | 11 |
+| 4.4 Test condition for Repeater .....                                           | 11 |
+| 4.4.1 Arrangements for test signals for repeaters .....                         | 12 |
+| 4.5 Exclusion bands.....                                                        | 12 |
+| 4.5.1 Transmitter exclusion band.....                                           | 12 |
+| 4.5.2 Receiver exclusion band .....                                             | 12 |
+| 4.6 BS test configurations.....                                                 | 13 |
+| 5 Performance assessment .....                                                  | 13 |
+| 5.1 General .....                                                               | 13 |
+| 5.2 Assessment of BLER in Downlink.....                                         | 14 |
+| 5.3 Assessment of BLER in Uplink .....                                          | 14 |
+| 5.4 Ancillary equipment .....                                                   | 14 |
+| 5.5 Repeaters .....                                                             | 14 |
+| 6 Performance Criteria.....                                                     | 14 |
+| 6.1 Performance criteria for continuous phenomena for BS .....                  | 14 |
+| 6.2 Performance criteria for transient phenomena for BS.....                    | 15 |
+| 6.3 (void) .....                                                                | 15 |
+| 6.4 Performance criteria for continuous phenomena for Ancillary equipment ..... | 15 |
+| 6.5 Performance criteria for transient phenomena for Ancillary equipment.....   | 16 |
+| 6.6 (void) .....                                                                | 16 |
+| 6.7 Performance criteria for continuous phenomena for repeaters.....            | 16 |
+| 6.8 Performance criteria for transient phenomena for repeaters .....            | 16 |
+| 6.9 (void) .....                                                                | 17 |
+| 7 Applicability overview .....                                                  | 17 |
+| 7.1 Emission .....                                                              | 17 |
+| 7.2 Immunity .....                                                              | 18 |
+| 7.3 Applicability of requirements in TS 37.113 .....                            | 18 |
+| 8 Emission.....                                                                 | 20 |
+| 8.1 Methods of measurement and limits for EMC emissions .....                   | 20 |
+| 8.2 Test configurations .....                                                   | 20 |
+| 8.3 Radiated emission from Base station, Repeater and ancillary equipment.....  | 20 |
+| 8.3.1 Radiated emission, Base stations and Repeater .....                       | 20 |
+| 8.3.1.1 Definition .....                                                        | 20 |
+| 8.3.1.2 Test method.....                                                        | 20 |
+| 8.3.1.2.1 FDD and 3,84 Mcps TDD option.....                                     | 20 |
+| 8.3.1.2.2 1,28 Mcps TDD option.....                                             | 21 |
+| 8.3.1.3 Limits .....                                                            | 21 |
+| 8.3.1.3.1 FDD and 3,84 Mcps TDD option.....                                     | 21 |
+| 8.3.1.3.2 1,28 Mcps TDD option.....                                             | 22 |
+| 8.3.1.4 Interpretation of the measurement results .....                         | 22 |
+| 8.3.2 Radiated emission, Ancillary equipment.....                               | 23 |
+
+|                        |                                                                                   |    |
+|------------------------|-----------------------------------------------------------------------------------|----|
+| 8.3.2.1                | Definition .....                                                                  | 23 |
+| 8.3.2.2                | Test method.....                                                                  | 23 |
+| 8.3.2.3                | Limits .....                                                                      | 23 |
+| 8.4                    | Conducted emission DC power input/output port .....                               | 23 |
+| 8.4.1                  | Definition .....                                                                  | 24 |
+| 8.4.2                  | Test method.....                                                                  | 24 |
+| 8.4.3                  | Limits .....                                                                      | 24 |
+| 8.5                    | Conducted emissions, AC mains power input/output port .....                       | 24 |
+| 8.5.1                  | Definition .....                                                                  | 24 |
+| 8.5.2                  | Test method.....                                                                  | 24 |
+| 8.5.3                  | Limits .....                                                                      | 25 |
+| 8.6                    | Harmonic Current emissions (AC mains input port).....                             | 25 |
+| 8.7                    | Voltage fluctuations and flicker (AC mains input port) .....                      | 25 |
+| 8.8                    | Telecommunication ports .....                                                     | 25 |
+| 8.8.1                  | Definition .....                                                                  | 25 |
+| 8.8.2                  | Test method.....                                                                  | 25 |
+| 8.8.3                  | Limits .....                                                                      | 26 |
+| 9                      | Immunity.....                                                                     | 26 |
+| 9.1                    | Test methods and levels for immunity tests .....                                  | 26 |
+| 9.2                    | Test configurations .....                                                         | 26 |
+| 9.3                    | RF electromagnetic field (80 MHz - 6000 MHz).....                                 | 27 |
+| 9.3.1                  | Definition .....                                                                  | 27 |
+| 9.3.2                  | Test method and level.....                                                        | 27 |
+| 9.3.3                  | Performance criteria.....                                                         | 28 |
+| 9.4                    | Electrostatic discharge.....                                                      | 28 |
+| 9.4.1                  | Definition .....                                                                  | 28 |
+| 9.4.2                  | Test method and level.....                                                        | 28 |
+| 9.4.3                  | Performance criteria.....                                                         | 28 |
+| 9.5                    | Fast transients common mode .....                                                 | 28 |
+| 9.5.1                  | Definition .....                                                                  | 29 |
+| 9.5.2                  | Test method and level.....                                                        | 29 |
+| 9.5.3                  | Performance criteria.....                                                         | 29 |
+| 9.6                    | RF common mode (0,15 MHz - 80 MHz).....                                           | 29 |
+| 9.6.1                  | Definition .....                                                                  | 29 |
+| 9.6.2                  | Test method and level.....                                                        | 29 |
+| 9.6.3                  | Performance criteria.....                                                         | 30 |
+| 9.7                    | Voltage dips and interruptions.....                                               | 30 |
+| 9.7.1                  | Definition .....                                                                  | 30 |
+| 9.7.2                  | Test method and level.....                                                        | 30 |
+| 9.7.3                  | Performance criteria.....                                                         | 30 |
+| 9.8                    | Surges, common and differential mode.....                                         | 31 |
+| 9.8.1                  | Definition .....                                                                  | 31 |
+| 9.8.2                  | Test method and level.....                                                        | 31 |
+| 9.8.2.1                | Test method for telecommunication ports directly connected to outdoor cables..... | 31 |
+| 9.8.2.2                | Test method for telecommunication ports connected to indoor cables.....           | 31 |
+| 9.8.2.3                | Test method for AC power ports.....                                               | 32 |
+| 9.8.3                  | Performance criteria.....                                                         | 32 |
+| Annex A (informative): | Change History.....                                                               | 33 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 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 specification.
+
+# --- 1 Scope
+
+The present document covers the assessment of base stations, repeaters and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC).
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations, repeaters and associated ancillary equipment in one of the following categories:
+
+- base stations for the FDD mode of UTRA meeting the requirements of TS 25.104 [1], with conformance demonstrated by compliance to TS 25.141 [3].
+- base stations for both options of the TDD mode of UTRA meeting the requirements of TS 25.105 [2], with conformance demonstrated by compliance to TS 25.142 [4]. The two options are the 3,84 Mcps and 1,28 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate.
+- repeaters for the FDD mode of UTRA meeting the requirements of TS 25.106 [10], with conformance demonstrated by compliance to TS 25.143 [11].
+
+Technical requirements related to the antenna port of base stations or repeaters are not included in the present document. These are found in the relevant product standards [1], [2], [3], [4], [10], [11].
+
+The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [5] and IEC 61000-6-3 [6].
+
+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 TS 25.104: "UTRA (BS) FDD; Radio transmission and reception".
+- [2] 3GPP TS 25.105: "UTRA (BS) TDD; Radio transmission and reception".
+- [3] 3GPP TS 25.141: "UTRA (BS) FDD; Base station conformance testing (FDD)".
+- [4] 3GPP TS 25.142: "UTRA (BS) TDD; Base station conformance testing (TDD)".
+- [5] IEC 61000-6-1: 2005; "Electromagnetic compatibility (EMC) - Part 6: Generic standards - Section 1: Immunity for residential, commercial and light-industrial environments".
+- [6] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6: Generic standards - Section 3: Emission standard for residential, commercial and light industrial environments".
+- [7] IEC 60050(161): "International Electrotechnical Vocabulary - Chapter 161: Electromagnetic compatibility".
+- [8] 3GPP TS 25.101: "UTRA (UE) FDD; UE Radio transmission and reception (FDD)".
+- [9] 3GPP TS 25.102: "UTRA (UE) TDD; UE Radio transmission and reception (TDD)".
+
+- [10] 3GPP TS 25.106: "UTRA Repeater; Radio Transmission and Reception".
+- [11] 3GPP TS 25.143: "UTRA Repeater conformance testing".
+- [12] ITU-R Rec. SM.329: "Unwanted emissions in the spurious domain".
+- [13] Void
+- [14] CISPR 16-1-1: "Specification for radio disturbance and immunity measuring apparatus and methods - Measuring apparatus".
+- [15] IEC 61000-3-2 (2004): "Electromagnetic compatibility (EMC) - Part 3: Limits - Section 2: Limits for harmonic current emissions (equipment input current  $\leq 16$  A)".
+- [16] IEC 61000-3-3 (2002): "Electromagnetic compatibility (EMC) - Part 3: Limits - Section 3: Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 16$  A".
+- [17] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 2: Electrostatic discharge immunity test".
+- [18] IEC 61000-4-3: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 3: Radiated, radio-frequency electromagnetic field immunity test".
+- [19] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 4: Electrical fast transient/burst immunity test".
+- [20] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 5: Surge immunity test".
+- [21] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 6: Immunity to contacted disturbances, induced by radio frequency fields".
+- [22] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4: Testing and measurement techniques - Section 11: Voltage dips, short interruptions and voltage variations. Immunity tests".
+- [23] ITU-R Recommendation SM.1539 (2001): "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329".
+- [24] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [25] IEC 61000-3-12 (2005): "Electromagnetic compatibility (EMC) - Part 3-12: Limits- Limits for harmonic current produced by equipment connected to public low-voltage system with input current  $> 16$  A and  $\leq 75$  A".
+- [26] IEC 61000-3-11 (2000): "Electromagnetic compatibility (EMC) - Part 3-11: Limits – Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 75$  A and subject to conditional connections"
+- [27] 3GPP TS 37.113: “E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)”.
+- [28] CISPR 32: “Electromagnetic compatibility of multimedia equipment - Emission requirements”.
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Ancillary equipment:** Equipment (apparatus), used in connection with a receiver, transmitter or transceiver is considered as an ancillary equipment (apparatus) if:
+
+- the equipment is intended for use in conjunction with a receiver, transmitter or transceiver to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and
+- the equipment cannot be used on a stand-alone basis to provide user functions independently of a receiver, transmitter or transceiver; and
+- the receiver, transmitter or transceiver to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions).
+
+**Base Station equipment:** Radio and/or ancillary equipment intended for operation at a fixed location and powered directly or indirectly (e.g. via an AC/DC converter or power supply) by AC mains network, or an extended local DC mains network.
+
+**BLER:** BLER is block error ratio. The BLER calculation shall be based on evaluating the CRC on each transport block.
+
+**Continuous phenomena (continuous disturbance):** Electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [7]).
+
+**Multi-band Base Station:** Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s).
+
+**Pass band:** The repeater can have one or several pass bands. The pass band is the frequency range that the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band.
+
+**Port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on an equipment intended for connection of cables to or from that equipment is considered as a port (see figure 1).
+
+**Radio communications equipment :** Telecommunications equipment which includes one or more transmitters and/or receivers and/or parts thereof for use in a fixed, mobile or portable application. It can be operated with ancillary equipment but if so, is not dependent on it for basic functionality.
+
+**Radio equipment:** Equipment which contains Radio digital unit and Radio unit.
+
+**Radio digital unit:** Equipment which contains base band and functionality for controlling Radio unit.
+
+**Radio unit:** Equipment which contains transmitter and/or receiver.
+
+**Receiver exclusion band:** The receiver exclusion band is the band of frequencies over which no tests of radiated immunity of a receiver are made. The exclusion band for receivers is expressed relative to the base station receive band.
+
+**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). In operating bands specified with only down-link or up-link, only the up-link or down-link as specified for the operating band is repeated.
+
+**Signal and control :** Port which carries information or control signals, excluding antenna ports.
+
+**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.
+
+**Transient phenomena:** Pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [7]).
+
+**Transmitter exclusion band:** The transmitter exclusion band is the band of frequencies over which no tests of radiated immunity of a transmitter are made. The exclusion band for transmitters is expressed relative to the carrier frequencies used (the carrier frequencies of the base stations activated transmitter(s).)
+
+![Diagram of an Apparatus with various ports.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram shows a central rectangle labeled "Apparatus" enclosed within a larger rectangle labeled "Enclosure Port". On the left side, three lines extend from the "Apparatus" rectangle to the "Enclosure Port" boundary, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". On the right side, three lines extend from the "Apparatus" rectangle to the "Enclosure Port" boundary, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port".
+
+Diagram of an Apparatus with various ports.
+
+**Figure 1: Examples of ports**
+
+![Diagram of BS Equipment with a single enclosure solution.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+The diagram shows a large rectangle labeled "BS Equipment". Inside this rectangle, on the right side, is a smaller rectangle labeled "Radio Equipment".
+
+Diagram of BS Equipment with a single enclosure solution.
+
+**Figure 1A: BS with single enclosure solution**
+
+![Diagram of BS Equipment with a multiple enclosure solution.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+The diagram shows a large rectangle labeled "BS Equipment". Inside this rectangle, on the left, is a dashed rectangle labeled "Radio Equipment". Within this dashed rectangle, there are two solid rectangles: "Radio digital unit" on the left and "Radio unit" on the right, connected by a horizontal line. The "Radio digital unit" is partially outside the dashed rectangle but inside the "BS Equipment" rectangle.
+
+Diagram of BS Equipment with a multiple enclosure solution.
+
+**Figure 1B: BS with multiple enclosure solution**
+
+## 3.2 Symbols
+
+(void)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [24] and the following apply:
+
+|     |                               |
+|-----|-------------------------------|
+| AC  | Alternating Current           |
+| AMN | Artificial Mains Network      |
+| CDN | Coupling/Decoupling Network   |
+| DC  | Direct Current                |
+| EMC | Electromagnetic Compatibility |
+| ESD | Electrostatic discharge       |
+| EUT | Equipment Under Test          |
+
+|      |                                    |
+|------|------------------------------------|
+| RF   | Radio frequency                    |
+| rms  | root mean square                   |
+| UTRA | Universal Terrestrial Radio Access |
+
+# --- 4 Test conditions
+
+## 4.1 General
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 25.141 [3] or TS 25.142 [4] or in the UTRA Repeater conformance testing specification TS25.143 [11]. The test conditions shall be recorded in the test report.
+
+For an EUT which contains more than one BS, it is sufficient to perform tests relating to each type of port of each representative type of the BS forming part of the EUT.
+
+For BS capable of multi-band operation, the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands shall be activated according to the test configuration in subclause 4.6. Tests shall be performed relating to each type of port and all bands shall be assessed during the tests.
+
+## 4.2 Arrangements for establishing a communication link
+
+The wanted RF input signal nominal frequency shall be selected by setting the UTRA Absolute Radio Frequency Channel Number (UARFCN) to an appropriate number.
+
+A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the air interface and/or the Iub interface. The test system shall be located outside of the test environment.
+
+When the EUT is required to be in the transmit/receive mode, the following conditions shall be met:
+
+- the EUT shall be commanded to operate at maximum rated transmit power;
+- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment;
+- The wanted input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects e.g. 15 dB above the reference sensitivity level as defined in TS 25.141 (for FDD) [3] or TS 25.142 (for TDD) [4], to provide a stable communication link.
+
+For immunity tests subclause 4.3 shall apply and the conditions shall be as follows:
+
+### 4.2.1 Multiple enclosure BS solution
+
+For a BS with multiple enclosures, the BS part with Radio digital unit and the Radio unit may be tested separately. Communication link shall be set up in the same way as if they are in single BS enclosure. The Radio Digital unit and the Radio unit shall communicate over an interface enabling establishment of a communication link.
+
+## 4.3 Narrow band responses on receivers
+
+### 4.3.1 FDD and 3,84 Mcps TDD option
+
+Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method:
+
+- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by 10 MHz;
+- if the deviation disappears in either or both of the above 10 MHz offset cases, then the response is considered as a narrow band response;
+
+- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to 12,5 MHz;
+- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test.
+
+Narrow band responses are disregarded.
+
+For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses.
+
+### 4.3.2 1,28 Mcps TDD option
+
+For 1.28Mcps chip rate TDD option, responses on receivers or duplex transceivers occurring during the test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method:
+
+- if during an immunity test the quantity being monitored goes outside the specified tolerances, it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by 3.2MHz;
+- if the deviation disappears in either or both of the above 3.2 MHz offset cases, then the response is considered as a narrow band response;
+- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to 4MHz;
+- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test.
+
+Narrow band responses are disregarded.
+
+For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses.
+
+## 4.4 Test condition for Repeater
+
+The wanted RF input signal nominal frequency shall be selected by setting the Absolute Radio Frequency Channel Number (ARFCN) to an appropriate number within the pass band of the Repeater.
+
+The Repeater path shall be tested with a suitable test system capable of measuring RF performance criteria (hereafter called "the test system"). The test system shall be located outside of the test environment.
+
+When the EUT is required to be in the operational mode, the following conditions shall be met:
+
+- the EUT shall be commanded to operate at maximum rated gain;
+- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment;
+
+For immunity tests conditions subclause 4.3 shall apply.
+
+### 4.4.1 Arrangements for test signals for repeaters
+
+For immunity tests of repeaters, the wanted RF input signal shall be coupled to one antenna port at a level which will result, when measured, in the maximum rated RF output power per channel, as declared by the manufacturer. The test shall either be repeated with a wanted signal coupled to the other antenna port, or a single test shall be performed with the specified input signals being simultaneously coupled to both antenna ports.
+
+## 4.5 Exclusion bands
+
+### 4.5.1 Transmitter exclusion band
+
+For the purpose of EMC specifications there shall be a transmitter exclusion band.
+
+For UTRA FDD:
+
+Lower carrier frequency used - 12,5 MHz. to upper carrier frequency used + 12,5 MHz.
+
+#### For UTRA 3,84 Mcps TDD option:
+
+Lower carrier frequency used - 12,5 MHz. to upper carrier frequency used + 12,5 MHz.
+
+#### For UTRA 1,28 Mcps TDD option:
+
+Lower carrier frequency used - 4 MHz to upper carrier frequency used + 4 MHz.
+
+#### For UTRA 7,68 Mcps TDD option:
+
+Lower carrier frequency used - 25 MHz. to upper carrier frequency used + 25 MHz.
+
+### 4.5.2 Receiver exclusion band
+
+The receiver exclusion band for base stations extends from the lower frequency of the Base Station receive band minus 20 MHz to the upper frequency of the Base Station receive band plus 20 MHz. The exclusion bands are as set out below:
+
+#### UTRA FDD:
+
+- a) 1900 MHz to 2000 MHz (Band I)
+- b) 1830 MHz to 1930 MHz (Band II)
+- c) 1690 MHz to 1805 MHz (Band III)
+- d) 1690 MHz to 1775 MHz (Band IV)
+- e) 804 MHz to 869 MHz (Band V)
+- f) 810 MHz to 860 MHz (Band VI)
+- g) 2480 MHz to 2590 MHz (Band VII)
+- h) 860 MHz to 935 MHz (Band VIII)
+- i) 1729.9 MHz to 1804.9 MHz (Band IX)
+- j) 1690 MHz to 1790 MHz (Band X)
+- k) 1407.9 MHz to 1467.9 MHz (Band XI)
+- l) 679-736 MHz (Band XII)
+- m) 757-807 MHz (Band XIII)
+- n) 768-818 MHz (Band XIV)
+- o) 810-865 MHz (Band XIX)
+- p) 712-782 MHz (Band XX)
+- q) 1427.9-1482.9 MHz (Band XXI)
+- r) 3390-3510 MHz (Band XXII)
+- s) 1830 MHz to 1935 MHz (Band XXV)
+- t) 794 MHz to 869 MHz (Band XXVI)
+- u) N/A (Band XXXII)
+
+#### UTRA 3,84 Mcps TDD option, UTRA 1,28 Mcps TDD option and UTRA 7,68 Mcps TDD option:
+
+- a) 1880 MHz to 1940 MHz  
+1990 MHz to 2045 MHz
+
+- b) 1830 MHz to 2010 MHz
+- c) 1890 MHz to 1950 MHz
+- d) 2550 MHz to 2640MHz
+- e) 2280MHz to 2420MHz
+- f) 1860 MHz to 1940 MHz
+
+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 the BS.
+
+## 4.6 BS test configurations
+
+The present clause defines the BS test configurations that shall be used for demonstrating conformance. A single UTRA carrier shall be used for testing of single-carrier capable BS. For other BS types, the test configurations in Table 4.6.1 shall be used. The test configurations (UTCx) are defined in TS 25.141 [3], subclause 4.12.
+
+**Table 4.6.1: Test configurations for UTRA BS**
+
+| BS test case                                                                                                                                                                                           | BS capable of multi-carrier operation in contiguous spectrum in single band only | BS capable of multi-carrier operation in both contiguous and non-contiguous spectrum in single band | BS capable of multi-band operation |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------|
+| Emission tests                                                                                                                                                                                         | UTC1                                                                             | UTC2                                                                                                | UTC1/2 (Note 1), UTC4              |
+| Immunity tests                                                                                                                                                                                         | UTC1                                                                             | UTC2                                                                                                | UTC1/2 (Note 1), UTC4              |
+| NOTE 1: UTC1 or UTC2 shall be applied in each supported operating band according to the respective capability in each band, as defined in the 2 <sup>nd</sup> and 3 <sup>rd</sup> column of the table. |                                                                                  |                                                                                                     |                                    |
+
+# 5 Performance assessment
+
+## 5.1 General
+
+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 band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation;
+- an exhaustive list of ports, classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+Performance assessment of a BS with multiple enclosures may be done separately for the BS part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice.
+
+A communication link used by more than one operating band shall be assessed on all operating bands. Communication link(s) and/or radio performance parameters for the operating bands can during the test be assessed simultaneously or separately for each band, depending on the test environment capability.
+
+## 5.2 Assessment of BLER in Downlink
+
+The output of the transmitter shall be connected to an equipment which meet the requirements for the BLER assessment of TS25.101 [8] in case of FDD and TS25.102 [9] in case of TDD for the bearer used in the immunity tests. The level of the signal supplied to the equipment should be within the range for which the assessment of BLER is not impaired. Power control shall be off during the immunity testing.
+
+## 5.3 Assessment of BLER in Uplink
+
+The value of the BLER at the output of the receiver shall be monitored at Iub-interface by using suitable test equipment.
+
+## 5.4 Ancillary equipment
+
+At the manufacturer's discretion the test may be performed on the ancillary equipment separately or a representative configuration of the combination of radio and ancillary equipment. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the ancillary equipment to be used with different radio equipment.
+
+## 5.5 Repeaters
+
+The parameter used for assessment of performance of a repeater is the gain within the pass band.
+
+# 6 Performance Criteria
+
+## 6.1 Performance criteria for continuous phenomena for BS
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and BLER defined in Table 1. If the test is not performed using one of these bearers (for, example, of none of them are supported by the BS), the characteristics of the bearer used shall be recorded in the test report.
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in Table 1 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the value shown in Table 1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 1: BS Performance Criteria for continuous phenomena for BS**
+
+| <b>Bearer Information<br/>Data Rate</b> | <b>Performance Criteria</b>            |
+|-----------------------------------------|----------------------------------------|
+| 12.2 kbps                               | BLER < $10^{-2}$<br>No loss of service |
+| 64 kbps                                 | BLER < $10^{-2}$<br>No loss of service |
+| 144 kbps                                | BLER < $10^{-2}$<br>No loss of service |
+| 384 kbps                                | BLER < $10^{-2}$<br>No loss of service |
+
+NOTE: The performance criteria, BLER <  $10^{-2}$  / No loss of service, applies also if a bearer with another characteristics is used in the test.
+
+## 6.2 Performance criteria for transient phenomena for BS
+
+The test should be, where possible, be performed using a bearer with the characteristics of data rate and BLER defined in Table 2. If the test is not performed using one of these bearers (for, example, of none of them are supported by the BS), the characteristics of the bearer used shall be recorded.
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 2 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the value shown in Table 2. After
+
+each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 2: BS Performance Criteria for transient phenomena for BS**
+
+| <b>Bearer Information Data Rate</b> | <b>Performance Criteria</b>                                                      |
+|-------------------------------------|----------------------------------------------------------------------------------|
+| 12.2 kbps                           | BLER > $10^{-2}$ temporarily, however the communication link shall be maintained |
+| 64 kbps                             | BLER > $10^{-2}$ temporarily, however the communication link shall be maintained |
+| 144 kbps                            | BLER > $10^{-2}$ temporarily, however the communication link shall be maintained |
+| 384 kbps                            | BLER > $10^{-2}$ temporarily, however the communication link shall be maintained |
+
+NOTE: The performance criteria, BLER >  $10^{-2}$  temporarily / however the communication link shall be maintained, applies also if a bearer with another characteristics is used in the test.
+
+## 6.3 (void)
+
+## 6.4 Performance criteria for continuous phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss of performance. If the minimum performance level or the permissible performance loss is not specified by the manufacture, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+## 6.5 Performance criteria for transient phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss of performance. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacture, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+## 6.6 (void)
+
+## 6.7 Performance criteria for continuous phenomena for repeaters
+
+The gain of the EUT shall be measured throughout the period of exposure of the phenomenon. The gain measured during the test shall not change from the gain measured before the test by more than  $\pm 1$  dB. At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data.
+
+## 6.8 Performance criteria for transient phenomena for repeaters
+
+The gain of the EUT shall be measured before the test and after each exposure. At the conclusion of each exposure the gain of the EUT shall not have changed by more than  $\pm 1$  dB. At the conclusion of the total test comprising the series of individual exposures, the EUT shall operate as intended with no loss of user control functions or stored data, as declared by the manufacturer, and the gain of the EUT shall not have changed by more than  $\pm 1$  dB.
+
+## 6.9 (void)
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+**Table 3: Emission applicability**
+
+| Phenomenon                       | Application                | Equipment test requirement |                     |            | Reference subclause in the present document | Reference Standard                        |
+|----------------------------------|----------------------------|----------------------------|---------------------|------------|---------------------------------------------|-------------------------------------------|
+|                                  |                            | BS equipment               | Ancillary equipment | Repeater   |                                             |                                           |
+| Radiated emission (NOTE 2)       | Enclosure                  | applicable                 |                     | applicable | 8.3.1                                       | ITU-R SM.329 [12]                         |
+| Radiated emission                | Enclosure                  |                            | applicable          |            | 8.3.2                                       | CISPR 32 [28]                             |
+| Conducted emission               | DC power input/output port | applicable                 | applicable          | applicable | 8.4                                         | CISPR 32 [28], CISPR 16-1-1 [14]          |
+| Conducted emission               | AC mains input/output port | applicable                 | applicable          | applicable | 8.5                                         | CISPR 32 [28]                             |
+| Harmonic current emissions       | AC mains input port        | applicable                 | applicable          | applicable | 8.6                                         | IEC 61000-3-2 [15] or IEC 61000-3-12 [25] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                 | applicable          | applicable | 8.7                                         | IEC 61000-3-3 [16] or IEC 61000-3-11 [26] |
+| Conducted emission               | Telecommunication port     | applicable                 | applicable          | applicable | 8.8                                         | CISPR 32 [28]                             |
+
+NOTE 1: Spurious emissions from antenna connector shall be measured according to TS 25.141 [3] and TS 25.142 [4] and TS 25.143 [11].
+
+NOTE 2: The radiated emissions requirement for the BS equipment covers radiated emissions in the spurious domain. Note that in ETSI standards and in 3GPP GERAN specifications it is considered a part of radio aspects.
+
+## 7.2 Immunity
+
+**Table 4: Immunity applicability**
+
+| Phenomenon                               | Application                                                               | Equipment test requirement |                     |            | Reference subclause in the present document | Reference standard |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|------------|---------------------------------------------|--------------------|
+|                                          |                                                                           | BS equipment               | Ancillary equipment | Repeater   |                                             |                    |
+| RF electromagnetic field (80 - 6000 MHz) | Enclosure                                                                 | applicable                 | applicable          | applicable | 9.3                                         | IEC 61000-4-3 [18] |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | applicable          | applicable | 9.4                                         | IEC 61000-4-2 [17] |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | applicable | 9.5                                         | IEC 61000-4-4 [19] |
+| RF common mode 0,15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | applicable | 9.6                                         | IEC 61000-4-6 [21] |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | applicable          | applicable | 9.7                                         | IEC 61000-4-11     |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | applicable          | applicable | 9.8                                         | IEC 61000-4-5 [20] |
+
+## 7.3 Applicability of requirements in TS 37.113
+
+For a BS that is UTRA (single-RAT) capable only, the requirements in the present document are applicable and additional conformance to TS 37.113 [27] is optional. For a BS additionally conforming to TS 37.113 [27], conformance to some of the emission test requirements in the present document can be demonstrated through the corresponding requirements in TS 37.113 [27] as listed in Table 4A and conformance to some of the immunity test requirements in the present document can be demonstrated through the corresponding requirements in TS 37.113 [27] as listed in Table 4B.
+
+**Table 4A: Alternative emission test requirements for a BS additionally conforming to TS 37.113 [27]**
+
+| Phenomenon                       | Application                | Clause in the present document | Alternative clause in TS 37.113 [27] |
+|----------------------------------|----------------------------|--------------------------------|--------------------------------------|
+| Radiated emission                | Enclosure                  | 8.3.1                          | 8.2.1                                |
+| Conducted emission               | DC power input/output port | 8.4                            | 8.3                                  |
+| Conducted emission               | AC mains input/output port | 8.5                            | 8.4                                  |
+| Harmonic current emissions       | AC mains input port        | 8.6                            | 8.5                                  |
+| Voltage fluctuations and flicker | AC mains input port        | 8.7                            | 8.6                                  |
+| Conducted emission               | Telecommunication port     | 8.8                            | 8.7                                  |
+
+**Table 4B: Alternative immunity test requirements for a BS additionally conforming to TS 37.113 [27]**
+
+| <b>Phenomenon</b>                        | <b>Application</b>                                                        | <b>Clause in the present document</b> | <b>Alternative clause in TS 37.113 [27]</b> |
+|------------------------------------------|---------------------------------------------------------------------------|---------------------------------------|---------------------------------------------|
+| RF electromagnetic field (80 - 6000 MHz) | Enclosure                                                                 | 9.3                                   | 9.2                                         |
+| Electrostatic discharge                  | Enclosure                                                                 | 9.4                                   | 9.3                                         |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | 9.5                                   | 9.4                                         |
+| RF common mode (0,15 - 80 MHz)           | Signal, telecommunications and control ports, DC and AC power input ports | 9.6                                   | 9.5                                         |
+| Voltage dips and interruptions           | AC mains power input ports                                                | 9.7                                   | 9.6                                         |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | 9.8                                   | 9.7                                         |
+
+# 8 Emission
+
+## 8.1 Methods of measurement and limits for EMC emissions
+
+## 8.2 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, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- 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 sections of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter section and receiver section of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.3 Radiated emission from Base station, Repeater and ancillary equipment
+
+### 8.3.1 Radiated emission, Base stations and Repeater
+
+This test is applicable to Base station and Repeater. This test shall be performed on a representative configuration of the Base station or Repeater.
+
+#### 8.3.1.1 Definition
+
+This test assesses the ability of BS and Repeater to limit unwanted emission from the enclosure port.
+
+#### 8.3.1.2 Test method
+
+##### 8.3.1.2.1 FDD and 3,84 Mcps TDD option
+
+- a) A test site fulfilling the requirements of ITU-R SM. 329 [12] shall be used. The BS or Repeater shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads.
+
+Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS or Repeater shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane.
+
+NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p.
+
+$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \quad \text{Ref: ITU-R SM.329 ANNEX 1 [12].}$$
+
+- b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated for measurement of spurious emission for FDD in the TS25.141 [3] and for 3.84 Mcps TDD option in the TS25.142 [4].
+
+In case of a Repeater the gain and the output power shall be set to the maximum value as declared by the manufacturer.
+
+- c) The received power shall be measured over the frequency range 30 MHz to 12.75 GHz, excluding 12.5MHz below the first carrier frequency to 12.5 MHz above the last carrier frequency used. The measurement bandwidth shall be 100 kHz between 30 MHz and 1 GHz and 1 MHz above 1 GHz as given in ITU-R SM.329 [12]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS).
+
+##### 8.3.1.2.2 1,28 Mcps TDD option
+
+- a) A test site fulfilling the requirements of ITU-R SM. 329 [12] shall be used. The BS shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads.
+
+Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarisation plane.
+
+NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p.
+
+$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \quad \text{Ref: ITU-R SM.329 ANNEX 1 [12].}$$
+
+- b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated for measurement of spurious emission for 1.28 Mcps TDD in the TS25.142 [4].
+- c) The received power shall be measured over the frequency range 30 MHz to 12.75 GHz, excluding 4MHz below the first carrier frequency to 4 MHz above the last carrier frequency used. The measurement bandwidth shall be 100 kHz between 30 MHz and 1 GHz and 1 MHz above 1 GHz as given in ITU-R SM.329 [12]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. Unless otherwise stated, all measurements are done as mean power (RMS).
+
+#### 8.3.1.3 Limits
+
+The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [12] and SM.1539 [23].
+
+##### 8.3.1.3.1 FDD and 3,84 Mcps TDD option
+
+The BS or the Repeater shall meet the limits below:
+
+**Table 5: Limits for radiated emissions from BS and repeater**
+
+| Frequency range                                                                                                             | Minimum requirement (e.r.p.)/Reference Bandwidth |
+|-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|
+| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$                                                                                  | -36 dBm/100 kHz                                  |
+| $1 \text{ GHz} \leq f < 12,75 \text{ GHz}$                                                                                  | -30 dBm/ 1MHz                                    |
+| $Fc1 - 12,5 \text{ MHz} < f < Fc2+12,5 \text{ MHz}$ (Note 1)                                                                | Not defined                                      |
+| NOTE 1: For BS capable of multi-band operation, the frequency ranges relating to the carriers of all supported bands apply. |                                                  |
+
+Key:
+
+Fc1: Center frequency of first carrier frequency used by the BS and repeater.
+
+Fc2: Center frequency of last carrier frequency used by the BS and repeater.
+
+##### 8.3.1.3.2 1,28 Mcps TDD option
+
+The BS shall meet the limits below:
+
+**Table 5A: Limits for radiated emissions from BS**
+
+| Frequency range                               | Minimum requirement (e.r.p.)/Reference Bandwidth |
+|-----------------------------------------------|--------------------------------------------------|
+| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$    | -36 dBm/100 kHz                                  |
+| $1 \text{ GHz} \leq f < 12,75 \text{ GHz}$    | -30 dBm/ 1MHz                                    |
+| $Fc1 - 4 \text{ MHz} < f < Fc2+4 \text{ MHz}$ | Not defined                                      |
+
+Key:
+
+Fc1: Center frequency of first carrier frequency used by the BS.
+
+Fc2: Center frequency of last carrier frequency used by the BS.
+
+#### 8.3.1.4 Interpretation of the measurement results
+
+The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows:
+
+- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document;
+- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report;
+- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 5B for BS and repeater.
+
+Table 5B specifies the Maximum measurement uncertainty of the Test System. The Test System shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated.
+
+A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment.
+
+**Table 5B: Maximum measurement uncertainty (BS, and Repeater)**
+
+| Parameter                                              | Uncertainty for EUT dimension $\leq 1$ m | Uncertainty for EUT dimension $> 1$ m |
+|--------------------------------------------------------|------------------------------------------|---------------------------------------|
+| Effective radiated RF power between 30 MHz to 180 MHz  | $\pm 6$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 180 MHz to 4 GHz   | $\pm 4$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 4 GHz to 12,75 GHz | $\pm 6$ dB                               | $\pm 9^*$ dB                          |
+
+\*Note: This value may be reduced to  $\pm 6$  dB when further information on the potential radiation characteristic of the EUT is available.
+
+NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 5B, this equipment can still be used, provided that an adjustment is made follows:
+
+Any additional uncertainty in the Test System over and above that specified in table 5B is used to tighten the Test Requirements - making the test harder to pass. This procedure will ensure that a Test System not compliant with table 5B does not increase the probability of passing an EUT that would otherwise have failed a test if a Test System compliant with table 5B had been used.
+
+### 8.3.2 Radiated emission, Ancillary equipment
+
+This test is applicable to ancillary equipment. This test shall be performed on a representative configuration of the ancillary equipment.
+
+#### 8.3.2.1 Definition
+
+This test assesses the ability of ancillary equipment to limit unwanted emission from the enclosure port.
+
+#### 8.3.2.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28]
+
+#### 8.3.2.3 Limits
+
+The ancillary equipment shall meet the limits according to CISPR 32 [28] shown in table 6 and table 6A.
+
+**Table 6: Limits for radiated emissions from ancillary equipment, measured on a stand-alone basis (10 m measuring distance)**
+
+| Frequency range  | Quasi-peak      |
+|------------------|-----------------|
+| 30 MHz-230 MHz   | 30 dB $\mu$ V/m |
+| 230 MHz-1000 MHz | 37 dB $\mu$ V/m |
+
+**Table 6A: Limits for radiated emissions from ancillary equipment, measured on a stand-alone basis (3 m measuring distance)**
+
+| Frequency range GHz                                        | Average limit dB $\mu$ V/m | Peak limit dB $\mu$ V/m |
+|------------------------------------------------------------|----------------------------|-------------------------|
+| 1 to 3                                                     | 50                         | 70                      |
+| 3 to 6                                                     | 54                         | 74                      |
+| Note: The lower limit applies at the transition frequency. |                            |                         |
+
+## 8.4 Conducted emission 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.5.
+
+This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the DC power input/output ports.
+
+### 8.4.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28] and the Artificial Mains Network (AMN) shall be connected to a DC power source.
+
+In the case of DC output ports, the ports shall be connected via a AMN to a load drawing the rated current of the source.
+
+A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded.
+
+The equipment shall be installed with a ground plane as defined in CISPR 32 [28]. The reference earth point of the AMNs shall be connected to the reference ground plane with a conductor as short as possible.
+
+The measurement receiver shall be in accordance with the requirements of section one of CISPR 16-1 [14].
+
+### 8.4.3 Limits
+
+The equipment shall meet the limits below (including the average limit and the quasi-peak limit) when using, respectively, an average detector receiver and a quasi-peak detector receiver and measured in accordance with the method described in subclause 8.4.2 above. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+The equipment shall meet the limits given in table 7.
+
+**Table 7: Limits for conducted emissions**
+
+| Frequency range | Quasi-peak   | Average      |
+|-----------------|--------------|--------------|
+| >0,15-0,5MHz    | 79dB $\mu$ V | 66dB $\mu$ V |
+| >0,5-30 MHz     | 73dB $\mu$ V | 60dB $\mu$ V |
+
+## 8.5 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, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.5.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the AC mains power input/output ports.
+
+### 8.5.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28].
+
+Mains connected ancillary equipment which is not part of the EUT shall be connected to the mains via a separate AMN. According to CISPR 16-1 [14], the Protective Earth (PE) conductor shall also be terminated by a 50  $\Omega$ /50  $\mu$ H common mode RF impedance.
+
+### 8.5.3 Limits
+
+The equipment shall meet the limits below (including the average limit and the quasi-peak limit) when using, respectively, an average detector receiver and a quasi-peak detector receiver and measured in accordance with the method described in subclause 8.5.2 above. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+**Table 8: Limits for conducted emissions**
+
+| <b>Frequency range</b>                                                                                    | <b>Quasi-peak</b> | <b>Average</b> |
+|-----------------------------------------------------------------------------------------------------------|-------------------|----------------|
+| > 0,15-0,5 MHz                                                                                            | 66 - 56 dBμV      | 56 - 46 dBμV   |
+| > 0.5- 5 MHz                                                                                              | 56 dBμV           | 46 dBμV        |
+| > 5-30 MHz                                                                                                | 60 dBμV           | 50 dBμV        |
+| NOTE: The limit decreases linearly with the logarithm of the frequency in the range 0,15 MHz to 0,50 MHz. |                   |                |
+
+Alternatively, for equipment intended to be used in telecommunication centres the limits given in table 9 shall be used.
+
+**Table 9: Limits for conducted emissions**
+
+| <b>Frequency range</b> | <b>Quasi-peak</b> | <b>Average</b> |
+|------------------------|-------------------|----------------|
+| >0,15-0,5MHz           | 79dBμV            | 66dBμV         |
+| >0,5-30 MHz            | 73dBμV            | 60dBμV         |
+
+## 8.6 Harmonic Current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [15] 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 [25] applies.
+
+## 8.7 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [16] 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-12 [26] applies.
+
+## 8.8 Telecommunication ports
+
+This test is applicable for radio equipment and/or ancillary equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment, the associated ancillary equipment, or a representative configuration of the combination of radio and ancillary equipment.
+
+### 8.8.1 Definition
+
+This test assesses the EUT unwanted emission present at the telecommunication ports.
+
+### 8.8.2 Test method
+
+The test method shall be in accordance with CISPR 32 [28].
+
+The measurement frequency range extends from 150 kHz to 30 MHz. When the EUT is a transmitter operating at frequencies below 30 MHz, then the exclusion band for transmitters applies (see subclause 4.5) for measurements in the transmit mode of operation.
+
+### 8.8.3 Limits
+
+The telecommunication ports shall meet the limits according to CISPR 32 [28] shown in table 10.
+
+**Table 10: Limits for conducted emissions from telecommunication ports**
+
+| Frequency range<br>MHz | Voltage limits<br>dB (μV) |          | Current limits<br>dB (μA) |          |
+|------------------------|---------------------------|----------|---------------------------|----------|
+|                        | Quasi-peak                | Average  | Quasi-peak                | Average  |
+| 0,15 to 0,5            | 84 to 74                  | 74 to 64 | 40 to 30                  | 30 to 20 |
+| 0,5 to 30              | 74                        | 64       | 30                        | 20       |
+
+NOTE 1: The limits decrease linearly with the logarithm of the frequency in the range 0,15 MHz to 0,5 MHz.  
+NOTE 2: The current and voltage disturbance limits are derived for use with an impedance stabilization network (ISN) which presents a common mode (asymmetric mode) impedance of 150 Ω to the telecommunication port under test (conversion factor is  $20 \log_{10} 150/I = 44 \text{ dB}$ ).
+
+Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in table 11 may be used.
+
+**Table 11: Limits for conducted emissions from telecommunication ports of equipment intended for use in telecommunication centres only**
+
+| Frequency range<br>MHz | Voltage limits<br>dB (μV) |          | Current limits<br>dB (μA) |          |
+|------------------------|---------------------------|----------|---------------------------|----------|
+|                        | Quasi-peak                | Average  | Quasi-peak                | Average  |
+| 0,15 to 0,5            | 97 to 87                  | 84 to 74 | 53 to 43                  | 40 to 30 |
+| 0,5 to 30              | 87                        | 74       | 43                        | 30       |
+
+NOTE 1: The limits decrease linearly with the logarithm of the frequency in the range 0,15 MHz to 0,5 MHz.  
+NOTE 2: The current and voltage disturbance limits are derived for use with an impedance stabilization network (ISN), which presents a common mode (asymmetric mode) impedance of 150 Ω to the telecommunication port under test (conversion factor is  $20 \log_{10} 150/I = 44 \text{ dB}$ ).
+
+# 9 Immunity
+
+## 9.1 Test methods and levels for immunity tests
+
+## 9.2 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;
+- 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, Radio Frequency (RF) input/output ports shall be correctly terminated;
+
+- 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 base station shall be performed by establishing communication links at the air-interface (e.g. with the mobile simulator) and the Iub-interface (e.g. with an RNC simulator) and evaluating the BLER (see figure 2);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the air-interface and Iub-interface. BLER 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 air-interface or Iub-interface. In case of looping is used care have to be taken that the BLER information doesn't change due to looping. The BLER evaluation shall be based on the number of transmitted blocks i.e including possible deleted blocks.
+- For BS capable of multi-band operation, communication links shall be established in such a way that all operating band(s) are activated during the test according to the applicable test configurations in subclause 4.6. Performance assessment may be done separately for each operating band.
+
+![Figure 2: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1' (receiver 1), and 'RX 2 (terminated)' (receiver 2). Arrows indicate data flow: from the Mobile simulator to the Base station TX, and from the Base station RX 1 and RX 2 to the Mobile simulator. The Base station is also connected to an 'RNC simulator' box on the right. Arrows indicate data flow: from the RNC simulator to the Base station TX, and from the Base station RX 1 and RX 2 to the RNC simulator.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg)
+
+```
+
+graph LR
+    MS[Mobile simulator] <--> BS[Base station]
+    BS <--> RNC[RNC simulator]
+    subgraph BS [Base station]
+        TX[TX]
+        RX1[RX 1]
+        RX2["RX 2 (terminated)"]
+    end
+    MS --> TX
+    TX --> MS
+    RNC --> TX
+    TX --> RNC
+    RX1 --> MS
+    RX2 --> MS
+    RX1 --> RNC
+    RX2 --> RNC
+  
+```
+
+Figure 2: Communication link set up for BS immunity measurement. The diagram shows a 'Mobile simulator' box on the left connected to a 'Base station' box in the center. The 'Base station' box contains 'TX' (transmitter), 'RX 1' (receiver 1), and 'RX 2 (terminated)' (receiver 2). Arrows indicate data flow: from the Mobile simulator to the Base station TX, and from the Base station RX 1 and RX 2 to the Mobile simulator. The Base station is also connected to an 'RNC simulator' box on the right. Arrows indicate data flow: from the RNC simulator to the Base station TX, and from the Base station RX 1 and RX 2 to the RNC simulator.
+
+Figure 2: Communication link set up for BS immunity measurement
+
+## 9.3 RF electromagnetic field (80 MHz - 6000 MHz)
+
+The test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.3.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure.
+
+### 9.3.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-3 [18]:
+
+- for transmitters, receivers and transceivers the following requirements shall apply:
+- the test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 1 % of the momentary frequency;
+- the test shall be performed over the frequency range 80 MHz - 6000 MHz;
+- responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies selected during the test shall be recorded in the test report.
+
+### 9.3.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.7 shall apply.
+
+## 9.4 Electrostatic discharge
+
+The test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of an electrostatic discharge.
+
+### 9.4.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-2 [17]:
+
+- for contact discharge, the equipment shall pass at  $\pm 4$  kV;
+- for air discharge shall pass at  $\pm 8$  kV;
+- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures.
+
+NOTE: Ensure that the EUT is fully discharged between each ESD exposure.
+
+### 9.4.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.8 shall apply.
+
+## 9.5 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 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 associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.5.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of fast transients present on one of the input/output ports.
+
+### 9.5.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-4 [19]:
+
+- the test level for signal ports, telecommunication ports and control ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [19];
+- the test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [19];
+- the test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [19].
+
+For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 Ω.
+
+### 9.5.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.8 shall apply.
+
+## 9.6 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 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 associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+NOTE: This test can also be performed using the intrusive method, where appropriate, see IEC 61000-4-6 [21].
+
+### 9.6.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic disturbance.
+
+### 9.6.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-6 [21]:
+
+- the test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1%frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz.
+- the test level shall be severity level 2 as given in IEC 61000-4-6 [21] corresponding to 3 V rms, at a transfer impedance of 150 Ω;
+
+- the test shall be performed over the frequency range 150 kHz - 80 MHz;
+- the injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [21];
+- responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies of the immunity test signal selected and used during the test shall be recorded in the test report.
+
+### 9.6.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+#### Repeater:
+
+The performance criteria of subclause 6.7 shall apply.
+
+## 9.7 Voltage dips and interruptions
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.7.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+### 9.7.2 Test method and level
+
+The following requirements shall apply.
+
+The test method shall be in accordance with IEC 61000-4-11 [22].
+
+The test levels shall be:
+
+- a voltage dip corresponding to a reduction of the supply voltage of 30 % for 10 ms;
+- a voltage dip corresponding to a reduction of the supply voltage of 60 % for 100 ms;
+- a voltage interruption corresponding to a reduction of the supply voltage of > 95 % for 5 000 ms.
+
+### 9.7.3 Performance criteria
+
+For a voltage dip corresponding to a reduction of the supply voltage of 30 % for 10 ms the performance criteria for transient phenomena shall be applied:
+
+- Criteria 6.2 for base station
+- Criteria 6.5 for ancillary equipment
+- Criteria 6.8 for repeater
+
+For a voltage dip corresponding to a reduction of the supply voltage of 60 % for 100 ms and/or a voltage interruption corresponding to a reduction of the supply voltage of > 95 % for 5 000 ms, the following applies:
+
+1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied:
+
+- Criteria 6.2 for base station
+  - Criteria 6.5 for ancillary equipment
+  - Criteria 6.8 for repeater
+2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator:
+- No unintentional responses shall occur at the end of the test
+  - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report
+
+## 9.8 Surges, common and differential mode
+
+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 associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.8.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+### 9.8.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-5 [20].
+
+The requirements and evaluation of test results given in clause 9.8.2.1 (telecommunication ports, outdoor cables), clause 9.8.2.2 (telecommunication ports, indoor cables) and clause 9.8.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT.
+
+#### 9.8.2.1 Test method for telecommunication ports directly connected to outdoor cables
+
+The test level for telecommunications ports, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [20], however, in telecommunications centres 0,5 kV line to ground shall be used. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20].
+
+The test generator shall provide the 1,2/50 µs pulse as defined in IEC 61000-4-5 [20].
+
+#### 9.8.2.2 Test method for telecommunication ports connected to indoor cables
+
+The test level for telecommunication ports, intended to be connected to indoor cables (longer than 10 m) shall be 0,5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [20].
+
+The test generator shall provide the 1,2/50 µs pulse as defined in IEC 61000-4-5 [20].
+
+#### 9.8.2.3 Test method for AC power ports
+
+The test level for AC power input ports shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [20].
+
+In telecom centres 1 kV line to ground and 0,5 kV line to line shall be used.
+
+The test generator shall provide the 1,2/50 µs pulse as defined in IEC 61000-4-5 [20].
+
+### 9.8.3 Performance criteria
+
+#### **Base station:**
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### **Ancillary equipment:**
+
+The performance criteria of subclause 6.5 shall apply.
+
+#### **Repeater:**
+
+The performance criteria of subclause 6.8 shall apply.
+
+# Annex A (informative): Change History
+
+| TSG   | Doc       | CR   | R | Title                                                                                                          | Cat | Curr   | New    | Work Item               |
+|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------|-----|--------|--------|-------------------------|
+| RP-37 |           |      |   | Rel-8 version created from v7.6.0                                                                              |     |        | 8.0.0  |                         |
+| RP-37 | RP-070658 | 0036 |   | Introduction of UMTS1500 requirements (Rel-8)                                                                  | B   | 7.6.0  | 8.0.0  | RInImp8-UMTS1500        |
+| RP-39 | RP-080124 | 0038 | 1 | Introduction of UMTS700 requirements                                                                           | B   | 8.0.0  | 8.1.0  | RInImp8-UMTS700         |
+| RP-40 | RP-080384 | 0039 |   | Introduction of UMTS2300 requirements                                                                          | B   | 8.1.0  | 8.2.0  | RInImp8-UMTS2300TDD     |
+| RP-41 | RP-080631 | 0040 |   | EMC for BS equipment divided into more than one cabinet                                                        | B   | 8.2.0  | 8.3.0  | TEI8                    |
+| RP-43 | RP-080197 | 0041 |   | Introduction of band 1880MHz for 25.113                                                                        | F   | 8.3.0  | 8.4.0  | RInImp9-UMTS1880TDD     |
+| RP-44 | RP-090559 | 0042 |   | Introduction of Extended UMTS800 requirements                                                                  | B   | 8.4.0  | 9.0.0  | RInImp9-UMTSLTE800      |
+| RP-46 | RP-091286 | 043  |   | Introduction of Extended UMTS1500 requirements for TS25.113 (Technically endorsed at RAN 4 52bis in R4-093626) | B   | 9.0.0  | 9.1.0  | UMTSLTE1500             |
+| RP-46 | RP-091279 | 045  |   | BS emission applicability correction (Technically endorsed at RAN 4 52bis in R4-094024)                        | A   | 9.0.0  | 9.1.0  | TEI8                    |
+| RP-47 | RP-100263 | 47   |   | Introduction of Band XX in 25.113                                                                              | B   | 9.1.0  | 9.2.0  | RInImp9-UMTSLTE800EU    |
+| RP-49 | RP-100923 | 048  |   | Clarification of radiated emissions requirement                                                                | F   | 9.2.0  | 9.3.0  | RInImp9-RFmulti         |
+| RP-50 | RP-101334 | 052  |   | Band XII channel arrangement correction on 25.113                                                              | A   | 9.3.0  | 9.4.0  | TEI8                    |
+| RP-50 | RP-101338 | 050  |   | Correction due to the introduction of the definition of pass band                                              | A   | 9.3.0  | 9.4.0  | TEI8                    |
+| RP-51 | RP-110344 | 0055 | - | Applicability of EMC requirements                                                                              | F   | 9.4.0  | 9.5.0  | TEI9                    |
+| RP-51 | -         | -    |   | Automatic upgrade from rel-9 to rel-10                                                                         | -   | 9.5.0  | 10.0.0 | -                       |
+| RP-52 | RP-110804 | 056  |   | Add Expanded 1900MHz band in 25.113                                                                            | B   | 10.0.0 | 10.1.0 | E1900-Core              |
+| RP-53 | RP-111255 | 057  |   | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 25.113                                                          | B   | 10.1.0 | 10.2.0 | RInImp8-UMTSLTE3500     |
+| RP-55 | RP-120305 | 058  |   | Add upper 850MHz band in 25.113                                                                                | B   | 10.2.0 | 11.0.0 | e850_UB-Core            |
+| RP-64 | RP-140926 | 061  |   | Introduction of operating band XXXII in TS25.113                                                               | B   | 11.0.0 | 12.0.0 | LTE_UTRA_SDL_BandL-Core |
+| RP-65 | RP-141562 | 062  | 1 | Update of definitions to support supplemental DL in TS25.113                                                   | F   | 12.0.0 | 12.1.0 | TEI12                   |
+| RP-68 | RP-150955 | 064  |   | EMC testing of multi-band operation for UTRA BS                                                                | A   | 12.1.0 | 12.2.0 | MB_MSR_RF-Perf          |
+| SP-70 | -         | -    | - | Update to Rel-13 version (MCC)                                                                                 | -   | 12.2.0 | 13.0.0 |                         |
+|       |           |      |   | Editorial correction in the cover page                                                                         |     | 13.0.0 | 13.0.1 |                         |
+
+| Change history |         |           |      |     |     |                                                                   |               |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------|---------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                   | New version   |
+| 2016/06        | RP-72   | RP-161142 | 0065 | 1   | F   | Clarification in EMC environmental conditions references          | 13.1.0        |
+| 2017-03        | RP-75   | -         | -    | -   | -   | Update to Rel-14 version (MCC)                                    | 14.0.0        |
+| 2018-03        | RAN#79  | RP-180282 | 0066 | 1   | F   | CR to TS 25.113: correction of the CISPR reference and ESD levels | 15.0.0        |
+| 2020-06        | SA#88   | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                    | <b>16.0.0</b> |
+| 2022-03        | SA#95   |           |      |     |     | Update to Rel-17 version (MCC)                                    | <b>17.0.0</b> |

marked/Rel-17/25_series/25116/raw.md

@@ -0,0 +1,770 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                           |    |
+|---------------------------------------------------------------------------|----|
+| Foreword .....                                                            | 5  |
+| 1 Scope.....                                                              | 6  |
+| 2 References.....                                                         | 6  |
+| 3 Definitions, symbols and abbreviations .....                            | 6  |
+| 3.1 Definitions.....                                                      | 6  |
+| 3.2 Symbols.....                                                          | 7  |
+| 3.3 Abbreviations .....                                                   | 7  |
+| 4 General.....                                                            | 7  |
+| 4.1 Relationship between Minimum Requirements and Test Requirements ..... | 8  |
+| 4.2 Regional requirements.....                                            | 9  |
+| 5 Frequency bands and channel arrangement .....                           | 10 |
+| 5.1 General .....                                                         | 10 |
+| 5.2 Frequency bands.....                                                  | 10 |
+| 5.3 TX-RX frequency separation .....                                      | 10 |
+| 5.4 Channel arrangement.....                                              | 11 |
+| 5.4.1 Channel spacing.....                                                | 11 |
+| 5.4.2 Channel raster .....                                                | 11 |
+| 5.4.3 Channel number.....                                                 | 11 |
+| 6 Output power.....                                                       | 11 |
+| 6.1 Maximum output power.....                                             | 11 |
+| 6.1.1 Minimum Requirements.....                                           | 11 |
+| 7 Frequency stability.....                                                | 12 |
+| 7.1 Minimum requirement.....                                              | 12 |
+| 8 Out of band gain.....                                                   | 12 |
+| 8.1 Minimum requirement.....                                              | 12 |
+| 9 Unwanted emission .....                                                 | 13 |
+| 9.1 Spectrum emission mask.....                                           | 13 |
+| 9.2 Spurious emissions.....                                               | 14 |
+| 9.2.1 Mandatory Requirements .....                                        | 15 |
+| 9.2.1.1 Spurious emissions (Category A) .....                             | 15 |
+| 9.2.1.1.1 Minimum Requirement .....                                       | 15 |
+| 9.2.1.2 Spurious emissions (Category B) .....                             | 15 |
+| 9.2.1.2.1 Minimum Requirement .....                                       | 15 |
+| 9.2.2 Co-existence with GSM 900 .....                                     | 16 |
+| 9.2.2.1 Operation in the same geographic area.....                        | 16 |
+| 9.2.2.1.1 Minimum Requirement .....                                       | 16 |
+| 9.2.2.2 Co-located base stations.....                                     | 16 |
+| 9.2.2.2.1 Minimum Requirement .....                                       | 16 |
+| 9.2.3 Co-existence with DCS 1800 .....                                    | 16 |
+| 9.2.3.1 Operation in the same geographic area.....                        | 16 |
+| 9.2.3.1.1 Minimum Requirement .....                                       | 16 |
+| 9.2.3.2 Co-located base stations.....                                     | 17 |
+| 9.2.3.2.1 Minimum Requirement .....                                       | 17 |
+| 9.2.4 Co-existence with UTRA-FDD.....                                     | 17 |
+| 9.2.4.1 Operation in the same geographic area.....                        | 17 |
+| 9.2.4.1.1 Minimum Requirement .....                                       | 17 |
+| 9.2.4.2 Co-located base stations.....                                     | 18 |
+| 9.2.4.2.1 Minimum Requirement .....                                       | 18 |
+| 9.2.5 Co-existence with unsynchronised TDD.....                           | 18 |
+| 9.2.5.1 Operation in the same geographic area.....                        | 18 |
+| 9.2.5.1.1 Minimum Requirement .....                                       | 19 |
+| 9.2.5.2 Co-located base stations.....                                     | 19 |
+| 9.2.5.2.1 Minimum Requirement .....                                       | 19 |
+
+|                             |                                                                    |           |
+|-----------------------------|--------------------------------------------------------------------|-----------|
+| 10                          | Modulation accuracy.....                                           | 20        |
+| 10.1                        | Error Vector Magnitude .....                                       | 20        |
+| 10.1.1                      | Minimum requirement.....                                           | 20        |
+| 10.2                        | Peak code domain error.....                                        | 20        |
+| 10.2.1                      | Minimum requirement.....                                           | 20        |
+| 11                          | Input intermodulation.....                                         | 20        |
+| 11.1                        | General requirement.....                                           | 20        |
+| 11.1.1                      | Minimum requirement.....                                           | 20        |
+| 12                          | Output intermodulation .....                                       | 21        |
+| 12.0                        | General .....                                                      | 21        |
+| 12.1                        | Minimum requirement.....                                           | 21        |
+| 13                          | Adjacent Channel Rejection Ratio (ACRR) .....                      | 21        |
+| 13.1                        | Definitions and applicability .....                                | 21        |
+| 13.2                        | Co-existence with UTRA.....                                        | 21        |
+| 13.2.1.                     | Minimum Requirements.....                                          | 21        |
+| 14                          | Timing Accuracy.....                                               | 22        |
+| 14.1                        | Minimum requirement.....                                           | 22        |
+| <b>Annex A (normative):</b> | <b>Environmental requirements for the Repeater equipment .....</b> | <b>24</b> |
+| Annex B (informative):      | Change history.....                                                | 25        |
+
+# --- Foreword
+
+This Technical Specification 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 establishes the minimum RF characteristics of LCR TDD Repeater.
+
+# --- 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] ITU-R Recommendation SM.329, "Unwanted emissions in the spurious domain".
+- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [4] 3GPP TS 25.153: "LCR TDD Repeater conformance testing"
+- [5] 3GPP TR 25.942: "RF system scenarios".
+- [6] IEC 60721-3-3 (2002): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 3: Stationary use at weather protected locations".
+- [7] IEC 60721-3-4 (1995): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations".
+
+# --- 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].
+
+**Carrier:** The modulated waveform conveying the LCR TDD physical channels
+
+**Channel bandwidth:** The RF bandwidth supporting a single LCR TDD RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
+
+**Channel edge:** The lowest and highest frequency of the LCR TDD carrier, separated by the channel bandwidth.
+
+**Donor coupling loss:** is the coupling loss between the repeater and the donor base station.
+
+**Downlink:** Signal path where base station transmits and mobile receives.
+
+**Maximum output power, Pmax:** This is the mean power level per carrier measured at the antenna connector of the Repeater in specified reference condition.
+
+**Output power, Pout:** This is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter.
+
+**Pass band:** The repeater can have one or several pass bands. The pass band is the frequency range that the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band.
+
+**Rated output power:** Rated output power of the repeater is the mean power level per carrier that the manufacturer has declared to be available at the antenna connector.
+
+**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station)
+
+**Transmission bandwidth:** Bandwidth of an instantaneous transmission from a UE or BS, measured in Resource Block units.
+
+**Transmission bandwidth configuration:** The highest transmission bandwidth allowed for uplink or downlink in a given channel bandwidth, measured in Resource Block units.
+
+**Uplink:** Signal path where mobile transmits and base station receives.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                       |                                                                                        |
+|-----------------------|----------------------------------------------------------------------------------------|
+| BW <sub>Channel</sub> | Channel bandwidth                                                                      |
+| BW <sub>Config</sub>  | Transmission bandwidth configuration, expressed in MHz.                                |
+| BW <sub>Meas</sub>    | Measurement bandwidth                                                                  |
+| BW <sub>Signal</sub>  | Bandwidth of the repeater input signal filling the repeater pass band                  |
+| F <sub>DL_low</sub>   | The lowest frequency of the downlink operating band                                    |
+| F <sub>DL_high</sub>  | The highest frequency of the downlink operating band                                   |
+| F <sub>UL_low</sub>   | The lowest frequency of the uplink operating band                                      |
+| F <sub>UL_high</sub>  | The highest frequency of the uplink operating band                                     |
+| f_offset_PB           | Distance from the channel edge frequency of the first or last channel in the pass band |
+| N <sub>DL</sub>       | Downlink LARFCN                                                                        |
+| N <sub>offs-DL</sub>  | Offset used for calculating downlink LARFCN                                            |
+| N <sub>offs-UL</sub>  | Offset used for calculating uplink LARFCN                                              |
+| N <sub>RB</sub>       | Transmission bandwidth configuration, expressed in units of resource blocks            |
+| N <sub>UL</sub>       | Uplink LARFCN                                                                          |
+| P <sub>max</sub>      | Maximum output power                                                                   |
+| P <sub>out</sub>      | Output power                                                                           |
+
+## 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].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| ACRR   | Adjacent Channel Rejection Ratio                |
+| BS     | Base Station                                    |
+| LARFCN | LCR TDD Absolute Radio Frequency Channel Number |
+| PB     | Pass Band                                       |
+
+# 4 General
+
+This specification applies only to LCR TDD repeaters.
+
+Unless otherwise stated, all requirements in this specification apply to both the up-link and down-link directions.
+
+## 4.1 Relationship between Minimum Requirements and Test Requirements
+
+The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 25.153 section 4 defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements.
+
+The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle.
+
+The Shared Risk principle is defined in ITU-R M.1545 [3].
+
+## 4.2 Regional requirements
+
+Some requirements in the present document may only apply in certain regions. Table 4.2-1 lists all requirements that may be applied differently in different regions.
+
+**Table 4.2-1: List of regional requirements**
+
+| Clause number | Requirement                                                                  | Comments                                                                                                                                                                                       |
+|---------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.2           | Channel bandwidth                                                            | Some channel bandwidths may be applied regionally.                                                                                                                                             |
+| 5.3           | Frequency bands                                                              | Some bands may be applied regionally.                                                                                                                                                          |
+| 5.4           | Channel arrangement                                                          | The requirement is applied according to what frequency bands in Clause 5.3 that are supported by the Repeater.                                                                                 |
+| 6.1           | Maximum output power                                                         | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal.                                        |
+| 9.1.1.1       | Operating band unwanted emissions (Category A)                               | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply.                                                 |
+| 9.1.1.2       | Operating band unwanted emissions (Category B)                               | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply.                                                |
+| 9.1.3         | Operating band unwanted emissions : Additional requirements                  | These requirements may be applied regionally for some operating bands.                                                                                                                         |
+| 9.2.1.1       | Spurious emissions (Category A)                                              | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply.                                                 |
+| 9.2.1.2       | Spurious emissions (Category B)                                              | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply.                                                |
+| 9.2.2.1       | Co-existence with GSM900 - Operation in the same geographic area             | This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS in geographic areas in which both GSM 900 and LCR TDD repeater are deployed.                                  |
+| 9.2.2.2       | Co-existence with GSM900 - Co-located base stations                          | This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and LCR TDD repeater are co-located.                                                              |
+| 9.2.3.1       | Co-existence with DCS1800 - Operation in the same geographic area            | This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS in geographic areas in which both DCS 1800 and LCR TDD repeater are deployed.                               |
+| 9.2.3.2       | Co-existence with DCS1800 - Co-located base stations                         | This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and LCR TDD repeater are co-located.                                                            |
+| 9.2.4.1       | Co-existence with UTRA FDD - Operation in the same geographic area           | This requirement may be applied to geographic areas in which both LCR TDD repeater and UTRA-FDD are deployed.                                                                                  |
+| 9.2.4.2       | Co-existence with UTRA FDD - Co-located base stations                        | This requirement may be applied for the protection of UTRA-FDD BS receivers when LCR TDD repeater and UTRA FDD BS are co-located.                                                              |
+| 9.2.5.1       | Co-existence with unsynchronized TDD - Operation in the same geographic area | This requirement may be applied for the protection of UTRA-TDD BS receivers in same geographic areas in which unsynchronized TDD is deployed.                                                  |
+| 9.2.5.2       | Co-existence with unsynchronized TDD -Co-located base stations               | This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD BS are unsynchronized co-located.                                                                    |
+| 11.2          | Input Intermodulation: Co-location with other systems                        | These requirements may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an LCR TDD Repeater. |
+| 11.3          | Input Intermodulation: Co-existence with other systems                       | These requirements may be applied when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS operating in another frequency band co-exist with an LCR TDD Repeater.            |
+
+# 5 Frequency bands and channel arrangement
+
+## 5.1 General
+
+The information presented in this section is based on the chip rates of 1.28 Mcps TDD.
+
+NOTE: Other chip rates may be considered in future releases.
+
+## 5.2 Frequency bands
+
+UTRA/TDD is designed to operate in the following bands;
+
+- a) 1900 - 1920 MHz: Uplink and downlink transmission  
+2010 - 2025 MHz Uplink and downlink transmission
+- b) 1850 - 1910 MHz Uplink and downlink transmission  
+1930 - 1990 MHz Uplink and downlink transmission
+- c) 1910 - 1930 MHz Uplink and downlink transmission
+- d) 2570 - 2620 MHz Uplink and downlink transmission
+- e) 2300 - 2400 MHz Uplink and downlink transmission
+- f) 1880 - 1920 MHz: Uplink and downlink transmission
+
+Note: Deployment in existing and other frequency bands is not precluded.
+
+The co-existence of TDD and FDD in the same bands is still under study in WG4.
+
+## 5.3 TX-RX frequency separation
+
+No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL.
+
+## 5.4 Channel arrangement
+
+### 5.4.1 Channel spacing
+
+The channel spacing is 1.6MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
+
+### 5.4.2 Channel raster
+
+The channel raster is 200 kHz for all bands, which means that the carrier frequency must be a multiple of 200 kHz.
+
+### 5.4.3 Channel number
+
+The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows:
+
+$$N_t = 5 * F \quad 0.0 \leq F \leq 3276.6 \text{ MHz}$$
+
+where F is the carrier frequency in MHz.
+
+# 6 Output power
+
+Output power,  $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter.
+
+Rated output power, PRAT, of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector.
+
+## 6.1 Maximum output power
+
+Maximum output power, Pmax, of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition.
+
+### 6.1.1 Minimum Requirements
+
+The requirements shall apply at maximum gain, with LCR TDD signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel.
+
+When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met.
+
+In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power.
+
+**Table 6.1: Repeater output power; normal conditions**
+
+| Rated output power | Limit           |
+|--------------------|-----------------|
+| $P \geq 31$ dBm    | +2 dB and -2 dB |
+| $P < 31$ dBm       | +3 dB and -3 dB |
+
+In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power.
+
+**Table 6.2: Repeater output power; extreme conditions**
+
+| Rated output power | Limit               |
+|--------------------|---------------------|
+| $P \geq 31$ dBm    | +2,5 dB and -2,5 dB |
+| $P < 31$ dBm       | +4 dB and -4 dB     |
+
+In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal.
+
+# 7 Frequency stability
+
+Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal.
+
+## 7.1 Minimum requirement
+
+The frequency deviation of the output signal with respect to the input signal shall be no more than  $\pm 0,01$  ppm.
+
+# 8 Out of band gain
+
+Out of band gain refers to the gain of the repeater outside the pass band.
+
+## 8.1 Minimum requirement
+
+The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station.
+
+In the intended application of the repeater, the out of band gain is less than the donor coupling loss.
+
+The repeater minimum donor coupling loss shall be declared by the manufacturer. This is this the minimum required attenuation between the donor BS and the repeater for proper repeater operation.
+
+The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where:
+
+- $f\_offset$  is the distance from the centre frequency of the first or last channel within the pass band.
+
+**Table 8.1: Out of band gain limits 1**
+
+| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain |
+|----------------------------------------------------------|--------------|
+| $1,0 \leq f\_offset < 1,8$ MHz                           | 60 dB        |
+| $1,8 \leq f\_offset < 5,8$ MHz                           | 45 dB        |
+| $5,8 \leq f\_offset < 10,8$ MHz                          | 45 dB        |
+| $10,8$ MHz $\leq f\_offset$                              | 35 dB        |
+
+For  $10,8$  MHz  $\leq f\_offset$  the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower.
+
+**Table 8.2: Out of band gain limits 2**
+
+| Repeater maximum output power as in 9.1.1.1                                 | Maximum gain                                                    |
+|-----------------------------------------------------------------------------|-----------------------------------------------------------------|
+| $P < 31$ dBm                                                                | Out of band gain $\leq$ minimum donor coupling loss             |
+| $31$ dBm $\leq P < 43$ dBm                                                  | Out of band gain $\leq$ minimum donor coupling loss             |
+| $P \geq 43$ dBm                                                             | Out of band gain $\leq$ minimum donor coupling loss - (P-43dBm) |
+| NOTE 1: The out of band gain is considered with $10,8$ MHz $\leq f\_offset$ |                                                                 |
+
+# 9 Unwanted emission
+
+## 9.1 Spectrum emission mask
+
+The mask defined in Table 9.1 to 9.3 may be mandatory in certain regions. In other regions this mask may not be applied.
+
+For regions where this clause applies, the requirement shall be met by a LCR TDD repeater transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in table 9.1 to 9.3 for the appropriate LCR TDD repeater maximum output power, in the frequency range from  $\Delta f = 0.8$  MHz to  $\Delta f_{max}$  from the carrier frequency, where:
+
+- $\Delta f$  is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f\_offset$  is the separation between the carrier frequency and the center frequency of the measuring filter.
+- $f\_offset_{max}$  is either 4 MHz or the offset to the UMTS Tx band edge as defined in section 5.2, whichever is the greater.
+- $\Delta f_{max}$  is equal to  $f\_offset_{max}$  minus half of the bandwidth of the measurement filter.
+
+![Illustrative diagram of spectrum emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf_max. Two masks are shown: one for P = 34 dBm (upper mask) and one for P = 26 dBm (lower mask). Both masks show a constant power density of -20 dBm in 30kHz from 0.8 to 1.0 MHz, followed by a roll-off until 1.8 MHz, where it flattens out at -28 dBm in 30kHz (or -13 dBm in 1 MHz) up to Δf_max.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg)
+
+Illustrative diagram of spectrum emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf\_max. Two masks are shown: one for P = 34 dBm (upper mask) and one for P = 26 dBm (lower mask). Both masks show a constant power density of -20 dBm in 30kHz from 0.8 to 1.0 MHz, followed by a roll-off until 1.8 MHz, where it flattens out at -28 dBm in 30kHz (or -13 dBm in 1 MHz) up to Δf\_max.
+
+**Illustrative diagram of spectrum emission mask**
+
+**Figure 9.1**
+
+**Table 9.1: Spectrum emission mask values, BS maximum output power  $P \geq 34$  dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                             | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$             | $0.815 \text{MHz} \leq f\_offset < 1.015 \text{MHz}$                 | -20 dBm                                                                                   | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$             | $1.015 \text{MHz} \leq f\_offset < 1.815 \text{MHz}$                 | $-20\text{dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                      | $1.815 \text{MHz} \leq f\_offset < 2.3 \text{MHz}$                   | -28 dBm                                                                                   | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$          | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | -13 dBm                                                                                   | 1 MHz                 |
+
+**Table 9.2: Spectrum emission mask values, BS maximum output power  $26 \leq P < 34$  dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$             | $0.815 \text{MHz} \leq f\_offset < 1.015 \text{MHz}$                 | $P - 54 \text{ dB}$                                                                         | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$             | $1.015 \text{MHz} \leq f\_offset < 1.815 \text{MHz}$                 | $P - 54\text{dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                      | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$                 | $P - 62 \text{ dB}$                                                                         | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$          | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | $P - 47 \text{ dB}$                                                                         | 1 MHz                 |
+
+**Table 9.3: Spectrum emission mask values, BS maximum output power P < 26 dBm**
+
+| Frequency offset of measurement filter - 3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|----------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$              | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$               | -28 dBm                                                                                     | 30 kHz                |
+| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$              | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$               | $-28 \text{ dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz                |
+| See note                                                       | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$                 | -36 dBm                                                                                     | 30 kHz                |
+| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | -21 dBm                                                                                     | 1 MHz                 |
+
+NOTE: This frequency range ensures that the range of values of  $f\_offset$  is continuous.
+
+## 9.2 Spurious emissions
+
+Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port.
+
+The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer's.
+
+For 1.28 Mcps TDD option, either requirement applies at frequencies within the specified frequency ranges which are more than 4 MHz under the first carrier frequency used or more than 4 MHz above the last carrier frequency used.
+
+Unless otherwise stated, all requirements are measured as mean power.
+
+### 9.2.1 Mandatory Requirements
+
+The requirements of either subclause 9.2.1.1 or subclause 9.2.1.2 shall apply.
+
+#### 9.2.1.1 Spurious emissions (Category A)
+
+The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [1], are applied.
+
+##### 9.2.1.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.4: LCR TDD repeater Mandatory spurious emissions limits, Category A**
+
+| Band                                                       | Minimum requirement | Measurement Bandwidth | Notes  |
+|------------------------------------------------------------|---------------------|-----------------------|--------|
+| 9kHz - 150kHz                                              |                     | 1 kHz                 | Note 1 |
+| 150kHz - 30MHz                                             |                     | 10 kHz                | Note 1 |
+| 30MHz - 1GHz                                               | -13 dBm             | 100 kHz               | Note 1 |
+| 1GHz - 12.75 GHz                                           |                     | 1 MHz                 | Note 2 |
+| NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1               |                     |                       |        |
+| NOTE 2: Upper frequency as in ITU SM.329 [1], s2.5 table 1 |                     |                       |        |
+
+NOTE: only the measurement bands are different according to the occupied bandwidth.
+
+#### 9.2.1.2 Spurious emissions (Category B)
+
+The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied.
+
+##### 9.2.1.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.5: LCR TDD repeater Mandatory spurious emissions limits, Category B**
+
+| Band                         | Maximum Level | Measurement Bandwidth | Notes  |
+|------------------------------|---------------|-----------------------|--------|
+| 9kHz - 150kHz                | -36 dBm       | 1 kHz                 | Note 1 |
+| 150kHz - 30MHz               | - 36 dBm      | 10 kHz                | Note 1 |
+| 30MHz - 1GHz                 | -36 dBm       | 100 kHz               | Note 1 |
+| 1GHz<br>↔<br>Fl -10 MHz      | -30 dBm       | 1 MHz                 | Note 1 |
+| Fl -10MHz<br>↔<br>Fu +10 MHz | -15 dBm       | 1 MHz                 | Note 2 |
+| Fu +10 MHz<br>↔<br>12,5 GHz  | -30 dBm       | 1 MHz                 | Note 3 |
+
+NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1  
+NOTE 2: Limit based on ITU-R SM.329 [1], s4.3 and Annex 7  
+NOTE 3: Bandwidth as in ITU-R SM.329 [1], s4.3 and Annex 7. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1
+
+Fl: Lower frequency of the band in which TDD operates  
+Fu: Upper frequency of the band in which TDD operates
+
+### 9.2.2 Co-existence with GSM 900
+
+#### 9.2.2.1 Operation in the same geographic area
+
+This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS receivers in geographic areas in which both GSM 900 and UTRA are deployed.
+
+##### 9.2.2.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.6: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of GSM 900 MS and GSM 900 BTS receiver**
+
+| Band          | Maximum Level | Measurement Bandwidth | Note |
+|---------------|---------------|-----------------------|------|
+| 876 - 915 MHz | -61 dBm       | 100 kHz               |      |
+| 921 - 960MHz  | -57 dBm       | 100 kHz               |      |
+
+#### 9.2.2.2 Co-located base stations
+
+This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located.
+
+##### 9.2.2.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.7: LCR TDD repeater Spurious emissions limits for protection of the GSM 900 BTS receiver**
+
+| Band          | Maximum Level | Measurement Bandwidth | Note |
+|---------------|---------------|-----------------------|------|
+| 876 - 915 MHz | -98 dBm       | 100 kHz               |      |
+
+### 9.2.3 Co-existence with DCS 1800
+
+#### 9.2.3.1 Operation in the same geographic area
+
+This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS receivers in geographic areas in which both DCS 1800 and UTRA are deployed.
+
+##### 9.2.3.1.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.8: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1785 MHz | -61 dBm       | 100 kHz               |      |
+| 1805 - 1880MHz  | -47 dBm       | 100 kHz               |      |
+
+**Table 9.8a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver operating in 1710-1755 MHz/1805-1850 MHz**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1755 MHz | -61 dBm       | 100 kHz               |      |
+| 1805 - 1850MHz  | -47 dBm       | 100 kHz               |      |
+
+#### 9.2.3.2 Co-located base stations
+
+This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located.
+
+##### 9.2.3.2.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.9: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when co-located with DCS 1800 BTS**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1785 MHz | -98 dBm       | 100 kHz               |      |
+
+**Table 9.10: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when co-located with DCS1800 BTS**
+
+| Band            | Maximum Level | Measurement Bandwidth | Note |
+|-----------------|---------------|-----------------------|------|
+| 1710 - 1755 MHz | -98 dBm       | 100 kHz               |      |
+
+### 9.2.4 Co-existence with UTRA-FDD
+
+#### 9.2.4.1 Operation in the same geographic area
+
+This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD operating in bands specified in Table 9.11 are deployed.
+
+##### 9.2.4.1.1 Minimum Requirement
+
+For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.11. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz.
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.11: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of UTRA-FDD**
+
+| Band                                                                                                                                                                                                                                                                                                  | Maximum Level | Measurement Bandwidth | Note |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------|
+| 1920 - 1980 MHz                                                                                                                                                                                                                                                                                       | -43 dBm (*)   | 3,84 MHz              |      |
+| 2110 - 2170 MHz                                                                                                                                                                                                                                                                                       | -52 dBm       | 1 MHz                 |      |
+| 2500 - 2570 MHz                                                                                                                                                                                                                                                                                       | -43 dBm(**)   | 3,84 MHz              |      |
+| 2620 - 2690 MHz                                                                                                                                                                                                                                                                                       | -52 dBm       | 1 MHz                 |      |
+| NOTE* For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. |               |                       |      |
+| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6 MHz below the lowest TDD carrier used, whichever is lower.                |               |                       |      |
+
+NOTE: The requirements in Table 9.11 are based on a coupling loss of 70 dB between LCR TDD repeater and FDD Wide Area base stations.
+
+#### 9.2.4.2 Co-located base stations
+
+This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located.
+
+##### 9.2.4.2.1 Minimum Requirement
+
+For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.12. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz.
+
+The power of any spurious emission shall not exceed:
+
+**Table 9.12: LCR TDD repeater Spurious emissions limits for BS co-located with UTRA-FDD**
+
+| Band                                                                                                                                                                                                                                                                                                   | Maximum Level | Measurement Bandwidth |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|
+| 1920 - 1980 MHz                                                                                                                                                                                                                                                                                        | -80 dBm (*)   | 3,84 MHz              |
+| 2110 - 2170 MHz                                                                                                                                                                                                                                                                                        | -52 dBm       | 1 MHz                 |
+| 2500 - 2570 MHz                                                                                                                                                                                                                                                                                        | - 80 dBm(**)  | 3,84 MHz              |
+| 2620 - 2690 MHz                                                                                                                                                                                                                                                                                        | -52 dBm       | 1 MHz                 |
+| NOTE * For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. |               |                       |
+| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6MHz below the lowest TDD carrier used, whichever is lower.                  |               |                       |
+
+NOTE: The requirements in Table 9.12 are based on a minimum coupling loss of 30 dB between LCR TDD repeater and UTRA-FDD base stations.
+
+### 9.2.5 Co-existence with unsynchronised TDD
+
+#### 9.2.5.1 Operation in the same geographic area
+
+This requirement shall apply in case the equipment is operated in the same geographic area with unsynchronised TDD BS.
+
+##### 9.2.5.1.1 Minimum Requirement
+
+In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the limits specified in table 9.13, otherwise the limits in table 9.14 shall apply.
+
+**Table 9.13: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -39 dBm       | 1,28 MHz              |
+| 2010 - 2025 MHz | -39 dBm       | 1,28 MHz              |
+| 2300 - 2400 MHz | -39 dBm       | 1,28 MHz              |
+| 2570 - 2620 MHz | -39 dBm       | 1,28 MHz              |
+| 1880 - 1920 MHz | -39 dBm       | 1,28 MHz              |
+
+**Table 9.14: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -39 dBm       | 3,84 MHz              |
+| 2010 - 2025 MHz | -39 dBm       | 3,84 MHz              |
+| 2570 - 2620 MHz | -39 dBm       | 3,84 MHz              |
+
+NOTE: The requirements in Table 9.13 and 9.14 for the LCR TDD repeater are based on a minimum coupling loss of 67 dB between LCR TDD repeater and unsynchronised TDD base stations.
+
+#### 9.2.5.2 Co-located base stations
+
+This requirement shall apply in case of co-location with unsynchronised TDD BS.
+
+##### 9.2.5.2.1 Minimum Requirement
+
+In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the limits specified in table 9.15, otherwise the limits in table 9.16 shall apply.
+
+**Table 9.15: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised 1,28 Mcps TDD**
+
+| Band                                                                                                                                | Maximum Level | Measurement Bandwidth |
+|-------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|
+| 1900 - 1920 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2010 - 2025 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2300 - 2400 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 2570 - 2620 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| 1880 - 1920 MHz                                                                                                                     | -76 dBm       | 1,28 MHz              |
+| NOTE: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. |               |                       |
+
+**Table 9.16: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised TDD**
+
+| Band            | Maximum Level | Measurement Bandwidth |
+|-----------------|---------------|-----------------------|
+| 1900 - 1920 MHz | -76 dBm       | 3,84 MHz              |
+| 2010 - 2025 MHz | -76 dBm       | 3,84 MHz              |
+| 2570 - 2620 MHz | -76 dBm       | 3,84 MHz              |
+
+NOTE: The requirements in Table 9.15 and 9.16 for the LCR TDD repeater are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations.
+
+# --- 10 Modulation accuracy
+
+## 10.1 Error Vector Magnitude
+
+The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 1.28MHz and roll-off  $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %.
+
+The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal LCR TDD signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer.
+
+### 10.1.1 Minimum requirement
+
+The Error Vector Magnitude shall not be worse than 8 %.
+
+## 10.2 Peak code domain error
+
+The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot.
+
+### 10.2.1 Minimum requirement
+
+The peak code domain error shall not exceed -30 dB at spreading factor 16.
+
+# --- 11 Input intermodulation
+
+The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band.
+
+## 11.1 General requirement
+
+The following requirement applies for interfering signals in the frequency bands defined in sub-clause 5.2, depending on the repeaters pass band.
+
+This requirement applies to the uplink and downlink of the repeater, at maximum gain.
+
+### 11.1.1 Minimum requirement
+
+For the parameters specified in table 11.1.1-1, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied.
+
+The frequency separation between the two interfering signals shall be adjusted so that the 3<sup>rd</sup> order intermodulation product is positioned in the centre of the pass band.
+
+Table 11.1.1-1 specifies the parameters for two interfering signals, where:
+
+- $f_1$  offset is the offset from the channel edge frequency of the first or last channel in the pass band of the closer carrier.
+
+**Table 11.1.1-1: Input intermodulation requirement**
+
+| <b>f<sub>1</sub> offset</b> | <b>Interfering Signal Levels</b> | <b>Type of signals</b> | <b>Measurement bandwidth</b> |
+|-----------------------------|----------------------------------|------------------------|------------------------------|
+| 1,0 MHz                     | -40 dBm                          | 2 CW carriers          | 1 MHz                        |
+
+# 12 Output intermodulation
+
+## 12.0 General
+
+The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna.
+
+The transmit intermodulation level is the power of the intermodulation products when a LCR TDD modulated interference signal is injected into the antenna connector at a mean power level of 30 dB lower than that of the mean power of the subject signal.
+
+## 12.1 Minimum requirement
+
+The frequency of the interference signal shall be  $\pm 1.6$  MHz,  $\pm 3.2$  MHz and  $\pm 4.8$  MHz offset from the subject signal. The Transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of section 9.1 and 9.2.
+
+# 13 Adjacent Channel Rejection Ratio (ACRR)
+
+## 13.1 Definitions and applicability
+
+Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. The carrier in the pass band and in the adjacent channel shall be of the same type (reference carrier).
+
+The requirement shall apply to the uplink and downlink of Repeater, at maximum gain, where the donor link is maintained via antennas (over the air Repeater).
+
+## 13.2 Co-existence with UTRA
+
+This requirement shall be applied for the protection of UTRA signals in geographic areas in which LCR TDD Repeater and UTRA BS are deployed so that they serve adjacent channels. The reference carrier is a UTRA-FDD carrier.
+
+### 13.2.1. Minimum Requirements
+
+In normal conditions the ACRR shall be higher than the value specified in the Table 13.2.1-1.
+
+**Table 13.2.1-1: Repeater ACRR**
+
+| <b>Co-existence with other systems</b> | <b>Repeater maximum output Pmax</b> | <b>Channel offset from the channel edge from the first or last 5MHz channel within the pass band.</b> | <b>ACRR limit</b> |
+|----------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------|-------------------|
+| UTRA                                   | $P \geq 31$ dBm                     | 2,5 MHz                                                                                               | 33dB              |
+|                                        | $P \geq 31$ dBm                     | 5,0 MHz                                                                                               | 33dB              |
+|                                        | $P < 31$ dBm                        | 2,5 MHz                                                                                               | 20dB              |
+|                                        | $P < 31$ dBm                        | 5,0 MHz                                                                                               | 20dB              |
+
+Note: For co-existence with TDD, a narrow band requirement is for further study.
+
+# 14 Timing Accuracy
+
+Timing Accuracy is the repeater synchronization accuracy with NodeB, it includes the downlink ramp on/off time and uplink ramp on/off time.
+
+## 14.1 Minimum requirement
+
+The downlink gain versus time should meet the mask specified in figure 14.1. The beginning and end point of downlink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator.
+
+![Figure 14.1: Downlink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain'. The horizontal axis shows a 'Downlink burst without GP' of a certain duration, preceded and followed by '8 chips' intervals where the gain is zero. The gain ramps up from zero to rated gain at the start of the burst and ramps back down to zero at the end.](5adf12d50dfea82178ca002a2c48641b_img.jpg)
+
+The diagram illustrates the downlink gain template. It features a horizontal line for 'Zero Gain' and another for 'Rated Gain'. A rectangular pulse represents the 'Downlink burst without GP'. The pulse starts after an '8 chips' interval from the left and ends before another '8 chips' interval on the right. Vertical lines indicate the ramp-up and ramp-down of the gain between zero and rated levels.
+
+Figure 14.1: Downlink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain'. The horizontal axis shows a 'Downlink burst without GP' of a certain duration, preceded and followed by '8 chips' intervals where the gain is zero. The gain ramps up from zero to rated gain at the start of the burst and ramps back down to zero at the end.
+
+Figure 14.1: Downlink gain ON/OFF template
+
+The uplink gain versus time should meet the mask specified in figure 14.2. The beginning and end point of uplink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator.
+
+![Figure 14.2: Uplink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain'. The horizontal axis shows an 'Uplink burst without GP' of a certain duration, preceded and followed by '8 chips' intervals where the gain is zero. The gain ramps up from zero to rated gain at the start of the burst and ramps back down to zero at the end.](85ad73d1c8ff59cd647b95f084937bc0_img.jpg)
+
+The diagram illustrates the uplink gain template, which is identical in structure to the downlink template. It shows a rectangular pulse for the 'Uplink burst without GP' between two '8 chips' intervals. The gain levels are 'Zero Gain' and 'Rated Gain', with vertical lines showing the ramp transitions.
+
+Figure 14.2: Uplink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain'. The horizontal axis shows an 'Uplink burst without GP' of a certain duration, preceded and followed by '8 chips' intervals where the gain is zero. The gain ramps up from zero to rated gain at the start of the burst and ramps back down to zero at the end.
+
+Figure 14.2: Uplink gain ON/OFF template
+
+# --- Annex A (normative):Environmental requirements for the Repeater equipment
+
+The Repeater equipment shall fulfil all the requirements in the full range of environmental conditions for the relevant environmental class from the relevant IEC specifications listed below
+
+- 60 721-3-3 "Stationary use at weather protected locations" [6];
+- 60 721-3-4 "Stationary use at non weather protected locations" [7]
+
+Normally it should be sufficient for all tests to be conducted using normal test conditions except where otherwise stated. For guidance on the use of test conditions to be used in order to show compliance refer to TS 25.153.
+

marked/Rel-17/25_series/25171/raw.md

@@ -0,0 +1,978 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                        |           |
+|------------------------------------------------------------------------|-----------|
+| Foreword .....                                                         | 5         |
+| 1 Scope.....                                                           | 6         |
+| 2 References.....                                                      | 6         |
+| 3 Definitions, symbols, abbreviations and test tolerances .....        | 7         |
+| 3.1 Definitions.....                                                   | 7         |
+| 3.2 Symbols.....                                                       | 7         |
+| 3.3 Abbreviations .....                                                | 7         |
+| 3.4 Test tolerances.....                                               | 8         |
+| 4 General.....                                                         | 8         |
+| 4.1 Introduction .....                                                 | 8         |
+| 4.2 Measurement parameters.....                                        | 8         |
+| 4.2.1 UE based A-GPS measurement parameters .....                      | 8         |
+| 4.2.2 UE assisted A-GPS measurement parameters.....                    | 8         |
+| 4.3 Response time .....                                                | 8         |
+| 4.4 Time assistance .....                                              | 8         |
+| 4.4.1 Use of fine time assistance .....                                | 9         |
+| 4.5 RRC states.....                                                    | 9         |
+| 4.6 2D position error .....                                            | 9         |
+| 5 A-GPS minimum performance requirements .....                         | 9         |
+| 5.1 Sensitivity.....                                                   | 9         |
+| 5.1.1 Coarse time assistance.....                                      | 9         |
+| 5.1.1.1 Minimum Requirements (Coarse time assistance) .....            | 10        |
+| 5.1.2 Fine time assistance.....                                        | 10        |
+| 5.1.2.1 Minimum Requirements (Fine time assistance) .....              | 10        |
+| 5.2 Nominal Accuracy.....                                              | 10        |
+| 5.2.1 Minimum requirements (nominal accuracy) .....                    | 11        |
+| 5.3 Dynamic Range.....                                                 | 11        |
+| 5.3.1 Minimum requirements (dynamic range).....                        | 11        |
+| 5.4 Multi-Path scenario .....                                          | 11        |
+| 5.4.1 Minimum Requirements (multi-path scenario) .....                 | 12        |
+| 5.5 Moving scenario and periodic update .....                          | 12        |
+| 5.5.1 Minimum Requirements (moving scenario and periodic update) ..... | 13        |
+| <b>Annex A (normative): Test cases.....</b>                            | <b>14</b> |
+| A.1 Conformance tests.....                                             | 14        |
+| A.2 Requirement classification for statistical testing .....           | 14        |
+| <b>Annex B (normative): Test conditions.....</b>                       | <b>15</b> |
+| B.1 General.....                                                       | 15        |
+| B.1.1 Parameter values .....                                           | 15        |
+| B.1.2 Time assistance .....                                            | 15        |
+| B.1.3 GPS Reference Time.....                                          | 15        |
+| B.1.4 Reference and UE locations .....                                 | 16        |
+| B.1.5 Satellite constellation and assistance data.....                 | 16        |
+| B.1.6 Atmospheric delays.....                                          | 16        |
+| B.1.7 UTRA Frequency and frequency error.....                          | 16        |
+| B.1.8 Information elements.....                                        | 16        |
+| B.1.9 GPS signals .....                                                | 16        |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message .....           | 16        |
+| <b>Annex C (normative): Propagation conditions .....</b>               | <b>18</b> |
+| C.1 General.....                                                       | 18        |
+| C.2 Propagation Conditions .....                                       | 18        |
+
+|                               |                                                                                                |           |
+|-------------------------------|------------------------------------------------------------------------------------------------|-----------|
+| C.2.1                         | Static propagation conditions .....                                                            | 18        |
+| C.2.2                         | Multi-path Case G1 .....                                                                       | 18        |
+| <b>Annex D (normative):</b>   | <b>Measurement sequence chart.....</b>                                                         | <b>19</b> |
+| D.1                           | General.....                                                                                   | 19        |
+| D.2                           | UE Based A-GPS Measurement Sequence Chart .....                                                | 19        |
+| D.2.1                         | UE Based GPS Message Sequence Normal.....                                                      | 19        |
+| D.2.2                         | UE Based GPS Message Sequence Normal for moving scenario and periodic update test case.....    | 21        |
+| D.2.3                         | UE Based GPS Message Sequence Failure.....                                                     | 22        |
+| D.3                           | UE Assisted A-GPS Measurement Sequence Chart .....                                             | 22        |
+| D.3.1                         | UE Assisted A-GPS Measurement Sequence Chart Normal .....                                      | 22        |
+| D.3.2                         | UE assisted A-GPS Measurement Sequence for moving scenario and periodic update test case ..... | 24        |
+| <b>Annex E (normative):</b>   | <b>Assistance data required for testing .....</b>                                              | <b>25</b> |
+| E.1                           | Introduction.....                                                                              | 25        |
+| E.2                           | Information elements required for UE-based.....                                                | 25        |
+| E.3                           | Information elements available for UE-assisted .....                                           | 26        |
+| <b>Annex F (normative):</b>   | <b>Converting UE-assisted measurement reports into position estimates ....</b>                 | <b>29</b> |
+| F.1                           | Introduction.....                                                                              | 29        |
+| F.2                           | UE measurement reports .....                                                                   | 29        |
+| F.3                           | WLS position solution .....                                                                    | 30        |
+| <b>Annex G (informative):</b> | <b>Change History.....</b>                                                                     | <b>32</b> |
+
+# --- Foreword
+
+This Technical Specification 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 establishes the minimum performance requirements for A-GPS for FDD mode of UTRA for the User Equipment (UE).
+
+# --- 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 TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [3] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)".
+- [4] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [5] 3GPP TS 25.302: "Services provided by the physical layer".
+- [6] 3GPP TS 25.215: "Physical layer; Measurements (FDD)".
+- [7] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [8] Navstar GPS Space Segment/Navigation User Interfaces, ICD-GPS 200, Rev. C.
+- [9] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996.
+- [10] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119.
+- [11] 3GPP TS 34.109: "Special conformance testing functions"
+
+# --- 3 Definitions, symbols, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.101 [1], 3GPP TS 25.104 [2] and the following apply:
+
+**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna
+
+**Node B:** logical node responsible for radio transmission / reception in one or more cells to/from the User Equipment. Terminates the Iub interface towards the RNC
+
+**L1:** L band GPS transmission frequency of 1575.42 MHz
+
+## 3.2 Symbols
+
+Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                           |
+|-------|-----------------------------------------------------------|
+| A-GPS | Assisted - Global Positioning System                      |
+| AWGN  | Additive White Gaussian Noise                             |
+| C/A   | Coarse/Acquisition                                        |
+| CPICH | Common Pilot CHannel                                      |
+| DCH   | Dedicated CHannel                                         |
+| DPCH  | Dedicated Physical CHannel                                |
+| DUT   | Device Under Test                                         |
+| ECEF  | Earth Centred, Earth Fixed                                |
+| FACH  | Fast Access CHannel                                       |
+| FDD   | Frequency Division Duplex                                 |
+| GPS   | Global Positioning System                                 |
+| GSS   | GPS System Simulator                                      |
+| HDOP  | Horizontal Dilution Of Precision                          |
+| LOS   | Line Of Sight                                             |
+| PICH  | Paging Indicator CHannel                                  |
+| RRC   | Radio Resource Control                                    |
+| RSCP  | Received Signal Code Power                                |
+| SFN   | System Frame Number                                       |
+| SMLC  | Standalone Mobile Location Center                         |
+| SRNC  | Serving Radio Network Controller                          |
+| SS    | FDD System simulator                                      |
+| TDD   | Time Division Duplex                                      |
+| TLM   | TeLeMetry word. It contains an 8-bits preamble (10001011) |
+| TOW   | Time Of Week                                              |
+| TTFF  | Time To First Fix                                         |
+| UE    | User Equipment                                            |
+| UTRA  | Universal Terrestrial Radio Access                        |
+| UTRAN | Universal Terrestrial Radio Access Network                |
+| WLS   | Weighted Least Square                                     |
+
+## 3.4 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.171 [3] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETR 273-1-2 [7], subclause 6.5.
+
+# 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for both UE based and UE assisted FDD A-GPS terminals.
+
+## 4.2 Measurement parameters
+
+### 4.2.1 UE based A-GPS measurement parameters
+
+In case of UE-based A-GPS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GPS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
+
+### 4.2.2 UE assisted A-GPS measurement parameters
+
+In case of UE-assisted A-GPS, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GPS are the UE GPS Code Phase measurements, as specified in 3GPP TS 25.302 [5] and 3GPP TS 25.215 [6]. The UE GPS Code Phase measurements are converted into a horizontal position estimate using the procedure detailed in Annex F.
+
+## 4.3 Response time
+
+Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [11] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10.
+
+## 4.4 Time assistance
+
+Time assistance is the provision of GPS time to the UE from the network via RRC messages. Currently two different GPS time assistance methods can be provided by the network.
+
+- a) Coarse time assistance is always provided by the network and provides current GPS time to the UE. The time provided is within  $\pm 2$  seconds of GPS system time. This allows the GPS time to be known within one GPS navigation data sub-frame. It is signalled to the UE by means of the GPS Week and GPS TOW msec fields in the Reference Time assistance data IE.
+- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GPS system time and the current UTRAN time. The accuracy of this relationship is  $\pm 10 \mu\text{s}$  of the actual relationship. This addresses the case when the network can provide an improved GPS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GPS timing of cell frames fields in the Reference Time assistance data IE.
+
+The time of applicability of time assistance is the beginning of the System Frame of the message containing the GPS Reference time.
+
+### 4.4.1 Use of fine time assistance
+
+The use of fine time assistance to improve the GPS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2.
+
+## 4.5 RRC states
+
+The minimum A-GPS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in annex B.
+
+## 4.6 2D position error
+
+The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered.
+
+# 5 A-GPS minimum performance requirements
+
+The A-GPS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in annexes D and E.
+
+The requirements in CELL\_PCH and URA\_PCH states are for further study.
+
+## 5.1 Sensitivity
+
+A sensitivity requirement is essential for verifying the performance of A-GPS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.
+
+### 5.1.1 Coarse time assistance
+
+In this test case 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 1: Test parameters**
+
+| Parameters                             | Unit    | Value      |
+|----------------------------------------|---------|------------|
+| Number of generated satellites         | -       | 8          |
+| HDOP Range                             | -       | 1.1 to 1.6 |
+| Propagation conditions                 | -       | AWGN       |
+| GPS Coarse time assistance error range | seconds | ±2         |
+| GPS Signal for one satellites          | dBm     | -142       |
+| GPS Signal for remaining satellites    | dBm     | -147       |
+
+#### 5.1.1.1 Minimum Requirements (Coarse time assistance)
+
+The position estimates shall meet the accuracy and response time specified in table 2.
+
+**Table 2: Minimum requirements (coarse time assistance)**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+### 5.1.2 Fine time assistance
+
+This requirement is only valid for fine time assistance capable UEs. In this requirement 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 3: Test parameters for fine time assistance capable terminals**
+
+| Parameters                             | Unit          | Value      |
+|----------------------------------------|---------------|------------|
+| Number of generated satellites         | -             | 8          |
+| HDOP Range                             | -             | 1.1 to 1.6 |
+| Propagation conditions                 | -             | AWGN       |
+| GPS Coarse time assistance error range | seconds       | $\pm 2$    |
+| GPS Fine time assistance error range   | $\mu\text{s}$ | $\pm 10$   |
+| GPS Signal for all satellites          | dBm           | -147       |
+
+#### 5.1.2.1 Minimum Requirements (Fine time assistance)
+
+The position estimates shall meet the accuracy and response time requirements in table 4.
+
+**Table 4: Minimum requirements for fine time assistance capable terminals**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.2 Nominal Accuracy
+
+Nominal accuracy requirement verifies the accuracy of A-GPS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.
+
+In this requirement 8 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5: Test parameters**
+
+| Parameters                             | Unit    | Value      |
+|----------------------------------------|---------|------------|
+| Number of generated satellites         | -       | 8          |
+| HDOP Range                             | -       | 1.1 to 1.6 |
+| Propagation conditions                 | -       | AWGN       |
+| GPS Coarse time assistance error range | seconds | $\pm 2$    |
+| GPS Signal for all satellites          | dBm     | -130       |
+
+### 5.2.1 Minimum requirements (nominal accuracy)
+
+The position estimates shall meet the accuracy and response time requirements in table 6.
+
+**Table 6: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 30 m               | 20 s              |
+
+## 5.3 Dynamic Range
+
+The aim of a dynamic range requirement is to ensure that a GPS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 7: Test parameters**
+
+| Parameters                               | Unit    | Value      |
+|------------------------------------------|---------|------------|
+| Number of generated satellites           | -       | 6          |
+| HDOP Range                               | -       | 1.4 to 2.1 |
+| GPS Coarse time assistance error range   | seconds | $\pm 2$    |
+| Propagation conditions                   | -       | AWGN       |
+| GPS Signal for 1 <sup>st</sup> satellite | dBm     | -129       |
+| GPS Signal for 2 <sup>nd</sup> satellite | dBm     | -135       |
+| GPS Signal for 3 <sup>rd</sup> satellite | dBm     | -141       |
+| GPS Signal for 4 <sup>th</sup> satellite | dBm     | -147       |
+| GPS Signal for 5 <sup>th</sup> satellite | dBm     | -147       |
+| GPS Signal for 6 <sup>th</sup> satellite | dBm     | -147       |
+
+### 5.3.1 Minimum requirements (dynamic range)
+
+The position estimates shall meet the accuracy and response time requirements in table 8.
+
+**Table 8: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.4 Multi-Path scenario
+
+The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.
+
+In this requirement 5 satellites are generated for the terminal. Two of the satellites have one tap channel representing Line-Of-Sight (LOS) signal. The three other satellites have two-tap channel, where the first tap represents LOS signal and the second reflected and attenuated signal as specified in Case G1 in subclause C.2.2.
+
+**Table 9: Test parameters**
+
+| Parameters                                                                                                               | Unit    | Value                                                 |
+|--------------------------------------------------------------------------------------------------------------------------|---------|-------------------------------------------------------|
+| Number of generated satellites (Satellites 1, 2 unaffected by multi-path)<br>(Satellites 3, 4, 5 affected by multi-path) | -       | 5                                                     |
+| GPS Coarse time assistance error range                                                                                   | seconds | $\pm 2$                                               |
+| HDOP Range                                                                                                               | -       | 1.8 to 2.5                                            |
+| Satellite 1, 2 signal                                                                                                    | dBm     | -130                                                  |
+| Satellite 3, 4, 5 signal                                                                                                 | dBm     | LOS signal of -130 dBm, multi-path signal of -136 dBm |
+
+### 5.4.1 Minimum Requirements (multi-path scenario)
+
+The position estimates shall meet the accuracy and response time requirements in table 10.
+
+**Table 10: Minimum requirements**
+
+| Success rate | 2-D position error | Max response time |
+|--------------|--------------------|-------------------|
+| 95 %         | 100 m              | 20 s              |
+
+## 5.5 Moving scenario and periodic update
+
+The purpose of the test case is to verify the receiver's capability to produce GPS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for a certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GPS receiver in changing UE speed and direction. In the requirement the UE
+
+moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.
+
+In this requirement 5 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.
+
+The UE moves on a rectangular trajectory of 940 m by 1 440 m with rounded corner defined in figure 1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
+
+**Table 11: Trajectory Parameters**
+
+| Parameter                        | Distance (m) | Speed (km/h)            |
+|----------------------------------|--------------|-------------------------|
+| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20           | 25                      |
+| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250          | 25 to 100 and 100 to 25 |
+| $l_{13}$                         | 400          | 100                     |
+| $l_{23}$                         | 900          | 100                     |
+
+![Figure 1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangular path with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The path is defined by segments l11, l12, l13, l14, l15 on the top and l21, l22, l23, l24, l25 on the bottom. Arrows indicate the direction of travel.](78ffccd66df9bafd96e3e081110d09dd_img.jpg)
+
+Figure 1: Rectangular trajectory of the moving scenario and periodic update test case. The diagram shows a rectangular path with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The path is defined by segments l11, l12, l13, l14, l15 on the top and l21, l22, l23, l24, l25 on the bottom. Arrows indicate the direction of travel.
+
+**Figure 1: Rectangular trajectory of the moving scenario and periodic update test case**
+
+**Table 12: Test Parameters**
+
+| Parameters                     | Unit | Value      |
+|--------------------------------|------|------------|
+| Number of generated satellites | -    | 5          |
+| HDOP Range                     | -    | 1.8 to 2.5 |
+| Propagation condition          | -    | AWGN       |
+| GPS signal for all satellites  | dBm  | -130       |
+
+### 5.5.1 Minimum Requirements (moving scenario and periodic update)
+
+The position estimates shall meet the accuracy requirement of table 13 with the periodical reporting interval defined in table 13 after the first reported position estimates.
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 13.
+
+**Table 13: Minimum requirements**
+
+| Success Rate | 2-D position error | Periodical reporting interval |
+|--------------|--------------------|-------------------------------|
+| 95 %         | 100 m              | 2 s                           |
+
+# --- Annex A (normative): Test cases
+
+## A.1 Conformance tests
+
+The conformance tests are specified in 3GPP TS 34.171 [3]. Statistical interpretation of the requirements is described in clause A.2.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 34.171 [3].
+
+# Annex B (normative): Test conditions
+
+## B.1 General
+
+This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated.
+
+### B.1.1 Parameter values
+
+Additionally, amongst all the listed parameters (see annex E), the following values for some important parameters are to be used in the measurement control message.
+
+**Table B.1: Parameter values**
+
+| Information element                                 | Value - TTFF tests<br>(except nominal<br>accuracy test) | Value - TTFF tests<br>(nominal accuracy<br>test) | Value - Periodic tests |
+|-----------------------------------------------------|---------------------------------------------------------|--------------------------------------------------|------------------------|
+| Measurement Reporting Mode                          | Periodical reporting                                    | Periodical reporting                             | Periodical reporting   |
+| Amount of reporting                                 | 1                                                       | 1                                                | Infinite (see note)    |
+| Reporting interval                                  | 20 000 ms                                               | 20 000 ms                                        | 2 000 ms               |
+| Horizontal accuracy                                 | 50 m                                                    | 15 m                                             | 50 m                   |
+| Vertical accuracy                                   | 100 m                                                   | 100 m                                            | 100 m                  |
+| NOTE: Infinite means during the complete test time. |                                                         |                                                  |                        |
+
+In the Sensitivity test case with Fine Time Assistance, the following parameter values are used.
+
+**Table B.2: Parameters for Fine Time Assistance test**
+
+| Information element   | Value      |
+|-----------------------|------------|
+| TUTRAN-GPS drift rate | 0          |
+| SFN-TOW Uncertainty   | lessThan10 |
+
+### B.1.2 Time assistance
+
+For every Test Instance in each TTFF test case, the IE GPS TOW msec shall have a random offset, relative to GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+For the Moving Scenario and Periodic Update Test Case the IE GPS TOW msec shall be set to the nominal value.
+
+### B.1.3 GPS Reference Time
+
+For every Test Instance in each TTFF test case, the GPS reference time shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix.
+
+### B.1.4 Reference and UE locations
+
+There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %.
+
+For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions.
+
+### B.1.5 Satellite constellation and assistance data
+
+The satellite constellation shall consist of 24 satellites. Almanac assistance data shall be available for all these 24 satellites. At least 9 of the satellites shall be visible to the UE (that is above 5 degrees elevation with respect to the UE). Other assistance data shall be available for 9 of these visible satellites. In each test, signals are generated for only a sub-set of these satellites for which other assistance data is available. The number of satellites in this sub-set is specified in the test. The satellites in this sub-set shall all be above 15 degrees elevation with respect to the UE. The HDOP for the test shall be calculated using this sub-set of satellites. The selection of satellites for this sub-set shall be random and consistent with achieving the required HDOP for the test.
+
+### B.1.6 Atmospheric delays
+
+Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs.
+
+### B.1.7 UTRA Frequency and frequency error
+
+In all test cases the UTRA frequency used shall be the mid range for the UTRA operating band. The UTRA frequency with respect to the GPS carrier frequency shall be offset by +0.025 PPM.
+
+### B.1.8 Information elements
+
+The information elements that are available to the UE in all the test cases are listed in annex E.
+
+### B.1.9 GPS signals
+
+The GPS signal is defined at the A-GPS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
+
+### B.1.10 RESET UE POSITIONING STORED INFORMATION Message
+
+In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [11] clause 5.4 shall be used.
+
+When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGPS* it shall:
+
+- discard any internally stored GPS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler);
+- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition;
+- calculate the position or perform GPS measurements using the 'new' reference time or reference location or other information.
+
+# Annex C (normative): Propagation conditions
+
+## C.1 General
+
+Void
+
+## C.2 Propagation Conditions
+
+### C.2.1 Static propagation conditions
+
+The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
+
+### C.2.2 Multi-path Case G1
+
+Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GPS L1 signal are defined in table C.1.
+
+**Table C.1: Case G1**
+
+| Initial relative Delay [GPS chip]                      | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] |
+|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------|
+| 0                                                      | $F_d$                                 | $F_d / N$                          | 0                        |
+| 0.5                                                    | $F_d - 0.1$                           | $(F_d - 0.1) / N$                  | -6                       |
+| NOTE: Discrete Doppler frequency is used for each tap. |                                       |                                    |                          |
+
+$N = f_{\text{GPSL1}} / f_{\text{chip}}$ , where  $f_{\text{GPSL1}}$  is the nominal carrier frequency of the GPS L1 signal (1575.42 MHz) and  $f_{\text{chip}}$  is the GPS L1 C/A code chip rate (1.023 Mchips/s).
+
+The initial carrier phase difference between taps shall be randomly selected between  $[0, 2\pi]$ . The initial value shall have uniform random distribution.
+
+# --- Annex D (normative): Measurement sequence chart
+
+## D.1 General
+
+The measurement Sequence Charts that are required in all the proposed test cases, are defined in this clause.
+
+---
+
+## D.2 UE Based A-GPS Measurement Sequence Chart
+
+### D.2.1 UE Based GPS Message Sequence Normal
+
+![Sequence diagram showing UE-Based GPS Message Sequence Normal between SRNC and UE.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (1))
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (1), Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (1), ReferencePosition (1))
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), 1st test instance
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (2))
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (2), Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (2), ReferencePosition (2))
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), 2nd test instance
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    Note right of SRNC: .....
+    UE-->>SRNC: RRC Measurement Report (Position Estimate), nth test instance
+```
+
+The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a UE (User Equipment) for a UE-based GPS message sequence. The sequence starts with the SRNC sending a 'RESET UE POSITIONING STORED INFORMATION' message to the UE. This is followed by three RRC measurement control messages from the SRNC to the UE: 'RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (1))', 'RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (1), Iono Model)', and 'RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (1), ReferencePosition (1))'. The UE then responds with an 'RRC Measurement Report (Position Estimate), 1<sup>st</sup> test instance'. The SRNC sends another 'RESET UE POSITIONING STORED INFORMATION' message, followed by three more RRC measurement control messages: 'RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5 (2))', 'RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9 (2), Iono Model)', and 'RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time (2), ReferencePosition (2))'. The UE responds with an 'RRC Measurement Report (Position Estimate), 2<sup>nd</sup> test instance'. The SRNC sends a third 'RESET UE POSITIONING STORED INFORMATION' message, followed by a series of dots indicating further instances. Finally, the UE sends an 'RRC Measurement Report (Position Estimate), n<sup>th</sup> test instance'.
+
+Sequence diagram showing UE-Based GPS Message Sequence Normal between SRNC and UE.
+
+**Figure D.1: UE-Based GPS Message Sequence Normal**
+
+### D.2.2 UE Based GPS Message Sequence Normal for moving scenario and periodic update test case
+
+![Sequence diagram showing the message exchange between SRNC and UE for a UE-based GPS test case.](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1, 2, 3, 4, 5)
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition)
+    Note left of UE: RRC Measurement Report (Position Estimate)
+    UE->>SRNC: RRC Measurement Report (Position Estimate)
+    Note left of UE: RRC Measurement Report (Position Estimate)
+    UE->>SRNC: RRC Measurement Report (Position Estimate)
+    Note left of UE: ...
+    Note left of UE: RRC Measurement Report (Position Estimate)
+    UE->>SRNC: RRC Measurement Report (Position Estimate)
+```
+
+The diagram illustrates the message sequence between an SRNC (Radio Network Controller) and a UE (User Equipment) for a UE-based GPS test case. The sequence starts with the SRNC sending a 'RESET UE POSITIONING STORED INFORMATION' message to the UE. This is followed by three 'RRC measurement control' messages from the SRNC to the UE: the first sets up reporting for satellites 1, 2, 3, 4, and 5; the second modifies the reporting for satellites 6, 7, 8, 9, and an ionospheric model; the third modifies the reporting to include periodic reporting criteria, GPS reference time, and reference position. The UE then responds with a series of 'RRC Measurement Report (Position Estimate)' messages, indicated by arrows pointing from the UE to the SRNC. There are three explicit reports shown, with a vertical ellipsis between the second and third, indicating multiple reports over time.
+
+Sequence diagram showing the message exchange between SRNC and UE for a UE-based GPS test case.
+
+**Figure D.2: UE-Based GPS Message Sequence Normal for moving scenario test case**
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire a position estimate.
+
+### D.2.3 UE Based GPS Message Sequence Failure
+
+![Sequence diagram showing UE Based GPS Message Sequence Failure between SRNC and UE.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5)
+    SRNC->>UE: RRC measurement control (Setup, No Reporting, Nav model Satellites 1,2,3,4,5)
+    Note right of SRNC: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model)
+    SRNC->>UE: RRC measurement control (Modify, No Reporting, Nav model Satellites 6,7,8,9, Iono Model)
+    Note right of SRNC: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition)
+    SRNC->>UE: RRC measurement control (Modify, Periodical Reporting Criterion, GPS Ref time, ReferencePosition)
+    Note left of UE: RRC Measurement Report (Position Error of type "There were not enough satellites to be received ")
+    UE->>SRNC: RRC Measurement Report (Position Error of type "There were not enough satellites to be received ")
+```
+
+The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a UE (User Equipment) for a UE-based GPS measurement sequence failure. The sequence starts with the SRNC sending three RRC measurement control messages to the UE. The first message is a 'Setup' with 'No Reporting' and a 'Nav model Satellites 1,2,3,4,5'. The second message is a 'Modify' with 'No Reporting' and a 'Nav model Satellites 6,7,8,9, Iono Model'. The third message is a 'Modify' with 'Periodical Reporting Criterion, GPS Ref time, ReferencePosition'. After these three messages, the UE sends an RRC Measurement Report to the SRNC. The report indicates a 'Position Error of type "There were not enough satellites to be received "'.
+
+Sequence diagram showing UE Based GPS Message Sequence Failure between SRNC and UE.
+
+Figure D.3: UE-Based GPS Message Sequence Failure
+
+## D.3 UE Assisted A-GPS Measurement Sequence Chart
+
+### D.3.1 UE Assisted A-GPS Measurement Sequence Chart Normal
+
+The assistance data requested by the UE and provided by the SRNC in this sequence of messages shall be selected from among those information elements described as available in clause E.3.
+
+![Sequence diagram showing UE-Assisted GPS Message Sequence between SRNC and UE. The sequence includes RESET UE POSITIONING STORED INFORMATION, RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time), RRC Measurement Report (Additional Assistance Data Request), RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9), RRC Measurement Control (Modify, Periodical Reporting Criteria), and RRC Measurement Report (GPS Measured Results #1, #2, ..., #n).](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    SRNC->>UE: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #1)
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    SRNC->>UE: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #2)
+    Note right of SRNC: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: ...
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #n)
+```
+
+Sequence diagram showing UE-Assisted GPS Message Sequence between SRNC and UE. The sequence includes RESET UE POSITIONING STORED INFORMATION, RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time), RRC Measurement Report (Additional Assistance Data Request), RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9), RRC Measurement Control (Modify, Periodical Reporting Criteria), and RRC Measurement Report (GPS Measured Results #1, #2, ..., #n).
+
+Figure D.4: UE-Assisted GPS Message Sequence
+
+### D.3.2 UE assisted A-GPS Measurement Sequence for moving scenario and periodic update test case
+
+The assistance data requested by the UE and provided by the SRNC in this sequence of messages shall be selected from among those information elements described as available in clause E.3.
+
+![Sequence diagram showing the UE assisted GPS message sequence for a moving scenario and periodic update. The sequence involves SRNC and UE interactions with messages like RESET UE POSITIONING STORED INFORMATION, RRC Measurement Control, and RRC Measurement Report.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg)
+
+```
+sequenceDiagram
+    participant SRNC
+    participant UE
+    Note over SRNC, UE: RESET UE POSITIONING STORED INFORMATION
+    SRNC->>UE: RRC Measurement Control (Setup, Periodical Reporting Criteria, GPS Reference Time)
+    UE-->>SRNC: RRC Measurement Report (Additional Assistance Data Request)
+    SRNC->>UE: RRC Measurement Control (Modify, No Reporting, Assistance Data Satellites 1,2,3,4,5,6,7,8,9)
+    SRNC->>UE: RRC Measurement Control (Modify, Periodical Reporting Criteria)
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #1)
+    Note over SRNC, UE: ...
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #2)
+    Note over SRNC, UE: ...
+    UE-->>SRNC: RRC Measurement Report (GPS Measured Results #n)
+```
+
+Sequence diagram showing the UE assisted GPS message sequence for a moving scenario and periodic update. The sequence involves SRNC and UE interactions with messages like RESET UE POSITIONING STORED INFORMATION, RRC Measurement Control, and RRC Measurement Report.
+
+**Figure D.5: UE assisted GPS Message Sequence for moving scenario and periodic update**
+
+**NOTE:** In the actual testing the UE may report error messages until it has been able to acquire GPS measured results.
+
+# Annex E (normative): Assistance data required for testing
+
+## E.1 Introduction
+
+This annex defines the assistance data IEs available in all test cases. The assistance data shall be given for satellites as defined in B.1.5.
+
+The information elements are given with reference to 3GPP TS 25.331 [4], where the details are defined.
+
+Clause E.2 lists the assistance data IEs required for testing of UE-based mode, and clause E.3 lists the assistance data available for testing of UE-assisted mode.
+
+## E.2 Information elements required for UE-based
+
+The following GPS assistance data IEs shall be present for each test:
+
+- a) **UE positioning GPS reference time IE.** This information element is defined in subclause 10.3.7.96 of 3GPP TS 25.331 [4].
+
+**Table E.1: UE positioning GPS reference time IE**
+
+| Name of the IE                                                                    | Fields of the IE                 | UE Based Coarse time | UE Based Fine Time |
+|-----------------------------------------------------------------------------------|----------------------------------|----------------------|--------------------|
+| UE positioning GPS reference time<br>subclause 10.3.7.96 of<br>3GPP TS 25.331 [4] |                                  |                      |                    |
+|                                                                                   | GPS Week                         | Yes                  | Yes                |
+|                                                                                   | GPS TOW msec                     | Yes                  | Yes                |
+|                                                                                   | UTRAN GPS reference time         |                      | Yes                |
+|                                                                                   | >UTRAN GPS timing of cell frames |                      | Yes                |
+|                                                                                   | >CHOICE mode                     |                      | Yes                |
+|                                                                                   | >>FDD                            |                      | Yes                |
+|                                                                                   | >>>Primary CPICH Info            |                      | Yes                |
+|                                                                                   | >>TDD                            |                      |                    |
+|                                                                                   | >>>cell parameters id            |                      |                    |
+|                                                                                   | >SFN                             |                      | Yes                |
+|                                                                                   | SFN-TOW Uncertainty              |                      | Yes                |
+|                                                                                   | TUTRAN-GPS drift rate            |                      | Yes                |
+|                                                                                   | GPS TOW Assist                   | Yes                  | Yes                |
+|                                                                                   | SatID                            | Yes                  | Yes                |
+|                                                                                   | TLM Message                      | Yes                  | Yes                |
+|                                                                                   | TLM Reserved                     | Yes                  | Yes                |
+|                                                                                   | Alert                            | Yes                  | Yes                |
+|                                                                                   | Anti-Spoof                       | Yes                  | Yes                |
+
+- b) **UE positioning GPS reference UE position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [4].
+
+**Table E.2: UE positioning GPS reference UE position IE**
+
+| Name of the IE                                                     | Fields of the IE                                        | UE Based Coarse time | UE Based Fine Time |
+|--------------------------------------------------------------------|---------------------------------------------------------|----------------------|--------------------|
+| Reference Location<br>subclause 10.3.8.4c of<br>3GPP TS 25.331 [4] | Ellipsoid point with Altitude and uncertainty ellipsoid | Yes                  | Yes                |
+
+- c) **UE positioning GPS navigation model IE.** This information element is defined in subclause 10.3.7.94 of 3GPP TS 25.331 [4]. The Navigation model will be chosen for the reference time and reference position.
+
+**Table E.3: UE positioning GPS navigation model IE**
+
+| Name of the IE                                                   | Fields of the IE | UE Based Coarse time | UE Based Fine Time |
+|------------------------------------------------------------------|------------------|----------------------|--------------------|
+| Navigation Model<br>subclause 10.3.7.94 of<br>3GPP TS 25.331 [4] |                  | Yes                  | Yes                |
+
+- d) **UE positioning GPS ionospheric model IE.** This information element is defined in subclause 10.3.7.92 of 3GPP TS 25.331 [4].
+
+**Table E.4: UE positioning GPS ionospheric model IE**
+
+| Name of the IE                                                    | Fields of the IE | UE Based Coarse time | UE Based Fine Time |
+|-------------------------------------------------------------------|------------------|----------------------|--------------------|
+| Ionospheric Model<br>subclause 10.3.7.92 of<br>3GPP TS 25.331 [4] |                  | Yes                  | Yes                |
+
+## E.3 Information elements available for UE-assisted
+
+The following GPS assistance data IEs shall be available for each test:
+
+- a) **UE positioning GPS reference time IE.** This information element is defined in subclause 10.3.7.96 of 3GPP TS 25.331 [4].
+
+**Table E.5: UE positioning GPS reference time IE**
+
+| Name of the IE                                                                    | Fields of the IE                 | UE Assisted Coarse time | UE Assisted Fine Time |
+|-----------------------------------------------------------------------------------|----------------------------------|-------------------------|-----------------------|
+| UE positioning GPS reference time<br>subclause 10.3.7.96 of<br>3GPP TS 25.331 [4] |                                  |                         |                       |
+|                                                                                   | GPS Week                         | Yes                     | Yes                   |
+|                                                                                   | GPS TOW msec                     | Yes                     | Yes                   |
+|                                                                                   | UTRAN GPS reference time         |                         | Yes                   |
+|                                                                                   | >UTRAN GPS timing of cell frames |                         | Yes                   |
+|                                                                                   | >CHOICE mode                     |                         | Yes                   |
+|                                                                                   | >>FDD                            |                         | Yes                   |
+|                                                                                   | >>>Primary CPICH Info            |                         | Yes                   |
+|                                                                                   | >>TDD                            |                         |                       |
+|                                                                                   | >>>cell parameters id            |                         |                       |
+|                                                                                   | >SFN                             |                         | Yes                   |
+|                                                                                   | SFN-TOW Uncertainty              |                         | Yes                   |
+|                                                                                   | TUTRAN-GPS drift rate            |                         | Yes                   |
+|                                                                                   | GPS TOW Assist                   | Yes                     | Yes                   |
+|                                                                                   | SatID                            | Yes                     | Yes                   |
+|                                                                                   | TLM Message                      | Yes                     | Yes                   |
+|                                                                                   | TLM Reserved                     | Yes                     | Yes                   |
+|                                                                                   | Alert                            | Yes                     | Yes                   |
+|                                                                                   | Anti-Spoof                       | Yes                     | Yes                   |
+
+- b) **UE positioning GPS reference UE position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [4].
+
+**Table E.6: UE positioning GPS reference UE position IE**
+
+| Name of the IE                                               | Fields of the IE                                        | UE Assisted Coarse Time | UE Assisted Fine Time |
+|--------------------------------------------------------------|---------------------------------------------------------|-------------------------|-----------------------|
+| Reference Location subclause 10.3.8.4c of 3GPP TS 25.331 [4] | Ellipsoid point with Altitude and uncertainty ellipsoid | Yes                     | Yes                   |
+
+- c) **UE positioning GPS almanac** This information element is defined in subclause 10.3.7.89 of 3GPP TS 25.331 [4]. The Almanac shall be chosen for the reference time.
+
+**Table E.7: UE positioning GPS almanac IE**
+
+| Name of the IE                                                       | Fields of the IE       | UE Assisted Coarse Time | UE Assisted Fine Time |
+|----------------------------------------------------------------------|------------------------|-------------------------|-----------------------|
+| UE positioning GPS almanac subclause 10.3.7.89 of 3GPP TS 25.331 [4] |                        |                         |                       |
+|                                                                      | Almanac Reference Week | Yes                     | Yes                   |
+|                                                                      | Satellite information  | Yes                     | Yes                   |
+
+- d) **UE positioning GPS navigation model IE.** This information element is defined in subclause 10.3.7.94 of 3GPP TS 25.331 [4]. The Navigation model will be chosen for the reference time and reference position.
+
+**Table E.8: UE positioning GPS navigation model IE**
+
+| Name of the IE                                             | Fields of the IE | UE Assisted Coarse Time | UE Assisted Fine Time |
+|------------------------------------------------------------|------------------|-------------------------|-----------------------|
+| Navigation Model subclause 10.3.7.94 of 3GPP TS 25.331 [4] |                  | Yes                     | Yes                   |
+
+- e) **UE positioning GPS acquisition assistance IE.** This information element is defined in subclause 10.3.7.88 of 3GPP TS 25.331 [4].
+
+**Table E.9: UE positioning GPS acquisition assistance IE**
+
+| Name of the IE                                                   | Fields of the IE                       | UE Assisted Coarse time | UE Assisted Fine Time |
+|------------------------------------------------------------------|----------------------------------------|-------------------------|-----------------------|
+| Acquisition Assistance subclause 10.3.7.88 of 3GPP TS 25.331 [4] |                                        |                         |                       |
+| -                                                                | GPS TOW msec                           | Yes                     | Yes                   |
+| -                                                                | UTRAN GPS reference time               |                         | Yes                   |
+| -                                                                | >UTRAN GPS timing of cell frames       |                         | Yes                   |
+| -                                                                | >CHOICE <i>mode</i>                    |                         | Yes                   |
+| -                                                                | >>FDD                                  |                         | Yes                   |
+| -                                                                | >>>Primary CPICH Info                  |                         | Yes                   |
+| -                                                                | >SFN                                   |                         | Yes                   |
+| -                                                                | Satellite information                  | Yes                     | Yes                   |
+| -                                                                | >SatID                                 | Yes                     | Yes                   |
+|                                                                  | >Doppler (0 <sup>th</sup> order term)  | Yes                     | Yes                   |
+|                                                                  | >Extra Doppler                         | Yes                     | Yes                   |
+|                                                                  | >>Doppler (1 <sup>st</sup> order term) | Yes                     | Yes                   |
+|                                                                  | >>Doppler Uncertainty                  | Yes                     | Yes                   |
+|                                                                  | >Code Phase                            | Yes                     | Yes                   |
+|                                                                  | >Integer Code Phase                    | Yes                     | Yes                   |
+|                                                                  | >GPS Bit number                        | Yes                     | Yes                   |
+|                                                                  | >Code Phase Search Window              | Yes                     | Yes                   |
+|                                                                  | >Azimuth and Elevation                 | Yes                     | Yes                   |
+|                                                                  | >> Azimuth                             | Yes                     | Yes                   |
+|                                                                  | >> Elevation                           | Yes                     | Yes                   |
+
+# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates
+
+## F.1 Introduction
+
+To convert the UE measurement reports in case of UE-assisted mode of A-GPS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [8], [9] and [10].
+
+## --- F.2 UE measurement reports
+
+In case of UE-assisted A-GPS, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [4]). The measurement parameters required for calculating the UE position are:
+
+- 1) Reference Time: The UE has two choices for the Reference Time:
+  - a) "UE GPS timing of cell frames";
+  - b) "GPS TOW msec".
+- 2) Measurement Parameters: 1 to <maxSat>:
+  - a) "Satellite ID (SV PRN)";
+  - b) "Whole GPS chips";
+  - c) "Fractional GPS Chips";
+  - d) "Pseudorange RMS Error".
+
+Additional information required at the system simulator:
+
+- 1) "UE positioning GPS reference UE position" (subclause 10.3.8.4c in 3GPP TS 25.331 [4]):  
+Used for initial approximate receiver coordinates.
+- 2) "UE positioning GPS navigation model" (subclause 10.3.7.94 in 3GPP TS 25.331 [4]):  
+Contains the GPS ephemeris and clock correction parameters as specified in [8]; used for calculating the satellite positions and clock corrections.
+- 3) "UE positioning GPS ionospheric model" (subclause 10.3.7.92 in 3GPP TS 25.331 [4]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [8] for computation of the ionospheric delay.
+
+## F.3 WLS position solution
+
+The WLS position solution problem is concerned with the task of solving for four unknowns;  $x_u, y_u, z_u$  the receiver coordinates in a suitable frame of reference (usually ECEF) and  $b_u$  the receiver clock bias. It typically requires the following steps:
+
+### Step 1: Formation of pseudo-ranges
+
+The observation of code phase reported by the UE for each satellite  $SV_i$  is related to the pseudo-range/c modulo 1 ms (the length of the C/A code period). For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite  $SV_i$  is calculated and the integer number of milli-seconds to be added to the UE code phase measurements is obtained.
+
+### Step 2: Formation of weighting matrix
+
+The UE reported "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm [9]. According to 3GPP TS 25.331 [4], the encoding for this field is a 6 bit value that consists of a 3 bit mantissa,  $X_i$  and a 3 bit exponent,  $Y_i$  for each  $SV_i$ :
+
+$$w_i = \text{RMSError} = 0.5 \times \left(1 + \frac{X_i}{8}\right) \times 2^{Y_i}$$
+
+The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Pseudorange RMS Error" values:
+
+$$W = \text{diag}\{1/w_1^2, 1/w_2^2, \dots, 1/w_n^2\}$$
+
+### Step 3: WLS position solution
+
+The WLS position solution is described in reference [9] and usually requires the following steps:
+
+- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in [8] section 20.3.3.4.3.
+- 2) Computation of clock correction parameters using the parameters and algorithms as defined in [8] section 20.3.3.3.3.1.
+- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in [8] section 20.3.3.5.2.5 for the ionospheric delay, and using the Gupta model in reference [10] p. 121 equation (2) for the tropospheric delay.
+- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
+  - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report.
+  - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in [8,9].
+  - c) Calculate difference between predicted and measured pseudo-ranges  $\Delta\rho$
+  - d) Calculate the "Geometry Matrix" **G** as defined in [9]:
+
+$$G \equiv \begin{bmatrix} -\hat{\mathbf{l}}_1^T & 1 \\ -\hat{\mathbf{l}}_2^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{l}}_n^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{l}}_i \equiv \frac{\mathbf{r}_{si} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{si} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{si} \text{ is the Satellite position vector for } SV_i \text{ (calculated in 1) above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$
+
+- e) Calculate the WLS solution according to [9]:
+
+$$\Delta \hat{x} = (G^T W G)^{-1} G^T W \Delta \rho$$
+
+- f) Adding the  $\Delta \hat{x}$  to the initial state estimate gives an improved estimate of the state vector:
+
+$$\hat{x} \rightarrow \hat{x} + \Delta \hat{x}.$$
+
+- 5) This new state vector  $\hat{x}$  can be used as new initial estimate and the procedure is repeated until the change in  $\hat{x}$  is sufficiently small.
+
+### Step 4: Transformation from Cartesian coordinate system to Geodetic coordinate system
+
+The state vector  $\hat{x}$  calculated in Step 3 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates  $x_u, y_u, z_u$  to geodetic latitude  $\phi$ , longitude  $\lambda$  and altitude  $h$  on the WGS84 reference ellipsoid.
+
+### Step 5: Calculation of "2-D Position Errors"
+
+The latitude  $\phi$  / longitude  $\lambda$  obtained after Step 4 is used to calculate the 2-D position error.
+
+# Annex G (informative): Change History
+
+**Table G.1: TS history before approval**
+
+| Date     | Meeting                        | Document  | Comment                                                                             | Version old | Version New |
+|----------|--------------------------------|-----------|-------------------------------------------------------------------------------------|-------------|-------------|
+|          | RAN WG4 #29                    | R4-031082 | Document proposed at RAN#29                                                         |             |             |
+|          | RAN WG4 #29                    | R4-031156 | Comments added inline with discussion at RAN#29                                     |             |             |
+| Dec 2003 |                                |           | Comment on R4-031156                                                                |             |             |
+| Jan 2004 | RAN WG4 #30                    | R4-040104 | Comments added after Ad-hoc 29/1/04                                                 |             |             |
+| Jan 2004 | RAN WG4 #29                    | R4-040169 | Revised version of R4-040104 to allow printing                                      |             |             |
+| May 2004 | RAN WG4 #31                    | R4-040362 | Revised version of R4-040233                                                        |             |             |
+| May 2004 | RAN WG4 #31                    | R4-040387 | Approved version at RAN#31                                                          |             |             |
+| May 2004 | RAN WG4 #31                    |           | V0.0.0 produced based on R4-040387                                                  |             | 0.0.0       |
+| May 2004 |                                |           | V0.1.0 with input from R4-040364                                                    | 0.0.0       | 0.1.0       |
+| Aug 2004 | Conference call on Aug 5, 2004 |           | V0.1.0 with approved CRs: R4-04043, R4-04048, R4AH-04049, R4AH-04050 and R4AH-04052 | 0.1.0       | 0.2.0       |
+| Aug 2004 | RAN WG4 #32                    | R4-040465 | V0.2.0 for approval at RAN WG4 #32                                                  |             |             |
+| Aug 2004 | RAN WG4 #32                    | R4-040564 | V0.3.0 for approval at RAN WG4 #32, inclusion of changes in R4-040535               | 0.2.0       | 0.3.0       |
+| Sep 2004 | RAN #25                        | RP-040341 | Submit for approval                                                                 | 0.3.0       | 1.0.0       |
+| Sep 2004 | RAN #25                        |           | Approved at RAN#24                                                                  | 1.0.0       | 6.0.0       |
+
+**Table G.2: Release 6 CR approved at TSG RAN #26**
+
+| RAN Tdoc  | Spec   | CR  | R | Ph    | Title                                   | Cat | Curr  | New   | Work Item          |
+|-----------|--------|-----|---|-------|-----------------------------------------|-----|-------|-------|--------------------|
+| RP-040413 | 25.171 | 001 | 2 | Rel-6 | Removal of inconsistencies in TS 25.171 | F   | 6.0.0 | 6.1.0 | LCS-UEPos-AGPSPerf |
+
+**Table G.3: Release 6 CR approved at TSG RAN #29**
+
+| RAN Tdoc  | Spec   | CR   | R | Ph    | Title                    | Cat | Curr  | New   | Work Item          |
+|-----------|--------|------|---|-------|--------------------------|-----|-------|-------|--------------------|
+| RP-050499 | 25.171 | 0003 | 1 | Rel-6 | Changes to GPS scenarios | F   | 6.1.0 | 6.2.0 | LCS-UEPos-AGPSPerf |
+
+**Table G.4: Creation of Release 7**
+
+| RAN Tdoc | Spec   | CR | R | Ph    | Title                                          | Cat | Curr  | New   | Work Item |
+|----------|--------|----|---|-------|------------------------------------------------|-----|-------|-------|-----------|
+|          | 25.171 |    |   | Rel-7 | Release 7 created following decision at RAN#31 |     | 6.1.0 | 7.0.0 |           |
+
+**Table G.4: Release 7 CRs approved at TSG RAN #32**
+
+| RAN Tdoc  | Spec   | CR   | R | Ph    | Title                                                          | Cat | Curr  | New   | Work Item |
+|-----------|--------|------|---|-------|----------------------------------------------------------------|-----|-------|-------|-----------|
+| RP-060305 | 25.171 | 0005 |   | Rel-7 | Horizontal Accuracy IE change for nominal accuracy requirement | A   | 7.0.0 | 7.1.0 | TEI6      |
+| RP-060305 | 25.171 | 0007 |   | Rel-7 | Change to altitude of simulated UE position                    | A   | 7.0.0 | 7.1.0 | TEI6      |
+
+**Table G.5: Release 8**
+
+| <b>RAN Meeting</b> | <b>RAN Tdoc</b> | <b>CR</b> | <b>R</b> | <b>Title</b>                   | <b>Cat</b> | <b>Curr</b> | <b>New</b> | <b>Work Item</b> |
+|--------------------|-----------------|-----------|----------|--------------------------------|------------|-------------|------------|------------------|
+| SP-42              |                 |           |          | Upgrade unchanged from Rel 7   |            |             | 8.0.0      |                  |
+| SP-46              |                 |           |          | Upgrade unchanged from Rel 8   |            |             | 9.0.0      |                  |
+| SP-51              |                 |           |          | Upgraded unchanged from Rel-9  |            | 9.0.0       | 10.0.0     |                  |
+| SP-57              | -               | -         | -        | Update to Rel-11 version (MCC) | -          | 10.0.0      | 11.0.0     | -                |
+| SP-65              | -               | -         | -        | Update to Rel-12 version (MCC) | -          | 11.0.0      | 12.0.0     |                  |
+| SP-70              | -               | -         | -        | Update to Rel-13 version (MCC) | -          | 12.0.0      | 13.0.0     |                  |
+| RP-75              | -               | -         | -        | Update to Rel-14 version (MCC) | -          | 13.0.0      | 14.0.0     |                  |
+
+| <b>Change history</b> |                |             |           |            |            |                                |  |                    |
+|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------|--|--------------------|
+| <b>Date</b>           | <b>Meeting</b> | <b>TDoc</b> | <b>CR</b> | <b>Rev</b> | <b>Cat</b> | <b>Subject/Comment</b>         |  | <b>New version</b> |
+| 2018-06               | SA#80          | -           | -         | -          | -          | Update to Rel-15 version (MCC) |  | 15.0.0             |
+| 2020-06               | SA#88          | -           | -         | -          | -          | Update to Rel-16 version (MCC) |  | <b>16.0.0</b>      |
+| 2022-03               | SA#95          |             |           |            |            | Update to Rel-17 version (MCC) |  | <b>17.0.0</b>      |

marked/Rel-17/25_series/25172/raw.md

@@ -0,0 +1,1143 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 5         |
+| 1 Scope.....                                                          | 6         |
+| 2 References.....                                                     | 6         |
+| 3 Definitions, symbols, abbreviations and test tolerances .....       | 7         |
+| 3.1 Definitions.....                                                  | 7         |
+| 3.2 Symbols.....                                                      | 7         |
+| 3.3 Abbreviations .....                                               | 7         |
+| 3.4 Test tolerances.....                                              | 8         |
+| 4 General.....                                                        | 8         |
+| 4.1 Introduction .....                                                | 8         |
+| 4.2 Measurement parameters.....                                       | 9         |
+| 4.2.1 UE-based A-GANSS measurement parameters .....                   | 9         |
+| 4.2.2 UE-assisted A-GANSS measurement parameters .....                | 9         |
+| 4.3 Response time .....                                               | 9         |
+| 4.4 Time assistance .....                                             | 9         |
+| 4.4.1 Use of fine time assistance .....                               | 9         |
+| 4.5 RRC states.....                                                   | 10        |
+| 4.6 2D position error .....                                           | 10        |
+| 4.7 User equipment supporting multiple constellations .....           | 10        |
+| 4.8 User equipment supporting multiple signals.....                   | 10        |
+| 5 A-GANSS minimum performance requirements.....                       | 10        |
+| 5.1 Sensitivity.....                                                  | 11        |
+| 5.1.1 Coarse time assistance.....                                     | 11        |
+| 5.1.1.1 Minimum requirements (coarse time assistance).....            | 11        |
+| 5.1.2 Fine time assistance.....                                       | 12        |
+| 5.1.2.1 Minimum requirements (fine time assistance).....              | 12        |
+| 5.2 Nominal accuracy.....                                             | 12        |
+| 5.2.1 Minimum requirements (nominal accuracy) .....                   | 13        |
+| 5.3 Dynamic range .....                                               | 13        |
+| 5.3.1 Minimum requirements (dynamic range).....                       | 14        |
+| 5.4 Multi-path scenario .....                                         | 14        |
+| 5.4.1 Minimum requirements (multi-path scenario).....                 | 15        |
+| 5.5 Moving scenario and periodic update .....                         | 15        |
+| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16        |
+| <b>Annex A (normative): Test cases.....</b>                           | <b>18</b> |
+| A.1 Conformance tests.....                                            | 18        |
+| A.2 Requirement classification for statistical testing .....          | 18        |
+| <b>Annex B (normative): Test conditions.....</b>                      | <b>19</b> |
+| B.1 General.....                                                      | 19        |
+| B.1.1 Parameter values .....                                          | 19        |
+| B.1.2 Time assistance .....                                           | 19        |
+| B.1.3 GANSS reference time.....                                       | 19        |
+| B.1.4 Reference and UE locations .....                                | 20        |
+| B.1.5 Satellite constellation and assistance data.....                | 20        |
+| B.1.6 Atmospheric delay.....                                          | 20        |
+| B.1.7 Sensors .....                                                   | 20        |
+| B.1.8 Information elements.....                                       | 20        |
+| B.1.9 GNSS signals.....                                               | 20        |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message .....          | 20        |
+| B.1.11 GNSS system time offsets.....                                  | 21        |
+
+|                             |                                                                                |           |
+|-----------------------------|--------------------------------------------------------------------------------|-----------|
+| <b>Annex C (normative):</b> | <b>Propagation conditions .....</b>                                            | <b>22</b> |
+| C.1                         | Static propagation conditions.....                                             | 22        |
+| C.2                         | Multi-path case.....                                                           | 22        |
+| <b>Annex D (normative):</b> | <b>Measurement sequence chart.....</b>                                         | <b>24</b> |
+| D.1                         | General .....                                                                  | 24        |
+| D.2                         | TTFF measurement sequence chart .....                                          | 24        |
+| D.3                         | Periodic update measurement sequence chart.....                                | 25        |
+| <b>Annex E (normative):</b> | <b>Assistance data required for testing .....</b>                              | <b>27</b> |
+| E.1                         | Introduction .....                                                             | 27        |
+| E.2                         | GPS assistance data.....                                                       | 27        |
+| E.3                         | GANSS assistance data .....                                                    | 27        |
+| <b>Annex F (normative):</b> | <b>Converting UE-assisted measurement reports into position estimates ....</b> | <b>31</b> |
+| F.1                         | Introduction .....                                                             | 31        |
+| F.2                         | UE measurement reports.....                                                    | 31        |
+| F.3                         | Weighted Least Squares (WLS) position solution .....                           | 32        |
+| Annex G (informative):      | Change history.....                                                            | 35        |
+
+# --- Foreword
+
+This Technical Specification 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 establishes the minimum performance requirements for A-GANSS for FDD mode of UTRA for the User Equipment (UE) that supports A-GANSS. It includes the minimum performance requirements for both UE-based and UE-assisted A-GANSS. The minimum performance requirements also include combinations of A-GPS and A-GANSS.
+
+# --- 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 TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [3] IS-GPS-200, Revision D, "Navstar GPS Space Segment/Navigation User Interfaces", March 7<sup>th</sup>, 2006.
+- [4] IS-GPS-705, "Navstar GPS Space Segment/User Segment L5 Interfaces", September 22, 2005.
+- [5] IS-GPS-800, "Navstar GPS Space Segment/User Segment L1C Interfaces", September 4, 2008.
+- [6] IS-QZSS, "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS", Ver.1.1, July 31, 2009.
+- [7] "Galileo OS Signal in Space ICD (OS SIS ICD)", Draft 0, Galileo Joint Undertaking, May 23<sup>rd</sup>, 2006.
+- [8] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1, 2008.
+- [9] "Specification for the Wide Area Augmentation System (WAAS) ", US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
+- [10] 3GPP TS 25.171: "Requirements for support of Assisted Global Positioning System (A-GPS) Frequency Division Duplex (FDD)".
+- [11] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)".
+- [12] 3GPP TS 34.172: "Terminal Conformance Specification, Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) (FDD)".
+- [13] 3GPP TS 34.109: "Special conformance testing functions".
+- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [15] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [16] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996.
+
+- [17] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119.
+- [18] 3GPP TS 25.215: "Physical layer; Measurements (FDD)".
+- [19] BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I(Version 1.0), China Satellite Navigation Office, December 2012.
+
+# 3 Definitions, symbols, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.101 [1], 3GPP TS 25.104 [2] and the following apply:
+
+**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbol applies:
+
+|                                 |                                                                                                                            |
+|---------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| B1I                             | BeiDou B1I navigation signal with carrier frequency of 1561.098 MHz.                                                       |
+| $c$                             | Speed of light.                                                                                                            |
+| E1                              | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz.                                                       |
+| E5                              | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz.                                                       |
+| E6                              | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz.                                                       |
+| G1                              | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . |
+| G2                              | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . |
+| $k$                             | GLONASS channel number, $k = -7 \dots 13$ .                                                                                |
+| L1 C/A                          | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz.              |
+| L1C                             | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz.                                             |
+| L2C                             | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz.                                             |
+| L5                              | GPS or QZSS L5 navigation signal with carrier frequency of 1176.450 MHz.                                                   |
+| <b>G</b>                        | Geometry Matrix.                                                                                                           |
+| $\rho_{\text{GNSS}_m, i}$       | Measured pseudo-range of satellite $i$ of $\text{GNSS}_m$ .                                                                |
+| <b>W</b>                        | Weighting Matrix.                                                                                                          |
+| $\mathbf{1}_{\text{GNSS}_m, i}$ | Line of sight unit vector from the user to the satellite $i$ of $\text{GNSS}_m$ .                                          |
+| $x$                             | State vector of user position and clock bias.                                                                              |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                                                              |
+|---------|----------------------------------------------------------------------------------------------|
+| A-GANSS | Assisted-Galileo and Additional Navigation Satellite Systems                                 |
+| A-GNSS  | Assisted-GNSS                                                                                |
+| A-GPS   | Assisted-Global Positioning System                                                           |
+| AWGN    | Additive White Gaussian Noise                                                                |
+| BDS     | BeiDou Navigation Satellite System                                                           |
+| C/A     | Coarse/Acquisition                                                                           |
+| DUT     | Device Under Test                                                                            |
+| ECEF    | Earth-Centered, Earth-Fixed                                                                  |
+| ECI     | Earth-Centered-Inertial                                                                      |
+| FDD     | Frequency Division Duplex                                                                    |
+| GEO     | Geostationary Earth Orbit                                                                    |
+| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) |
+
+|        |                                            |
+|--------|--------------------------------------------|
+| GNSS   | Global Navigation Satellite System         |
+| GPS    | Global Positioning System                  |
+| GSS    | GNSS System Simulator                      |
+| HDOP   | Horizontal Dilution Of Precision           |
+| ICD    | Interface Control Document                 |
+| IGSO   | Inclined Geosynchronous Satellite Orbit    |
+| IS     | Interface Specification                    |
+| LOS    | Line Of Sight                              |
+| MEO    | Medium Earth Orbit                         |
+| QZS    | Quasi-Zenith Satellite                     |
+| QZSS   | Quasi-Zenith Satellite System              |
+| RF     | Radio Frequency                            |
+| RRC    | Radio Resource Control                     |
+| SBAS   | Space Based Augmentation System            |
+| SFN    | System Frame Number                        |
+| SS     | FDD System Simulator                       |
+| SV     | Space Vehicle                              |
+| TBD    | To Be Determined                           |
+| TOD    | Time Of Day                                |
+| TOW    | Time Of Week                               |
+| TTFF   | Time To First Fix                          |
+| UE     | User Equipment                             |
+| UTRA   | Universal Terrestrial Radio Access         |
+| UTRAN  | Universal Terrestrial Radio Access Network |
+| WLS    | Weighted Least Squares                     |
+| WGS-84 | World Geodetic System 1984                 |
+
+## 3.4 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.172 [12] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETR 273-1-2 [15], subclause 6.5.
+
+# --- 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for both UE-based and UE-assisted FDD A-GNSS terminals. The minimum performance requirements also include combinations of A-GPS and A-GNSS.
+
+## 4.2 Measurement parameters
+
+### 4.2.1 UE-based A-GNSS measurement parameters
+
+In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
+
+### 4.2.2 UE-assisted A-GNSS measurement parameters
+
+In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GNSS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code measurements, as specified in 3GPP TS 25.215 [18]. The UE GNSS code measurements that may be combined with UE GPS code phase measurements as specified in 3GPP TS 25.215 [18] are converted into a horizontal position estimate using the procedure detailed in Annex F.
+
+## 4.3 Response time
+
+Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GANSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GANSS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GANSS and GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [13] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10.
+
+## 4.4 Time assistance
+
+Time assistance is the provision of GANSS reference time to the UE from the network via RRC messages. Currently two different GANSS time assistance methods can be provided by the network.
+
+- a) Coarse time assistance is always provided by the network and provides current GANSS time to the UE. The time provided is within  $\pm 2$  seconds of GANSS system time. It is signalled to the UE by means of the GANSS Day and GANSS TOD fields in the GANSS Reference Time assistance data IE.
+- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GANSS system time and the current UTRAN time. The accuracy of this relationship is  $\pm 10 \mu\text{s}$  of the actual relationship. This addresses the case when the network can provide an improved GANSS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GANSS timing of cell frames fields in the GANSS Reference Time assistance data IE.
+
+The specific GANSS system time is identified through the GANSS Time ID field of the GANSS Reference Time IE. In case where several GANSS are used in the tests, only one GANSS Time ID is used to determine the Time of Day. For all the constellations, the GANSS Time Model assistance and UTC Model assistance shall be available at the system simulator, as specified in Annex E.
+
+The time of applicability of time assistance is the beginning of the System Frame of the message containing the GANSS Reference time.
+
+### 4.4.1 Use of fine time assistance
+
+The use of fine time assistance to improve the GANSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2.
+
+## 4.5 RRC states
+
+The minimum A-GANSS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in Annex B.
+
+## 4.6 2D position error
+
+The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered.
+
+## 4.7 User equipment supporting multiple constellations
+
+Minimum performance requirements are defined for each global GANSS constellation (Galileo, Modernized GPS, GLONASS and BDS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated.
+
+NOTE: For test cases where signals from "GPS" and "Modernized GPS" are included, "GPS" and "Modernized GPS" are considered as a single constellation, unless otherwise specified.
+
+## 4.8 User equipment supporting multiple signals
+
+For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 5 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5 plus the relative power level defined in Table 4.8-1.
+
+**Table 4.8-1: Relative signal power levels for each signal type for each GNSS**
+
+|                                                        | Galileo |       | GPS/Modernized GPS |         | GLONASS |       | QZSS   |         | SBAS |      | BDS |    |       |
+|--------------------------------------------------------|---------|-------|--------------------|---------|---------|-------|--------|---------|------|------|-----|----|-------|
+|                                                        | E1      | 0 dB  | L1 C/A             | 0 dB    | G1      | 0 dB  | L1 C/A | 0 dB    | L1   | 0 dB | B1I | D1 | 0 dB  |
+| Signal power levels relative to reference power levels | E6      | +2 dB | L1C                | +1.5 dB | G2      | -6 dB | L1C    | +1.5 dB |      |      |     | D2 | +5 dB |
+|                                                        | E5      | +2 dB | L2C                | -1.5 dB |         |       | L2C    | -1.5 dB |      |      |     |    |       |
+|                                                        |         |       | L5                 | +3.6 dB |         |       | L5     | +3.6 dB |      |      |     |    |       |
+
+NOTE 1: For test cases which involve "Modernized GPS", the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports "GPS" in addition to "Modernized GPS".
+
+NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately.
+
+NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type.
+
+# 5 A-GNSS minimum performance requirements
+
+The A-GNSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GANSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E.
+
+The requirements in CELL\_PCH and URA\_PCH states are for further study.
+
+## 5.1 Sensitivity
+
+A sensitivity requirement is essential for verifying the performance of A-GNSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.
+
+### 5.1.1 Coarse time assistance
+
+In this test case 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.1-1: Test parameters**
+
+| <b>System</b>      | <b>Parameters</b>                         | <b>Unit</b> | <b>Value</b>      |
+|--------------------|-------------------------------------------|-------------|-------------------|
+|                    | Number of generated satellites per system | -           | See Table 5.1.1-2 |
+|                    | Total number of generated satellites      | -           | 6                 |
+|                    | HDOP range                                |             | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -           | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds     | ±2                |
+| Galileo            | Reference high signal power level         | dBm         | -142              |
+|                    | Reference low signal power level          | dBm         | -147              |
+| GPS <sup>(1)</sup> | Reference high signal power level         | dBm         | -142              |
+|                    | Reference low signal power level          | dBm         | -147              |
+| GLONASS            | Reference high signal power level         | dBm         | -142              |
+|                    | Reference low signal power level          | dBm         | -147              |
+| BDS                | Reference high signal power level         | dBm         | -136              |
+|                    | Reference low signal power level          | dBm         | -145              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.1-2: Power level and satellite allocation**
+
+|                      |                   | <b>Satellite allocation for each constellation</b> |               |               |
+|----------------------|-------------------|----------------------------------------------------|---------------|---------------|
+|                      |                   | <b>GNSS-1<sup>(1)</sup></b>                        | <b>GNSS-2</b> | <b>GNSS-3</b> |
+| Single constellation | High signal level | 1                                                  | -             | -             |
+|                      | Low signal level  | 5                                                  | -             | -             |
+| Dual constellation   | High signal level | 1                                                  | -             | -             |
+|                      | Low signal level  | 2                                                  | 3             | -             |
+| Triple constellation | High signal level | 1                                                  | -             | -             |
+|                      | Low signal level  | 1                                                  | 2             | 2             |
+
+Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.
+
+#### 5.1.1.1 Minimum requirements (coarse time assistance)
+
+The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1.
+
+**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)**
+
+| <b>System</b> | <b>Success rate</b> | <b>2-D position error</b> | <b>Max response time</b> |
+|---------------|---------------------|---------------------------|--------------------------|
+| All           | 95 %                | 100 m                     | 20 s                     |
+
+### 5.1.2 Fine time assistance
+
+This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.2-1: Test parameters**
+
+| System             | Parameters                                | Unit    | Value             |
+|--------------------|-------------------------------------------|---------|-------------------|
+|                    | Number of generated satellites per system | -       | See Table 5.1.2-2 |
+|                    | Total number of generated satellites      | -       | 6                 |
+|                    | HDOP range                                |         | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -       | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds | ±2                |
+|                    | GANSS fine time assistance error range    | µs      | ±10               |
+| Galileo            | Reference signal power level              | dBm     | -147              |
+| GPS <sup>(1)</sup> | Reference signal power level              | dBm     | -147              |
+| GLONASS            | Reference signal power level              | dBm     | -147              |
+| BDS                | Reference signal power level              | dBm     | -147              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.2-2: Satellite allocation**
+
+|                      | Satellite allocation for each constellation |        |        |
+|----------------------|---------------------------------------------|--------|--------|
+|                      | GNSS-1                                      | GNSS-2 | GNSS-3 |
+| Single constellation | 6                                           | -      | -      |
+| Dual constellation   | 3                                           | 3      | -      |
+| Triple constellation | 2                                           | 2      | 2      |
+
+#### 5.1.2.1 Minimum requirements (fine time assistance)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1.
+
+**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.2 Nominal accuracy
+
+Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2.
+
+**Table 5.2-1: Test parameters**
+
+| System             | Parameters                                      | Unit    | Value                 |
+|--------------------|-------------------------------------------------|---------|-----------------------|
+|                    | Number of generated satellites per system       | -       | See Table 5.2-2       |
+|                    | Total number of generated satellites            | -       | 6 or 7 <sup>(2)</sup> |
+|                    | HDOP Range                                      | -       | 1.4 to 2.1            |
+|                    | Propagation conditions                          | -       | AWGN                  |
+|                    | GANSS coarse time assistance error range        | seconds | ±2                    |
+| GPS <sup>(1)</sup> | Reference signal power level for all satellites | dBm     | -128.5                |
+| Galileo            | Reference signal power level for all satellites | dBm     | -127                  |
+| GLONASS            | Reference signal power level for all satellites | dBm     | -131                  |
+| QZSS               | Reference signal power level for all satellites | dBm     | -128.5                |
+| SBAS               | Reference signal power level for all satellites | dBm     | -131                  |
+| BDS                | Reference signal power level for all satellites | dBm     | -133                  |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.  
+Note 2: 7 satellites apply only for SBAS case.
+
+If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
+
+If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
+
+**Table 5.2-2: Satellite allocation**
+
+|                                                                            | Satellite allocation for each constellation |                       |                       |      |
+|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|------|
+|                                                                            | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> | SBAS |
+| Single constellation                                                       | 6                                           | --                    | --                    | 1    |
+| Dual constellation                                                         | 3                                           | 3                     | --                    | 1    |
+| Triple constellation                                                       | 2                                           | 2                     | 2                     | 1    |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                                             |                       |                       |      |
+
+### 5.2.1 Minimum requirements (nominal accuracy)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1.
+
+**Table 5.2.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 15 m               | 20 s              |
+
+## 5.3 Dynamic range
+
+The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used.
+
+**Table 5.3-1: Test parameters**
+
+| System                                                                                      | Parameters                                | Unit    | Value           |
+|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------|
+|                                                                                             | Number of generated satellites per system | -       | See Table 5.3-2 |
+|                                                                                             | Total number of generated satellites      | -       | 6               |
+|                                                                                             | HDOP Range                                | -       | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                    | -       | AWGN            |
+|                                                                                             | GANSS coarse time assistance error range  | seconds | ±2              |
+| Galileo                                                                                     | Reference high signal power level         | dBm     | -127.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| GPS <sup>(1)</sup>                                                                          | Reference high signal power level         | dBm     | -129            |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| GLONASS                                                                                     | Reference high signal power level         | dBm     | -131.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| BDS                                                                                         | Reference high signal power level         | dBm     | -133.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -145            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                           |         |                 |
+
+**Table 5.3-2: Power level and satellite allocation**
+
+|                                                                            |                   | Satellite allocation for each constellation |                       |                       |
+|----------------------------------------------------------------------------|-------------------|---------------------------------------------|-----------------------|-----------------------|
+|                                                                            |                   | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> |
+| Single constellation                                                       | High signal level | 2                                           | --                    | --                    |
+|                                                                            | Low signal level  | 4                                           | --                    | --                    |
+| Dual constellation                                                         | High signal level | 1                                           | 1                     | --                    |
+|                                                                            | Low signal level  | 2                                           | 2                     | --                    |
+| Triple constellation                                                       | High signal level | 1                                           | 1                     | 1                     |
+|                                                                            | Low signal level  | 1                                           | 1                     | 1                     |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                   |                                             |                       |                       |
+
+### 5.3.1 Minimum requirements (dynamic range)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1.
+
+**Table 5.3.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.4 Multi-path scenario
+
+The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.
+
+In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal.
+
+**Table 5.4-1: Test parameter**
+
+| System                                                                                      | Parameters                                | Unit    | Value           |
+|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------|
+|                                                                                             | Number of generated satellites per system | -       | See Table 5.4-2 |
+|                                                                                             | Total number of generated satellites      | -       | 6               |
+|                                                                                             | HDOP range                                |         | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                    | -       | AWGN            |
+|                                                                                             | GNSS coarse time assistance error range   | seconds | ±2              |
+| Galileo                                                                                     | Reference signal power level              | dBm     | -127            |
+| GPS <sup>(1)</sup>                                                                          | Reference signal power level              | dBm     | -128.5          |
+| GLONASS                                                                                     | Reference signal power level              | dBm     | -131            |
+| BDS                                                                                         | Reference signal power level              | dBm     | -133            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                           |         |                 |
+
+**Table 5.4-2: Channel model allocation**
+
+|                      |                 | Channel model allocation for each constellation |        |        |
+|----------------------|-----------------|-------------------------------------------------|--------|--------|
+|                      |                 | GNSS-1                                          | GNSS-2 | GNSS-3 |
+| Single constellation | One-tap channel | 2                                               | --     | --     |
+|                      | Two-tap channel | 4                                               | --     | --     |
+| Dual constellation   | One-tap channel | 1                                               | 1      | --     |
+|                      | Two-tap channel | 2                                               | 2      | --     |
+| Triple constellation | One-tap channel | 1                                               | 1      | 1      |
+|                      | Two-tap channel | 1                                               | 1      | 1      |
+
+### 5.4.1 Minimum requirements (multi-path scenario)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1.
+
+**Table 5.4.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.5 Moving scenario and periodic update
+
+The purpose of the test case is to verify the receiver's capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.
+
+In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.
+
+The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
+
+**Table 5.5-1: Trajectory Parameters**
+
+| Parameter                        | Distance (m) | Speed (km/h)            |
+|----------------------------------|--------------|-------------------------|
+| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20           | 25                      |
+| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250          | 25 to 100 and 100 to 25 |
+| $l_{13}$                         | 400          | 100                     |
+| $l_{23}$                         | 900          | 100                     |
+
+![Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the left side and l21, l22, l23, l24, l25 on the right side. Arrows indicate the direction of movement: clockwise from the top-left corner.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg)
+
+Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the left side and l21, l22, l23, l24, l25 on the right side. Arrows indicate the direction of movement: clockwise from the top-left corner.
+
+**Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case**
+
+**Table 5.5-2: Test Parameters**
+
+| <b>System</b>                                                                               | <b>Parameters</b>                               | <b>Unit</b> | <b>Value</b>    |
+|---------------------------------------------------------------------------------------------|-------------------------------------------------|-------------|-----------------|
+|                                                                                             | Number of generated satellites per system       | -           | See Table 5.5-3 |
+|                                                                                             | Total number of generated satellites            | -           | 6               |
+|                                                                                             | HDOP Range per system                           | -           | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                          | -           | AWGN            |
+|                                                                                             | GANSS coarse time assistance error range        | seconds     | ±2              |
+| Galileo                                                                                     | Reference signal power level for all satellites | dBm         | -127            |
+| GPS <sup>(1)</sup>                                                                          | Reference signal power level for all satellites | dBm         | -128.5          |
+| GLONASS                                                                                     | Reference signal power level for all satellites | dBm         | -131            |
+| BDS                                                                                         | Reference signal power level for all satellites | dBm         | -133            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                                 |             |                 |
+
+**Table 5.5-3: Satellite allocation**
+
+|                                                                            | <b>Satellite allocation for each constellation</b> |                             |                             |
+|----------------------------------------------------------------------------|----------------------------------------------------|-----------------------------|-----------------------------|
+|                                                                            | <b>GNSS 1<sup>(1)</sup></b>                        | <b>GNSS 2<sup>(1)</sup></b> | <b>GNSS 3<sup>(1)</sup></b> |
+| Single constellation                                                       | 6                                                  | --                          | --                          |
+| Dual constellation                                                         | 3                                                  | 3                           | --                          |
+| Triple constellation                                                       | 2                                                  | 2                           | 2                           |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                                                    |                             |                             |
+
+### 5.5.1 Minimum requirements (moving scenario and periodic update)
+
+The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates.
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS/GANSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 5.5.1-1.
+
+**Table 5.5.1-1: Minimum requirements**
+
+| <b>System</b> | <b>Success rate</b> | <b>2-D position error</b> | <b>Periodical reporting interval</b> |
+|---------------|---------------------|---------------------------|--------------------------------------|
+| All           | 95 %                | 50 m                      | 2 s                                  |
+
+# --- Annex A (normative): Test cases
+
+## A.1 Conformance tests
+
+The conformance tests are specified in 3GPP TS 34.172 [12]. Statistical interpretation of the requirements is described in clause A.2.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 34.172 [12].
+
+# Annex B (normative): Test conditions
+
+## B.1 General
+
+This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated.
+
+### B.1.1 Parameter values
+
+Additionally, amongst all the listed parameters (see Annex E), the following values for some important parameters are to be used in the measurement control message.
+
+**Table B.1.1-1: Parameter values**
+
+| Information element        | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests |
+|----------------------------|---------------------------------------------------|--------------------------------------------|------------------------|
+| Measurement Reporting Mode | Periodical reporting                              | Periodical reporting                       | Periodical reporting   |
+| Amount of reporting        | 1                                                 | 1                                          | Infinite (see Note)    |
+| Reporting interval         | 20 000 ms                                         | 20 000 ms                                  | 2 000 ms               |
+| Horizontal accuracy        | 51.2 m                                            | 7.7 m                                      | 24.5 m                 |
+| Vertical accuracy          | 102 m                                             | 102 m                                      | 102 m                  |
+| Note:                      | Infinite means during the complete test time.     |                                            |                        |
+
+In the Sensitivity test case with Fine Time Assistance, the following parameter values are used.
+
+**Table B.1.1-2: Parameters for fine time assistance test**
+
+| Information element                           | Value   |
+|-----------------------------------------------|---------|
+| TUTRAN-GPS drift rate                         | 0       |
+| TUTRAN-GNSS drift rate                        | 0       |
+| UE Positioning GPS Reference Time Uncertainty | 10.2 µs |
+| GNSS TOD Uncertainty                          | 10.2 µs |
+
+### B.1.2 Time assistance
+
+For every Test Instance in each TTFF test case, the GNSS/GPS Reference Time shall have a random offset, relative to GNSS/GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS/GNSS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+For the Moving Scenario and Periodic Update Test Case the GNSS/GPS Reference Time shall be set to the nominal value.
+
+### B.1.3 GNSS reference time
+
+For every Test Instance in each TTFF test case, the GNSS reference time (and GPS reference time, if applicable) shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix.
+
+### B.1.4 Reference and UE locations
+
+There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km.
+
+The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %.
+
+For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions.
+
+For test cases which include satellites from regional systems, such as QZSS and SBAS, the reference location shall be selected within the defined coverage area of the systems.
+
+### B.1.5 Satellite constellation and assistance data
+
+The satellite constellation shall consist of 24 satellites for GLONASS; 27 satellites for GPS, Modernized GPS and Galileo; 3 satellites for QZSS; 2 satellites for SBAS and 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo, GLONASS and BDS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites (or 7 if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for GPS, Modernized GPS, Galileo, GLONASS and BDS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO.
+
+NOTE: Currently up to 30 BDS satellites (maximum 22 MEO) can be supported.
+
+### B.1.6 Atmospheric delay
+
+Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs.
+
+### B.1.7 Sensors
+
+The minimum performance requirements shall be met without the use of any data coming from sensors that can aid the positioning.
+
+### B.1.8 Information elements
+
+The information elements that are available to the UE in all the test cases are listed in Annex E.
+
+### B.1.9 GNSS signals
+
+The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
+
+### B.1.10 RESET UE POSITIONING STORED INFORMATION Message
+
+In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [13] clause 5.4 shall be used.
+
+When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS* it shall:
+
+- discard any internally stored GPS and GANSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler);
+- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition;
+
+- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information.
+
+### B.1.11 GNSS system time offsets
+
+If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns.
+
+# Annex C (normative): Propagation conditions
+
+## C.1 Static propagation conditions
+
+The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
+
+## C.2 Multi-path case
+
+Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GANSS signals are defined in table C.2-1.
+
+**Table C.2-1: Multipath case**
+
+| Initial Relative Delay [m]                             | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] |
+|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------|
+| 0                                                      | $F_d$                                 | $F_d / N$                          | 0                        |
+| X                                                      | $F_d - 0.1$                           | $(F_d - 0.1) / N$                  | Y                        |
+| Note: Discrete Doppler frequency is used for each tap. |                                       |                                    |                          |
+
+Where the X and Y depends on the GNSS signal type and is shown in table C.2-2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in table C.2-3 (where k in table C.2-3 is the GLONASS frequency channel number).
+
+**Table C.2-2: Relative Delay and Attenuation of Non Line of Sight Signals**
+
+| System             | Signals | X [m] | Y [dB] |
+|--------------------|---------|-------|--------|
+| Galileo            | E1      | 125   | -4.5   |
+|                    | E5a     | 15    | -6     |
+|                    | E5b     | 15    | -6     |
+| GPS/Modernized GPS | L1 C/A  | 150   | -6     |
+|                    | L1C     | 125   | -4.5   |
+|                    | L2C     | 150   | -6     |
+|                    | L5      | 15    | -6     |
+| GLONASS            | G1      | 275   | -12.5  |
+|                    | G2      | 275   | -12.5  |
+| BDS                | B1I     | 75    | -4.5   |
+
+**Table C.2-3: Ratio between the transmitted carrier frequency of the signals and the transmitted chip rate**
+
+| System             | Signals | N                        |
+|--------------------|---------|--------------------------|
+| Galileo            | E1      | 1540                     |
+|                    | E5a     | 115                      |
+|                    | E5b     | 118                      |
+| GPS/Modernized GPS | L1 C/A  | 1540                     |
+|                    | L1C     | 1540                     |
+|                    | L2C     | 1200                     |
+|                    | L5      | 115                      |
+| GLONASS            | G1      | $3135.03 + k \cdot 1.10$ |
+|                    | G2      | $2438.36 + k \cdot 0.86$ |
+| BDS                | B1I     | 763                      |
+
+The initial carrier phase difference between taps shall be randomly selected between 0 and  $2\pi$ . The initial value shall have uniform random distribution.
+
+# Annex D (normative): Measurement sequence chart
+
+## D.1 General
+
+The measurement Sequence Charts that are required in all the test cases, are defined in this clause.
+
+## D.2 TTFF measurement sequence chart
+
+The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (indicated by a dashed line); (f) UE sends 'RRC Measurement Report' to SS.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SS
+    participant UE
+    Note left of SS: (a)
+    SS->>UE: Reset UE Positioning Stored Information
+    Note left of SS: (b)
+    SS->>UE: RRC Measurement Control (Setup)
+    Note left of UE: (c)
+    UE->>SS: RRC Measurement Report (Assistance Data Request)
+    Note left of SS: (d)
+    SS->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (e)
+    SS-->>UE: RRC Measurement Control (Modify)
+    Note left of UE: (f)
+    UE->>SS: RRC Measurement Report
+  
+```
+
+Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (indicated by a dashed line); (f) UE sends 'RRC Measurement Report' to SS.
+
+Figure D.2-1: Measurement Sequence Chart for the TTFF Test Cases
+
+- The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+- The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                          |                                                                        |
+|------------------------------------------|------------------------------------------------------------------------|
+| <i>MEASUREMENT COMMAND</i>               | Setup                                                                  |
+| <i>CHOICE MEASUREMENT TYPE</i>           | UE positioning measurement                                             |
+| <i>UE POSITIONING REPORTING QUANTITY</i> |                                                                        |
+| >Method Type                             | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                     | set to 'GPS';                                                          |
+| >Horizontal Accuracy                     | as defined in Annex B;                                                 |
+| >Vertical Accuracy                       | as defined in Annex B;                                                 |
+| >Additional Assistance Data Request      | TRUE                                                                   |
+| >GANSS Positioning Methods               | set according to the UE capabilities and test case;                    |
+| <i>MEASUREMENT VALIDITY</i>              |                                                                        |
+| >UE state                                | All states                                                             |
+| <i>CHOICE REPORTING CRITERIA</i>         | Periodical reporting criteria                                          |
+| >Amount of reporting                     | 1 (see Annex B);                                                       |
+| >Reporting interval                      | 20 seconds (see Annex B);                                              |
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GANSS assistance data.
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GANSS MEASURED RESULTS* present in case of UE-assisted GANSS.
+
+Steps (a) to (f) are repeated for each test instance.
+
+## D.3 Periodic update measurement sequence chart
+
+The measurement sequence chart for the Moving Scenario and Periodic Update test case, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the interaction between System Simulator (SS) and User Equipment (UE) for a periodic update measurement test case. The sequence starts with (a) SS sending 'Reset UE Positioning Stored Information' to UE. (b) SS sends 'RRC Measurement Control (Setup)' to UE. (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS. (d) SS sends 'RRC Measurement Control (Modify)' to UE. (e) SS sends another 'RRC Measurement Control (Modify)' to UE via a dashed line. (f) UE sends 'RRC Measurement Report' to SS. (g) UE sends another 'RRC Measurement Report' to SS. (h) UE sends another 'RRC Measurement Report' to SS, followed by vertical ellipsis. (i) UE sends the final 'RRC Measurement Report' to SS.](86b4670fc1a5a694821ee92b99c1209a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SS
+    participant UE
+    Note left of SS: (a)
+    SS->>UE: Reset UE Positioning Stored Information
+    Note left of SS: (b)
+    SS->>UE: RRC Measurement Control (Setup)
+    Note left of UE: (c)
+    UE->>SS: RRC Measurement Report (Assistance Data Request)
+    Note left of SS: (d)
+    SS->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (e)
+    SS-->>UE: RRC Measurement Control (Modify)
+    Note left of UE: (f)
+    UE->>SS: RRC Measurement Report
+    Note left of UE: (g)
+    UE->>SS: RRC Measurement Report
+    Note left of UE: (h)
+    UE->>SS: RRC Measurement Report
+    Note left of UE: ...
+    Note left of UE: (i)
+    UE->>SS: RRC Measurement Report
+  
+```
+
+Sequence diagram showing the interaction between System Simulator (SS) and User Equipment (UE) for a periodic update measurement test case. The sequence starts with (a) SS sending 'Reset UE Positioning Stored Information' to UE. (b) SS sends 'RRC Measurement Control (Setup)' to UE. (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS. (d) SS sends 'RRC Measurement Control (Modify)' to UE. (e) SS sends another 'RRC Measurement Control (Modify)' to UE via a dashed line. (f) UE sends 'RRC Measurement Report' to SS. (g) UE sends another 'RRC Measurement Report' to SS. (h) UE sends another 'RRC Measurement Report' to SS, followed by vertical ellipsis. (i) UE sends the final 'RRC Measurement Report' to SS.
+
+**Figure D.3-1: Measurement Sequence Chart for the Moving Scenario and Periodic Update Test Case**
+
+- (a) The system simulator sends a RESET *UE POSITIONING STORED INFORMATION* message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                |                            |
+|--------------------------------|----------------------------|
+| <i>MEASUREMENT COMMAND</i>     | Setup                      |
+| <i>CHOICE MEASUREMENT TYPE</i> | UE positioning measurement |
+
+# UE POSITIONING REPORTING QUANTITY
+
+|                                     |                                                                        |
+|-------------------------------------|------------------------------------------------------------------------|
+| >Method Type                        | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                | set to 'GPS';                                                          |
+| >Horizontal Accuracy                | as defined in Annex B;                                                 |
+| >Vertical Accuracy                  | as defined in Annex B;                                                 |
+| >Additional Assistance Data Request | TRUE                                                                   |
+| >GNSS Positioning Methods           | set according to the UE capabilities and test case;                    |
+| MEASUREMENT VALIDITY                |                                                                        |
+| >UE state                           | All states                                                             |
+| CHOICE REPORTING CRITERIA           | Periodical reporting criteria                                          |
+| >Amount of reporting                | infinite (see Annex B);                                                |
+| >Reporting interval                 | 2 seconds (see Annex B);                                               |
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GNSS assistance data.
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GNSS MEASURED RESULTS* present in case of UE-assisted GNSS.
+- (g) – (i) The UE continues to provide RRC MEASUREMENT REPORT messages as in step (g) until the moving trajectory has been completed.
+
+NOTE: The UE may report error messages at step (f) until it has been able to acquire GNSS signals.
+
+# Annex E (normative): Assistance data required for testing
+
+## E.1 Introduction
+
+This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5.
+
+The information elements are given with reference to 3GPP TS 25.331 [14], where the details are defined.
+
+## E.2 GPS assistance data
+
+The GPS L1 C/A assistance data are as defined in 3GPP TS 25.171 [10], Annex E.
+
+## E.3 GANSS assistance data
+
+- a) **UE Positioning GANSS Reference Time IE.** This information element is defined in subclause 10.3.7.96o of 3GPP TS 25.331 [14].
+
+**Table E.3-1: GANSS reference time IE**
+
+| Name of the IE                      | Fields of the IE                   | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test |
+|-------------------------------------|------------------------------------|---------------------------------------------------|---------------------------------------|
+| UE Positioning GANSS Reference Time |                                    |                                                   |                                       |
+|                                     | GANSS Day                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD Uncertainty              | Yes                                               | Yes                                   |
+|                                     | GANSS Time ID                      | Yes                                               | Yes                                   |
+|                                     | UTRAN GANSS Reference Time         |                                                   |                                       |
+|                                     | >UTRAN GANSS Timing of Cell Frames |                                                   | Yes                                   |
+|                                     | >CHOICE mode                       |                                                   | Yes                                   |
+|                                     | >>FDD                              |                                                   | Yes                                   |
+|                                     | >>>Primary CPICH Info              |                                                   | Yes                                   |
+|                                     | >SFN                               |                                                   | Yes                                   |
+|                                     | TUTRAN-GANSS Drift Rate            |                                                   | Yes                                   |
+
+- b) **UE Positioning GANSS Reference UE Position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [14].
+
+**Table E.3-2: GANSS reference location IE**
+
+| Name of the IE                             | Fields of the IE                                        |
+|--------------------------------------------|---------------------------------------------------------|
+| UE Positioning GANSS Reference UE Position | Ellipsoid point with Altitude and uncertainty ellipsoid |
+
+- c) **UE Positioning GANSS Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92a of 3GPP TS 25.331 [14].
+
+**Table E.3-3: GANSS ionospheric model IE**
+
+| Name of the IE                         | Fields of the IE |
+|----------------------------------------|------------------|
+| UE Positioning GANSS Ionospheric Model |                  |
+
+- d) **UE Positioning GANSS Additional Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92b of 3GPP TS 25.331 [14].
+
+**Table E.3-4: GANSS additional ionospheric model IE**
+
+| Name of the IE                                       | Fields of the IE |
+|------------------------------------------------------|------------------|
+| UE Positioning GANSS<br>Additional Ionospheric Model |                  |
+
+- e) **UE Positioning GANSS Time Model IE.** This information element is only required for multi system tests, and is defined in subclause 10.3.7.97a of 3GPP TS 25.331 [14].
+
+**Table E.3-5: GANSS time model IE**
+
+| Name of the IE                     | Fields of the IE                                   |
+|------------------------------------|----------------------------------------------------|
+| UE Positioning GANSS Time<br>Model |                                                    |
+|                                    | GNSS TOD_ID<br>For each GNSS included in the test. |
+
+- f) **UE Positioning GANSS Navigation Model IE.** This information element is defined in subclause 10.3.7.94a of 3GPP TS 25.331 [14].
+
+**Table E.3-6: GANSS navigation model IE**
+
+| Name of the IE                           | Fields of the IE |
+|------------------------------------------|------------------|
+| UE Positioning GANSS<br>Navigation Model |                  |
+
+- g) **UE Positioning GANSS Additional Navigation Models IE.** This information element is defined in subclause 10.3.7.94b of 3GPP TS 25.331 [14].
+
+**Table E.3-7: GANSS navigation model IE**
+
+| Name of the IE                           | Fields of the IE |
+|------------------------------------------|------------------|
+| UE Positioning GANSS<br>Navigation Model |                  |
+
+**Table E.3-8: GANSS clock and orbit model choices**
+
+| GANSS               | Clock and Orbit Model Choice |
+|---------------------|------------------------------|
+| Galileo             | Model-1                      |
+| Modernized GPS      | Model-3                      |
+| GLONASS             | Model-4                      |
+| QZSS QZS-L1         | Model-2                      |
+| QZSS QZS-L1C/L2C/L5 | Model-3                      |
+| SBAS                | Model-5                      |
+| BDS                 | Model-6                      |
+
+- h) **UE Positioning GANSS Reference Measurement Information IE.** This information element is defined in subclause 10.3.7.88b of 3GPP TS 25.331 [14].
+
+**Table E.3-9: GANSS reference measurement information IE**
+
+| Name of the IE                                         | Fields of the IE                     |
+|--------------------------------------------------------|--------------------------------------|
+| UE Positioning GANSS Reference Measurement Information |                                      |
+|                                                        | SatID                                |
+|                                                        | Doppler (0 <sup>th</sup> order term) |
+|                                                        | Doppler (1 <sup>st</sup> order term) |
+|                                                        | Doppler Uncertainty                  |
+|                                                        | Code Phase                           |
+|                                                        | Integer Code Phase                   |
+|                                                        | Code Phase Search Window             |
+|                                                        | Azimuth                              |
+|                                                        | Elevation                            |
+
+- i) **UE Positioning GANSS Almanac IE.** This information element is defined in subclause 10.3.7.89a of 3GPP TS 25.331 [14].
+
+**Table E.3-10: GANSS almanac model IE**
+
+| Name of the IE               | Fields of the IE |
+|------------------------------|------------------|
+| UE Positioning GANSS Almanac |                  |
+
+**Table E.3-11: GANSS almanac choices**
+
+| GANSS               | Almanac Model Choice |
+|---------------------|----------------------|
+| Galileo             | Model-1              |
+| Modernized GPS      | Model-3,4            |
+| GLONASS             | Model-5              |
+| QZSS QZS-L1         | Model-2              |
+| QZSS QZS-L1C/L2C/L5 | Model-3,4            |
+| SBAS                | Model-6              |
+| BDS                 | Model-7              |
+
+- j) **UE Positioning GANSS UTC Model IE.** This information element is defined in subclause 10.3.7.97c of 3GPP TS 25.331 [14].
+
+**Table E.3-12: GANSS UTC model IE**
+
+| Name of the IE                 | Fields of the IE |
+|--------------------------------|------------------|
+| UE Positioning GANSS UTC Model |                  |
+
+- k) **UE Positioning GANSS Additional UTC Models IE.** This information element is defined in subclause 10.3.7.97d of 3GPP TS 25.331 [14].
+
+**Table E.3-13: GANSS additional UTC model IE**
+
+| Name of the IE                                | Fields of the IE |
+|-----------------------------------------------|------------------|
+| UE Positioning GANSS Additional UTC Models IE |                  |
+
+**Table E.3-14: GANSS UTC model choices**
+
+| <b>GANSS</b>        | <b>UTC Model Choice</b>        |
+|---------------------|--------------------------------|
+| Galileo             | UE Positioning GANSS UTC Model |
+| Modernized GPS      | Model-1                        |
+| GLONASS             | Model-2                        |
+| QZSS QZS-L1         | UE Positioning GANSS UTC Model |
+| QZSS QZS-L1C/L2C/L5 | Model-1                        |
+| SBAS                | Model-3                        |
+| BDS                 | Model-4                        |
+
+- I) UE Positioning GANSS Auxiliary Information IE.** This information element is defined in subclause 10.3.7.97f of 3GPP TS 25.331 [14].
+
+**Table E.3-15: GANSS auxiliary information IE**
+
+| <b>Name of the IE</b>                         | <b>Fields of the IE</b> |
+|-----------------------------------------------|-------------------------|
+| UE Positioning GANSS Auxiliary Information IE |                         |
+
+# --- Annex F (normative):Converting UE-assisted measurement reports into position estimates
+
+## F.1 Introduction
+
+To convert the UE measurement reports in case of UE-assisted mode of A-GANSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [3], [4], [5], [6], [7], [8], [9], [16] and [17].
+
+## --- F.2 UE measurement reports
+
+In case of UE-assisted A-GANSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE (subclause 10.3.7.93a in 3GPP TS 25.331 [14]). In case the UE provides also measurements on the GPS L1 C/A signal, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [14]). The measurement parameters required for calculating the UE position are:
+
+- 1) Reference Time: The UE has two choices for the Reference Time:
+  - a) "UE GANSS Timing of Cell Frames" and/or "UE GPS Timing of Cell Frames";
+  - b) "GANSS TOD msec" and/or "GPS TOW msec" if GPS L1 C/A signal measurements are also provided.
+
+NOTE: It is not expected that an UE will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy.
+
+- 2) Measurement Parameters for each GANSS and GANSS Signal: 1 to <maxGANSSSat>:
+  - a) "Satellite ID"; mapping according to table 10.3.7.88b in 3GPP TS 25.331 [14];
+  - b) "GANSS Code Phase";
+  - c) "GANSS Integer Code Phase";
+  - d) "GANSS Integer Code Phase Extension";
+  - e) "Code Phase RMS Error";
+- 3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 1 to <maxSat>:
+  - a) "Satellite ID (SV PRN)";
+  - b) "Whole GPS chips";
+  - c) "Fractional GPS Chips";
+  - d) "Pseudorange RMS Error".
+
+Additional information required at the system simulator:
+
+- 1) "UE Positioning GANSS Reference UE Position" or "UE Positioning GPS Reference UE Position" (subclause 10.3.8.4c in 3GPP TS 25.331 [14]):  
+Used for initial approximate receiver coordinates.
+- 2) "UE Positioning GANSS Navigation Model" and "UE Positioning GANSS Additional Navigation Models" (subclauses 10.3.7.94a and 10.3.7.94b in 3GPP TS 25.331 [14]):
+
+Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections.
+
+- 3) "UE Positioning GANSS Ionospheric Model" (subclause 10.3.7.92a in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [7] for computation of the ionospheric delay.
+- 4) "UE Positioning GANSS Additional Ionospheric Model" (subclause 10.3.7.92b in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [6] for computation of the ionospheric delay.
+- 5) "UE Positioning GANSS Time Model" (subclause 10.3.7.97a in 3GPP TS 25.331 [14]):  
+Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "UE Positioning GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UE Positioning GPS UTC Model" (subclause 10.3.7.97 in 3GPP TS 25.331 [14]), "UE Positioning GANSS UTC Model" (subclause 10.3.7.97c in 3GPP TS 25.331 [14]), or "UE Positioning GANSS Additional UTC Models" (subclause 10.3.7.97d in 3GPP TS 25.331 [14]).
+- 6) "UE Positioning GPS Navigation Model" (subclause 10.3.7.94 in 3GPP TS 25.331 [14]):  
+Contains the GPS ephemeris and clock correction parameters as specified in [3]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements.
+- 7) "UE Positioning GPS Ionospheric Model" (subclause 10.3.7.92 in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [3] for computation of the ionospheric delay.
+
+## F.3 Weighted Least Squares (WLS) position solution
+
+The WLS position solution problem is concerned with the task of solving for four unknowns;  $x_u, y_u, z_u$  the receiver coordinates in a suitable frame of reference (usually ECEF) and  $b_u$  the receiver clock bias relative to the selected GNSS specific system time. It typically requires the following steps:
+
+### Step 1: Formation of pseudo-ranges
+
+The observation of code phase reported by the UE for each satellite  $SV_i$  is related to the pseudo-range/ $c$  modulo the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite  $SV_i$  at the time of measurement is calculated, and the integer number of milliseconds to be added to the UE code phase measurements is obtained.
+
+### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets
+
+In case the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator:
+
+$$\rho_{GNSS_{m,i}} \equiv \rho_{GNSS_{m,i}} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$
+
+where  $\rho_{GNSS_{m,i}}$  is the measured pseudo-range of satellite  $i$  of GNSS $_m$ . The system time  $t_{GNSS_k}$  of GNSS $_k$  is the reference time frame, and  $(t_{GNSS_k} - t_{GNSS_m})$  is the available GNSS-GNSS time offset, and  $c$  is the speed of light.
+
+### Step 3: Formation of weighting matrix
+
+The UE reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [16]. According to 3GPP TS 25.331 [14], the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa,  $X_i$  and a 3 bit exponent,  $Y_i$  for each  $SV_i$  of GNSS $_j$ :
+
+$$w_{GNSS_{j,i}} = RMSError = 0.5 \times \left(1 + \frac{X_i}{8}\right) 2^{Y_i}$$
+
+The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values:
+
+$$W = \text{diag}\{1/w_{\text{GNSS},1,1}^2, 1/w_{\text{GNSS},1,2}^2, \dots, 1/w_{\text{GNSS},1,n}^2, \dots, 1/w_{\text{GNSS},m,1}^2, 1/w_{\text{GNSS},m,2}^2, \dots, 1/w_{\text{GNSS},m,l}^2\}$$
+
+### Step 4: WLS position solution
+
+The WLS position solution is described in e.g., [16] and usually requires the following steps:
+
+- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed.
+- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS.
+- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [17] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model (see subclause F.2) adapted to the particular GNSS frequency.
+- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
+  - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report.
+  - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [16].
+  - c) Calculate difference between predicted and measured pseudo-ranges  $\Delta\rho$ .
+  - d) Calculate the "Geometry Matrix" **G** as defined in [16]:
+
+$$G \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{\text{GNSS},1,1}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS},1,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},1,n}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},m,1}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS},m,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},m,l}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{\text{GNSS},m,i} \equiv \frac{\mathbf{r}_{s_{\text{GNSS},m,i}} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{s_{\text{GNSS},m,i}} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{s_{\text{GNSS},m,i}} \text{ is the satellite position vector for SV}_i \text{ of GNSS}_m \text{ (calculated in 1) above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$
+
+- e) Calculate the WLS solution according to [16]:
+
+$$\Delta\hat{\mathbf{x}} = (G^T W G)^{-1} G^T W \Delta\rho$$
+
+- f) Adding the  $\Delta\hat{\mathbf{x}}$  to the initial state estimate gives an improved estimate of the state vector:
+
+$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta\hat{\mathbf{x}}.$$
+
+- 5) This new state vector  $\hat{\mathbf{x}}$  can be used as new initial estimate and the procedure is repeated until the change in  $\hat{\mathbf{x}}$  is sufficiently small.
+
+### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system
+
+The state vector  $\hat{\mathbf{x}}$  calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates  $x_u, y_u, z_u$  to geodetic latitude  $\phi$ , longitude  $\lambda$  and altitude  $h$  on the WGS84 reference ellipsoid.
+
+### **Step 6: Calculation of "2-D Position Errors"**
+
+The latitude  $\varphi$  / longitude  $\lambda$  obtained after Step 5 is used to calculate the 2-D position error.
+

marked/Rel-17/25_series/25173/raw.md

@@ -0,0 +1,1114 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                       |           |
+|-----------------------------------------------------------------------|-----------|
+| Foreword .....                                                        | 5         |
+| 1 Scope.....                                                          | 6         |
+| 2 References.....                                                     | 6         |
+| 3 Definitions, symbols, abbreviations and test tolerances .....       | 7         |
+| 3.1 Definitions.....                                                  | 7         |
+| 3.2 Symbols.....                                                      | 7         |
+| 3.3 Abbreviations .....                                               | 8         |
+| 3.4 Test tolerances.....                                              | 8         |
+| 4 General.....                                                        | 8         |
+| 4.1 Introduction .....                                                | 8         |
+| 4.2 Measurement parameters.....                                       | 9         |
+| 4.2.1 UE-based A-GANSS measurement parameters .....                   | 9         |
+| 4.2.2 UE-assisted A-GANSS measurement parameters .....                | 9         |
+| 4.3 Response time .....                                               | 9         |
+| 4.4 Time assistance .....                                             | 9         |
+| 4.4.1 Use of fine time assistance .....                               | 9         |
+| 4.5 RRC states.....                                                   | 10        |
+| 4.6 2D position error .....                                           | 10        |
+| 4.7 User equipment supporting multiple constellations .....           | 10        |
+| 4.8 User equipment supporting multiple signals.....                   | 10        |
+| 5 A-GANSS minimum performance requirements.....                       | 11        |
+| 5.1 Sensitivity.....                                                  | 11        |
+| 5.1.1 Coarse time assistance.....                                     | 11        |
+| 5.1.1.1 Minimum requirements (coarse time assistance).....            | 11        |
+| 5.1.2 Fine time assistance.....                                       | 12        |
+| 5.1.2.1 Minimum requirements (fine time assistance).....              | 12        |
+| 5.2 Nominal accuracy.....                                             | 12        |
+| 5.2.1 Minimum requirements (nominal accuracy) .....                   | 13        |
+| 5.3 Dynamic range .....                                               | 13        |
+| 5.3.1 Minimum requirements (dynamic range).....                       | 14        |
+| 5.4 Multi-path scenario .....                                         | 14        |
+| 5.4.1 Minimum requirements (multi-path scenario).....                 | 15        |
+| 5.5 Moving scenario and periodic update .....                         | 15        |
+| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16        |
+| <b>Annex A (normative): Test cases.....</b>                           | <b>18</b> |
+| A.1 Conformance tests.....                                            | 18        |
+| A.2 Requirement classification for statistical testing .....          | 18        |
+| <b>Annex B (normative): Test conditions.....</b>                      | <b>19</b> |
+| B.1 General.....                                                      | 19        |
+| B.1.1 Parameter values .....                                          | 19        |
+| B.1.2 Time assistance .....                                           | 19        |
+| B.1.3 GANSS reference time.....                                       | 19        |
+| B.1.4 Reference and UE locations .....                                | 20        |
+| B.1.5 Satellite constellation and assistance data.....                | 20        |
+| B.1.6 Atmospheric delay.....                                          | 20        |
+| B.1.7 Sensors .....                                                   | 20        |
+| B.1.8 Information elements.....                                       | 20        |
+| B.1.9 GNSS signals.....                                               | 20        |
+| B.1.10 RESET UE POSITIONING STORED INFORMATION Message .....          | 20        |
+| B.1.11 GNSS system time offsets.....                                  | 21        |
+
+|                             |                                                                                |           |
+|-----------------------------|--------------------------------------------------------------------------------|-----------|
+| <b>Annex C (normative):</b> | <b>Propagation conditions .....</b>                                            | <b>22</b> |
+| C.1                         | Static propagation conditions.....                                             | 22        |
+| C.2                         | Multi-path case.....                                                           | 22        |
+| <b>Annex D (normative):</b> | <b>Measurement sequence chart.....</b>                                         | <b>24</b> |
+| D.1                         | General.....                                                                   | 24        |
+| D.2                         | TTFF measurement sequence chart .....                                          | 24        |
+| D.3                         | Periodic update measurement sequence chart.....                                | 25        |
+| <b>Annex E (normative):</b> | <b>Assistance data required for testing .....</b>                              | <b>27</b> |
+| E.1                         | Introduction.....                                                              | 27        |
+| E.2                         | GPS assistance data.....                                                       | 27        |
+| E.3                         | GANSS assistance data.....                                                     | 27        |
+| <b>Annex F (normative):</b> | <b>Converting UE-assisted measurement reports into position estimates ....</b> | <b>31</b> |
+| F.1                         | Introduction.....                                                              | 31        |
+| F.2                         | UE measurement reports.....                                                    | 31        |
+| F.3                         | Weighted Least Squares (WLS) position solution .....                           | 32        |
+| Annex G (informative):      | Change history.....                                                            | 35        |
+
+# --- Foreword
+
+This Technical Specification 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 establishes the minimum performance requirements for A-GNSS for TDD mode of UTRA for the User Equipment (UE) that supports A-GNSS. It includes the minimum performance requirements for both UE-based and UE-assisted A-GNSS. The minimum performance requirements also include combinations of A-GPS and A-GNSS.
+
+# --- 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 TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [2] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)".
+- [3] IS-GPS-200, Revision D, "Navstar GPS Space Segment/Navigation User Interfaces", March 7<sup>th</sup>, 2006.
+- [4] IS-GPS-705, "Navstar GPS Space Segment/User Segment L5 Interfaces", September 22, 2005.
+- [5] IS-GPS-800, "Navstar GPS Space Segment/User Segment L1C Interfaces", September 4, 2008.
+- [6] IS-QZSS, "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS", Ver.1.1, July 31, 2009.
+- [7] "Galileo OS Signal in Space ICD (OS SIS ICD)", Draft 0, Galileo Joint Undertaking, May 23<sup>rd</sup>, 2006.
+- [8] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1, 2008.
+- [9] "Specification for the Wide Area Augmentation System (WAAS) ", US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
+- [10] 3GPP TS 25.171: "Requirements for support of Assisted Global Positioning System (A-GPS) Frequency Division Duplex (FDD)".
+- [11] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)".
+- [12] 3GPP TS 34.172: "Terminal Conformance Specification, Assisted Galileo and Additional Navigation Satellite Systems (A-GNSS) (FDD)".
+- [13] 3GPP TS 34.109: "Special conformance testing functions".
+- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [15] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [16] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996.
+
+- [17] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119.
+- [18] 3GPP TS 25.225: "Physical layer; Measurements (TDD)".
+- [19] BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal BII(Version 1.0), China Satellite Navigation Office, December 2012.
+- [20] 3GPP TS 37.571: "User Equipment (UE) conformance specification for UE positioning".
+
+# 3 Definitions, symbols, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 25.102 [1], 3GPP TS 25.105 [2] and the following apply:
+
+**Horizontal Dilution Of Precision (HDOP)**: measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbol applies:
+
+|                                 |                                                                                                                            |
+|---------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| BII                             | BeiDou BII navigation signal with carrier frequency of 1561.098 MHz                                                        |
+| $c$                             | Speed of light.                                                                                                            |
+| E1                              | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz.                                                       |
+| E5                              | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz.                                                       |
+| E6                              | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz.                                                       |
+| G1                              | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . |
+| G2                              | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . |
+| $k$                             | GLONASS channel number, $k = -7 \dots 13$ .                                                                                |
+| L1 C/A                          | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz.              |
+| L1C                             | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz.                                             |
+| L2C                             | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz.                                             |
+| L5                              | GPS or QZSS L5 navigation signal with carrier frequency of 1176.450 MHz.                                                   |
+| <b>G</b>                        | Geometry Matrix.                                                                                                           |
+| $\rho_{\text{GNSS}_m, i}$       | Measured pseudo-range of satellite $i$ of $\text{GNSS}_m$ .                                                                |
+| <b>W</b>                        | Weighting Matrix.                                                                                                          |
+| $\mathbf{1}_{\text{GNSS}_m, i}$ | Line of sight unit vector from the user to the satellite $i$ of $\text{GNSS}_m$ .                                          |
+| $x$                             | State vector of user position and clock bias.                                                                              |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                              |
+|---------|--------------------------------------------------------------|
+| A-GANSS | Assisted-Galileo and Additional Navigation Satellite Systems |
+| A-GNSS  | Assisted-GNSS                                                |
+| A-GPS   | Assisted-Global Positioning System                           |
+| AWGN    | Additive White Gaussian Noise                                |
+| BDS     | BeiDou Navigation Satellite System                           |
+| C/A     | Coarse/Acquisition                                           |
+
+|         |                                                                                              |
+|---------|----------------------------------------------------------------------------------------------|
+| DUT     | Device Under Test                                                                            |
+| ECEF    | Earth-Centered, Earth-Fixed                                                                  |
+| ECI     | Earth-Centered-Inertial                                                                      |
+| FDD     | Frequency Division Duplex                                                                    |
+| GEO     | Geostationary Earth Orbit                                                                    |
+| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) |
+| GNSS    | Global Navigation Satellite System                                                           |
+| GPS     | Global Positioning System                                                                    |
+| GSS     | GNSS System Simulator                                                                        |
+| HDOP    | Horizontal Dilution Of Precision                                                             |
+| ICD     | Interface Control Document                                                                   |
+| IGSO    | Inclined Geosynchronous Satellite Orbit/Interface Specification                              |
+| LOS     | Line Of Sight                                                                                |
+| MEO     | Medium Earth Orbit                                                                           |
+| QZS     | Quasi-Zenith Satellite                                                                       |
+| QZSS    | Quasi-Zenith Satellite System                                                                |
+| RF      | Radio Frequency                                                                              |
+| RRC     | Radio Resource Control                                                                       |
+| SBAS    | Space Based Augmentation System                                                              |
+| SFN     | System Frame Number                                                                          |
+| SS      | System Simulator                                                                             |
+| SV      | Space Vehicle                                                                                |
+| TOD     | Time Of Day                                                                                  |
+| TOW     | Time Of Week                                                                                 |
+| TTFF    | Time To First Fix                                                                            |
+| UE      | User Equipment                                                                               |
+| UTRA    | Universal Terrestrial Radio Access                                                           |
+| UTRAN   | Universal Terrestrial Radio Access Network                                                   |
+| WLS     | Weighted Least Squares                                                                       |
+| WGS-84  | World Geodetic System 1984                                                                   |
+
+## 3.4 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.172 [12] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETR 273-1-2 [15], subclause 6.5.
+
+# --- 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for both UE-based and UE-assisted TDD A-GNSS terminals. The minimum performance requirements also include combinations of A-GPS and A-GNSS.
+
+## 4.2 Measurement parameters
+
+### 4.2.1 UE-based A-GNSS measurement parameters
+
+In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
+
+### 4.2.2 UE-assisted A-GNSS measurement parameters
+
+In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GNSS are the UE GANSS code measurements, as specified in 3GPP TS 25.225 [18]. The UE GANSS code measurements that may be combined with UE GPS code phase measurements as specified in 3GPP TS 25.225 [18] are converted into a horizontal position estimate using the procedure detailed in Annex F.
+
+## 4.3 Response time
+
+Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GANSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GANSS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GANSS and GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [13] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10.
+
+## 4.4 Time assistance
+
+Time assistance is the provision of GANSS reference time to the UE from the network via RRC messages. Currently two different GANSS time assistance methods can be provided by the network.
+
+- a) Coarse time assistance is always provided by the network and provides current GANSS time to the UE. The time provided is within  $\pm 2$  seconds of GANSS system time. It is signalled to the UE by means of the GANSS Day and GANSS TOD fields in the GANSS Reference Time assistance data IE.
+- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GANSS system time and the current UTRAN time. The accuracy of this relationship is  $\pm 10 \mu\text{s}$  of the actual relationship. This addresses the case when the network can provide an improved GANSS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GANSS timing of cell frames fields in the GANSS Reference Time assistance data IE.
+
+The specific GANSS system time is identified through the GANSS Time ID field of the GANSS Reference Time IE. In case where several GANSS are used in the tests, only one GANSS Time ID is used to determine the Time of Day. For all the constellations, the GANSS Time Model assistance and UTC Model assistance shall be available at the system simulator, as specified in Annex E.
+
+The time of applicability of time assistance is the beginning of the System Frame of the message containing the GANSS Reference time.
+
+### 4.4.1 Use of fine time assistance
+
+The use of fine time assistance to improve the GANSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2.
+
+## 4.5 RRC states
+
+The minimum A-GNSS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in Annex B.
+
+## 4.6 2D position error
+
+The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered.
+
+## 4.7 User equipment supporting multiple constellations
+
+Minimum performance requirements are defined for each global GANSS constellation (Galileo, Modernized GPS, GLONASS and BDS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated.
+
+NOTE: For test cases where signals from "GPS" and "Modernized GPS" are included, "GPS" and "Modernized GPS" are considered as a single constellation, unless otherwise specified.
+
+## 4.8 User equipment supporting multiple signals
+
+For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 5 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5 plus the relative power level defined in Table 4.8-1.
+
+**Table 4.8-1: Relative signal power levels for each signal type for each GNSS**
+
+|                                                        | Galileo |       | GPS/Modernized GPS |         | GLONASS |       | QZSS   |         | SBAS |      | BDS |    |       |
+|--------------------------------------------------------|---------|-------|--------------------|---------|---------|-------|--------|---------|------|------|-----|----|-------|
+|                                                        | E1      | 0 dB  | L1 C/A             | 0 dB    | G1      | 0 dB  | L1 C/A | 0 dB    | L1   | 0 dB | B1I | D1 | 0 dB  |
+| Signal power levels relative to reference power levels | E6      | +2 dB | L1C                | +1.5 dB | G2      | -6 dB | L1C    | +1.5 dB |      |      |     | D2 | +5 dB |
+|                                                        | E5      | +2 dB | L2C                | -1.5 dB |         |       | L2C    | -1.5 dB |      |      |     |    |       |
+|                                                        |         |       | L5                 | +3.6 dB |         |       | L5     | +3.6 dB |      |      |     |    |       |
+|                                                        |         |       |                    |         |         |       |        |         |      |      |     |    |       |
+
+NOTE 1: For test cases which involve "Modernized GPS", the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports "GPS" in addition to "Modernized GPS".
+
+NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately.
+
+NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type.
+
+# 5 A-GANSS minimum performance requirements
+
+The A-GANSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GANSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E.
+
+The requirements in CELL\_PCH and URA\_PCH states are for further study.
+
+## 5.1 Sensitivity
+
+A sensitivity requirement is essential for verifying the performance of A-GANSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.
+
+### 5.1.1 Coarse time assistance
+
+In this test case 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.1-1: Test parameters**
+
+| System             | Parameters                                | Unit    | Value             |
+|--------------------|-------------------------------------------|---------|-------------------|
+|                    | Number of generated satellites per system | -       | See Table 5.1.1-2 |
+|                    | Total number of generated satellites      | -       | 6                 |
+|                    | HDOP range                                |         | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -       | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds | $\pm 2$           |
+| Galileo            | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| GPS <sup>(1)</sup> | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| GLONASS            | Reference high signal power level         | dBm     | -142              |
+|                    | Reference low signal power level          | dBm     | -147              |
+| BDS                | Reference high signal power level         | dBm     | -136              |
+|                    | Reference low signal power level          | dBm     | -145              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.1-2: Power level and satellite allocation**
+
+|                      |                   | Satellite allocation for each constellation |        |        |
+|----------------------|-------------------|---------------------------------------------|--------|--------|
+|                      |                   | GNSS-1 <sup>(1)</sup>                       | GNSS-2 | GNSS-3 |
+| Single constellation | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 5                                           | -      | -      |
+| Dual constellation   | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 2                                           | 3      | -      |
+| Triple constellation | High signal level | 1                                           | -      | -      |
+|                      | Low signal level  | 1                                           | 2      | 2      |
+
+Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.
+
+#### 5.1.1.1 Minimum requirements (coarse time assistance)
+
+The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1.
+
+**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+### 5.1.2 Fine time assistance
+
+This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.
+
+**Table 5.1.2-1: Test parameters**
+
+| System             | Parameters                                | Unit    | Value             |
+|--------------------|-------------------------------------------|---------|-------------------|
+|                    | Number of generated satellites per system | -       | See Table 5.1.2-2 |
+|                    | Total number of generated satellites      | -       | 6                 |
+|                    | HDOP range                                |         | 1.4 to 2.1        |
+|                    | Propagation conditions                    | -       | AWGN              |
+|                    | GANSS coarse time assistance error range  | seconds | ±2                |
+|                    | GANSS fine time assistance error range    | µs      | ±10               |
+| Galileo            | Reference signal power level              | dBm     | -147              |
+| GPS <sup>(1)</sup> | Reference signal power level              | dBm     | -147              |
+| GLONASS            | Reference signal power level              | dBm     | -147              |
+| BDS                | Reference signal power level              | dBm     | -147              |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.
+
+**Table 5.1.2-2: Satellite allocation**
+
+|                      | Satellite allocation for each constellation |        |        |
+|----------------------|---------------------------------------------|--------|--------|
+|                      | GNSS-1                                      | GNSS-2 | GNSS-3 |
+| Single constellation | 6                                           | -      | -      |
+| Dual constellation   | 3                                           | 3      | -      |
+| Triple constellation | 2                                           | 2      | 2      |
+
+#### 5.1.2.1 Minimum requirements (fine time assistance)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1.
+
+**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.2 Nominal accuracy
+
+Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2.
+
+**Table 5.2-1: Test parameters**
+
+| System             | Parameters                                      | Unit    | Value                 |
+|--------------------|-------------------------------------------------|---------|-----------------------|
+|                    | Number of generated satellites per system       | -       | See Table 5.2-2       |
+|                    | Total number of generated satellites            | -       | 6 or 7 <sup>(2)</sup> |
+|                    | HDOP Range                                      | -       | 1.4 to 2.1            |
+|                    | Propagation conditions                          | -       | AWGN                  |
+|                    | GANSS coarse time assistance error range        | seconds | ±2                    |
+| GPS <sup>(1)</sup> | Reference signal power level for all satellites | dBm     | -128.5                |
+| Galileo            | Reference signal power level for all satellites | dBm     | -127                  |
+| GLONASS            | Reference signal power level for all satellites | dBm     | -131                  |
+| QZSS               | Reference signal power level for all satellites | dBm     | -128.5                |
+| SBAS               | Reference signal power level for all satellites | dBm     | -131                  |
+| BDS                | Reference signal power level for all satellites | dBm     | -133                  |
+
+Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.  
+Note 2: 7 satellites apply only for SBAS case.
+
+If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
+
+If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
+
+**Table 5.2-2: Satellite allocation**
+
+|                                                                            | Satellite allocation for each constellation |                       |                       |      |
+|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|------|
+|                                                                            | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> | SBAS |
+| Single constellation                                                       | 6                                           | --                    | --                    | 1    |
+| Dual constellation                                                         | 3                                           | 3                     | --                    | 1    |
+| Triple constellation                                                       | 2                                           | 2                     | 2                     | 1    |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                                             |                       |                       |      |
+
+### 5.2.1 Minimum requirements (nominal accuracy)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1.
+
+**Table 5.2.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 15 m               | 20 s              |
+
+## 5.3 Dynamic range
+
+The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.
+
+In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used.
+
+**Table 5.3-1: Test parameters**
+
+| System                                                                                      | Parameters                                | Unit    | Value           |
+|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------|
+|                                                                                             | Number of generated satellites per system | -       | See Table 5.3-2 |
+|                                                                                             | Total number of generated satellites      | -       | 6               |
+|                                                                                             | HDOP Range                                | -       | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                    | -       | AWGN            |
+|                                                                                             | GANSS coarse time assistance error range  | seconds | ±2              |
+| Galileo                                                                                     | Reference high signal power level         | dBm     | -127.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| GPS <sup>(1)</sup>                                                                          | Reference high signal power level         | dBm     | -129            |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| GLONASS                                                                                     | Reference high signal power level         | dBm     | -131.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -147            |
+| BDS                                                                                         | Reference high signal power level         | dBm     | -133.5          |
+|                                                                                             | Reference low signal power level          | dBm     | -145            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                           |         |                 |
+
+**Table 5.3-2: Power level and satellite allocation**
+
+|                                                                            |                   | <b>Satellite allocation for each constellation</b> |                             |                             |
+|----------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------------|-----------------------------|
+|                                                                            |                   | <b>GNSS 1<sup>(1)</sup></b>                        | <b>GNSS 2<sup>(1)</sup></b> | <b>GNSS 3<sup>(1)</sup></b> |
+| Single constellation                                                       | High signal level | 2                                                  | --                          | --                          |
+|                                                                            | Low signal level  | 4                                                  | --                          | --                          |
+| Dual constellation                                                         | High signal level | 1                                                  | 1                           | --                          |
+|                                                                            | Low signal level  | 2                                                  | 2                           | --                          |
+| Triple constellation                                                       | High signal level | 1                                                  | 1                           | 1                           |
+|                                                                            | Low signal level  | 1                                                  | 1                           | 1                           |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                   |                                                    |                             |                             |
+
+### 5.3.1 Minimum requirements (dynamic range)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1.
+
+**Table 5.3.1-1: Minimum requirements**
+
+| <b>System</b> | <b>Success rate</b> | <b>2-D position error</b> | <b>Max response time</b> |
+|---------------|---------------------|---------------------------|--------------------------|
+| All           | 95 %                | 100 m                     | 20 s                     |
+
+## 5.4 Multi-path scenario
+
+The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.
+
+In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal.
+
+**Table 5.4-1: Test parameter**
+
+| <b>System</b>                                                                               | <b>Parameters</b>                         | <b>Unit</b> | <b>Value</b>    |
+|---------------------------------------------------------------------------------------------|-------------------------------------------|-------------|-----------------|
+|                                                                                             | Number of generated satellites per system | -           | See Table 5.4-2 |
+|                                                                                             | Total number of generated satellites      | -           | 6               |
+|                                                                                             | HDOP range                                |             | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                    | -           | AWGN            |
+|                                                                                             | GNSS coarse time assistance error range   | seconds     | ±2              |
+| Galileo                                                                                     | Reference signal power level              | dBm         | -127            |
+| GPS <sup>(1)</sup>                                                                          | Reference signal power level              | dBm         | -128.5          |
+| GLONASS                                                                                     | Reference signal power level              | dBm         | -131            |
+| BDS                                                                                         | Reference signal power level              | dBm         | -133            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                           |             |                 |
+
+**Table 5.4-2: Channel model allocation**
+
+|                      |                 | <b>Channel model allocation for each constellation</b> |               |               |
+|----------------------|-----------------|--------------------------------------------------------|---------------|---------------|
+|                      |                 | <b>GNSS-1</b>                                          | <b>GNSS-2</b> | <b>GNSS-3</b> |
+| Single constellation | One-tap channel | 2                                                      | --            | --            |
+|                      | Two-tap channel | 4                                                      | --            | --            |
+| Dual constellation   | One-tap channel | 1                                                      | 1             | --            |
+|                      | Two-tap channel | 2                                                      | 2             | --            |
+| Triple constellation | One-tap channel | 1                                                      | 1             | 1             |
+|                      | Two-tap channel | 1                                                      | 1             | 1             |
+
+### 5.4.1 Minimum requirements (multi-path scenario)
+
+The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1.
+
+**Table 5.4.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Max response time |
+|--------|--------------|--------------------|-------------------|
+| All    | 95 %         | 100 m              | 20 s              |
+
+## 5.5 Moving scenario and periodic update
+
+The purpose of the test case is to verify the receiver's capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.
+
+In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.
+
+The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
+
+**Table 5.5-1: Trajectory Parameters**
+
+| Parameter                        | Distance (m) | Speed (km/h)            |
+|----------------------------------|--------------|-------------------------|
+| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20           | 25                      |
+| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250          | 25 to 100 and 100 to 25 |
+| $l_{13}$                         | 400          | 100                     |
+| $l_{23}$                         | 900          | 100                     |
+
+![Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the top edge and l21, l22, l23, l24, l25 on the bottom edge. Arrows indicate the direction of movement: clockwise from the top-left corner.](3f1987804d7d78bc3b3bc560e974280a_img.jpg)
+
+Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the top edge and l21, l22, l23, l24, l25 on the bottom edge. Arrows indicate the direction of movement: clockwise from the top-left corner.
+
+**Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case**
+
+**Table 5.5-2: Test Parameters**
+
+| System                                                                                      | Parameters                                      | Unit    | Value           |
+|---------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-----------------|
+|                                                                                             | Number of generated satellites per system       | -       | See Table 5.5-3 |
+|                                                                                             | Total number of generated satellites            | -       | 6               |
+|                                                                                             | HDOP Range per system                           | -       | 1.4 to 2.1      |
+|                                                                                             | Propagation conditions                          | -       | AWGN            |
+|                                                                                             | GANSS coarse time assistance error range        | seconds | ±2              |
+| Galileo                                                                                     | Reference signal power level for all satellites | dBm     | -127            |
+| GPS <sup>(1)</sup>                                                                          | Reference signal power level for all satellites | dBm     | -128.5          |
+| GLONASS                                                                                     | Reference signal power level for all satellites | dBm     | -131            |
+| BDS                                                                                         | Reference signal power level for all satellites | dBm     | -133            |
+| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |                                                 |         |                 |
+
+**Table 5.5-3: Satellite allocation**
+
+|                                                                            | Satellite allocation for each constellation |                       |                       |
+|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|
+|                                                                            | GNSS 1 <sup>(1)</sup>                       | GNSS 2 <sup>(1)</sup> | GNSS 3 <sup>(1)</sup> |
+| Single constellation                                                       | 6                                           | --                    | --                    |
+| Dual constellation                                                         | 3                                           | 3                     | --                    |
+| Triple constellation                                                       | 2                                           | 2                     | 2                     |
+| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |                                             |                       |                       |
+
+### 5.5.1 Minimum requirements (moving scenario and periodic update)
+
+The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates.
+
+NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS/GANSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 5.5.1-1.
+
+**Table 5.5.1-1: Minimum requirements**
+
+| System | Success rate | 2-D position error | Periodical reporting interval |
+|--------|--------------|--------------------|-------------------------------|
+| All    | 95 %         | 50 m               | 2 s                           |
+
+# --- Annex A (normative): Test cases ---
+
+## A.1 Conformance tests
+
+The conformance tests are specified in 3GPP TS 37.571 [20]. Statistical interpretation of the requirements is described in clause A.2.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 37.571 [20].
+
+# Annex B (normative): Test conditions
+
+## B.1 General
+
+This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated.
+
+### B.1.1 Parameter values
+
+Additionally, amongst all the listed parameters (see Annex E), the following values for some important parameters are to be used in the measurement control message.
+
+**Table B.1.1-1: Parameter values**
+
+| Information element                                 | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests |
+|-----------------------------------------------------|---------------------------------------------------|--------------------------------------------|------------------------|
+| Measurement Reporting Mode                          | Periodical reporting                              | Periodical reporting                       | Periodical reporting   |
+| Amount of reporting                                 | 1                                                 | 1                                          | Infinite (see Note)    |
+| Reporting interval                                  | 20 000 ms                                         | 20 000 ms                                  | 2 000 ms               |
+| Horizontal accuracy                                 | 51.2 m                                            | 7.7 m                                      | 24.5 m                 |
+| Vertical accuracy                                   | 102 m                                             | 102 m                                      | 102 m                  |
+| Note: Infinite means during the complete test time. |                                                   |                                            |                        |
+
+In the Sensitivity test case with Fine Time Assistance, the following parameter values are used.
+
+**Table B.1.1-2: Parameters for fine time assistance test**
+
+| Information element                           | Value   |
+|-----------------------------------------------|---------|
+| TUTRAN-GPS drift rate                         | 0       |
+| TUTRAN-GANSS drift rate                       | 0       |
+| UE Positioning GPS Reference Time Uncertainty | 10.2 µs |
+| GANSS TOD Uncertainty                         | 10.2 µs |
+
+### B.1.2 Time assistance
+
+For every Test Instance in each TTFF test case, the GANSS/GPS Reference Time shall have a random offset, relative to GANSS/GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS/GANSS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution.
+
+For the Moving Scenario and Periodic Update Test Case the GANSS/GPS Reference Time shall be set to the nominal value.
+
+### B.1.3 GANSS reference time
+
+For every Test Instance in each TTFF test case, the GANSS reference time (and GPS reference time, if applicable) shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix.
+
+### B.1.4 Reference and UE locations
+
+There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the
+
+new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %.
+
+For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions.
+
+For test cases which include satellites from regional systems, such as QZSS and SBAS, the reference location shall be selected within the defined coverage area of the systems.
+
+### B.1.5 Satellite constellation and assistance data
+
+The satellite constellation shall consist of 24 satellites for GLONASS; 27 satellites for GPS, Modernized GPS and Galileo; 3 satellites for QZSS; 2 satellites for SBAS and 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo, GLONASS and BDS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites (or 7 if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for GPS, Modernized GPS, Galileo, GLONASS and BDS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO.
+
+NOTE: Currently up to 30 BDS satellites (maximum 22 MEO) can be supported.
+
+### B.1.6 Atmospheric delay
+
+Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs.
+
+### B.1.7 Sensors
+
+The minimum performance requirements shall be met without the use of any data coming from sensors that can aid the positioning.
+
+### B.1.8 Information elements
+
+The information elements that are available to the UE in all the test cases are listed in Annex E.
+
+### B.1.9 GNSS signals
+
+The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
+
+### B.1.10 RESET UE POSITIONING STORED INFORMATION Message
+
+In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [13] clause 5.4 shall be used.
+
+When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS* it shall:
+
+- discard any internally stored GPS and GANSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler);
+- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition;
+
+- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information.
+
+### B.1.11 GNSS system time offsets
+
+If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns.
+
+# Annex C (normative): Propagation conditions
+
+## C.1 Static propagation conditions
+
+The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
+
+## C.2 Multi-path case
+
+Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GANSS signals are defined in table C.2-1.
+
+**Table C.2-1: Multipath case**
+
+| Initial Relative Delay [m]                             | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] |
+|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------|
+| 0                                                      | $F_d$                                 | $F_d / N$                          | 0                        |
+| X                                                      | $F_d - 0.1$                           | $(F_d - 0.1) / N$                  | Y                        |
+| Note: Discrete Doppler frequency is used for each tap. |                                       |                                    |                          |
+
+Where the X and Y depends on the GNSS signal type and is shown in table C.2-2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in table C.2-3 (where k in table C.2-3 is the GLONASS frequency channel number).
+
+**Table C.2-2: Relative Delay and Attenuation of Non Line of Sight Signals**
+
+| System             | Signals | X [m] | Y [dB] |
+|--------------------|---------|-------|--------|
+| Galileo            | E1      | 125   | -4.5   |
+|                    | E5a     | 15    | -6     |
+|                    | E5b     | 15    | -6     |
+| GPS/Modernized GPS | L1 C/A  | 150   | -6     |
+|                    | L1C     | 125   | -4.5   |
+|                    | L2C     | 150   | -6     |
+|                    | L5      | 15    | -6     |
+| GLONASS            | G1      | 275   | -12.5  |
+|                    | G2      | 275   | -12.5  |
+| BDS                | B1I     | 75    | -4.5   |
+
+**Table C.2-3: Ratio between the transmitted carrier frequency of the signals and the transmitted chip rate**
+
+| System             | Signals | N                        |
+|--------------------|---------|--------------------------|
+| Galileo            | E1      | 1540                     |
+|                    | E5a     | 115                      |
+|                    | E5b     | 118                      |
+| GPS/Modernized GPS | L1 C/A  | 1540                     |
+|                    | L1C     | 1540                     |
+|                    | L2C     | 1200                     |
+|                    | L5      | 115                      |
+| GLONASS            | G1      | $3135.03 + k \cdot 1.10$ |
+|                    | G2      | $2438.36 + k \cdot 0.86$ |
+| BDS                | B1I     | 763                      |
+
+The initial carrier phase difference between taps shall be randomly selected between 0 and  $2\pi$ . The initial value shall have uniform random distribution.
+
+# Annex D (normative): Measurement sequence chart
+
+## D.1 General
+
+The measurement Sequence Charts that are required in all the test cases, are defined in this clause.
+
+## D.2 TTFF measurement sequence chart
+
+The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (dashed line); (f) UE sends 'RRC Measurement Report' to SS.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg)
+
+```
+
+sequenceDiagram
+    participant SS
+    participant UE
+    Note left of SS: (a)
+    SS->>UE: Reset UE Positioning Stored Information
+    Note left of SS: (b)
+    SS->>UE: RRC Measurement Control (Setup)
+    Note left of UE: (c)
+    UE-->>SS: RRC Measurement Report (Assistance Data Request)
+    Note left of SS: (d)
+    SS->>UE: RRC Measurement Control (Modify)
+    Note left of SS: (e)
+    SS-->>UE: RRC Measurement Control (Modify)
+    Note left of UE: (f)
+    UE-->>SS: RRC Measurement Report
+  
+```
+
+Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (dashed line); (f) UE sends 'RRC Measurement Report' to SS.
+
+Figure D.2-1: Measurement Sequence Chart for the TTFF Test Cases
+
+- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                          |                                                                        |
+|------------------------------------------|------------------------------------------------------------------------|
+| <i>MEASUREMENT COMMAND</i>               | Setup                                                                  |
+| <i>CHOICE MEASUREMENT TYPE</i>           | UE positioning measurement                                             |
+| <i>UE POSITIONING REPORTING QUANTITY</i> |                                                                        |
+| >Method Type                             | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                     | set to 'GPS';                                                          |
+| >Horizontal Accuracy                     | as defined in Annex B;                                                 |
+| >Vertical Accuracy                       | as defined in Annex B;                                                 |
+| >Additional Assistance Data Request      | TRUE                                                                   |
+| >GANSS Positioning Methods               | set according to the UE capabilities and test case;                    |
+| <i>MEASUREMENT VALIDITY</i>              |                                                                        |
+| >UE state                                | All states                                                             |
+| <i>CHOICE REPORTING CRITERIA</i>         | Periodical reporting criteria                                          |
+| >Amount of reporting                     | 1 (see Annex B);                                                       |
+| >Reporting interval                      | 20 seconds (see Annex B);                                              |
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GANSS assistance data.
+
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE UE POSITIONING MEASURED RESULTS with UE POSITIONING POSITION ESTIMATE INFO present in case of UE-based, or UE POSITIONING GPS MEASURED RESULTS and/or UE POSITIONING GANSS MEASURED RESULTS present in case of UE-assisted GANSS.
+
+Steps (a) to (f) are repeated for each test instance.
+
+## D.3 Periodic update measurement sequence chart
+
+The measurement sequence chart for the Moving Scenario and Periodic Update test case, for both UE-assisted and UE-based GANSS, is defined in this subclause.
+
+![Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for a periodic update measurement sequence. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. (i) UE to SS: RRC Measurement Report. Vertical ellipsis between (h) and (i) indicates repeated steps.](86b4670fc1a5a694821ee92b99c1209a_img.jpg)
+
+Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for a periodic update measurement sequence. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. (i) UE to SS: RRC Measurement Report. Vertical ellipsis between (h) and (i) indicates repeated steps.
+
+**Figure D.3-1: Measurement Sequence Chart for the Moving Scenario and Periodic Update Test Case**
+
+- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*.
+- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements:
+
+|                                          |                                                                        |
+|------------------------------------------|------------------------------------------------------------------------|
+| <i>MEASUREMENT COMMAND</i>               | Setup                                                                  |
+| <i>CHOICE MEASUREMENT TYPE</i>           | UE positioning measurement                                             |
+| <i>UE POSITIONING REPORTING QUANTITY</i> |                                                                        |
+| >Method Type                             | set to either 'UE assisted' or 'UE based', dependent on the test case; |
+| >Positioning Methods                     | set to 'GPS';                                                          |
+| >Horizontal Accuracy                     | as defined in Annex B;                                                 |
+
+>Vertical Accuracy as defined in Annex B;  
+ >Additional Assistance Data Request TRUE  
+ >GNSS Positioning Methods set according to the UE capabilities and test case;  
+ MEASUREMENT VALIDITY  
+ >UE state All states  
+ CHOICE REPORTING CRITERIA Periodical reporting criteria  
+ >Amount of reporting infinite (see Annex B);  
+ >Reporting interval 2 seconds (see Annex B);
+
+- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GNSS assistance data.
+- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b).
+- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GNSS MEASURED RESULTS* present in case of UE-assisted GNSS.
+- (g) – (i) The UE continues to provide RRC MEASUREMENT REPORT messages as in step (g) until the moving trajectory has been completed.
+
+NOTE: The UE may report error messages at step (f) until it has been able to acquire GNSS signals.
+
+# Annex E (normative): Assistance data required for testing
+
+## E.1 Introduction
+
+This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5.
+
+The information elements are given with reference to 3GPP TS 25.331 [14], where the details are defined.
+
+## E.2 GPS assistance data
+
+The GPS L1 C/A assistance data are as defined in 3GPP TS 25.171 [10], Annex E.
+
+## E.3 GANSS assistance data
+
+- a) **UE Positioning GANSS Reference Time IE.** This information element is defined in subclause 10.3.7.96o of 3GPP TS 25.331 [14].
+
+**Table E.3-1: GANSS reference time IE**
+
+| Name of the IE                      | Fields of the IE                   | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test |
+|-------------------------------------|------------------------------------|---------------------------------------------------|---------------------------------------|
+| UE Positioning GANSS Reference Time |                                    |                                                   |                                       |
+|                                     | GANSS Day                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD                          | Yes                                               | Yes                                   |
+|                                     | GANSS TOD Uncertainty              | Yes                                               | Yes                                   |
+|                                     | GANSS Time ID                      | Yes                                               | Yes                                   |
+|                                     | UTRAN GANSS Reference Time         |                                                   |                                       |
+|                                     | >UTRAN GANSS Timing of Cell Frames |                                                   | Yes                                   |
+|                                     | >CHOICE mode                       |                                                   | Yes                                   |
+|                                     | >>FDD                              |                                                   | Yes                                   |
+|                                     | >>>Primary CPICH Info              |                                                   | Yes                                   |
+|                                     | >SFN                               |                                                   | Yes                                   |
+|                                     | TUTRAN-GANSS Drift Rate            |                                                   | Yes                                   |
+
+- b) **UE Positioning GANSS Reference UE Position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [14].
+
+**Table E.3-2: GANSS reference location IE**
+
+| Name of the IE                             | Fields of the IE                                        |
+|--------------------------------------------|---------------------------------------------------------|
+| UE Positioning GANSS Reference UE Position | Ellipsoid point with Altitude and uncertainty ellipsoid |
+
+- c) **UE Positioning GANSS Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92a of 3GPP TS 25.331 [14].
+
+**Table E.3-3: GANSS ionospheric model IE**
+
+| Name of the IE                         | Fields of the IE |
+|----------------------------------------|------------------|
+| UE Positioning GANSS Ionospheric Model |                  |
+
+- d) **UE Positioning GANSS Additional Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92b of 3GPP TS 25.331 [14].
+
+**Table E.3-4: GANSS additional ionospheric model IE**
+
+| Name of the IE                                    | Fields of the IE |
+|---------------------------------------------------|------------------|
+| UE Positioning GANSS Additional Ionospheric Model |                  |
+
+- e) **UE Positioning GANSS Time Model IE.** This information element is only required for multi system tests, and is defined in subclause 10.3.7.97a of 3GPP TS 25.331 [14].
+
+**Table E.3-5: GANSS time model IE**
+
+| Name of the IE                  | Fields of the IE                                   |
+|---------------------------------|----------------------------------------------------|
+| UE Positioning GANSS Time Model |                                                    |
+|                                 | GNSS_TOD_ID<br>For each GNSS included in the test. |
+
+- f) **UE Positioning GANSS Navigation Model IE.** This information element is defined in subclause 10.3.7.94a of 3GPP TS 25.331 [14].
+
+**Table E.3-6: GANSS navigation model IE**
+
+| Name of the IE                        | Fields of the IE |
+|---------------------------------------|------------------|
+| UE Positioning GANSS Navigation Model |                  |
+
+- g) **UE Positioning GANSS Additional Navigation Models IE.** This information element is defined in subclause 10.3.7.94b of 3GPP TS 25.331 [14].
+
+**Table E.3-7: GANSS navigation model IE**
+
+| Name of the IE                        | Fields of the IE |
+|---------------------------------------|------------------|
+| UE Positioning GANSS Navigation Model |                  |
+
+**Table E.3-8: GANSS clock and orbit model choices**
+
+| GANSS               | Clock and Orbit Model Choice |
+|---------------------|------------------------------|
+| Galileo             | Model-1                      |
+| Modernized GPS      | Model-3                      |
+| GLONASS             | Model-4                      |
+| QZSS QZS-L1         | Model-2                      |
+| QZSS QZS-L1C/L2C/L5 | Model-3                      |
+| SBAS                | Model-5                      |
+| BDS                 | Model-6                      |
+
+- h) **UE Positioning GANSS Reference Measurement Information IE.** This information element is defined in subclause 10.3.7.88b of 3GPP TS 25.331 [14].
+
+**Table E.3-9: GANSS reference measurement information IE**
+
+| Name of the IE                                         | Fields of the IE                     |
+|--------------------------------------------------------|--------------------------------------|
+| UE Positioning GANSS Reference Measurement Information |                                      |
+|                                                        | SatID                                |
+|                                                        | Doppler (0 <sup>th</sup> order term) |
+|                                                        | Doppler (1 <sup>st</sup> order term) |
+|                                                        | Doppler Uncertainty                  |
+|                                                        | Code Phase                           |
+|                                                        | Integer Code Phase                   |
+|                                                        | Code Phase Search Window             |
+|                                                        | Azimuth                              |
+|                                                        | Elevation                            |
+
+- i) **UE Positioning GANSS Almanac IE.** This information element is defined in subclause 10.3.7.89a of 3GPP TS 25.331 [14].
+
+**Table E.3-10: GANSS almanac model IE**
+
+| Name of the IE               | Fields of the IE |
+|------------------------------|------------------|
+| UE Positioning GANSS Almanac |                  |
+
+**Table E.3-11: GANSS almanac choices**
+
+| GANSS               | Almanac Model Choice |
+|---------------------|----------------------|
+| Galileo             | Model-1              |
+| Modernized GPS      | Model-3,4            |
+| GLONASS             | Model-5              |
+| QZSS QZS-L1         | Model-2              |
+| QZSS QZS-L1C/L2C/L5 | Model-3,4            |
+| SBAS                | Model-6              |
+| BDS                 | Model-7              |
+
+- j) **UE Positioning GANSS UTC Model IE.** This information element is defined in subclause 10.3.7.97c of 3GPP TS 25.331 [14].
+
+**Table E.3-12: GANSS UTC model IE**
+
+| Name of the IE                 | Fields of the IE |
+|--------------------------------|------------------|
+| UE Positioning GANSS UTC Model |                  |
+
+- k) **UE Positioning GANSS Additional UTC Models IE.** This information element is defined in subclause 10.3.7.97d of 3GPP TS 25.331 [14].
+
+**Table E.3-13: GANSS additional UTC model IE**
+
+| Name of the IE                                | Fields of the IE |
+|-----------------------------------------------|------------------|
+| UE Positioning GANSS Additional UTC Models IE |                  |
+
+**Table E.3-14: GANSS UTC model choices**
+
+| <b>GANSS</b>        | <b>UTC Model Choice</b>        |
+|---------------------|--------------------------------|
+| Galileo             | UE Positioning GANSS UTC Model |
+| Modernized GPS      | Model-1                        |
+| GLONASS             | Model-2                        |
+| QZSS QZS-L1         | UE Positioning GANSS UTC Model |
+| QZSS QZS-L1C/L2C/L5 | Model-1                        |
+| SBAS                | Model-3                        |
+| BDS                 | Model-4                        |
+
+- I) UE Positioning GANSS Auxiliary Information IE.** This information element is defined in subclause 10.3.7.97f of 3GPP TS 25.331 [14].
+
+**Table E.3-15: GANSS auxiliary information IE**
+
+| <b>Name of the IE</b>                         | <b>Fields of the IE</b> |
+|-----------------------------------------------|-------------------------|
+| UE Positioning GANSS Auxiliary Information IE |                         |
+
+# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates ---
+
+## F.1 Introduction
+
+To convert the UE measurement reports in case of UE-assisted mode of A-GNSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [3], [4], [5], [6], [7], [8], [9], [19], [16] and [17].
+
+## --- F.2 UE measurement reports
+
+In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE (subclause 10.3.7.93a in 3GPP TS 25.331 [14]). In case the UE provides also measurements on the GPS L1 C/A signal, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [14]). The measurement parameters required for calculating the UE position are:
+
+- 1) Reference Time: The UE has two choices for the Reference Time:
+  - a) "UE GANSS Timing of Cell Frames" and/or "UE GPS Timing of Cell Frames";
+  - b) "GANSS TOD msec" and/or "GPS TOW msec" if GPS L1 C/A signal measurements are also provided.
+
+NOTE: It is not expected that an UE will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy.
+
+- 2) Measurement Parameters for each GANSS and GANSS Signal: 1 to <maxGANSSSat>:
+  - a) "Satellite ID"; mapping according to table 10.3.7.88b in 3GPP TS 25.331 [14];
+  - b) "GANSS Code Phase";
+  - c) "GANSS Integer Code Phase";
+  - d) "GANSS Integer Code Phase Extension";
+  - e) "Code Phase RMS Error";
+- 3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 1 to <maxSat>:
+  - a) "Satellite ID (SV PRN)";
+  - b) "Whole GPS chips";
+  - c) "Fractional GPS Chips";
+  - d) "Pseudorange RMS Error".
+
+Additional information required at the system simulator:
+
+- 1) "UE Positioning GANSS Reference UE Position" or "UE Positioning GPS Reference UE Position" (subclause 10.3.8.4c in 3GPP TS 25.331 [14]):  
+Used for initial approximate receiver coordinates.
+- 2) "UE Positioning GANSS Navigation Model" and "UE Positioning GANSS Additional Navigation Models" (subclauses 10.3.7.94a and 10.3.7.94b in 3GPP TS 25.331 [14]):
+
+Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections.
+
+- 3) "UE Positioning GANSS Ionospheric Model" (subclause 10.3.7.92a in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [7] for computation of the ionospheric delay.
+- 4) "UE Positioning GANSS Additional Ionospheric Model" (subclause 10.3.7.92b in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [6] for computation of the ionospheric delay.
+- 5) "UE Positioning GANSS Time Model" (subclause 10.3.7.97a in 3GPP TS 25.331 [14]):  
+Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "UE Positioning GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UE Positioning GPS UTC Model" (subclause 10.3.7.97 in 3GPP TS 25.331 [14]), "UE Positioning GANSS UTC Model" (subclause 10.3.7.97c in 3GPP TS 25.331 [14]), or "UE Positioning GANSS Additional UTC Models" (subclause 10.3.7.97d in 3GPP TS 25.331 [14]).
+- 6) "UE Positioning GPS Navigation Model" (subclause 10.3.7.94 in 3GPP TS 25.331 [14]):  
+Contains the GPS ephemeris and clock correction parameters as specified in [3]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements.
+- 7) "UE Positioning GPS Ionospheric Model" (subclause 10.3.7.92 in 3GPP TS 25.331 [14]):  
+Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [3] for computation of the ionospheric delay.
+
+## F.3 Weighted Least Squares (WLS) position solution
+
+The WLS position solution problem is concerned with the task of solving for four unknowns;  $x_u, y_u, z_u$  the receiver coordinates in a suitable frame of reference (usually ECEF) and  $b_u$  the receiver clock bias relative to the selected GNSS specific system time. It typically requires the following steps:
+
+### Step 1: Formation of pseudo-ranges
+
+The observation of code phase reported by the UE for each satellite  $SV_i$  is related to the pseudo-range/ $c$  modulo the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite  $SV_i$  at the time of measurement is calculated, and the integer number of milliseconds to be added to the UE code phase measurements is obtained.
+
+### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets
+
+In case the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator:
+
+$$\rho_{GNSS_m,i} \equiv \rho_{GNSS_m,i} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$
+
+where  $\rho_{GNSS_m,i}$  is the measured pseudo-range of satellite  $i$  of GNSS $_m$ . The system time  $t_{GNSS_k}$  of GNSS $_k$  is the reference time frame, and  $(t_{GNSS_k} - t_{GNSS_m})$  is the available GNSS-GNSS time offset, and  $c$  is the speed of light.
+
+### Step 3: Formation of weighting matrix
+
+The UE reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [16]. According to 3GPP TS 25.331 [14], the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa,  $X_i$  and a 3 bit exponent,  $Y_i$  for each  $SV_i$  of GNSS $_j$ :
+
+$$w_{GNSS_j,i} = RMSError = 0.5 \times \left(1 + \frac{X_i}{8}\right) 2^{Y_i}$$
+
+The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values:
+
+$$W = \text{diag}\{1/w_{\text{GNSS}_{1,1}}^2, 1/w_{\text{GNSS}_{1,2}}^2, \dots, 1/w_{\text{GNSS}_{1,n}}^2, \dots, 1/w_{\text{GNSS}_{m,1}}^2, 1/w_{\text{GNSS}_{m,2}}^2, \dots, 1/w_{\text{GNSS}_{m,l}}^2\}$$
+
+### Step 4: WLS position solution
+
+The WLS position solution is described in e.g., [16] and usually requires the following steps:
+
+- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed.
+- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS.
+- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [17] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model (see subclause F.2) adapted to the particular GNSS frequency.
+- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
+  - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report.
+  - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [16].
+  - c) Calculate difference between predicted and measured pseudo-ranges  $\Delta\rho$ .
+  - d) Calculate the "Geometry Matrix" **G** as defined in [16]:
+
+$$G \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{\text{GNSS}_{1,1}}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS}_{1,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{1,n}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,1}}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,l}}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{\text{GNSS}_{m,i}} \equiv \frac{\mathbf{r}_{\text{sGNSS}_{m,i}} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{\text{sGNSS}_{m,i}} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{\text{sGNSS}_{m,i}} \text{ is the satellite position vector for SV}_i \text{ of GNSS}_m \text{ (calculated in 1) above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$
+
+- e) Calculate the WLS solution according to [16]:
+
+$$\Delta\hat{\mathbf{x}} = (G^T W G)^{-1} G^T W \Delta\rho$$
+
+- f) Adding the  $\Delta\hat{\mathbf{x}}$  to the initial state estimate gives an improved estimate of the state vector:
+
+$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta\hat{\mathbf{x}}.$$
+
+- 5) This new state vector  $\hat{\mathbf{x}}$  can be used as new initial estimate and the procedure is repeated until the change in  $\hat{\mathbf{x}}$  is sufficiently small.
+
+### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system
+
+The state vector  $\hat{\mathbf{x}}$  calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates  $x_u, y_u, z_u$  to geodetic latitude  $\phi$ , longitude  $\lambda$  and altitude  $h$  on the WGS84 reference ellipsoid.
+
+### **Step 6: Calculation of "2-D Position Errors"**
+
+The latitude  $\varphi$  / longitude  $\lambda$  obtained after Step 5 is used to calculate the 2-D position error.
+

marked/Rel-17/25_series/25201/raw.md

@@ -0,0 +1,427 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                       |           |
+|-------------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                        | 4         |
+| 1 Scope.....                                                                                          | 5         |
+| 2 References.....                                                                                     | 5         |
+| 3 Abbreviations .....                                                                                 | 6         |
+| 4 General description of Layer 1.....                                                                 | 7         |
+| 4.1 Relation to other layers .....                                                                    | 7         |
+| 4.1.1 General Protocol Architecture .....                                                             | 7         |
+| 4.1.2 Service provided to higher layers .....                                                         | 7         |
+| 4.2 General description of Layer 1 .....                                                              | 8         |
+| 4.2.1 Multiple Access .....                                                                           | 8         |
+| 4.2.2 Channel coding and interleaving.....                                                            | 9         |
+| 4.2.3 Modulation and spreading .....                                                                  | 9         |
+| 4.2.4 Physical layer procedures .....                                                                 | 9         |
+| 4.2.5 Physical layer measurements.....                                                                | 10        |
+| 4.2.6 Relationship of the physical layer functions .....                                              | 10        |
+| 5 Document structure of physical layer specification.....                                             | 11        |
+| 5.1 Overview .....                                                                                    | 11        |
+| 5.2 TS 25.201: Physical layer – General description .....                                             | 11        |
+| 5.3 TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD) ..... | 11        |
+| 5.4 TS 25.212: Multiplexing and channel coding (FDD) .....                                            | 11        |
+| 5.5 TS 25.213: Spreading and modulation (FDD) .....                                                   | 12        |
+| 5.6 TS 25.214: Physical layer procedures (FDD) .....                                                  | 12        |
+| 5.7 TS 25.215: Physical layer – Measurements (FDD).....                                               | 12        |
+| 5.8 TS 25.221: Physical channels and mapping of transport channels onto physical channels (TDD) ..... | 12        |
+| 5.9 TS 25.222: Multiplexing and channel coding (TDD) .....                                            | 13        |
+| 5.10 TS 25.223: Spreading and modulation (TDD).....                                                   | 13        |
+| 5.11 TS 25.224: Physical layer procedures (TDD) .....                                                 | 13        |
+| 5.12 TS 25.225: Physical layer – Measurements (TDD) .....                                             | 13        |
+| 5.13 TR 25.833: Physical layer items not for inclusion in Release '99.....                            | 13        |
+| 5.14 TR 25.944: Channel coding and multiplexing examples .....                                        | 13        |
+| <b>Annex A (informative): Preferred mathematical notations .....</b>                                  | <b>14</b> |
+| Annex B (informative): Change history.....                                                            | 15        |
+
+# --- Foreword
+
+This Technical Specification (TS) 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 describes a general description of the physical layer of the UTRA radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 25.200 series. The TS 25.200 series specifies the Uu point for the 3G mobile system, and defines the minimum level of specifications required for basic connections in terms of mutual connectivity and compatibility.
+
+# --- 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 TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".
+- [2] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
+- [3] 3GPP TS 25.213: "Spreading and modulation (FDD)".
+- [4] 3GPP TS 25.214: "Physical layer procedures (FDD)".
+- [5] 3GPP TS 25.215: "Physical layer – Measurements (FDD)".
+- [6] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
+- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)".
+- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)".
+- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)".
+- [10] 3GPP TS 25.225: "Physical layer – Measurements (TDD)".
+- [11] 3GPP TR 25.833: "Physical layer items not for inclusion in Release '99".
+- [12] 3GPP TR 25.944: "Channel coding and multiplexing examples".
+- [13] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [14] 3GPP TS 25.302: "Services provided by the physical layer".
+- [15] 3GPP TS 25.101: "UE Radio transmission and reception (FDD)".
+- [16] 3GPP TS 25.102: "UE Radio transmission and reception (TDD)".
+- [17] 3GPP TS 25.104: "BTS Radio transmission and reception (FDD)".
+- [18] 3GPP TS 25.105: "BTS Radio transmission and reception (TDD)".
+
+# 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                               |
+|---------|-----------------------------------------------|
+| 16QAM   | 16 Quadrature Amplitude Modulation            |
+| 64QAM   | 64 Quadrature Amplitude Modulation            |
+| ARQ     | Automatic Repeat Request                      |
+| BER     | Bit Error Rate                                |
+| CCTrCH  | Coded Composite Transport Channel             |
+| DCA     | Dynamic channel allocation                    |
+| DCH     | Dedicated Channel                             |
+| DS-CDMA | Direct-Sequence Code Division Multiple Access |
+| DSCH    | Downlink Shared Channel                       |
+| DwPCH   | Downlink Pilot Channel                        |
+| DwPTS   | Downlink Pilot Time Slot                      |
+| E-DCH   | Enhanced Dedicated Channel                    |
+| E-HICH  | E-DCH Hybrid ARQ Indicator Channel            |
+| E-RGCH  | E-DCH Relative Grant Channel                  |
+| FDD     | Frequency Division Duplex                     |
+| FEC     | Forward Error Correction                      |
+| FER     | Frame Error Rate                              |
+| GSM     | Global System for Mobile Communication        |
+| HS-DSCH | High Speed Downlink Shared channel            |
+| HS-SCCH | HS-DSCH Shared Control Channel                |
+| L1      | Layer 1 (physical layer)                      |
+| L2      | Layer 2 (data link layer)                     |
+| L3      | Layer 3 (network layer)                       |
+| LAC     | Link Access Control                           |
+| MAC     | Medium Access Control                         |
+| MBSFN   | MBMS over a Single Frequency Network          |
+| Mcps    | Mega Chip Per Second                          |
+| MIMO    | Multiple Input Multiple Output                |
+| QPSK    | Quaternary Phase Shift Keying                 |
+| RACH    | Random Access Channel                         |
+| RF      | Radio Frequency                               |
+| RLC     | Radio Link Control                            |
+| RRC     | Radio Resource Control                        |
+| SAP     | Service Access Point                          |
+| SCH     | Synchronisation Channel                       |
+| SIR     | Signal-to-Interference Ratio                  |
+| TDD     | Time Division Duplex                          |
+| TDMA    | Time Division Multiple Access                 |
+| TFCI    | Transport-Format Combination Indicator        |
+| UE      | User Equipment                                |
+| UMTS    | Universal Mobile Telecommunications System    |
+| UpPTS   | Uplink Pilot Time Slot                        |
+| UpPCH   | Uplink Pilot Channel                          |
+| UTRA    | UMTS Terrestrial Radio Access                 |
+| UTRAN   | UMTS Terrestrial Radio Access Network         |
+| WCDMA   | Wide-band Code Division Multiple Access       |
+
+# 4 General description of Layer 1
+
+## 4.1 Relation to other layers
+
+### 4.1.1 General Protocol Architecture
+
+Radio interface which is prescribed by this specification means the Uu point between User Equipment (UE) and network. The radio interface is composed of Layers 1, 2 and 3. Layer 1 is based on WCDMA/TD-SCDMA technology
+
+and the TS 25.200 series describes the Layer-1 specification. Layers 2 and 3 of the radio interface are described in the TS 25.300 series.
+
+![Figure 1: Radio interface protocol architecture around the physical layer. The diagram shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). A vertical line on the left labeled 'Control / Measurements' connects Layer 3 and Layer 1. Layer 2 contains 'Logical channels' above the MAC block and 'Transport channels' below the MAC block. The Physical layer is at the bottom, connected to the MAC block via a circle representing a Service Access Point (SAP).](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg)
+
+Figure 1: Radio interface protocol architecture around the physical layer. The diagram shows three layers: Layer 3 (Radio Resource Control (RRC)), Layer 2 (Medium Access Control), and Layer 1 (Physical layer). A vertical line on the left labeled 'Control / Measurements' connects Layer 3 and Layer 1. Layer 2 contains 'Logical channels' above the MAC block and 'Transport channels' below the MAC block. The Physical layer is at the bottom, connected to the MAC block via a circle representing a Service Access Point (SAP).
+
+**Figure 1: Radio interface protocol architecture around the physical layer**
+
+Figure 1 shows the UTRA radio interface protocol architecture around the physical layer (Layer 1). The physical layer interfaces the Medium Access Control (MAC) sub-layer of Layer 2 and the Radio Resource Control (RRC) Layer of Layer 3. The circles between different layer/sub-layers indicate Service Access Points (SAPs). The physical layer offers different Transport channels to MAC. A transport channel is characterized by how the information is transferred over the radio interface. MAC offers different Logical channels to the Radio Link Control (RLC) sub-layer of Layer 2. A logical channel is characterized by the type of information transferred. Physical channels are defined in the physical layer. There are two duplex modes: Frequency Division Duplex (FDD) and Time Division Duplex (TDD). In the FDD mode a physical channel is characterized by the code, frequency and in the uplink the relative phase (I/Q); in addition E-HICH and E-RGCH are also defined by a specific orthogonal signature sequence. In the TDD mode the physical channels are also characterized by the timeslot and additionally, the E-HICH is further defined by a specific orthogonal signature sequence. For 1.28Mcps TDD, the E-HICH can be also further defined by a group of orthogonal signature sequences. The physical layer is controlled by RRC.
+
+### 4.1.2 Service provided to higher layers
+
+The physical layer offers data transport services to higher layers. The access to these services is through the use of transport channels via the MAC sub-layer. The physical layer is expected to perform the following functions in order to provide the data transport service. See also TS 25.302:
+
+- Macrodiversity distribution/combining and soft handover execution.
+- Error detection on transport channels and indication to higher layers.
+- FEC encoding/decoding of transport channels.
+- Multiplexing of transport channels and demultiplexing of coded composite transport channels (CCTrCHs).
+- Rate matching of coded transport channels to physical channels.
+- Mapping of coded composite transport channels on physical channels.
+- Power weighting and combining of physical channels.
+- Modulation and spreading/demodulation and despreading of physical channels.
+- Frequency and time (chip, bit, slot, frame) synchronisation.
+- Radio characteristics measurements including FER, SIR, Interference Power, etc., and indication to higher layers.
+- Inner - loop power control.
+- RF processing. (Note: RF processing is defined in TS 25.100 series).
+- synchronization shift control
+
+- Beamforming
+- MIMO transmission
+- Hybrid ARQ soft-combining for HS-DSCH and E-DCH
+
+When network elements (UEs and network) provide compatible service bearers (for example support a speech bearer) they should be assured of successful interworking. Moreover, different implementation options of the same (optional) feature would lead to incompatibility between UE and network. Therefore, this shall be avoided.
+
+## 4.2 General description of Layer 1
+
+### 4.2.1 Multiple Access
+
+The access scheme is Direct-Sequence Code Division Multiple Access (DS-CDMA) with information either spread over approximately 5 MHz (FDD and 3.84 Mcps TDD) bandwidth, thus also often denoted as Wideband CDMA (WCDMA) due that nature, 10MHz (7.68 Mcps TDD) bandwidth, or 1.6MHz (1.28Mcps TDD), thus also often denoted as Narrowband CDMA. UTRA has two modes, FDD (Frequency Division Duplex) & TDD (Time Division Duplex), for operating with paired and unpaired bands respectively. The possibility to operate in either FDD or TDD mode allows for efficient utilisation of the available spectrum according to the frequency allocation in different regions. FDD and TDD modes are defined as follows:
+
+FDD: A duplex method whereby uplink and downlink transmissions use two separated radio frequencies. In the FDD, each uplink and downlink uses the different frequency band. A pair of frequency bands which have specified separation shall be assigned for the system.
+
+TDD: A duplex method whereby uplink and downlink transmissions are carried over same radio frequency by using synchronised time intervals. In the TDD, time slots in a physical channel are divided into transmission and reception part. Information on uplink and downlink are transmitted reciprocally.
+
+UTRA TDD has three options, the 3.84Mcps option and the 1.28Mcps option, the 7.68Mcps TDD option. In UTRA TDD there is TDMA component in the multiple access in addition to DS-CDMA. Thus the multiple access has been also often denoted as TDMA/CDMA due to the added TDMA nature.
+
+A 10 ms radio frame is divided into 15 slots (2560 chip/slot at the chip rate 3.84 Mcps). A physical channel is therefore defined as a code (or number of codes) and additionally in TDD mode the sequence of time slots completes the definition of a physical channel. In FDD, for HS-DSCH, E-DCH and associated signalling channels, 2ms sub-frames consisting of 3 slots are defined.
+
+The information rate of the channel varies with the symbol rate being derived from the 3.84 Mcps chip rate and the spreading factor. Spreading factors are from 256 to 2 with FDD uplink, from 512 to 4 with FDD downlink, and from 16 to 1 for TDD uplink and downlink. Thus the respective modulation symbol rates vary from 1920 k symbols/s to 15 k symbols/s (7.5 k symbols/s) for FDD uplink (downlink), and for TDD the momentary modulation symbol rates shall vary from 3.84 M symbols/s to 240 k symbols/s.
+
+For the 7.68Mcps TDD option, a 10 ms radio frame is divided into 15 slots (5120 chip/slot). A physical channel is therefore defined as a code (or number of codes) and the sequence of time slots.
+
+The information rate of the channel varies with the symbol rate being derived from the 7.68 Mcps chip rate and the spreading factor. Spreading factors are from 32 to 1 for both uplink and downlink. Thus the respective modulation symbol rates vary from 7.68 M symbols/s to 240 k symbols/s.
+
+For 1.28Mcps TDD option, a 10 ms radio frame is divided into two 5ms sub-frames. In each sub-frame, there are 7 normal time slots and 3 special time slots. Note that in case of entire carrier dedicated to MBSFN there are 7 normal MBSFN Traffic time slots and 1 short MBSFN Special time slot in each sub-frame. A basic physical channel is therefore characterised by the frequency, code and time slot.
+
+The information rate of the channel varies with the symbol rate being derived from the 1.28 Mcps chiprate and the spreading factor. Spreading factors is from 16 to 1 for both uplink and downlink. Thus the respective modulation symbol rates shall vary from 80.0K symbols/s to 1.28M symbols/s.
+
+### 4.2.2 Channel coding and interleaving
+
+For the channel coding in UTRA two options are supported for FDD and three options are supported for TDD:
+
+- Convolutional coding.
+- Turbo coding.
+- No coding (only TDD).
+
+Channel coding selection is indicated by higher layers. In order to randomise transmission errors, bit interleaving is performed further.
+
+### 4.2.3 Modulation and spreading
+
+The UTRA modulation scheme is QPSK (8PSK is also used for 1.28Mcps TDD option). For HS-DSCH transmission, 16QAM and 64QAM can also be used. 16QAM and 64QAM are further supported for E-DCH transmission, and 16QAM is supported for MBSFN<sup>1</sup> FACH transmissions. Pulse shaping is specified in the TS 25.100 series.
+
+With CDMA nature the spreading (& scrambling) process is closely associated with modulation. In UTRA different families of spreading codes are used to spread the signal:
+
+- For separating channels from same source, channelisation codes derived with the code tree structure as given in TS 25.213 and 25.223 are used.
+- For separating different cells the following solutions are supported.
+- FDD mode: Gold codes with 10 ms period (38400 chips at 3.84 Mcps) used, with the actual code itself length  $2^{18}-1$  chips, as defined in TS 25.213.
+- TDD mode: for the 3.84Mcps and 1.28Mcps TDD options, scrambling codes with the length 16 are used as defined in TS 25.223; for the 7.68Mcps TDD option, scrambling codes with length 32 are used.
+- For separating different UEs the following code families are defined.
+- FDD mode: Gold codes with 10 ms period, or alternatively S(2) codes 256 chip period.
+- TDD mode: for the 3.84Mcps and 1.28Mcps TDD options, codes with period of 16 chips and midamble sequences of different length depending on the environment; for the 7.68Mcps TDD option, codes with period of 32 chips and midamble sequences of different length depending on the environment.
+
+### 4.2.4 Physical layer procedures
+
+There are several physical layer procedures involved with UTRA operation. Such procedures covered by physical layer description are:
+
+- 1) The power control, inner loop for FDD mode, and for the 3.84Mcps TDD and 7.68Mcps TDD options open loop in uplink and inner loop in downlink, for 1.28Mcps TDD option, open loop in uplink and inner loop in both uplink and downlink.
+- 2) Cell search operation.
+- 3) Uplink synchronization control with open and closed loop.
+- 4) Random access
+- 5) Procedures related to HS-DSCH transmission, including HS-SCCH less operation and MIMO transmission.
+- 6) Procedures related to E-DCH transmission, including MIMO transmission.
+- 7) Procedures related to discontinuous transmission and reception.
+
+---
+
+<sup>1</sup> MBSFN transmission is characterised by a group of synchronised base stations transmitting the same wave form by using a common scrambling code
+
+### 4.2.5 Physical layer measurements
+
+Radio characteristics including FER, SIR, Interference power, etc., are measured and reported to higher layers and network. Such measurements are:
+
+- 1) Handover measurements for handover within UTRA. Specific features being determined in addition to the relative strength of the cell, for the FDD mode the timing relation between for cells for support of asynchronous soft handover.
+- 2) The measurement procedures for preparation for handover to GSM900/GSM1800.
+- 3) The measurement procedures for UE before random access process.
+- 4) The measurement procedures for Dynamic Channel Allocation (DCA) of TDD mode.
+- 5) UTRAN measurements.
+
+### 4.2.6 Relationship of the physical layer functions
+
+The functionality of the layer 1 is split over several specifications each for FDD and TDD. The following figures, although not categorical, show as an introduction the relationship of layer 1 functions by specification in terms of users plane information flow.
+
+![Diagram of FDD layer 1 functions relationships by specification](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+This diagram illustrates the functional relationships for FDD layer 1. It features five rectangular blocks. At the top left is '25.214 procedures', which has a dashed downward arrow to '25.211' and a dashed rightward arrow to '25.213' labeled 'control'. To the top right is '25.215 measurements', which has a dashed downward arrow to '25.213'. Below '25.211' is '25.212', which receives 'traffic' from the left and has a solid rightward arrow to '25.213'. '25.213' has a solid rightward arrow pointing out of the diagram.
+
+Diagram of FDD layer 1 functions relationships by specification
+
+Figure 2 - FDD layer 1 functions relationships by specification
+
+![Diagram of TDD layer 1 functions relationships by specification](b0211cee4b20034939d883ac0d70f696_img.jpg)
+
+This diagram illustrates the functional relationships for TDD layer 1. It features five rectangular blocks. At the top left is '25.224 procedures', which has a dashed downward arrow to '25.221' and a dashed rightward arrow to '25.223' labeled 'control'. To the top right is '25.225 measurements', which has a dashed downward arrow to '25.223'. Below '25.221' is '25.222', which receives 'traffic' from the left and has a solid rightward arrow to '25.223'. '25.223' has a solid rightward arrow pointing out of the diagram.
+
+Diagram of TDD layer 1 functions relationships by specification
+
+Figure 3 - TDD layer 1 functions relationships by specification
+
+# --- 5 Document structure of physical layer specification
+
+## 5.1 Overview
+
+The physical layer specification consists of a general document (TS 25.201), five FDD mode documents (TS 25.211 through 25.215), five TDD mode documents (TS 25.221 through 25.225). In addition, there are two technical reports (TR 25.833 and 25.944).
+
+## 5.2 TS 25.201: Physical layer – General description
+
+The scope is to describe:
+
+- the contents of the Layer 1 documents (TS 25.200 series);
+- where to find information;
+- a general description of Layer 1.
+
+## 5.3 TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD)
+
+The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the FDD mode, and to specify:
+
+- the different transport channels that exist;
+- which physical channels exist;
+- what is the structure of each physical channel, slot format etc.;
+- relative timing between different physical channels in the same link, and relative timing between uplink and downlink;
+- mapping of transport channels onto the physical channels.
+
+## 5.4 TS 25.212: Multiplexing and channel coding (FDD)
+
+The scope is to describe multiplexing, channel coding and interleaving in the FDD mode, and to specify:
+
+- coding and multiplexing of transport channels into CCTrCHs;
+- channel coding alternatives;
+- coding for Layer 1 control information, such as TFCI;
+- the different interleavers;
+- how is rate matching done;
+- physical channel segmentation and mapping.
+
+## 5.5 TS 25.213: Spreading and modulation (FDD)
+
+The scope is to establish the characteristics of the spreading and modulation in the FDD mode, and to specify:
+
+- the spreading (channelisation plus scrambling);
+- generation of channelisation and scrambling codes;
+- generation of RACH preamble codes;
+- generation of SCH synchronisation codes;
+
+- modulation.
+
+RF channel arrangements and Pulse shaping are specified in TS 25.101 for UE and in TS 25.104 for Node-B.
+
+## 5.6 TS 25.214: Physical layer procedures (FDD)
+
+The scope is to establish the characteristics of the physical layer procedures in the FDD mode, and to specify:
+
+- cell search procedures;
+- power control procedures;
+- random access procedure.
+
+## 5.7 TS 25.215: Physical layer – Measurements (FDD)
+
+The scope is to establish the characteristics of the physical layer measurements in the FDD mode, and to specify:
+
+- the measurements that Layer 1 is to perform;
+- reporting of measurements to higher layers and network;
+- handover measurements, idle-mode measurements etc.
+
+## 5.8 TS 25.221: Physical channels and mapping of transport channels onto physical channels (TDD)
+
+The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the TDD mode, and to specify:
+
+- transport channels;
+- physical channels, structure and contents;
+- mapping of transport channels onto the physical channels.
+
+## 5.9 TS 25.222: Multiplexing and channel coding (TDD)
+
+The scope is to describe multiplexing, channel coding and interleaving in the TDD mode, and to specify:
+
+- channel coding and multiplexing of transport channels into CCTrCHs;
+- channel coding alternatives;
+- coding for Layer 1 control information, such as TFCI;
+- interleaving;
+- rate matching;
+- physical channel segmentation and mapping.
+
+## 5.10 TS 25.223: Spreading and modulation (TDD)
+
+The scope is to establish the characteristics of the spreading and modulation in the TDD mode, and to specify:
+
+- data modulation;
+- spreading;
+- generation of synchronisation codes.
+
+RF channel arrangements and Pulse shaping are specified in TS 25.102 for UE and in TS 25.105 for Node-B.
+
+## 5.11 TS 25.224: Physical layer procedures (TDD)
+
+The scope is to establish the characteristics of the physical layer procedures in the TDD mode, and to specify:
+
+- cell synchronisation;
+- timing advance;
+- power control procedures;
+- idle mode tasks.
+
+## 5.12 TS 25.225: Physical layer – Measurements (TDD)
+
+The scope is to establish the characteristics of the physical layer measurements in the TDD mode, and to specify:
+
+- the measurements that Layer 1 is to perform;
+- reporting of measurements to higher layers and network;
+- handover measurements, idle-mode measurements etc.
+
+## 5.13 TR 25.833: Physical layer items not for inclusion in Release '99
+
+The scope is to collect materials on UTRA physical layer items not included in the Release '99 specification documents, such as DSCH control channel, FAUSCH, Hybrid ARQ, 4-state SCCC turbo coding and ODMA.
+
+## 5.14 TR 25.944: Channel coding and multiplexing examples
+
+The scope is to describe examples of channel coding and multiplexing for transport channels of various types and cases.
+
+# Annex A (informative): Preferred mathematical notations
+
+The following table contains the preferred mathematical notations used in L1 documentation.
+
+| Item                                                                            | Notation                                                                                                                                                     |
+|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| multiply product                                                                | cross sign, e.g. $a \times b$                                                                                                                                |
+| matrix product                                                                  | dot sign, e.g. $a \cdot b$                                                                                                                                   |
+| scalar product (product of a matrix by a scalar)                                | dot sign, scalar should precede matrix<br>$(1 + j) \cdot \begin{bmatrix} u \\ v \end{bmatrix}$ e.g.                                                          |
+| matrix dimensioning                                                             | number of rows $\times$ number of column, e.g.:<br>$R \times C$                                                                                              |
+| Kronecker product                                                               | $a \otimes b$                                                                                                                                                |
+| bracketing of sets (all elements of same type, not ordered elements)            | curly brackets $\{ \}$ , e.g.<br>$\{a_i\}_{i \in \{1, 2, \dots, p\}}$ $\{a_1, a_2, \dots, a_p\}$ , or                                                        |
+| bracketing of lists (all elements not necessary of same type, ordered elements) | round brackets (), e.g. $(A, u, x)$                                                                                                                          |
+| bracketing of sequences (all elements of same type, ordered elements)           | angle brackets, e.g. $\langle a_1, a_2, \dots, a_p \rangle$ or<br>$\langle a_i \rangle_{i \in \{1, 2, \dots, p\}}$                                           |
+| bracketing of function argument                                                 | round brackets, e.g. $f(x)$                                                                                                                                  |
+| bracketing of array index                                                       | square brackets, e.g. $a[x]$                                                                                                                                 |
+| bracketing of matrix or vector                                                  | square brackets [], e.g. $\begin{bmatrix} x \\ y \end{bmatrix}$ , $\begin{bmatrix} x & y \end{bmatrix}$ , or $\begin{bmatrix} 1 & 1 \\ 1 & -1 \end{bmatrix}$ |
+| Separation of indexes                                                           | use a comma : e.g. $N_{i,j}$                                                                                                                                 |
+| use of italic for symbols                                                       | a symbol should be either in italic or in normal font, but mixing up should be avoided.                                                                      |
+| bracketing of arithmetic expression to force precedence of operations           | round brackets : e.g. $(a + b) \times c$                                                                                                                     |
+| necessity of bracketing arithmetic expressions                                  | When only + and $\times$ bracketing is not necessary. When the mod operator is used explicit bracketing of mod operands and possibly result should be done.  |
+| number type                                                                     | in a context of non negative integer numbers, some notes should stress when a number is signed, or possibly fractional.                                      |
+| binary xor and and                                                              | respectively use + or $\cdot$ . If no "mod 2" is explicitly in the expression some text should stress that the operation is modulo 2.                        |
+| matrix or vector transpose                                                      | $v^T$                                                                                                                                                        |
+| $1 \times 1$ matrices                                                           | implicitly cast to its unique element.                                                                                                                       |
+| vector dot product                                                              | $u^T \cdot v$ for column vectors, and $u \cdot v^T$ for line vectors                                                                                         |
+| complex conjugate                                                               | $v^*$                                                                                                                                                        |
+| matrix or vector Hermitian transpose                                            | $v^H$                                                                                                                                                        |
+| real part and imaginary part of complex numbers.                                | $\text{Re}(x)$ and $\text{Im}(x)$                                                                                                                            |
+

marked/Rel-17/25_series/25202/raw.md

@@ -0,0 +1,981 @@
+
+
+
+
+
+
+# Contents
+
+|                                                               |    |
+|---------------------------------------------------------------|----|
+| Foreword .....                                                | 5  |
+| 1 Scope.....                                                  | 6  |
+| 2 References.....                                             | 6  |
+| 3 Definitions, symbols and abbreviations .....                | 6  |
+| 3.1 Definitions.....                                          | 6  |
+| 3.2 Symbols.....                                              | 7  |
+| 3.3 Abbreviations .....                                       | 7  |
+| 4 Background and introduction.....                            | 7  |
+| 5 Requirements .....                                          | 8  |
+| 6 Physical layer structure .....                              | 8  |
+| 6.0 Services offered to higher layers.....                    | 8  |
+| 6.1 Frame structure.....                                      | 8  |
+| 6.2 Burst structure .....                                     | 8  |
+| 6.3 Midambles.....                                            | 9  |
+| 6.4 Coding and Modulation.....                                | 12 |
+| 6.5 Scrambling Codes .....                                    | 12 |
+| 6.6 Synchronisation Codes.....                                | 13 |
+| 6.7 Transmit diversity .....                                  | 13 |
+| 6.9 Indicator Channels.....                                   | 13 |
+| 6.9.1 Paging Indicator Channel (PICH) .....                   | 13 |
+| 6.9.2 MBMS Indicator Channel (MICH).....                      | 13 |
+| 6.10 Mapping of transport channels to physical channels ..... | 13 |
+| 7 Physical layer procedures.....                              | 15 |
+| 7.1 Power Control .....                                       | 15 |
+| 7.2 Timing Advance.....                                       | 15 |
+| 7.3 HSDPA procedures .....                                    | 15 |
+| 7.4 Synchronisation procedures .....                          | 15 |
+| 7.5 RACH procedures .....                                     | 15 |
+| 7.6 Discontinuous transmission (DTX) procedure.....           | 15 |
+| 7.7 Downlink transmit diversity procedure.....                | 15 |
+| 7.8 DSCH procedure .....                                      | 15 |
+| 7.9 Macrodiversity procedure .....                            | 15 |
+| 7.10 IPDL procedure .....                                     | 16 |
+| 7.11 E-DCH procedures .....                                   | 16 |
+| 8 UE capabilities .....                                       | 16 |
+| 9 Layer 2/3 protocol aspects .....                            | 16 |
+| 9.1 Protocol architecture .....                               | 16 |
+| 9.2 Signalling .....                                          | 16 |
+| 9.2.1 General .....                                           | 16 |
+| 9.2.2 L2/MAC differences.....                                 | 16 |
+| 9.2.3 L2/RRC differences.....                                 | 16 |
+| 9.3 HSDPA related issues .....                                | 17 |
+| 9.4 Mobility.....                                             | 17 |
+| 9.5 Idle Mode Procedures.....                                 | 17 |
+| 9.6 E-DCH related issues .....                                | 17 |
+| 10 Iub/Iur aspects .....                                      | 17 |
+| 10.1 Impacts on Iub/Iur interfaces – general aspects .....    | 17 |
+| 10.1.1 Timing advance and Rx Timing Deviation .....           | 17 |
+| 10.1.2 Paging .....                                           | 18 |
+| 10.1.3 DSCH Power Control from the RNC .....                  | 18 |
+| 10.2 Impacts on Iub/Iur control plane protocols .....         | 18 |
+| 10.3 Impacts on Iub/Iur user plane protocols .....            | 18 |
+
+|                        |                                                     |    |
+|------------------------|-----------------------------------------------------|----|
+| 11                     | Radio aspects.....                                  | 19 |
+| 11.1                   | UE radio transmission and reception .....           | 19 |
+| 11.1.1                 | Transmitter characteristics.....                    | 19 |
+| 11.1.1.1               | Transmit power .....                                | 19 |
+| 11.1.1.2               | Output RF spectrum emissions .....                  | 19 |
+| 11.1.1.2.1             | Occupied bandwidth.....                             | 19 |
+| 11.1.1.2.2             | Out of band emission.....                           | 19 |
+| 11.1.1.2.2.1           | Spectrum emission mask .....                        | 19 |
+| 11.1.1.2.2.2           | Adjacent Channel Leakage power Ratio (ACLR).....    | 20 |
+| 11.1.1.2.2.3           | Spurious emissions .....                            | 20 |
+| 11.1.2                 | Receiver characteristics .....                      | 20 |
+| 11.1.2.1               | Reference sensitivity level.....                    | 20 |
+| 11.1.2.1.1             | Minimum Requirement .....                           | 20 |
+| 11.1.2.2               | Adjacent Channel Selectivity (ACS) .....            | 20 |
+| 11.1.2.2.1             | Minimum Requirement .....                           | 20 |
+| 11.1.2.3               | Blocking characteristics .....                      | 21 |
+| 11.1.2.3.1             | Minimum Requirement .....                           | 21 |
+| 11.1.2.4               | Spurious response .....                             | 22 |
+| 11.1.2.4.1             | Minimum Requirement .....                           | 22 |
+| 11.1.2.5               | Spurious emissions .....                            | 22 |
+| 11.1.2.5.1             | Minimum Requirement .....                           | 23 |
+| 11.2                   | Base station radio transmission and reception ..... | 23 |
+| 11.2.1                 | Transmitter characteristics.....                    | 23 |
+| 11.2.1.1               | Base station output power.....                      | 23 |
+| 11.2.1.2               | Output RF spectrum emissions .....                  | 23 |
+| 11.2.1.2.1             | Occupied bandwidth.....                             | 23 |
+| 11.2.1.2.2             | Out of band emission.....                           | 23 |
+| 11.2.1.2.2.1           | Spectrum emission mask .....                        | 23 |
+| 11.2.1.2.2.2           | Adjacent Channel Leakage power Ratio (ACLR).....    | 25 |
+| 11.2.1.2.2.2.1         | Minimum requirement .....                           | 25 |
+| 11.2.1.2.2.3           | Spurious emissions .....                            | 26 |
+| 11.2.2                 | Receiver characteristics .....                      | 26 |
+| 11.2.2.1               | Reference sensitivity level.....                    | 26 |
+| 11.2.2.1.1             | Minimum requirement.....                            | 26 |
+| 11.2.2.2               | Adjacent Channel Selectivity (ACS) .....            | 26 |
+| 11.2.2.2.1             | Minimum requirement.....                            | 26 |
+| 11.2.2.3               | Blocking characteristics .....                      | 27 |
+| 11.2.2.3.1             | Minimum requirement.....                            | 27 |
+| 11.2.2.3.2             | Collocation with GSM900 and/or DCS 1800 .....       | 28 |
+| 11.2.2.4               | Spurious emissions .....                            | 28 |
+| 11.2.2.4.1             | Minimum requirement.....                            | 29 |
+| Annex A (informative): | Change history.....                                 | 30 |
+
+# --- Foreword
+
+This Technical Specification 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 overall technical specification for the support of the 7.68Mcps TDD option in UTRA.
+
+# --- 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 25.895 (V6.0.0): "Analysis of higher chip rates for UTRA TDD evolution".
+- [2] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
+- [3] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)".
+- [4] 3GPP TS 25.223: "Spreading and modulation (TDD)".
+- [5] 3GPP TS 25.224: "Physical layer procedures (TDD)".
+- [6] 3GPP TS 25.225: "Physical layer; Measurements (TDD)".
+- [7] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [8] 3GPP TS 25.306: "UE Radio Access capabilities".
+- [9] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification".
+- [10] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [11] 3GPP TS 25.105 "UTRAN (BS) TDD; Radio transmission and reception".
+- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [12] 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 [12].
+
+(void)
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+(void)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [12] 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 [12].
+
+|          |                                                      |
+|----------|------------------------------------------------------|
+| BCH      | Broadcast Channel                                    |
+| CCPCH    | Common Control Physical Channel                      |
+| DCH      | Dedicated Channel                                    |
+| DPCH     | Dedicated Physical Channel                           |
+| DSCH     | Downlink Shared Channel                              |
+| E-AGCH   | E-DCH Absolute Grant Channel                         |
+| E-DCH    | Enhanced Dedicated Channel                           |
+| E-HICH   | E-DCH Hybrid ARQ Indicator Channel                   |
+| E-PUCH   | E-DCH Physical Uplink Channel                        |
+| E-RUCCH  | E-DCH Random Access Uplink Control Channel           |
+| FACH     | Forward Access Channel                               |
+| HS-DSCH  | High Speed Downlink Shared Channel                   |
+| HS-PDSCH | High Speed Physical Downlink Shared Channel          |
+| HS-SCCH  | Shared Control Channel for HS-DSCH                   |
+| HS-SICH  | Shared Information Channel for HS-DSCH               |
+| P-CCPCH  | Primary CCPCH                                        |
+| PCH      | Paging Channel                                       |
+| PDSCH    | Physical Downlink Shared Channel                     |
+| PI       | Paging Indicator (value calculated by higher layers) |
+| PICH     | Page Indicator Channel                               |
+| PRACH    | Physical Random Access Channel                       |
+| PUSCH    | Physical Uplink Shared Channel                       |
+| RACH     | Random Access Channel                                |
+| S-CCPCH  | Secondary CCPCH                                      |
+| SCH      | Synchronisation Channel                              |
+| TrCH     | Transport Channel                                    |
+| USCH     | Uplink Shared Channel                                |
+
+# --- 4 Background and introduction
+
+The 7.68Mcps TDD option is an evolution of the 3.84Mcps TDD option to a higher chip rate. There exists a great degree of commonality between the 3.84Mcps TDD option and the 7.68Mcps TDD option. Nevertheless, there are many aspects of the 7.68Mcps TDD option that require separate specification to the 3.84Mcps TDD option. The following aspects are specified at a high level in this document:
+
+- Physical layer structure;
+- Physical layer procedures;
+- UE capabilities;
+- Layer 2/3 protocol aspects;
+- Iub / Iur aspects;
+- Radio aspects;
+
+# 5 Requirements
+
+- The 7.68Mcps TDD option shall provide significant enhancements in terms of user experience (throughput and delay) and/or capacity (at least to the extent shown in [1]).
+- Full mobility shall be supported, i.e., mobility should be supported for high-speed UE cases also, but optimisation should be for low-speed to medium-speed scenarios.
+- It is highly desirable for the 7.68Mcps TDD option to maintain commonality with the 3.84Mcps TDD option. New features shall therefore provide significant incremental gain for an acceptable complexity.
+- The UE and network complexity shall be minimised for a given level of system performance.
+- The impact on current releases in terms of both protocol and hardware perspectives shall be taken into account.
+
+# 6 Physical layer structure
+
+## 6.0 Services offered to higher layers
+
+The 7.68Mcps TDD option supports an identical set of transport channels and indicators to the 3.84Mcps TDD option.
+
+## 6.1 Frame structure
+
+The 7.68Mcps TDD option frame is of length 10ms and consists of 15 timeslots of duration  $5120 \cdot T_c$ , where  $T_c$  is the chip duration ( $T_c = 1 / 7.68 \cdot 10^6 = 130.2\text{ns}$ ). Any timeslot in the frame can be either uplink or downlink. At least one timeslot in the frame is assigned to the uplink and at least one timeslot in the frame is assigned to the downlink. The frame structure is shown in Figure 6.1.1.
+
+![Figure 6.1.1: The 7.68Mcps TDD option frame structure. This is an illustrative diagram of the spectrum emission mask. The x-axis represents 'Frequency separation Δf from the carrier [MHz]' with values 5.0, 5.2, 6.0, 7.0, 15.0, and f_offset_max. The y-axis represents 'Power density in 1 MHz [dBm]' with values -15, -20, -25, -30, -35, and -40. The mask shows a power density of -40 dBm at 5.0 MHz, rising to -31 dBm at 6.0 MHz, and then to -39 dBm at 7.0 MHz. At 15.0 MHz, the power density is -43 dBm. The mask also shows a power density of -31 dBm for frequencies between 6.0 MHz and 7.0 MHz, and -39 dBm for frequencies between 7.0 MHz and 15.0 MHz. The right side of the diagram shows a power density of -25 dBm for frequencies above 15.0 MHz.](2396add2849eccefcbcfbe1c7142a253_img.jpg)
+
+Figure 6.1.1: The 7.68Mcps TDD option frame structure. This is an illustrative diagram of the spectrum emission mask. The x-axis represents 'Frequency separation Δf from the carrier [MHz]' with values 5.0, 5.2, 6.0, 7.0, 15.0, and f\_offset\_max. The y-axis represents 'Power density in 1 MHz [dBm]' with values -15, -20, -25, -30, -35, and -40. The mask shows a power density of -40 dBm at 5.0 MHz, rising to -31 dBm at 6.0 MHz, and then to -39 dBm at 7.0 MHz. At 15.0 MHz, the power density is -43 dBm. The mask also shows a power density of -31 dBm for frequencies between 6.0 MHz and 7.0 MHz, and -39 dBm for frequencies between 7.0 MHz and 15.0 MHz. The right side of the diagram shows a power density of -25 dBm for frequencies above 15.0 MHz.
+
+Figure 6.1.1: The 7.68Mcps TDD option frame structure
+
+## 6.2 Burst structure
+
+The 7.68Mcps burst consists of two data field portions, a midamble portion containing a training sequence and a guard period as shown in Figure 6.2.1. Several bursts can be transmitted at the same time where each burst uses a different OVSF channelisation code, but the same scrambling code.
+
+![Figure 6.2.1: 7.68Mcps TDD option burst structure. This diagram shows a burst structure consisting of four fields: Data field, Midamble, Data field, and guard period. The total duration of the burst is indicated as 5120 * T_c.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg)
+
+|            |          |            |              |
+|------------|----------|------------|--------------|
+| Data field | Midamble | Data field | guard period |
+|------------|----------|------------|--------------|
+
+$5120 \cdot T_c$
+
+Figure 6.2.1: 7.68Mcps TDD option burst structure. This diagram shows a burst structure consisting of four fields: Data field, Midamble, Data field, and guard period. The total duration of the burst is indicated as 5120 \* T\_c.
+
+Figure 6.2.1: 7.68Mcps TDD option burst structure
+
+Three burst types are specified: burst types 1, 2 and 3. The maximum number of training sequences supported in burst types 1 and 3 is either 4, 8 or 16 depending on cell configuration and either 4 or 8 for burst type 2 depending on cell configuration. The lengths of the fields within each burst are defined in Table 6.2.1.
+
+**Table 6.2.1: Number of chips within fields of the 7.68Mcps burst**
+
+| Field        | Burst Type 1 | Burst Type 2 | Burst Type 3 |
+|--------------|--------------|--------------|--------------|
+| Data field 1 | 1952         | 2208         | 1952         |
+| Midamble     | 1024         | 512          | 1024         |
+| Data field 2 | 1952         | 2208         | 1760         |
+| Guard Period | 192          | 192          | 384          |
+
+On the downlink, a spreading factor of 32 is supported. Additionally for DPCH, PDSCH and HS-PDSCH, a spreading factor of 1 is supported on the downlink.
+
+On the uplink, spreading factors of 1, 2, 4, 8, 16 and 32 are supported for DPCH, PUSCH and E-PUCH. PRACH and E-RUCCH only support spreading factors 16 and 32 and HS-SICH only supports spreading factor 32.
+
+The spreading factors and burst types supported for different physical channels are defined in Table 6.2.2.
+
+**Table 6.2.2: Spreading factors and burst types supported by physical channels**
+
+| Physical channel | Supported spreading factors | Supported burst types |
+|------------------|-----------------------------|-----------------------|
+| UL DPCH          | 1, 2, 4, 8, 16, 32          | 1, 2, 3               |
+| DL DPCH          | 1, 32                       | 1, 2                  |
+| P-CCPCH          | 32                          | 1                     |
+| S-CCPCH          | 32                          | 1, 2                  |
+| PRACH            | 16, 32                      | 3                     |
+| PUSCH            | 1, 2, 4, 8, 16, 32          | 1, 2, 3               |
+| PDSCH            | 1, 32                       | 1, 2                  |
+| HS-PDSCH         | 1, 32                       | 1, 2                  |
+| HS-SCCH          | 32                          | 1, 2                  |
+| HS-SICH          | 32                          | 1, 2                  |
+| E-PUCH           | 1, 2, 4, 8, 16, 32          | 1, 2, 3               |
+| E-AGCH           | 32                          | 1, 2                  |
+| E-HICH           | 32                          | 1, 2                  |
+| E-RUCCH          | 16, 32                      | 3                     |
+
+Transmission of TPC and TFCI are performed in accordance with the general procedures used for the existing 3.84 Mcps TDD option. Due to the maximum spreading factor being increased from 16 (3.84Mcps) to 32 (7.68Mcps), usage of SF16 for TPC/TFCI is replaced with SF32 where appropriate.
+
+## 6.3 Midambles
+
+Midambles for burst types 1, 2 and 3 are created using the method applied for 3.84Mcps TDD. The basic midamble code for burst types 1 and 3 is of length 912; for burst type 2 the basic midamble code is of length 456.
+
+Default, common and UE specific midamble modes are supported in the 7.68Mcps TDD option. The characteristics of these midamble allocations at 7.68Mcps are identical to their characteristics at 3.84Mcps. The number of active channelisation codes is signaled via midamble through an extension of the scheme applied at 3.84Mcps TDD (the extension accounts for the higher spreading factor supported at 7.68Mcps).
+
+Midamble transmit powers are allocated as for 3.84Mcps TDD.
+
+The association between midambles and channelisation codes for burst types 1, 2 and 3 are as shown in figure 6.3.1 for  $K_{cell} = 16$ , figure 6.3.2 for  $K_{cell} = 8$  and figure 6.3.3 for  $K_{cell} = 4$ . Secondary channelisation codes are marked with a \*.
+
+These associations apply both for UL and DL.
+
+![A hierarchical tree diagram showing the association of midambles to spreading codes for KCell = 16. The tree starts with m^(1) - c_1^(1) at the root, branching into m^(1) - c_2^(1) and m^(b) - c_2^(2). It further branches through multiple levels of midamble and code identifiers (c_4, c_8, c_16, c_32) to reach 32 leaf nodes representing final spreading codes.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates a binary tree structure for associating midambles to spreading codes. The root node is  $m^{(1)} - c_1^{(1)}$ . It branches into two nodes:  $m^{(1)} - c_2^{(1)}$  and  $m^{(b)} - c_2^{(2)}$ . Each of these nodes branches into two more nodes, and so on, following a pattern of doubling the number of nodes at each level. The nodes are labeled with midamble identifiers ( $m$ ) and code identifiers ( $c$ ) with superscripts indicating the level or group. The final level of the tree consists of 32 leaf nodes, each representing a unique spreading code association, such as  $m^{(1)} - c_{32}^{(1)}$ ,  $m^{(1)} - c_{32}^{(2)*}$ ,  $m^{(9)} - c_{32}^{(3)}$ ,  $m^{(9)} - c_{32}^{(4)*}$ ,  $m^{(2)} - c_{32}^{(5)}$ ,  $m^{(2)} - c_{32}^{(6)*}$ ,  $m^{(10)} - c_{32}^{(7)}$ ,  $m^{(10)} - c_{32}^{(8)*}$ ,  $m^{(3)} - c_{32}^{(9)}$ ,  $m^{(3)} - c_{32}^{(10)*}$ ,  $m^{(11)} - c_{32}^{(11)}$ ,  $m^{(11)} - c_{32}^{(12)*}$ ,  $m^{(6)} - c_{32}^{(13)}$ ,  $m^{(6)} - c_{32}^{(14)*}$ ,  $m^{(14)} - c_{32}^{(15)}$ ,  $m^{(14)} - c_{32}^{(16)*}$ ,  $m^{(5)} - c_{32}^{(17)}$ ,  $m^{(5)} - c_{32}^{(18)*}$ ,  $m^{(13)} - c_{32}^{(19)}$ ,  $m^{(13)} - c_{32}^{(20)*}$ ,  $m^{(4)} - c_{32}^{(21)}$ ,  $m^{(4)} - c_{32}^{(22)*}$ ,  $m^{(12)} - c_{32}^{(23)}$ ,  $m^{(12)} - c_{32}^{(24)*}$ ,  $m^{(7)} - c_{32}^{(25)}$ ,  $m^{(7)} - c_{32}^{(26)*}$ ,  $m^{(15)} - c_{32}^{(27)}$ ,  $m^{(15)} - c_{32}^{(28)*}$ ,  $m^{(8)} - c_{32}^{(29)}$ ,  $m^{(8)} - c_{32}^{(30)*}$ ,  $m^{(16)} - c_{32}^{(31)}$ , and  $m^{(16)} - c_{32}^{(32)*}$ .
+
+A hierarchical tree diagram showing the association of midambles to spreading codes for KCell = 16. The tree starts with m^(1) - c\_1^(1) at the root, branching into m^(1) - c\_2^(1) and m^(b) - c\_2^(2). It further branches through multiple levels of midamble and code identifiers (c\_4, c\_8, c\_16, c\_32) to reach 32 leaf nodes representing final spreading codes.
+
+Figure 6.3.1: Association of Midambles to Spreading Codes for  $K_{Cell} = 16$
+
+![A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K_Cell = 8. The tree starts with m^(1) - c_1^(1) at the root, branching into m^(1) - c_2^(1) and m^(5) - c_2^(2). It further branches through multiple levels of midamble and code combinations (e.g., m^(1) - c_4^(1), m^(3) - c_4^(2), m^(5) - c_4^(3), m^(7) - c_4^(4)) down to the final spreading codes (e.g., m^(1) - c_32^(1) through m^(8) - c_32^(32)).](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+The diagram illustrates the hierarchical association of Midambles to Spreading Codes for  $K_{Cell} = 8$ . The tree structure is as follows:
+
+- Root:**  $m^{(1)} - c_1^{(1)}$
+- Level 1:**  $m^{(1)} - c_2^{(1)}$  and  $m^{(5)} - c_2^{(2)}$
+- Level 2:**
+  - From  $m^{(1)} - c_2^{(1)}$ :  $m^{(1)} - c_4^{(1)}$  and  $m^{(3)} - c_4^{(2)}$
+  - From  $m^{(5)} - c_2^{(2)}$ :  $m^{(5)} - c_4^{(3)}$  and  $m^{(7)} - c_4^{(4)}$
+- Level 3:**
+  - From  $m^{(1)} - c_4^{(1)}$ :  $m^{(1)} - c_8^{(1)}$  and  $m^{(2)} - c_8^{(2)}$
+  - From  $m^{(3)} - c_4^{(2)}$ :  $m^{(3)} - c_8^{(3)}$  and  $m^{(6)} - c_8^{(4)}$
+  - From  $m^{(5)} - c_4^{(3)}$ :  $m^{(5)} - c_8^{(5)}$  and  $m^{(4)} - c_8^{(6)}$
+  - From  $m^{(7)} - c_4^{(4)}$ :  $m^{(7)} - c_8^{(7)}$  and  $m^{(8)} - c_8^{(8)}$
+- Level 4:**
+  - From  $m^{(1)} - c_8^{(1)}$ :  $m^{(1)} - c_{16}^{(1)}$  and  $m^{(1)} - c_{16}^{(2)*}$
+  - From  $m^{(2)} - c_8^{(2)}$ :  $m^{(2)} - c_{16}^{(3)}$  and  $m^{(2)} - c_{16}^{(4)*}$
+  - From  $m^{(3)} - c_8^{(3)}$ :  $m^{(3)} - c_{16}^{(5)}$  and  $m^{(3)} - c_{16}^{(6)*}$
+  - From  $m^{(6)} - c_8^{(4)}$ :  $m^{(6)} - c_{16}^{(7)}$  and  $m^{(6)} - c_{16}^{(8)*}$
+  - From  $m^{(5)} - c_8^{(5)}$ :  $m^{(5)} - c_{16}^{(9)}$  and  $m^{(5)} - c_{16}^{(10)*}$
+  - From  $m^{(4)} - c_8^{(6)}$ :  $m^{(4)} - c_{16}^{(11)}$  and  $m^{(4)} - c_{16}^{(12)*}$
+  - From  $m^{(7)} - c_8^{(7)}$ :  $m^{(7)} - c_{16}^{(13)}$  and  $m^{(7)} - c_{16}^{(14)*}$
+  - From  $m^{(8)} - c_8^{(8)}$ :  $m^{(8)} - c_{16}^{(15)}$  and  $m^{(8)} - c_{16}^{(16)*}$
+- Level 5 (Final Codes):**
+  - From  $m^{(1)} - c_{16}^{(1)}$ :  $m^{(1)} - c_{32}^{(1)}$  and  $m^{(1)} - c_{32}^{(2)*}$
+  - From  $m^{(1)} - c_{16}^{(2)*}$ :  $m^{(1)} - c_{32}^{(3)*}$  and  $m^{(1)} - c_{32}^{(4)*}$
+  - From  $m^{(2)} - c_{16}^{(3)}$ :  $m^{(2)} - c_{32}^{(5)}$  and  $m^{(2)} - c_{32}^{(6)*}$
+  - From  $m^{(2)} - c_{16}^{(4)*}$ :  $m^{(2)} - c_{32}^{(7)*}$  and  $m^{(2)} - c_{32}^{(8)*}$
+  - From  $m^{(3)} - c_{16}^{(5)}$ :  $m^{(3)} - c_{32}^{(9)}$  and  $m^{(3)} - c_{32}^{(10)*}$
+  - From  $m^{(3)} - c_{16}^{(6)*}$ :  $m^{(3)} - c_{32}^{(11)*}$  and  $m^{(3)} - c_{32}^{(12)*}$
+  - From  $m^{(6)} - c_{16}^{(7)}$ :  $m^{(6)} - c_{32}^{(13)}$  and  $m^{(6)} - c_{32}^{(14)*}$
+  - From  $m^{(6)} - c_{16}^{(8)*}$ :  $m^{(6)} - c_{32}^{(15)*}$  and  $m^{(6)} - c_{32}^{(16)*}$
+  - From  $m^{(5)} - c_{16}^{(9)}$ :  $m^{(5)} - c_{32}^{(17)}$  and  $m^{(5)} - c_{32}^{(18)*}$
+  - From  $m^{(5)} - c_{16}^{(10)*}$ :  $m^{(5)} - c_{32}^{(19)*}$  and  $m^{(5)} - c_{32}^{(20)*}$
+  - From  $m^{(4)} - c_{16}^{(11)}$ :  $m^{(4)} - c_{32}^{(21)}$  and  $m^{(4)} - c_{32}^{(22)*}$
+  - From  $m^{(4)} - c_{16}^{(12)*}$ :  $m^{(4)} - c_{32}^{(23)*}$  and  $m^{(4)} - c_{32}^{(24)*}$
+  - From  $m^{(7)} - c_{16}^{(13)}$ :  $m^{(7)} - c_{32}^{(25)}$  and  $m^{(7)} - c_{32}^{(26)*}$
+  - From  $m^{(7)} - c_{16}^{(14)*}$ :  $m^{(7)} - c_{32}^{(27)*}$  and  $m^{(7)} - c_{32}^{(28)*}$
+  - From  $m^{(8)} - c_{16}^{(15)}$ :  $m^{(8)} - c_{32}^{(29)}$  and  $m^{(8)} - c_{32}^{(30)*}$
+  - From  $m^{(8)} - c_{16}^{(16)*}$ :  $m^{(8)} - c_{32}^{(31)*}$  and  $m^{(8)} - c_{32}^{(32)*}$
+
+A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K\_Cell = 8. The tree starts with m^(1) - c\_1^(1) at the root, branching into m^(1) - c\_2^(1) and m^(5) - c\_2^(2). It further branches through multiple levels of midamble and code combinations (e.g., m^(1) - c\_4^(1), m^(3) - c\_4^(2), m^(5) - c\_4^(3), m^(7) - c\_4^(4)) down to the final spreading codes (e.g., m^(1) - c\_32^(1) through m^(8) - c\_32^(32)).
+
+Figure 6.3.2: Association of Midambles to Spreading Codes for  $K_{Cell} = 8$
+
+![Figure 6.3.3: Association of Midambles to Spreading Codes for K_Cell = 4. The diagram is a binary tree showing the hierarchical association of midambles to spreading codes. It starts with a root node m^{(1)} - c_1^{(1)} which branches into two main paths: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. The m^{(1)} - c_2^{(1)} path further branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. The m^{(5)} - c_2^{(2)} path branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. Each of these four nodes then branches into two sub-nodes, m^{(\cdot)} - c_8^{(\cdot)} and m^{(\cdot)} - c_8^{(\cdot)*}, which finally branch into pairs of spreading codes m^{(\cdot)} - c_{16}^{(\cdot)} and m^{(\cdot)} - c_{16}^{(\cdot)*}. Each of these 16 nodes then branches into two final spreading codes m^{(\cdot)} - c_{32}^{(\cdot)} and m^{(\cdot)} - c_{32}^{(\cdot)*}, resulting in a total of 32 leaf nodes representing the spreading codes.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Figure 6.3.3: Association of Midambles to Spreading Codes for K\_Cell = 4. The diagram is a binary tree showing the hierarchical association of midambles to spreading codes. It starts with a root node m^{(1)} - c\_1^{(1)} which branches into two main paths: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. The m^{(1)} - c\_2^{(1)} path further branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. The m^{(5)} - c\_2^{(2)} path branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. Each of these four nodes then branches into two sub-nodes, m^{(\cdot)} - c\_8^{(\cdot)} and m^{(\cdot)} - c\_8^{(\cdot)\*}, which finally branch into pairs of spreading codes m^{(\cdot)} - c\_{16}^{(\cdot)} and m^{(\cdot)} - c\_{16}^{(\cdot)\*}. Each of these 16 nodes then branches into two final spreading codes m^{(\cdot)} - c\_{32}^{(\cdot)} and m^{(\cdot)} - c\_{32}^{(\cdot)\*}, resulting in a total of 32 leaf nodes representing the spreading codes.
+
+**Figure 6.3.3: Association of Midambles to Spreading Codes for  $K_{\text{Cell}} = 4$**
+
+For PRACH and E-RUCCH, up to 16 midambles and channelisation codes may be supported. The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a basic midamble code,  $m_1$ , or a second basic midamble code,  $m_2$ , which is a time inverted version of the basic midamble code  $m_1$ . A fixed association exists between PRACH/E-RUCCH midambles and channelisation codes.
+
+## 6.4 Coding and Modulation
+
+Multiplexing and channel coding is aligned with 3.84Mcps TDD with the exception that physical channel sequence numbering and the coding of the channelisation code set information on HS-SCCH and E-AGCH shall account for the support of SF32 at 7.68Mcps.
+
+## 6.5 Scrambling Codes
+
+The binary scrambling code,  $c_{7,68}^n$ , for cell parameter  $n$  in the 7.68Mcps TDD option is formed from the concatenation of the binary scrambling codes  $c_{3,84}^n$  and  $c_{3,84}^{(n+2) \bmod 128}$  shown in Annex A of [4].
+
+## 6.6 Synchronisation Codes
+
+The synchronisation codes for the 7.68Mcps TDD option are formed by repetition coding of the 3.84Mcps TDD synchronisation code words. Unique modulation sequences are applied to these code words that enable the UE to determine the code group, frame alignment and chip rate of the cell.
+
+The synchronization channel (SCH) is constructed in an identical manner to the construction at 3.84Mcps. The relationship between code group,  $n$ , and  $t_{offset,n}$  at 7.68Mcps is:
+
+$$t_{offset,n} =$$
+
+## 6.7 Transmit diversity
+
+Support for beamforming and transmit diversity are aligned with the 3.84Mcps TDD option.
+
+## 6.8 Measurements
+
+## 6.9 Indicator Channels
+
+### 6.9.1 Paging Indicator Channel (PICH)
+
+The paging indicator channel is spread at SF32, but in other respects is identical to the 3.84Mcps TDD PICH [2].
+
+The PICH block may comprise up to  $N_{PICH} = 8$  frames. The PCH block may comprise up to  $2 \times N_{PCH} = 2 \times 16$  frames.
+
+### 6.9.2 MBMS Indicator Channel (MICH)
+
+The MBMS indicator channel is spread at SF32, but in other respects is identical to the 3.84Mcps TDD MICH [2].
+
+## 6.10 Mapping of transport channels to physical channels
+
+In the 7.68Mcps TDD option, transport channels are mapped onto physical channels according to figure 6.10.1.
+
+| <b>Transport Channels</b> | <b>Physical Channels</b>                               |
+|---------------------------|--------------------------------------------------------|
+| DCH _____                 | Dedicated Physical Channel (DPCH)                      |
+| BCH _____                 | Primary Common Control Physical Channel (P-CCPCH)      |
+| FACH _____                | Secondary Common Control Physical Channel (S-CCPCH)    |
+| PCH _____                 |                                                        |
+| RACH _____                | Physical Random Access Channel (PRACH)                 |
+| USCH _____                | Physical Uplink Shared Channel (PUSCH)                 |
+| DSCH _____                | Physical Downlink Shared Channel (PDSCH)               |
+|                           | Paging Indicator Channel (PICH)                        |
+|                           | MBMS Indication Channel (MICH)                         |
+|                           | Synchronisation Channel (SCH)                          |
+| HS-DSCH _____             | High Speed Physical Downlink Shared Channel (HS-PDSCH) |
+|                           | Shared Control Channel for HS-DSCH (HS-SCCH)           |
+|                           | Shared Information Channel for HS-DSCH (HS-SICH)       |
+| E-DCH _____               | E-DCH Physical Uplink Channel (E-PUCH)                 |
+|                           | E-DCH Random Access Uplink Control Channel (E-RUCCH)   |
+|                           | E-DCH Absolute Grant Channel (E-AGCH)                  |
+|                           | E-DCH Hybrid ARQ Indicator Channel (E-HICH)            |
+
+**Figure 6.10.1: Transport channel to physical channel mapping**
+
+The mapping between DCH, BCH, FACH, USCH and DSCH transport channels to physical channels is identical to the mapping at 3.84Mcps TDD.
+
+The mapping between the RACH transport channel and the PRACH physical channel is identical to the mapping at 3.84Mcps TDD.
+
+The mapping between the HS-DSCH transport channel and HS-PDSCH physical channels is identical to the mapping at 3.84Mcps TDD. The association and timing between HS-SCCH, HS-DSCH and HS-SICH is identical to the association and timing at 3.84Mcps TDD with the exception that the UE must monitor up to a maximum of eight HS-SCCH ( $M=8$ ).
+
+The mapping between the E-DCH transport channel and E-PUCH physical channels is identical to the mapping at 3.84Mcps TDD. The association and timing between E-AGCH, E-PUCH and E-HICH is identical to the association and timing at 3.84Mcps TDD with the exception that up to two channelisation codes for E-HICH are supported for the 7.68Mcps option.
+
+The mapping of E-DCH control information to E-RUCCH when E-PUCH resources are unavailable is identical to that for 3.84Mcps TDD.
+
+# 7 Physical layer procedures
+
+## 7.1 Power Control
+
+Transmitter power control, both on the uplink and downlink, is aligned with that of 3.84Mcps TDD.
+
+## 7.2 Timing Advance
+
+The timing advance architecture is the same as for 3.84Mcps TDD. The required timing advance, 'UL Timing Advance'  $TA_{ul}$  will be represented as a 7 bit number (0-127) and shall be the multiplier of 4 chips which is nearest to the required timing advance.
+
+PUSCH, UL DPCH and HS-SICH are timing advanced. PRACH and E-RUCCH are not timing advanced.
+
+## 7.3 HSDPA procedures
+
+The HS-DSCH procedure is aligned with 3.84Mcps TDD. When SCTD antenna diversity is applied to HS-PDSCH on the beacon channel, the presence of channelisation code  $c_{32}^{(k=1)}$  shall implicitly indicate presence of channelisation code  $c_{32}^{(k=2)}$ .
+
+## 7.4 Synchronisation procedures
+
+The synchronization procedures are aligned with 3.84Mcps TDD.
+
+## 7.5 RACH procedures
+
+The RACH procedure is aligned with 3.84Mcps TDD. However, the use of higher layer signaling to indicate that in some frames a timeslot shall be blocked for RACH uplink transmission is not supported.
+
+## 7.6 Discontinuous transmission (DTX) procedure
+
+The DTX procedure is aligned with that of 3.84Mcps TDD.
+
+## 7.7 Downlink transmit diversity procedure
+
+The downlink transmit diversity procedure is aligned with that of 3.84Mcps TDD. In Space Code Transmit Diversity mode the data sequence is spread with the channelisation codes  $c_{32}^{(k=1)}$  and  $c_{32}^{(k=2)}$ , the spread sequence on code  $c_{32}^{(k=2)}$  is then transmitted on the diversity antenna.
+
+## 7.8 DSCH procedure
+
+Higher layer signaling is used to indicate to the UE the need for PDSCH detection. Physical layer signaling is not used to indicate to the UE the need for PDSCH detection.
+
+## 7.9 Macrodiversity procedure
+
+The macrodiversity procedure is aligned with that of 3.84Mcps TDD.
+
+## 7.10 IPDL procedure
+
+The IPDL procedure is aligned with that of 3.84Mcps TDD.
+
+## 7.11 E-DCH procedures
+
+The E-DCH procedures are aligned with those of 3.84Mcps TDD with modifications to accommodate SF32 for the E-PUCH code hopping procedure and the E-PUCH power control procedure.
+
+# 8 UE capabilities
+
+UE capabilities for the 7.68 Mcps TDD mode are based on those for 3.84 Mcps TDD. The capabilities for 7.68Mcps TDD account for the higher number of physical channels supported and additionally support higher peak bit rates. The minimum MBMS capability at 7.68Mcps is twice the minimum capability at 3.84Mcps. The detailed UE capabilities for 7.68Mcps TDD are described in [8].
+
+# 9 Layer 2/3 protocol aspects
+
+## 9.1 Protocol architecture
+
+The protocol architecture for 7.68 Mcps TDD is the same as the protocol architecture for 3.84 Mcps TDD. Section 5.1 of [7] provides an overview of the radio interface protocol architecture.
+
+## 9.2 Signalling
+
+### 9.2.1 General
+
+There are signalling differences between 7.68 Mcps TDD and 3.84 Mcps TDD. These differences concern L2/MAC and L3/RRC (see Section 5.1 of [7]) only. L2/RLC, L2/BMC, L2/PDCP and L3 U-plane information are not impacted.
+
+### 9.2.2 L2/MAC differences
+
+The L2/MAC differences between 7.68 Mcps TDD and 3.84 Mcps TDD are due to the support of a higher capability HSDPA UE at 7.68 Mcps (20.4Mbps) and a higher capability E-DCH UE at 7.68 Mcps (17.7Mbps). The L2/MAC differences concern:
+
+- the maximum number of PDUs transmitted in a single TTI (636 at 7.68 Mcps compared to 318 for 3.84 Mcps TDD).
+- HSDPA transport block size signalling. The maximum transport block size that can be signalled at 7.68 Mcps is twice that at 3.84 Mcps. A new table and formula for transport block size signalling for 7.68 Mcps TDD HS-DSCH is included in [9].
+- E-DCH transport block size signalling. The maximum transport block size that can be signalled at 7.68 Mcps is approximately twice that at 3.84 Mcps. A new table and formula for transport block size signalling for 7.68 Mcps TDD E-DCH is included in [9].
+
+### 9.2.3 L2/RRC differences
+
+The L2/RRC differences concern:
+
+**Use of SF 32:** The signalling is extended to include support for SF32. The 7.68 Mcps cell will be configured to use SF 16 or 32 for PRACH and E-RUCCH rather than SF 8 and 16 as 3.84 Mcps
+
+**Open Loop Power Control:** Configuration of a cell for use of SF 16 or 32 with respect to the PRACH impacts calculation of the uplink transmit power for PRACH and requires the UE to add 3dB to the RACH Constant Value in the equation:
+
+$$P_{\text{PRACH}} = L_{\text{PCCPCH}} + I_{\text{BTS}} + \text{PRACH Constant value}$$
+
+for the case where RACH Spreading Factor = 16.
+
+The same applies for open loop power control of E-RUCCH.
+
+**Capability Update Requirement:** A new IE "UE radio access 7.68 Mcps TDD capability update requirement" is used.
+
+**Uplink Timing Advance:** A different Uplink Timing Advance IE is required at 7.68 Mcps to account for the number of bits used to signal timing advance at 7.68 Mcps. A number of RRC messages are impacted due to the use of a different Uplink Timing Advance IE for 7.68 Mcps TDD to 3.84 Mcps TDD.
+
+**DL Physical Channel Capability:** The physical channel capability at 7.68 Mcps is extended in order to account for the greater number of physical channels supported at 7.68 Mcps.
+
+**Burst Types and Midambles:** Signalling related to burst types is modified since burst type 2 at 7.68 Mcps supports  $K_{\text{cell}}$  of 4 or 8.
+
+## 9.3 HSDPA related issues
+
+The highest UE capability at 7.68Mcps is double that at 3.84Mcps, hence the maximum transport block size and the maximum number of PDUs that can be transmitted in a single TTI are double that of 3.84 Mcps. The range of UE capabilities is extended and the maximum UE capability for 7.68 Mcps is 20.4 Mbits/s.
+
+## 9.4 Mobility
+
+Inter RAT and intra RAT handover for 7.68 Mcps TDD is as for 3.84 Mcps TDD with handover between 3.84 Mcps TDD and 7.68 Mcps TDD cells also supported. Bands a), b), c), a + b), a + c), b + c) and a + b + c) can be configured for 7.68 Mcps TDD or 3.84 Mcps TDD or 1.28 Mcps TDD.
+
+## 9.5 Idle Mode Procedures
+
+Idle mode procedures are as for 3.84 Mcps TDD.
+
+## 9.6 E-DCH related issues
+
+The highest UE capability at 7.68Mcps is approximately double that at 3.84Mcps, hence the maximum transport block size and the maximum number of PDUs that can be transmitted in a single TTI are increased with respect to that of 3.84 Mcps. The range of UE capabilities is extended and the maximum UE capability for 7.68 Mcps is 17.7 Mbits/s.
+
+# --- 10 Iub/Iur aspects
+
+## 10.1 Impacts on Iub/Iur interfaces – general aspects
+
+### 10.1.1 Timing advance and Rx Timing Deviation
+
+The timing advance algorithm (in RRM, at the RNC) uses Rx Timing Deviation measurements made by the Node B and passed to the RNC in frame protocols. At 3.84 Mcps the resolution is 4 chips. The timing advance determined by RRM is signalled to the UE (RRC).
+
+In addition, the Node B can be configured to take more accurate Rx Timing Deviation measurements of a UE, which are sent to the RNC as dedicated measurements. At 3.84 Mcps the resolution of these is 0.0625 chips. These accurate measurements can be used in location (they are passed to the location system using the PCAP protocol).
+
+Strategy for 7.68 Mcps :
+
+Timing advance & Rx Timing Deviation over FP
+
+- > 4 chip resolution
+- > same dynamic range as 3.84 Mcps (in secs)
+
+Rx Timing Deviation, dedicated measurement
+
+- > 0.0625 chip resolution giving greater measurement accuracy
+- > same dynamic range as 3.84 Mcps (in secs)
+
+### 10.1.2 Paging
+
+For the 7.68Mcps option, the maximum number of paging indicators per paging block should be doubled to accommodate the greater number of users that may be supported by the 10 MHz carrier. To achieve this:
+
+- the number of PICH blocks per paging block (NPICH) is extended from {2,4} to {2,4,8}
+- the number of PCH blocks per paging block (NPCH) is extended from {1..8} to {1..16}.
+
+Consequently, a unique value range for the PI-bitmap needs to be defined for 7.68 Mcps.
+
+### 10.1.3 DSCH Power Control from the RNC
+
+In 3.84 Mcps TDD, the PDSCH may be power controlled from the RNC by sending a transmit power level value in the DSCH DATA FRAME that carries DSCH transport blocks to the Node B. For 7.68 Mcps, the same method can be used and this has been agreed by RAN1. Since the transmit power level is expressed relative to the maximum transmit power, no changes are needed to accommodate 7.68Mcps.
+
+## 10.2 Impacts on Iub/Iur control plane protocols
+
+There are a number of changes to RNSAP, PCAP & NBAP protocols to incorporate:
+
+- **Use of SF 32:** The signalling is extended to include support for SF32. The 7.68 Mcps cell will be configured to use SF 16 or 32 for PRACH and E-RUCCH rather than SF 8 and 16 as 3.84 Mcps
+- **Burst Types and Midambles:** Signalling related to burst types is modified since burst type 2 at 7.68Mcps supports  $K_{cell}$  of 4 or 8.
+- **Number of physical channels:** the SF32 change implies an increase in the number of physical channels that may be supported.
+- **Measurements:** changes are introduced for Rx Timing Deviation and SFN-SFN measurements.
+- **Cell Synchronisation:** this procedure is not supported.
+
+## 10.3 Impacts on Iub/Iur user plane protocols
+
+Specifications 25.425, 25.427 and 25.435 are modified to include 7.68Mcps operation in a similar fashion to 3.84 Mcps. Changes are also needed to accommodate the different rx timing deviation and timing advance signalling for 7.68Mcps compared to 3.84Mcps (see Section 10.1 above). The paging indicator bit-map is also revised (see Section 10.1 above).
+
+# --- 11 Radio aspects
+
+## 11.1 UE radio transmission and reception
+
+### 11.1.1 Transmitter characteristics
+
+#### 11.1.1.1 Transmit power
+
+Common with 3.84Mcps TDD option.
+
+#### 11.1.1.2 Output RF spectrum emissions
+
+##### 11.1.1.2.1 Occupied bandwidth
+
+Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power of the transmitted spectrum, centred on the assigned channel frequency. The occupied channel bandwidth shall be less than 10 MHz based on a chip rate of 7.68 Mcps.
+
+##### 11.1.1.2.2 Out of band emission
+
+Out of band emissions are unwanted emissions immediately outside the nominal channel resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and adjacent channel leakage power ratio (ACLR).
+
+###### 11.1.1.2.2.1 Spectrum emission mask
+
+The spectrum emission mask of the UE applies to frequencies, which are between 5 MHz and 25MHz from the UE centre carrier frequency. The out of channel emission is specified relative to the RRC filtered mean power of the UE carrier. The power of any UE emission shall not exceed the levels specified in Table 11.1.1.
+
+**Table 11.1.1: Spectrum Emission Mask of higher chip rate reference configuration**
+
+| $\Delta f^*$ in MHz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Minimum requirement                                                                              | Measurement bandwidth |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------|
+| 5.0 – 7.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | $\left\{ -38 - 7.5 \cdot \left( \frac{\Delta f}{\text{MHz}} - 5.0 \right) \right\} \text{ dBc}$  | 30 kHz **             |
+| 7.0 – 15                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | $\left\{ -38 - 0.5 \cdot \left( \frac{\Delta f}{\text{MHz}} - 7.0 \right) \right\} \text{ dBc}$  | 1 MHz ***             |
+| 15.0 – 17.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | $\left\{ -42 - 5.0 \cdot \left( \frac{\Delta f}{\text{MHz}} - 15.0 \right) \right\} \text{ dBc}$ | 1 MHz ***             |
+| 17.0 – 25.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | -53 dBc                                                                                          | 1 MHz ***             |
+| * $\Delta f$ is the separation between the carrier frequency and the centre of the measuring filter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                                                                                                  |                       |
+| ** The first and last measurement position with a 30 kHz filter is at $\Delta f$ equals to 5.015 MHz and 6.985 MHz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                                                                  |                       |
+| *** The first and last measurement position with a 1 MHz filter is at $\Delta f$ equals to 7.5 MHz and 24.5 MHz. As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth can be different from the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. |                                                                                                  |                       |
+| The lower limit shall be -47dBm/7.68 MHz or the minimum requirement presented in this table which ever is the higher.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                                  |                       |
+
+###### 11.1.1.2.2.2 Adjacent Channel Leakage power Ratio (ACLR)
+
+Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency.
+
+If the adjacent channel RRC filtered mean power is greater than -50dBm measured with a 3.84 Mcps RRC filter then the ACLR shall be higher than the value specified in Table 11.1.2.
+
+**Table 11.1.2: UE ACLR of higher chip rate reference configuration**
+
+| Power Class | adjacent channel          | Chip Rate for RRC Measurement Filter | ACLR limit |
+|-------------|---------------------------|--------------------------------------|------------|
+| 2, 3        | UE channel $\pm$ 7.5 MHz  | 3.84 MHz                             | 33 dB      |
+| 2, 3        | UE channel $\pm$ 12.5 MHz | 3.84 MHz                             | 43 dB      |
+| 2, 3        | UE channel $\pm$ 20.0 MHz | 7.68 MHz                             | 43 dB      |
+
+###### NOTE:
+
+- 1) The requirement shall still be met in the presence of switching transients.
+- 2) The ACLR requirements reflect what can be achieved with present state of the art technology.
+
+###### 11.1.1.2.2.3 Spurious emissions
+
+The spurious emissions limits shall be common with 3.84 Mcps TDD option and shall be applicable for offsets greater than 25 MHz from the UE centre frequency.
+
+### 11.1.2 Receiver characteristics
+
+#### 11.1.2.1 Reference sensitivity level
+
+The reference sensitivity level is the minimum mean power received at the UE antenna port at which the BIT Error Ratio BER shall not exceed a specific value.
+
+##### 11.1.2.1.1 Minimum Requirement
+
+The BER shall not exceed 0.001 for the parameters specified in Table 11.1.3.
+
+**Table 11.1.3: Test parameters for reference sensitivity (7.68 Mcps TDD Option)**
+
+| Parameter                      | Level | Unit         |
+|--------------------------------|-------|--------------|
+| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0     | dB           |
+| $\hat{I}_{or}$                 | -105  | dBm/7.68 MHz |
+
+#### 11.1.2.2 Adjacent Channel Selectivity (ACS)
+
+Adjacent Channel Selectivity is a measure of a receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s).
+
+##### 11.1.2.2.1 Minimum Requirement
+
+The ACS shall be better than the value indicated in Table 11.1.4 for the test parameters specified in Table 11.1.5 where the BER shall not exceed 0.001
+
+**Table 11.1.4: Adjacent Channel Selectivity (7.68 Mcps TDD Option)**
+
+| Power Class | Unit | ACS |
+|-------------|------|-----|
+| 2           | dB   | 33  |
+| 3           | dB   | 33  |
+
+**Table 11.1.5: Test parameters for Adjacent Channel Selectivity (7.68 Mcps TDD Option)**
+
+| Parameter                             | Unit         | Level        |
+|---------------------------------------|--------------|--------------|
+| $\frac{\sum DPCH\_Ec}{I_{or}}$        | dB           | 0            |
+| $\hat{I}_{or}$                        | dBm/7.68 MHz | -91          |
+| $I_{ac}$ mean power (modulated)       | dBm          | -52          |
+| $F_{uw}$ offset (3.84 Mcps Modulated) | MHz          | +7.5 or -7.5 |
+| $F_{uw}$ offset (7.68 Mcps Modulated) | MHz          | +10 or -10   |
+
+#### 11.1.2.3 Blocking characteristics
+
+The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occur.
+
+##### 11.1.2.3.1 Minimum Requirement
+
+The BER shall not exceed 0.001 for the parameters specified in table 11.1.6 and table 11.1.7. For table 11.1.7 up to 24 exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size.
+
+**Table 11.1.6: In-band blocking**
+
+| Parameter                        | Level                                     |                                           | Unit         |
+|----------------------------------|-------------------------------------------|-------------------------------------------|--------------|
+| $\frac{\sum DPCH\_Ec}{I_{or}}$   | 0                                         |                                           | dB           |
+| $\hat{I}_{or}$                   | -102                                      |                                           | dBm/7.68 MHz |
+| $I_{ouw}$ mean power (modulated) | -53<br>(for $F_{uw}$ offset $\pm 20$ MHz) | -41<br>(for $F_{uw}$ offset $\pm 30$ MHz) | dBm          |
+
+**Table 11.1.7: Out of band blocking**
+
+| Parameter                                                                                    | Band 1                                                                                                                                                                                                                                                                | Band 2                             | Band 3                           | Unit         |
+|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------|--------------|
+| $\frac{\sum DPCH\_Ec}{I_{or}}$                                                               | 0                                                                                                                                                                                                                                                                     | 0                                  | 0                                | dB           |
+| $\hat{I}_{or}$                                                                               | -102                                                                                                                                                                                                                                                                  | -102                               | -102                             | dBm/7.68 MHz |
+| $I_{ouw}$ (CW)                                                                               | -44                                                                                                                                                                                                                                                                   | -30                                | -15                              | dBm          |
+| $F_{uw}$<br>For operation in frequency bands as defined in subclause 5.2(a) of TS25.102 [10] | 1840 < f < 1870<br>1950 < f < 1980<br>2055 < f < 2085                                                                                                                                                                                                                 | 1815 < f < 1840<br>2085 < f < 2110 | 1 < f < 1815<br>2110 < f < 12750 | MHz          |
+| $F_{uw}$<br>For operation in frequency bands as defined in subclause 5.2(b) of TS25.102 [10] | 1790 < f < 1820<br>2020 < f < 2050                                                                                                                                                                                                                                    | 1765 < f < 1790<br>2050 < f < 2075 | 1 < f < 1765<br>2075 < f < 12750 | MHz          |
+| $F_{uw}$<br>For operation in frequency bands as defined in subclause 5.2(c) of TS25.102 [10] | 1850 < f < 1880<br>1960 < f < 1990                                                                                                                                                                                                                                    | 1825 < f < 1850<br>1990 < f < 2015 | 1 < f < 1825<br>2015 < f < 12750 | MHz          |
+| 1.                                                                                           | For operation referenced in 5.2(a) of TS25.102 [10], from 1870 < f < 1900 MHz, 1920 < f < 1950 MHz, 1980 < f < 2010 MHz and 2025 < f < 2055 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied. |                                    |                                  |              |
+| 2.                                                                                           | For operation referenced in 5.2(b) of TS25.102 [10], from 1820 < f < 1850 MHz and 1990 < f < 2020 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied.                                           |                                    |                                  |              |
+| 3.                                                                                           | For operation referenced in 5.2(c) of TS25.102 [10], from 1880 < f < 1910 MHz and 1930 < f < 1960 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied.                                           |                                    |                                  |              |
+
+#### 11.1.2.4 Spurious response
+
+Spurious response is a measure of the receiver's ability to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the blocking limit is not met.
+
+##### 11.1.2.4.1 Minimum Requirement
+
+The BER shall not exceed 0.001 for the parameters specified in Table 11.1.8.
+
+**Table 11.1.8: Spurious Response**
+
+| Parameter                      | Level                         | Unit         |
+|--------------------------------|-------------------------------|--------------|
+| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0                             | dB           |
+| $\hat{I}_{or}$                 | -102                          | dBm/7.68 MHz |
+| $I_{ouw}$ (CW)                 | -44                           | dBm          |
+| $F_{uw}$                       | Spurious response frequencies | MHz          |
+
+#### 11.1.2.5 Spurious emissions
+
+The Spurious Emissions Power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector.
+
+##### 11.1.2.5.1 Minimum Requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 11.1.9: Receiver spurious emission requirements**
+
+| Band                                                                       | Maximum level | Measurement Bandwidth | Note                                                                                                                                         |
+|----------------------------------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| 30 MHz – 1 GHz                                                             | -57 dBm       | 100 kHz               |                                                                                                                                              |
+| 1 GHz – 1.9 GHz and<br>1.92 GHz – 2.01 GHz and<br>2.025 GHz – 2.11 GHz     | -47 dBm       | 1 MHz                 | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the UE. |
+| 1.9 GHz – 1.92 GHz and<br>2.01 GHz – 2.025 GHz and<br>2.11 GHz – 2.170 GHz | -57 dBm       | 7.68 MHz              | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the UE. |
+| 2.170 GHz – 12.75 GHz                                                      | -47 dBm       | 1 MHz                 |                                                                                                                                              |
+
+## 11.2 Base station radio transmission and reception
+
+### 11.2.1 Transmitter characteristics
+
+#### 11.2.1.1 Base station output power
+
+Common with 3.84Mcps TDD option.
+
+#### 11.2.1.2 Output RF spectrum emissions
+
+##### 11.2.1.2.1 Occupied bandwidth
+
+Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power for transmitted spectrum and is centered on the assigned channel frequency. The occupied channel bandwidth is less than 10 MHz based on a chip rate of 7.68 Mcps.
+
+##### 11.2.1.2.2 Out of band emission
+
+Out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission requirement is specified both in terms of a spectrum emission mask and adjacent channel power ratio for the transmitter.
+
+###### 11.2.1.2.2.1 Spectrum emission mask
+
+The mask defined in Table 11.2.1 to 11.2.4 below may be mandatory in certain regions. In other regions this mask may not be applied.
+
+For regions where this clause applies, the requirement shall be met by a base station transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 11.2.1 to 11.2.4 for the appropriate BS maximum output power, in the frequency range from  $\Delta f = 5$  MHz to  $\Delta f_{\max}$  from the carrier frequency, where:
+
+- $\Delta f$  is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f_{\text{offset}}$  is the separation between the carrier frequency and the center frequency of the measuring filter.-  
+ $f_{\text{offsetmax}}$  is either 25 MHz or the offset to the UMTS Tx band edge as defined in TS25.105 [11], whichever is the greater.
+- $\Delta f_{\max}$  is equal to  $f_{\text{offsetmax}}$  minus half of the bandwidth of the measurement filter.
+
+![Illustrative diagram of spectrum emission mask. The graph shows Power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and Power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents Frequency separation Δf from the carrier [MHz] with markers at 5.0, 5.2, 6.0, 7.0, and 15.0, followed by a break and f_offset_max. Three masks are shown for different power levels: P = 43 dBm (top, starting at -17 dBm in 30kHz), P = 39 dBm (middle, starting at -21 dBm in 30kHz), and P = 31 dBm (bottom, starting at -29 dBm in 30kHz). All masks show a 15 dB/MHz roll-off until they reach a flat limit of -35 dBm in 30kHz (or -20 dBm in 1 MHz) starting at 6.015 MHz.](a289b64f80c6df506c0c55d553fc4496_img.jpg)
+
+Illustrative diagram of spectrum emission mask. The graph shows Power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and Power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents Frequency separation Δf from the carrier [MHz] with markers at 5.0, 5.2, 6.0, 7.0, and 15.0, followed by a break and f\_offset\_max. Three masks are shown for different power levels: P = 43 dBm (top, starting at -17 dBm in 30kHz), P = 39 dBm (middle, starting at -21 dBm in 30kHz), and P = 31 dBm (bottom, starting at -29 dBm in 30kHz). All masks show a 15 dB/MHz roll-off until they reach a flat limit of -35 dBm in 30kHz (or -20 dBm in 1 MHz) starting at 6.015 MHz.
+
+Illustrative diagram of spectrum emission mask
+
+Figure 11.2.1: Spectrum emission mask
+
+Table 11.2.1: Spectrum emission mask values, BS maximum output power  $P \geq 43$  dBm
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$               | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$               | -17 dBm                                                                                     | 30 kHz                |
+| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$               | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$               | $-17 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz                |
+| (see note)                                                    | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$                 | -29 dBm                                                                                     | 30 kHz                |
+| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$            | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                  | -16 dBm                                                                                     | 1 MHz                 |
+
+Table 11.2.2: Spectrum emission mask values, BS maximum output power  $39 \leq P < 43$  dBm
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$               | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$               | -17 dBm                                                                                     | 30 kHz                |
+| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$               | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$               | $-17 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz                |
+| (see note)                                                    | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$                 | -29 dBm                                                                                     | 30 kHz                |
+| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$                | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$                  | -16 dBm                                                                                     | 1 MHz                 |
+| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                 | $P - 59 \text{ dB}$                                                                         | 1 MHz                 |
+
+**Table 11.2.3: Spectrum emission mask values, BS maximum output power  $31 \leq P < 39$  dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                                 | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------|
+| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$               | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$               | $P - 56 \text{ dB}$                                                                           | 30 kHz                |
+| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$               | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$               | $P - 56 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz                |
+| (see note)                                                    | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$                 | $P - 68 \text{ dB}$                                                                           | 30 kHz                |
+| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$                | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$                  | $P - 55 \text{ dB}$                                                                           | 1 MHz                 |
+| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                 | $P - 59 \text{ dB}$                                                                           | 1 MHz                 |
+
+**Table 11.2.4: Spectrum emission mask values, BS maximum output power  $P < 31$  dBm**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level                                                                               | Measurement bandwidth |
+|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------|
+| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$               | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$               | -25 dBm                                                                                     | 30 kHz                |
+| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$               | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$               | $-25 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz                |
+| (see note)                                                    | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$                 | -37 dBm                                                                                     | 30 kHz                |
+| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$                | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$                  | -24 dBm                                                                                     | 1 MHz                 |
+| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$           | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                 | -28 dBm                                                                                     | 1 MHz                 |
+
+NOTE: This frequency range ensures that the range of values of  $f\_offset$  is continuous.
+
+###### 11.2.1.2.2.2 Adjacent Channel Leakage power Ratio (ACLR)
+
+Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency. The requirements shall apply for all configurations of BS (single carrier or multi-carrier), and for all operating modes foreseen by the manufacturer's specification.
+
+In some cases the requirement is expressed as adjacent channel leakage power, which is the RRC filtered mean power for the given bandwidth of the victim system at the defined adjacent channel offset.
+
+The requirement depends on the deployment scenario. Different deployment scenarios have been defined as given below.
+
+###### 11.2.1.2.2.2.1 Minimum requirement
+
+The ACLR of a single carrier BS or a multi-carrier BS with contiguous carrier frequencies shall be higher than the value specified in Table 11.2.5.
+
+**Table 11.2.5: BS ACLR**
+
+| BS adjacent channel offset below the first or above the last carrier frequency used | Chip Rate for RRC Measurement Filter | ACLR limit |
+|-------------------------------------------------------------------------------------|--------------------------------------|------------|
+| 7.5 MHz                                                                             | 3.84 Mcps                            | 45 dB      |
+| 12.5 MHz                                                                            | 3.84 Mcps                            | 55 dB      |
+| 10.0 MHz                                                                            | 7.68 Mcps                            | 45 dB      |
+| 20.0 MHz                                                                            | 7.68 Mcps                            | 55 dB      |
+
+If a BS provides multiple non-contiguous single carriers or multiple non-contiguous groups of contiguous single carriers, the above requirements shall be applied individually to the single carriers or group of single carriers.
+
+###### 11.2.1.2.2.3 Spurious emissions
+
+Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port.
+
+The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer.
+
+The requirement applies at frequencies within the specified frequency ranges which are more than 25 MHz under the first carrier frequency used or more than 25 MHz above the last carrier frequency used.
+
+The mandatory requirements for Category A and Category B shall be common with 3.84 Mcps TDD option.
+
+### 11.2.2 Receiver characteristics
+
+#### 11.2.2.1 Reference sensitivity level
+
+The reference sensitivity level is the minimum mean power received at the antenna connector at which the BER shall not exceed the specific value indicated in section 11.2.2.1.1.
+
+##### 11.2.2.1.1 Minimum requirement
+
+The UL reference measurement channel used in the simulations of TR25.895 is the 12.2 kbps channel specified in Annex A.2.1 of TS25.105 [11] with twice the spreading factor (SF=16) and mid-amble (1024 chips). The reference sensitivity level and performance of the BS shall be as specified in Table 11.2.6.
+
+**Table 11.2.6: BS reference sensitivity level**
+
+| BS Class      | Reference measurement channel data rate | BS reference sensitivity level | BER                        |
+|---------------|-----------------------------------------|--------------------------------|----------------------------|
+| Wide Area BS  | 12.2 kbps                               | -109 dBm                       | BER shall not exceed 0.001 |
+| Local Area BS | 12.2 kbps                               | -95 dBm                        | BER shall not exceed 0.001 |
+
+#### 11.2.2.2 Adjacent Channel Selectivity (ACS)
+
+Adjacent channel selectivity (ACS) is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of a single code CDMA modulated adjacent channel signal at a given frequency offset from the center frequency of the assigned channel. ACS is the ratio of the receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s).
+
+##### 11.2.2.2.1 Minimum requirement
+
+The BER shall not exceed 0.001 for the parameters specified in table 11.2.7.
+
+**Table 11.2.7: Adjacent channel selectivity**
+
+| Parameter                               |               | Level | Unit |
+|-----------------------------------------|---------------|-------|------|
+| Reference measurement channel data rate |               | 12.2  | kbps |
+| Wanted signal mean power                | Wide Area BS  | -103  | dBm  |
+|                                         | Local Area BS | -89   | dBm  |
+| Interfering signal mean power           | Wide Area BS  | -49   | dBm  |
+|                                         | Local Area BS | -35   | dBm  |
+| Fuw offset (Modulated)                  |               | 10    | MHz  |
+
+#### 11.2.2.3 Blocking characteristics
+
+The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The blocking performance requirement applies to interfering signals with center frequency within the ranges specified in the tables below, using a 1MHz step size.
+
+##### 11.2.2.3.1 Minimum requirement
+
+The static reference performance as specified in clause 11.2.2.1.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the parameters as specified in Table 11.2.8 to 11.2.10 for the Wide Area BS and as specified in Table 11.2.11 to 11.2.13 for the Local Area BS.
+
+**Table 11.2.8: Blocking requirements for Wide Area BS for operating bands defined in 5.2(a) of TS 25.105 [11]**
+
+| Centre Frequency of Interfering Signal                  | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1900 – 1920 MHz,<br>2010 – 2025 MHz                     | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1880 – 1900 MHz,<br>1990 – 2010 MHz,<br>2025 – 2045 MHz | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1920 – 1980 MHz                                         | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1880 MHz,<br>1980 – 1990 MHz,<br>2045 – 12750 MHz   | -15 dBm                       | -103 dBm                 | —                                    | CW carrier                 |
+
+**Table 11.2.9: Blocking requirements for Wide Area BS for operating bands defined in 5.2(b) of TS 25.105 [11]**
+
+| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1850 – 1990 MHz                        | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1830 – 1850 MHz,<br>1990 – 2010 MHz    | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1830 MHz,<br>2010 – 12750 MHz      | -15 dBm                       | -103 dBm                 | —                                    | CW carrier                 |
+
+**Table 11.2.10: Blocking requirements for Wide Area BS for operating bands defined in 5.2(c) of TS 25.105 [11]**
+
+| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1910 – 1930 MHz                        | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1890 – 1910 MHz,<br>1930 – 1950 MHz    | -40 dBm                       | -103 dBm                 | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1890 MHz,<br>1950 – 12750 MHz      | -15 dBm                       | -103 dBm                 | —                                    | CW carrier                 |
+
+**Table 11.2.11: Blocking requirements for Local Area BS for operating bands defined in 5.2(a) of TS25.105 [11]**
+
+| Centre Frequency of Interfering Signal                  | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1900 – 1920 MHz,<br>2010 – 2025 MHz                     | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1880 – 1900 MHz,<br>1990 – 2010 MHz,<br>2025 – 2045 MHz | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1920 – 1980 MHz                                         | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1880 MHz,<br>1980 – 1990 MHz,<br>2045 – 12750 MHz   | -15 dBm                       | -89 dBm                  | —                                    | CW carrier                 |
+
+**Table 11.2.12: Blocking requirements for Local Area BS for operating bands defined in 5.2(b) of TS 25.105 [11]**
+
+| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1850 – 1990 MHz                        | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1830 – 1850 MHz,<br>1990 – 2010 MHz    | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1830 MHz,<br>2010 – 12750 MHz      | -15 dBm                       | -89 dBm                  | —                                    | CW carrier                 |
+
+**Table 11.2.13: Blocking requirements for Local BS for operating bands defined in 5.2(c) of TS25.105 [11]**
+
+| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal |
+|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|
+| 1910 – 1930 MHz                        | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1890 – 1910 MHz,<br>1930 – 1950 MHz    | -30 dBm                       | -89 dBm                  | 20 MHz                               | WCDMA signal with one code |
+| 1 – 1890 MHz,<br>1950 – 12750 MHz      | -15 dBm                       | -89 dBm                  | —                                    | CW carrier                 |
+
+##### 11.2.2.3.2 Collocation with GSM900 and/or DCS 1800
+
+Common with 3.84 Mcps TDD option.
+
+#### 11.2.2.4 Spurious emissions
+
+The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS antenna connector. The requirements apply to all BS with separate RX and TX antenna port. The test shall be performed when both TX and RX are on with the TX port terminated.
+
+##### 11.2.2.4.1 Minimum requirement
+
+The power of any spurious emission shall not exceed:
+
+**Table 11.2.14: Receiver spurious emission requirements**
+
+| Band                                           | Maximum level | Measurement Bandwidth | Note                                                                                                                                         |
+|------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| 30 MHz – 1 GHz                                 | -57 dBm       | 100 kHz               |                                                                                                                                              |
+| 1 GHz – 1.9 GHz and<br>1.98 GHz – 2.01 GHz     | -47 dBm       | 1 MHz                 | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. |
+| 1.9 GHz – 1.98 GHz and<br>2.01 GHz – 2.025 GHz | -75 dBm       | 7.68 MHz              | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. |
+| 2.025 GHz – 12.75 GHz                          | -47 dBm       | 1 MHz                 | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. |
+

marked/Rel-17/25_series/25300/raw.md

@@ -0,0 +1,454 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 5  |
+| 1 Scope.....                                                               | 6  |
+| 2 References.....                                                          | 6  |
+| 3 Definitions, symbols and abbreviations.....                              | 7  |
+| 3.1 Definitions.....                                                       | 7  |
+| 3.2 Symbols.....                                                           | 7  |
+| 3.3 Abbreviations .....                                                    | 7  |
+| 4 Heterogeneous Networks Mobility Enhancements.....                        | 7  |
+| 5 Heterogeneous Networks Enhancements.....                                 | 7  |
+| 6 DCH Enhancements (FDD only) .....                                        | 8  |
+| 6.1 DL overhead optimization.....                                          | 8  |
+| 6.2 Enhanced rate matching and transport channel multiplexing .....        | 8  |
+| 6.3 DL frame early termination (DL FET) and UL DPCCH with DL FET ACK ..... | 9  |
+| 6.3.1 DL FET Full mode (Mode 1) .....                                      | 9  |
+| 6.3.2 DL FET Basic mode (Mode 0).....                                      | 9  |
+| 6.4 Uplink DPDCH dynamic 10ms transmission.....                            | 9  |
+| 7 Access Control in Connected Mode (CELL_FACH, CELL_PCH and URA_PCH) ..... | 10 |
+| 8 Access control enhancements .....                                        | 10 |
+| 8.1 DSAC and PPAC update for the UE in CELL_DCH state.....                 | 10 |
+| 9 Enhanced Broadcast of System Information.....                            | 10 |
+| 9.1 Second system information broadcast channel .....                      | 10 |
+| 9.2 Scheduling information overhead reduction .....                        | 12 |
+| 9.3 MIB and Cell Value Tag range extension.....                            | 12 |
+| 10 RAN assisted WLAN interworking.....                                     | 12 |
+| 10.1 General principles .....                                              | 12 |
+| 10.2 Access network selection and traffic steering rules .....             | 13 |
+| 11 Increased minimum number of carriers to monitor .....                   | 13 |
+| 12 Extended DRX in Idle mode.....                                          | 13 |
+| 13 L2 and L3 Downlink enhancements for UMTS.....                           | 14 |
+| 13.1 Retrievable configurations .....                                      | 14 |
+| 13.2 URA_PCH with seamless transition .....                                | 14 |
+| 13.3 Optimization from IDLE to CONNECTED state .....                       | 14 |
+| 13.4 Blind HARQ retransmissions for HSDPA.....                             | 15 |
+| 13.5 Enhanced state transition.....                                        | 15 |
+| 13.6 Improved synchronized RRC procedures .....                            | 15 |
+| 14 Downlink TPC enhancements for UMTS.....                                 | 15 |
+| 15 NAICS offloading (FDD only) .....                                       | 15 |
+| 16 ACDC in Idle Mode.....                                                  | 15 |
+| 17 RRC optimization .....                                                  | 16 |
+| 17.1 RRC measurement events for UPH reporting.....                         | 16 |
+| 17.2 Simultaneous Setup and Release of RABs and RBs.....                   | 16 |
+
+18 HS-SCCH DRX in CELL\_FACH state (FDD only) ..... 16
+
+19 Dual Cell E-DCH operation enhancements ..... 16
+
+20 QoE Measurement Collection..... 16
+
+21 DL Interference Mitigation (FDD only) ..... 17
+
+22 Simplified HS-SCCH type 1 operation..... 17
+
+23 NR SRVCC to UTRAN ..... 17
+
+Annex A (informative): Change history..... 18
+
+# --- Foreword
+
+This Technical Specification 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 provides an overview and overall description of the UTRA radio interface functionalities from Release 12 onwards which are not covered by the Technical Specifications TS 25.308 [2] or TS 25.319 [3].
+
+# 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 25.308: "UTRA HSDPA: UTRAN Overall Description (Stage 2) ".
+- [3] 3GPP TS 25.319: "Enhanced Uplink: Overall description (Stage 2) ".
+- [4] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols - Stage 3".
+- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [6] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
+- [7] 3GPP TR 25.704: "Study on enhanced broadcast of system information".
+- [8] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
+- [9] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [10] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
+- [11] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)".
+- [12] 3GPP TS 25.331: "Radio Resource Control (RRC)".
+- [13] 3GPP TR 25.993: "Typical examples of Radio Access Bearers (RABs) and Radio Bearers (RBs) supported by Universal Terrestrial Radio Access (UTRA)".
+- [14] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
+- [15] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
+- [16] 3GPP TS 38.300: "NR; Overall description; Stage 2".
+- [17] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+
+# 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].
+
+**Power saving mode:** Mode configured and controlled by NAS that allows the UE to reduce its power consumption, as defined in TS 24.008 [4], TS 23.060 [5], TS 23.682 [6].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+<symbol> <Explanation>
+
+## 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].
+
+|        |                                                                |
+|--------|----------------------------------------------------------------|
+| ACDC   | Application specific Congestion control for Data Communication |
+| ANDSF  | Access Network Discovery and Selection Function                |
+| DPCCH2 | Dedicated Physical Control Channel 2                           |
+| NCL    | Neighbour Cell List                                            |
+| NR     | NR Radio Access                                                |
+| OPI    | Offload Preference Indicator                                   |
+| PSM    | Power Saving Mode                                              |
+| SRVCC  | Single Radio Voice Call Continuity                             |
+| QoE    | Quality of Experience                                          |
+| WLAN   | Wireless Local Area Network                                    |
+
+# 4 Heterogeneous Networks Mobility Enhancements
+
+Neighbour Cell List (NCL) extension
+
+- The size of the inter-frequency neighbour cell list is extended for CELL\_DCH, CELL\_FACH, CELL\_PCH, URA\_PCH states and Idle mode, so that network could configure more inter-frequency neighbour cells than 32 for UE to monitor and detect under massive small cell deployment scenario.
+
+Change of best cell on a configured secondary downlink frequency (event 2g)
+
+- Event 2g is an inter-frequency measurement event. It is applicable only to the secondary downlink frequency with configured HS-DSCH operation, and it can be configured on more than one secondary downlink frequency.
+
+Enhanced Serving Cell Change for Event 1C
+
+- The enhanced Serving Cell Change procedure could also be applied to Event 1C, which is defined in TS 25.308 [2].
+
+# 5 Heterogeneous Networks Enhancements
+
+Serving E-DCH cell decoupling
+
+- Serving E-DCH cell decoupling is introduced in order to improve the quality of reception of the uplink E-DCH control channels and the E-DCH SI in the presence of strong uplink/downlink imbalance. The UE is configured with different serving HS-DSCH cell and serving E-DCH cell.
+
+Radio Links without DPCH/F-DPCH
+
+- The UE is configured with a subset of non-serving E-DCH radio links in the UE's E-DCH active set to operate in the absence of DPCH/F-DPCH. However, a UE is allowed to only receive either E-HICH or both E-HICH and E-RGCH from these non-serving E-DCH cells to mitigate uplink interference to a cell that is unable to power control a UE in the presence of strong uplink/downlink imbalance.
+
+## DPCCH2 transmission
+
+- In order to improve the quality of reception of the HS-DPCCH in the presence of strong uplink/imbalance, a new secondary uplink pilot channel (DPCCH2) is introduced in the serving HS-DSCH cell as the reference for the HS-DPCCH channel power.
+
+# --- 6 DCH Enhancements (FDD only)
+
+DCH enhancements aims at improving the link efficiency and UE battery performance for voice calls compared to R99 DCH. DCH enhancements constitutes of the following sub-features:
+
+- DL overhead optimization
+- Enhanced rate matching and transport channel multiplexing
+- DL Frame Early Termination (DL FET)
+- Uplink DPCCH with DL FET ACK
+- Uplink DPDCH dynamic 10ms transmission
+
+DCH enhancements supports two modes (Basic and Full). The mode choice controls how the DL Frame Early Termination sub-feature operates, as described in 6.3. All other sub-features are active in both modes.
+
+DCH enhancements is only applicable if the TTI of all DCH transport channels on both downlink and uplink is at least 20 ms.
+
+If a UE is configured with both CS and PS mapped to the DCH transport channel (in uplink or downlink or both), then DCH enhancements may be configured only when PS has UL:0 and DL:0kbps RAB configuration (3GPP TR 25.993 [13]).
+
+## 6.1 DL overhead optimization
+
+This sub-feature introduces new DL DPCH slot format by removing the dedicated pilot bits from DL DPCCH and reusing them for DL DPDCH instead.
+
+The R99 downlink physical channel (DPCH) consists of 0.66ms slots that contain 2 groups of data (DPDCH) symbols and 3 groups of control (DPCCH) symbols. The size of the groups is determined by the slot format. The control symbol groups are TPC - controlling uplink transmit power, TFCI - specifying the downlink packet type, and dedicated pilot - supporting channel estimation for DL power control and closed-loop transmit diversity. While the TFCI group may be empty in certain slot formats, the pilot and TPC are currently always non-empty. The dedicated pilot bits are used for estimation of DL SIR. With this sub-feature, new DL DPCH slot formats are introduced by removing the dedicated pilot bits and reusing the TPC bits instead for estimating the DL SIR. Correspondingly, the number of data symbols in a slot is increased leading to less control channel overhead on the downlink.
+
+DL closed-loop transmit diversity is not supported when this sub-feature is configured.
+
+## 6.2 Enhanced rate matching and transport channel multiplexing
+
+The physical layer in R99 is designed to carry potentially a large variety of transport blocks with different sizes. The drawback for this design is the rate matching may not be efficient when some transport format combinations are not frequently used. For example, DCCH channel carries non-zero transport blocks not as often as voice DTCH channel. The enhanced rate matching and transport channel multiplexing sub-feature sets a zero rate matching attribute for DCCH, whenever DCCH channel does not carry a transport block together with DTCH channel. The DCCH bit fields are used to transmit DTCH transport channels instead. This potentially improves link efficiency due to less puncturing and better rate matching of the transport block with the available physical channel resources.
+
+## 6.3 DL frame early termination (DL FET) and UL DPCCH with DL FET ACK
+
+In a power-controlled system such as R99 DCH, inefficiencies in the power-control loop, such as limited granularity, delays and errors in the feedback, result in the presence of excess SINR at the receiver. This means that packets such as the voice packets which have a long (20ms) transmission time interval (TTI) can often be early-decoded, i.e, decoded prior to reception of all the data symbols in a TTI by running the channel decoder at multiple time instants during the TTI instead of only once at the end of the TTI. This is referred to as Frame Early Termination (FET). As described below, DCH enhancements introduces new mechanisms to R99 DCH in order to support DL FET.
+
+A new design of UL DPCCH is introduced to support DL FET. With the new design, TFCI information is carried in the first 10 slots of each 20ms TTI for the uplink. Sending the TFCI information early in each 20ms TTI allows sending of DL FET ACK or NACK information using the TFCI bits in remaining UL DPCCH slots that do not carry TFCI.
+
+Furthermore, there are two modes of operation introduced with support for DL FET in DCH enhancements as described below.
+
+### 6.3.1 DL FET Full mode (Mode 1)
+
+In the Full mode of operation:
+
+- The UE acknowledges successful early decoding of a DL packet via a DL FET ACK on the newly designed UL DPCCH channel, which then allows the NodeB to stop transmission of the packet.
+- AMR Class A, B, C transport channels are concatenated on the DL which further helps in early decoding of DL DPDCH.
+
+### 6.3.2 DL FET Basic mode (Mode 0)
+
+In the Basic mode of operation:
+
+- DL FET is achieved by applying the DL BLER target at slot 14 (10ms) in each 20ms TTI duration. The NodeB may decide to stop transmission of the DL voice packet at slot 14 provided that the Uplink is in 10ms transmission mode (see sub-clause 6.4). The UE does not indicate successful decoding of the DL packet via the DL FET ACK or NACK field in UL DPCCH.
+- AMR Class A, B, C transport channels are not concatenated on the downlink.
+
+## 6.4 Uplink DPDCH dynamic 10ms transmission
+
+The R99 DCH transport channels for a voice call are typically configured with 20ms TTI. However, the transport block sizes for a voice call could potentially be transmitted over a shorter duration. The sub-feature of uplink DPDCH dynamic 10ms transmission allows for dynamically selecting a shorter transmission time, i.e. 10ms, at the physical layer to transmit a voice packet on the uplink. The UE selects on whether to use a 10ms or 20ms transmission duration based on considerations such as the power headroom at the UE. The UE also discontinues the transmission of UL DPCCH for the remaining duration of the TTI when both UL transport block has been completed transmitted and DL has been successfully decoded early.
+
+With 20ms TTI transmission at the physical layer, the pilot channel (UL DPCCH) is sent for the entire 20ms duration. This sub-feature potentially improves link efficiency due to reduction in UL DPCCH overhead as well as improves UE battery performance by allowing the UE to turn off its transceiver once the reception and transmission has been completed before the end of a 20ms TTI.
+
+# --- 7 Access Control in Connected Mode (CELL\_FACH, CELL\_PCH and URA\_PCH)
+
+For FDD, certain categories of UEs may be configured for Access Control in connected mode. This feature allows for a network to differentiate and control accesses of UE for DTCH transmission in CELL\_FACH state and for DCCH/CCCH due to uplink data transmission in CELL\_PCH state or URA\_PCH state, when uplink congestion is being experienced.
+
+The network may differentiate among the UE population by assigning UEs to one of 16 defined Access Groups. The network can indicate the identity of the access group to which the UE is assigned via RRC dedicated signalling.
+
+For each network assigned Access Group, the network can indicate in System Information whether the UEs in CELL\_FACH state, CELL\_PCH state or URA\_PCH state in that group are Blocked or Unblocked for DTCH data transmission and for DCCH/CCCH due to uplink data transmission. The System Information Block containing the Access Group information is scheduled by the network only during periods of uplink congestion. A UE in CELL\_FACH state, CELL\_PCH state or URA\_PCH state which has data to transmit and has an access group identity will reacquire the System Information Block containing the Access Group information based on the expiration of a timer.
+
+UEs in CELL\_PCH (without seamless transition to CELL\_FACH state) or URA\_PCH (without seamless transition to CELL\_FACH) are not allowed to initiate Cell Update procedure triggered due to DTCH data transmission with cause "uplink data transmission" when the Access Group of the UE is Blocked.
+
+UEs in CELL\_PCH (with seamless transition to CELL\_FACH state) or URA\_PCH (with seamless transition to CELL\_FACH state) are not allowed to initiate Measurement Report procedure triggered due to DTCH data transmission when the Access Group of the UE is Blocked.
+
+A UE in CELL\_FACH state, CELL\_PCH state or URA\_PCH state which is blocked for DTCH transmission and for DCCH/CCCH due to data transmission in the uplink is permitted to transmit uplink RLC Control PDUs.
+
+# 8 Access control enhancements
+
+## 8.1 DSAC and PPAC update for the UE in CELL\_DCH state
+
+In CELL\_DCH state, it allows the network to indicate to the UE about the DSAC and PPAC parameters through dedicated signalling so that the UE can obtain the updated DSAC and PPAC information.
+
+# 9 Enhanced Broadcast of System Information
+
+## 9.1 Second system information broadcast channel
+
+In order to increase system information capacity (see TR 25.704 [7]) a second system information broadcast channel on SCCPCH can be configured, in addition to the system information broadcast channel on PCCPCH.
+
+The second system information broadcast channel is mapped to a separate SCCPCH, which is different from the SCCPCH used for paging and FACH/CTCH, as depicted in Figure 9.1-1.
+
+![Figure 9.1-1: Channel mapping of system information broadcast channel and second system information broadcast channel. The diagram shows the mapping from Logical channels to Transport channels and then to Physical channels. Logical channels include PCCH, a group of CCCH, CTCH (CBS), DCCH, and DTCH, and BCCH. Transport channels include PCH, FACH, and BCH. Physical channels include PICH, SCCPCH, and PCCPCH. The mapping is as follows: PCCH maps to PCH, which maps to PICH and SCCPCH. CCCH, CTCH (CBS), DCCH, and DTCH map to FACH, which maps to SCCPCH. BCCH maps to BCH, which maps to SCCPCH and PCCPCH. Two dashed ovals highlight the mapping of BCH to SCCPCH (labeled 'Second system information broadcast channel 'BCH on SCCPCH'') and BCH to PCCPCH (labeled 'System information broadcast channel 'BCH on PCCPCH'').](cd48273072c5c3a23e11fde892d1b6b6_img.jpg)
+
+Figure 9.1-1: Channel mapping of system information broadcast channel and second system information broadcast channel. The diagram shows the mapping from Logical channels to Transport channels and then to Physical channels. Logical channels include PCCH, a group of CCCH, CTCH (CBS), DCCH, and DTCH, and BCCH. Transport channels include PCH, FACH, and BCH. Physical channels include PICH, SCCPCH, and PCCPCH. The mapping is as follows: PCCH maps to PCH, which maps to PICH and SCCPCH. CCCH, CTCH (CBS), DCCH, and DTCH map to FACH, which maps to SCCPCH. BCCH maps to BCH, which maps to SCCPCH and PCCPCH. Two dashed ovals highlight the mapping of BCH to SCCPCH (labeled 'Second system information broadcast channel 'BCH on SCCPCH'') and BCH to PCCPCH (labeled 'System information broadcast channel 'BCH on PCCPCH'').
+
+Figure 9.1-1: Channel mapping of system information broadcast channel and second system information broadcast channel.
+
+The UE should be able to monitor at least two SCCPCHs simultaneously, but the UE may skip reading the second system information broadcast channel during CTCH occasions in Idle mode and CELL\_PCH/URA\_PCH state. When HS-DSCH in CELL\_FACH is used, a UE supporting second system information broadcast channel monitors the corresponding SCCPCH while listening to HS-DSCH.
+
+REL-12 and later SIBs are introduced on both the system information broadcast channel as well as the second system information broadcast channel. Pre-REL-12 SIBs may be broadcasted on the second system information broadcast channel in addition to the system information broadcast channel. Any SIB type may be scheduled simultaneously on system information broadcast channel and second system information broadcast channel provided that the content is the same.
+
+Most of the existing principles and procedures for system information reading are retained for the second system information broadcast channel. To reduce the latency to acquire the system information on both system information broadcast channel and second system information broadcast channel, the UE acquires the system information on both channels simultaneously. The simultaneous acquisition of system information on both system information broadcast channel and second system information broadcast channel is depicted in Figure 9.1-2.
+
+![Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel. The diagram shows two horizontal timelines representing broadcast channels. The top timeline is the 'System information broadcast channel (BCH on PCCPCH)' and contains blocks for MIB (red), SB1 (orange), SIBx (yellow), and SIBy (green). The bottom timeline is the 'Second system information broadcast channel (BCH on SCCPCH)' and contains blocks for SB3 (orange), SIBa (yellow), and SIBb (green). A 'Paging / SICI message with MIB value tag and SB3 value tag' is shown on the left, with arrows pointing to the MIB and SB3 blocks. A 'UE' label is at the bottom left. Arrows indicate the UE's acquisition process: one arrow points from the UE to the MIB, another from the MIB to the SB1, and a third from the SB3 to the SIBa and SIBb blocks.](5e92d9e8e9ce204e405bff2367f88176_img.jpg)
+
+Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel. The diagram shows two horizontal timelines representing broadcast channels. The top timeline is the 'System information broadcast channel (BCH on PCCPCH)' and contains blocks for MIB (red), SB1 (orange), SIBx (yellow), and SIBy (green). The bottom timeline is the 'Second system information broadcast channel (BCH on SCCPCH)' and contains blocks for SB3 (orange), SIBa (yellow), and SIBb (green). A 'Paging / SICI message with MIB value tag and SB3 value tag' is shown on the left, with arrows pointing to the MIB and SB3 blocks. A 'UE' label is at the bottom left. Arrows indicate the UE's acquisition process: one arrow points from the UE to the MIB, another from the MIB to the SB1, and a third from the SB3 to the SIBa and SIBb blocks.
+
+**Figure 9.1-2: System information acquisition on system information broadcast channel and second system information broadcast channel.**
+
+When the SB3 value tag in PAGING TYPE 1 or SYSTEM INFORMATION CHANGE INDICATION (SICI) message is updated the UE supporting second system information broadcast channel is required to re-acquire the system information on the second system information broadcast channel. When the SB3 value tag is updated, but the MIB value tag is not, the UE supporting second system information broadcast channel is only required to re-acquire the system information on the second system information broadcast channel.
+
+The scheduling block 3 (SB3) contains the scheduling information for the system information on the second system information broadcast channel. This scheduling information uses the SFN of the PCCPCH.
+
+The SB3 is broadcasted with a pre-defined offset (40 ms) from the start of the frame containing the MIB, as depicted in the Figure 9.1-3. The MIB on BCH mapped on PCCPCH contains the channelization code of the second system information broadcast channel, the repetition interval of SB3 and the number of segments of SB3. The remaining configuration parameters of the second system information broadcast channel are pre-defined.
+
+![Diagram illustrating the scheduling of System Information Blocks (SIBs). The top timeline shows the System information broadcast channel (BCH on PCCPCH) with a periodicity of 80 ms. The MIB is shown as a red block, followed by SIB1 (orange block), and then other SIBs (red blocks). The bottom timeline shows the Second system information broadcast channel (BCH on SCCPCH) with a periodicity of 40 ms. SIB3 (orange block) is shown with a pre-defined offset from the start of the frame containing the MIB.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+The diagram shows two horizontal timelines representing broadcast channels. The top timeline is labeled 'System information broadcast channel (BCH on PCCPCH)' and has a periodicity of 'MIB interval 80 ms'. It shows a red block labeled 'MIB' followed by an orange block labeled 'SB1' (SIB1), and then several red blocks. The bottom timeline is labeled 'Second system information broadcast channel (BCH on SCCPCH)' and has a periodicity of '40 ms'. It shows an orange block labeled 'SB3' (SIB3). A vertical dashed line connects the start of the MIB block on the top timeline to the start of the SB3 block on the bottom timeline, indicating a pre-defined offset.
+
+Diagram illustrating the scheduling of System Information Blocks (SIBs). The top timeline shows the System information broadcast channel (BCH on PCCPCH) with a periodicity of 80 ms. The MIB is shown as a red block, followed by SIB1 (orange block), and then other SIBs (red blocks). The bottom timeline shows the Second system information broadcast channel (BCH on SCCPCH) with a periodicity of 40 ms. SIB3 (orange block) is shown with a pre-defined offset from the start of the frame containing the MIB.
+
+**Figure 9.1-3: SB3 pre-defined offset from the start of the frame containing the MIB.**
+
+## 9.2 Scheduling information overhead reduction
+
+To reduce the overhead of SIB scheduling information, included in MIB and Scheduling Blocks, the network may use mandatory default values for SIB\_OFF and SEG\_COUNT (when SIB\_POS offset info is included) for SIBs of REL-12 or later.
+
+## 9.3 MIB and Cell Value Tag range extension
+
+To reduce the risk of Cell Value Tag wrap around, the network may broadcast a range extension (1..16) of the Cell Value Tag for SIB3, SIB5, SIB5bis, SIB21 and SIB22. The network may also extend the MIB value tag range (1..16). For UEs supporting these extensions the SIBs and MIB wrap around at 16, while for UEs not supporting this feature the SIBs wraps around at 4 (and MIB at 8). SIBs of REL-12 or later use the extended Cell Value Tag range (1..16).
+
+# 10 RAN assisted WLAN interworking
+
+This clause describes the mechanisms to support traffic steering between UTRAN and WLAN.
+
+## 10.1 General principles
+
+This version of the specification supports UTRAN assisted UE based bi-directional traffic steering between UTRAN and WLAN for UEs in Idle mode and CELL\_DCH, CELL\_FACH, CELL\_PCH and URA\_PCH states.
+
+UTRAN provides assistance parameters via broadcast and dedicated RRC signalling to the UE. The RAN assistance parameters may include UTRAN signal strength thresholds, WLAN channel utilization thresholds, WLAN backhaul data rate thresholds, WLAN signal strength thresholds and Offload Preference Indicator (OPI). UTRAN can also provide a list of WLAN identifiers to the UE via broadcast and dedicated signalling.
+
+The UE uses the RAN assistance parameters in the evaluation of:
+
+- access network selection and traffic steering rules defined in TS 25.304 [9]; or
+- ANDSF policies defined in TS 24.312 [8]
+
+for traffic steering decisions between UTRAN and WLAN as specified in TS 23.402 [10].
+
+The OPI is only used in ANDSF policies as specified in TS 24.312 [8].
+
+WLAN identifiers are only used in access network selection and traffic steering rules defined in TS 25.304 [9].
+
+If the UE is provisioned with ANDSF policies it shall forward the received RAN assistance parameters to upper layers, otherwise it shall use them in the access network selection and traffic steering rules defined in subclause 10.2 and TS 25.304 [9]. The access network selection and traffic steering rules defined in subclause 10.2 and TS 25.304 [9] are applied only to the WLANs of which identifiers are provided by the UTRAN.
+
+The UE in CELL\_DCH state shall apply the parameters obtained via dedicated signalling, and shall keep those parameters during handover if they are not reconfigured or deleted; the UE shall discard the parameters obtained via dedicated signalling at SRNS relocation.
+
+The UE in CELL\_FACH state shall apply the parameters obtained via dedicated signalling if such have been received from the serving cell; otherwise the UE shall apply the parameters obtained via broadcast signalling. Upon cell selection/reselection the UE shall discard the dedicated parameters.
+
+The UE in Idle mode, CELL\_PCH or URA\_PCH state shall keep and apply the parameters obtained via dedicated signalling until selection/reselection of another cell than the one where these parameters were received or a timer has expired since the UE moved from CELL\_DCH or CELL\_FACH to Idle mode, CELL\_PCH or URA\_PCH state, upon which the UE shall discard the dedicated parameters and apply the parameters obtained via broadcast signalling.
+
+In the case of RAN sharing, each PLMN sharing the RAN can broadcast independent sets of RAN assistance parameters.
+
+## 10.2 Access network selection and traffic steering rules
+
+The UE indicates to upper layers when (and for which WLAN identifiers) access network selection and traffic steering rules defined in TS 25.304 [9] are fulfilled. The selection among WLANs that fulfil the access network selection and traffic steering rules is up to UE implementation.
+
+When the UE applies the access network selection and traffic steering rules defined in TS 25.304 [9], higher layers perform traffic steering between UTRAN and WLAN.
+
+# 11 Increased minimum number of carriers to monitor
+
+The increased number of carrier monitoring feature allows a UE to monitor more UMTS and LTE frequencies in all RRC states.
+
+When increased carrier monitoring is used, the network signals whether a carrier should be measured with "reduced measurement performance" together with a scaling factor applicable for CELL\_DCH and CELL\_FACH states. In Idle mode, CELL\_PCH and URA\_PCH states a fixed scaling factor is used. When a carrier does not belong to the "reduced measurement performance" group, it belongs to the "normal measurement performance" group.
+
+The value and the use of scaling factor are specified in [11].
+
+# 12 Extended DRX in Idle mode
+
+The extended DRX (eDRX) feature enables DRX 10,24 seconds up to 2621.44 seconds (~44 minutes) in Idle mode for the PS domain.
+
+The eDRX feature in Idle mode uses the Paging Occasions (PO) as determined by the CN domain specific DRX cycle length coefficient (PS domain) in SIB1 [12] and specified by the Discontinuous Reception for Paging [9]. However the UE is not required to monitor every PO, but only the POs that belong to the Paging Transmission Window (PTW):
+
+![Diagram illustrating Extended DRX in Idle mode. It shows a timeline with a 'Sleep period' of duration T_eDRX, followed by a 'Paging Transmission Window (PTW)' of duration T_PTW. Inside the PTW, there are four 'PO' (Paging Occasion) markers. The 'PS DRX cycle' is indicated as the interval between the start of one PTW and the start of the next.](ea37ab05b033e59cfdf7b074161aaf5a_img.jpg)
+
+The diagram shows a horizontal timeline representing time. A long green bar represents the 'Sleep period' with a duration labeled  $T_{eDRX}$ . This is followed by an orange bar representing the 'Paging Transmission Window (PTW)' with a duration labeled  $T_{PTW}$ . Within the PTW, there are four yellow boxes labeled 'PO' (Paging Occasion). A dashed line with arrows at both ends indicates the 'PS DRX cycle', which is the time interval from the start of one PTW to the start of the next.
+
+Diagram illustrating Extended DRX in Idle mode. It shows a timeline with a 'Sleep period' of duration T\_eDRX, followed by a 'Paging Transmission Window (PTW)' of duration T\_PTW. Inside the PTW, there are four 'PO' (Paging Occasion) markers. The 'PS DRX cycle' is indicated as the interval between the start of one PTW and the start of the next.
+
+**Figure 12-1: Extended DRX in Idle mode**
+
+The eDRX parameter in Idle mode values, i.e. timer values for  $T_{eDRX}$  and  $T_{PTW}$  are negotiated and configured during ATTACH and RAU procedure ([4] and [5]). Timer  $T_{eDRX}$  is (re-)started when upper layers indicate successful completion of the ATTACH/RAU procedure, including eDRX parameters in Idle mode. When timer  $T_{eDRX}$  expires, the UE wakes-up from sleep, it checks the MIB for any system information changes and it starts monitoring the paging occasions in the PS DRX in Idle mode. When timer  $T_{eDRX}$  expires it is re-started, and timer  $T_{PTW}$  is started. When timer  $T_{PTW}$  expires the UE stops monitoring paging occasions in the PS DRX in Idle mode. The timer  $T_{eDRX}$  and  $T_{PTW}$  do not stop/reset when the UE transitions from Idle to Connected or transitions from Connected to Idle. The timers  $T_{eDRX}$  and  $T_{PTW}$  are stopped, if running, when upper layer indicates that the eDRX parameters in Idle mode are not included in the ATTACH/RAU complete. The timers  $T_{eDRX}$  and  $T_{PTW}$  are reset when upper layer indicates that a new value is configured in ATTACH/RAU complete. The value of  $T_{eDRX}$  is signaled in IE “eDRX value” in ATTACH/RAU [4] for timer T331 in RRC [12]. The value of  $T_{PTW}$  is signaled in IE “Paging Time Window” in ATTACH/RAU [4] for timer T332 in RRC [12].
+
+# --- 13 L2 and L3 Downlink enhancements for UMTS
+
+## 13.1 Retrievable configurations
+
+The retrievable configurations feature allows the UE to store configurations together with an identity. When the network invokes a retrievable configuration, it needs to signal only its identity. A retrievable configuration can be signalled to a UE in any state except for idle. Retrievable configurations are cleared when entering idle mode and at SRNS relocation.
+
+There are two ways of signalling the retrievable configurations: one way is that as a result of an RRC signalling procedure, the UE stores the received configuration as a retrievable configuration, and the other way is that the network preconfigures the UE with at least one retrievable configuration. The network can signal a delta to a stored configuration for either of the two ways. The UE validates a retrievable configuration when it invokes it.
+
+## 13.2 URA\_PCH with seamless transition
+
+The feature URA\_PCH with seamless transition to CELL\_FACH is described in 3GPP TS 25.319 [3].
+
+## 13.3 Optimization from IDLE to CONNECTED state
+
+If the UE supports "NodeB triggered HS-DPCCH transmission", the RNC can issue the indication to trigger acquisition of the common E-DCH resource or to release the allocated common E-DCH resource for the particular UE.
+
+## 13.4 Blind HARQ retransmissions for HSDPA
+
+The feature blind HARQ retransmissions for HSDPA is described in 3GPP TS 25.308 [2].
+
+## 13.5 Enhanced state transition
+
+This feature allows the UE to move to a more power efficient state without explicit RRC reconfiguration. The UE sends the RRC indication to the RNC and moves to the target state upon reception of the RLC ACK from the RNC. The state transition is applicable to the following cases: from CELL\_DCH to CELL\_FACH, from CELL\_FACH to CELL\_PCH/URA\_PCH, and from CELL\_DCH to CELL\_PCH/URA\_PCH.
+
+While configuring a UE with enhanced state transition, the RNC can provide RRC configuration that will be applied once the UE enters the target state.
+
+## 13.6 Improved synchronized RRC procedures
+
+In improved synchronized RRC procedures, firstly the UE receives an RRC reconfiguration message for a synchronized RRC procedure indicating that the activation time shall be dynamically determined. Then, when the UE is ready to switch to the new configuration indicated in the RRC message, it sends a MAC Control Information to the Node B. On reception of the HARQ ACK to the MAC Control Information, the UE calculates the activation time by adding an offset to the current CFN. The UE reconfigures at the calculated activation time and sends an RRC configuration complete message upon successful completion of the procedure.
+
+The network can also indicate a legacy activation time, at which the switch to the new configuration latest shall occur. The UE will choose the smallest value of the legacy activation time and the calculated activation time as the final activation time.
+
+# --- 14 Downlink TPC enhancements for UMTS
+
+In CELL\_DCH state, the network can configure a UE with power control Algorithm 3 when the F-DPCH is also configured. For this algorithm, the TPC command is transmitted only once in a certain number of consecutive slots, and other TPC commands are DTXed in the remaining slots. The number of consecutive slots can be configured with 3 or 5 slots.
+
+If a UE is configured with Algorithm 3 on any of the radio links, then all the radio links within the same RLS must have power control Algorithm 3. If power control Algorithm 3 is configured in one RLS, and any of the legacy algorithms is configured in another RLS, then the UE will behave as per Algorithm 3 to determine transmission power under such configuration.
+
+For generation of TPC in uplink DPCCH, the UE will generate and transmit TPC command as per the algorithm configured on the serving radio link.
+
+# --- 15 NAICS offloading (FDD only)
+
+In this offloading mechanism, the UE is configured with the Multiflow operation 3GPP TS 25.308 [2], which allows the UE to measure and send CQIs for cells belonging to a different Node B. Based on received channel quality information, the UE can be offloaded from the serving Node B HS-DSCH cell(s) to HS-DSCH cell(s) belonging to a different Node B through the network specific behaviour, e.g. serving cell change procedure.
+
+# --- 16 ACDC in Idle Mode
+
+The ACDC feature allows network to control new PS domain access attempts from particular applications in the UE in idle mode to prevent/mitigate overload of the access network and/or the core network.
+
+The applications on the UE may be associated with an ACDC category. At subscription, at least four ACDC categories, and up to 16 ACDC categories, are allocated to the subscriber and stored in the ACDC Management Object (MO) or USIM [9].
+
+The access barring information for each ACDC category is broadcast in SIB. The ACDC capable UE controls the access attempt for a certain application based on the broadcast barring information and the configuration of ACDC categories in the UE.
+
+The following guidelines define the behaviour of a UE configured with ACDC when other access control mechanisms (ACB, EAB and DSAC) are co-existing:
+
+- When DSAC and ACDC are configured together, the PS domain DSAC will be ignored by the UEs.
+- When EAB and ACDC are configured together, the UE will first check EAB and then check ACDC.
+- For UEs configured with ACDC, ACB is ignored.
+
+# --- 17 RRC optimization
+
+## 17.1 RRC measurement events for UPH reporting
+
+The RRC measurement events for UPH reporting allow the UE to perform measurements on UE Power Headroom (UPH) and signal measurement events when the UPH becomes larger or less than an absolute threshold respectively. The thresholds are configurable, as well as hysteresis, time-to-trigger, filter coefficient and pending time after trigger for each of the events.
+
+## 17.2 Simultaneous Setup and Release of RABs and RBs
+
+The simultaneous setup and release of RABs and RBs enhancement allows setup, release and reconfiguration of radio access bearers and radio bearers in the same RRC message.
+
+# --- 18 HS-SCCH DRX in CELL\_FACH state (FDD only)
+
+With the feature HS-SCCH DRX in CELL\_FACH state, the UE discontinuously receives only HS-SCCH orders without decoding HS-DSCH in CELL\_FACH state. Details could be referred in 3GPP TS 25.308 [2].
+
+# --- 19 Dual Cell E-DCH operation enhancements
+
+This feature Dual Cell E-DCH operation enhancements is described in 3GPP TS 25.319 [3].
+
+# --- 20 QoE Measurement Collection
+
+With this feature, the network can configure collection of measurements from the UE. The feature defines QoE measurement configuration and measurement reporting containers, and the feature uses the MDT framework [14]. QoE measurement configuration received from OAM or CN is encapsulated in a container, which is inserted in a Measurement Control message and forwarded to the UE transparently. QoE measurements received from UE higher layer are inserted in a container in a Measurement Report message and sent over SRB4.
+
+The supported service types for QoE Measurement Collection are QoE Measurement Collection for streaming services and QoE Measurement Collection for MTSI services.
+
+The QoE measurement configuration is supported in CELL\_DCH and CELL\_FACH states, whereas the QoE measurement reporting is supported in CELL\_DCH state only.
+
+Both signalling based and management based initiation cases are allowed. For the signalling based case, the QoE Measurement Collection is initiated towards a specific UE from CN nodes using the MDT mechanism as described in clause 5.1.3 [14]; for the management based case, the QoE Measurement Collection is initiated from OAM targeting an area (without targeting a specific UE).
+
+# --- 21 DL Interference Mitigation (FDD only)
+
+The feature DL interference mitigation enables the UE to receive an indication about a potential increase in the DL adjacent channel interference level (e.g. due to adjacent GSM carriers). The corresponding signalling indication is conveyed in broadcast messages SIB5, SIB5bis and SIB6. The UE may use this indication to mitigate the DL interference, e.g. by using optimized Rx filtering.
+
+# --- 22 Simplified HS-SCCH type 1 operation
+
+This feature Simplified HS-SCCH type 1 operation is described in 3GPP TS 25.308 [2].
+
+# --- 23 NR SRVCC to UTRAN
+
+The feature NR SRVCC to UTRAN enables a UE to perform a SRVCC procedure from NR only to UTRAN FDD. The SRVCC architecture and signalling flow have been defined in TS 23.216 [15]. In TS 38.300 [16], inter-RAT mobility procedure on NR SRVCC to UTRAN FDD has been defined. The UE receives in the handover to UTRAN command security information which is used to derive both ciphering and integrity protection keys for operation in UTRAN, as specified in TS 38.300 [16]. During the handover, as specified in TS 25.413 [17], the target RNC node receives the SRVCC source RAT indication from the source NR node. After the UE completes the IMS voice service in UTRAN FDD, the security mode control procedure is performed to activate the integrity protection for the voice service in the CS domain. When and how to perform the return procedure from UTRAN to NR after the UE completes the voice service depends on UE implementation.
+

marked/Rel-17/25_series/25307/raw.md

@@ -0,0 +1,242 @@
+
+
+
+
+
+
+# Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 Definitions and abbreviations ..... 5
+
+3.1 Definitions..... 5
+
+3.2 Abbreviations ..... 5
+
+3A General ..... 5
+
+4 Void..... 6
+
+5 Void..... 6
+
+6 Void..... 6
+
+7 Void..... 6
+
+8 Void..... 6
+
+9 Void..... 6
+
+10 Void..... 6
+
+11 Void..... 6
+
+12 Void..... 6
+
+13 Void..... 6
+
+14 Void..... 6
+
+15 Void..... 7
+
+16 Void..... 7
+
+17 Void..... 7
+
+18 Void..... 7
+
+19 Void..... 7
+
+20 Void..... 7
+
+21 Void..... 7
+
+22 Void..... 7
+
+23 Void..... 7
+
+24 Void..... 7
+
+25 Void..... 7
+
+**Annex A (normative): Void..... 9**
+
+**Annex B (normative): Frequency arrangement for overlapping operating bands ..... 10**
+
+Annex C (informative): Change history..... 11
+
+# --- Foreword
+
+This Technical Specification 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 specifies requirements on UEs supporting a frequency band that is independent of release.
+
+# --- 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] to [29] Void.
+
+[30] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)".
+
+[31] 3GPP TS 25.102: "UE Radio Transmission and Reception (TDD)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [1] apply.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                           |
+|-----|---------------------------|
+| FDD | Frequency Division Duplex |
+| RRC | Radio Resource Control    |
+| UE  | User Equipment            |
+
+# --- 3A General
+
+TSG-RAN has agreed that the standardisation of new frequency bands may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band of operation that is specified in a later release, it is necessary to specify some extra requirements.
+
+For example, Band III is contained in the Release 5 specifications. In order to implement a UE conforming to Release '4 but supporting Band III, it is necessary for the UE to additionally conform to some parts of the Release 5 specifications, such as the radio frequency requirements for the Band III and some signalling extensions relating to the UE radio access capabilities.
+
+NOTE: See NOTE in clause 4.4 in [30] or [31].
+
+# --- 4 Void
+
+---
+
+5 Void
+
+---
+
+6 Void
+
+---
+
+7 Void
+
+---
+
+8 Void
+
+---
+
+9 Void
+
+---
+
+10 Void
+
+---
+
+11 Void
+
+---
+
+12 Void
+
+---
+
+13 Void
+
+---
+
+14 Void
+
+---
+
+15 Void
+
+---
+
+16 Void
+
+---
+
+17 Void
+
+---
+
+18 Void
+
+---
+
+19 Void
+
+---
+
+20 Void
+
+---
+
+21 Void
+
+---
+
+22 Void
+
+---
+
+23 Void
+
+---
+
+24 Void
+
+---
+
+25 Void
+
+# --- Annex A (normative): Void
+
+# Annex B (normative): Frequency arrangement for overlapping operating bands
+
+The following information is provided in order to assist a UE to derive the DL UARFCN and UL UARFCN in a multi-band environment, in which multiple overlapping operating bands may be indicated in the IE "Multiple Frequency Band indicator list" (System Information Block type 5, System Information Block type 5bis and System Information Block type 6), or the IE "Multiple Frequency Info List FDD" (System Information Block type 11, System Information Block type 11bis and System Information Block type 12).
+
+The sets of bands (multi-band environment), independent of release, that may be indicated in a cell are shown in Table B-1. Subsets of these may also be indicated. The DL UARFCN and UL UARFCN are derived according to [25.101].
+
+**Table B-1: Overlapping bands (multi-band environments) for each UTRA band**
+
+| UTRA Operating Band | Overlapping UTRA operating bands | Duplex Mode |
+|---------------------|----------------------------------|-------------|
+| 2                   | 25                               | FDD         |
+| 3                   | 9                                | FDD         |
+| 4                   | 10                               | FDD         |
+| 5                   | 18, 19, 26                       | FDD         |
+| 9                   | 3                                | FDD         |
+| 10                  | 4                                | FDD         |
+| 18                  | 5, 26                            | FDD         |
+| 19                  | 5, 26                            | FDD         |
+| 25                  | 2                                | FDD         |
+| 26                  | 5, 18, 19                        | FDD         |
+

marked/Rel-17/25_series/25324/raw.md

@@ -0,0 +1,909 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                   |    |
+|-------------------------------------------------------------------|----|
+| Foreword .....                                                    | 5  |
+| 1 Scope.....                                                      | 6  |
+| 2 References.....                                                 | 6  |
+| 3 Definitions and abbreviations .....                             | 6  |
+| 3.1 Definitions.....                                              | 6  |
+| 3.2 Abbreviations .....                                           | 7  |
+| 4 General.....                                                    | 7  |
+| 4.1 Model of BMC .....                                            | 7  |
+| 5 Functions.....                                                  | 8  |
+| 6 Services provided to Upper Layers.....                          | 8  |
+| 7 Services expected from RLC .....                                | 9  |
+| 8 Elements for layer-to-layer communication .....                 | 9  |
+| 8.1 Service Primitives between RRC and BMC .....                  | 9  |
+| 8.1.1 Primitives.....                                             | 9  |
+| 8.1.1.1 CBMC-Measurement-IND .....                                | 9  |
+| 8.1.1.2 CBMC-Rx-IND .....                                         | 9  |
+| 8.1.1.3 CBMC-Config-REQ .....                                     | 10 |
+| 8.1.2 Parameters .....                                            | 10 |
+| 8.1.2.1 CB-Traffic-Volume .....                                   | 10 |
+| 8.1.2.2 Action.....                                               | 10 |
+| 8.1.2.3 DRX selection.....                                        | 10 |
+| 8.1.2.4 CTCH configuration .....                                  | 10 |
+| 8.2 Service Primitives between upper layer (U-plane) and BMC..... | 11 |
+| 8.2.1 Primitives.....                                             | 11 |
+| 8.2.1.1 Primitives used in relation to UMTS Core Network .....    | 11 |
+| 8.2.1.1.1 BMC-Data-REQ.....                                       | 11 |
+| 8.2.1.1.2 BMC-Data-IND.....                                       | 12 |
+| 8.2.1.1.3 BMC-Data-CNF .....                                      | 12 |
+| 8.2.1.1.4 BMC-Congestion-IND .....                                | 12 |
+| 8.2.1.1.5 BMC-Normal-IND .....                                    | 12 |
+| 8.2.1.1.6 BMC-Activation-REQ .....                                | 12 |
+| 8.2.1.1.7 BMC-Deactivation-REQ.....                               | 12 |
+| 8.2.1.1.8 BMC-DRX-REQ.....                                        | 13 |
+| 8.2.1.1.9 BMC-Error-IND.....                                      | 13 |
+| 8.2.1.2 Primitives used for ANSI-41 Core Network.....             | 13 |
+| 8.2.1.2.1 BMC-Data41-REQ.....                                     | 13 |
+| 8.2.1.2.2 BMC-Data41-IND.....                                     | 13 |
+| 8.2.1.2.3 BMC-Error41-IND.....                                    | 13 |
+| 8.2.2 Parameters .....                                            | 14 |
+| 8.2.2.1 Message-ID.....                                           | 14 |
+| 8.2.2.2 Serial Number .....                                       | 14 |
+| 8.2.2.3 Data-Coding-Scheme.....                                   | 14 |
+| 8.2.2.4 CB-Data .....                                             | 14 |
+| 8.2.2.5 Category.....                                             | 14 |
+| 8.2.2.6 Repetition-Period .....                                   | 14 |
+| 8.2.2.7 Number-of-Broadcasts-Requested.....                       | 14 |
+| 8.2.2.8 CB-DRX-Schedule-Period.....                               | 14 |
+| 8.2.2.9 Reserved-CB-Capacity .....                                | 15 |
+| 8.2.2.10 Cause.....                                               | 15 |
+| 8.2.2.11 Transport Layer Message.....                             | 15 |
+| 8.2.2.12 Broadcast Address .....                                  | 15 |
+| 8.2.2.13 Error Type.....                                          | 15 |
+
+|                        |                                           |    |
+|------------------------|-------------------------------------------|----|
+| 9                      | Procedures.....                           | 15 |
+| 9.1                    | BMC Message Broadcast.....                | 15 |
+| 9.2                    | Generation of Schedule message.....       | 15 |
+| 9.3                    | Traffic volume measurement .....          | 16 |
+| 9.4                    | BMC message reception.....                | 16 |
+| 10                     | BMC Messages .....                        | 17 |
+| 10.1                   | General .....                             | 17 |
+| 10.2                   | BMC CBS Message .....                     | 17 |
+| 10.3                   | BMC Schedule Message .....                | 17 |
+| 10.4                   | BMC CBS41 Message .....                   | 18 |
+| 11                     | Information Elements.....                 | 19 |
+| 11.1                   | Message Type.....                         | 19 |
+| 11.2                   | Message ID.....                           | 19 |
+| 11.3                   | Serial Number .....                       | 19 |
+| 11.4                   | Data Coding Scheme.....                   | 20 |
+| 11.5                   | CB Data.....                              | 20 |
+| 11.6                   | Offset to Begin CTCH Block Set Index..... | 20 |
+| 11.7                   | Length of CBS Schedule Period.....        | 21 |
+| 11.8                   | New Message Bitmap.....                   | 21 |
+| 11.9                   | Message Description .....                 | 22 |
+| 11.10                  | Broadcast Address.....                    | 23 |
+| 11.11                  | CB Data41 .....                           | 23 |
+| 11.12                  | CBS Schedule Message Extension.....       | 24 |
+| 11.13                  | CBS Message Serial Numbers .....          | 24 |
+| 11.14                  | Serial Number List Entry .....            | 25 |
+| Annex A (informative): | Change history.....                       | 26 |
+
+# --- Foreword
+
+This Technical Specification (TS) 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 provides the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface.
+
+# --- 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 TS 25.322: "RLC Protocol Specification".
+- [2] 3GPP TS 25.301: "Radio Interface Protocol Architecture".
+- [3] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
+- [4] 3GPP TS 23.038: "Alphabets and Language".
+- [5] 3GPP TS 25.419: "UTRAN Iu interface: Service Area Broadcast Protocol SABP".
+- [6] 3GPP TS 25.925: "Radio Interface for Broadcast/Multicast Services".
+- [7] TIA/EIA-41-D: "Technical realization of Cell Broadcast Service (CBS)".
+- [8] TIA/EIA-637-A: "TR45 – Short Message Service for Spread Spectrum Systems".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**CB message:** user data as transmitted from Cell Broadcast Centre to UE (BMC SDU)
+
+**CB repetition period:** period after which a CB message should be broadcast again if more than one repetition are requested
+
+**Number of Broadcast Requested:** number of broadcasts requested for a CB message. This number is infinite or finite
+
+**DRX Schedule Period:** schedule period as optionally requested by the CBC (unit: seconds)
+
+**Reserved CB Capacity:** percentage of the capacity reserved for CB messages with category HIGH on the allocated radio resources CTCH, FACH and S-CCPCH. This parameter can be set optionally by the CBC.
+
+**CTCH Block Set:** subset of the transport block set of FACH on which the CTCH used for CBS is mapped uniquely
+
+**CBS schedule period:** finite sequence of CTCH Block Sets of variable length in which scheduled CB messages are broadcast
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                             |
+|-----|-----------------------------|
+| AS  | Access Stratum              |
+| BMC | Broadcast/Multicast Control |
+
+|         |                                    |
+|---------|------------------------------------|
+| C-SAP   | Control Service Access Point       |
+| CBC     | Cell Broadcast Centre              |
+| CBS     | Cell Broadcast Service             |
+| CTCH    | Common Traffic Channel             |
+| CTCH-BS | CTCH Block Set                     |
+| FACH    | Forward Access Channel             |
+| IE      | Information Element                |
+| kbps    | kilo-bits per second               |
+| L1      | Layer 1 (physical layer)           |
+| L2      | Layer 2 (data link layer)          |
+| L3      | Layer 3 (network layer)            |
+| MAC     | Medium Access Control              |
+| NAS     | Non Access Stratum                 |
+| NSAPI   | Network layer Service Access Point |
+| PDCP    | Packet Data Convergence Protocol   |
+| RLC     | Radio Link Control                 |
+| RRC     | Radio Resource Control             |
+| UE      | User Equipment                     |
+
+# --- 4 General
+
+## 4.1 Model of BMC
+
+Broadcast/Multicast Control (BMC) is a sublayer of L2 that exists in the User-Plane only. It is located above RLC. The L2/BMC sublayer is assumed as transparent for all services except broadcast/multicast.
+
+Figure 4.1-1 shows the model of the L2/BMC sublayer within the UTRAN radio interface protocol architecture.
+
+At the UTRAN side, the BMC sublayer shall consist of one BMC protocol entity per cell. Each BMC entity requires a single CTCH, which is provided by the MAC sublayer, through the RLC sublayer. The BMC requests the Unacknowledged Mode service of the RLC.
+
+It is assumed that there is a function in the RNC above BMC that resolves the geographical area information of the CB message (or, if applicable, performs evaluation of a cell list) received from the Cell Broadcast Centre (CBC). A BMC protocol entity serves only those messages at BMC-SAP that are to be broadcast into a specified cell.
+
+![Figure 4.1-1: BMC protocol model diagram](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the BMC protocol model. At the top, a dashed box labeled 'user-plane' is connected to an oval labeled 'BMC-SAP'. Below 'BMC-SAP' is a grey rectangular box labeled 'L2/BMC sublayer', which contains a white rectangular box labeled 'BMC'. To the left of the 'L2/BMC sublayer' box, an oval labeled 'CBMC-SAP' is connected to a grey rectangular box labeled 'RRC'. Below the 'L2/BMC sublayer' box is an oval labeled 'UM'. Below 'UM' is another grey rectangular box labeled 'L2/RLC sublayer', which contains a white rectangular box labeled 'RLC'. At the bottom of the 'L2/RLC sublayer' box is an oval labeled 'CTCH-SAP'.
+
+Figure 4.1-1: BMC protocol model diagram
+
+Figure 4.1-1: BMC protocol model
+
+# 5 Functions
+
+The functions are specified in [2]. They are:
+
+- Storage of Cell Broadcast Messages.
+- Traffic volume monitoring and radio resource request for CBS.
+- Scheduling of BMC messages.
+- Transmission of BMC messages to UE.
+- Delivery of Cell Broadcast messages to upper layer (NAS).
+
+# 6 Services provided to Upper Layers
+
+The BM-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in unacknowledged mode.
+
+The BMC sublayer interacts with other entities as illustrated in figure 1 of chapter 4. The interactions with the upper layer/U-plane and the RRC layer are specified in terms of primitives where the primitives represent the logical exchange of information and control between the BMC sublayer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points (SAPs).
+
+Three types of primitives are used for this document, as follows:
+
+- **REQUEST:**  
+This type is used when a higher layer is requesting a service from a lower layer.
+- **INDICATION:**  
+This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer.
+
+###### - **CONFIRM:**
+
+This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed.
+
+The primitives defined below are for communications between upper layer and BMC, as well as RRC and BMC in the same protocol stack.
+
+For the BMC sublayer two sets of primitives are defined.
+
+### - **Primitives between BMC and upper layer (U-plane):**
+
+BMC - Generic name - Type: Parameters.
+
+### - **Primitives between BMC and the RRC entity:**
+
+CBMC - Generic name - Type: Parameters.
+
+# 7 Services expected from RLC
+
+The BMC uses the unacknowledged mode service of the RLC sublayer.
+
+See [1] for details.
+
+# 8 Elements for layer-to-layer communication
+
+## 8.1 Service Primitives between RRC and BMC
+
+### 8.1.1 Primitives
+
+The primitives supported at CBMC-SAP between RRC and BMC are shown in Table 8.1.1-1.
+
+**Table 8.1.1-1: Primitives between BMC and RRC**
+
+| Generic Name         | Parameters            |
+|----------------------|-----------------------|
+| CBMC-Measurement-IND | CB-Traffic-Volume     |
+| CBMC-Rx-IND          | Action, DRX selection |
+| CBMC-Config-REQ      | CTCH configuration    |
+
+#### 8.1.1.1 CBMC-Measurement-IND
+
+The CBMC-Measurement-IND primitive is used by BMC to indicate the CB traffic volume.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+CB-Traffic-Volume.
+
+#### 8.1.1.2 CBMC-Rx-IND
+
+The CBMC-Rx-IND primitive is used by BMC to indicate to RRC whether CB message reception shall start or stop and indicate when CB messages of interest are arriving in the next CBS schedule period.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+Action.
+
+DRX selection.
+
+#### 8.1.1.3 CBMC-Config-REQ
+
+The CBMC-Config-REQ primitive is used by RRC to inform the BMC about the setting of the CTCH configuration.
+
+**Primitive Type:** indication.
+
+##### **Parameters:**
+
+CTCH configuration.
+
+### 8.1.2 Parameters
+
+#### 8.1.2.1 CB-Traffic-Volume
+
+Expected CTCH transmission rate [kbps].
+
+Value set: 0,1,...,32.
+
+#### 8.1.2.2 Action
+
+Start CBS reception.
+
+Stop CBS reception.
+
+#### 8.1.2.3 DRX selection
+
+List of absolute CTCH BS indices which are of interest and which should be received by Layer 1.
+
+#### 8.1.2.4 CTCH configuration
+
+Current CTCH-BS index,  $1 \leq i \leq 256$ .
+
+FACH identification.
+
+Transport Format Set of the allocated FACH (TB size, TBS size, TTI).
+
+Reserved CTCH transmission rate [kbps]: 0,1,...,32.
+
+## 8.2 Service Primitives between upper layer (U-plane) and BMC
+
+### 8.2.1 Primitives
+
+The primitives supported at BMC-SAP between BMC and upper layer (U-plane) are shown in Table 8.2.1-1.
+
+**Table 8.2.1-1: Primitives between BMC and upper layer**
+
+**Legend: [ ] optional parameters**
+
+| Generic Name         | Parameters                                                                                                                                                             |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BMC-Data-REQ         | Message-ID,<br>[, Old-Serial-Number],<br>New-Serial-Number,<br>Data-Coding-Scheme,<br>CB-Data ,<br>[Category],<br>Repetition-Period,<br>Number-of-Broadcasts-Requested |
+| BMC-Data-IND         | Message-ID,<br>Serial-Number,<br>Data-Coding-Scheme,<br>CB-Data                                                                                                        |
+| BMC-Data-CNF         | Message-ID,<br>Serial-Number                                                                                                                                           |
+| BMC-Congestion-IND   |                                                                                                                                                                        |
+| BMC-Normal-IND       |                                                                                                                                                                        |
+| BMC-Activation-REQ   | Message-ID (n times)                                                                                                                                                   |
+| BMC-Deactivation-REQ | Message-ID (n times)                                                                                                                                                   |
+| BMC-DRX-REQ          | CB-DRX-Schedule-Period, Reserved-CB-Capacity                                                                                                                           |
+| BMC-Error-IND        | Cause                                                                                                                                                                  |
+| BMC-Data41-REQ       | Transport Layer Message,<br>Broadcast Address                                                                                                                          |
+| BMC-Data41-IND       | Transport Layer Message,                                                                                                                                               |
+| BMC-Error41-IND      | Error Type                                                                                                                                                             |
+
+#### 8.2.1.1 Primitives used in relation to UMTS Core Network
+
+##### 8.2.1.1.1 BMC-Data-REQ
+
+The BMC-Data-REQ primitive is used by upper layer to request repeated transmission of CB messages.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID;  
+[Old-Serial-Number];  
+New-Serial-Number;  
+Data-Coding-Scheme;  
+CB-Data;  
+[Category];  
+Repetition-Period;  
+Number-of-Broadcasts-Requested.
+
+##### 8.2.1.1.2 BMC-Data-IND
+
+The BMC-Data-IND primitive is used to indicate received CB messages (i.e. CB Data) to upper layer.
+
+**Primitive Type:** indication.
+
+###### **Parameters:**
+
+Message-ID;
+
+Serial-Number;
+
+Data-Coding-Scheme;
+
+CB-Data.
+
+##### **8.2.1.1.3 BMC-Data-CNF**
+
+The BMC-Data-CNF primitive is used to indicate the complete broadcast of CB messages.
+
+**Primitive Type:** confirmation.
+
+###### **Parameters:**
+
+Message-ID.
+
+Serial-Number.
+
+##### **8.2.1.1.4 BMC-Congestion-IND**
+
+The BMC-Congestion-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC entity is congested.
+
+**Primitive Type:** indication.
+
+###### **Parameters:** None.
+
+##### **8.2.1.1.5 BMC-Normal-IND**
+
+The BMC-Normal-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC has recovered from a congestion situation and is operating normal.
+
+**Primitive Type:** indication.
+
+###### **Parameters:** None.
+
+##### **8.2.1.1.6 BMC-Activation-REQ**
+
+The BMC-Activation-REQ primitive is used to request CB message reception and to notify which CB messages are of interest and shall be delivered to the upper layer.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID (n times).
+
+##### **8.2.1.1.7 BMC-Deactivation-REQ**
+
+The BMC-Deactivation-REQ primitive is used to request stop of reception of listed CB messages. If no more CB messages are to be received, CB message reception shall stop.
+
+**Primitive Type:** request.
+
+###### **Parameters:**
+
+Message-ID (n times).
+
+##### **8.2.1.1.8 BMC-DRX-REQ**
+
+The BMC-DRX-REQ primitive is used to command CBS discontinuous reception (CB DRX).
+
+NOTE: In UMTS, a Set DRX procedure is not requested for the CBC in TS 23.041. It is left to an O&M system to provide such a function or not.
+
+**Primitive Type:** request.
+
+**Parameters:**
+
+CB-DRX-Schedule-Period.
+
+Reserved-CB-Capacity.
+
+##### 8.2.1.1.9 BMC-Error-IND
+
+The BMC-Error-IND primitive is used to indicate unsuccessful operations of the BMC entity requested.
+
+**Primitive Type:** indication.
+
+**Parameters:**
+
+Cause.
+
+#### 8.2.1.2 Primitives used for ANSI-41 Core Network
+
+##### 8.2.1.2.1 BMC-Data41-REQ
+
+The BMC-Data41-REQ primitive is used by upper layer (Transport Layer) to request repeated transmission of CBS messages if the source is ANSI-41 core network.
+
+**Primitive Type:** request.
+
+**Parameters:**
+
+Transport Layer Message.
+
+Broadcast Address.
+
+##### 8.2.1.2.2 BMC-Data41-IND
+
+The BMC-Data-IND primitive is used to indicate received CB messages to upper layer (Transport Layer) if the source is ANSI-41 core network.
+
+**Primitive Type:** indication.
+
+**Parameters:**
+
+Transport Layer Message.
+
+Broadcast Address.
+
+##### 8.2.1.2.3 BMC-Error41-IND
+
+The BMC-Error-IND primitive is used to report BMC Layer Error to the upper layer (Transport Layer) if the source is ANSI-41 core network.
+
+**Primitive Type:** indication.
+
+**Parameters:**
+
+Error Type.
+
+### 8.2.2 Parameters
+
+#### 8.2.2.1 Message-ID
+
+Part of the CB message identification describing the source and type of a CB message. This parameter is described in [3].
+
+#### 8.2.2.2 Serial Number
+
+Part of the CB message identification describing variants of a CB message. This parameter is described in [3].
+
+#### 8.2.2.3 Data-Coding-Scheme
+
+Data coding scheme applied to the CB information. This parameter is described in [4] and [3].
+
+#### 8.2.2.4 CB-Data
+
+CB information to be broadcast.
+
+NOTE: The relation to GSM CBS pages can be found in [6] or [3].
+
+#### 8.2.2.5 Category
+
+Indicates the category (priority) of the CB message.
+
+Values:
+
+HIGH (CB message is to be broadcast at the earliest opportunity in the reserved CB capacity of the current CB DRX schedule period).
+
+NORMAL (default, CB messages to be broadcast according to the associated repetition period).
+
+BACKGROUND (CB message to be broadcast in the CB capacity not occupied by HIGH or NORMAL CB messages within a CB DRX schedule period).
+
+This parameter is described in [3].
+
+#### 8.2.2.6 Repetition-Period
+
+Indicates the period of time after which broadcast of the CB message should be repeated. This parameter is described in [3].
+
+NOTE: For GSM, the repetition period is a multiple of 1.883 seconds (cf. [3]).
+
+#### 8.2.2.7 Number-of-Broadcasts-Requested
+
+Number of times a CB message is to be broadcast.
+
+Values:
+
+0 indefinitely.
+
+$n$ ,  $1 \leq n \leq 65535$  finite number of times to be broadcast.
+
+This parameter is described in [3].
+
+#### 8.2.2.8 CB-DRX-Schedule-Period
+
+Indication of the CB DRX schedule period length.
+
+#### 8.2.2.9 Reserved-CB-Capacity
+
+Indicates the capacity reserved for CB messages with Category = HIGH or new CB messages.
+
+#### 8.2.2.10 Cause
+
+CB message already stored.
+
+Old CB message not stored.
+
+#### 8.2.2.11 Transport Layer Message
+
+This parameter is described in [8].
+
+#### 8.2.2.12 Broadcast Address
+
+This parameter is described in [8].
+
+#### 8.2.2.13 Error Type
+
+The error codes shall be SMS\_CauseCode values as defined in the SMS\_CauseCode Table in [7].
+
+# 9 Procedures
+
+## 9.1 BMC Message Broadcast
+
+![Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) box is on the left and a UTRAN (UMTS Radio Access Network) box is on the right. A horizontal arrow labeled 'BMC message' points from the UTRAN box to the UE box. Vertical lines extend downwards from both boxes, representing their lifelines.](a7c51c18111139f9aca2805114108565_img.jpg)
+
+```
+sequenceDiagram
+    participant UTRAN
+    participant UE
+    Note left of UTRAN: BMC message
+    UTRAN->>UE: BMC message
+```
+
+Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) box is on the left and a UTRAN (UMTS Radio Access Network) box is on the right. A horizontal arrow labeled 'BMC message' points from the UTRAN box to the UE box. Vertical lines extend downwards from both boxes, representing their lifelines.
+
+**Figure 9.1-1: Procedure for broadcast of BMC messages**
+
+This procedure is used for broadcasting BMC messages from the network to UEs in a cell. A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode and in CELL\_PCH and URA\_PCH RRC-states of Connected mode.
+
+Three types of BMC messages are identified: CBS Message, CBS41 Message and Schedule Message.
+
+## 9.2 Generation of Schedule message
+
+NOTE: Principles and examples are described in [6].
+
+This procedure calculates the CBS schedule periods and assigns BMC messages (i.e. CBS Messages, CBS41 Messages and Schedule Messages) to the CBS schedule periods and gives an indication which of the CTCH Block Sets containing a part of or a complete BMC messages has the status "new".
+
+NOTE: The concatenation function of RLC shall not be applied. RLC Length Indicators shall not be concatenated with RLC SDUs they do not refer to.
+
+Algorithms used for scheduling are implementation dependent and thus do not need to be specified. Some parameters may be set by CBC or O&M system.
+
+CTCH Block Sets are indicated in a New Message Bitmap IE of BMC Schedule Message as new (bit position of a CTCH Block Set is set to value "1") when one of the following conditions is met:
+
+The CTCH Block Set contains part of or a complete BMC message which was either not sent during the previous CBS schedule period, or sent unscheduled during the preceding CBS schedule period; or, the CTCH Block Set is indicated as of free usage, reading advised, or it contains the Schedule Message partly or complete of the following CBS schedule period, or it contains a CBS41 Message partly or complete.
+
+Other BMC messages sent in the same CBS schedule messages are indicated as "old" (bit position of CTCH Block Set containing this message partly or complete is set to value 0).
+
+The indication "new" is set both for the first transmission of a BMC message in the CBS schedule period or a repetition of it within the CBS schedule period. For CBS41 Messages, repetition is not specified.
+
+The input parameters of the scheduling procedure are set by CBC or RRC or by the O&M system for the BMC.
+
+The CBC input parameters are:
+
+CB messages (i.e. BMC SDUs),  
+Message Identifier per CB message,  
+Serial Number per CB message,  
+CB repetition period per CB message,  
+Number of Broadcast Requested per CB message.
+
+The RRC input parameters are:
+
+Sizes of CTCH Block Sets,  
+Timing of CTCH Block Set sequence.
+
+The O&M (BMC) input parameters are:
+
+DRX Schedule Period (cell related parameter) requested optionally,  
+Reserved CB Capacity (cell related parameter) requested optionally.
+
+## 9.3 Traffic volume measurement
+
+The BMC entity on the network side predicts periodically the expected amount of CBS traffic volume (unit: kbps) that is needed for transmission of CB messages currently and indicates this to RRC.
+
+The algorithms used for traffic volume prediction are implementation dependent and thus do not need to be specified. Some parameters may be set by O&M system. The algorithms depend on the chosen algorithms for CB message scheduling (cf. subclause 9.2).
+
+## 9.4 BMC message reception
+
+The BMC entity on the UE side evaluates received BMC Schedule Messages and takes decisions which BMC messages should be received. The reception of a BMC message is indicated to RRC if the CTCH Block Sets carrying this BMC message are indicated as new. If the upper layer has requested reception of individual CB messages when in status "old", the reception of these BMC messages are also indicated to RRC.
+
+If not otherwise requested by upper layers, only those CB messages received in BMC CBS Messages should be delivered to upper layers for which the Serial Number associated with the CB message has changed. This implies that the BMC has to store the last received Serial Number of each CB message activated by upper layers.
+
+Every CBS41 Message received by BMC shall be delivered to upper layer.
+
+# --- 10 BMC Messages
+
+## 10.1 General
+
+A BMC message is equivalent with a BMC PDU. There are three types of BMC messages defined, CBS messages and CBS41 messages, which carry cell broadcast data from higher layer, and *Schedule messages*, which provide information for support of Discontinuous Reception (DRX) of cell broadcast data at the UE.
+
+BMC messages and information elements are specified using the tabular format methodology as specified in TR 25.921, and additional text is describing the encoding.
+
+NOTE: Only IEs marked as MP or CV in the "Need" column exist, with the exception of the IE "BMC Schedule Message Extension" of the BMC Schedule Message (see subclause 10.3).
+
+BMC messages (i.e. BMC PDUs) specified by tabular format consist of an ordered sequence IE1,...IEn of information element fields.
+
+The octet string of a BMC message is defined as the concatenation of the octets of the IEs maintaining the sequence order. The bits within an octet are numbered 0 to 7; bit 0 is the least significant bit and is transmitted first. The octets are transmitted in order of increasing octet number, i.e. starting with octet 1. This means that bit 0 of octet 1 is transmitted as the first (leftmost) bit in the Data field of the UMD PDU [1].
+
+The UE shall ignore any unrecognised bits at the end of a BMC message.
+
+NOTE: Although not explicitly stated as a requirement in release '99, 4 and 5 specifications it is assumed that release '99, 4, 5 UEs will also ignore any unrecognised bits at the end of a BMC message.
+
+## 10.2 BMC CBS Message
+
+The CBS Message carries the cell broadcast data and the address information if the address information is based on GSM CBS.
+
+RLC-SAP: UM;
+
+Logical channel: CTCH;
+
+Direction: UTRAN → UE.
+
+**Table 10.2-1: CBS Message**
+
+| Information Element | Need | Multi | Type and reference | Semantics description |
+|---------------------|------|-------|--------------------|-----------------------|
+| Message Type        | MP   |       | Sec. 11.1          |                       |
+| Message ID          | MP   |       | Sec. 11.2          |                       |
+| Serial Number       | MP   |       | Sec. 11.3          |                       |
+| Data Coding Scheme  | MP   |       | Sec. 11.4          |                       |
+| CB Data             | MP   |       | Sec. 11.5          |                       |
+
+## 10.3 BMC Schedule Message
+
+The BMC Schedule Message describes for the succeeding CBS schedule period the time locations for each CBS Message and the location of the Schedule Message of the following CBS schedule period. The UE is not required to start receiving a CBS Schedule Period earlier than 100ms after UE has received the complete BMC Schedule message.
+
+RLC-SAP: UM.
+
+Logical channel: CTCH.
+
+Direction: UTRAN → UE.
+
+**Table 10. 3-1: Schedule Message**
+
+| Information Element             | Need | Multi                                  | Type and reference | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                 | Version |
+|---------------------------------|------|----------------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Message Type                    | MP   |                                        | Sec. 11.1          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Offset to Begin CTCH BS index   | MP   |                                        | Sec. 11.6          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Length of CBS Scheduling Period | MP   |                                        | Sec. 11.7          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| New Message Bitmap              | MP   |                                        | Sec. 11.8          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |
+| Message Description             | MP   | 1 to <Length of CBS Scheduling Period> | Sec. 11.9          | Message Description IE is included for each new message (1 in the New message bitmap) as well as for each old message (0 in the New message bitmap). The i-th Message Description IE refers to the i-th bit in the New Message Bitmap IE. The multiplicity for the IE "Message Description" does not require an additional length indication in the encoded message. The multiplicity shall be derived from the IE "Length of CBS Scheduling Period". |         |
+| BMC Schedule Message Extension  | OP   |                                        | Sec 11.12          |                                                                                                                                                                                                                                                                                                                                                                                                                                                       | REL-6   |
+
+The IE "BMC Schedule Message Extension" is optional. There is no explicit mechanism to indicate the presence of this IE in the BMC Schedule Message.
+
+## 10.4 BMC CBS41 Message
+
+The CBS41 Message carries the cell broadcast data and the address information if the address information is based on ANSI-41 CBS.
+
+RLC-SAP: UM.
+
+Logical channel: CTCH.
+
+Direction: UTRAN → UE.
+
+**Table 10.4-1: CBS41 Message**
+
+| Information Element | Need | Multi | Type and reference | Semantics description |
+|---------------------|------|-------|--------------------|-----------------------|
+| Message Type        | MP   |       | Sec. 11.1          |                       |
+| Broadcast Address   | MP   |       | Sec. 11.10         |                       |
+| CB Data41           | MP   |       | Sec. 11.11         |                       |
+
+# 11 Information Elements
+
+## 11.1 Message Type
+
+**Table 11.1-1: Message Type IE**
+
+| IE/Group name | Need | Multi | Type and reference                    | Semantics description                                                                                     |
+|---------------|------|-------|---------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| Message Type  | MP   |       | Enumerated (0 .. 255)<br>Table 11.1-2 | This IE is coded as the binary representation of the Message Type. This IE is mapped onto a single octet. |
+
+Coding of Message Type
+
+**Table 11.1-2: Coding of Message Type IE**
+
+|            |                                                                                                   |
+|------------|---------------------------------------------------------------------------------------------------|
+| 1          | CBS Message                                                                                       |
+| 2          | Schedule Message                                                                                  |
+| 3          | CBS41 Message                                                                                     |
+| 0, 4.. 255 | Reserved for future use (PDUs with this coding will be discarded by this version of the protocol) |
+
+## 11.2 Message ID
+
+**Table 11.2-1: Message ID IE**
+
+| IE/Group name | Need | Multi | Type and reference | Semantics description                                                                                                                                      |
+|---------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Message ID    | MP   |       | Octet string (2)   | Identification of source and type of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. |
+
+## 11.3 Serial Number
+
+**Table 11.3-1: Serial Number IE**
+
+| IE/Group Name | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                    |
+|---------------|------|-------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Serial Number | MP   |       | Octet string (2)   | Identification of variations of a CBS message (part of the overall CBS message identification). The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. |
+
+## 11.4 Data Coding Scheme
+
+**Table 11.4-1: Data Coding Scheme IE**
+
+| IE/Group name      | Need | Multi | Type and reference | Semantics description                                                                                |
+|--------------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------|
+| Data Coding Scheme | MP   |       | Bitstring(8)       | Identification of the alphabet/coding and the language applied. This IE is encoded according to [4]. |
+
+## 11.5 CB Data
+
+**Table 11.5-1: CB Data IE**
+
+| IE/Group name | Need | Multi | Type and reference             | Semantics description                                                                                                                                                                                                                                                                     |
+|---------------|------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CB Data       | MP   |       | Octet string (N)<br>$N \geq 1$ | Content of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [4] and so on.<br>NOTE: This IE contains the CB Data as received in the SABP with the length indicator of the PER aligned bit string as received on SABP being removed. |
+
+NOTE: The number N is less than or equal to 1246 octets if a GSM CBS message is broadcast.
+
+## 11.6 Offset to Begin CTCH Block Set Index
+
+**Table 11.6-1: Offset to Begin CTCH Block Set Index IE**
+
+| IE/Group name                 | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                                                                                                                 |
+|-------------------------------|------|-------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Offset to Begin CTCH BS Index | MP   |       | Integer (1..255)   | Pointer to the first CTCH BS of the next CBS Schedule Period relative to the CTCH BS index of the first part of the current BMC Schedule Message. This IE is coded as the binary representation of the Offset to Begin CTCH BS Index. This IE is mapped onto a single octet. The value 0 is reserved. |
+
+## 11.7 Length of CBS Schedule Period
+
+**Table 11.7-1: Length of CBS Schedule Period IE**
+
+| Information Element/Group name | Need | Multi | Type and reference | Semantics description                                                                                                                                                                                                                                                                                           |
+|--------------------------------|------|-------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Length of CBS Schedule Period  | MP   |       | Integer (1..255)   | Number of consecutive CTCH BS of the next CBS Schedule Period. Together with Offset to Begin CTCH BS Index it points to the end of the CBS schedule period. This IE is coded as the binary representation of the Length of CBS Schedule Period. This IE is mapped onto a single octet. The Value 0 is reserved. |
+
+## 11.8 New Message Bitmap
+
+**Table 11.8-1: New Message Bitmap IE**
+
+| Information Element/Group name | Need | Multi | Type and reference                                                                                                                                                                                    | Semantics description                                                          |
+|--------------------------------|------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| New Message Bitmap             | MP   |       | Octet string (N)<br><br>if "Length of CBS Schedule Period" mod 8 = 0 then<br>N = "Length of CBS Schedule Period" div 8,<br>else<br>N = "Length of CBS Schedule Period" div 8 + 1.<br><br>Table 11.8-2 | Bitmap indicating CTCH BS which contains new CBS Messages completely or partly |
+
+Coding of New Message Bitmap.
+
+**Table 11.8-2: Coding of New Message Bitmap IE**
+
+| 0                                                                                                                                                                                       | 1                 | 2                 | 3               | 4 | 5 | 6 | 7 | Bit     |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|-----------------|---|---|---|---|---------|
+| CTCH BS index B                                                                                                                                                                         | CTCH BS index B+1 | CTCH BS index B+2 | ...             |   |   |   |   | Octet 1 |
+|                                                                                                                                                                                         |                   |                   |                 |   |   |   |   | Octet 2 |
+|                                                                                                                                                                                         |                   |                   |                 |   |   |   |   | ...     |
+|                                                                                                                                                                                         | ...               | CTCH BS index E-1 | CTCH BS index E | 0 | 0 | 0 | 0 | Octet n |
+| Legend: B First CTCH BS index of the CBS schedule period, $1 \leq B \leq 256$<br>E Last CTCH BS index of the CBS schedule period,<br>$E = B + \text{Length of CBS Schedule Period} - 1$ |                   |                   |                 |   |   |   |   |         |
+
+CTCH BS Index i:
+
+Each bit of the New CBS Message Bitmap refers to the content of CTCH BS index i,  $i=B, \dots, E$ . Its meaning is as follows:
+
+- 1 The CTCH BS index i contains a BMC Message partly or completely which was either not sent during the previous schedule period, or sent unscheduled during the preceding schedule period; or, the CTCH BS is indicated as of free usage, reading advised; or it contains the Schedule Message partly or complete of the following CBS schedule period, or it contains a CBS41 Message partly or complete. The value is 1 both for the first transmission of a given BMC message in the CBS schedule period or a repetition of it within the CBS schedule period.
+- 0 The CTCH BS is such that value 1 is not suitable.
+
+The length of the New Message Bitmap is given by the IE Length of CBS Schedule Period. If it is not a multiple of 8 the remaining bit positions are padded with "0".
+
+## 11.9 Message Description
+
+**Table 11.9-1: Message Description IE**
+
+| IE/Group Name                                 | Need    | Multi | Type and reference                     | Semantics description                                                                                                                                                                       |
+|-----------------------------------------------|---------|-------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Message Description Type                      | MP      |       | Enumerated(0..255)<br><br>Table 11.9-3 | This IE is coded as the binary representation of the Message Description Type. This IE is mapped onto a single octet.                                                                       |
+| Message ID                                    | CV MDT1 |       | Octet string (2)                       | This IE is coded as the binary representation of the Message ID. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on.                   |
+| Offset to CTCH BS index of first transmission | CV MDT2 |       | Integer (0..255)                       | This IE is coded as the binary representation of the Offset to CTCH BS index of first transmission relative to the start of the BMC schedule period. This IE is mapped onto a single octet. |
+
+**Table 11.9-2: Conditions**
+
+| <b>Condition</b> | <b>Explanation</b>                                                                                                                                                                                                                 |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MDT1             | If Message Description Type = 1 or 5 then:<br>the CB-Message-Id IE is included                                                                                                                                                     |
+| MDT2             | If Message Description Type = 0 or 4 then:<br>the Offset to CTCH BS index of first transmission IE is included<br>pointing to the CTCH BS index where the BMC message is transmitted<br>the first time within the schedule period. |
+
+**Table 11.9-3: Encoding of Message Description Type**
+
+| <b>Value</b> | <b>Explanation</b>                                                                       |
+|--------------|------------------------------------------------------------------------------------------|
+| 0            | Repetition of new BMC CBS message within schedule period                                 |
+| 1            | New BMC CBS message (a BMC CBS message never previously sent)                            |
+| 2            | Reading advised                                                                          |
+| 3            | Reading optional                                                                         |
+| 4            | Repetition of old BMC CBS message within schedule period                                 |
+| 5            | Old BMC CBS message (repetition of a BMC CBS message sent in a previous schedule period) |
+| 6            | Schedule message                                                                         |
+| 7            | CBS41 message                                                                            |
+| 8            | no message                                                                               |
+| 9.. 255      | Reserved for future use<br>(IEs received with this value will be replaced by value 3)    |
+
+NOTE: Message Description Type values 0, 1, 4, 5 and 6 indicate transmission of a BMC message partly or completely.
+
+## 11.10 Broadcast Address
+
+**Table 11.10-1: Data Coding Scheme IE**
+
+| <b>IE/Group name</b> | <b>Need</b> | <b>Multi</b> | <b>Type and reference</b> | <b>Semantics description</b>                                                                                                                      |
+|----------------------|-------------|--------------|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| Broadcast Address    | MP          |              | Octet string (5)          | Address information for higher layer.<br>The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. |
+
+## 11.11 CB Data41
+
+**Table 11.11-1: CB Data IE**
+
+| <b>IE/Group name</b> | <b>Need</b> | <b>Multi</b> | <b>Type and reference</b>      | <b>Semantics description</b>                                                                                                                  |
+|----------------------|-------------|--------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| CB Data41            | MP          |              | Octet string (N)<br>$N \geq 1$ | Content of CBS message (ANSI-41).<br>The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. |
+
+## 11.12 CBS Schedule Message Extension
+
+**Table 11.12-1: CBS Schedule Message Extension IE**
+
+| Information Element     | Need    | Multi | Type and reference                   | Semantics description | Version |
+|-------------------------|---------|-------|--------------------------------------|-----------------------|---------|
+| Future extension bitmap | MP      |       | Octet string(1)                      |                       | REL-6   |
+| Extension 0             | CV ext0 |       | CBS Message Serial Numbers Sec 11.13 |                       | REL-6   |
+| Extension 1             | CV ext1 |       | Null                                 |                       | REL-6   |
+| Extension 2             | CV ext2 |       | Null                                 |                       | REL-6   |
+| Extension 3             | CV ext3 |       | Null                                 |                       | REL-6   |
+| Extension 4             | CV ext4 |       | Null                                 |                       | REL-6   |
+| Extension 5             | CV ext5 |       | Null                                 |                       | REL-6   |
+| Extension 6             | CV ext6 |       | Null                                 |                       | REL-6   |
+| Extension 7             | CV ext7 |       | Null                                 |                       | REL-6   |
+
+**Table 11.12-2: Conditions**
+
+| Condition | Explanation                                                                                                                                                                                          |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| extn      | If bit <i>n</i> of the Future extension bitmap is set to 1 then Extension <i>n</i> is present.<br>If bit <i>n</i> of the Future extension bitmap is set to 0 then Extension <i>n</i> is not present. |
+
+## 11.13 CBS Message Serial Numbers
+
+**Table 11.13: CBS Message Serial Numbers IE**
+
+| Information Element          | Need | Multi                              | Type and reference | Semantics description | Version |
+|------------------------------|------|------------------------------------|--------------------|-----------------------|---------|
+| Length of Serial Number List | MP   |                                    | Integer (0..255)   |                       | REL-6   |
+| Serial Number List Entry     | MP   | 0 to <Length of Serial Number List | Sec. 11.14         |                       | REL-6   |
+
+## 11.14 Serial Number List Entry
+
+**Table 11.14: Serial Number List Entry IE**
+
+| <b>Information Element</b> | <b>Need</b> | <b>Multi</b> | <b>Type and reference</b> | <b>Semantics description</b>                                                                                                                                                                                                                                     | <b>Version</b> |
+|----------------------------|-------------|--------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|
+| Serial Number              | MP          |              | Sec. 11.3                 | The CBS Message Serial Number of the BMC CBS Message referred to by the CTCH BS Index.                                                                                                                                                                           | REL-6          |
+| CTCH BS Index              | MP          |              | Integer (0..255)          | <p>The CTCH BS Index IE indicates the index of the CTCH BS within the BMC Schedule Period which contains the start of the BMC CBS Message.</p> <p>This IE is coded as the binary representation of the CTCH BS Index. This IE is mapped onto a single octet.</p> | REL-6          |
+

marked/Rel-17/25_series/25327/raw.md

@@ -0,0 +1,137 @@
+
+
+
+
+
+
+# Contents
+
+Foreword ..... 4
+
+1 Scope..... 5
+
+2 References..... 5
+
+3 Definitions, symbols and abbreviations..... 5
+
+3.1 Definitions..... 5
+
+3.2 Abbreviations ..... 5
+
+4 DB-DC-HSDPA configurations independent of release..... 6
+
+4.1 Void..... 6
+
+4.2 Void..... 6
+
+4.3 Void..... 6
+
+5 4C-HSDPA configurations independent of release ..... 6
+
+5.1 Single-band contiguous configurations..... 6
+
+5.1.1 Void..... 6
+
+5.1.2 Void..... 6
+
+5.2 Dual-band configurations..... 6
+
+5.2.1 Void..... 6
+
+5.2.2 Void..... 6
+
+5.2.3 Void..... 6
+
+5.2.4 Void..... 6
+
+5.2.5 Void..... 6
+
+6 8C-HSDPA configurations independent of release ..... 6
+
+Annex A (informative): Change history..... 7
+
+# --- Foreword
+
+This Technical Specification 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 specifies requirements on UEs supporting a DB-DC-HSDPA, 4C-HSDPA, and 8C-HSDPA configuration that is independent of release. TSG-RAN has agreed that the standardisation of new configurations may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a configuration that is specified in a later release, it is necessary to specify some extra requirements.
+
+For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
+
+Similarly, 4C-HSDPA configuration I-3 is contained in the Release 11 specification [3]. In order to implement a UE conforming to Release 10, but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 11 specifications.
+
+# --- 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 25.101 (Release 10): "User Equipment (UE) radio transmission and reception (FDD)".
+- [3] 3GPP TS 25.101 (Release 11): "User Equipment (UE) radio transmission and reception (FDD)".
+- [4] Void
+- [5] Void
+
+# --- 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 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].
+
+|             |                           |
+|-------------|---------------------------|
+| DB-DC-HSDPA | Dual Band Dual Cell HSDPA |
+| 4C-HSDPA    | Four-carrier HSDPA        |
+| 8C-HSDPA    | Eight-carrier HSDPA       |
+
+# --- 4 DB-DC-HSDPA configurations independent of release
+
+4.1 Void
+
+4.2 Void
+
+4.3 Void
+
+# --- 5 4C-HSDPA configurations independent of release
+
+5.1 Single-band contiguous configurations
+
+5.1.1 Void
+
+5.1.2 Void
+
+5.2 Dual-band configurations
+
+5.2.1 Void
+
+5.2.2 Void
+
+5.2.3 Void
+
+5.2.4 Void
+
+5.2.5 Void
+
+# --- 6 8C-HSDPA configurations independent of release
+

marked/Rel-17/25_series/25367/raw.md

@@ -0,0 +1,397 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                             |           |
+|-----------------------------------------------------------------------------|-----------|
+| Foreword .....                                                              | 4         |
+| 1 Scope.....                                                                | 5         |
+| 2 References.....                                                           | 5         |
+| 3 Definitions, symbols and abbreviations.....                               | 5         |
+| 3.1 Definitions.....                                                        | 5         |
+| 3.2 Abbreviations .....                                                     | 6         |
+| 4 Overview.....                                                             | 7         |
+| 5 CSG Identification .....                                                  | 8         |
+| 6 CSG Selection.....                                                        | 8         |
+| 6.1 Manual CSG ID Selection.....                                            | 8         |
+| 7 CSG Cell Reselection.....                                                 | 9         |
+| 7.1 Measurement Rules for CSG Cells .....                                   | 9         |
+| 7.2 Reselection to CSG Cell.....                                            | 9         |
+| 7.2.1 Criteria for Intra-frequency Cell Reselection.....                    | 9         |
+| 7.2.2 Criteria for Inter-frequency Cell Reselection.....                    | 9         |
+| 7.2.3 Criteria for Inter-RAT Cell Reselection.....                          | 9         |
+| 7.3 Reselection from CSG Cell .....                                         | 9         |
+| 7.3.1 Criteria for Intra-frequency Cell Reselection.....                    | 9         |
+| 7.3.2 Criteria for Inter-frequency Cell Reselection.....                    | 9         |
+| 7.3.3 Criteria for Inter-RAT Cell Reselection.....                          | 9         |
+| 7.4 Reselection from CSG Cell to CSG Cell .....                             | 10        |
+| 7.5 Parameters for CSG Cell Reselection .....                               | 10        |
+| 8 CSG and Hybrid Cell Handover .....                                        | 10        |
+| 8.1 Handover to CSG/Hybrid Cell .....                                       | 10        |
+| 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure .....           | 11        |
+| 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure ..... | 12        |
+| 8.2 Handover from CSG Cell.....                                             | 13        |
+| 8.3 Handover from CSG Cell to CSG Cell .....                                | 13        |
+| 9 Support of Hybrid Cells .....                                             | 13        |
+| 9.1 Measurement Rules.....                                                  | 13        |
+| 9.2 Reselection .....                                                       | 13        |
+| <b>Annex B (informative): Void.....</b>                                     | <b>14</b> |
+| Annex C (informative): Change history.....                                  | 14        |
+
+# --- Foreword
+
+This Technical Specification 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
+
+This document provides a high level description of the mobility procedures applicable to Home NodeB support in the current Release. Where appropriate, the reasons behind the agreements are provided. Throughout this document, unless otherwise stated, the UE is assumed to be a current Release UE that supports the Closed Subscriber Group (CSG) feature, whether it is actually a member of a CSG or not. A UE that does not support the CSG feature is not required to support any of the procedures stated in this document.
+
+# --- 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 25.304: "UE procedures in idle mode and procedures for cell reselection in connected mode".
+- [3] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".
+- [4] 3GPP TS 23.011: "Service accessibility".
+- [5] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs".
+- [6] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB)".
+- [7] 3GPP TS 25.214: "Physical layer procedures (FDD)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Acceptable Cell:** A cell that satisfies certain conditions as specified [2]. A UE can always attempt emergency calls on an acceptable cell.
+
+**CSG whitelist:** A list provided by NAS containing all the CSG Identities of the CSGs to which the subscriber belongs.
+
+NOTE: This list is known as Allowed CSG List in Rel-8 Access Stratum specifications.
+
+**Available PLMN:** A PLMN for which the UE has found at least one cell and read its PLMN identity.
+
+**Barred Cell:** A cell a UE is not allowed to camp on.
+
+**Camped on a cell:** UE has completed the cell selection/reselection process and has chosen a cell. The UE monitors system information and (in most cases) paging information.
+
+**Camped on any cell:** UE is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity.
+
+**Closed Subscriber Group (CSG):** A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells).
+
+**CSG Cell:** A cell, part of the PLMN, broadcasting a CSG Indicator that is set to TRUE and a specific CSG identity. A CSG cell is accessible by the members of the closed subscriber group for that CSG identity.
+
+**CSG Identity (CSG ID):** An identifier broadcast by a CSG/Hybrid cell or cells and used by the UE to facilitate access for authorised members of the associated Closed Subscriber Group.
+
+**CSG member cell:** A cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity.
+
+**DRX cycle:** Individual time interval between monitoring Paging Occasion for a specific UE.
+
+**Equivalent PLMN list:** List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, MBSFN Cluster selection MBSFN Cluster reselection and handover according to the information provided by the NAS.
+
+**Home NodeB (HNB):** A HNB is a customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a mobile operator's network using broadband IP backhaul.
+
+**HNB Name:** The Home NodeB Name is a broadcast string in free text format that provides a human readable name for the Home NodeB CSG identity.
+
+**Home PLMN:** A PLMN where the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the PLMN identity are the same as the MCC and MNC of the IMSI.
+
+**Hybrid cell:** A cell broadcasting a CSG identity which is accessible as a CSG cell by UEs which are members of the CSG and as a normal cell by all other UEs.
+
+**Non-CSG Cell:** A cell that is not a CSG cell, e.g. a macro cell.
+
+**Process:** A local action in the UE invoked by a RRC procedure or an Idle Mode procedure.
+
+**Radio Access Mode:** Radio access mode of the cell, FDD or TDD.
+
+**Radio Access Technology:** Type of technology used for radio access, for instance UTRA or GSM.
+
+**Registered PLMN:** This is the PLMN on which certain Location Registration outcomes have occurred.
+
+**Registration Area:** (NAS) registration area is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure.
+
+**Reserved Cell:** A cell on which camping is not allowed, except for particular UEs, if so indicated in the system information.
+
+**Restricted Cell:** A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred.
+
+**Selected PLMN:** This is the PLMN that has been selected by the NAS, either manually or automatically.
+
+**Serving cell:** The cell on which the UE is camped.
+
+**Strongest cell:** The cell on a particular carrier that is considered strongest according to the layer 1 cell search procedure [7]. As the details of the layer 1 cell search are implementation dependent, the precise definition of 'strongest cell' is also implementation dependent.
+
+**Suitable Cell:** This is a cell on which an UE may camp.
+
+## 3.2 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].
+
+|      |                           |
+|------|---------------------------|
+| AS   | Access Stratum            |
+| BCCH | Broadcast Control Channel |
+| CM   | Connection Management     |
+| CN   | Core Network              |
+| CSG  | Closed Subscriber Group   |
+
+|        |                                            |
+|--------|--------------------------------------------|
+| DRX    | Discontinuous Reception                    |
+| E-UTRA | Evolved UMTS Terrestrial Radio Access      |
+| FDD    | Frequency Division Duplex                  |
+| GPRS   | General Packet Radio Service               |
+| GSM    | Global System for Mobile Communications    |
+| HCS    | Hierarchical Cell Structure                |
+| HNB    | Home NodeB                                 |
+| IMSI   | International Mobile Subscriber Identity   |
+| MCC    | Mobile Country Code                        |
+| MM     | Mobility Management                        |
+| MNC    | Mobile Network Code                        |
+| NAS    | Non-Access Stratum                         |
+| PCH    | Paging Channel                             |
+| PI     | Page Indicator                             |
+| PICH   | Page Indication Channel                    |
+| PLMN   | Public Land Mobile Network                 |
+| RAT    | Radio Access Technology                    |
+| RRC    | Radio Resource Control                     |
+| SAP    | Service Access Point                       |
+| TDD    | Time Division Duplex                       |
+| TMGI   | Temporary Mobile Group Identity            |
+| UE     | User Equipment                             |
+| UMTS   | Universal Mobile Telecommunications System |
+| UTRA   | UMTS Terrestrial Radio Access              |
+| UTRAN  | UMTS Terrestrial Radio Access Network      |
+
+# --- 4 Overview
+
+A Home NodeB may provide restricted access to only UEs belonging to a Closed Subscriber Group (CSG). One or more of such cells providing restricted access, known as CSG cells, are identified by a unique numeric identifier called CSG Identity. To facilitate access control, a UE with CSG subscription would have an CSG whitelist, which contains one or more CSG Identities associated with the CSG cells on which the UE is allowed access. The UE uses the CSG whitelist along with the CSG Identity and associated PLMN ID broadcast by the CSG Cells in CSG cell selection and reselection.
+
+A HNB can also be operated as a hybrid cell. A hybrid cell is accessed as a CSG cell by a UE whose CSG whitelist contains the cell's CSG ID and associated PLMN ID and as a normal cell by all other UEs. Members of the CSG are expected to receive preferential access according to [5].
+
+NOTE: Although pre-Rel-9 UEs are able to camp on hybrid cells (which would be regarded as normal cells for access) there is no possibility for these UEs to identify a hybrid cell as a CSG cell even though the cell's CSG identity and associated PLMN ID are in the UE's CSG whitelist.
+
+In addition, manual selection of CSG Identity is introduced, which enables the human user to manually select a CSG Identity for UE to camp on.
+
+This document provides high level descriptions and procedures of the mobility features to support CSG deployment in the current Release. The following areas will be covered in the subsequent chapters:
+
+- Identifiers associated with the CSG framework
+- Manual selection of CSG Identity
+- Measurement rules for CSG Cells
+- Cell reselection to a CSG cell, from a CSG cell, and between CSG cells
+- Handover to a CSG cell, from a CSG cell, and between CSG cells, where applicable
+- Measurement rules, (re)selection and handover procedures for hybrid cells.
+
+# --- 5 CSG Identification
+
+One or more Closed Subscriber Group (CSG) cells are identified by a unique numeric identifier called CSG Identity or CSG ID. A UE belonging to a CSG has the corresponding CSG ID and associated PLMN ID in its CSG whitelist. The CSG whitelist is maintained and provided by NAS. The CSG ID is broadcast in system information by the CSG cell or hybrid cell, and used by the UE for cell (re)selection and handover purposes.
+
+A cell may optionally broadcast the CSG Indicator, whose presence and value of TRUE indicates the cell is a CSG cell. The absence of the CSG indicator in a cell which broadcasts a CSG identity indicates that it is a hybrid cell.
+
+A CSG cell or hybrid cell may broadcast the HNB Name, a textual identifier, in system information. The HNB Name can be used to aid the human user in manual selection of a CSG ID.
+
+At the physical layer, a CSG cell is identified by its carrier frequency (UARFCN) and Primary Scrambling Code (PSC). A set of PSCs could be reserved for CSG deployment and this reserved PSC range may be signalled in system information. The PSC of a CSG cell belongs to the reserved PSC range if broadcast.
+
+On the mixed carrier frequency shared by both non-CSG cells (UMTS macro cells) and CSG cells, CSG cells broadcast in system information the PSC range reserved by the network for CSG cells. The non-CSG cells may also broadcast the reserved PSC range. The reserved PSC range is only applicable to the UARFCN within the PLMN where the UE received this information. The UE considers the last received reserved PSC range to be valid within the entire PLMN for the duration of 24 hours. The UE may use the reserved PSC information for CSG cell search and (re)selection purposes, according to UE's implementation.
+
+NOTE: In shared network scenario, aligned PSC ranges are beneficial in the shared carrier frequency across the involved PLMNs. Furthermore, in deployments where cells broadcast different primary PLMN (with or without multiple PLMN IDs), it is beneficial that CSG and non-CSG cells will broadcast same PSC ranges. Moreover, it is beneficial if a CSG cell, if listed in system information and associated with a PLMN, is associated with the primary PLMN of the serving cell.
+
+Non-CSG cells and CSG cells may broadcast indications of one or more carrier frequencies used for dedicated CSG deployment. This information may be used by a UE to avoid unnecessary measurements on that frequency even when cell measurement rules would require measurements of this carrier frequency. Indications of which carrier frequencies are dedicated to CSG-only deployment may be signalled in system information and are applicable only in the cell where this information is broadcast.
+
+# --- 6 CSG Selection
+
+## 6.1 Manual CSG ID Selection
+
+Manual CSG ID selection enables a human user to select a CSG ID. In manual CSG ID selection the UE may scan all frequencies in the supported frequency bands and display a list of found CSG IDs or the corresponding HNB Names if broadcast by the CSG cells or hybrid cells, and indications as to whether the found CSG IDs and associated PLMN IDs are contained in the UE's CSG whitelist. When the user selects an entry in the list, the UE selects any CSG cell or hybrid cell among the ones with same CSG ID and PLMN ID. The UE may normally camp on the chosen cell if it is a CSG member cell or a hybrid cell.
+
+During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell that is not a CSG member cell.
+
+Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UE's CSG whitelist is updated.
+
+The UE is allowed to *not* support manual CSG ID selection in connected mode.
+
+# 7 CSG Cell Reselection
+
+## 7.1 Measurement Rules for CSG Cells
+
+To measure CSG member cell(s), a UE applies an autonomous search function, per UE implementation, regardless of which RAT the UE is camping on. The autonomous search function determines when and where to search for the CSG member cells.
+
+Autonomous search procedure is disabled by the search function if UE's CSG whitelist does not exist or is empty.
+
+On a mixed carrier, a UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells.
+
+A UE may avoid measurements of any CSG cells that are known by the UE not to be CSG member cells on the carrier frequency dedicated to CSG deployment.
+
+## 7.2 Reselection to CSG Cell
+
+The cell reselection criteria described in this section is applicable when the UE is in the following call states: Idle Mode, Cell\_PCH, URA\_PCH and Cell\_FACH states, unless otherwise stated.
+
+Inter-RAT and inter-frequency reselection in CELL\_FACH state only needs to be performed when second DRX is used.
+
+### 7.2.1 Criteria for Intra-frequency Cell Reselection
+
+For intra-frequency reselection from a non-CSG cell to a CSG member cell, the UE follows the same cell ranking rules as those defined for the UTRA case in [2]. The UE may ignore not allowed CSG cells in the ranking. The UE applies reselection parameters broadcast by the serving cell. A UE may normally camp on a CSG member cell.
+
+### 7.2.2 Criteria for Inter-frequency Cell Reselection
+
+For inter-frequency cell reselection, the UE considers the frequency where its CSG member cell is on to have the highest priority value, irrespective of network configured frequency priorities, as long as the CSG member cell remains best ranked on that frequency.
+
+### 7.2.3 Criteria for Inter-RAT Cell Reselection
+
+Inter-RAT reselection to a CSG member cell is supported when the UE is camped on another RAT. The UE requirements are defined in the specifications of the concerned RAT.
+
+## 7.3 Reselection from CSG Cell
+
+### 7.3.1 Criteria for Intra-frequency Cell Reselection
+
+For intra-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2].
+
+### 7.3.2 Criteria for Inter-frequency Cell Reselection
+
+For inter-frequency reselection from a CSG member cell to a non-CSG cell, the UE follows the same cell ranking rules as those defined for the UTRA case defined in [2].
+
+### 7.3.3 Criteria for Inter-RAT Cell Reselection
+
+For reselection from a CSG cell to a GSM or E-UTRA cell, the UE follows the respective procedures defined in [2].
+
+## 7.4 Reselection from CSG Cell to CSG Cell
+
+For reselection between CSG member cells, the UE follows the same cell ranking rules as those defined for the UTRA case in [2].
+
+## 7.5 Parameters for CSG Cell Reselection
+
+No new parameters are defined for CSG cell ranking. The same cell reselection parameters defined for the UTRA case in [2] are used for CSG cell ranking purposes, if configured. The operator may configure the cell reselection parameters, such as Qoffset and Qhyst, to bias the reselection of CSG cells.
+
+# --- 8 CSG and Hybrid Cell Handover
+
+## 8.1 Handover to CSG/Hybrid Cell
+
+Handover to a HNB/HeNB follows the framework as specified in [3], [6]. Handover to a HNB/HeNB is different from the normal handover procedure in four aspects:
+
+1. **Proximity Estimation:** in case the UE is able to determine, based on UE implementation, that it is near a CSG member cell, the UE may provide to the SRNC an indication of proximity. The CSG proximity indication may be used as follows:
+  - a. If a measurement configuration is not present for the concerned frequency/RAT, the SRNC may configure the UE to perform measurements and reporting for the concerned frequency/RAT.
+  - b. The SRNC may determine whether to perform other actions related to handover to HNB/HeNBs based on having received a proximity indication (for example, the SRNC may not configure compressed mode gaps for the UE to detect the HNB/HeNB on a different frequency/RAT unless it has received a proximity indication).
+2. **PSC/PCI Confusion:** due to the typical cell size of HNB/HeNBs being much smaller than macro cells, there can be multiple HNBs/HeNBs within the coverage of the SRNC that have the same PSC/PCI. This leads to a condition referred to as PSC/PCI confusion, wherein the SRNC is unable to determine the correct target cell for handover from the PSC/PCI included in the measurement reports from the UE. PSC/PCI confusion is solved by the UE reporting the cell identity of the target HNB/HeNB.
+3. **Access Control:** If the target cell is a hybrid cell, prioritization of allocated resources may be performed based on the UE's membership status. Access control is done by a two step process, where first the UE reports whether the target cell is a CSG member cell based on the UE's CSG whitelist, and then the network verifies the reported status.
+4. **PLMN Report:** If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+
+Mobility from SRNC to a CSG/hybrid cell from network perspective is described in [6]. The following two sections describe the radio aspects. The SRNC in the call flows of these sections can be an RNC or a HNB.
+
+### 8.1.1 CSG/Hybrid Cell Intra-frequency Measurement Procedure
+
+![Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant SRNC
+    Note right of SRNC: 5. Handover processing [6]
+    SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)]
+    UE-->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication]
+    SRNC->>UE: 3. MEASUREMENT CONTROL [(CSG Intrafrequency cell info), (Intra-frequency SI Acquisition)]
+    UE-->>SRNC: 4. MEASUREMENT REPORT [PSC, Cell Identity, CSG Member Indication]
+  
+```
+
+The diagram shows a sequence of interactions between a User Equipment (UE) and a Serving Radio Network Controller (SRNC). The process begins with the SRNC sending a 'MEASUREMENT CONTROL' message to the UE, specifying 'CSG Proximity detection' as the measurement type. The UE responds with a 'MEASUREMENT REPORT' containing a 'CSG Proximity Indication'. Upon receiving this, the SRNC sends another 'MEASUREMENT CONTROL' message, this time providing 'CSG Intrafrequency cell info' and requesting 'Intra-frequency SI Acquisition'. The UE then sends a 'MEASUREMENT REPORT' that includes the 'PSC', 'Cell Identity', and 'CSG Member Indication'. Finally, the SRNC initiates 'Handover processing' as described in reference [6].
+
+Sequence diagram illustrating the Intra-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.
+
+**Figure 8.1.1-1: Intra-frequency Measurement Procedure of CSG and Hybrid cells**
+
+- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type.
+- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation).
+- 3) If a measurement configuration for CSG/hybrid cells is not present, the SRNC configures the UE with relevant measurement configuration which includes the PSCs that the UE must measure and the PSCs for which SI acquisition should be performed. The network may use the CSG proximity indication for intra-frequency case to minimize the time during which measurements for CSG/hybrid cells are configured.
+- 4) The UE sends a measurement report including the measured PSC, Cell Identity, CSG ID and CSG membership indication of the target HNB to the SRNC (e.g., due to a triggered intra-frequency event 1d). The UE can acquire MIB and SIB3/SIB4 of intra-frequency target HNB cells in parallel with reception of the serving cell transmissions in CELL\_DCH. No measurement gaps are required for reading MIB and SIB3/SIB4. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+- 5) SRNC can then proceed with the handover processing as described in [6].
+
+After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements configured.
+
+The PSC confusion is resolved by steps 3 and 4. The SRNC can request SI acquisition and reporting for any PSC, not limited to PSCs of CSG or hybrid cells.
+
+### 8.1.2 CSG/Hybrid Cell Inter-frequency/Inter-RAT Measurement Procedure
+
+![Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant SRNC
+    SRNC->>UE: 1. MEASUREMENT CONTROL [(Measurement Type = CSG Proximity detection)]
+    UE->>SRNC: 2. MEASUREMENT REPORT [CSG Proximity Indication]
+    SRNC->>UE: 3. MEASUREMENT CONTROL [ CSG Inter-frequency cell info]
+    UE->>SRNC: 4. MEASUREMENT REPORT [measured PSCs]
+    SRNC->>UE: 5. MEASUREMENT CONTROL [(report criteria = Periodical reporting criteria), (Amount of reporting = 1), (Inter-frequency SI Acquisition)]
+    Note left of UE: 6. UE reads System Information of the target HNB
+    UE->>SRNC: 7. MEASUREMENT REPORT [Cell Identity, CSG Member Indication]
+    Note right of SRNC: 8. Handover processing [6]
+  
+```
+
+Sequence diagram illustrating the Inter-frequency Measurement Procedure of CSG and Hybrid cells between a UE and an SRNC.
+
+**Figure 8.1.2-1: Inter-frequency Measurement Procedure of CSG and Hybrid cells.**
+
+- 1) The SRNC configures the UE with a measurement having "CSG Proximity detection" as measurement type.
+- 2) The UE sends an "entering" CSG proximity indication when it determines it may be near a CSG member cell (based on UE implementation). The CSG proximity indication includes the RAT and frequency of the cell.
+- 3) The SRNC configures a measurement on the concerned frequency/RAT to measure CSG/hybrid cells. Compressed mode gaps, if required by the UE, are also activated to allow UE to perform measurements on the reported RAT and frequency. The network may also use the proximity indication to minimize the requesting of handover preparation information of CSG/hybrid cells by avoiding requesting such information when the UE is not in the geographical area where its CSG member cells are located.
+- 4) The UE sends a measurement report including the measured PSCs/PCIs.
+- 5) The SRNC configures the UE to perform SI acquisition and reporting of a particular PSC/PCI.
+- 6) The UE performs SI acquisition using autonomous gaps, i.e., the UE may suspend reception and transmission with the SRNC to acquire the relevant system information from the target HNB/HeNB.
+- 7) The UE sends a measurement report including Cell Identity, CSG ID and CSG membership indication. If the target cell is a shared CSG/hybrid cell, the UE reports the subset of the broadcasted PLMN identities that fulfil the CSG member cell definition.
+- 8) SRNC can then proceed with the handover processing. The handover processing for inter-frequency handover to a CSG/Hybrid cell is described in [6].
+
+NOTE: The above steps also apply to inter-RAT mobility from UMTS cell to HeNB.
+
+After sending an "entering" CSG proximity indication (step 2), if the UE determines that it is no longer near any CSG member cell (on the reported proximate RAT and frequency), the UE sends a "leaving" CSG proximity indication to the SRNC. Upon reception of this indication, the SRNC may reconfigure the UE to stop measurements on the reported RAT and frequency.
+
+In the above procedure, step 2 may not be performed in case the UE has not previously visited the HNB, e.g., when the UE first visits a CSG/hybrid cell.
+
+The PSC/PCI confusion is resolved by steps 5, 6 and 7. The SRNC can request SI acquisition and reporting for any PSC/PCI, not limited to PSCs/PCIs of CSG or hybrid cells.
+
+## 8.2 Handover from CSG Cell
+
+In Cell\_DCH state, the handover procedure from a CSG member cell to a non-CSG cell is expected to be the same as the procedure specified in [3].
+
+## 8.3 Handover from CSG Cell to CSG Cell
+
+In Cell\_DCH state, handover between CSG member cells with the same CSG ID is expected to be the same as the procedure specified in Section 8.1.
+
+In Cell\_DCH state, handover between CSG member cells with different CSG IDs is expected to be the same as the procedure specified in Section 8.1.
+
+# --- 9 Support of Hybrid Cells
+
+## 9.1 Measurement Rules
+
+To measure for hybrid cells with a CSG Identity and its associated PLMN ID belonging to an entry in the UE's CSG whitelist, measurement rules of Chapter 7.1 apply. Otherwise, normal measurement rules apply.
+
+NOTE: The autonomous search for hybrid cells does not imply that UE need to constantly check the CSG ID of all cells it sees.
+
+## 9.2 Reselection
+
+In case the UE has CSG ID and its associated PLMN ID of the hybrid cell in its CSG whitelist, cell reselection procedures will be the same as for a CSG cell as described in Chapter 7.2.
+
+For all other UEs, cell reselection procedures will utilise normal cell reselection rules.
+
+# --- Annex B (informative): Void

marked/Rel-17/25_series/25410/raw.md

@@ -0,0 +1,1016 @@
+
+
+
+
+Error! No  
+text of
+
+Error! No text of specified style in  
+document.
+
+# Contents
+
+|                                                                               |    |
+|-------------------------------------------------------------------------------|----|
+| Foreword .....                                                                | 5  |
+| 1 Scope.....                                                                  | 6  |
+| 2 References.....                                                             | 6  |
+| 3 Definitions and abbreviations .....                                         | 7  |
+| 3.1 Definitions.....                                                          | 7  |
+| 3.2 Abbreviations .....                                                       | 7  |
+| 3.3 Specification Notations .....                                             | 8  |
+| 4 General Aspects .....                                                       | 9  |
+| 4.1 UTRAN Architecture .....                                                  | 9  |
+| 4.1.1 Iu Interface Architecture.....                                          | 9  |
+| 4.1.2 I <sub>u</sub> connection principles .....                              | 10 |
+| 4.1.3 Implementation of the NAS Node Selection Function.....                  | 10 |
+| 4.1.4 Implementation of MOCN configuration support.....                       | 10 |
+| 4.2 I <sub>u</sub> Interface General Principles .....                         | 10 |
+| 4.3 I <sub>u</sub> Interface Specification Objectives.....                    | 10 |
+| 4.4 I <sub>u</sub> Interface Capabilities.....                                | 11 |
+| 4.5 I <sub>u</sub> Interface Characteristics .....                            | 12 |
+| 4.5.1 Use of Transport Network User Plane as Signalling Bearer .....          | 12 |
+| 4.5.1.1 Use of SCCP.....                                                      | 12 |
+| 4.5.1.1.1 General .....                                                       | 12 |
+| 4.5.1.1.2 SCCP Connection Establishment procedure.....                        | 12 |
+| 4.5.1.1.3 SCCP Connection Release procedure .....                             | 14 |
+| 4.5.1.1.4 General SCCP Abnormal Conditions.....                               | 15 |
+| 4.5.1.2 Use of MTP3b.....                                                     | 15 |
+| 4.5.2 Use of Transport Network User Plane as User Data Bearer.....            | 15 |
+| 4.5.2.1 Use of AAL2.....                                                      | 15 |
+| 4.5.2.2 Use of GTP-U .....                                                    | 15 |
+| 4.5.2.3 Use of RTP.....                                                       | 15 |
+| 4.5.3 Use of Transport Network User Plane on Iu-BC.....                       | 15 |
+| 5 Functions of the I <sub>u</sub> Interface Protocols & Functional Split..... | 16 |
+| 5.1 General .....                                                             | 16 |
+| 5.2 RAB management Functions .....                                            | 18 |
+| 5.2.1 RAB establishment, modification and release function .....              | 18 |
+| 5.2.2 RAB characteristics mapping to Uu bearers function .....                | 18 |
+| 5.2.3 RAB characteristics mapping to Iu transport bearers.....                | 18 |
+| 5.2.4 RAB queuing, pre-emption and priority function .....                    | 18 |
+| 5.3 Radio Resource Management over Iu .....                                   | 19 |
+| 5.3.1 Radio resource admission control .....                                  | 19 |
+| 5.3.2 Broadcast information management.....                                   | 19 |
+| 5.4 I <sub>u</sub> link Management functions .....                            | 19 |
+| 5.4.1 I <sub>u</sub> Signalling Link Management function .....                | 19 |
+| 5.4.2 ATM Virtual Connection Management function .....                        | 19 |
+| 5.4.3 AAL2 connection establish and release function .....                    | 19 |
+| 5.4.4 AAL5 management function .....                                          | 19 |
+| 5.4.5 GTP-U tunnels management function .....                                 | 19 |
+| 5.4.6 TCP Management Function.....                                            | 20 |
+| 5.4.7 Buffer Management.....                                                  | 20 |
+| 5.4.8 RTP Session Management Function .....                                   | 20 |
+| 5.5 I <sub>u</sub> U-plane (RNL) Management Functions .....                   | 20 |
+| 5.5.1 I <sub>u</sub> U-plane frame protocol mode selection function.....      | 20 |
+| 5.5.2 I <sub>u</sub> U-plane frame protocol initialisation .....              | 20 |
+| 5.6 Mobility Management Functions .....                                       | 20 |
+| 5.6.1 Location information update function .....                              | 20 |
+| 5.6.2 Handover and Relocation functions .....                                 | 21 |
+| 5.6.2.1 Inter RNC hard HO function, Iur not used or not available .....       | 21 |
+| 5.6.2.2 Serving RNS Relocation function.....                                  | 21 |
+
+|                        |                                                                                               |    |
+|------------------------|-----------------------------------------------------------------------------------------------|----|
+| 5.6.2.3                | Inter system Handover (e.g. UMTS-GSM) function .....                                          | 21 |
+| 5.6.2A                 | Inter System Change (e.g. UMTS-GSM) function.....                                             | 21 |
+| 5.6.3                  | Paging Triggering.....                                                                        | 21 |
+| 5.6.4                  | Shared Networks Access Control.....                                                           | 21 |
+| 5.6.5                  | GERAN System Information Retrieval.....                                                       | 21 |
+| 5.7                    | Security Functions.....                                                                       | 21 |
+| 5.7.1                  | Data Confidentiality .....                                                                    | 21 |
+| 5.7.1.1                | Radio interface ciphering function .....                                                      | 21 |
+| 5.7.1.2                | Ciphering key management function.....                                                        | 22 |
+| 5.7.2                  | Data integrity .....                                                                          | 22 |
+| 5.7.2.1                | Integrity checking .....                                                                      | 22 |
+| 5.7.2.2                | Integrity key management .....                                                                | 22 |
+| 5.8                    | Service and Network Access Functions .....                                                    | 22 |
+| 5.8.1                  | Core Network signalling data transfer function .....                                          | 22 |
+| 5.8.2                  | Data Volume Reporting.....                                                                    | 22 |
+| 5.8.3                  | UE Tracing .....                                                                              | 22 |
+| 5.8.4                  | Location reporting function.....                                                              | 22 |
+| 5.8.5                  | MDT .....                                                                                     | 22 |
+| 5.9                    | Co-ordination Functions.....                                                                  | 22 |
+| 5.9.1                  | Paging Co-ordination function .....                                                           | 22 |
+| 5.9.2                  | NAS Node Selection Function .....                                                             | 23 |
+| 5.9.3                  | Information Transfer Function .....                                                           | 23 |
+| 5.9.4                  | MOCN Rerouting Function.....                                                                  | 23 |
+| 5.9.5                  | SIPTO at Iu-PS Function.....                                                                  | 23 |
+| 5.9.6                  | SIPTO at the Local Network with Standalone GW.....                                            | 23 |
+| 5.10                   | MBMS Functions .....                                                                          | 23 |
+| 5.10.1                 | MBMS RAB Management functions .....                                                           | 23 |
+| 5.10.2                 | MBMS UE Linking Function.....                                                                 | 23 |
+| 5.10.3                 | MBMS Registration Control Function .....                                                      | 23 |
+| 5.10.4                 | MBMS Enquiry Function .....                                                                   | 24 |
+| 6                      | I <sub>u</sub> Interface Protocol Structure.....                                              | 24 |
+| 6.1                    | General .....                                                                                 | 24 |
+| 6.2                    | Iu-CS .....                                                                                   | 25 |
+| 6.3                    | I <sub>u</sub> -BC.....                                                                       | 26 |
+| 6.4                    | I <sub>u</sub> -PS .....                                                                      | 27 |
+| 7                      | Other I <sub>u</sub> Interface Specifications .....                                           | 27 |
+| 7.1                    | UTRAN I <sub>u</sub> Interface: Layer 1 (3GPP TS 25.411) .....                                | 27 |
+| 7.2                    | UTRAN I <sub>u</sub> Interface: Signalling Transport (3GPP TS 25.412) .....                   | 27 |
+| 7.3                    | UTRAN I <sub>u</sub> Interface: RANAP Specification (3GPP TS 25.413).....                     | 27 |
+| 7.4                    | UTRAN I <sub>u</sub> Interface: Data Transport and Transport Signalling (3GPP TS 25.414)..... | 28 |
+| 7.5                    | UTRAN I <sub>u</sub> Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415).....            | 28 |
+| 7.6                    | UTRAN I <sub>u</sub> Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419) .....   | 28 |
+| 7.7                    | Summary .....                                                                                 | 28 |
+| Annex A (informative): | Change History.....                                                                           | 29 |
+
+# --- Foreword
+
+This Technical Specification (TS) 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 an introduction to the 3GPP TS 25.41x series of Technical Specifications that define the Iu interface for the interconnection of Radio Network Controller (RNC) component of the UMTS Terrestrial Radio Access Network (UTRAN) to the Core Network of the UMTS system.
+
+# --- 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 TS 25.401: "UTRAN Overall Description".
+- [2] 3GPP TR 23.930: "Iu Principles".
+- [3] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions".
+- [4] 3GPP TS 25.411: "UTRAN Iu Interface Layer 1".
+- [5] 3GPP TS 25.412: "UTRAN Iu Interface Signalling Transport".
+- [6] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
+- [7] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling".
+- [8] 3GPP TS 25.415: "UTRAN Iu Interface User Plane Protocols".
+- [9] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part".
+- [10] ITU-T Recommendation Q.712 (1996-07): "Definition and function of signalling connection control part messages".
+- [11] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes".
+- [12] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures".
+- [13] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [14] 3GPP TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP".
+- [15] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2".
+- [16] ITU-T Recommendation Q.2630.1: "AAL type 2 signalling protocol - (Capability Set 1)".
+- [17] ITU-T Recommendation Q.2630.2: "AAL type 2 signalling protocol - Capability Set 2".
+- [18] IETF RFC 3332 (2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)".
+- [19] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications".
+- [20] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [21] IETF RFC 793 (1981-09): "TCP, Transmission Control Protocol".
+
+- [22] IETF RFC 791 (1981-09): "Internet Protocol".
+- [23] Void
+- [24] Void
+- [25] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
+- [26] 3GPP TS 23.251: "Network sharing; Architecture and functional description".
+- [27] 3GPP TS23.246: Multimedia Broadcast/Multicast Service (MBMS) Architecture and functional description
+- [28] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
+- [29] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [30] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TS 25.401 [1] apply.
+
+### MBMS related terms and definitions:
+
+**MBMS bearer service:** as defined in TS 23.246 [27].
+
+**MBMS RAB:** as defined in TS 25.346 [28].
+
+**MBMS Iu signalling connection:** as defined in TS 25.346 [28].
+
+**MBMS session start:** as defined in TS 25.346 [28].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                      |
+|---------|------------------------------------------------------|
+| 3G-MSC  | 3 <sup>rd</sup> Generation Mobile Switching Centre   |
+| 3G-SGSN | 3 <sup>rd</sup> Generation Serving GPRS Support Node |
+| AAL     | ATM Adaptation Layer                                 |
+| ATM     | Asynchronous Transfer Mode                           |
+| BC      | Broadcast                                            |
+| BSSMAP  | Base Station Subsystem Management Application Part   |
+| CBS     | Cell Broadcast Service                               |
+| CC      | Connection Confirm                                   |
+| CN      | Core Network                                         |
+| CR      | Connection Release                                   |
+| CREF    | Connection Refusal                                   |
+| CS      | Circuit Switched                                     |
+| GT      | Global Title                                         |
+| GTP-U   | GPRS Tunnelling Protocol                             |
+| GWCN    | Gateway Core Network                                 |
+| IMSI    | International Mobile Subscriber Identity             |
+| IP      | Internet Protocol                                    |
+| ISDN    | Integrated Services Digital Network                  |
+| L-GW    | Local GateWay                                        |
+| LA      | Location Area                                        |
+
+|          |                                                  |
+|----------|--------------------------------------------------|
+| M3UA     | MTP3 User Adaptation Layer                       |
+| MBMS     | Multimedia Broadcast Multicast Service           |
+| MDT      | Minimization of Drive-Tests                      |
+| MOCN     | Multi Operator Core Network                      |
+| NAS      | Non Access Stratum                               |
+| NACC     | Network Assisted Cell Change                     |
+| NNSF     | NAS Node Selection Function                      |
+| O&M      | Operation and Maintenance                        |
+| PLMN     | Public Land Mobile Network                       |
+| PS       | Packet Switched                                  |
+| PSTN     | Public Switched Telephone Network                |
+| PVC      | Permanent Virtual Circuit                        |
+| QoE      | Quality of Experience                            |
+| QoS      | Quality of Service                               |
+| RA       | Routing Area                                     |
+| RAB      | Radio Access Bearer                              |
+| RANAP    | Radio Access Network Application Part            |
+| RIM      | RAN Information Management                       |
+| RLP      | Radio Link Protocol                              |
+| RNC      | Radio Network Controller                         |
+| RNL      | Radio Network Layer                              |
+| RRC      | Radio Resource Control                           |
+| RTCP     | Real Time Control Protocol                       |
+| RTP      | Real Time Protocol                               |
+| SA       | Service Area                                     |
+| SABP     | Service Area Broadcast Protocol                  |
+| SAP      | Service Access Point                             |
+| SCCP     | Signalling Connection Control Part               |
+| SIPTO    | Selected IP Traffic Offload                      |
+| SIPTO@LN | Selected IP Traffic Offload at the Local Network |
+| SCTP     | Stream Control Transmission Protocol             |
+| SNA      | Shared Network Area                              |
+| SPC      | Signalling Point Code                            |
+| SRNS     | Serving Radio Network Subsystem                  |
+| SSN      | Sub-System Number                                |
+| SVC      | Switched Virtual Circuit                         |
+| S-GW     | Serving GateWay                                  |
+| TCP      | Transmission Control Protocol                    |
+| UE       | User Equipment                                   |
+| UDP      | User Datagram Protocol                           |
+| UP       | User Plane                                       |
+| URA      | UTRAN Registration Area                          |
+| UTRAN    | UMTS Terrestrial Radio Access Network            |
+| VC       | Virtual Circuit                                  |
+
+## 3.3 Specification Notations
+
+For the purposes of the present document, the following notations apply:
+
+|           |                                                                                                                                                                                                                       |
+|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Network Layer procedures.  |
+| Message   | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message.                         |
+| Frame     | When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH transport frame. |
+
+# 4 General Aspects
+
+## 4.1 UTRAN Architecture
+
+### 4.1.1 Iu Interface Architecture
+
+The overall UMTS architecture and UTRAN architectures are described in TS 25.401 [1]. This subclause specifies only the architecture of the Iu interface, and shall not constrain the network architecture of either Core or Radio Access Networks.
+
+The Iu interface is specified at the boundary between the Core Network and UTRAN. Figure 4.1 depicts the logical division of the Iu interface. From the Iu perspective, the UTRAN access point is an RNC.
+
+![Figure 4.1: Iu Interface Architecture diagram showing UTRAN on the left and Core Network (CN) on the right, separated by the Iu Interface. UTRAN contains four Node Bs connected to two RNCs. The RNCs are connected to the Iu Interface, which is then connected to the CN. The CN contains three domains: CS Domain, PS Domain, and BC Domain. The Iu Interface is labeled with 'Iu-CS', 'Iu-PS', and 'Iu-BC' corresponding to the CS, PS, and BC domains respectively.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram illustrates the Iu Interface Architecture. On the left, the UTRAN (Radio Access Network) contains four Node Bs connected to two RNCs (Radio Network Controllers). The RNCs are connected to the Iu Interface, which is represented by a vertical dashed line. On the right, the Core Network (CN) is divided into three domains: CS Domain (Circuit Switched), PS Domain (Packet Switched), and BC Domain (Broadcast). The Iu Interface is labeled with 'Iu-CS', 'Iu-PS', and 'Iu-BC' corresponding to the CS, PS, and BC domains respectively. The RNCs are connected to the Iu Interface, which then connects to the CN domains.
+
+Figure 4.1: Iu Interface Architecture diagram showing UTRAN on the left and Core Network (CN) on the right, separated by the Iu Interface. UTRAN contains four Node Bs connected to two RNCs. The RNCs are connected to the Iu Interface, which is then connected to the CN. The CN contains three domains: CS Domain, PS Domain, and BC Domain. The Iu Interface is labeled with 'Iu-CS', 'Iu-PS', and 'Iu-BC' corresponding to the CS, PS, and BC domains respectively.
+
+**Figure 4.1: Iu Interface Architecture**
+
+The Iu interface towards the PS-domain of the core network is called Iu-PS, and the Iu interface towards the CS-domain is called Iu-CS. The differences between Iu-CS and Iu-PS are treated elsewhere in the present document. The Iu interface to the Broadcast domain is called Iu-BC.
+
+There shall not be more than one Iu interface (Iu-PS) towards the PS-domain from any one RNC— except where the NNSF is used, see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. Each RNC shall not have more than one Iu interface (Iu-CS) towards its default CN node within the CS domain, but may also have further Iu interfaces (Iu-CS) towards other CN nodes within the CS domain. (See [6] for definition of Default CN node.) These further Iu interfaces (Iu-CS) shall only be used as a result of intra-MSC inter-system handover or SRNS relocation, in the case the anchor CN node directly connects to the target RNC. There may also be more than one Iu interface towards the CS-Domain if the NNSF is used – see subclause 4.1.3, or in MOCN configuration – see TS 23.251 [26]. There shall not be more than one Iu interface (Iu-BC) from an RNC towards the Broadcast domain.
+
+In the separated core network architecture, this means that there shall be separate signalling and user data connections towards the PS and CS domains – this applies in both transport and radio network layers.
+
+In the combined architecture, there shall be separate connections in the user plane towards the PS and CS domains (in both transport and radio network layers). In the control plane, there shall be separate SCCP connections to the two logical domains.
+
+In either architecture, there can be several RNCs within UTRAN and so UTRAN may have several Iu access points towards the Core Network. As a minimum, each Iu access point (in UTRAN or CN) shall independently fulfil the requirements of the relevant Iu specifications (25.41x series – see clause 7).
+
+### 4.1.2 I<sub>u</sub> connection principles
+
+The I<sub>u</sub> interface has a hierarchical architecture where one higher layer entity controls several lower layer entities. The hierarchy for the CN - UTRAN signalling connection end points is described below:
+
+- Each CN Access Point may be connected to one or more UTRAN Access Points.
+- For the PS domain, each UTRAN Access Point shall not be connected to more than one CN Access Point – except where the NNSF is used, see subclause 4.1.3, or when RNC is shared in MOCN configuration..
+- For the CS domain, each UTRAN Access Point may be connected to one or more CN Access Points.
+- For the BC domain, each UTRAN Access Point may be connected to one CN Access Point only.
+
+### 4.1.3 Implementation of the NAS Node Selection Function
+
+The optional NAS Node Selection Function (NNSF) is described in TS 23.236 [25].
+
+If the NAS Node Selection Function is used by an RNC:
+
+- There may be more than one I<sub>u</sub> interface (I<sub>u</sub>-CS) towards the CS domain and/or more than one I<sub>u</sub> interface (I<sub>u</sub>-PS) towards the PS-domain from this RNC.
+
+### 4.1.4 Implementation of MOCN configuration support
+
+The MOCN configuration is described in TS 23.251 [26]. When the RNC is shared in MOCN configuration:
+
+- There may be more than one I<sub>u</sub> interface (I<sub>u</sub>-CS) towards the CS domain of different CN operators and/or more than one I<sub>u</sub> interface (I<sub>u</sub>-PS) towards the PS-domain of different CN operators from this RNC.
+- The MOCN Rerouting Function shall be supported.
+
+## 4.2 I<sub>u</sub> Interface General Principles
+
+From a UTRAN perspective, maximising the commonality of the various protocols that flow on the I<sub>u</sub> interface is desirable. This means at the minimum that:
+
+- A common set of radio access bearer services will be offered by UTRAN to the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN).
+
+There will be a common functional split between UTRAN and the Core Network nodes, regardless of their type (e.g. 3G-MSC or 3G-SGSN).
+
+Signalling in the radio network control plane shall not depend on the specific choice of transport layers.
+
+## 4.3 I<sub>u</sub> Interface Specification Objectives
+
+The following objectives are partly derived from TR 23.930 [2].
+
+The I<sub>u</sub> interface shall be specified such that it can support:
+
+- the interconnection of RNCs with Core Network Access Points within a single PLMN, and within several PLMNs in case of network sharing, as described in TS 23.251 [26].
+- the interconnection of RNCs with Core Network Access Points irrespective of the manufacturer of any of the elements.
+- all UMTS services.
+
+The I<sub>u</sub> interface shall facilitate the use of the same RNC, MSC or SGSN in all PLMNs.
+
+The I<sub>u</sub> interface shall facilitate the sharing of transport technology between I<sub>u</sub>-PS and I<sub>u</sub>-BC.
+
+The I<sub>u</sub> interface shall allow interworking to the GSM Core Network.
+
+Independence between the protocol layers and between control and user planes shall be maintained on the I<sub>u</sub> interface.
+
+The I<sub>u</sub> interface shall allow independent evolution of technologies within the Core, Radio Access and Transport Networks.
+
+The I<sub>u</sub> interface shall allow separate evolution of O&M facilities.
+
+The I<sub>u</sub> interface shall be standardised as an open and multi-vendor interface.
+
+The I<sub>u</sub> interface specifications shall facilitate the migration of some services from the CS-domain to the PS-domain. In particular, the RANAP protocol shall be common to both PS and CS domains, and the I<sub>u</sub> user plane protocol(s) shall be independent of the core network domain (PS or CS), except where a specific feature is only required for one domain.
+
+## 4.4 I<sub>u</sub> Interface Capabilities
+
+The following capabilities are derived from the requirements described in TR 23.930 [2].
+
+The I<sub>u</sub> interface supports:
+
+- procedures to establish, maintain and release Radio Access Bearers;
+- procedures to perform SRNS relocation, intra-system handover, inter-system handover and inter-system change;
+- procedures to support the Cell Broadcast service;
+- a set of general procedures, not related to a specific UE;
+- the separation of each UE on the protocol level for user specific signalling management;
+- the transfer of NAS signalling messages between UE and CN;
+- location services by transferring requests from the CN to UTRAN, and location information from UTRAN to CN. The location information may comprise a geographical area identifier or global co-ordinates with uncertainty parameters;
+- simultaneous access to multiple CN domains for a single UE;
+- mechanisms for resource reservation for packet data streams;
+- procedures to support MBMS bearer services;
+- mechanisms to support SIPTO at Iu-PS for a specific UE (optional);
+- mechanisms to support SIPTO at the Local Network with standalone GW for a specific UE (optional).
+
+## 4.5 I<sub>u</sub> Interface Characteristics
+
+### 4.5.1 Use of Transport Network User Plane as Signalling Bearer
+
+#### 4.5.1.1 Use of SCCP
+
+##### 4.5.1.1.1 General
+
+The SCCP (ITU-T Rec. Q.711 [9] /ITU-T Rec. Q.712 [10]/ITU-T Rec. Q.713 [11]/ITU-T Rec. Q.714 [12]) is used to support signalling messages between the CNs and the RNC. One user function of the SCCP, called Radio Access Network Application Part (RANAP), is defined. The RANAP uses one SCCP signalling connection per active UE and CN for the transfer of layer 3 messages. RANAP also uses one SCCP signalling connection per MBMS bearer service.
+
+Both connectionless and connection-oriented procedures are used to support the RANAP. TS 25.413 [6] explains whether connection oriented or connectionless services should be used for each layer 3 procedure.
+
+RANAP may use SSN, SPC and/or GT and any combination of them as addressing schemes for the SCCP. Which of the available addressing scheme to use for the SCCP is an operator matter.
+
+When GT addressing is utilised, the following settings shall be used:
+
+- SSN Indicator = 1 (RANAP SSN as defined in TS 23.003 [13] shall always be included).
+- Global Title Indicator = 0100 (GT includes translation type, numbering plan, encoding scheme and nature of address indicator).
+- Translation Type = 0000 0000 (not used).
+- Numbering Plan = 0001 (E.163/4).
+- Nature of Address Indicator = 000 0100 (International Significant Number).
+- Encoding Scheme = 0001 or 0010 (BCD, odd or even).
+- Routing indicator = 0 or 1 (route on GT or PC/SSN).
+
+When used, the GT shall be the E.164 address of the relevant node.
+
+The following subclauses describe the use of SCCP connections for RANAP transactions. Subclause 4.5.1.2 describes the connection establishment procedures. Subclause 4.5.1.3 describes the connection release procedures. Subclause 4.5.1.4 describes abnormal conditions.
+
+##### 4.5.1.1.2 SCCP Connection Establishment procedure
+
+A new SCCP connection is established when information related to the communication between a UE and the network has to be exchanged between RNC and CN, and no SCCP connection exists between the CN and the RNC involved, for the concerned UE. A new SCCP connection is also established for MBMS service purpose between the RNC and CN.
+
+Various SCCP connection establishment cases have to be distinguished:
+
+- i) RNC Initiated SCCP Signalling Connection for a UE;
+- ii) CN Initiated SCCP Signalling Connection for a UE;
+- iii) CN Initiated SCCP Signalling Connection for an MBMS Service.
+
+The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future.
+
+###### 4.5.1.1.2.1 Establishment procedure in case i
+
+The SCCP signalling connection establishment is initiated, by the RNC, at the reception of the first layer 3 non access stratum message from the UE or at the execution of the enhanced relocation or at the initiation of the UE Registration Query procedure.
+
+###### Initiation
+
+The RNC sends SCCP CONNECTION REQUEST message to the Core Network. A RANAP message shall be included in the user data field of the SCCP CONNECTION REQUEST message when the RANAP message size is less than or equal to the maximum size of the user data field in the SCCP CONNECTION REQUEST message. When the RANAP message is longer than the maximum size, the user data field shall not be included in the SCCP CONNECTION REQUEST message.
+
+If the Core Network receives an SCCP CONNECTION REQUEST message for a UE for which an SCCP connection already exists, or if the Core Network receives an SCCP CONNECTION REQUEST message that does not include a user data field, and later finds out that the SCCP CONNECTION REQUEST message was for a UE for which an SCCP connection already exists, the Core Network shall ensure that the new SCCP connection and the already existing SCCP connection are for the same UE, e.g. by security functions, and if so, release the already existing SCCP connection via the normal Iu Release procedure and all UTRAN resources allocated to it.
+
+###### Termination
+
+- **successful outcome**
+  - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the RNC.
+- **unsuccessful outcome**
+
+- If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the RNC. This message may contain a RANAP message in the user data field.
+
+For more information on how the RANAP procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query are handled, please see the elementary procedures Initial UE Message, Enhanced Relocation Complete and UE Registration Query in TS 25.413 [6].
+
+![Sequence diagram for RNC Initiated SCCP Signalling Connection. The diagram shows the RNC sending a CR (SSN=RANAP, a1=x) to the CN, and the CN responding with either a CC (a1=y, a2=x) or a CREF (a2=x).](410562339ce067fdc6fa41940c118658_img.jpg)
+
+```
+
+sequenceDiagram
+    participant RNC
+    participant CN
+    Note right of RNC: a1 = source local reference,
+    a2 = destination local reference,
+    x = SCCP connection reference at the RNC,
+    y = SCCP connection reference at the CN.
+
+    RNC->>CN: CR {SSN=RANAP, a1=x, RANAP message or no user data}
+    CN-->>RNC: CC {a1=y, a2=x, RANAP message or no user data}
+    Note right of CN: or
+    CN-->>RNC: CREF {a2=x, RANAP message or no user data}
+  
+```
+
+Sequence diagram for RNC Initiated SCCP Signalling Connection. The diagram shows the RNC sending a CR (SSN=RANAP, a1=x) to the CN, and the CN responding with either a CC (a1=y, a2=x) or a CREF (a2=x).
+
+**Figure 4.2: Setting-up of RNC Initiated SCCP Signalling Connection**
+
+###### **4.5.1.1.2.2 Establishment procedure in case ii**
+
+The SCCP signalling connection establishment is initiated, by the Core Network, in connection with performing a Relocation.
+
+###### **Initiation**
+
+The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message.
+
+###### **Termination**
+
+- **successful outcome**
+  - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network.
+- **unsuccessful outcome**
+  - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field.
+
+![Sequence diagram for CN Initiated SCCP Signalling Connection. The diagram shows the CN sending a CR (SSN=RANAP, a1=y) to the RNC, and the RNC responding with either a CC (a1=x, a2=y) or a CREF (a2=y).](f20786b603b41e24b5d5899f710b5947_img.jpg)
+
+```
+
+sequenceDiagram
+    participant RNC
+    participant CN
+    Note right of RNC: a1 = source local reference,
+    a2 = destination local reference,
+    x = SCCP connection reference at the RNC,
+    y = SCCP connection reference at the CN.
+
+    CN->>RNC: CR {SSN=RANAP, a1=y, RANAP message or no user data}
+    RNC-->>CN: CC {a1=x, a2=y, RANAP message or no user data}
+    Note right of RNC: or
+    RNC-->>CN: CREF {a2=y, RANAP message or no user data}
+  
+```
+
+Sequence diagram for CN Initiated SCCP Signalling Connection. The diagram shows the CN sending a CR (SSN=RANAP, a1=y) to the RNC, and the RNC responding with either a CC (a1=x, a2=y) or a CREF (a2=y).
+
+**Figure 4.3: Setting-up of CN Initiated SCCP Signalling Connection**
+
+###### 4.5.1.1.2.3 Establishment procedure in case iii
+
+The SCCP signalling connection establishment is initiated, by the Core Network, to establish a new SCCP connection between the RNC and the CN for an MBMS service at the start of an MBMS session and when no SCCP connection already exists between the CN and the RNC involved, for the concerned MBMS service.
+
+###### Initiation
+
+The Core Network initiates the connection establishment by sending an SCCP CONNECTION REQUEST message to the RNC. Optionally, a RANAP message may be included in the user data field of the SCCP CONNECTION REQUEST message.
+
+###### Termination
+
+- **successful outcome**
+  - The SCCP CONNECTION CONFIRM message, which may optionally contain a connection oriented RANAP message in the user data field, is returned to the Core Network.
+- **unsuccessful outcome**
+  - If the SCCP signalling connection establishment fails, an SCCP CONNECTION REFUSAL message will be sent back to the Core Network. This message may contain a RANAP message in the user data field.
+
+##### 4.5.1.1.3 SCCP Connection Release procedure
+
+This procedure is always initiated at the Core Network side in normal release case.
+
+An SCCP connection is released when the CN realises that a given signalling connection is no longer required.
+
+The CN sends a SCCP RELEASED message.
+
+The procedure may be initiated at the Core Network side and the RNC side in any abnormal release case.
+
+##### 4.5.1.1.4 General SCCP Abnormal Conditions
+
+If a user-out-of-service information or signalling-point-inaccessible information is received by the RANAP, no new attempt to establish SCCP connections towards the affected point code will be started until the corresponding user-in-service information or signalling-point-accessible information is received.
+
+When a user-out-of-service information or signalling-point-inaccessible is received by the RNC, an optional timer may be started. When the timer expires, all the SCCP connections towards the affected point code will be released. When the user-in-service or signalling-point-accessible is received, the timer is stopped.
+
+If for any reason an SCCP connection is released, the optional timer expires or a connection refusal is received while any of the RANAP procedures are being performed or while a dedicated resource is still allocated, the following actions are taken:
+
+###### At RNC:
+
+- Any RNC procedure relating to that connection is abandoned.
+- The UTRAN resources allocated to the connection are released.
+
+###### At Core Network:
+
+- The resources associated with the SCCP connection are cleared as soon as possible.
+
+#### 4.5.1.2 Use of MTP3b
+
+- For a given MSC, the RNC shall be able to access RANAP and ALCAP either under the same MTP3b (IETF RFC 3332 [18]) destination point code, or under different point codes;
+- For a given RNC, the MSC shall be able to access RANAP and ALCAP either under the same MTP3b destination point code, or under different point codes.
+
+### 4.5.2 Use of Transport Network User Plane as User Data Bearer
+
+#### 4.5.2.1 Use of AAL2
+
+In the ATM transport option AAL2 is used as the user data bearer towards the CS domain.
+
+Q.2630.2 is used as the protocol for dynamically setup AAL-2 connections over Iu towards the CS domain. Q.2630.2 adds new optional capabilities to Q.2630.1.
+
+#### 4.5.2.2 Use of GTP-U
+
+GTP-U is used as the user data bearer towards the PS domain.
+
+RANAP Signalling is used to establish, modify and release the GTP-U tunnels towards the PS domain.
+
+#### 4.5.2.3 Use of RTP
+
+RTP/UDP/IP (IETF RFC 1889 [19]/ IETF RFC 768 [20]/ IETF RFC 791[22]) is used as the user data bearer towards the CS domain in the IP transport option. The use of RTCP (IETF RFC 1889 [19]) is optional.
+
+RANAP Signalling is used to establish, modify and release RTP sessions towards the CS domain.
+
+### 4.5.3 Use of Transport Network User Plane on Iu-BC
+
+TCP/IP (IETF RFC 793[21]/ IETF RFC 791[22]) is used as the bearer for the radio network layer protocol over I<sub>u</sub>-BC.
+
+The TCP connection is normally established by the CN using standard TCP procedures.
+
+A new TCP connection is established by the RNC only when there is information (e.g. failure or restart indications) that needs to be sent from RNC to the CN, and there is no existing TCP connection. The RNC shall establish the connection using standard TCP procedures.
+
+The node that established the connection shall release the TCP connection.
+
+# --- 5 Functions of the I<sub>u</sub> Interface Protocols & Functional Split
+
+## 5.1 General
+
+This subclause defines the functional split between the core network and the UMTS radio access network. In addition, the possible interaction between the functions is defined. The functional split is shown in table 5.1.
+
+**Table 5.1: Iu interface functional split**
+
+| Function                                                        | UTRAN | CN |
+|-----------------------------------------------------------------|-------|----|
+| <b>RAB management functions:</b>                                |       |    |
+| RAB establishment, modification and release                     | X     | X  |
+| RAB characteristics mapping I <sub>u</sub> transmission bearers | X     |    |
+| RAB characteristics mapping Uu bearers                          | X     |    |
+| RAB queuing, pre-emption and priority                           | X     | X  |
+| <b>Radio Resource Management functions:</b>                     |       |    |
+| Radio Resource admission control                                | X     |    |
+| Broadcast Information                                           | X     | X  |
+| <b>I<sub>u</sub> link Management functions:</b>                 |       |    |
+| I <sub>u</sub> signalling link management                       | X     | X  |
+| ATM VC management                                               | X     | X  |
+| AAL2 establish and release                                      | X     | X  |
+| AAL5 management                                                 | X     | X  |
+| GTP-U Tunnels management                                        | X     | X  |
+| TCP Management                                                  | X     | X  |
+| Buffer Management                                               | X     |    |
+| <b>I<sub>u</sub> U-plane (RNL) Management:</b>                  |       |    |
+| I <sub>u</sub> U-plane frame protocol management                |       | X  |
+| I <sub>u</sub> U-plane frame protocol initialization            | X     |    |
+| <b>Mobility management functions:</b>                           |       |    |
+| Location information reporting                                  | X     | X  |
+| Handover and Relocation                                         |       |    |
+| Inter RNC hard HO, Iur not used or not available                | X     | X  |
+| Serving RNS Relocation (intra/inter MSC)                        | X     | X  |
+| Inter system hard HO (UMTS-GSM)                                 | X     | X  |
+| Inter system Change (UMTS-GSM)                                  | X     | X  |
+| Paging Triggering                                               |       | X  |
+| GERAN System Information Retrieval                              | X     | X  |
+| <b>Security Functions:</b>                                      |       |    |
+| Data confidentiality                                            |       |    |
+| Radio interface ciphering                                       | X     |    |
+| Ciphering key management                                        |       | X  |
+| User identity confidentiality                                   | X     | X  |
+| Data integrity                                                  |       |    |
+| Integrity checking                                              | X     |    |
+| Integrity key management                                        |       | X  |
+| <b>Service and Network Access functions:</b>                    |       |    |
+| CN Signalling data                                              | X     | X  |
+| Data Volume Reporting                                           | X     |    |
+| UE Tracing                                                      | X     | X  |
+| MDT                                                             | X     | X  |
+| Location reporting                                              | X     | X  |
+| QoE                                                             | X     | X  |
+| <b>I<sub>u</sub> Co-ordination functions:</b>                   |       |    |
+| Paging co-ordination                                            | X     | X  |
+| NAS Node Selection Function                                     | X     |    |
+| MOCN Rerouting Function                                         | X     | X  |
+| SIPTO at I <sub>u</sub> -PS                                     | X     | X  |
+| SIPTO at the Local Network with Standalone GW                   | X     | X  |
+| <b>MBMS functions</b>                                           | X     | X  |
+| MBMS RAB Management                                             | X     | X  |
+| MBMS UE Linking Function                                        | X     | X  |
+| MBMS Registration Control Function                              | X     | X  |
+| MBMS Enquiry Function                                           | X     | X  |
+
+## 5.2 RAB management Functions
+
+### 5.2.1 RAB establishment, modification and release function
+
+The RAB, Radio Access Bearer, is defined to be set-up between UE and CN. Depending on subscription, service, requested QoS etc. different types of RABs will be used. It is the CN that controls towards the UTRAN the establishment, modification or release of a RAB. Furthermore, the CN selects the type of the transport bearer, i.e. ATM or IP.
+
+The RAB identity is allocated by CN by mapping the value for the NAS Binding information (from the actual protocol IE for the respective CN domain) to the RAB ID as specified in TS 23.110 [3]. The RAB identity is globally significant on both the radio bearer and on the Iu bearer for a given UE in a particular CN domain.
+
+RAB establishment, modification and release is a CN initiated function.
+
+RAB establishment, modification and release is a UTRAN executed function.
+
+RAB release request is a UTRAN initiated function, triggered when UTRAN e.g. fails to keep the RAB established with the UE.
+
+### 5.2.2 RAB characteristics mapping to Uu bearers function
+
+The RAB characteristics mapping function is used to map the radio access bearers to the Uu bearers. The mapping is performed during the establishment of the RAB. UTRAN shall perform the mapping between the bearers.
+
+RAB mapping to Uu transmission bearers is a UTRAN function.
+
+### 5.2.3 RAB characteristics mapping to Iu transport bearers
+
+The RAB characteristics mapping function is used to map the radio access bearers to the Iu interface transport bearers. The mapping is performed during the establishment of the RAB.
+
+UTRAN shall perform this mapping between the bearers if AAL2 is used, since it is the UTRAN that establishes the AAL2 connections.
+
+In case of RAB towards the PS domain, UTRAN shall perform the mapping between the radio access bearers and the IP layer.
+
+RAB characteristics mapping to Iu transport bearers is a UTRAN function.
+
+### 5.2.4 RAB queuing, pre-emption and priority function
+
+The allocation/retention priority level of a RAB is determined by the CN based on e.g. subscription information, QoS information etc. Accordingly, the CN shall request RAB establishment or modification with an indication of the priority level and the pre-emption capability of that RAB and the queuing vulnerability. Queuing and resource pre-emption shall be performed by UTRAN accordingly.
+
+RAB queuing, pre-emption and allocation/retention priority handling is a UTRAN controlled function.
+
+RAB queuing, pre-emption and allocation/retention priority setting is a CN function.
+
+## 5.3 Radio Resource Management over Iu
+
+### 5.3.1 Radio resource admission control
+
+When UTRAN receives a request to establish or modify a radio access bearer from the CN, the current radio resource situation is analysed and the admission control either accepts or rejects the request. This is called "Radio resource admission control" and is handled by the UTRAN. If the request is queued, it is handled by the RAB queuing, pre-emption and priority function.
+
+### 5.3.2 Broadcast information management
+
+This function consists in the broadcast from network toward UE of some information in the coverage area of the whole network or different parts of the network.
+
+There are two kinds of Broadcast information management. UTRAN broadcast information, and Cell Broadcast information management. All UTRAN broadcast information management shall be handled locally within UTRAN. All Cell Broadcast information is controlled by CN and executed by UTRAN.
+
+## 5.4 I<sub>u</sub> link Management functions
+
+### 5.4.1 I<sub>u</sub> Signalling Link Management function
+
+The I<sub>u</sub> signalling link management function provides a reliable transfer of the radio network signalling between UTRAN and CN. Both CN and UTRAN manage the function.
+
+This function is in particular responsible for I<sub>u</sub> signalling connection establishment, which can be established either by the CN or the RNC and for I<sub>u</sub> signalling connection release, which is controlled by CN possibly upon UTRAN request.
+
+### 5.4.2 ATM Virtual Connection Management function
+
+This function refers to handling of ATM Virtual Connections (VCs) between CN and UTRAN.
+
+This function shall be used to establish, maintain and release the ATM VCs. For permanent VCs, it is regarded to be an O&M function.
+
+This function also includes the selection of a Virtual Circuit to be used for a particular RAB. The selection of ATM VC upon an I<sub>u</sub> radio access bearer service request, shall be done by UTRAN. The selected VC shall fulfil the requirements of the request. The VC may consist of several sublinks: such as SCCP connections, AAL2 connections or IP flows.
+
+### 5.4.3 AAL2 connection establish and release function
+
+This function is used to establish and release the AAL type 2 connections between CN and UTRAN upon an I<sub>u</sub> radio access bearer service request. Both UTRAN and CN are taking part in the establishment of AAL2 connection. UTRAN shall initiate both establishment and release of AAL2 connections. In abnormal cases, the CN may also initiate release of AAL2 connections. The use of AAL2 for I<sub>u</sub> transmission bearers depends on type of CN.
+
+### 5.4.4 AAL5 management function
+
+AAL5 connections between CN and UTRAN shall be pre-configured at system initialisation. Basic configuration is PVCs. For user data, SVC is possible.
+
+The AAL5 management is a function handled by both the CN and the UTRAN.
+
+### 5.4.5 GTP-U tunnels management function
+
+This function is used to establish and release GTP-U tunnels between CN and UTRAN upon a radio access bearer service request. This involves assigning a tunnel identifier for each direction and the creation of a context containing the tunnel information. The tunnel identifier for the downlink is allocated by the UTRAN, and the tunnel identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the context. The use of GTP-U for I<sub>u</sub> transport bearers depends on type of CN.
+
+### 5.4.6 TCP Management Function
+
+This function is used to establish and release the TCP connections between CN and UTRAN over I<sub>u</sub>-BC.
+
+The TCP management function exists in both UTRAN and CN.
+
+### 5.4.7 Buffer Management
+
+Congestion control shall be performed over the I<sub>u</sub> user plane using buffer management and no flow control.
+
+This function includes buffers to store received packet data units that at reception can not be processed due to e.g. congestion. In UTRAN, there must be a buffer management function handling received packets from the peer CN node.
+
+The used mechanism is not in the scope of the present document and not relevant to be standardised.
+
+Buffer management is a UTRAN function.
+
+### 5.4.8 RTP Session Management Function
+
+This function is used to establish and release RTP sessions between CN and UTRAN upon a radio access bearer service request. This involves assigning a RTP session identifier for each direction and the creation of a context containing the RTP session information. The RTP session identifier for the downlink is allocated by the UTRAN, and the RTP session identifier for the uplink is allocated by the CN. Both CN and UTRAN should maintain the RTP session context. The use of RTP for Iu transport bearers depends on type of CN.
+
+## 5.5 I<sub>u</sub> U-plane (RNL) Management Functions
+
+### 5.5.1 I<sub>u</sub> U-plane frame protocol mode selection function
+
+The I<sub>u</sub> UP in the Radio Network Layer provides modes of operation that can be activated on RAB basis. For a given RAB, the I<sub>u</sub> UP operates either in a Transparent or in Support mode. I<sub>u</sub> U-plane frame protocol mode is selected by the CN. A set of appropriate U-plane version(s) is indicated within RANAP. The final U-plane version is selected during the I<sub>u</sub> UP initiation procedure among the indicated version(s).
+
+This function is a CN function.
+
+### 5.5.2 I<sub>u</sub> U-plane frame protocol initialisation
+
+I<sub>u</sub> U-plane frame protocol is initialised by the UTRAN. In certain cases, as described in TS 23.153 [15], the I<sub>u</sub> U-plane frame protocol may be initialised by the CN.
+
+## 5.6 Mobility Management Functions
+
+### 5.6.1 Location information update function
+
+Some functionality within the CN, needs information about the present location of an active UE, i.e. a UE with established signalling connection. The Location information update function is used to transfer this information from the UTRAN to the CN. It is the UTRAN responsibility to send this information initially at the signalling connection establishment for a UE and at any change of the UE location as long as the signalling connection exists. For this function, the location information shall be at Location and Routing Area level.
+
+### 5.6.2 Handover and Relocation functions
+
+#### 5.6.2.1 Inter RNC hard HO function, I<sub>ur</sub> not used or not available
+
+This functionality includes procedures for handover from one RNC to another RNC when I<sub>ur</sub> interface is not used or is not available, i.e. soft handover is not possible. The connection is switched in the CN, so both UTRAN and CN are involved. Both intra and inter CN entity cases are applicable. This functionality includes also the moving of the Serving RNS functionality from one RNC to another RNC.
+
+#### 5.6.2.2 Serving RNS Relocation function
+
+This functionality allows moving the Serving RNS functionality from one RNC to another RNC, e.g. closer to where the UE has moved during the communication. The Serving RNS Relocation procedure may be applied when active cell management functionality has created a suitable situation for it. Both UTRAN and CN are involved.
+
+#### 5.6.2.3 Inter system Handover (e.g. UMTS-GSM) function
+
+Inter system handover is performed when a mobile hands over between cells belonging to different systems such as GSM and UMTS. For intersystem handover between UMTS and GSM, the GSM procedures are used within the GSM network. Both UTRAN and CN are involved.
+
+NOTE: The GSM BSSMAP procedures are outside the scope of the present document.
+
+### 5.6.2A Inter System Change (e.g. UMTS-GSM) function
+
+Inter system change is performed when a GPRS attached mobile moves from cells belonging to different systems such as GSM and UMTS. For intersystem change between UMTS and GSM, the GPRS procedures are used within the GPRS network. Both UTRAN and CN are involved.
+
+### 5.6.3 Paging Triggering
+
+The Core Network shall, when considered necessary, trigger the Location/Routing/RNC Area paging in the UTRAN system.
+
+### 5.6.4 Shared Networks Access Control
+
+The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to the UTRAN and the neighbouring networks on a PLMN or an SNA basis. The Shared Networks Access Control function is further described in TS 25.401 [1].
+
+### 5.6.5 GERAN System Information Retrieval
+
+In order to provide the UE with system information related to NACC towards a GERAN system - to be used as an optimisation - the GERAN System Information Retrieval function allows the source system to request GERAN (via CN) to provide this system information. The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in TS 25.401 [1]
+
+## 5.7 Security Functions
+
+### 5.7.1 Data Confidentiality
+
+#### 5.7.1.1 Radio interface ciphering function
+
+The radio interface shall be ciphered upon request of the Core Network. Both Signalling and user data may be subject to ciphering. The ciphering shall be done within UTRAN.
+
+#### 5.7.1.2 Ciphering key management function
+
+The ciphering key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm.
+
+### 5.7.2 Data integrity
+
+#### 5.7.2.1 Integrity checking
+
+The purpose of the integrity check is to make sure that the signalling continues between the same elements as by authentication. The integrity check shall be done within the UTRAN.
+
+#### 5.7.2.2 Integrity key management
+
+The integrity key and the permitted algorithm shall be supplied by the CN. UTRAN selects the used algorithm.
+
+## 5.8 Service and Network Access Functions
+
+### 5.8.1 Core Network signalling data transfer function
+
+The NAS CN signalling data such as Call Control (CC), Session Management (SM), Mobility Management (MM), Short Message Services Point to Point and Supplementary Services (SS) shall be transparently conveyed between the CN and the UE. Over the Iu interface, the same Iu interface channel that is used for the UTRAN-CN signalling shall be used.
+
+### 5.8.2 Data Volume Reporting
+
+The data volume reporting function is used to report the volume of unacknowledged data to the CN. The function shall be in the UTRAN and is triggered from the CN.
+
+### 5.8.3 UE Tracing
+
+This feature allows tracing of various events related to the UE and its activities. This is an O&M functionality.
+
+### 5.8.4 Location reporting function
+
+The positioning function performs the determination of the geographical position and optionally the velocity for an UE. The location reporting function transfers the positioning information between the UTRAN and the CN according to CN commands. This function involves UTRAN and CN.
+
+### 5.8.5 MDT
+
+This feature enables the transfer of MDT measurements collected by the UE, as defined in TS 37.320 [30]. This is an O&M functionality.
+
+## 5.9 Co-ordination Functions
+
+### 5.9.1 Paging Co-ordination function
+
+The two CN domain architecture implies need for a page co-ordination, i.e. handling of page triggered by one CN node when UE has a signalling connection to the other CN node. The paging co-ordination is performed by UTRAN and/or optionally by CN. The Common ID is used for UTRAN paging co-ordination. The CN provides the UTRAN with the Common ID.
+
+The paging co-ordination is a UTRAN function. Optionally the paging co-ordination may be performed in the CN.
+
+### 5.9.2 NAS Node Selection Function
+
+The optional NAS Node Selection Function enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource.
+
+The method by which the RNC initially assigns CN resources is implementation dependent.
+
+The NNSF is described in detail in TS 23.236 [25].
+
+### 5.9.3 Information Transfer Function
+
+The Information Transfer function allows configuration data to be passed from the CN to the RNC upon CN trigger. This function is operated in acknowledged mode. It should be used by the CN to maintain alignment between the data as configured in the CN and the configuration data provided to the UTRAN. This may be used e.g. to coordinate the SNA geographical definition (LA to SNA mapping) between CN and UTRAN in order to apply access control on an SNA basis.
+
+### 5.9.4 MOCN Rerouting Function
+
+Rerouting is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration for network sharing non-supporting UEs when they perform initial attach /registration. In this case RNC may not know towards which CN to route the initial UE request message and the latter may be rerouted to another CN via RNC.
+
+The MOCN Rerouting Function is described in detail in TS 23.251 [26].
+
+### 5.9.5 SIPTO at Iu-PS Function
+
+If supported, SIPTO at Iu-PS Function provides the capability to offload certain PS RABs from the CN at RAB setup. The SIPTO at Iu-PS is implementation dependent and may be implemented in a separate entity outside of RNS, for further information see TS 23.060 [29].
+
+### 5.9.6 SIPTO at the Local Network with Standalone GW
+
+SIPTO@LN provides access to a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's core network by using standalone GW (with S-GW and L-GW collocated) in the local network, as specified in TS 23.060 [29].
+
+## 5.10 MBMS Functions
+
+### 5.10.1 MBMS RAB Management functions
+
+The MBMS RAB, Radio Access Bearer, is defined to be set-up between the CN and one or several UEs for MBMS. Depending on the MBMS service characteristics, different types of MBMS RABs will be used. It is the CN that controls towards the UTRAN the establishment, update or release of an MBMS RAB. The MBMS RAB is defined for the PS domain only.
+
+### 5.10.2 MBMS UE Linking Function
+
+This function provides the RNC with the list of MBMS services that a given UE, with existing dedicated Iu-PS signalling connection, has “joined” or has “left” TS 23.246 [27].
+
+### 5.10.3 MBMS Registration Control Function
+
+This function allows the RNC to either register or deregister to the PS core network domain for a specific MBMS bearer service so that it is notified whenever a session of this service starts.
+
+It also allows the CN to inform the RNC that a given MBMS bearer service is no longer available.
+
+### 5.10.4 MBMS Enquiry Function
+
+This function allows the RNC to request to the SGSN the list of MBMS bearer services that a given UE has “joined” TS 23.246 [27] or the IP Multicast Address and APN defined in TS 23.246 [27] which correspond to a given MBMS bearer service.
+
+# --- 6 I<sub>u</sub> Interface Protocol Structure
+
+## 6.1 General
+
+The Radio Network signalling over I<sub>u</sub> consists of the Radio Access Network Application Part (RANAP). The RANAP protocol consists of mechanisms to handle all procedures between the CN and UTRAN. It is also capable of conveying messages transparently between the CN and the UE without interpretation or processing by the UTRAN.
+
+Over the I<sub>u</sub> interface the RANAP protocol is, e.g. used for:
+
+- Facilitate a set of general UTRAN procedures from the Core Network such as paging -notification as defined by the notification SAP in TS 23.110 [3].
+- Separate each User Equipment (UE) on the protocol level for mobile specific signalling management as defined by the dedicated SAP in TS 23.110 [3].
+- Transfer of transparent non-access signalling as defined in the dedicated SAP in TS 23.110 [3].
+- Request of various types of UTRAN Radio Access Bearers through the dedicated SAP in TS 23.110 [3].
+- Perform the SRNS Relocation function.
+- Perform the various MBMS procedures.
+- Perform SIPTO at Iu-PS (optional).
+
+The Radio Access Bearers are provided by the Access Stratum.
+
+Over Iu-BC, a datagram mechanism is used, so there is no clear separation of control and user planes, and the SABP protocol is used for data transfer and signalling.
+
+## 6.2 Iu-CS
+
+Figure 6.1 shows the protocol structure for I<sub>u</sub>-CS, following the structure described in TS 25.401 [1].
+
+![Protocol structure diagram for Iu-CS interface towards CS Domain. It shows three vertical columns: Control Plane, Transport Network Control Plane, and User Plane. The Control Plane contains RANAP, SCCP, M3UA, MTP3b, SCTP, IP, AAL5, Data Link, and ATM. The Transport Network Control Plane contains Q.2630.2, Q.2150.1, MTP3b, SSCF-NNI, SSCOP, AAL5, and ATM. The User Plane contains Iu UP Protocol Layer, AAL2, RTP/RTCP(*), UDP/IP, ATM, and Data Link. All three planes share a common Physical Layer at the bottom. The Radio Network Layer is at the top, and the Transport Network Layer is shown on the left side.](171115f072e42b379238ed0dd438e9d7_img.jpg)
+
+Protocol structure diagram for Iu-CS interface towards CS Domain. It shows three vertical columns: Control Plane, Transport Network Control Plane, and User Plane. The Control Plane contains RANAP, SCCP, M3UA, MTP3b, SCTP, IP, AAL5, Data Link, and ATM. The Transport Network Control Plane contains Q.2630.2, Q.2150.1, MTP3b, SSCF-NNI, SSCOP, AAL5, and ATM. The User Plane contains Iu UP Protocol Layer, AAL2, RTP/RTCP(\*), UDP/IP, ATM, and Data Link. All three planes share a common Physical Layer at the bottom. The Radio Network Layer is at the top, and the Transport Network Layer is shown on the left side.
+
+\*) RTCP is optional.
+
+Figure 6.1: I<sub>u</sub> -Interface Protocol Structure towards CS Domain
+
+## 6.3 I<sub>u</sub>-BC
+
+Figure 6.2 shows the protocol structure for the I<sub>u</sub>-BC.
+
+![Protocol stack diagram for Iu-BC interface showing layers from Radio Network Layer down to Physical Layer, with SA Broadcast Plane and Transport Network Layer components.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+The diagram illustrates the protocol structure for the I<sub>u</sub>-BC interface. It is divided into two main sections: the Radio Network Layer and the Transport Network Layer.
+
+- Radio Network Layer:** Contains the SA Broadcast Plane, which includes the SABP Protocol Layer.
+- Transport Network Layer:** Contains the Transport User Plane and the Network Plane. The Transport User Plane consists of TCP, IP, and AAL5 layers. The Network Plane consists of TCP, IP, and ATM layers. The ATM layer is connected to the Data Link layer, which is connected to the Physical Layer.
+
+Vertical arrows indicate the flow of data: from the SABP Protocol Layer down through the Transport User Plane (TCP, IP, AAL5) to the ATM layer, and from the Network Plane (TCP, IP) down through the Data Link layer to the Physical Layer. Double-headed vertical arrows connect the AAL5 layer to the ATM layer and the IP layer to the Data Link layer.
+
+Protocol stack diagram for Iu-BC interface showing layers from Radio Network Layer down to Physical Layer, with SA Broadcast Plane and Transport Network Layer components.
+
+**Figure 6.2: I<sub>u</sub> Interface Protocol Structure towards Broadcast Domain**
+
+## 6.4 Iu-PS
+
+Figure 6.3 shows the protocol structure for Iu-PS, following the structure described in TS 25.401 [1].
+
+![Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram shows the protocol stack for the Iu-PS interface. At the top is the Radio Network Layer, which contains the Control Plane (RANAP) and the User Plane (Iu UP Protocol Layer). Below this is the Transport Network Layer, which is divided into three vertical sections: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The left section contains SCCP, MTP3-B, M3UA, SCTP, SSCF-NNI, SSCP, AAL5, ATM, and Physical Layer. The right section contains GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. Arrows indicate the flow of data between the layers.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg)
+
+Figure 6.3: Iu Interface Protocol Structure towards PS Domain. The diagram shows the protocol stack for the Iu-PS interface. At the top is the Radio Network Layer, which contains the Control Plane (RANAP) and the User Plane (Iu UP Protocol Layer). Below this is the Transport Network Layer, which is divided into three vertical sections: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The left section contains SCCP, MTP3-B, M3UA, SCTP, SSCF-NNI, SSCP, AAL5, ATM, and Physical Layer. The right section contains GTP-U, UDP, IP, AAL5, ATM, and Physical Layer. Arrows indicate the flow of data between the layers.
+
+Figure 6.3: Iu Interface Protocol Structure towards PS Domain
+
+# 7 Other Iu Interface Specifications
+
+## 7.1 UTRAN Iu Interface: Layer 1 (3GPP TS 25.411)
+
+TS 25.411 [4] specifies the range of physical layer technologies that may be used to support the Iu interface.
+
+## 7.2 UTRAN Iu Interface: Signalling Transport (3GPP TS 25.412)
+
+TS 25.412 [5] specifies the signalling bearers for the RANAP and transport network control plane protocols for both Iu-PS and Iu-CS.
+
+## 7.3 UTRAN Iu Interface: RANAP Specification (3GPP TS 25.413)
+
+TS 25.413 [6] specifies the RANAP protocol for radio network control plane signalling over the Iu interface.
+
+## 7.4 UTRAN Iu Interface: Data Transport and Transport Signalling (3GPP TS 25.414)
+
+TS 25.414 [7] specifies the transport bearers for the user plane of the Iu interface. It also specifies the protocol used to control these transport bearers.
+
+## 7.5 UTRAN I<sub>u</sub> Interface: CN-UTRAN User Plane Protocol (3GPP TS 25.415)
+
+TS 25.415 [8] specifies the user plane frame handling protocol for the I<sub>u</sub> interface.
+
+## 7.6 UTRAN I<sub>u</sub> Interface: Service Area Broadcast Protocol SABP (3GPP TS 25.419)
+
+TS 25.419 [14] specifies the communication requirements over the I<sub>u</sub> interface towards the BC domain.
+
+## 7.7 Summary
+
+The present document, 3GPP TS 25.410, specifies the general aspects and principles of the I<sub>u</sub> interface as a whole.
+
+The relationship between the other technical specifications that define the UTRAN I<sub>u</sub> interface is shown in figure 7.1.
+
+![Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the protocol stack for the Iu interface, organized into three vertical columns: Control Plane, User Plane, and SA Broadcast Plane. The top layer is the Radio Network Layer, which contains specific protocols: 25.413 in the Control Plane, 25.415 in the User Plane, and 25.419 in the SA Broadcast Plane. Below this is the Transport Network Layer, which is subdivided into Transport User Plane and Network Plane. The Control Plane's Transport User Plane contains protocol 25.412. The User Plane's Transport User Plane contains protocol 25.414. The SA Broadcast Plane's Transport User Plane also contains protocol 25.414. A common Network Plane at the bottom of the Transport Network Layer contains protocol 25.411. Arrows indicate the flow of data between the Radio Network Layer protocols and the corresponding Transport Network Layer components.](db5ab5d386827a5d5f5fad0f45612b90_img.jpg)
+
+Figure 7.1: Summary of Iu Interface Specification Structure. This diagram illustrates the protocol stack for the Iu interface, organized into three vertical columns: Control Plane, User Plane, and SA Broadcast Plane. The top layer is the Radio Network Layer, which contains specific protocols: 25.413 in the Control Plane, 25.415 in the User Plane, and 25.419 in the SA Broadcast Plane. Below this is the Transport Network Layer, which is subdivided into Transport User Plane and Network Plane. The Control Plane's Transport User Plane contains protocol 25.412. The User Plane's Transport User Plane contains protocol 25.414. The SA Broadcast Plane's Transport User Plane also contains protocol 25.414. A common Network Plane at the bottom of the Transport Network Layer contains protocol 25.411. Arrows indicate the flow of data between the Radio Network Layer protocols and the corresponding Transport Network Layer components.
+
+Figure 7.1: Summary of I<sub>u</sub> Interface Specification Structure
+
+# Annex A (informative): Change History
+
+| Date / TSG | TSG Doc   | CR   | Rev | Subject/Comment                                                            | New    |
+|------------|-----------|------|-----|----------------------------------------------------------------------------|--------|
+| 12/2008    | -         | -    | -   | Creation of Rel-8 version based on v7.0.0                                  | 8.0.0  |
+| RP-43      | RP-090078 | 0068 | 1   | RANAP: Enhanced Relocation Complete Request in SCCP: Connection Request    | 8.1.0  |
+| 12/2009    | -         | -    | -   | Created version 9.0.0 based on v. 8.1.0                                    | 9.0.0  |
+| 12/2010    |           |      |     | Created version 10.0.0 based on v. 9.0.0                                   | 10.0.0 |
+| RP-50      | RP-101389 | 0070 | -   | Introduction of the SIPTO at Iu-PS Function                                | 10.0.0 |
+| SP-49      | SP-100629 |      | -   | Clarification on the use of References (TS 21.801 CR#0030)                 | 10.1.0 |
+| RP-51      | RP-110230 | 0074 | 1   | Support for MDT                                                            | 10.1.0 |
+| RP-52      | RP-110684 | 0075 | -   | Correction of references                                                   | 10.2.0 |
+| 09/2012    |           |      |     | Update to Rel-11 version (MCC)                                             | 11.0.0 |
+| RP-62      | RP-131909 | 0076 | 6   | Introduction of Standalone GW for SIPTO@LN                                 | 12.0.0 |
+| RP-70      | RP-152088 | 0077 | 1   | Introduction of improvements to CS/PS coordination in UTRAN Shared Network | 13.0.0 |
+
+| Change history |         |           |      |     |     |                                                  |             |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                  | New version |
+| 2017-03        | RAN#75  | RP-170545 | 0079 | 1   | B   | Introduction of QMC for streaming services       | 14.0.0      |
+| 2018-06        | SA#80   | -         | -    | -   | -   | Promotion to Release 15 without technical change | 15.0.0      |
+| 2020-07        | SA#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                   | 16.0.0      |
+| 2022-03        | SA#95-e |           |      |     |     | Promotion to Release 17 without technical change | 17.0.0      |